Place: Magisterial District 5, Big South Fork, Casey, Kentucky[4]
Residence:
User ID: 53DF068A7162D6E0F001BB9A80A131FC
Record ID Number: MH:IF1776
Date: 1900
Place: Magisterial District 5, Big South Fork, Casey, Kentucky[5]
Sources
↑ Brown-30900 was created by Casey Adams through the import of Casey.GED on Aug 5, 2014. This comment and citation can be deleted after the biography has been edited and primary sources are included.
↑ Source: #S24 Record ID Number: MH:SC3438 Page: Year: 1900; Census Place: Big South Fork, Casey, Kentucky; Roll: T623_514; Page: 9A; Enumeration District: 23. Data: Text: Birth date: Sep 1889 Birth place: Kentucky Residence date: 1900 Residence place: Magisterial District 5, Big South Fork, Casey, Kentucky Note: #N3980 Note: #N3981
↑ Source: #S24 Record ID Number: MH:SC3439 Page: Year: 1900; Census Place: Big South Fork, Casey, Kentucky; Roll: T623_514; Page: 9A; Enumeration District: 23. Data: Text: Birth date: Sep 1889 Birth place: Kentucky Residence date: 1900 Residence place: Magisterial District 5, Big South Fork, Casey, Kentucky Note: #N3976 Note: #N3977
↑ Source: #S24 Record ID Number: MH:SC3440 Page: Year: 1900; Census Place: Big South Fork, Casey, Kentucky; Roll: T623_514; Page: 9A; Enumeration District: 23. Data: Text: Birth date: Sep 1889 Birth place: Kentucky Residence date: 1900 Residence place: Magisterial District 5, Big South Fork, Casey, Kentucky Note: #N3978 Note: #N3979
↑ Source: #S24 Record ID Number: MH:SC3441 Page: Year: 1900; Census Place: Big South Fork, Casey, Kentucky; Roll: T623_514; Page: 9A; Enumeration District: 23. Data: Text: Birth date: Sep 1889 Birth place: Kentucky Residence date: 1900 Residence place: Magisterial District 5, Big South Fork, Casey, Kentucky Note: #N3982 Note: #N3983
Source: S20 Record ID Number: MH:S20 User ID: 53DF068C3FCFB983C001BB9A80A131FC Title: Ancestry Family Trees Publication: Online publication - Provo, UT, USA: Ancestry.com. Original data: Family Tree files submitted by Ancestry members. Repository: #R1 Note: #N7080 Record ID Number: MH:SC3437 Page: Ancestry Family Trees Data: Text: http://trees.ancestry.com/pt/AMTCitationRedir.aspx?tid=5726692&pid=485
Repository: R1 Record ID Number: MH:R1 User ID: 53DF068C3F2139813001BB9A80A131FC Name: Ancestry.com Address: http://www.Ancestry.com Note: #N7060
Note N7060
Record ID Number: MH:N7060
Note N7080This information comes from 1 or more individual Ancestry Family Tree files. This source citation points you to a current version of those files. Note: The owners of these tree files may have removed or changed information since this source citation was created.
Record ID Number: MH:N7080
PRIN MH:S20
Source: S24 Record ID Number: MH:S24 User ID: 53DF068C3FF1D9844001BB9A80A131FC Author: Ancestry.com Title: 1900 United States Federal Census Publication: Online publication - Provo, UT, USA: Ancestry.com Operations Inc, 2004.Original data - United States of America, Bureau of the Census. Twelfth Census of the United States, 1900. Washington, D.C.: National Archives and Records Administration, 1900. T623, 18 Repository: #R1 Note: #N7084
Is Willie your ancestor? Please don't go away! Login to collaborate or comment, or ask our community of genealogists a question.
Sponsored Search by Ancestry.com
DNA Connections
It may be possible to confirm family relationships with Willie by comparing test results with other carriers of his ancestors' Y-chromosome or mitochondrial DNA.
However, there are no known yDNA or mtDNA test-takers in his direct paternal or maternal line.
It is likely that these autosomal DNA test-takers will share some percentage of DNA with Willie: