John R. Long Senior[1][2][3][4][5][6][7][8] was born in 1750[9] in Cecil, Maryland, United States[10] He passed away in 1836 in Ashe, North Carolina, United States[11][12] He was buried in Amelia, Alleghany, North Carolina, United States of America. [13]
DNA
A triangulated group has been discovered that shares John Long and his wife (now confirmed to be a Phipps) as most-recent common ancestors. They share an 8.3 cM segment on chromosome 12.
Update: Further analysis of this Chromosome-12 segment has revealed a VERY strong connection to the Phipps family, indicating that John did indeed marry a Phipps. No documentation has yet been found to confirm her name is "Nellie." Since descendants of both Martha Taylor (John's 2nd child) and Mary Ladreth (John's youngest known child) have the Chr-12 segment, it is believed that the Phipps wife was the mother of all of John's children. Banta-570 01:48, 20 September 2023 (UTC)
Residence
1830
Ashe, North Carolina, USA. [14]
1820
Ashe, North Carolina, United States. [15]
1815
Ashe County, NC. [16]
1810
Lincoln, North Carolina, United States. [17]
1800
Morgan, Ashe, North Carolina. [18]
1790
Wilkes, North Carolina, United States. [19]
Sources
↑ Source: #S203 Page: Database online. Data: Text: Record for Nellie PHIPPS.
↑ Source: #S-158790533 Year: 1810; Census Place: Lincoln, North Carolina; Roll: 40; Page: 416; Image: 00629; Family History Library Film: 0337913
↑ Source: #S-156874759 Year: 1800; Census Place: Morgan, Ashe, North Carolina; Series: M32; Roll: 29; Page: 83; Image: 70; Family History Library Film: 337905
↑ Source: #S-156902218 Year: 1790; Census Place: Wilkes, North Carolina; Series: M637; Roll: 7; Page: 160; Image: 99; Family History Library Film: 0568147
Find a Grave, database and images (www.findagrave.com/memorial/126281290/john-r-long : accessed 20 July 2021), memorial page for John R Long Sr. (1750–Oct 1836), Find a Grave Memorial ID 126281290, citing John Long Sr Family Cemetery, Amelia, Alleghany County, North Carolina, USA ; Maintained by RainbowLady777 (contributor 47433959) Find A Grave: Memorial #126281290.
Source: S203 Author: Ancestry.com Title: Public Member Trees Publication: Name: Name: Ancestry.com Operations, Inc.; Location: Provo, UT, USA; Date:2006;; Repository: #R1.
Repository: R1 Name: www.ancestry.com.
Written Family History.
Personal knowledge of Dreema Ortiz.
Source: S-156874759 Repository: #R-795490851 1800 United States Federal Census Ancestry.com Publication: Ancestry.com Operations Inc.
Repository: R-795490851 Ancestry.com
Source: S-156902218 Repository: #R-795490851 1790 United States Federal Census Ancestry.com Publication: Ancestry.com Operations, Inc.
Source: S-157318030 Repository: #R-795490851 1820 United States Federal Census Ancestry.com Publication: Ancestry.com Operations, Inc.
Source: S-158790533 Repository: #R-795490851 1810 United States Federal Census Ancestry.com Publication: Ancestry.com Operations, Inc.
Source: S-159664103 Repository: #R-795490851 1830 United States Federal Census Ancestry.com Publication: Ancestry.com Operations, Inc.
Source: S-161114731 Repository: #R-795490851 U.S., Find A Grave Index, 1600s-Current Ancestry.com Publication: Ancestry.com Operations, Inc.
Source: S364203464 Repository: #R-795490851 North Carolina, Compiled Census and Census Substitutes Index, 1790-1890 Ancestry.com Publication: Ancestry.com Operations Inc.
Is John your ancestor? Please don't go away! Login to collaborate or comment, or
contact
a profile manager, or ask our community of genealogists a question.
Sponsored Search by Ancestry.com
DNA Connections
It may be possible to confirm family relationships with John by comparing test results with other carriers of his Y-chromosome or his mother's 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 John:
Long-11026 and Long-11931 appear to represent the same person because: These are the same person. Their wives' names are different, so apparently there's an inconsistency there that needs to be explained.