Glasgow Surname Project

Individual research record

William R Glasco

1876-05-24 – 1944-08-04

Glasco-166 · 1 mapped association

Pennsylvania, United StatesKennett Square, Chester, Pennsylvania, United States

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
3Close relations
1Evidence items
7Candidate leads
Birth
1876-05-24 · Pennsylvania, United States
Death
1944-08-04 · Kennett Square, Chester, Pennsylvania, United States
Parents
Amy Glasgowunmarked
Spouses
Annie (Johnson) Glasco
Children
Henry Junior Glasco
Gender
Male
WikiTree
Glasco-166
Research clusters
Worldwide One-Tree profile leads
Mapped descendants
2

Comparison context

These child positions and checks are the subject details used to rank possible parents below.

Naming sequence used by the parentage model

Paternal grandfather positionHenry Junior Glasco (1899)
Maternal grandfather positionNot identifiable from dated child profiles
Maternal grandmother positionNot identifiable from dated child profiles
Paternal grandmother positionNot identifiable from dated child profiles

Known-position checks: 0 support · 0 conflict. Ordinals retain unnamed children and recognise reused names.

Relationship comparison

Potential parents or duplicates

Compare scored leads with the subject details above—not proof.

Higher-signal leadReview carefullyWeak lead

Possible fathers5 leads

Automated fit35/100
Weak Lead
Dates1852–1925Generation24 years age gapRecorded placesGlasgow, Cambria County, Pennsylvania, United States · GlasgowIndependent clue breadth · 6Age · Broad Geography · Household · Same-Sex Generational Naming · Spouse · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 24-year parent-child age gap (+18)
  • known spouse Sarah Elizabeth (Irwin) Glasgow had a plausible maternal age (28) at the subject's birth (+7)
  • candidate's birth is 47 years before the subject's earliest dated child (1899), a compatible grandparent-generation interval (+4)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 24-year parent-child age gap (+18)
  • candidate's birth is 47 years before the subject's earliest dated child (1899), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: pennsylvania (+1; not a locality match)
  • a known child was born within 5 years of the subject (+1)
  • known spouse Sarah Elizabeth (Irwin) Glasgow had a plausible maternal age (28) at the subject's birth (+7)
  • candidate and subject share the given name William (+4; weak direct parent-child name recurrence, 223 public profiles)

Deductions and cautions: No indexed conflict; documentary proof still required

Automated fit33/100
Weak Lead
Dates1840–?Generation36 years age gapRecorded placesKirkurdIndependent clue breadth · 4Age · Same-Sex Generational Naming · Spouse · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 36-year parent-child age gap (+18)
  • known spouse Jean (Watson) Glasgow had a plausible maternal age (35) at the subject's birth (+7)
  • candidate's birth is 59 years before the subject's earliest dated child (1899), a compatible grandparent-generation interval (+4)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 36-year parent-child age gap (+18)
  • candidate's birth is 59 years before the subject's earliest dated child (1899), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • known spouse Jean (Watson) Glasgow had a plausible maternal age (35) at the subject's birth (+7)
  • candidate and subject share the given name William (+4; weak direct parent-child name recurrence, 223 public profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show 3 lower-scoring possible fathers
Automated fit29/100
Weak Lead
Dates1838–1914Generation38 years age gapRecorded placesHenry, Henry, Tennessee, United States · Mcgregor, Mclennan, Texas, United StatesIndependent clue breadth · 5Age · Same-Sex Generational Naming · Spouse · Spouse-Specific Child Window · Two-GenerationSame-spouse child windowManerva Jane (Burns) GlasgowCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 38-year parent-child age gap (+18)
  • known spouse Manerva Jane (Burns) Glasgow had a plausible maternal age (33) at the subject's birth (+7)
  • candidate's birth is 61 years before the subject's earliest dated child (1899), a compatible grandparent-generation interval (+4)

same country, but no indexed locality overlap (−10)

Show complete scoring
  • plausible 38-year parent-child age gap (+18)
  • candidate's birth is 61 years before the subject's earliest dated child (1899), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • subject's birth fits between children attributed to the same parental couple (1864–1883) (+6; other parent Manerva Jane (Burns) Glasgow)
  • known spouse Manerva Jane (Burns) Glasgow had a plausible maternal age (33) at the subject's birth (+7)
  • candidate and subject share the given name William (+4; weak direct parent-child name recurrence, 223 public profiles)

Deductions and cautions: same country, but no indexed locality overlap (−10)

Automated fit29/100
Weak Lead
Dates1835–1914Generation41 years age gapRecorded placesIndiana, United States · Osgood, Ripley, Indiana, United States · Indiana, USAIndependent clue breadth · 5Age · Same-Sex Generational Naming · Spouse · Spouse-Specific Child Window · Two-GenerationSame-spouse child windowEllen A (Hebbard) GlasgowCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 41-year parent-child age gap (+18)
  • known spouse Ellen A (Hebbard) Glasgow had a plausible maternal age (33) at the subject's birth (+7)
  • candidate's birth is 64 years before the subject's earliest dated child (1899), a compatible grandparent-generation interval (+4)

same country, but no indexed locality overlap (−10)

Show complete scoring
  • plausible 41-year parent-child age gap (+18)
  • candidate's birth is 64 years before the subject's earliest dated child (1899), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • subject's birth fits between children attributed to the same parental couple (1866–1877) (+6; other parent Ellen A (Hebbard) Glasgow)
  • known spouse Ellen A (Hebbard) Glasgow had a plausible maternal age (33) at the subject's birth (+7)
  • candidate and subject share the given name William (+4; weak direct parent-child name recurrence, 223 public profiles)

Deductions and cautions: same country, but no indexed locality overlap (−10)

Automated fit27/100
Weak Lead
Dates1856–1909Generation20 years age gapRecorded placesYoungstown, Mahoning, Ohio, United States · Philadelphia, Pennsylvania, United StatesIndependent clue breadth · 4Age · Broad Geography · Same-Sex Generational Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 20-year parent-child age gap (+18)
  • candidate's birth is 43 years before the subject's earliest dated child (1899), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: pennsylvania (+1; not a locality match)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 20-year parent-child age gap (+18)
  • candidate's birth is 43 years before the subject's earliest dated child (1899), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: pennsylvania (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name William (+4; weak direct parent-child name recurrence, 223 public profiles)

Deductions and cautions: No indexed conflict; documentary proof still required

How parent leads are calculated

Automated leads use birth surnames—not married surnames—as parental eligibility, role-specific biological age limits, bounded and approximate-date uncertainty, household chronology, specific time-aware localities, mapped distance, tenancy succession, migration destinations and sex-aware Scottish naming positions across generations. People already attached as the subject's parents stay in the identity summary and are excluded from this alternative-candidate list, regardless of relationship confidence. The main calibration uses clues available on disconnected profiles; existing parent and sibling links are retained as comparison context rather than treated as transferable evidence. Common ordered names and grandparent-to-child echoes receive a small non-zero weight, so a John or James match can support several independent criteria without producing a lead alone. Rare names, repeated bearers and bundles across otherwise distinct branches receive substantially more weight according to catalogue frequency. An exact migration place is weighted by its rarity and repetition across both branches; a shared destination country is worth only one point. Extra weight is added only when at least three independent clue types converge: naming, locality, specific migration, household chronology or collateral networks. Sparse profiles retain a clearly labelled chronology-only fallback instead of disappearing. Countries, states, counties and research clusters do not count as a shared locality, and fallback, broad representative or kin-inferred coordinates are excluded from distance scoring. Shared descendant profiles are removed before branch-name comparison. A candidate already recorded as a parent-in-law is excluded. A confident or independently supported parent is treated as settled; uncertain and unassessed attachments remain open to alternative comparison. A different linked parent, an uncle/aunt or grandparent path, and a matching existing child profile prevent an alternative from being classified as a strong direct-parent lead until the underlying tree conflict or duplicate is resolved. Familiar forms such as Bessie are normalised. Surname remains an eligibility filter worth zero points.

Naming customs, shared farms and occupations are circumstantial. Children, spouses and collateral relatives may be missing, and tree-derived family networks are not independent evidence. Scores rank research leads; they do not prove parentage.

Same-name candidate

William GlasgowGlasgow-757

Automated fit63/100
Similar Person
Dates1876–?PlacesPennsylvania, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • same birth year (+30)
  • shared recorded place (+20)

unassessed mother attachments differ (−5)

Full comparison detail
  • same first and last name (+18)
  • same birth year (+30)
  • shared recorded place (+20)

Conflicts: unassessed mother attachments differ (−5)

Same-name candidate

William GlasgowGlasgow-1036

Automated fit51/100
Similar Person
Dates1871–?PlacesPennsylvania, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 5 (+18)
  • shared recorded place (+20)

unassessed mother attachments differ (−5)

Full comparison detail
  • same first and last name (+18)
  • birth years within 5 (+18)
  • shared recorded place (+20)

Conflicts: unassessed mother attachments differ (−5)

How duplicate leads are calculated

Dates are eligibility gates, not merely deductions: chronologically impossible people are excluded. Dates, places, spouses, parent certainty and children's profiles and names are then compared. A high score is a prompt to inspect records, not a merge recommendation.

Open only what you need

Research & records

Life and record timelineChronological mapped occurrences and their underlying sources.1 record
b. 1876

Profile-stated birthplace: Pennsylvania, United States

Pennsylvania, United States

One-Tree export profile fields are search leads, not sources; relationships are shown only where the export supplies parent links.

One-Tree profile leadunknown
Source and mapping detail

WikiTree profile export for Glasco-166

No sufficiently specific citation match found.

Precision: Country-centre fallback for profile locality

Evidence assessmentWhat is supported, uncertain or disputed in the current case model.4 claims
1Tree Only

Documented or strongly supported

No claims in this category have been formally assessed.

Working hypotheses and conflicts

No claims in this category have been formally assessed.

Research questionsOpen problems, missing bridges and the next records to inspect.0 open

No formal open question is recorded for this person.

Sources and provenanceStructured citations and source-quality classifications.1 source

Source or provenance: quality describes the record layer, not every conclusion drawn from it.

  1. tree_only WikiTree profile export for Glasco-166
Technical profile and raw captureDataset metadata, machine dossier and captured WikiTree biography.Advanced

WikiTree profile information

Dataset: ONT_Glasco_2026-08-18T16_05.json · generated 2026-08-20

Machine-readable dossier