Source: S1 GEDCOM file submitted by John Jasen: gedcom merges from ancestry and myheritage, jjasen/gmail.com. Imported on 28 February 2016. heritage, jjasen/gmail.com. Imported on 28 February 2016. TID 0 Footnote GEDCOM file submitted by John Jasen: gedcom merges from ancestry and myheritage, jjasen/gmail.com. Imported on 28 February 2016. ShortFootnote GEDCOM file submitted by John Jasen: gedcom merges from ancestry and myheritage, jjasen/gmail.com. Imported on 28 February 2016. Bibliography GEDCOM file, John Jasen: gedcom merges from ancestry and myheritage.
Source: S1984 Ancestry Family Trees (Online publication - Provo, UT, USA: Ancestry.com. Original data: Family Tree files submitted by Ancestry members.) m. Original data: Family Tree files submitted by Ancestry members. TID 0 Footnote Ancestry Family Trees (Online publication - Provo, UT, USA: Ancestry.com. Original data: Family Tree files submitted by Ancestry members.) ShortFootnote Ancestry Family Trees Bibliography Ancestry Family Trees. Online publication - Provo, UT, USA: Ancestry.com. Original data: Family Tree files submitted by Ancestry members. Repository: #R1 Ancestry Family Tree Page Ancestry Family Tree http://trees.ancestry.com/pt/AMTCitationRedir.aspx?tid=87558839&pid=95
Is Michael your ancestor? Please don't go away! Login to collaborate or comment, or contact
the 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 Michael 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 Michael: