Untangling Three Men Named Matthias Whitney of Killingly

The trail began with a brief entry in the American Genealogical-Biographical Index pointing to Revolutionary War rolls for a Matthias Whitney of Connecticut. At first it seemed possible that the record might belong to Matthias Whitney born in 1747, a known resident of Killingly. But once the probate files were examined, it became clear that the real issue was not whether “Matthias Whitney” had service — it was determining which Matthias the record described.

Two probate files — one in 1776 and another in 1800 — proved that more than one man of that name lived in Killingly. A later Revolutionary War pension deposition then introduced a third. When the records are placed in chronological and geographic context, the identities separate cleanly.

Matthias Whitney (1720–1776)

Matthias Whitney, born 26 May 1720 in Groton, Massachusetts, son of Cornelius and Sarah (Shepard) Whitney, removed to Killingly, Connecticut, where he married Alice Robbins and raised his family.

His estate was probated in the Plainfield probate district in 1776. The file explicitly treats him as deceased and names his widow Alice and their children, including Jonathan.¹ This record fixes the end of his life in Killingly and establishes the first generation of the family there.

Because he was dead by June 1776, no later Revolutionary War record or nineteenth-century deposition can belong to him.

Matthias Whitney (1747–1800)

The second man was his son, Matthias Whitney, born in Killingly on 22 February 1747.

He died in 1800, and his estate was settled in the Plainfield probate district. The distribution is especially valuable because it preserves the birth order of the children:

the widow (not named)
George Whitney, eldest son
Sarah Whitney, eldest daughter
Martha Palmer, second daughter to the deceased
Aaron Whitney, second son
Selah Whitney, fourth daughter
Achsah Whitney, fifth daughter²

This is not simply a list of heirs — it is a ranked family structure.

Separate guardianship records dated October 1800 identify the younger children and give their ages:

Aaron Whitney, aged 12
Selah Whitney, aged 16
Achsah Whitney, aged 9³⁻⁵

These guardianships confirm that the Matthias who died in 1800 left minor children whose legal affairs were handled immediately in the Plainfield probate district. That evidence places his death in Connecticut and shows that his family remained there.

It also directly contradicts the long-repeated statement that this Matthias removed to Hancock, Massachusetts, and later to New York. If he had done so, his estate and his minor children would not be under the jurisdiction of the Plainfield probate court in 1800.

In addition, minor probate records exist for the children, including Aaron, further reinforcing that this family group belongs to the man who died in Connecticut.⁶

The Third Matthias: The Nephew/Cousin

The third man appears in an unexpected place — a deposition in the Revolutionary War pension file of Noah Day dated 1832.

In that statement, Matthias Whitney testified that he:

was born in Killingly, Connecticut
later removed to Hancock, Massachusetts
and afterward moved to New York⁷

This single paragraph explains the migration that Pierce associated with the wrong man.

This Matthias cannot be the 1720 Matthias, who was dead in 1776.
He cannot be the 1747 Matthias, who died in 1800.

He is instead the son of Joshua Whitney — the nephew of the elder Matthias and the cousin of Matthias (1747–1800).

Once he is placed correctly in the family, the geographical pattern makes sense. The deposition confirms that the man who went to Hancock and then to New York was a different Matthias — not the one whose estate was probated in Connecticut in 1800.

Pierce Revisited

Frederick Clifton Pierce correctly showed that multiple men named Matthias Whitney existed in this generation. However, on page 59 he assigned the Hancock, Massachusetts and New York residence to Matthias (1747–1800).⁸

The deposition demonstrates that this migration belongs to the nephew/cousin instead.

In that sense, Pierce preserved an important clue — the movement to Hancock and New York — but attached it to the wrong individual. The probate and guardianship records allow that clue to be reassigned to the correct Matthias.

Conclusion

The records resolve into three distinct men:

Matthias Whitney (1720–1776), the father, who died in Killingly and whose 1776 probate names his widow Alice and their children.¹

Matthias Whitney (1747–1800), the son, who died in Connecticut; his estate was divided among his widow and children in a clearly ordered distribution, and whose minor children — Aaron (12), Selah (16), and Achsah (9) — were placed under guardianship in October 1800.²⁻⁵

Matthias Whitney, the nephew/cousin, born in Killingly, later of Hancock, Massachusetts, and ultimately of New York, who gave a deposition in 1832 and is the best candidate for the Revolutionary War references that began this investigation.⁷

What first appeared to be a single confusing identity becomes, when the records are read together, three separate and well-documented lives.


Sources

  1. Plainfield (Connecticut) Probate District, estate of Matthias Whitney, 1776.
  2. Plainfield (Connecticut) Probate District, estate distribution of Matthias Whitney, 1800.
  3. Plainfield (Connecticut) Probate District, guardianship of Aaron Whitney, October 1800; aged 12.
  4. Plainfield (Connecticut) Probate District, guardianship of Selah Whitney, October 1800; aged 16.
  5. Plainfield (Connecticut) Probate District, guardianship of Achsah Whitney, October 1800; aged 9.
  6. Plainfield (Connecticut) Probate District, minor probate for Aaron Whitney, son of Matthias Whitney, 1800.
  7. Revolutionary War pension file of Noah Day, deposition of Matthias Whitney, 1832; states he was born in Killingly, removed to Hancock, Massachusetts, and later to New York.
  8. Frederick Clifton Pierce, The Descendants of John Whitney, Who Came from London, England, to Watertown, Massachusetts, in 1635 (Chicago: Press of W. B. Conkey Company, 1895), 59.

Working with French-Canadian Naming Practices

By the time a researcher encounters a family such as the Seguin dit Laderoute family, it becomes clear that the challenge of French-Canadian genealogy does not lie in missing records. Parish and notarial documentation in Québec is often abundant, continuous, and well preserved. The difficulty lies instead in how names were used and recorded.

The preceding posts have examined devotional given names, dit surnames, and the way these practices intersect across different record types. This final post brings those observations together and offers a framework for working with French-Canadian records without losing track of individuals.

Quebec, Canada, Notarial Records for Pierre Seguin and Barbe Fillion 2 Feb 1704

Names Are Descriptive, Not Fixed Identifiers

In eighteenth-century Québec, names functioned descriptively rather than administratively. A record identified a person sufficiently for its purpose, not permanently or exclusively. Baptismal records emphasized religious identity and parentage. Marriage contracts emphasized legal standing and family affiliation. Later records might emphasize marital status or residence.

As a result, variation in recorded names should be expected. Consistency across every record was neither required nor sought by the clerks who created them.¹


Record Context Matters More Than Name Form

When names appear unstable, context provides continuity. Place, chronology, family relationships, and associates consistently identify individuals even when name forms shift. In the Seguin dit Laderoute family, apparent contradictions dissolve once records are evaluated across an entire lifetime rather than in isolation.

This approach requires resisting the impulse to resolve name differences immediately. Instead, patterns emerge through accumulation of evidence.


Dit Names Are Additive, Not Substitutive

Dit names such as Laderoute added information; they did not replace surnames. Their appearance, disappearance, or reversal within records reflects clerical habit and context rather than a change in family identity. Treating dit names as aliases rather than alternate surnames allows records to be read cohesively.²

Written variations—dit, d’, de, or alias—serve the same function and should be interpreted as equivalent unless evidence suggests otherwise.


Women’s Identities Require Particular Care

Women’s records often reflect multiple identities: birth family, dit name, and marital association. A woman may appear under any of these forms depending on the type of record. This is not evidence of disappearance or duplication but of a system in which identity was situational.

Following women across records requires particular attention to place and relationships, especially in communities where given names repeat across siblings and generations.


Modern Systems Introduce Their Own Distortions

Many difficulties encountered today arise not from the historical records themselves, but from the modern systems used to organize them. Databases that require a single “correct” name or prioritize uniformity can unintentionally fragment individuals or merge distinct people.

Recognizing the limits of modern indexing is an essential part of working responsibly with French-Canadian sources.³


Reading the Records on Their Own Terms

The solution to French-Canadian naming challenges is not standardization, but interpretation. Recording names as they appear, noting variation, and evaluating identity through corroborating evidence allows the records to speak in their own language.

The Seguin dit Laderoute family illustrates that what initially appears confusing often reflects a coherent and functional naming system once its underlying conventions are understood.


Conclusion

French-Canadian records reward patience and context. Names that appear unstable are often reliable once viewed within their cultural and historical framework. By approaching these records with an understanding of devotional naming, dit names, and record-specific priorities, researchers can move beyond frustration and toward clarity.

The goal is not to force eighteenth-century records to conform to modern expectations, but to learn how identity was expressed at the time those records were created.


Notes

  1. Allan Greer, The People of New France (Toronto: University of Toronto Press, 1997), 63–66.
  2. René Jetté, Dictionnaire généalogique des familles du Québec (Montréal: Les Presses de l’Université de Montréal, 1983), introduction.
  3. Québec, Canada, Vital and Church Records (Drouin Collection); Québec, Canada, Notarial Records, 1637–1935.

When One Person Has Many Names

After examining devotional given names and dit surnames separately, it becomes clear that the real challenge for modern researchers lies in how these practices interact across different types of records. A single individual may appear under several legitimate name forms over the course of a lifetime, depending on the context in which the record was created.

The Seguin dit Laderoute family provides a clear example of this phenomenon, particularly in the records of Pierre Seguin dit Laderoute’s daughter, Marie Geneviève Seguin dit Laderoute.


Baptismal Identity

Marie Geneviève Seguin dit Laderoute was baptized in 1712.¹ In her baptismal record, she appears with both a devotional given name and a family surname that includes the dit name. At this stage of life, the record reflects the priorities of the Church: religious naming conventions and parental identity.

The baptismal name establishes her place within the family, but it does not define how she will necessarily appear in later records.


Marriage Records and Name Selection

When Marie Geneviève married Jean Beauchamp in 1731, her name appears in a notarial marriage record that identifies her as Geneviève Seguin dit Laderoute.² In this context, the emphasis shifts. The notary’s concern is legal identity and family affiliation rather than devotional completeness.

The omission of “Marie” in this record does not indicate a different person. Instead, it reflects the common practice of using the second given name as the practical identifier in adulthood.


Later Records and Variability

In later records associated with Marie Geneviève—whether related to the baptisms of her children, the marriages of those children, or notarial acts involving the family—her name may appear in additional forms. She may be recorded as Geneviève Seguin, Geneviève Laderoute, or Geneviève Beauchamp, depending on the type of record and the habits of the clerk.³

Each of these forms is historically valid. None represents a change in identity. Rather, each reflects a different aspect of her life: birth family, married status, or legal context.


Why Modern Systems Struggle

Modern genealogical systems tend to treat names as fixed identifiers. When applied to French-Canadian records, this assumption often leads to confusion. A woman such as Marie Geneviève Seguin dit Laderoute may be divided into multiple profiles because her name appears differently in different records, or incorrectly merged with another individual who shares a similar name.

In reality, the records themselves are consistent once their conventions are understood. It is the modern expectation of uniformity that creates the apparent conflict.


Reading Records Across a Lifetime

Understanding how names functioned in New France requires reading records across an individual’s entire life rather than in isolation. Baptismal, marriage, burial, and notarial records each served different purposes and therefore emphasized different aspects of identity.

For Marie Geneviève Seguin dit Laderoute, the variation in name forms across records reflects continuity rather than contradiction. Place, chronology, family relationships, and associates provide the connective tissue that confirms identity when names alone appear unstable.


Preparing for the Final Post

This examination of one individual demonstrates how devotional given names, dit surnames, and clerical habit combine to produce legitimate variation in the historical record. The challenge for researchers is not to force consistency where none existed, but to recognize patterns that reflect historical practice.

The final post in this series will step back from this specific family and offer practical guidance on how to approach French-Canadian records more generally, drawing on the examples already discussed.


Notes

  1. Québec, Canada, Vital and Church Records (Drouin Collection), baptism of Marie Geneviève Seguin dit Laderoute, 1712.
  2. Québec, Canada, Notarial Records, marriage contract of Jean Beauchamp and Geneviève Seguin dit Laderoute, 12 August 1731.
  3. Québec, Canada, Vital and Church Records (Drouin Collection), various baptisms and marriages involving the Beauchamp family, mid-eighteenth century.

What Does “dit Laderoute” Mean?

After grappling with repeated given names such as “Marie,” many researchers encounter a second layer of complexity in French-Canadian records: the appearance of an additional name introduced by the word dit. In the Seguin dit Laderoute family, this additional name—Laderoute—appears consistently across generations and records, raising questions about whether it represents a surname change, a nickname, or a separate family altogether.

In fact, dit names were a common and functional feature of naming practices in New France. Understanding how they were used—and how they were written—is essential for interpreting the records correctly.


The Meaning and Purpose of Dit Names

The French word dit means “called” or “known as.” A dit name functioned as an alias rather than a replacement surname. It could serve several purposes: distinguishing individuals with the same surname, identifying a particular branch of a family, reflecting military service, or referencing a place or personal characteristic.¹

Importantly, the presence of a dit name did not erase the original surname. Both names could be used independently or together, depending on context, clerk, or habit.


Pierre Seguin dit Laderoute

In this family, the surname Seguin appears alongside the dit name Laderoute beginning with Pierre Seguin dit Laderoute and continuing among his children. Pierre did not “become” a Laderoute; rather, he belonged to the Seguin family and was also known as Laderoute.

Across parish and notarial records, Pierre may be identified as Pierre Seguin, Pierre Laderoute, or Pierre Seguin dit Laderoute. Each of these forms refers to the same individual. The choice of name reflects the habits of the priest or notary who created the record, not a change in identity.


Variations in the Written Form of Dit Names

Modern researchers often encounter dit names written in several different forms and may assume that these variations reflect different meanings. In eighteenth-century Québec, this assumption is misleading.

The word dit may appear written in full, abbreviated, or contracted, including forms such as dit, d’, de, or occasionally alias.² These variations reflect clerical preference and writing speed rather than any distinction in function or status.

For example, entries recorded as Seguin dit Laderoute, Seguin d’Laderoute, or Seguin de Laderoute all convey the same meaning: Seguin, called Laderoute. The contracted form d’ is particularly common in notarial records and should not be interpreted as a marker of nobility, geographic origin, or surname change.


Dit Names Across Generations

The use of dit names was often inherited, though not always consistently. Some children retained the dit name, some used only the original surname, and others alternated between the two across their lifetimes. In the Seguin dit Laderoute family, Pierre’s children appear with varying forms of the surname, sometimes emphasizing “Seguin,” sometimes “Laderoute,” and sometimes both.

This variability does not indicate separate families or lines. Instead, it reflects a flexible naming system in which multiple identifiers could coexist without conflict.


Dit Names and Women’s Records

For women, dit names introduce additional complexity. A woman might appear under her baptismal surname, her dit name, her husband’s surname, or a combination of these forms depending on the type of record. In the Seguin dit Laderoute family, the presence or absence of “Laderoute” in later records does not signal a change in family affiliation.

As with given names, variation in surname form should be understood as a feature of the record-keeping system rather than evidence of multiple individuals.


Reading Dit Names in Context

The presence of a dit name signals that a record belongs to a naming system different from the modern one. Rather than attempting to standardize or correct these names, researchers benefit most from recording them as they appear and evaluating identity through corroborating evidence such as place, chronology, and family relationships.

The Seguin dit Laderoute family provides a clear example of how dit names functioned as flexible identifiers within a stable community. Recognizing this flexibility is essential for avoiding false divisions and misinterpretations in French-Canadian genealogical research.

In the next post, the focus will shift from naming systems themselves to the records that preserve them, and to how a single individual can legitimately appear under multiple name forms across baptisms, marriages, burials, and notarial documents.


Notes

  1. René Jetté, Dictionnaire généalogique des familles du Québec (Montréal: Les Presses de l’Université de Montréal, 1983), introduction; Yves Landry, Les noms de famille en Nouvelle-France (Montréal: Septentrion, 1992).
  2. Québec, Canada, Notarial Records, 1637–1935; parish registers of the Montreal and Lanaudière regions, eighteenth century, passim.

Born in Ohio, Pennsylvania, or Somewhere Else? Resolving Conflicting Records for George Lawhead

Anyone who researches nineteenth-century families eventually encounters the same problem: the records do not agree. Birthplaces shift. Ages fluctuate. Census entries contradict one another. The question is not whether conflicts exist, but how they can be evaluated responsibly.

George Washington Lawhead provides an unusually well-documented case study. Across census records, military documents, marriage records, and his death certificate, his place and year of birth vary repeatedly. Rather than choosing a single record and discarding the rest, this post examines how those conflicts can be weighed and resolved.

George Lawhead Civil War Pension Photo

The Competing Birthplaces

Records associated with George Lawhead list three different states as his birthplace:

  • Ohio
  • New York
  • Pennsylvania

Ohio appears most frequently, including in the 1850, 1860, and 1880 federal censuses.¹ New York appears once, in the 1870 census.² Pennsylvania appears in the 1900 census and on George’s death certificate.³

When evaluating these conflicts, the first question is not which record is newest or most detailed, but who supplied the information and how close that informant was to the event being recorded.


Census Records and Enumerator Error

The 1850 and 1860 censuses place George in households headed by relatives, listing his birthplace as Ohio. These entries were created while George was still a child or young adult and likely relied on information provided by family members with direct knowledge of his birth.

The 1870 census, which lists his birthplace as New York, presents a different problem. That same census page incorrectly lists New York as the birthplace of George’s mother-in-law, who is known from other records to have been born in Vermont. The surrounding entries show a strong pattern of Michigan and New York birthplaces, suggesting enumerator habit rather than individual accuracy. In this context, the New York entry is best treated as an error rather than a competing claim.


Pennsylvania and Late-Life Informants

The 1900 census and George’s 1905 death certificate both give his birthplace as Pennsylvania. In each case, George himself was unlikely to have been the informant.

The 1900 census information was almost certainly supplied by Henrietta Savage, with whom George was living at the time. The death certificate lists the undertaker as the informant, who would have obtained his information secondhand, most likely from Henrietta.⁴

George Lawhead’s death certificate

These records were created decades after George’s birth and depend on memory rather than firsthand knowledge. They also conflict with the majority of earlier records, making them less reliable for determining birthplace.


County Confusion: Morrow vs. Monroe

Several records narrow George’s birthplace further, naming Westfield Township and alternately identifying the county as Morrow or Monroe. This apparent contradiction dissolves when examined historically.

Morrow County, Ohio, did not exist at the time of George’s birth. It was formed in 1848 from portions of Delaware, Marion, Knox, and Richland counties. Westfield Township later became part of Morrow County, but would have belonged to Delaware County at the time of George’s birth in 1845.

Morrow County – the colors indicating the 4 counties from which it was formed.

Monroe County, Ohio, does exist, but has no Westfield Township. The similarity in pronunciation between Morrow and Monroe provides a plausible explanation for the inconsistency. When combined with the presence of Lawhead family records, burials, and probate documents in what became Morrow County, Westfield Township in central Ohio emerges as the most consistent location.


The Question of the Birth Year

George’s reported birth year varies among 1842, 1843, 1845, and occasionally 1846. The date itself, February 10, remains consistent across multiple records.

The earliest census records support an 1845 birth year. Later records, including enlistment papers and some marriage records, imply an earlier birth year that would have made George legally eligible to enlist at age eighteen in 1861.

Age inflation among underage Civil War enlistees was common and well documented. Once a false age entered the record, it often persisted, especially in documents created close in time to military service. In George’s case, the later reappearance of an earlier birth year can be explained by proximity to his enlistment and the continued reuse of that information in subsequent records.

When all records are considered together, 1845 is supported by the greatest number of independent sources, including early census records and family documentation.


Weighing the Evidence

Resolving conflicting records requires pattern recognition rather than certainty from a single source. In George Lawhead’s case:

  • Ohio appears as his birthplace in the majority of records
  • Early records agree more consistently than late ones
  • Errors cluster by document type rather than randomly
  • Informant knowledge declines over time

Taken together, the evidence supports a conclusion that George Washington Lawhead was born on 10 February 1845 in Westfield Township, in what later became Morrow County, Ohio.

This conclusion does not require discarding conflicting records. Instead, it acknowledges them, explains them, and assigns them appropriate weight.


Conclusion

Conflicting records are not obstacles to genealogical research; they are evidence themselves. They reveal who was asked, who answered, and how information moved through families and institutions over time.

George Lawhead’s records demonstrate why no single document should be treated as definitive in isolation. By examining context, informants, timing, and patterns, it is possible to reach a conclusion that respects the complexity of the historical record without overstating certainty.

In that sense, George Lawhead’s story offers more than a set of dates and places. It offers a model for how genealogical conflicts can be approached thoughtfully and responsibly.


Sources

  1. 1850, 1860, and 1880 U.S. Federal Census records for George Lawhead.
  2. 1870 U.S. Federal Census, Grant Township, Iosco County, Michigan.
  3. 1900 U.S. Federal Census and Michigan death certificate, 1905.
  4. Michigan death record, East Jordan, Charlevoix County, Michigan.

A Three-Inch Pension File: How the Federal Government Rebuilt One Man’s Family

By the time the Civil War pension file of George Washington Lawhead was closed, it measured nearly three inches thick. That volume was not the result of a single application or a simple claim. Instead, it reflected decades of filings, investigations, affidavits, and competing narratives—all attempting to answer one question the federal government demanded be resolved with precision: who legally belonged to George Lawhead’s family?

The answer, as determined by pension law, did not always align with lived reality.

Henrietta, Ethel, George, Jessie Lawhead

Mary King and Claims Made During George’s Lifetime

Mary King began applying for George Lawhead’s pension while he was still alive.¹ She asserted abandonment and dependency, describing a marriage that had ended when George left her while she was pregnant with their second child. No divorce had ever been obtained.

These early claims were denied, but each filing generated documentation: correspondence, affidavits, and field examiner reports. Pension officials were required to confirm George’s service, identity, marital status, and financial responsibility. As a result, much of the pension file predates George’s death.

Mary’s persistence mattered. Although unsuccessful at the time, her filings preserved testimony and evidence that would later become central to posthumous decisions.


Abandonment, Not Divorce

Under nineteenth-century pension law, abandonment did not dissolve a marriage. Without a legal divorce, Mary King remained George Lawhead’s lawful wife regardless of separation, distance, or the passage of time.

This distinction would later prove decisive. Pension officials consistently noted that George had never obtained a divorce from Mary.² The legal bond between them remained intact until his death, even as George formed subsequent families elsewhere.


Henrietta Savage and a Public Separation

By the early 1890s, George was living with Henrietta Savage. Henrietta was herself legally married and the mother of several children when she left her husband to live with George. In January 1892, a Michigan newspaper reported on the separation, making the situation a matter of public record.³

George and Henrietta lived together for years and had two daughters. Census records show them functioning as a household, and George supported the family financially when able. None of these facts were disputed during the pension investigation.

What remained in question was not whether the family existed, but whether it could be recognized under the law.


The Pension Bureau’s Role

The Bureau of Pensions did not judge morality or domestic harmony. Its task was narrower and more rigid: to determine eligibility under federal statute.

Investigators examined:

  • the legality of each marriage
  • the absence or presence of divorce decrees
  • the timing of relationships
  • sworn testimony from claimants and witnesses

Each relationship was assessed not as a lived experience, but as a legal status.


Competing Claims After George’s Death

George Washington Lawhead died on 20 January 1905.⁴ After his death, two women filed pension claims as his widow: Mary King and Henrietta Savage.

This triggered one of the most detailed posthumous investigations in the file. Pension examiners revisited decades-old records, re-interviewed witnesses, and re-evaluated earlier findings—including the determination that George Lawhead and George Loyd were the same man.

Mary King’s claim rested on the absence of divorce and the validity of her marriage. Henrietta’s claim rested on years of cohabitation, financial dependency, and the presence of minor children.


The 1912 Ruling

In 1912, the Bureau of Pensions issued its final ruling.⁵ Mary King was declared George Lawhead’s lawful widow.

The decision rested on two findings:

  1. George had never divorced Mary King.
  2. Mary’s earlier marriage was determined to have been legally void due to her age at the time, rendering her free to marry George in 1865.

As a result, all of George’s later marriages were deemed legally invalid for pension purposes. Henrietta Savage’s claim was denied, as were claims filed on behalf of her children.

This ruling did not negate the existence of George’s later family. It simply placed that family outside the boundaries recognized by federal pension law.


Children Acknowledged, Benefits Denied

One of the most difficult aspects of the case was the treatment of George’s children with Henrietta Savage. Pension records acknowledged their birth and dependency. Their relationship to George was not disputed.

However, under the law as applied, their mother was not a lawful widow, and the children were therefore ineligible for benefits derived from her claim. The pension system recognized biological relationships but prioritized marital legality.


Why the File Is So Large

George Lawhead’s pension file is thick because it documents conflict over time, not a single dispute. It contains:

  • early abandonment claims
  • identity investigations
  • medical examinations
  • competing widow applications
  • posthumous legal review

Each layer built upon the last, preserving voices that would otherwise be lost: Mary King’s persistence, Henrietta Savage’s testimony, family members’ affidavits, and investigators’ conclusions.


Conclusion

The pension file of George Washington Lawhead illustrates the distance between lived family and legal family in nineteenth-century America. It shows how federal systems imposed rigid definitions on complex human relationships—and how those definitions carried lasting consequences.

By the time the government finished reconstructing George Lawhead’s family, the man himself had been dead for years. What remained was a record not just of service and disability, but of how law, identity, and family collided in the aftermath of war.


Sources

  1. Pension correspondence and affidavits filed by Mary King during George Lawhead’s lifetime.
  2. Bureau of Pensions examiner notes regarding marital status and absence of divorce.
  3. Michigan newspaper report, January 1892, documenting Henrietta Savage’s separation.
  4. Michigan death record for George Washington Lawhead, 1905.
  5. Bureau of Pensions ruling on lawful widowhood, 1912.

When Did John Powell Really Die?

Solving an 1886–1887 Genealogical Mystery with Weather, Newspapers, and Cemetery Records

One of the most frustrating problems in genealogy is when official records and newspapers disagree. That is exactly what happened with John Powell of Pontiac, Michigan — and it took three independent record systems and 19th-century weather data to resolve it.

At first glance, the sources contradict each other:

  • Oakland County’s death register records John Powell’s death as 31 December 1886.
  • Two notices in The Pontiac Bill Poster in early 1887 state that he “died last Saturday” and later say he “died Feb. 1887.”
  • His burial, according to Oak Hill Cemetery in Pontiac, occurred on Saturday, 29 January 1887.

Which date is correct?


The Official Record: December 31, 1886

The Oakland County “Return of Deaths” ledger lists:

John Powell, Pontiac — Dec. 31, 1886 — widower, aged 88 years, 4 months, 4 days, born New York.

This is not an estimate or a heading. The date Dec. 31, 1886 is written directly on John Powell’s line in the register.

More importantly, Oakland County holds no death certificate for him in 1887, meaning the county had already legally recorded his death in 1886. That establishes 31 December 1886 as his legal date of death.

Additionally, no probate record has been found for John Powell. Probate records can sometimes give the date of death.


What the Newspaper Really Reported

The Pontiac Bill Poster of Wednesday, February 2, 1887 states:

“John Powell, of Auburn, died last Saturday; aged 88 years, and funeral services were held Sunday at Amy Church. The remains were brought to Pontiac for burial.”

“Last Saturday” relative to Feb. 2, 1887 equals Saturday, January 29, 1887 — which is exactly the day Oak Hill Cemetery recorded his burial.

The newspaper was therefore describing the burial week, not the legal date of death. Oh, and if you are wondering about Amy Church – apparently Amy is what the locals called Auburn Hills/Auburn Heights at the time. This was most likely a Methodist Church, although so far, I have not been able to confirm this.

The Pontiac Bill Poster article a month later – with incorrect data on death and age is incorrect. Although I suspect the birth information is actually right.

Why Burial Was Delayed: The Ground Was Frozen Solid

Weather records now make the situation unmistakably clear.

Using official U.S. Signal Service observations from Windsor, Ontario (the nearest long-running station to Detroit and Pontiac), we can see when winter locked the ground.

From mid-December 1886, southeast Michigan entered a sustained hard freeze:

DateHighLow
Dec 1432°F24°F
Dec 1525°F6°F
Dec 1614°F7°F
Dec 1727°F−2°F
Dec 2520°F1°F
Dec 2813°F−5°F
Dec 3123°F10°F

From December 14 onward, nighttime temperatures stayed below freezing for more than two weeks. This means:

  • The soil would have been frozen by Christmas
  • Snow fell on frozen ground on Dec. 24 (6 inches) and Dec. 31 (4 inches)
  • The ground never thawed between mid-December and mid-January

On the day John Powell died — December 31, 1886 — conditions were brutal:

  • High 23°F
  • Low 10°F
  • 4 inches of fresh snow

Burial at that time would have required digging through frozen soil beneath heavy snow — something cemeteries avoided whenever possible.


When Burial Became Possible

A major thaw finally arrived in late January 1887:

DateHighLow
Jan 2045°F27°F
Jan 2251°F26°F
Jan 2456°F26°F
Jan 2842°F31°F
Jan 2942°F25°F

This was a ten-day thaw, long enough to soften frozen soil and allow graves to be opened. Oak Hill Cemetery buried John Powell on Saturday, January 29, 1887 — the first realistic opportunity.

Two days later winter returned with six inches of new snow on January 31.

The timing could not be clearer.


Putting It All Together

EventDateEvidence
DeathDec 31, 1886Oakland County death register
Heavy snow & frozen groundDec 31, 188623°F / 10°F, 4″ snow
Sustained thaw beginsJan 20, 1887Weather records
BurialSat Jan 29, 1887Oak Hill Cemetery
FuneralSun Jan 30, 1887Pontiac Bill Poster
Obituary printedFeb 2, 1887Pontiac Bill Poster

The Correct Conclusion

John Powell died in Pontiac on 31 December 1886. He was buried on 29 January 1887 after winter conditions delayed burial for nearly a month.

The newspaper was reporting the burial and funeral, not the legal date of death — which is why the dates appeared to conflict.

In the end, vital records, cemetery logs, newspapers, and even the weather all tell the same story.


Sources

  1. Sources
    1. Oakland County, Michigan — Death Register (1886)
    Oakland County Clerk, Return of Deaths, entry for John Powell, Pontiac, dated 31 December 1886; widower, age 88, born New York.
    (Original handwritten county register; no 1887 death certificate exists for John Powell.)

    2. Oak Hill Cemetery, Pontiac, Michigan — Interment Register
    Oak Hill Cemetery sexton’s record for John Powell, showing burial on 29 January 1887.
    (Information confirmed directly with cemetery staff via phone call 15 January 2026 by the author.)

    3. The Pontiac Bill Poster (Pontiac, Michigan), 2 February 1887
    Obituary notice for John Powell, stating he “died last Saturday” and that “funeral services were held Sunday at Amy Church; the remains were brought to Pontiac for burial.”
    (“Last Saturday” relative to 2 Feb 1887 = 29 Jan 1887.)

    4. The Pontiac Bill Poster, 2 March 1887
    Biographical notice of John Powell, stating he “died Feb. 1887 aged 87.”
    (This later notice is a typo reflecting the burial/funeral month, not the legal death date.)

    5. U.S. Signal Service Weather Records — Windsor Riverside, Ontario (near Detroit & Pontiac)
    National Centers for Environmental Information (NOAA), Global Historical Climatology Network (GHCN-Daily):
    December 1886 daily observations, including 31 Dec 1886: high 23°F, low 10°F, 4 inches of snow, documenting frozen ground and active snowfall
    January 1887 daily observations, including Jan 29, 1887: high 42°F, low 25°F, no snow, documenting the thaw window that allowed burial and Jan 31, 1887: 6 inches of new snow

Who are Mr. & Mrs. Potter?

One of the many brick walls that I have is figuring out who the parents of Mary Potter Hickmott are. Mary Potter was born sometime between 1794 and 1801 (most likely before 1797) in England. I know this from several census records starting with the 1841 census for Horsmonden, Kent, England.

Screen Shot 2018-12-28 at 5.41.37 PM

The Potter surname is confirmed from a marriage index (no image of the original is found online – just an index, which of course could be wrong).

Screen Shot 2018-12-28 at 5.47.36 PM

When I first saw the 1841 census and saw there was a James Potter living with the Hickmotts, and that he was aged appropriately to be a brother of Mary, it turned me onto the name. So, combined with the marriage record, I’m fairly certain of the surname Potter.

So, who were Mary and James Potter’s parents? Darned good question. I still don’t know. Given that I know the Hickmotts were in Horsmonden for a number of years prior to this, it stands to reason the Potters may also be from there. However, there isn’t a record for a baptism of a Mary or James Potter in the 1790-1810 timeframe. So, I expanded my search to the surrounding area. I found a few possibilities – but not all of the parents are recorded, and of the ones that are recorded, there isn’t one couple that stands out as the possible parents of Mary and James (they all have different parents). There’s one baptism for a Mary Potter that catches my eye – but I discount it because the baptism date is my birthday (obviously different years) – so I think it catches my eye only because of that. Of course, it is certainly possible that Mary and James are not siblings – but close cousins (or not even related – just a coincidence of same surname). However, I tend to think that if something happened to James’ wife and he ended up a single parent of a young girl, that a female family member would step in to help out for a bit – which is why I hold the belief they were siblings.

This is one puzzle that may go unsolved….

Origin of a name

I remember when I was younger and had started wondering about my genealogy roots, asking my mother how she and dad came up with my name. She told me, “You were named after your father’s sister and one of my sisters who both died as babies.” Then she told me that if I had been born a boy, I would have been named after both grandfathers.

Names tend to run in families, with children being named after grandparents or siblings of the parents in order to honor them. So, I began to wonder about where the names came from – were my two aunts named after others and if so, who?

Mom’s sister was Carol Jean. Carol was born August 31, 1943 and died September 20, 1943. As far as I have been able to determine, Grandpa and Grandma didn’t name Carol Jean after any relatives. Her’s was a “new name” in that part of my family tree. Of course mom wasn’t the only one who wished to honor her sister as I have a cousin who also gets her name from this infant.

Dad’s sister was Nancy Jane. Nancy Jane was stillborn July 9, 1943 – a macerated fetus. She was 11 years after my father, and would be the last child of my paternal grandparents. Grandma named her only daughter after her paternal grandmother, Nancy Jane Whitney. Unfortunately, I haven’t been able to find much information on Nancy Jane Whitney’s family, so I’m not sure if she was a name sake too.

So, 30 years after their deaths, my two infant aunts had a namesake – me.

My brother was named after my father, so that made me wonder about my sister’s name. After all, she’s 13 years older than I am. When I asked mom – she told me they just liked the name – there wasn’t any other reason for her name. If you ask my sister, she’ll say she was named after a Johnny Cash song that dad liked – but that’s a bit hard to believe considering the song was released almost a decade after her birth. Sometimes names are just new to the family.

My paternal grandmother was partly named after her paternal great-aunt Sabria Whitney – and preferred to go by this name. My own father’s name  honors our Munson ancestry – where we descend from 3 generations of Daniel Munson, and our Lacy and Foster ancestries for his first name.

When my brother had his first child, he wanted that Daniel name to continue – and when that child turned out to be female, they feminized the name.