Next documented: Crittenden County, Kentucky, USA (1856) | Documented in 1850: Roane County, Tennessee, USA | Check these locations.
0 research attempt(s) — not yet researched
Log in to add a research attempt.
Our Family's Journey Through America
Record evaluation: No records evaluated
Print Preview / Print Chronology
Born 18 Mar 1850 · Died 19 Sep 1856
TNG facts are read-only. Member research is reviewed separately.
Automatically calculated research ideas, not documented facts. Existing matching TNG census, marriage, obituary, and probate events are excluded where identifiable. Other existing sources may require manual review.
Calculation: Known birth year in TNG; planning period 1850–1856 (80 years is a search horizon, not a death fact)
Next documented: Crittenden County, Kentucky, USA (1856) | Documented in 1850: Roane County, Tennessee, USA | Check these locations.
Log in to add a research attempt.
Check surviving population schedules; coverage varies by county and year.
Next documented: Crittenden County, Kentucky, USA (1856) | Documented in 1850: Roane County, Tennessee, USA | Check these locations.
Log in to add a research attempt.
Known death year; search newspapers near death and last known residence.
Last documented: Roane County, Tennessee, USA (1850) | Documented in 1856: Crittenden County, Kentucky, USA | Check these locations.
Log in to add a research attempt.
Known death year; investigate probate jurisdiction and surviving records.
Last documented: Roane County, Tennessee, USA (1850) | Documented in 1856: Crittenden County, Kentucky, USA | Check these locations.
Log in to add a research attempt.
TNG facts are read-only. Research proposals appear after administrator approval; pending proposals are visible to administrators.
Imported directly from the current TNG person record.
Imported directly from the current TNG person record.
Log in to TNG to submit research evidence or notes.
We strive to document all of our sources in this family tree. If you have something to add, please let us know. We will be happy to make any change if there is better documentation than what we have.