Glasgow Surname Project

Individual research record

Kenneth Wayne Glasgow

1948-06-14 – 2007-12-09

Glasgow-3866 · 1 mapped association

Halifax, North Carolina, United StatesRoanoke Rapids, Halifax, North Carolina, United States

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
1Close relations
2Evidence items
10Candidate leads
Birth
1948-06-14 · Halifax, North Carolina, United States
Death
2007-12-09 · Roanoke Rapids, Halifax, North Carolina, United States
Parents
Not recorded
Spouses
Not recorded
Children
Christopher Glasgow
Gender
Male
WikiTree
Glasgow-3866
Research clusters
Worldwide One-Tree profile leads
Mapped descendants
1

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 positionNot identifiable from dated child profiles
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 fit8/100
Weak Lead
Dates1931–1967Generation17 years age gapRecorded placesArlington, Virginia, United States · Alexandria, Virginia, United StatesIndependent clue breadth · 2Age · Same-Sex Generational NamingCurrent relationshipNot currently linked as parent
Strongest signals
  • possible 17-year parent-child age gap (+10)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name Kenneth (+8; weak direct parent-child name recurrence, 2 public profiles)

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

Show complete scoring
  • possible 17-year parent-child age gap (+10)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name Kenneth (+8; weak direct parent-child name recurrence, 2 public profiles)

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

Automated fit0/100
Weak Lead
Dates1889–1970Generation59 years age gapRecorded placesSurry County, North Carolina, United States · Alleghany County, North Carolina, United StatesIndependent clue breadth · 3Age · Local Sibling Birth · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • candidate has only broad or undated birth-locality overlap: north (+6)
  • less typical 59-year parent-child age gap (+2)
  • same research cluster (+0; grouping is not kinship evidence)

candidate's child Isom Glasco (Glasco-117) is also a plausible father in the subject's birth locality (−6; current tree places this candidate one generation farther back); no known spouse has a plausible maternal age at the subject's birth (−6; an unknown spouse remains possible)

Show complete scoring
  • less typical 59-year parent-child age gap (+2)
  • candidate has only broad or undated birth-locality overlap: north (+6)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate has another child, Nellie Fay (Glasco) Starnes, born 13 years from the subject in the same specific birth locality (+2; possible sibling-household clue)

Deductions and cautions: candidate's child Isom Glasco (Glasco-117) is also a plausible father in the subject's birth locality (−6; current tree places this candidate one generation farther back); no known spouse has a plausible maternal age at the subject's birth (−6; an unknown spouse remains possible)

Show 3 lower-scoring possible fathers

Possible Father

Isom GlascoGlasco-117

Automated fit31/100
Chronology-Only Fallback
Dates1924–1999Generation24 years age gapRecorded placesAlleghany County, North Carolina, United StatesIndependent clue breadth · 3Age · Spouse · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 24-year parent-child age gap (+18)
  • known spouse Nora Virginia (Combs) Glasco had a plausible maternal age (18) at the subject's birth (+7)
  • candidate has only broad or undated birth-locality overlap: north (+6)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 24-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: north (+6)
  • same research cluster (+0; grouping is not kinship evidence)
  • known spouse Nora Virginia (Combs) Glasco had a plausible maternal age (18) at the subject's birth (+7)

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

Automated fit28/100
Chronology-Only Fallback
Dates1915–2007Generation33 years age gapRecorded placesHalifax, North Carolina, United StatesIndependent clue breadth · 2Age · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 33-year parent-child age gap (+18)
  • candidate is associated with the subject's stated birthplace, but not by a reliable near-contemporary record (+10)
  • same research cluster (+0; grouping is not kinship evidence)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 33-year parent-child age gap (+18)
  • candidate is associated with the subject's stated birthplace, but not by a reliable near-contemporary record (+10)
  • same research cluster (+0; grouping is not kinship evidence)

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

Automated fit25/100
Chronology-Only Fallback
Dates1918–1997Generation30 years age gapRecorded placesHenderson Ky.Independent clue breadth · 2Age · SpouseCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 30-year parent-child age gap (+18)
  • known spouse Ruth L. (Siefferman) Glasco had a plausible maternal age (27) at the subject's birth (+7)
  • same research cluster (+0; grouping is not kinship evidence)

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

Show complete scoring
  • plausible 30-year parent-child age gap (+18)
  • same research cluster (+0; grouping is not kinship evidence)
  • known spouse Ruth L. (Siefferman) Glasco had a plausible maternal age (27) at the subject's birth (+7)

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

Possible mothers5 leads

Automated fit28/100
Chronology-Only Fallback
Dates1926–2024Generation22 years age gapRecorded placesHalifax, North Carolina, United States · Stuarts Draft, Augusta, Virginia, United StatesIndependent clue breadth · 2Age · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 22-year parent-child age gap (+18)
  • candidate is associated with the subject's stated birthplace, but not by a reliable near-contemporary record (+10)
  • same research cluster (+0; grouping is not kinship evidence)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 22-year parent-child age gap (+18)
  • candidate is associated with the subject's stated birthplace, but not by a reliable near-contemporary record (+10)
  • same research cluster (+0; grouping is not kinship evidence)

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

Automated fit24/100
Chronology-Only Fallback
Dates1930–1989Generation18 years age gapRecorded placesAlleghany, North Carolina, United StatesIndependent clue breadth · 2Age · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 18-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: north (+6)
  • same research cluster (+0; grouping is not kinship evidence)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 18-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: north (+6)
  • same research cluster (+0; grouping is not kinship evidence)

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

Show 3 lower-scoring possible mothers
Automated fit24/100
Chronology-Only Fallback
Dates1929–1999Generation19 years age gapRecorded placesAlleghany County, North Carolina, United StatesIndependent clue breadth · 2Age · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 19-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: north (+6)
  • same research cluster (+0; grouping is not kinship evidence)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 19-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: north (+6)
  • same research cluster (+0; grouping is not kinship evidence)

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

Automated fit24/100
Chronology-Only Fallback
Dates1929–2011Generation19 years age gapRecorded placesNorth Carolina, United StatesIndependent clue breadth · 2Age · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 19-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: north (+6)
  • same research cluster (+0; grouping is not kinship evidence)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 19-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: north (+6)
  • same research cluster (+0; grouping is not kinship evidence)

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

Automated fit24/100
Chronology-Only Fallback
Dates1926–1985Generation22 years age gapRecorded placesOmaha, Douglas, Nebraska, United States · North Platte, Lincoln, Nebraska, United StatesIndependent clue breadth · 2Age · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 22-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: north (+6)
  • same research cluster (+0; grouping is not kinship evidence)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 22-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: north (+6)
  • same research cluster (+0; grouping is not kinship evidence)

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.

No sufficiently similar same-name person is currently indexed.

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. 1948

Profile-stated birthplace: Halifax, North Carolina, United States

Halifax, North Carolina, 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 Glasgow-3866

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.2 claims
1Tree Only
1Unknown

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.2 sources

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

  1. unknown This was my father
  2. tree_only WikiTree profile export for Glasgow-3866
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

WikiTree biography, citations and relationship snapshot

Glasgow-3866 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2026-05-18.

Profile location claims

EventDateLocationStatus
birthHalifax, North Carolina, United StatesWikiTree profile field
deathRoanoke Rapids, Halifax, North Carolina, United StatesWikiTree profile field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ChildrenChristopherGlasgow-3865

Record-bearing passages

  • Biography Kenneth was born in 1948. He passed away in 2007. Sources

    • This was my father

Profile source citations

  1. This was my father
Full captured biography text
Biography
Kenneth was born in 1948. He passed away in 2007.
Sources
* This was my father
Raw WikiTree biography markup
== Biography ==

Kenneth was born in 1948.  He passed away in 2007.
== Sources ==
<references />
* This was my father