Glasgow Surname Project

Individual research record

Thomas Courtlyn Glasgow

1918-11-01 – 2000-10-22

Glasgow-2125 · 1 mapped association

Howard, Arkansas, United StatesHoward, Arkansas, United States

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
2Close relations
2Evidence items
12Candidate leads
Birth
1918-11-01 · Howard, Arkansas, United States
Death
2000-10-22 · Howard, Arkansas, United States
Parents
Not recorded
Spouses
Fern Carol (Rosik) Glasgow
Children
Donna Glasgow
Gender
Male
WikiTree
Glasgow-2125
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 fit23/100
Weak Lead
Dates1873–1952Generation45 years age gapRecorded placesRector, Clay Co., Arkansas, United States · Cardwell, Dunklin County, Missouri, United States · Rector, Clay Co., ARIndependent clue breadth · 3Age · Broad Geography · Same-Sex Generational NamingCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 45-year parent-child age gap (+18)
  • weak broad-area overlap: arkansas (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 45-year parent-child age gap (+18)
  • weak broad-area overlap: arkansas (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name Thomas (+4; weak direct parent-child name recurrence, 86 public profiles)

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

Automated fit19/100
Weak Lead
Dates1898–1953Generation20 years age gapRecorded placesTexas, United States · Norwalk, Los Angeles, California, United StatesIndependent clue breadth · 3Age · Same-Sex Generational Naming · SpouseCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 20-year parent-child age gap (+18)
  • known spouse Rachel (Pennington) Glasco had a plausible maternal age (18) at the subject's birth (+7)
  • same research cluster (+0; grouping is not kinship evidence)

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

Show complete scoring
  • plausible 20-year parent-child age gap (+18)
  • same research cluster (+0; grouping is not kinship evidence)
  • known spouse Rachel (Pennington) Glasco had a plausible maternal age (18) at the subject's birth (+7)
  • candidate and subject share the given name Thomas (+4; weak direct parent-child name recurrence, 86 public profiles)

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

Show 3 lower-scoring possible fathers
Automated fit16/100
Weak Lead
Dates1866–1930Generation52 years age gapRecorded placesRector, Clay, Arkansas, United States · Clay County, Arkansas, United States · Rector, Clay, Arkansas, USAIndependent clue breadth · 4Age · Broad Geography · Household · Local Sibling BirthCurrent relationshipNot currently linked as parent
Strongest signals
  • possible 52-year parent-child age gap (+10)
  • a known child was born within 5 years of the subject (+1)
  • weak broad-area overlap: arkansas (+1; not a locality match)

No indexed conflict; documentary proof still required

Show complete scoring
  • possible 52-year parent-child age gap (+10)
  • weak broad-area overlap: arkansas (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)
  • a known child was born within 5 years of the subject (+1)
  • candidate has another child, Madeline A Glasgow, born 5 years from the subject in the same specific birth locality (+4; possible sibling-household clue)

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

Automated fit12/100
Weak Lead
Dates1888–?Generation30 years age gapRecorded placesPennsylvania, United StatesIndependent clue breadth · 2Age · Same-Sex Generational NamingCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 30-year parent-child age gap (+18)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name Thomas (+4; weak direct parent-child name recurrence, 86 public profiles)

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

Show complete scoring
  • plausible 30-year parent-child age gap (+18)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name Thomas (+4; weak direct parent-child name recurrence, 86 public profiles)

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

Automated fit12/100
Weak Lead
Dates1878–?Generation40 years age gapRecorded placesAlabama, United StatesIndependent clue breadth · 2Age · Same-Sex Generational NamingCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 40-year parent-child age gap (+18)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name Thomas (+4; weak direct parent-child name recurrence, 86 public profiles)

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

Show complete scoring
  • plausible 40-year parent-child age gap (+18)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name Thomas (+4; weak direct parent-child name recurrence, 86 public profiles)

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

Possible mothers5 leads

Automated fit28/100
Chronology-Only Fallback
Dates1890–1987Generation28 years age gapRecorded placesHoward, Arkansas, United StatesIndependent clue breadth · 2Age · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 28-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 28-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
Dates1897–1969Generation21 years age gapRecorded placesArkansas, United States · Howard County, Arkansas, United States · Arkansas, USAIndependent clue breadth · 2Age · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 21-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: howard (+6)
  • same research cluster (+0; grouping is not kinship evidence)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 21-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: howard (+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 fit19/100
Chronology-Only Fallback
Dates1899–1982Generation19 years age gapRecorded placesLe Flore, Oklahoma, United States · Sebastian, Arkansas, United StatesIndependent clue breadth · 2Age · Broad GeographyCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 19-year parent-child age gap (+18)
  • weak broad-area overlap: arkansas (+1; not a locality match)
  • 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)
  • weak broad-area overlap: arkansas (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)

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

Automated fit19/100
Chronology-Only Fallback
Dates1898–?Generation20 years age gapRecorded placesArkansas, United States · ArkansasIndependent clue breadth · 2Age · Broad GeographyCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 20-year parent-child age gap (+18)
  • weak broad-area overlap: arkansas (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 20-year parent-child age gap (+18)
  • weak broad-area overlap: arkansas (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)

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

Automated fit19/100
Chronology-Only Fallback
Dates1898–1972Generation20 years age gapRecorded placesArkansas, United States · Lewisville, Lafayette County, Arkansas, United StatesIndependent clue breadth · 2Age · Broad GeographyCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 20-year parent-child age gap (+18)
  • weak broad-area overlap: arkansas (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 20-year parent-child age gap (+18)
  • weak broad-area overlap: arkansas (+1; not a locality match)
  • 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.

Automated fit36/100
Similar Person
Dates1921–1982PlacesWeakley County, Tennessee, United States → Weakley County, Tennessee, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 3 (+18)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 3 (+18)

Conflicts: No indexed conflict

Same-name candidate

Thomas S GlasgowGlasgow-1787

Automated fit20/100
Similar Person
Dates1898–?PlacesBallynasollus, Kildress, Cookstown, County Tyrone, Ireland, United KingdomParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 20 (+2)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 20 (+2)

Conflicts: No indexed conflict

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

Profile-stated birthplace: Howard, Arkansas, United States

Howard, Arkansas, 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-2125

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.3 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 Personal knowledge of his daughter, Donna Jean Glasgow.
  2. tree_only WikiTree profile export for Glasgow-2125
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-2125 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2022-02-04.

Profile location claims

EventDateLocationStatus
birthHoward, Arkansas, United StatesWikiTree profile field
deathHoward, Arkansas, United StatesWikiTree profile field
marriage1941-02-14Chillicothe, Livingston, Missouri, United StatesWikiTree relationship field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ChildrenDonnaGlasgow-901
SpousesFern Carol GlasgowRosik-61919-12-06 · Milford, Dickinson, Iowa, United States · 1994-05-30 · Nashville, Howard, Arkansas, United States · 1941-02-14 · Chillicothe, Livingston, Missouri, United States

Record-bearing passages

  • Biography He was known as Tom by those on my mother's side of the family, including his children, but he was called Courtlyn by his family of origin and others in his community where he grew up. Sources

    • Personal knowledge of his daughter, Donna Jean Glasgow.

Profile source citations

  1. Personal knowledge of his daughter, Donna Jean Glasgow.
Full captured biography text
Biography
He was known as Tom by those on my mother's side of the family, including his children, but he was called Courtlyn by his family of origin and others in his community where he grew up.
Sources
* Personal knowledge of his daughter, Donna Jean Glasgow.
Raw WikiTree biography markup
== Biography ==
He was known as Tom by those on my mother's side of the family, including his children, but he was called Courtlyn by his family of origin and others in his community where he grew up.

== Sources ==
<references />
* Personal knowledge of his daughter, Donna Jean Glasgow.