Ancient Icelandic Viking Settlers Expand the Y DNA Tree

The harsh yet starkly beautiful volcanic island of Iceland was only settled about 1100 years ago, between 870 and 930 CE (current era). Obviously, the original settlers had to originate in locations where populations were already established. During this time, Vikings had been raiding islands and coastal regions of Ireland, Scotland, and England.

Their DNA, now unearthed, tells their tale.

This 2018 paper, Ancient genomes from Iceland reveal the making of a human population by Ebenesersdóttir et al, along with the supplementary material, here, provides insight into the genomes of 27 ancient Icelanders who are a combination of Norse, Gaelic and admixed individuals. The Irish Times wrote a non-academic article, here.

Unequal contributions of the ancient founders, plus isolation resulting in genetic drift separates the current Icelandic population from the founder populations. These ancient Icelandic genomes, autosomally, are more similar to their founding populations than today’s Icelanders.

While autosomal DNA recombines in each generation, Y and mitochondrial DNA does not, revealing the exact DNA of the original founding members of the population. This, of course, allows us to peer back in time. We can see who they match, historically, and where. Today, we can see if our Y and mitochondrial DNA matches them as well.

The authors of the paper selected 35 ancient individuals, believed to be first-generation founders, to have their whole genomes sequenced, of which 27 were successful. Sometimes the ancient DNA is just too degraded to sequence properly.

Nineteen of these burials are pre-Christian, 2 from Christian burials and one that is “Early Modern,” dated to 1678 CE. Ages are expressed, as follows:

  • Pre-Christian <1000 CE
  • Pre-Christian 950-1050 CE
  • Early modern Born 1678 CE
  • Pre-Christian <1050 cal CE

Dates that say “cal CE” mean that they were carbon 14 dated and calibrated and CE (alone) means that those dates are based on the archaeological context of grave goods, other remains, and environmental indicators such as volcanic ash.

As he did with the 442 ancient Viking genomes that I wrote about, here, Goran Runfeldt who heads the research department at FamilyTreeDNA downloaded the Icelandic genomes, extracted and aligned the mitochondrial and Y DNA results.

Michael Sager analyzed the Y DNA and those results, once again, have refined, enhanced or split at least 8 branches of the Y DNA tree.

For instructions about how to see if your mitochondrial or Y DNA results match any of these ancient genomes, please click here. If you haven’t yet tested, you can order or upgrade a Y or mitochondrial DNA test, here.

The Graves

This map, provided in the paper by the authors, shows the burial locations of the remains, noted by sample numbers. Circles are females, squares are male. Light gray was later excluded from the author’s study.

Some of these burials and grave goods are fascinating. For example, note the horse and dog burials.

Goran and Michael have been kind enough to share their analysis, below, along with comments. Thanks, guys!

Sample: DAV-A9
Location: Dalvík (Brimnes), North, Iceland
Study Information: One of the largest and most studied pre-Christian burial sites in Iceland. Thirteen human skeletal remains, six horse skeletons, and the remains of three dogs were found at the site. In one of the graves, the deceased individual had been placed in a sitting position at the rear of a boat
Age: Pre-Christian 900-1000 CE
Y-DNA: I-FGC21765
FTDNA Comment: Likely splits this branch
mtDNA: H1

Sample: DKS-A1
Location: Öndverðarnes, West, Iceland
Study Information: Grave goods included a sword, a spearhead, a knife, a shield-boss, a bone-pin, and fragments of iron. According to a morphological analysis, the skeletal remains show evidence of developmental delay that could be explained by hypogonadism caused by Klinefelter syndrome, testicular disorder or castration.
Age: Pre-Christian 850-1000 CE
Y-DNA: R-YP6099
mtDNA: U5a1h

Sample: FOV-A1
Location: Fossvellir, East, Iceland
Study Information: The remains are thought to have been placed at the site after the individual was deceased. The bones had been carefully arranged on top of each other and were surrounded by stone slabs and turf.
Age: Christian 1246-1302 CE
Y-DNA: R-DF23
mtDNA: HV17a

Sample: GRS-A1
Location: Grímsstaðir, North, Iceland
Study Information: Three pre-Christian burials were found in close proximity to each other near the site of a farmstead. We analysed one of the skeletal remains (GRS-A1), which were excavated in 1937. No grave goods were found at the site.
Age: Pre-Christian <1050 cal CE
Y-DNA: R-BY92608
mtDNA: K1a1b1b

Sample: GTE-A1
Location: Gilsárteigur, East, Iceland
Study Information: In 1949, field-leveling exposed a pre-Christian burial site near an old farm site. The remains of two skeletons were excavated in 1957. Both burials contained grave goods.
Age: Pre-Christian <1000 CE
Y-DNA: R-CTS4179
mtDNA: H4a1a4b

Sample: HSJ-A1
Location: Hrólfsstaðir, East, Iceland
Study Information: A comb, knife, and pieces of charcoal were found in the grave.
Age: Pre-Christian <1000 CE
Y-DNA: I-BY202281
FTDNA Comment: forms a branch with 2 men (Scotland and England). I-BY202281. The two modern samples share an additional 11 markers that HSJ-A1 is ancestral for
mtDNA: H3g1

Sample: KNS-A1
Location: Karlsnes, South, Iceland
Study Information: Grave goods included a spearhead, a knife, two lead weights, three beads, and a small stone.
Age: Pre-Christian 950-1050 CE
Y-DNA: R-Z290
mtDNA: H5

Sample: KOV-A2
Location: Kópavogur, West, Iceland
Study Information: Two skeletal remains. Based on archaeological evidence, the remains were identified as a female, born 1664, and a male, born 1678. According to historical records, they were executed in 1704 for the murder of the female’s husband. The male was beheaded, and his impaled head publicly exhibited, whereas the female was drowned. Their remains were buried in unconsecrated ground at a site called Hjónadysjar.
Age: Early modern Born 1678 CE
Y-DNA: R-L151
mtDNA: H1

Sample: MKR-A1
Location: Viðar (Másvatn), North, Iceland
Study Information: The remains date to <1477 C.E. based on volcanic ash chronology, and are thought to be from a pre-Christian burial site.
Age: Pre-Christian <1050 cal CE
Y-DNA: R-YP1258
mtDNA: K1c1b

Sample: NNM-A1
Location: Njarðvík, East, Iceland
Study Information: A human skull (NNM-A1) was found at a site considered to be a badly damaged pre-Christian burial.
Age: Pre-Christian <1000 CE
Y-DNA: R-BY56981
mtDNA: H2a2b5a

Sample: ORE-A1
Location: Ormsstaðir, East, Iceland
Study Information: Pre-Christian site near an old farmstead was excavated after being exposed during field leveling. One human skeleton (ORE-A) was found, along with an axe, a knife, and three lead weights. A single human bone from another individual was found nearby.
Age: Pre-Christian 900-1000 CE
Y-DNA: R-PH93
mtDNA: K1a3a

Sample: SBT-A1
Location: Smyrlaberg, North, Iceland
Study Information: Pre-Christian burial site in an old gravel quarry. Two years later its excavation revealed a male skeleton (SBT-A1) and an iron knife. Another grave, badly damaged, was found nearby, but only fragments of bone were recovered.
Age: Pre-Christian <1000 CE
Y-DNA: I-FGC74518
FTDNA Comment: Shares 6 SNPs with a man from England. Forms a branch down of I-BY46619 (Z140). Branch = I-FGC74518
mtDNA: H3g1a

Sample: SSG-A2
Location: Sílastaðir, North, Iceland
Study Information: A cluster of four pre-Christian graves. Based on morphological analysis, three of the skeletons were deemed male, and one female.
Age: Pre-Christian 850-1000 CE
Y-DNA: R-BY41282
FTDNA Comment: Split the R-BY23441 block – derived only for BY41282 (Z246)
mtDNA: J1c3g

Sample: SSG-A3
Location: Sílastaðir, North, Iceland
Study Information: A cluster of four pre-Christian graves. Based on morphological analysis, three of the skeletons were deemed male, and one female.
Age: Pre-Christian 850-1000 CE
Y-DNA: I-FGC9493
mtDNA: T2b2b

Sample: SSJ-A2
Location: Surtsstaðir, East, Iceland
Study Information: The remains of two individuals were found at the site, along with grave goods.
Age: Pre-Christian 850-1000 CE
Y-DNA: I-Y129187
mtDNA: U5a1a1

Sample: STT-A2
Location: Straumur, East, Iceland
Study Information: Pre-Christian burial site was excavated, which included the remains of four individuals (one child, one male, one female, and another adult whose sex could not be determined by morphological analysis). Grave goods included a horse bone, a small axe, thirty boat rivets, a lead weight, two pebbles, and a knife.
Age: Pre-Christian 975-1015 cal CE
Y-DNA: R-FT118419
FTDNA Comment: Shares 22 SNPs with a man from Wales. They form the branch R-FT118419 (Z251)
mtDNA: U4b1b1

Sample: SVK-A1
Location: Svínadalur, North, Iceland
Study Information: Human skeletal remains were brought to the National Museum of Iceland. They had been exposed for many years near an old farmhouse. There were no grave goods found at the site, but the remains are thought to be pre-Christian.
Age: Pre-Christian <1050 cal CE
Y-DNA: I-FGC21682
FTDNA Comment: Joins VK110 and VK400 as an additional I-FGC21682* (P109)
mtDNA: I2

Sample: TGS-A1
Location: Tunga, North, Iceland
Study Information: Human skeletal remains (TGS-A1) were excavated in 1981 by inhabitants at a nearby farm. They were classified at the National Museum of Iceland as having unknown temporal origin. The remains were radiocarbon dated for this study, indicating that they date from the 10th century C.E.
Age: Pre-Christian 943-1024 cal CE
Y-DNA: R-Y10827
FTDNA Comment: Likely R-BY4659. Also PH1220+, but this is a C>T mutation also present in hg I ancient samples R7 and Carrowkeel531.
mtDNA: T2e1

Sample: TSK-A26 / ÞSK-A26
Location: Skeljastaðir, South, Iceland
Study Information: Christian cemetery at Skeljastaðir in Þjórsárdalur. The remains are dated to before 1104 C.E., as the site was abandoned in the wake of a volcanic eruption of Mount Hekla in that year.
Age: Christian 1120 cal CE
Y-DNA: R-Y77406
FTDNA Comment: Shares 2 SNPs with a man from Norway. Forms branch down of R-BY30235 (L448). New branch = R-Y77406
mtDNA: J1b1a1a

Sample: VDP-A6
Location: Vatnsdalur, West, Iceland
Study Information: Boat grave with seven skeletal remains (three females and four males), along with a dog skeleton. Grave goods included a knife, thirty beads, a silver Thor’s hammer, a fragmented Cufic coin (ca. 870–930 C.E.) and jewelry.
Age: Pre-Christian 850-1050 CE
Y-DNA: R-YP1120
mtDNA: H1c3a

Sample: VDP-A7
Location: Vatnsdalur, West, Iceland
Study Information: Boat grave with seven skeletal remains (three females and four males), along with a dog skeleton. Grave goods included a knife, thirty beads, a silver Thor’s hammer, a fragmented Cufic coin (ca. 870–930 C.E.) and jewelry.
Age: Pre-Christian 850-1050 CE
Y-DNA: R-FT209682
FTDNA Comment: Shares 7 SNPs with a man from Sweden. Forms branch down of R-BY71305 (Z18). New branch = R-FT209682
mtDNA: H4a1a1

Sample: YGS-B2
Location: Ytra-Garðshor, North, Iceland
Study Information: The site included the disturbed remains of nine human skeletons (four males, two females, one child and two individuals whose sex could not be inferred based on morphological analysis). There were grave goods in all graves.
Age: Pre-Christian <1000 CE
Y-DNA: R-Y98267
FTDNA Comment: Split the R-Y84777 block (L238). Derived only for Y98267
mtDNA: J1c1a

_____________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Products and Services

Genealogy Research

FamilyTreeDNA’s myOrigins Version 3 Rollout

As the fall leaves change colors and people are turning more to inside activities, FamilyTree DNA began rolling out MyOrigins version 3 today.

That’s the good news. The bad news is that everyone is trying to sign on at the same time, so the system is quite slow right now. Maybe that’s actually good news too because it means people are interested AND maybe they will take this opportunity to add trees and link matches if they have not already done so!

What’s Happening?

Yesterday, the following email was sent to group project administrators.

If you’d like to view the list of all populations reported, click here.

The Rollout

I really like the process of prioritizing people who have signed in most recently. They are clearly the most interested in their results.

If you’re wondering if your results have been updated, sign on to your account. Look at your messages to the left of your Autosomal DNA Results.

click to enlarge

If you don’t see this message, then you have the new MyOrigins 3 results, so simply click on MyOrigins.

More Results Coming

Not only are more people going to be receiving results soon, but additional features will be released over time:

  • Population-based chromosome painting, including trace amounts less than 1%. I expect this feature will be released after everyone has received updated results – but that’s my assumption – not from FTDNA.
  • Some people may receive additional population trace amounts not reported in this initial release to facilitate chromosome painting – so check back every couple weeks to see if your results have changed.

My Results

click to enlarge

I have multiple kits at Family Tree DNA – one tested there and one from Ancestry that I use when I write about twins and siblings. Ancestry uses a different chip when processing their DNA tests, and my results at FamilyTreeDNA are somewhat different for the two tests. Keep in mind that the two tests test some of the same locations, but not all.

click to enlarge

I have a 23andMe test I could upload as well. I may do that, simply to compare results, especially since 23andMe also shows my Native segments. Once Family Tree DNA releases their ethnicity chromosome painting, I’ll want to see if the tests report the same locations.

My Comparison

My British Isles are much more specific now. Much of my genealogy from the British Isles is somewhat ambiguous. I know positively that some lines are from there – just not exactly where.

Trace amounts do not contribute to the totals. I wasn’t sure quite how to handle this since we don’t know how much the trace amount actually is – and if it’s noise in some cases.

Here’s the comparison of the four major vendors and their current results, above and below.

I can’t discern the exact amount of Native, although it’s clearly small. I know it’s present and not noise because I’ve proven these segments to the ancestors whose Y and mitochondrial DNA prove their Native origins.

Furthermore, MyOrigins3 essentially matches my Native segments at 23andMe. I know this because I was fortunate enough to have had that sneak peek earlier this year when MyOrigins3 was in beta. You can take a look at Dr. Maier’s presentation about MyOrigins3, here.

Population-based chromosome painting is coming for everyone after the MyOrigins3 rollout is complete. No, I couldn’t pry a more specific date out of anyone😊

How Can Ethnicity Help Your Genealogy?

By clicking on the Shared Origins tab, you can see a list of your matches that have some of the same populations and locations. Of course, this doesn’t mean that your match is because of that population, or within that population, but it does provide you with a place to start – especially if the population is a minority population to you – like my Native American.

I can view the list of my Shared Origins matches, view our matching segments in the chromosome browser to see how we triangulate and share matches with others – hopefully identifying our common ancestor.

In my case, I’ve also painted my known matches at DNAPainter, so most of my segments map to an ancestral line. I compare segment with a specific match to my identified segments at DNAPainter and I’ll probably be able to determine if our matching segment could be assigned that ethnicity by identifying the ancestral line.

Caveats

You all know the caveats I always preach, right?

  • Ethnicity is only an estimate!
  • Just because you don’t show a specific ethnicity doesn’t mean you don’t have that heritage.
  • You don’t inherit exactly half of the DNA of your ancestors. In fact, you may or may not inherit anything measurable from any specific ancestor(s) several generations back in time.
  • Small amounts of ethnicity can be noise.
  • You cannot have an ethnicity that neither of your parents have, although it may be named as something else from the same region. Chromosome painting will help unravel this immensely.
  • Did I mention that ethnicity is only an estimate?

Levity

Now for some much-needed levity

I had forgotten about this, but today, my friend mentioned that this is his favorite ad ever. Yes, an ad. It’s well worth the watch – only a minute or so and I guarantee, it will make you laugh out loud!!!

Go Thor!!!!!!

_____________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Products and Services

Genealogy Research

Ancestry Releases Updated Ethnicity Estimates – Hope You Still Have Your Kilt!

Ancestry has been rolling out their new DNA ethnicity results over the past couple of weeks. By now, pretty much all customers have updated results.

When you sign on and click on your DNA tab, you’ll see a message at the top that tells you whether you have new results or they are coming soon.

I wrote about how ethnicity results are calculated in the article, Ethnicity Testing – A Conundrum. You might want to take a minute and read the article because it applies to methods generally and is not specific to any one vendor.

Ethnicity analysis is quite accurate at the continental level, plus Jewish, but less so within continents like Europe. Your results will vary from vendor to vendor and from update to update with the same vendor over time.

To be very clear, your DNA doesn’t change – and neither does your genealogy, obviously – but the evaluation methods used by various vendors change as more people test, reference populations grow, and the vendors improve their algorithms.

Of course, “improve” is subjective. Changes that “improve” one person’s results have the exact opposite effect on other people.

The Eye of the Beholder

Every time vendors release new population or ethnicity results, everyone runs to check. Then – queue up either “they finally got it right” or teeth gnashing! 😊

Everyone hopes for “better” results – but expectations vary widely and how people determine what “better” means to them is quite subjective.

So yes, the accuracy of the results is truly in the eye of the beholder and often related to how much genealogy they’ve actually done. Surprises in your genealogy can equal surprises in your ethnicity too.

Quantitative Analysis

First, let’s be very clear – you do NOT inherit exactly half of the DNA of each of your distant ancestors in each generation. So you might have NO DNA of an ancestor several generations back in time and multiple segments contributed by another ancestor in the same generation. I wrote about how inheritance actually works in the article, Concepts: Inheritance.

Obviously, if you don’t carry a specific ancestor’s DNA, you also don’t carry any genetic markers for any portion of their ethnic heritage either.

Measuring

The best you can do in terms of ancestral ethnicity percentage expectations is to methodically analyze your tree for the geographic and ethnic heritage of your ancestors.

I explained how I calculated realistic ethnicity estimate percentages in the article, Concepts – Calculating Ethnicity Percentages.

In summary, I made a spreadsheet of my 64 great-great-great-great-great-grandparents, each of which, if the DNA was divided in exactly half and passed to the next generation, would contribute 1.56% of my DNA.

Vendors can typically measure geographically-associated DNA less than 1%. At some point, however, the segments are simply too small to reliably identify and associate with a geographic location or population.

Over time, how different vendors refer to and label different parts of the world both vary and change.

Region Names and Ancestral Assignment

I created a spreadsheet where I track both my “expected” DNA based on my genealogy and the amount of reported DNA from that region by each vendor. As I added vendor results, I sometimes had to add categories since their categories aren’t exactly the same as mine. You’ll observe this in the following sections.

You might notice the “inferred” category. I wrote about this in the Calculating Ethnicity Percentages article, but the inferred locations stem from situations like an unknown wife of a man who is living in England or Germany. We can probably infer that they are from that same country.

In the US, an earlier era spouse’s ethnicity might be inferred from marrying a Scot’s-Irish person, living in a Scots-Irish community or being a member of a Scots-Irish church, for example. Chances are very high that a Scots-Irish man’s wife is also from the “British Isles” someplace.

When creating my spreadsheet, I was intentionally conservative in my genealogical estimates.

Ancestry Update in General

Are there any trends or themes in this most recent Ancestry update? As a matter of fact, yes.

Everybody’s Scottish it seems. I hope you didn’t trade your kilt in for that liederhosen a few years ago, because it looks like you just might need that kilt again.

In fact, Ancestry wrote a blog article about why so many people now have Scotland as an ethnicity location, or have a higher percentage if they already showed Scotland before. I had to laugh, because let me summarize the net-net of the Ancestry article for you, the British Isles is “all mixed up,” meaning highly admixed of course. That’s pretty much the definition of my genealogy!

Another theme is that many testers have Scandinavian origins again.

Back in 2012, Ancestry had a “Scandinavian problem,” and pretty much everyone was Scandinavian in that release, even if they had nary a drop of Scandinavian ancestry. And no, not every person has an unknown paternity event and if they did, the Scandinavians cannot possibly be responsible for all of them. The Viking prowess was remarkable, but not THAT remarkable.

Eight years later, Scandinavian is back.

So, how did Ancestry do on my percentages?

Well, I’m Not Scottish…

In the greatest of ironies, I now show no Scottish at all. My calculations show 5.46%, and it’s probably higher because I descend from Scots-Irish that I can’t place in a location.

I guess I need to turn in my Campbell tartan along with a few others.

I do, however, have Norway back again, but no Scandinavian genealogy.

This chart shows all of the Ancestry updates over time, including this latest, plus a range column for this update.

In addition to the 2020 percentage numbers, I’ve included the ranges shown by Ancestry in the far right column for the 2020 update.

Ranges

When viewing your own results, be sure to click on the right arrow for a population to view the range.

You’ll be able to view the range and additional information.

In this case, Ancestry is confident that I have at least 35% DNA from England & Northwest Europe, and perhaps as much as 41%.

You’ll note that my range for the questionable Scandinavia is 0-5. The only two ethnicities that have ranges that do not include zero are England & Northwestern Europe and Germanic Europe.

My Opinion

I know that I have Native American heritage and that it’s reflected in my ethnicity – or should be.

23andMe results, below, shows me the chromosome locations of Native American segments, and when I track those segments back in time, they track to the ancestors in the Acadian population known to have married Native American partners as reflected in church records. Those ancestors were proven as Native through Y and mitochondrial DNA of their descendants which you can view in the Acadian AmerIndian DNA Project, here.

I wrote about using ethnicity segments identified at 23andMe with DNAPainter to triangulate ancestors in the article, Native American and Minority Ancestors Identified Using DNAPainter Plus Ethnicity Segments.

For me personally, including my Native heritage in my ethnicity results is important. I can’t “do” anything much with that at Ancestry, other than view my match’s shared ethnicity. Since my Native heritage doesn’t show at Ancestry, I can’t use it at all genetically.

Why is this important? Looking at a match on my Acadian line and seeing that we share at least some Native heritage MIGHT, just MIGHT be a hint about a common ancestor. Of course, that’s just a clue, because we might both be native from different sources. If my Native ethnicity is missing at Ancestry, I can’t do that. It’s worth noting that in 2017, Ancestry did report my Native heritage and other vendors do as well.

23andMe provides detailed, downloadable, segment information that translates into useful genealogical information. FamilyTreeDNA has announced that they will be providing ethnicity segment information as well after their new myOrigins release.

The Big 4

How do the Big 4 vendors stack up relative to my genealogy and ethnicity?

And for Native American heritage?

I took the liberty of highlighting which vendor is the closest to my estimated genealogy percentages, but want to remind you that these percentages will only be exactly accurate if the DNA is passed exactly in half in each generation, which doesn’t happen. Therefore, my genealogy is an educated estimate as well. Still, the results shouldn’t be WAY off.

An appropriate sanity check would be that my genealogy analysis and the DNA ethnicity results are relatively close. Many people think they are a lot more of something because those are the family stories they heard – but when they do the analysis, they realize that they might expect a different mixture. For example, my aunt told me that my paternal grandmother’s Appalachian family line was German and Jewish – and they are neither. However, German and Jewish lived in my head for a long time and that was what I initially expected to find.

What’s Next?

Both MyHeritage and Family Tree DNA are slated to release new versions of their population genetics tools – so you’ll be seeing new estimates from both vendors “soon.” Both announced at RootsTech they would deliver new results later in the year, and while I don’t have a release date for either vendor – keep in mind that both FamilyTreeDNA and MyHeritage have brought new labs online from scratch in record time in a humanitarian effort to fight Covid. This critically important work has assuredly interrupted their development schedules. You can read about that here and here.

Kudos to both vendors. Ethnicity can wait.

_____________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Products and Services

Genealogy Research

442 Ancient Viking Skeletons Hold DNA Surprises – Does Your Y or Mitochondrial DNA Match? Daily Updates Here!

Yesterday, in the journal Nature, the article “Population genomics of the Viking world,” was published by Margaryan, et al, a culmination of 6 years of work.

Just hours later, Science Daily published the article, “World’s largest DNA sequencing of Viking skeletons reveals they weren’t all Scandinavian.” Science magazine published “’Viking’ was a job description, not a matter of heredity, massive ancient DNA study shows.” National Geographic wrote here, and CNN here.

Vikings Not All Scandinavian – Or Blonde

Say what??? That’s not at all what we thought we knew. That’s the great thing about science – we’re always learning something new.

442 Viking skeletons from outside Scandinavia were sequenced by Eske Willerslev’s lab, producing whole genome sequences for both men and women from sites in Scotland, Ukraine, Poland, Russia, the Baltic, Iceland, Greenland and elsewhere in continental Europe. They were then compared to known Viking samples from Scandinavia.

Not the grave where the sample was taken, but a Viking cemetery from Denmark.

One Viking boat burial in an Estonian Viking cemetery shows that 4 Viking brothers died and were buried together, ostensibly perishing in the same battle, on the same day. Based on their DNA, the brothers probably came from Sweden.

Vikings raiding parties from Scandinavia originated in Norway, Sweden and Denmark. At least some Viking raiders seem to be closely related to each other, and females in Iceland appear to be from the British Isles, suggesting that they may have “become” Vikings – although we don’t really understand the social and community structure.

Genes found in Vikings were contributed from across Europe, including southern Europe, and as afar away as Asia. Due to mixing resulting from the Viking raids beginning at Lindisfarne in 793 , the UK population today carries as much as 6% Viking DNA. Surprisingly, Swedes had only 10%.

Some Viking burials in both Orkney and Norway were actually genetically Pictish men. Converts, perhaps? One of these burials may actually be the earliest Pict skeleton sequenced to date.

Y DNA

Of the 442 skeletons, about 300 were male. The whole genome sequence includes the Y chromosome along with mitochondrial DNA, although it requires special processing to separate it usefully.

Goran Runfeldt, a member of the Million Mito team and head of research at FamilyTreeDNA began downloading DNA sequences immediately, and Michael Sager began analyzing Y DNA, hoping to add or split Y DNA tree branches.

Given the recent split of haplogroup P and A00, these ancient samples hold HUGE promise.

Michael and Goran have agreed to share their work as they process these samples – providing a rare glimpse real-time into the lab.

You and the Tree

Everyone is so excited about this paper, and I want you to be able to see if your Y or mitochondrial DNA, or that of your relatives matches the DNA haplogroups in the paper.

The paper itself uses the older letter=number designations for Y DNA haplogroup, so FamilyTreeDNA is rerunning, aligning and certifying the actual SNPs. The column FTDNA Haplogroup reflects the SNP Y haplogroup name.

Note that new Y DNA branches appear on the tree the day AFTER the change is made, and right now, changes resulting from this paper are being made hourly. I will update the haplogroup information daily as more becomes available. Pay particular attention to the locations that show where the graves were found along with the FamilyTreeDNA notes.

Goran has also included the mtDNA haplogroup as identified in the paper. Mitochondrial DNA haplogroups have not been recalculated, but you just might see them in the Million Mito Project😊

Here’s what you’ll need to do:

  • Go to your Y or mitochondrial DNA results and find your haplogroup.

  • Do a browser search on this article to see if your haplogroup is shown. On a PC, that’s CTRL+F to show the “find” box. If your haplogroup isn’t showing, you could be downstream of the Viking haplogroup, so you’ll need to use the Y DNA Block Tree (for Big Y testers) or public haplotree, here.
  • If you’ve taken the Big Y test, click on the Block Tree on your results page and then look across the top of your results page to see if the haplogroup in question is “upstream” or a parent of your haplogroup.

click to enlarge

If you don’t see it, keep scanning to the left until you see the last SNP.

click to enlarge

  • If the haplogroup you are seeking is NOT shown in your direct upstream branches, you can type the name of the haplogroup into the search box. For example, I’ve typed I-BY3428. You can also simply click on the FTDNA name haplogroup link in the table, below, considerately provided by Goran.

click to enlarge

I don’t see the intersecting SNP yet, between the tester and the ancient sample, so if I click on I-Y2592, I can view the rest of the upstream branches of haplogroup I.

click to enlarge

By looking at the Y DNA SNPs of the tester, and the Y DNA SNPs of the ancient sample, I can see that the intersecting SNP is DF29, roughly 52 SNP generations in the past. Rule of thumb is that SNP generations are 80-100 years each.

How About You – Are You Related to a Viking?

Below, you’ll find the information from Y DNA results in the paper, reprocessed and analyzed, with FamilyTreeDNA verified SNP names, along with the mitochondrial DNA haplogroup of each Viking male.

Are you related, and if so, how closely?

I was surprised to find a sister-branch to my own mitochondrial J1c2f. J1c2 and several subclades or branches were found in Viking burials.

I need to check all of my ancestral lines, both male and female. There’s history waiting to be revealed. What have you discovered?

Ancient Viking Sample Information

Please note that this information will be updated on business days until all samples have been processed and placed on the Y DNA tree – so this will be a “live” copy of the most current phylogenetic information.

Link to the locations to see the locations of the excavation sites, and the haplogroups for the tree locations. Michael Sager is making comments as he reviews each sample.

Enjoy!

Sample: VK14 / Russia_Ladoga_5680-12
Location: Ladoga, Russia
Age: Viking 10-12th centuries CE
Y-DNA: I-BY3428
mtDNA: J1c1a

Sample: VK16 / Russia_Ladoga_5680-2
Location: Ladoga, Russia
Age: Viking 11-12th centuries CE
Y-DNA: I-M253
mtDNA: X2b4

Sample: VK17 / Russia_Ladoga_5680-17
Location: Ladoga, Russia
Age: Viking 10-12th centuries CE
Y-DNA: T-Y138678
FTDNA Comment: Shares 5 SNPs with a man from Chechen Republic, forming a new branch down of T-Y22559 (T-Y138678)
mtDNA: U5a2a1b

Sample: VK18 / Russia_Ladoga_5680-3
Location: Ladoga, Russia
Age: Viking 10-12th centuries CE
Y-DNA: R-YP1370
mtDNA: H1b1

Sample: VK20 / Russia_Ladoga_5680-1
Location: Ladoga, Russia
Age: Viking 11th century CE
Y-DNA: I-Y22478
FTDNA Comment: Splits the I-Z24071 branch, positive only for Y22478. New path = I-Y22486>I-Y22478>I-Z24071
mtDNA: H6c

Sample: VK22 / Russia_Ladoga_5680-13
Location: Ladoga, Russia
Age: Viking 10-12th centuries CE
Y-DNA: I-A8462
mtDNA: T2b

Sample: VK23 / Russia_Ladoga_5680-9
Location: Ladoga, Russia
Age: Viking 10-12th centuries CE
Y-DNA: I-M253
mtDNA: U4a1a

Sample: VK24 / Faroe_AS34/Panum
Location: Hvalba, Faroes
Age: Viking 11th century
Y-DNA: R-FGC12948
mtDNA: J1b1a1a

Sample: VK25 / Faroe_1
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: R-FT381000
FTDNA Comment: Splits the R-BY11762 branch, positive for 5 variants ancestral for ~14, new path = R-A8041>R-BY11764>BY11762
mtDNA: H3a1a

Sample: VK27 / Faroe_10
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: R-L513
mtDNA: U5a1g1

Sample: VK29 / Sweden_Skara 17
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: I-S7642
mtDNA: T2b3b

Sample: VK30 / Sweden_Skara 105
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-S2857
mtDNA: U5b1c2b

Sample: VK31 / Sweden_Skara 194
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-L21
mtDNA: I4a

Sample: VK34 / Sweden_Skara 135
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-BY111759
mtDNA: HV-T16311C!

Sample: VK35 / Sweden_Skara 118
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-CTS4179
mtDNA: T2f1a1

Sample: VK39 / Sweden_Skara 181
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: G-Z1817
mtDNA: T2b4b

Sample: VK40 / Sweden_Skara 106
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-BY166438
FTDNA Comment: Shares 10 SNPs with a man with unknown origins (American) downstream of R-BY1701. New branch R-BY166438
mtDNA: T1a1

Sample: VK42 / Sweden_Skara 62
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: J-FGC32685
mtDNA: T2b11

Sample: VK44 / Faroe_17
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: R-S658
mtDNA: H3a1a

Sample: VK45 / Faroe_18
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: R-CTS8277
mtDNA: H3a1

Sample: VK46 / Faroe_19
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: R-BY202785
FTDNA Comment: Forms a branch with VK245 down of R-BY202785 (Z287). New branch = R-FT383000
mtDNA: H5

Sample: VK48 / Gotland_Kopparsvik-212/65
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-FGC52679
mtDNA: H10e

Sample: VK50 / Gotland_Kopparsvik-53.64
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: I-Y22923
mtDNA: H1-T16189C!

Sample: VK51 / Gotland_Kopparsvik-88/64
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: N-L1026
mtDNA: U5b1e1

Sample: VK53 / Gotland_Kopparsvik-161/65
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: I-CTS10228
mtDNA: HV9b

Sample: VK57 / Gotland_Frojel-03601
Location: Frojel, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-L151
mtDNA: J1c6

Sample: VK60 / Gotland_Frojel-00702
Location: Frojel, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-YP1026
mtDNA: H13a1a1b

Sample: VK64 / Gotland_Frojel-03504
Location: Frojel, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-BY58559
mtDNA: I1a1

Sample: VK70 / Denmark_Tollemosegard-EW
Location: Tollemosegård, Sealand, Denmark
Age: Early Viking Late Germanic Iron Age/early Viking
Y-DNA: I-BY73576
mtDNA: H7d4

Sample: VK71 / Denmark_Tollemosegard-BU
Location: Tollemosegård, Sealand, Denmark
Age: Early Viking Late Germanic Iron Age/early Viking
Y-DNA: I-S22349
mtDNA: U5a1a

Sample: VK75 / Greenland late-0929
Location: V051, Western Settlement, Greenland
Age: Late Norse 1300 CE
Y-DNA: R-P310
mtDNA: H54

Sample: VK87 / Denmark_Hesselbjerg Grav 41b, sk PC
Location: Hesselbjerg, Jutland, Denmark
Age: Viking 850-900 CE
Y-DNA: R-Z198
mtDNA: K1c2

Sample: VK95 / Iceland_127
Location: Hofstadir, Iceland
Age: Viking 10-13th centuries CE
Y-DNA: R-S658
mtDNA: H6a1a3a

Sample: VK98 / Iceland_083
Location: Hofstadir, Iceland
Age: Viking 10-13th centuries CE
Y-DNA: I-BY3433
FTDNA Comment: Splits I-BY3430. Derived for 1 ancestral for 6. New path = I-BY3433>I-BY3430
mtDNA: T2b3b

Sample: VK101 / Iceland_125
Location: Hofstadir, Iceland
Age: Viking 10-13th centuries CE
Y-DNA: R-BY110718
mtDNA: U5b1g

Sample: VK102 / Iceland_128
Location: Hofstadir, Iceland
Age: Viking 10-13th centuries CE
Y-DNA: R-Y96503
FTDNA Comment: Shares 3 SNPs with a man from Sweden. Forms a new branch downstream of R-FGC23826. New branch = R-Y96503
mtDNA: J1c3f

Sample: VK110 / Iceland_115S
Location: Hofstadir, Iceland
Age: Viking 10-13th centuries CE
Y-DNA: I-FGC21682
mtDNA: H10-x

Sample: VK117 / Norway_Trondheim_SK328
Location: Trondheim, Nor_Mid, Norway
Age: Medieval 12-13th centuries CE
Y-DNA: R-S9257
mtDNA: H1a3a

Sample: VK123 / Iceland_X104
Location: Hofstadir, Iceland
Age: Viking 10-13th centuries CE
Y-DNA: R-Y130994
FTDNA Comment: Shares 17 SNPs with a man from the UAE. Creates a new branch downstream of R2-V1180. New branch = R-Y130994
mtDNA: J1c9

Sample: VK127 / Iceland_HDR08
Location: Hringsdalur, Iceland
Age: Viking 10th century CE
Y-DNA: R-BY92608
mtDNA: H3g1b

Sample: VK129 / Iceland_ING08
Location: Ingiridarstadir, Iceland
Age: Viking 10th century CE
Y-DNA: R-BY154143
FTDNA Comment: Shares 3 SNPs with a man from Sweden. Forms a new branch downstream of R1a-YP275. New branch = R-BY154143
mtDNA: U5b1b1a

Sample: VK133 / Denmark_Galgedil KO
Location: Galgedil, Funen, Denmark
Age: Viking 8-11th centuries CE
Y-DNA: R-Z8
mtDNA: K1a4a1a3

Sample: VK134 / Denmark_Galgedil ALZ
Location: Galgedil, Funen, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: R-BY97519
mtDNA: H1cg

Sample: VK138 / Denmark_Galgedil AQQ
Location: Galgedil, Funen, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: R-S1491
mtDNA: T2b5

Sample: VK139 / Denmark_Galgedil ANG
Location: Galgedil, Funen, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: R-BY32008
mtDNA: J1c3k

Sample: VK140 / Denmark_Galgedil PT
Location: Galgedil, Funen, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: G-M201
mtDNA: H27f

Sample: VK143 / UK_Oxford_#7
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: R-Y13833
FTDNA Comment: Splits R-Y13816. Derived for 6 ancestral for 3. New path = R-Y13816>R-Y13833
mtDNA: U5b1b1-T16192C!

Sample: VK144 / UK_Oxford_#8
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: I-Y2592
mtDNA: V1a1

Sample: VK145 / UK_Oxford_#9
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: R-YP1708
mtDNA: H17

Sample: VK146 / UK_Oxford_#10
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: I-M6155
mtDNA: J1c3e1

Sample: VK147 / UK_Oxford_#11
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: R-Y75899
mtDNA: T1a1q

Sample: VK148 / UK_Oxford_#12
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: I-M253
mtDNA: H6a1a

Sample: VK149 / UK_Oxford_#13
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: I-M253
mtDNA: H1a1

Sample: VK150 / UK_Oxford_#14
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: I-FT4725
mtDNA: H1-C16239T

Sample: VK151 / UK_Oxford_#15
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: I-S19291
mtDNA: T2b4-T152C!

Sample: VK153 / Poland_Bodzia B1
Location: Bodzia, Poland
Age: Viking 10-11th centuries CE
Y-DNA: R-M198
mtDNA: H1c3

Sample: VK156 / Poland_Bodzia B4
Location: Bodzia, Poland
Age: Viking 10-11th centuries CE
Y-DNA: R-Y9081
mtDNA: J1c2c2a

Sample: VK157 / Poland_Bodzia B5
Location: Bodzia, Poland
Age: Viking 10-11th centuries CE
Y-DNA: I-S2077
mtDNA: H1c

Sample: VK159 / Russia_Pskov_7283-20
Location: Pskov, Russia
Age: Viking 10-11th centuries CE
Y-DNA: R-A7982
mtDNA: U2e2a1d

Sample: VK160 / Russia_Kurevanikka_7283-3
Location: Kurevanikha, Russia
Age: Viking 10-13th centuries CE
Y-DNA: R-YP1137
mtDNA: C4a1a-T195C!

Sample: VK163 / UK_Oxford_#1
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: I-M253
mtDNA: U2e2a1a1

Sample: VK165 / UK_Oxford_#3
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: I-S18218
mtDNA: U4b1b1

Sample: VK166 / UK_Oxford_#4
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: R-BY67003
FTDNA Comment: Splits R-BY45170 (DF27). Derived for 2, ancestral for 7. New path = R-BY67003>R-BY45170
mtDNA: H3ag

Sample: VK167 / UK_Oxford_#5
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: I-BY34674
mtDNA: H4a1a4b

Sample: VK168 / UK_Oxford_#6
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: R-Z18
mtDNA: H4a1a4b

Sample: VK170 / Isle-of-Man_Balladoole
Location: Balladoole, IsleOfMan
Age: Viking 9-10th centuries CE
Y-DNA: R-S3201
mtDNA: HV9b

Sample: VK172 / UK_Oxford_#16
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: R-FT7019
mtDNA: I1a1e

Sample: VK173 / UK_Oxford_#17
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: I-FT13004
FTDNA Comment: Splits I2-FT12648, derived for 5, ancestral for 7. New path FT13004>FT12648
mtDNA: U5a1b-T16362C

Sample: VK174 / UK_Oxford_#18
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: R-FGC17429
mtDNA: H1-C16239T

Sample: VK175 / UK_Oxford_#19
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: R-Y47841
FTDNA Comment: Shares 6 SNPs with man from Sweden down of R-BY38950 (R-Y47841)
mtDNA: H1a1

Sample: VK176 / UK_Oxford_#20
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: I-FT3562
mtDNA: H10

Sample: VK177 / UK_Oxford_#21
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: R-FT31867
FTDNA Comment: Shares 3 SNPs with a man from Greece. Forms a new branch downstream of R-BY220332 (U152). New branch = R-FT31867
mtDNA: H82

Sample: VK178 / UK_Oxford_#22
Location: St_John’s_College_Oxford, Oxford, England, UK
Age: Viking 880-1000 CE
Y-DNA: R-BY176639
FTDNA Comment: Links up with PGA3 (Personal Genome Project Austria) and FTDNA customer from Denmark. PGA and FTDNA customer formed a branch earlier this week, VK178 will join them at R-BY176639 (Under L48)
mtDNA: K2a5

Sample: VK179 / Greenland F2
Location: Ø029a, Eastern Settlement, Greenland
Age: Early Norse 10-12th centuries CE
Y-DNA: I-F3312
mtDNA: K1a3a

Sample: VK183 / Greenland F6
Location: Ø029a, Eastern Settlement, Greenland
Age: Early Norse 10-12th centuries CE
Y-DNA: I-F3312
mtDNA: T2b21

Sample: VK184 / Greenland F7
Location: Ø029a, Eastern Settlement, Greenland
Age: Early Norse 10-12th centuries CE
Y-DNA: R-YP4342
mtDNA: H4a1a4b

Sample: VK186 / Greenland KNK-[6]
Location: Ø64, Eastern Settlement, Greenland
Age: Early Norse 10-12th centuries CE
Y-DNA: I-Y79817
FTDNA Comment: Shares 3 SNPs with a man from Norway downstream of I-Y24625. New branch = I-Y79817
mtDNA: H1ao

Sample: VK190 / Greenland late-0996
Location: Ø149, Eastern Settlement, Greenland
Age: Late Norse 1360 CE
Y-DNA: I-FGC15543
FTDNA Comment: Splits I-FGC15561. Derived 11 ancestral for 6. New path = I-FGC15543>I-FGC15561
mtDNA: K1a-T195C!

Sample: VK201 / Orkney_Buckquoy, sk M12
Location: Buckquoy_Birsay, Orkney, Scotland, UK
Age: Viking 5-6th century CE
Y-DNA: I-B293
mtDNA: H3k1a

Sample: VK202 / Orkney_Buckquoy, sk 7B
Location: Buckquoy_Birsay, Orkney, Scotland, UK
Age: Viking 10th century CE
Y-DNA: R-A151
mtDNA: H1ai1

Sample: VK203 / Orkney_BY78, Ar. 1, sk 3
Location: Brough_Road_Birsay, Orkney, Scotland, UK
Age: Viking 10th century CE
Y-DNA: R-BY10450
FTDNA Comment: FT83323-
mtDNA: H4a1a1a1a1

Sample: VK204 / Orkney_Newark for Brothwell
Location: Newark_Deerness, Orkney, Scotland, UK
Age: Viking 10th century CE
Y-DNA: R-BY115469
mtDNA: H1m

Sample: VK205 / Orkney_Newark 68/12
Location: Newark_Deerness, Orkney, Scotland, UK
Age: Viking 10th century CE
Y-DNA: R-YP4345
mtDNA: H3

Sample: VK210 / Poland_Kraków-Zakrzówek gr. 24
Location: Kraków, Poland
Age: Medieval 11-13th centuries CE
Y-DNA: I-Z16971
mtDNA: H5e1a1

Sample: VK211 / Poland_Cedynia gr. 435
Location: Cedynia, Poland
Age: Medieval 11-13 centuries CE
Y-DNA: R-M269
mtDNA: W6

Sample: VK212 / Poland_Cedynia gr. 558
Location: Cedynia, Poland
Age: Viking 11-12th centuries CE
Y-DNA: R-CTS11962
mtDNA: H1-T152C!

Sample: VK215 / Denmark_Gerdrup-B; sk 1
Location: Gerdrup, Sealand, Denmark
Age: Viking 9th century CE
Y-DNA: R-M269
mtDNA: J1c2k

Sample: VK217 / Sweden_Ljungbacka
Location: Ljungbacka, Malmo, Sweden
Age: Viking 9-12th centuries CE
Y-DNA: R-L151
mtDNA: J1b1b1

Sample: VK218 / Russia_Ladoga_5680-4
Location: Ladoga, Russia
Age: Viking 10-12th centuries CE
Y-DNA: R-BY2848
mtDNA: H5

Sample: VK219 / Russia_Ladoga_5680-10
Location: Ladoga, Russia
Age: Viking 10-11th centuries CE
Y-DNA: I-Y22024
mtDNA: T2b6a

Sample: VK220 / Russia_Ladoga_5680-11
Location: Ladoga, Russia
Age: Viking 10-12th centuries CE
Y-DNA: I-FT253975
FTDNA Comment: CTS2208+, BY47171-, CTS7676-, Y20288-, BY69785-, FT253975+
mtDNA: J2b1a

Sample: VK221 / Russia_Ladoga_5757-14
Location: Ladoga, Russia
Age: Viking 9-10th centuries CE
Y-DNA: I-Y5473
mtDNA: K1d

Sample: VK223 / Russia_Gnezdovo 75-140
Location: Gnezdovo, Russia
Age: Viking 10-11th centuries CE
Y-DNA: I-BY67763
mtDNA: H13a1a1c

Sample: VK224 / Russia_Gnezdovo 78-249
Location: Gnezdovo, Russia
Age: Viking 10-11th centuries CE
Y-DNA: N-CTS2929
mtDNA: H7a1

Sample: VK225 / Iceland_A108
Location: Hofstadir, Iceland
Age: Viking 10-13th centuries CE
Y-DNA: R-BY92608
mtDNA: H3v-T16093C

Sample: VK232 / Gotland_Kopparsvik-240.65
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-Y16505
FTDNA Comment: Speculative placement – U106+, but U106 (C>T) in ancient samples can be misleading. LAV010, NA34, I7779, ble007, R55 and EDM124 are all non-R ancient samples that are U106+. More conservative placement is at R-P310
mtDNA: N1a1a1

Sample: VK234 / Faroe_2
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: R-FT381000
FTDNA Comment: Same split as VK25. They share one marker FT381000 (26352237 T>G)
mtDNA: H3a1a

Sample: VK237 / Faroe_15
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: R-S6355
mtDNA: J2a2c

Sample: VK238 / Faroe_4
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: R-YP396
mtDNA: H3a1a

Sample: VK239 / Faroe_5
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: R-M269
mtDNA: H5

Sample: VK242 / Faroe_3
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: R-S764
mtDNA: H3a1a

Sample: VK244 / Faroe_12
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: R-CTS4179
mtDNA: H2a2a2

Sample: VK245 / Faroe_16
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: R-BY202785
FTDNA Comment: Forms a branch with VK46 down of R-BY202785 (Z287). New branch = R-FT383000
mtDNA: H3a1

Sample: VK248 / Faroe_22
Location: Church2, Faroes
Age: Early modern 16-17th centuries CE
Y-DNA: I-M253
mtDNA: H49a

Sample: VK251 / Gotland_Kopparsvik-30.64
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-M459
mtDNA: U5b1e1

Sample: VK256 / UK_Dorset-3722
Location: Ridgeway_Hill_Mass_Grave_Dorset, Dorset, England, UK
Age: Viking 10-11th centuries CE
Y-DNA: R-YP5718
mtDNA: H1c7

Sample: VK257 / UK_Dorset-3723
Location: Ridgeway_Hill_Mass_Grave_Dorset, Dorset, England, UK
Age: Viking 10-11th centuries CE
Y-DNA: I-Y19934
mtDNA: H5a1c1a

Sample: VK258 / UK_Dorset-3733
Location: Ridgeway_Hill_Mass_Grave_Dorset, Dorset, England, UK
Age: Viking 10-11th centuries CE
Y-DNA: R-YP1395
FTDNA Comment: Shares 5 SNPs with a man from Norway. Forms a new branch down of R-YP1395. New branch = R-PH420
mtDNA: K1a4a1

Sample: VK259 / UK_Dorset-3734
Location: Ridgeway_Hill_Mass_Grave_Dorset, Dorset, England, UK
Age: Viking 10-11th centuries CE
Y-DNA: R-FT20255
FTDNA Comment: Both VK449 and VK259 share 3 SNPs with a man from Sweden. Forms a new branch down of R-FT20255 (Z18). New branch = R-FT22694
mtDNA: I2

Sample: VK260 / UK_Dorset-3735
Location: Ridgeway_Hill_Mass_Grave_Dorset, Dorset, England, UK
Age: Viking 10-11th centuries CE
Y-DNA: Q-BY77336
mtDNA: H1e1a

Sample: VK261 / UK_Dorset-3736
Location: Ridgeway_Hill_Mass_Grave_Dorset, Dorset, England, UK
Age: Viking 10-11th centuries CE
Y-DNA: R-BY64643
mtDNA: H52

Sample: VK262 / UK_Dorset-3739
Location: Ridgeway_Hill_Mass_Grave_Dorset, Dorset, England, UK
Age: Viking 10-11th centuries CE
Y-DNA: I-FT347811
FTDNA Comment: Shares 2 SNPs with an American of unknown origins. Forms a new branch down of Y6908 (Z140). At the same time a new branch was discovered that groups this new Ancient/American branch with the established I-FT274828 branch. New ancient path = I-Y6908>I-FT273257>I-FT347811
mtDNA: J1c4

Sample: VK263 / UK_Dorset-3742
Location: Ridgeway_Hill_Mass_Grave_Dorset, Dorset, England, UK
Age: Viking 10-11th centuries CE
Y-DNA: R-Z16372
mtDNA: K1a4d

Sample: VK264 / UK_Dorset-3744
Location: Ridgeway_Hill_Mass_Grave_Dorset, Dorset, England, UK
Age: Viking 10-11th centuries CE
Y-DNA: R-BY30937
mtDNA: N1a1a1a2

Sample: VK267 / Sweden_Karda 21
Location: Karda, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: R-L23
mtDNA: T2b4b

Sample: VK268 / Sweden_Karda 22
Location: Karda, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: R-M269
mtDNA: K1c1

Sample: VK269 / Sweden_Karda 24
Location: Karda, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: R-M269
mtDNA: H1e1a

Sample: VK273 / Russia_Gnezdovo 77-255
Location: Gnezdovo, Russia
Age: Viking 10-11th centuries CE
Y-DNA: R-BY61747
mtDNA: U5a2a1b1

Sample: VK274 / Denmark_Kaargarden 391
Location: Kaagården, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: R-PH3519
mtDNA: T2b-T152C!

Sample: VK275 / Denmark_Kaargarden 217
Location: Kaagården, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: I-BY74743
mtDNA: H

Sample: VK279 / Denmark_Galgedil AXE
Location: Galgedil, Funen, Denmark
Age: Viking 10th century CE
Y-DNA: I-Y10639
mtDNA: I4a

Sample: VK280 / Denmark_Galgedil UO
Location: Galgedil, Funen, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: I-Y3713
mtDNA: H11a

Sample: VK281 / Denmark_Barse Grav A
Location: Bårse, Sealand, Denmark
Age: Viking 10th century CE
Y-DNA: I-FGC22153
FTDNA Comment: Splits I-Y5612 (P109). Derived for 8, ancestral for 2. New path = I-Y5612>I-Y5619
mtDNA: T2

Sample: VK282 / Denmark_Stengade I, LMR c195
Location: Stengade_I, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: R-CTS1211
mtDNA: H4a1a4b

Sample: VK286 / Denmark_Bogovej Grav BJ
Location: Bogøvej, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: R-S10708
mtDNA: J1c-C16261T

Sample: VK287 / Denmark_Kaargarden Grav BS
Location: Kaagården, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: R-S22676
mtDNA: T2b

Sample: VK289 / Denmark_Bodkergarden Grav H, sk 1
Location: Bødkergarden, Langeland, Denmark
Age: Viking 9th century CE
Y-DNA: R-U106
mtDNA: J2b1a

Sample: VK290 / Denmark_Kumle Hoje Grav O
Location: Kumle_høje, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: R-FT264183
FTDNA Comment: Shares at least 4 SNPs with a man from Sweden, forming a new branch downstream R-FT263905 (U106). New branch = R-FT264183. HG02545 remains at R-FT263905
mtDNA: I1a1

Sample: VK291 / Denmark_Bodkergarden Grav D, sk 1
Location: Bødkergarden, Langeland, Denmark
Age: Viking 9th century CE
Y-DNA: I-Y20861
mtDNA: U5a1a2b

Sample: VK292 / Denmark_Bogovej Grav A.D.
Location: Bogøvej, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: R-M417
mtDNA: J1c2c1

Sample: VK295 / Denmark_Hessum sk 1
Location: Hessum, Funen, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: I-Y4738
mtDNA: T1a1

Sample: VK296 / Denmark_Hundstrup Mose sk 1
Location: Hundstrup_Mose, Sealand, Denmark
Age: Early Viking 660-780 CE
Y-DNA: I-S7660
mtDNA: HV6

Sample: VK297 / Denmark_Hundstrup Mose sk 2
Location: Hundstrup_Mose, Sealand, Denmark
Age: Early Viking 670-830 CE
Y-DNA: I-Y4051
mtDNA: J1c2h

Sample: VK301 / Denmark_Ladby Grav 4
Location: Ladby, Funen, Denmark
Age: Viking 640-890 CE
Y-DNA: I-FT105192
mtDNA: R0a2b

Sample: VK306 / Sweden_Skara 33
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: I-FT115400
FTDNA Comment: Shares 3 mutations with a man from Sweden. Forms a new branch down of I-S19291. New branch = I-FT115400. VK151 has no coverage for 2 of these mutations
mtDNA: H15a1

Sample: VK308 / Sweden_Skara 101
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-BY33037
mtDNA: H1c

Sample: VK309 / Sweden_Skara 53
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-YP6189
mtDNA: K1b1c

Sample: VK313 / Denmark_Rantzausminde Grav 2
Location: Rantzausminde, Funen, Denmark
Age: Viking 850-900 CE
Y-DNA: R-JFS0009
mtDNA: H1b

Sample: VK315 / Denmark_Bakkendrup Grav 16
Location: Bakkendrup, Sealand, Denmark
Age: Viking 850-900 CE
Y-DNA: I-Y98280
FTDNA Comment: Shares 1 SNP with a man from the Netherlands. Forms a new branch downstream of I-Y37415 (P109). New branch = I-Y98280
mtDNA: T1a1b

Sample: VK316 / Denmark_Hessum sk II
Location: Hessum, Funen, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: I-Y130659
FTDNA Comment: Splits I-Y130594 (Z59). Derived for 1 ancestral for 6. New path = I-Y130659>I-Y130594>I-Y130747. Ancient sample STR_486 also belongs in this group, at I-Y130747
mtDNA: K1a4

Sample: VK317 / Denmark_Kaargarden Grav BF99
Location: Kaagården, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: J-BY62479
FTDNA Comment: Splits J2-BY62479 (M67). Derived for 9, ancestral for 3. New path = J-BY62479>J-BY72550
mtDNA: H2a2a1

Sample: VK320 / Denmark_Bogovej Grav S
Location: Bogøvej, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: I-Y103013
FTDNA Comment: Shares 3 SNPs with a man from Sweden. Forms a new branch down of I-FT3562 (P109). New branch = I-Y103013
mtDNA: U5a1a1

Sample: VK323 / Denmark_Ribe 2
Location: Ribe, Jutland, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: R-S10185
mtDNA: K2a6

Sample: VK324 / Denmark_Ribe 3
Location: Ribe, Jutland, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: R-BY16590
FTDNA Comment: Splits R-BY16590 (L47). Derived for 7, ancestral for 3. New path = R-S9742>R-BY16950
mtDNA: N1a1a1a2

Sample: VK326 / Denmark_Ribe 5
Location: Ribe, Jutland, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: R-Y52895
mtDNA: U5b1-T16189C!-T16192C!

Sample: VK327 / Denmark_Ribe 6
Location: Ribe, Jutland, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: I-BY463
mtDNA: H6a1a5

Sample: VK329 / Denmark_Ribe 8
Location: Ribe, Jutland, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: R-S18894
mtDNA: H3-T152C!

Sample: VK332 / Oland_1088
Location: Oland, Sweden
Age: Viking 858 ±68 CE
Y-DNA: I-S8522
FTDNA Comment: Possibly falls beneath I-BY195155. Shares one C>T mutation with a BY195155* sample
mtDNA: T2b24

Sample: VK333 / Oland_1028
Location: Oland, Sweden
Age: Viking 885 ± 69 CE
Y-DNA: R-Z29034
mtDNA: H2a2a1

Sample: VK335 / Oland_1068
Location: Oland, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: R-BY39347
FTDNA Comment: Shares 8 SNPs with a man from France. Forms a new branch down of R-BY39347 (U152). New branch = R-FT304388
mtDNA: K1b2a3

Sample: VK336 / Oland_1075
Location: Oland, Sweden
Age: Viking 853 ± 67 CE
Y-DNA: R-BY106906
mtDNA: K2a3a

Sample: VK337 / Oland_1064
Location: Oland, Sweden
Age: Viking 858 ± 68 CE
Y-DNA: I-BY31739
FTDNA Comment: Possible Z140
mtDNA: U5a1b3a

Sample: VK338 / Denmark_Bogovej Grav BV
Location: Bogøvej, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: R-A6707
mtDNA: W3a1

Sample: VK342 / Oland_1016
Location: Oland, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: I-BY78615
FTDNA Comment: Shares 2 SNPs with a man from Finland. Forms a new branch down of I2-Y23710 (L801). New branch = I-BY78615
mtDNA: H2a1

Sample: VK343 / Oland_1021
Location: Oland, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: I-Y7232
mtDNA: H3h

Sample: VK344 / Oland_1030
Location: Oland, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: R-BY32357
mtDNA: J1c2t

Sample: VK345 / Oland_1045
Location: Oland, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: R-FT148754
FTDNA Comment: Splits R-FT148754 (DF63). Derived for 8, ancestral for 6. New path = R-FT148796>R-FT148754
mtDNA: H4a1

Sample: VK346 / Oland_1057
Location: Oland, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: J-Z8424
mtDNA: H2a2b

Sample: VK348 / Oland_1067
Location: Oland, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: I-Z171
mtDNA: T2b28

Sample: VK349 / Oland_1073
Location: Oland, Sweden
Age: Viking 829 ± 57 CE
Y-DNA: R-BY166065
FTDNA Comment: Shares 2 SNPs with a man from England. Forms a branch down of R-BY166065 (L1066). New branch = R-BY167052
mtDNA: H1e2a

Sample: VK352 / Oland_1012
Location: Oland, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: I-FGC35755
FTDNA Comment: Possibly forms a branch down of I-Y15295. 2 possible G>A mutations with a I-Y15295* sample
mtDNA: H64

Sample: VK354 / Oland_1026
Location: Oland, Sweden
Age: Viking 986 ± 38 CE
Y-DNA: R-S6752
mtDNA: H2a1

Sample: VK355 / Oland_1046
Location: Oland, Sweden
Age: Viking 847 ± 65 CE
Y-DNA: L-L595
FTDNA Comment: Joins 2 other ancients on this rare branch. ASH087 and I2923
mtDNA: U5b1b1a

Sample: VK357 / Oland_1097
Location: Oland, Sweden
Age: Viking 1053 ± 60 CE
Y-DNA: I-FT49567
FTDNA Comment: Shares 4 SNPs with a man from England. Forms a new branch down of I-A5952 (Z140). New branch = I-FT49567
mtDNA: J2b1a

Sample: VK362 / Denmark_Bogovej LMR 12077
Location: Bogøvej, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: E-CTS5856
FTDNA Comment: Possibly E-Z16663
mtDNA: V7b

Sample: VK363 / Denmark_Bogovej BT
Location: Bogøvej, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: I-BY198083
FTDNA Comment: Shares 2 SNPs with a man from Switzerland. Forms a new branch down of I-A1472 (Z140). New branch = I-BY198083
mtDNA: U4b1a1a1

Sample: VK365 / Denmark_Bogovej BS
Location: Bogøvej, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: R-BY34800
mtDNA: U8a2

Sample: VK367 / Denmark_Bogovej D
Location: Bogøvej, Langeland, Denmark
Age: Viking 10th century CE
Y-DNA: I-BY67827
FTDNA Comment: VK506 and VK367 split the I-BY67827 branch. Derived for 2 SNPs total. They also share one unique marker (26514336 G>C). New branches = I-Y16449>I-BY72774>I-FT382000
mtDNA: J1b1a1

Sample: VK369 / Denmark_Bakkendrup losfund-2, conc.1
Location: Bakkendrup, Sealand, Denmark
Age: Viking 850-900 CE
Y-DNA: R-FGC7556
FTDNA Comment: Shares 13 SNPs with an American. Forms a new branch down of R-FGC7556 (DF99). New branch = R-FT108043
mtDNA: H1a

Sample: VK373 / Denmark_Galgedil BER
Location: Galgedil, Funen, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: R-L20
mtDNA: J2b1a

Sample: VK379 / Oland_1077
Location: Oland, Sweden
Age: Early Viking 700 CE
Y-DNA: I-FGC22048
mtDNA: U3b1b

Sample: VK380 / Oland_1078
Location: Oland, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: I-Y22923
mtDNA: H27

Sample: VK382 / Oland_1132
Location: Oland, Sweden
Age: Early Viking 700 CE
Y-DNA: I-L813
mtDNA: H3g1

Sample: VK384 / Denmark_Hesselbjerg Grav 14, sk EU
Location: Hesselbjerg, Jutland, Denmark
Age: Viking 850-900 CE
Y-DNA: R-FGC10249
mtDNA: H3g1

Sample: VK386 / Norway_Oppland 5305
Location: Oppland, Nor_South, Norway
Age: Viking 9-11th centuries CE
Y-DNA: R-S695
mtDNA: J1b1a1

Sample: VK388 / Norway_Nordland 253
Location: Nordland, Nor_North, Norway
Age: Viking 8-16th centuries CE
Y-DNA: I-Y22507
FTDNA Comment: Splits I-Y22507. Derived for 1 ancestral for 5. New path = I-Y22504>I-Y22507
mtDNA: J1c5

Sample: VK389 / Norway_Telemark 3697
Location: Telemark, Nor_South, Norway
Age: Viking 10th century CE
Y-DNA: R-Z27210
FTDNA Comment: Splits R-Z27210 (U106). Derived for 1 ancestral for 2. New path = R-Y32857>R-Z27210
mtDNA: T2b

Sample: VK390 / Norway_Telemark 1648-A
Location: Telemark, Nor_South, Norway
Age: Iron Age 5-6th centuries CE
Y-DNA: R-FT7019
mtDNA: K2a3

Sample: VK394 / Norway_Hedmark 4460
Location: Hedmark, Nor_South, Norway
Age: Viking 10th century CE
Y-DNA: R-YP5161
FTDNA Comment: Shares 1 SNP with a man from Denmark. Forms a new branch down of R-YP5161 (L448). New branch = R-BY186623
mtDNA: H13a1a1a

Sample: VK395 / Sweden_Skara 275
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: N-BY21973
mtDNA: X2c1

Sample: VK396 / Sweden_Skara 166
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-BY18970
FTDNA Comment: Splits R-BY18970 (DF98). Derived for 2, ancestral for 4 (BY18964+?). New path = R-BY18973>R-BY18970
mtDNA: J1c2t

Sample: VK397 / Sweden_Skara 237
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-S7759
mtDNA: J1b1a1

Sample: VK398 / Sweden_Skara 231
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: T-BY215080
mtDNA: H1b1-T16362C

Sample: VK399 / Sweden_Skara 276
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: N-FGC14542
mtDNA: H4a1a1a

Sample: VK400 / Sweden_Skara 236
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: I-FGC21682
mtDNA: H1-C16239T

Sample: VK401 / Sweden_Skara 229
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-YP5155
FTDNA Comment: Splits R-YP5155. Derived for 4, ancestral for 1. New path = R-YP5155>R-Y29963
mtDNA: H2a2b

Sample: VK403 / Sweden_Skara 217
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-BY3222
mtDNA: K1a4a1a2b

Sample: VK404 / Sweden_Skara 277
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: I-BY55382
FTDNA Comment: Shares 3 SNPs with a man from Sweden. Forms a new branch down of I-BY55382 (L22). New branch = I-BY108664
mtDNA: U4a2

Sample: VK405 / Sweden_Skara 83
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-L21
mtDNA: K1a10

Sample: VK406 / Sweden_Skara 203
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: N-Y7795
FTDNA Comment: Shares 2 SNPs with a man from Sweden. Forms a new branch down of N-Y7795. New branch = N-FT381631
mtDNA: K1a4a1

Sample: VK407 / Sweden_Skara 274
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: I-Y18232
mtDNA: H1c21

Sample: VK408 / Russia_Ladoga_5757-18
Location: Ladoga, Russia
Age: Viking 10-12th centuries CE
Y-DNA: R-CTS11962
mtDNA: H74

Sample: VK409 / Russia_Ladoga_5680-14
Location: Ladoga, Russia
Age: Viking 10-12th centuries CE
Y-DNA: I-DF29
mtDNA: H3h

Sample: VK410 / Russia_Ladoga_5680-15
Location: Ladoga, Russia
Age: Viking 11-12th centuries CE
Y-DNA: I-M253
mtDNA: X2b-T226C

Sample: VK411 / Denmark_Galgedil TT
Location: Galgedil, Funen, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: R-M269
mtDNA: H1a1

Sample: VK414 / Norway_Oppland 1517
Location: Oppland, Nor_South, Norway
Age: Viking 10-11th centuries CE
Y-DNA: R-PH12
FTDNA Comment: Splits R1a-PH12. Derived for 2, ancestral for 1. New path R-Y66214>R-PH12
mtDNA: H6a1a

Sample: VK418 / Norway_Nordland 1502
Location: Nordland, Nor_North, Norway
Age: Iron Age 4th century CE
Y-DNA: R-CTS5533
mtDNA: J1c2c1

Sample: VK419 / Norway_Nordland 1522
Location: Nordland, Nor_North, Norway
Age: Viking 6-10th centuries CE
Y-DNA: N-S9378
FTDNA Comment: Shares 2 SNPs with a man from France. Forms a new branch down of N-S9378 (L550). New branch = N-BY160234
mtDNA: U5b1b1g1

Sample: VK420 / Norway_Hedmark 2813
Location: Hedmark, Nor_South, Norway
Age: Viking 8-11th centuries CE
Y-DNA: I-FGC15560
FTDNA Comment: Shares 8 SNPs with an American man. Forms a new branch down of I-BY158446. New branch = I-FT118954
mtDNA: I4a

Sample: VK421 / Norway_Oppland 3777
Location: Oppland, Nor_South, Norway
Age: Viking 10-11th centuries CE
Y-DNA: R-M198
mtDNA: U5b2c2b

Sample: VK422 / Norway_Hedmark 4304
Location: Hedmark, Nor_South, Norway
Age: Viking 10th century CE
Y-DNA: R-YP390
mtDNA: J1b1a1a

Sample: VK424 / Sweden_Skara 273
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-M269
mtDNA: K2b1a1

Sample: VK425 / Sweden_Skara 44
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-Z331
mtDNA: U3a1

Sample: VK426 / Sweden_Skara 216
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: R-M269
mtDNA: U6a1a1

Sample: VK427 / Sweden_Skara 209
Location: Varnhem, Skara, Sweden
Age: Viking 10-12th centuries CE
Y-DNA: I-Y5362
mtDNA: K1a4

Sample: VK430 / Gotland_Frojel-00502
Location: Frojel, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: N-S18447
mtDNA: T1a1b

Sample: VK431 / Gotland_Frojel-00487A
Location: Frojel, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-P312
mtDNA: H2a1

Sample: VK438 / Gotland_Frojel-04498
Location: Frojel, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-CTS11962
mtDNA: H1

Sample: VK443 / Oland_1101
Location: Oland, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: I-A20404
mtDNA: U5b2b5

Sample: VK444 / Oland_1059
Location: Oland, Sweden
Age: Viking 847 ± 65 CE
Y-DNA: R-PH1477
mtDNA: K1a

Sample: VK445 / Denmark_Gl Lejre-A1896
Location: Gl._Lejre, Sealand, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: I-Z2040
mtDNA: U3b

Sample: VK446 / Denmark_Galgedil LS
Location: Galgedil, Funen, Denmark
Age: Viking 9-11th centuries CE
Y-DNA: I-BY19383
FTDNA Comment: Shares 1 SNP with a man from England. Forms a new branch down of I-BY19383 (Z2041). New branch = I-BY94803
mtDNA: U5a1a1-T16362C

Sample: VK449 / UK_Dorset-3746
Location: Ridgeway_Hill_Mass_Grave_Dorset, Dorset, England, UK
Age: Viking 10-11th centuries CE
Y-DNA: R-FT20255
FTDNA Comment: Both VK449 and VK259 share 3 SNPs with a man from Sweden. Forms a new branch down of R-FT20255 (Z18). New branch = R-FT22694
mtDNA: H6a2a

Sample: VK452 / Gotland_Kopparsvik-111
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-CTS11962
mtDNA: T2b

Sample: VK453 / Gotland_Kopparsvik-134
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-YP256
mtDNA: H8c

Sample: VK461 / Gotland_Frojel-025A89
Location: Frojel, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: N-Y5005
FTDNA Comment: Possibly down of Y15161. Shares 2 C>T mutations with a Y15161* kit
mtDNA: H7b

Sample: VK463 / Gotland_Frojel-019A89
Location: Frojel, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-Y13467
mtDNA: H1b5

Sample: VK466 / Russia_Gnezdovo 77-222
Location: Gnezdovo, Russia
Age: Viking 10-11th centuries CE
Y-DNA: R-PF6162
mtDNA: H6a1a4

Sample: VK468 / Gotland_Kopparsvik-235
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-BY125166
mtDNA: H1a1

Sample: VK469 / Gotland_Kopparsvik-260
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-FGC17230
mtDNA: H3ac

Sample: VK471 / Gotland_Kopparsvik-63
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-M417
mtDNA: H1m

Sample: VK473 / Gotland_Kopparsvik-126
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: I-S14887
mtDNA: N1a1a1a1

Sample: VK474 / Gotland_Kopparsvik-137
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: E-Y4971
FTDNA Comment: Possible E-Y4972 (Shares 1 G>A mutation with a E-Y4972* sample)
mtDNA: J1d

Sample: VK475 / Gotland_Kopparsvik-187
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: R-BY27605
mtDNA: H1a

Sample: VK479 / Gotland_Kopparsvik-272
Location: Kopparsvik, Gotland, Sweden
Age: Viking 900-1050 CE
Y-DNA: G-Y106451
mtDNA: H1a1

Sample: VK480 / Estonia_Salme_II-E
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: R-YP617
mtDNA: U4a2a1

Sample: VK481 / Estonia_Salme_II-F
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: N-FGC14542
FTDNA Comment: Shares 1 SNP with a man from Sweden. Forms a new branch down of N-FGC14542. New branch = N–BY149019. VK399 possibly groups with these two as well
mtDNA: T2a1a

Sample: VK482 / Estonia_Salme_II-P
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-SK1234
mtDNA: H1a

Sample: VK483 / Estonia_Salme_II-V
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-Y141089
FTDNA Comment: Said to be brother of VK497 at I-BY86407 which is compatible with this placement, although no further Y-SNP evidence exists due to low coverage
mtDNA: H16

Sample: VK484 / Estonia_Salme_II-Q
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: R-FT103482
FTDNA Comment: VK484 and VK486 both split R-FT103482 (Z283). Derived for 9 ancestral for 6. New path = R-FT104609>R-FT103482
mtDNA: H6a1a

Sample: VK485 / Estonia_Salme_II-O
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-BY266
FTDNA Comment: Said to be brother of VK497 at I-BY86407 which is compatible with this placement, although no further Y-SNP evidence exists due to low coverage
mtDNA: H16

Sample: VK486 / Estonia_Salme_II-G
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: R-FT103482
FTDNA Comment: VK484 and VK486 both split R-FT103482 (Z283). Derived for 9 ancestral for 6. New path = R-FT104609>R-FT103482
mtDNA: U4a2a

Sample: VK487 / Estonia_Salme_II-A
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: R-YP4932
FTDNA Comment: Joins ancient Estonian samples V9 and X14
mtDNA: H17a2

Sample: VK488 / Estonia_Salme_II-H
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-L813
mtDNA: H5c

Sample: VK489 / Estonia_Salme_II-Ä
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: N-Y21546
mtDNA: T2e1

Sample: VK490 / Estonia_Salme_II-N
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-FGC8677
FTDNA Comment: Said to be brother of VK497 at I-BY86407 which is compatible with this placement, although no further Y-SNP evidence exists due to low coverage
mtDNA: H16

Sample: VK491 / Estonia_Salme_II-Õ
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-Y141089
mtDNA: H6a1a

Sample: VK492 / Estonia_Salme_II-B
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-Z73
mtDNA: H1b5

Sample: VK493 / Estonia_Salme_II-Š
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: R-S6353
FTDNA Comment: Shares 1 SNP with a man from Finland. Forms a new branch down of R-S6353. New branch = R-BY166432
mtDNA: H2a2a1

Sample: VK494 / Poland_Sandomierz 1/13
Location: Sandomierz, Poland
Age: Viking 10-11th centuries CE
Y-DNA: R-BY25698
mtDNA: X2c2

Sample: VK495 / Estonia_Salme_II-C
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-BY98617
FTDNA Comment: Shares 1 SNP with a man from Romania. Forms a branch down of I-BY98617 (L22). New branch = I-FT373923
mtDNA: H1b

Sample: VK496 / Estonia_Salme_II-W
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-BY198216
mtDNA: H1a

Sample: VK497 / Estonia_Salme_II-Ö
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-BY86407
mtDNA: H16

Sample: VK498 / Estonia_Salme_II-Z
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: R-S6752
mtDNA: H1q

Sample: VK504 / Estonia_Salme_I-1
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: N-S23232
mtDNA: H28a

Sample: VK505 / Estonia_Salme_I-2
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: N-Y30126
mtDNA: J1b1a1b

Sample: VK506 / Estonia_Salme_I-3
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-BY67827
FTDNA Comment: VK506 and VK367 split the I-BY67827 branch. Derived for 2 SNPs total. They also share one unique marker (26514336 G>C). New branches = I-Y16449>I-BY72774>I-FT382000
mtDNA: J1c2

Sample: VK507 / Estonia_Salme_I-4
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-CTS8407
FTDNA Comment: Shares 1 SNP with a man from Denmark. Forms a branch down of I-CTS8407 (P109). New branch = I-BY56459
mtDNA: HV6

Sample: VK508 / Estonia_Salme_I-5
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: N-Y10933
mtDNA: J1c5

Sample: VK509 / Estonia_Salme_I-6
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-Y36105
mtDNA: H1n-T146C!

Sample: VK510 / Estonia_Salme_I-7
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-Y19932
FTDNA Comment: Shares 8 SNPs with a man from Russia. Creates a new branch down of I-Y19932 (L22). New branch = I-BY60851
mtDNA: H10e

Sample: VK511 / Estonia_Salme_II-X
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-Y132154
mtDNA: T2a1a

Sample: VK512 / Estonia_Salme_II-Ü
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: N-Y21546
mtDNA: H2a2b1

Sample: VK513 / Greenland F8
Location: Ø029, East_Settlement, Greenland
Age: Early Norse 10-12th centuries CE
Y-DNA: R-S2886
mtDNA: J1c1b

Sample: VK514 / Norway_Nordland 5195
Location: Nordland, Nor_North, Norway
Age: Viking 6-10th centuries CE
Y-DNA: R-YP4963
mtDNA: K2b1a1

Sample: VK515 / Norway_Nordland 4512
Location: Nordland, Nor_North, Norway
Age: Viking 10th century CE
Y-DNA: I-FGC8677
mtDNA: H52

Sample: VK516 / Norway_Sor-Trondelag 4481
Location: Sor-Trondelag, Nor_Mid, Norway
Age: Viking 10th century CE
Y-DNA: R-CTS8746
mtDNA: H6a1a

Sample: VK517 / Sweden_Uppsala_UM36031_623b
Location: Skämsta, Uppsala, Sweden
Age: Viking 11th century
Y-DNA: I-BY78615
mtDNA: J1c3f

Sample: VK519 / Norway_Nordland 4691b
Location: Nordland, Nor_North, Norway
Age: Viking 6-10th centuries CE
Y-DNA: I-M253
mtDNA: HV0a1

Sample: VK521 / Sol941 Grav900 Brondsager Torsiinre
Location: Brondsager_Torsiinre, Sealand, Denmark
Age: Iron Age 300 CE
Y-DNA: I-FGC43065
mtDNA: H16b

Sample: VK524 / Norway_Nordland 3708
Location: Nordland, Nor_North, Norway
Age: Viking 10th century CE
Y-DNA: I-M6155
mtDNA: HV0a1

Sample: VK528 / Norway_Troms 4049
Location: Troms, Nor_North, Norway
Age: Viking 8-9th centuries CE
Y-DNA: R-BY135243
mtDNA: K1a4a1b

Sample: VK529 / Norway_Nordland 642
Location: Nordland, Nor_North, Norway
Age: Viking 8-9th centuries CE
Y-DNA: I-BY106963
mtDNA: H7

Sample: VK531 / Norway_Troms 5001A
Location: Troms, Nor_North, Norway
Age: LNBA 2400 BC
Y-DNA: R-Y13202
mtDNA: U2e2a

Sample: VK532 / Kragehave Odetofter XL718
Location: Kragehave Odetofter, Sealand, Denmark
Age: Iron Age 100 CE
Y-DNA: I-S26361
FTDNA Comment: Shares 5 SNPs with a man from Sweden. Forms a new branch down of I-S26361 (Z2041). New branch = I-FT273387
mtDNA: U2e2a1a

Sample: VK533 / Oland 1076 28364 35
Location: Oland, Sweden
Age: Viking 9-11th centuries CE
Y-DNA: N-BY21933
FTDNA Comment: Splits N-BY21933 (L550). Derived for 1 ancestral for 13. New path = N-BY29005>N-BY21933
mtDNA: H13a1a1e

Sample: VK534 / Italy_Foggia-869
Location: San_Lorenzo, Foggia, Italy
Age: Medieval 11-13th centuries CE
Y-DNA: R-FGC71023
mtDNA: H1

Sample: VK535 / Italy_Foggia-891
Location: San_Lorenzo, Foggia, Italy
Age: Medieval 12-13th centuries CE
Y-DNA: R-Z2109
mtDNA: T1a5

Sample: VK538 / Italy_Foggia-1249
Location: Cancarro, Foggia, Italy
Age: Medieval 11-13th centuries CE
Y-DNA: L-Z5931
mtDNA: H-C16291T

Sample: VK539 / Ukraine_Shestovitsa-8870-97
Location: Shestovitsa, Ukraine
Age: Viking 10-12th centuries CE
Y-DNA: I-BY61100
FTDNA Comment: Splits I-BY61100 (Z2041). Derived for 5 ancestral for 3. New path I-BY65928>I-BY61100
mtDNA: V

Sample: VK541 / Ukraine_Lutsk
Location: Lutsk, Ukraine
Age: Medieval 13th century
Y-DNA: R-YP593
mtDNA: H7

Sample: VK542 / Ukraine_Chernigov
Location: Chernigov, Ukraine
Age: Viking 11th century
Y-DNA: I-S20602
mtDNA: H5a2a

Sample: VK543 / Ireland_EP55
Location: Eyrephort, Ireland
Age: Viking 9th century CE
Y-DNA: R-S2895
mtDNA: I2

Sample: VK545 / Ireland_SSG12
Location: Ship_Street_Great, Dublin, Ireland
Age: Viking 7-9th centuries CE
Y-DNA: R-DF105
mtDNA: H1bb

Sample: VK546 / Ireland_08E693
Location: Islandbridge, Dublin, Ireland
Age: Viking 9th century CE
Y-DNA: R-L448
mtDNA: HV6

Sample: VK547 / Norway_Nordland 4727
Location: Nordland, Nor_North, Norway
Age: Viking 8-11th centuries CE
Y-DNA: I-FT8660
FTDNA Comment: Splits I-FT8660 (L813) Derived for 3, ancestral for 3. New path = I-FT8660>I-FT8457
mtDNA: V

Sample: VK549 / Estonia_Salme_II-J
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-P109
mtDNA: T2b5a

Sample: VK550 / Estonia_Salme_II-D
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: N-Y4706
mtDNA: V

Sample: VK551 / Estonia_Salme_II-U
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: R-CTS4179
mtDNA: J2a1a1a2

Sample: VK552 / Estonia_Salme_II-K
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-Z2900
mtDNA: H10e

Sample: VK553 / Estonia_Salme_II-M
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-FGC22026
FTDNA Comment: Splits I-FGC22026. Derived for 1, ancestral for 7. New path = I-FGC22035>I-FGC22026
mtDNA: K1c1h

Sample: VK554 / Estonia_Salme_II-L
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-M253
mtDNA: W6a

Sample: VK555 / Estonia_Salme_II-I
Location: Salme, Saaremaa, Estonia
Age: Early Viking 8th century CE
Y-DNA: I-Z73
mtDNA: U3b1b

Sample: VK579 / Oland 1099 1785/67 35
Location: Oland, Sweden
Age: Iron Age 200-400 CE
Y-DNA: N-L550
mtDNA: H1s

Sample: VK582 / SBM1028 ALKEN ENGE 2013, X2244
Location: Alken_Enge, Jutland, Denmark
Age: Iron Age 1st century CE
Y-DNA: I-L801
mtDNA: H6a1b3

Update History:

  • 9-17-2020 – updated 3 times, approximately one-third complete
  • 9-18-2020 – updated in afternoon with another 124 analyzed
  • 9-19-2020 – updated with 142 analyzed
  • 9-21-2020 – updates with 240 analyzed – only 60 to go!
  • 9-22-2020 – last update – A total of 285 entries analyzed and placed on the FTDNA tree where appropriate. 15 were too low quality or low coverage for a reliable haplogroup call, so they were excluded.

____________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Products and Services

Genealogy Research

Y DNA Haplogroup P Gets a Brand-New Root – Plus Some Branches

With almost 35,000 branches comprised of 316,000 SNPs, branches on the Y DNA tree are split every day. In fact, roughly 1000 branches are being added to the Y DNA tree of mankind at Family Tree DNA each month. I wrote about how to navigate their public tree, here, and you can view the tree, here. You can also read about Y DNA terminology, here.

Splitting a deep, very old branch into subclades is unusual – and exciting. Finding a new root, taking the entire haplogroup back another notch in time is even more amazing, especially when that root is 46,000 years old.

Haplogroup P is the parent haplogroup of both Q and R.

This portion of the 2010 haplogroup poster provided to Family Tree DNA conference attendees shows the basic branching structure of haplogroup P, R and Q, with haplogroup P being defined at that time by several equivalent SNPs that had not yet been split into any other subgroups or branches of P. Notice that P295 is shown, but not F115 or PF5850 which would be discovered in years to come.

Haplogroup R, a subclade of P, is the most common haplogroup in Europe, with roughly half of European men falling on some branch of haplogroup R.

Map and haplogroup R distribution courtesy of FamilyTreeDNA

In Ireland, nearly all men fall into a subgroup of haplogroup R.

A lot of progress has been made in the past decade.

This week, FamilyTreeDNA identified a split in haplogroup P, upstream of haplogroups Q and R, establishing a new root above haplogroup P-P295.

The Previous 2020 Tree

This is a 2020 “before” picture of the tree as it pertains to haplogroup P. You can see P-P295 at the top as the root or beginning mutation that defined haplogroup P. That was, of course, before this new discovery.

click to enlarge

At Family Tree DNA, according to this tree where testers self-identify the location of their most distant known patrilineal ancestor, haplogroup P testers are found in multiple Asian locations. Some haplogroup P kits may have only purchased specific SNP tests, not the full Big Y and would actually be placed on downstream branches if they upgraded. Haplogroup P itself is quite rare and generally only found in Siberia, Southeast Asia, and diaspora regions.

Subgroups Q and R are found across Europe and Asia. Additionally, some subgroups of haplogroup Q migrated across the land bridge, Beringia, to populate the Americas.

You might be wondering – if there are only a few people who fall directly into haplogroup P, how was it split?

Great question.

How Was Haplogroup P Split?

Testing of ancient DNA has been a boon to science and genealogy, both, and one of my particular interests.

Recently, Goran Runfeldt who heads the R&D team at FamilyTreeDNA was reading the paper titled Ancient migrations in Southeast Asia and noticed that in the supplementary material, several genomic files from ancient samples were available to download. Of course, that was just the beginning, because the files had to be aligned and processed – then the accuracy verified – requiring input from other team members including Michael Sager who maintains the Y DNA haplotree.

Additionally, the paper’s authors sequenced the whole genomes of two present-day Jehai people from Northern Parak State, West Malaysia, a small group of traditional hunter-gatherers, many of whom still live in isolation. One of those samples was the individual whose Y DNA provided the new root SNP, P-PF5850, that is located above the previous root of haplogroup P, P-P295.

Until this sample was analyzed by Goran, Michael and team, three SNPs, PF5850, P295 and F115, were considered to be equivalent, because no tie-breaker had surfaced to indicate which SNPs occurred in what order. Now we know that PF5850 happened first and is the root of haplogroup P.

I asked Michael Sager, the phylogeneticist at FamilyTreeDNA, better-known as “Mr. Big Y,” due to his many-years-long Godfather relationship with the Y DNA tree, how he knew where to place PF5850, and how it became a new root.

Michael explained that we know that P-PF5850 is the new root because the three SNPs that indicated the previous root, P295, PF5850 and F115 are present in all previous samples, but mutations at both P295 and F115 are absent in the new sample, indicating that PF5850 preceded what is now the old P root.

The two SNPs, P295 and F115 occurred some time later.

This sample also included more than 300 additional unique mutations that may become branches in the future. As more people test and more ancient samples are found and sequenced, there’s lots of potential for further branching. Even with more than 50,000 NGS Big-Y DNA tests in the Family Tree DNA database, there’s still so much we don’t know, yet to be discovered.

Amazingly, mutation P-PF5850 occurred approximately 46,000 years ago meaning that this branch had remained hidden all this time. For all we know, he might be the only man left alive with this particular lineage of mankind, but it’s likely more will surface eventually.

click to enlarge

Michael Sager had previously analyzed samples from The population history of northeastern Siberia since the Pleistocene by Sikora et al. You’ll notice that additional branches of haplogroup P are reflected in ancient samples Yana1 and Yana2 which split P-M45, twice.

Branch Definitions

Today, haplogroup branches are defined by their SNP name, except for base and main branches such as P, P1, P2, etc. Haplogroup P is very old and you’ll find it referred to as simply P, P1 or P2 in most literature, not by SNP name. Goran labeled the old branch names beside the current SNP names, and provided a preliminary longhand letter+number branch name with the * for explanatory purposes.

The problem with the old letter+number system is that when new upstream branches are inserted, the current haplogroup “P” has to shift down and become something else. That’s problematic when reading papers. In order to understand which SNP the paper is actually referencing, you have to know what SNP was labeled as “P” at the time the paper was written.

For example, a new P was just defined, so P becomes P1, but the previous P1 has to become something else, resulting in a domino effect of renaming. While that’s not a significant issue with haplogroup P, because it has seldom changed, it’s a huge challenge with the 17,000+ haplogroup R branches. Hence, the transition several years ago to using SNP names such as P295 instead of the older letter+number designations such as P, which now needs to become something like P1.

Haplogroup Ages

Goran was kind enough to provide additional information as well, including the estimated “Time to Most Recent Common Ancestor,” or TMRCA, a feature currently in development for all haplogroups. You can see that P-PF5850 is estimated to be approximately 46,000 years old, “ca 46 kybp,” meaning “circa 46 thousand years before present.”

The founding ancestor of haplogroup Q lived approximately 31,000 years ago, and ancestral R lived about 28,000 years ago, someplace in Asia. Their common ancestor, P-P226, lived about 33,000 years ago.

How cool is this that you can peer back in time to view these ancient lineages – the story still told in our Y DNA today.

What About You?

If you’re a male, you can upgrade to or purchase a Big Y-700 to participate, here. In addition to discovering where you fall on the tree of mankind, you’ll discover who you match on your direct patrilineal side and where their ancestors are located in the world.

_____________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Products and Services

Genealogy Research

Deleting DNA Results or Closing Your Account Does NOT Automatically = Destroying Your Original DNA Sample

First and foremost, I want to state unequivocally that I am NOT advocating closing your account at any of the testing vendor sites. That’s not the purpose of this article. In fact, I encourage everyone to use each tool to extract every drop of information possible.

The purpose is to educate and inform you that IF you close your account and/or delete your DNA RESULTS from your account, even if the vendor in question says that the action is irreversible and you will need to resubmit a new sample and purchase a new test if you change your mind, that does NOT necessarily mean that your physical DNA sample itself will be destroyed unless you take separate action to request sample destruction. It also does not automatically reverse any previously-granted research permissions.

Many people presume that if they delete their results and/or close their account, that automatically means that their original spit or swab sample is destroyed – and that’s not necessarily true.

First, we need to understand the difference between:

  • A DNA sample
  • A DNA raw data results file, also referred to as a download file
  • DNA matches or a match file

The Difference Between a DNA Sample, Results and Download Files, and Matches

There are three distinct parts of the DNA testing process that people often confuse. It’s important to understand these distinct pieces because you interact with them differently and vendors do as well. In other words, deleting your DNA results file, or closing your account does not necessarily mean that your original sample is destroyed unless you request (and confirm) that separately.

DNA Sample – The DNA sample itself is the swab or vial of spit that you submit to the vendor for processing. That sample is sent to a lab where DNA is extracted and processed on a specific DNA chip that produces a file with roughly 700,000 locations for autosomal tests.

After your DNA results are processed and the vendor knows that they do not need to rerun your sample, how or if your DNA sample is stored, and where, is a function of each specific vendor and their policies.

One vendor, Family Tree DNA archives your DNA sample vials for 25 years as a free benefit so that you (or your heirs should you pass away) can order additional products or upgrades. FamilyTreeDNA offers various levels of Y DNA and mitochondrial DNA testing along with autosomal (Family Finder) results – so there are several upgrade avenues.

This short article, 4 Kinds of DNA for Genetic Genealogy, explains the difference between various kinds of DNA tests.

It’s less obvious why a vendor who does not offer genealogical DNA products other than autosomal testing would retain a customer’s actual DNA sample. The other three vendors, while they don’t currently offer additional genealogy DNA products, do offer health upgrades and purchase options. They may be retaining samples so that their customers could potentially upgrade and they would have a sample on-hand to rerun, if necessary.

Both MyHeritage and 23andMe offer a combined ancestry/genealogy plus health product initially, or customers can purchase the health add-on later. FamilyTreeDNA offers a high-end comprehensive Exome health product for existing customers, the Tovana Genome Report, but it’s a different test altogether and requires a fresh DNA sample.

Furthermore, both Ancestry and 23andMe either conduct health/medical research internally and/or participate in research partnerships with outside entities and may be hoping that their customers will opt-in to research.

Regardless of the underlying reason why, keep in mind that your actual sample is likely being archived someplace, assuming there is any left after processing, unless you request that your sample be destroyed.

Refer to each vendor’s Terms and Conditions, their Privacy Policy along with any other linked documents to gain insight into how each vendor operates. Furthermore, one of those documents will provide instructions for how to request the destruction of your actual DNA sample, should you choose to do so.

All vendors change the contents of their Terms and Conditions along with other legal documents from time to time, so be sure to refer to the current version.

The DNA sample itself is NOT the same thing as the output from the processing, which is the DNA raw data results file.

DNA Raw Data Results File – The DNA results file contains only a small fraction of the three billion locations found in the human genome. Autosomal DNA tests include only about 700,000 (plus or minus) selected locations produced by the chip the vendor is utilizing. The output of the laboratory process is referred to as a raw data file or the DNA results file. People sometimes refer to this as the download file as well, because it’s the file you can download from each vendor.

The results in a raw data file look like this:

When you download and transfer your file from one vendor to another, the raw data file is what you are transferring. You can find instructions for downloading your data file from each vendor, here.

  • The DNA raw data or download file is NOT your actual DNA, which is what is extracted from the liquid in the vial.
  • The raw data or download file is NOT a list of your matches, which may or may not be a separate file available for downloading, depending on the vendor.

The raw data file only contains letters representing your two genotyped nucleotides (T, A, C or G) for the rsid (accession #) for each genetic address or position tested. Each genetic address contains two SNPs, or single nucleotide polymorphisms. You don’t need to understand the details, just that one nucleotide at that address is received from your mother and one from your father.

The example above shows my first 4 locations in my raw data file. You can see that I received an A from both parents at the first two locations, and a G from both parents and the second two locations.

Match File

The values in your DNA results file are compared to other people in the vendor’s database. If enough contiguous locations match, typically more than 500 matching SNPs, plus additional cM (centiMorgan) threshold match criteria, shown below, you are determined to be a match with that other person. You will each be placed on the other person’s match list, and the vendor will then provide additional processing based on the signature features they offer to their clients.

Of the four main vendors, three, Family Tree DNA, MyHeritage and 23andMe allow customers to download a match file in spreadsheet format that provides additional information about each match. Ancestry, unfortunately, does not.

You cannot upload your match file to other vendors – only your raw data file gets uploaded which the vendor then processes in the same way they would if you had tested at their company.

If someone on your match list wants to be included in the database at another vendor, they will either need to test at that vendor or transfer their file to that vendor. Every vendor has people in their database that the other vendors don’t have, so it behooves all genealogists to be in each of the four databases either by testing directly or uploading their raw data files as a transfer.

Of the four main vendors, FamilyTreeDNA and MyHeritage both accept transfers from other vendors and provide free matching, but 23andMe and Ancestry do not. Note that both FamilyTreeDNA and MyHeritage do charge for advanced features, $19 and $29, respectively, but in both cases, it’s significantly less than the cost of a test.

Deleting Results and Closing Accounts

Again, I am NOT advocating that anyone should close accounts at any vendor. In fact, I would discourage DNA deletion. Some people delete their DNA or close their accounts when other options would better serve their purposes. However, if you decide to do so, you need to be aware of the following:

  • If you have a genealogical tree/records research account at Ancestry or MyHeritage, you can delete your DNA results but maintain your genealogy research account, if you desire. You will lose the benefits of having a DNA test at that vendor if you delete your DNA test.
  • At those two vendors, if you delete your DNA, that does not automatically affect the genealogy side of your account except for combined features like ThruLines at Ancestry and Theories of Family Relativity at MyHeritage.
  • If you DOWNLOAD your DNA file, that does NOT delete the file at the original testing vendor unless you do so separately. Downloading only means that you download a copy of the file. Your original raw data results file is still at the vendor, UNLESS YOU CHOOSE TO DELETE YOUR RESULTS. Do not delete your results file unless you want to lose your matches and no longer participate in DNA testing or DNA-related features at that vendor.
  • If you are planning to delete your DNA results at a particular vendor, download a raw data file first, and verify that the file works correctly by uploading the file to one of the vendors that accepts transfers. Save the raw data file permanently on your computer. This preserves at least some of your testing investment and allows you to utilize your DNA results file elsewhere.
  • If you delete your DNA results at any of the major vendors, you cannot restore the results file at that vendor without repurchasing and resubmitting a new DNA test. For vendors who accept transfers, you could potentially re-upload your file as a transfer, but you would need to pay for advanced features.
  • If you delete your DNA results at vendors who do NOT offer additional genealogical research services, meaning at 23andMe and Family Tree DNA, there is no reason to maintain an account at that vendor.

If you delete your results or close your account at any vendor, it DOES mean that:

  • The DNA result you’ve deleted along with corresponding matches and other features are permanently gone. You cannot change your mind. Delete=permanent.
  • At FamilyTreeDNA, you can delete one kind of DNA test without deleting all types of DNA tests for a particular individual. For example, you could delete a Y DNA result but not delete mitochondrial or the autosomal Family Finder test.
  • You will have to pay to retest should you change your mind.

If you delete your results or close the DNA portion of your account, it DOES NOT necessarily mean that:

  • Your DNA sample is destroyed.
  • You’ve revoked any permissions previously given for participation in research.

You will need to perform both of these tasks separately and independently of deleting your DNA file at a vendor and/or closing your account.

Every Vendor is Different

The process of requesting sample destruction and revoking research permissions is different at each vendor, with or without closing your account.

Every vendor’s terms and conditions are separate and different. Some vendors may automatically close your account if you request sample destruction, and others won’t. Some may automatically delete your sample if you close your account, but I know for certain that’s not uniformly true.

Terms and conditions, as well as standard procedures, change over time as well.

I’m not telling you which vendors operate in which ways, because this article will someday be dated and vendor policies change. I don’t want to take the chance of leading someone astray in the future.

Therefore, if you wish to have your sample destroyed and/or revoke any research permissions previously granted, I strongly suggest that you call the vendor’s customer support and convey specifically what you want, and why. The vendor may offer alternatives to achieve what you desire without deleting your sample and account.

To delete your sample and/or account, you may need to provide your request in writing.

Request verification in writing that your sample has been destroyed and that any previously granted research authority/permission has been rescinded.

Research Permission

Please note that you can rescind previously granted research permission WITHOUT affecting your account in any other way. However, the reverse is not true – deleting your sample and closing your account does not automatically rescind previously-granted research permission.

You can only rescind permission for future research, not research already underway or completed that includes your DNA and corresponding answers to research questions.

Extra Steps

I hope you will continue to enjoy the results of your DNA tests for years to come. New features and benefits are added regularly, as are new matches – any one of which has the potential to break down that pesky brick wall. Equally as important, at least to me, is the legacy I’m leaving with my combined tree, DNA, and research work for future generations.

However, what’s right for me may not be right for you. If you make a different decision, be sure that you fully understand the different parts of DNA testing along with the various options and steps you may need to take to achieve your goal.

_____________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Products and Services

Genealogy Research

23andMe Genetic Tree Provides Critical Clue to Solve 137-Year-Old Disappearance Mystery

DNA can convey messages from the great beyond – from times past and people that died long before we were born.

I had the most surprising experience this week. It began with receiving an email with the sender name of my long-time research buddy, cousin Garmon Estes.

It’s all the more surprising because not only did Garmon never own a computer, despite my ceaseless encouragement, he passed over in 2013 at the age of 85. So, imagine my shock to open my email to see a message from Garmon. Queue up spooky music😊

As it turned out, Garmon’s nephew is also Garmon. I had communicated with the family off and on over the years since the death of Garmon the elder. Garmon, the younger, had written to tell me that the second “great brick wall” that haunted his Uncle Garmon had fallen – and how that happened, thanks to DNA.

Garmon, the Elder

Estes Garmon

Garmon Estes, the elder

I first met Garmon the elder, via letter, back in the 1970s or maybe early 80s. He was an experienced genealogist and I was beginning.

At that time, Garmon had been chasing the identity of the father of our common ancestor, John R. Estes, for decades, and I was just embarking on what would become a lifelong adventure, or perhaps it could better be called an obsession.

John R. Estes had moved from some unknown location to Claiborne County, Tennessee with his wife and family about 1820. That’s pretty much all we knew at that time. Garmon had spent decades before the age of online records researching every John Estes he could find. I can’t even begin to tell you how many John Esteses existed that needed to be eliminated as candidates.

Garmon lived in California, far from Tennessee. I lived in Indiana, then Michigan – significantly closer. He began caring for his ill spouse, and I began traveling to dusty courthouses, sometimes reading musty books page by yellowed page, extracting everything Estes. Garmon worked from his local Family History Center when he could and wrote letters.

Between our joint sleuthing and many theories that we both composed and subsequently shot down, we narrowed John R. Estes’s location of origin to Halifax County, Virginia. However, there were multiple John Esteses living there at the same time, about the same age, none using middle initials reliably, and some not at all. How inconsiderate!

I began perusing every possible record. I had eliminated some Johns as candidates, most often because they clearly remained in the community after our John had moved to Claiborne County. Late one night, in our local family history center, I found that fateful clue – John R. Estes noted as (S.G.) short for “son of George,” on just one tax list. All it takes is that one gold-nugget record.

It was after 10 PM when I left the Family History Center and even later when I got home. I debated whether I should call Garmon or not, but I decided that indeed, he would want to know immediately, even if I did call at an inconvenient time or wake him up.

The discovery of John’s father, of course, opened the door for much more research, and it solved one of Garmon’s two brick walls that had haunted his genealogy life.

He never solved the second one, but it wasn’t for lack of trying.

What Happened to Willis Alexander Garmon Estes?

Willis Alexander Garmon Estes was born on December 21, 1854, in Lenoir, Roane County, TN. His nickname was Willie.

Willie married Martha Lee Mathis in 1874 and they had 4 children beginning with the first child born the next year in Roane County. Sometime between 1875 and the birth of the second child in 1877, they migrated to Greenwood, Wise County, Texas where their next two children were born in 1877 and 1881.

Martha was pregnant for their fourth child in 1883 when something very strange happened. Willie disappeared, and I do mean literally and completely. Just poof, gone.

Not sure what to do, Martha’s father, who lived in Missouri, went to Texas to retrieve his pregnant daughter and her children and took her and the children home to Missouri where their last child was born that September.

Willie was only 28 when he vanished. The family, of course, had many stories about what happened. Texas at that time was pretty much the “wild west” and the stories about Willie reflected exactly that.

Texas was sometimes the refuge of outlaws and shady characters. One story revealed that Willie had shot a man back in Tennessee and the family fled to Louisiana, then Texas. Of course, that doesn’t tell us why he disappeared in Texas, but it opens the door to speculation and casts doubt on his character, perhaps.

Another story was that he was shot by Indians.

A third story stated that Willie settled in Indian Territory north of the Red River, now Oklahoma, and that he had an altercation with an Indian over the supposed theft of firewood, although who was accusing who was unclear. Willie shot the Indian, then had to flee for his life, leaving his pregnant wife and children as a posse of Indian Police surrounded his house. Willie supposedly promised Martha that he would return, but never did. It was reported that he was shot in Mexico, but no further details emerged.

Aren’t these just maddeningly vague???

Yet another story was that Willie headed for the goldfields of California, struck it rich, and was murdered on the way back home. The details varied, but one version had him murdered by a traveling companion on the trail. Another had him becoming ill and dying in a hospital in St. Louis where his wife went to search for him, to no avail. That might explain why she went back to Missouri, Garmon postulated. And yet a third version was some hybrid of the two where “someone” tried to find Willie’s family for years to reveal what had happened, and where, but was never successful. Of course, how did the family know about this if the mystery person was unable to find the family? But I digress.

Garmon desperately wanted to solve that mystery. He wanted closure.

I didn’t realize that the genealogy bug had bitten Garmon’s nephew too, but it clearly has. Garmon would be so proud.

With Garmon the younger’s permission, I’m publishing “the rest of the story,” Connecting the Dots, as written by Garmon the younger, with a few technical interjections from me involving DNA from time to time.

Connecting the Dots

In 2015, My dad Richard Estes, my brother Corey Estes, and I took a trip to Texas and Oklahoma to see if we could find out more about Willis Alexander Garmon Estes’ disappearance.

Estes greenwood

We visited Greenwood, Texas and nearby Decatur where we looked at historical records at the Wise County Clerk Office. We also went up to Oklahoma City to see the state archives and to Tishomingo to look at any records that might be available.

Estes Oklahoma history.png

Interestingly enough, we did not find any clues as to the disappearance of Willis Alexander Garmon Estes. There were no newspaper articles or criminal records concerning any incidents with Willis Alexander Garmon Estes. The only new information that we found was a couple of land deeds showing that Willis Alexander Garmon Estes’ brother Fielding had bought and sold land in Wise County during the time that Willis Alexander Garmon Estes was living in Greenwood.

We left empty-handed on our trip but our curiosity remained strong and we began talking to each other about going on another trip to Tennessee to speak with Estes family members in Loudon County to see if they might know something about Willis Alexander Garmon’s disappearance.

DNA Testing

In December of 2018, my wife, children, and I had our DNA tested using the service 23andMe. We received test results within a month of sending in saliva samples. The results did not reveal anything unusual.

Fast forward to October 2019. 23andMe introduced a new Family Tree feature that automatically creates a family tree based on the DNA results that you share with relatives in 23andMe. This was a fascinating feature and I noticed that all of my family members were automatically placed into the correct position on the family tree without me having to do anything.

[Roberta’s note – this is not always the case, so don’t necessarily expect the same level of accuracy. The tree is a wonderful innovative feature, just treat family placement as hints and not facts.]

Every few weeks as more and more people had their DNA tested on 23andMe, new relatives were added to the family tree.

In February 2020, I noticed something interesting under the location of Willis Alexander Garmon Estes on the family tree. A woman by the name of Edna appeared as a descendent of Willis Alexander Garmon Estes. The first thing I did was to try and get in contact with her on 23andMe. No luck. Next, I thought maybe she was the descendent of one of Willis Alexander Garmon’s sons (James, John, or George). However, after researching the descendants of each of those lines, Edna’s name did not appear.

The next step I took was to look up as many Ednas by that last name on ancestry.com as I could find and trace their ancestry back to see where it led.

There were two Ednas by that last name in the United States whose age matched the one on 23andMe. I traced both of their ancestry lines back to the 1800’s. Neither one had Willis Alexander Garmon Estes as an ancestor.

Breakthrough

During the middle of March 2020, when I was quarantined at home from work due to the COVID-19 virus, I took another look at Edna’s family lines. I noticed there was a gentleman by the name of James Henry Houston mentioned as an ancestor.

The interesting thing about James was that he was born on the same day, same year, and in the same county as Willis Alexander Garmon Estes. James Henry Houston was born on December 26, 1854 in Loudon County, Tennessee. This seemed like possibly more than a coincidence, so I dived into the data a little bit more.

I looked at federal census records to find out more about James Henry Houston’s past. Strangely there were no official records of him until May 12, 1889 when he married Allie Ona Taylor in Erath, Texas. Normally, if someone is born in 1854, they would show up in one of the federal census records of 1860, 1870, or 1880. James Henry Houston does not show up in any official federal census records until 1900.

According to ancestry records, James Henry Houston married Allie Ona Taylor in 1889 and resided in the Hood County region of Texas until 1910. During this time, he raised 8 children with his wife Allie.

In 1920, the federal census placed him and Allie in Whitehall, Montana. The last federal census he appears in is 1930. He lived in Pomona, California where he died in 1933 at the age of 78.

At this point, I thought it was highly likely that James Henry Houston and Willis Alexander Garmon Estes were the same person. If my hunch was correct then a photo of James Henry Houston would most likely show a resemblance to his son, my great grandfather John Alexander Estes.

Estes James Henry Houston

The photos above show a remarkable similarity in the eyes, nose, mouth, and facial structure between the two men. To me, the photo and historical evidence is enough to conclude that Willis Alexander Garmon Estes is James Henry Houston.

Garmon’s Concluding Thoughts

As I reflect on the fact that Willis Alexander Garmon Estes renamed himself James Henry Houston and moved from Wise County down to Hood County, Texas – approximately 60 miles distance to marry and raise a new family, many more questions come to mind.

What exactly happened to cause Willis Alexander Garmon Estes to leave his wife and children behind? Was it simply a marital dispute or did it involve a criminal offense and running from the law as was mentioned in the family lore?

Did my great grandfather know that his father lived in Pomona in 1930, which was only 6 miles away from where he was living in Rancho Cucamonga? Were there other family members that knew what happened but promised not to tell anyone else? We may never know.

Finally, I want to add one more piece to the story that I found fascinating. On ancestry.com, many of the family trees for James Henry Houston state that the mother and father of James Henry Houston was Jennie Bray and Henry Houston. No information is given for their birthdates or where they came from. The mother and father of Willis Alexander Garmon Estes was Jennie McVey and William Estes. The names Jennie Bray and Jennie McVey are very similar. In order to hide his true identity, James Henry Houston would have to make up a surname for his father since he called himself Houston, not Estes. Willis Alexander Garmon Estes had a brother named John Houston Estes. This might explain why James Henry Houston chose to use the surname Houston rather than another name.

Congratulations Garmon

I know this made Garmon the elder puff up with pride for Garmon the younger’s sleuthing skills and leap for joy at the solve. Garmon, the elder, had two main genealogy goals throughout his entire life. One was solved while he was living, but it took another generation to solve this one.

Great job, Garmon!

About the 23andMe Genetic Tree

23andMe is the only vendor to construct a “trial balloon” genetic tree based only on how the tester matches people and how they do, or don’t, match each other. This occurs with no input from testers in the form of genealogical trees of identifying how people are related to the tester.

Family Tree DNA has Phased Family Matching, MyHeritage has Theories of Family Relativity, and Ancestry has ThruLines which all do some sort of DNA+tree+relationship connectivity, but since 23andMe does not support user-created or uploaded trees, anything they produce has to be using DNA alone.

On one hand, it’s frustrating for genealogists, but on the other hand, there is sometimes a benefit to a different “all genetic” approach.

Of course, the only information that 23andMe has to utilize unless your parents have tested is how closely you match your matches and how closely your matches match each other. This allows 23andMe to place your matches at least in a “neighborhood” on your tree, at least approximately accurate, unless your parents are related to each other and that shared DNA causes things to get dicey quickly.

I wrote about 23andMe’s new relationship triangulation tree when it was first introduced in September 2019, nearly a year ago, here. The launch was rocky for a number of reasons, and if you’ve done genealogy for a long time, your research goals are likely to be further back in time than this 4 generation relationship tree will reveal.

23andMe tree

Click to enlarge

This is what my relationship tree looked like at the time the function was launched. You’ll note that 23andMe places relationships back in time 4 generations, to your great-great-grandparents, meaning that you might have 3rd or even 4th cousins showing up on your genetic tree.

I initially had a total of 18 people placed on my tree, with 3 being close family, 4 being accurate, 4 unknown, 1 uncertain and 6, or one third, inaccurate.

Keep in mind that 23andMe doesn’t make any provision to accommodate or take into account half-relationships, like half-brother or half-sister, either currently or historically. Therefore, descendant placement predictions can be “off” because half-siblings only carry the DNA from one common parent, instead of two, making those relationships appear more distant than they really are.

In Garmon’s case, his great-great-grandfather is the ancestor who was MIA, so the genetic tree has the potential to work well for this purpose.

Estes 23andme tree today

click to enlarge

Today, my tree looks somewhat different, with only 14 people displayed instead of 18, and 6 waiting in the wings to see if I can help 23andMe figure out how and where to place them.

Since the initial launch, customers have been given the opportunity to add their ancestors’ names to their nodes. This works just fine so long as nobody married more than once and had children from both marriages.

Estes Willie Alexander today

click to enlarge

 

Here’s a closer image of the left-hand side of my tree where I’ve super-imposed the location of Willis Alexander Garmon Estes and Edna, as they are related to Garmon the Younger, at bottom right. Ignore the other names – I only utilized my own tree for an example tree structure.

One more generation and it’s unlikely that 23andMe would have made the connection between Edna and Garmon the younger.

Not only does this illustrate the perfect reason to test the oldest generations in your family, but also never to ignore an unknown match that seems to be within the past 3 or 4 generations. You never know what mysteries you might unravel.

Four generations actually reaches back in time quite substantially. In my case, my great-great-grandparents were born in 1805, 1810, 1812, 1813, 1815, 1816, 1818 (2), 1820, 1822, 1827, 1829, 1830, 1832, 1841 and 1848.

If you have mysteries within your closest 4 generations to unravel, the genetic tree at 23andMe might provide valuable clues, but only if you’re willing to do the requisite work to figure out HOW these people match you.

You can’t transfer your DNA file TO 23andMe, so if you want to have your results in the 23andMe database, you’ll need to test there.

Acknowledgments: Thank you to Garmon Estes, the younger, for generously sharing this story and allowing publication. My heart was warmed to see your generational research trip.

Thank you to Garmon Estes, the elder, for being my research partner for so many years. You can finally RIP now, although somehow I suspect you already have these answers.

_____________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Products and Services

Genealogy Research

Search Techniques for Y and Mitochondrial DNA Test Candidates

I utilize DNA matches in various ways, some of which are a little unusual. In many cases, I mine autosomal DNA matches to search for people whose Y and mitochondrial DNA can provide descendants, including me and them, with additional insights into our common ancestors.

Y and mitochondrial DNA connects testers to their ancestors in ways that autosomal cannot. It’s a different type of DNA, not combined with the DNA of the other parent, so it’s not diluted and halved in each generation like autosomal DNA. Y and mitochondrial lines each descend from only one ancestral line, rich in historical information, with the ability to reach far back in time along with the ability to connect testers recently.

You First

The very first thing you can do to further your own research is to test yourself in three ways:

  • Autosomal DNA – Test at all 4 primary testing vendors, meaning FamilyTreeDNA, MyHeritage, Ancestry and 23andMe. The reason for testing at (or transferring to) multiple vendors is because they each have a unique focus and tools. Perhaps more importantly, they each have different people in their databases. Each testing company has benefits. FamilyTreeDNA has people who tested as long as 20 years ago and are no longer available for testing. MyHeritage has many European testers and you’ll find matches there that you won’t find elsewhere if your ancestors came from Europe. Ancestry has the largest database, but fewer advanced tools.
  • Full Sequence Mitochondrial DNA Available at FamilyTreeDNA, this test allows focus solely on your matrilineal line, meaning your mother’s mother’s mother’s line directly without confusion introduced by DNA from other lines.
  • Y DNA – For males only, also available at FamilyTreeDNA, provides focus on the direct patrilineal, or surname, line.

Obviously, if you haven’t upgraded your own Y and mitochondrial DNA tests to the highest level possible, the first thing you can do is to test or upgrade to the highest level where you receive the most refined amount of information.

(There’s a sale at FamilyTreeDNA right now, lasting until August 31, 2020, so it’s a great time to upgrade or order Y and mitochondrial. Check it out here.)

Different Kinds of DNA Serve Different Genealogical Purposes

Let’s look, briefly at how the various types of DNA tests benefit genealogy. Autosomal tests that you and family members can take will help you find other family members to test for specific Y and mitochondrial DNA lines.

Remember that you can test family members in addition to yourself, so if you’re a female, you may want to recruit your father or an uncle or brother to represent your patrilineal line DNA. If you’d like to read a brief article about the different types of DNA and their benefits, 4 Kinds of DNA for Genetic Genealogy is a good resource.

Y and Mito Pedigree.png

In this image, you can see that if you’re a male you can test for both your Y (blue-square) and mitochondrial DNA (red-circle) ancestral lines. If you’re a female, you can test only your mitochondrial DNA because females don’t have a Y chromosome. Both males and females, of course, can test (green) autosomal DNA which reveals a different type of connection to all of your ancestral lines, but with autosomal, you have to figure out which people match you on which lines.

Y and mitochondrial DNA provides you with a different type of information about laser-focused specific lines that you can’t obtain through autosomal testing, and reaches back in time far beyond the curtain when surnames were adopted.

personal pedigree

You personally can only test for the red-circle mitochondrial DNA line, and perhaps the blue-square Y DNA line if you’re a male. Unless you find family members to test for the Y and mitochondrial DNA of your ancestors, you’re leaving valuable information unresearched. That means all those colored boxes and squares that aren’t blue or red.

I’ve solved MANY brick walls using both Y and mitochondrial DNA, often in conjunction with autosomal.

Let’s take a look at each type of DNA testing a little more in-depth, so that you understand how each one works and why they are important to genealogy.

The Specifics

Y DNA – Y DNA descends through the direct male paternal line and is inherited by men only. You match against other Y DNA testers, hopefully finding surname links.

The Big Y test and upgrade at FamilyTreeDNA provides testers with all 111 traditional STR markers, plus another 589+ STRs available only in the Big Y test, plus a scan of the balance of the rest of the Y chromosome that is useful for genealogy. SNP results are increasingly being used for genealogy, in addition to STRs.

SNPs group men into genetic lineages and STRs help with defining and refining the closest generations when matching to each other. Often, the benefits of these two tests overlap, which is why I recommend that males test to the Big Y-700 level which provides 700+ STR markers plus all SNPs with mutations that define ancestral lineages.

Y DNA haplogroups, derived from SNPs, reveal the geographic part of the world where the lineage originated, such as Europe, the Americas, Asia and Africa, as well as a migration path across the continents based on where SNPs are and were historically found. Ancient DNA samples are being added to the database.

If you or a family member took an earlier Y DNA test, you can upgrade to the Big Y-700 today which provides you with matching for both the STR markers and separately, SNP markers, along with other genealogical tools.

You can order or upgrade your Y DNA here. Don’t forget family members accounts you may control. They may agree to have their kit upgraded too.

To upgrade, sign in to your account, and click on your desired upgrade level under Y DNA testing.

ymt y upgrade.png

Then click on upgrades.

ymt upgrade.png

I wrote about Y DNA in these recent articles:

I have more Y DNA articles planned for the future.

You can search for additional articles by going to the main page of this blog and enter “Y DNA” into the search box for additional articles already published.

Many features such as the matches maps, haplogroup origins and ancestral origins pages are the same for Y DNA results as mitochondrial DNA results. You can view mitochondrial articles here.

Mitochondrial DNA (mtDNA) – Mitochondrail DNA descends through the direct matrilineal line to both sexes of children. Everyone has mitochondrial DNA and it is inherited matrilineally by you from your mother, from her mother, from her mother, etc.

The FMS or full mitochondrial sequence DNA test tests the entire mitochondria that provides information about your direct matrilineal line. Family Tree DNA provides matching, which can sometimes lead to genealogical breakthroughs such as when I identified Lydia Brown, the mother of my Phoebe Crumley and then a couple years later, her mother, Phoebe Cole – via mitochondrial DNA. Those discoveries led us to her mother, Mary Mercy Kent, via genealogy records. All we needed was to punch our way through that initial brick wall – and mitochondrial DNA was our battering ram.

Additionally, you’ll receive a full haplogroup designation which allows you to look back in time before the advent of surnames and identifies the location where your ancestral line came from. For those seeking confirmation of Native American heritage, Y and mitochondrial DNA provides unquestionable proof and doesn’t wash out in time as autosomal DNA does.

Mitochondrial DNA includes haplogroups, matching and other genealogical tools.

You can order or upgrade you or a family member’s mitochondrial DNA here.

To upgrade, sign in to your account, and click on the desired upgrade level.

ymt mt upgrade

Then click on Upgrade if you’re upgrading or Add On if you’re ordering a new product for yourself.

ymt add ons upgrades.png

I wrote several mitochondrial DNA articles and compiled them into a summary article for your convenience.

Autosomal DNA – With autosomal DNA testing, you test once and there’s not an upgrade unless the vendor changes DNA testing platforms, which is rare. Each of the four vendors compares your DNA with all other people who’ve taken that test, or transferred from other companies. They match you with descendants from all of your ancestral lines. While the Y and mtDNA tests look back deeply in time as well as recently on one specific line, the autosomal tests are broad but not deep, spanning all ancestral lines, but limited to approximately 10 generations.

Each autosomal vendor has unique benefits and focus as well as shortcomings. I’ve listed the major points for each vendor relative to searching for Y and mitochondrial
DNA testing candidates. It’s important to understand the advantages of each vendor because it will help you understand the testers you are most likely to find in each database and may help focus your search.

FamilyTreeDNA’s Family Finder

  • Because FamilyTreeDNA archives customer’s DNA for 25 years, many people who tested Y or mitochondrial DNA 20 years ago and are now deceased upgraded to autosomal tests when they became available, or have been upgraded by family members since. These early testers often reach back another generation or so into the past to people born a century ago.
  • Advanced autosomal matching integrates with Y and mitochondrial DNA along with surname and other projects
  • Phased Family Matching provides the ability to link family members that match you to your tree which allows Family Tree DNA to group matches as paternal or maternal by utilizing matching segments to the same side of your family
  • Genetic Affairs, a third-party tool available for testers, builds common trees by reading the trees of your matches and comparing their trees with your own to identify common ancestors.
  • Genetic Affairs builds trees and pedigrees of your matches by searching for common ancestors in your MATCHES trees, even if you have no tree or don’t share those ancestors in your tree. This functionality includes Y and mitochondrial DNA if you have tested. This facilitates discovery of common ancestors of the people who you match, which may well lead you to ancestral discoveries as well.
  • Genetic Affairs offers clustering of your shared matches.
  • DNA file transfers are accepted from other vendors, free, with a $19 one time fee to unlock advanced tools.
  • Family Tree DNA has tested people worldwide, with a few location exceptions, since inception in the year 2000.
  • No direct triangulation, but Phased Family Matching provides maternal and paternal side triangulation when matches can be grouped into maternal and paternal sides.
  • Matches and segment match information are available for download.
  • The great thing about the advanced matching tool at Family Tree DNA is that it facilitates searching for people who match you on different kinds of tests, so it helps determine the potential closeness or distance of Y and mitochondrial relationships.

MyHeritage

Ancestry

  • Ancestry has the largest database, but did not begin testing until 2012 and did not test widely outside of the US/UK for some time. They now sell tests in 34 countries. Their testers are primarily focused in the US, Canada, England, Scotland, Ireland, and diaspora, with some overlap into Europe.
  • Ancestry offers ThruLines, a tool that connects testers whose DNA matches with common ancestors in their trees.
  • Ancestry does not provide a chromosome browser, a tool provided by the other three primary testing companies, nor do they provide triangulation or matching segment location information necessary to confirm that you match on the same segment with other people.
  • Ancestry has issued cease and desist orders to third party tools that perform functions such as clustering, autotrees, autopedigrees or downloading of matches. Ancestry does not provide these types of features for their users.
  • Ancestry does not accept transfers, so if you want to be in Ancestry’s database, you must test with Ancestry.
  • No Y or mitochondrial DNA testing available.
  • Match list is not available for download.

23andMe

  • The primary focus of 23andMe has always been health testing, so many people who test at 23andMe are not interested in genealogy.
  • 23andMe tests are sold in about 50 countries, but not worldwide.
  • 23andMe provides a chromosome browser, triangulation, segment information and a beta genetically constructed tree for close matches.
  • 23andMe does NOT support a genealogical tree either uploaded or created on their site, making tree comparisons impossible.
  • Genetic Affairs AutoCluster works at 23andMe, but AutoTree and AutoPedigree do not because 23andMe does not support trees.
  • 23andMe does make match files available for downloading.
  • No Y or mitochondrial DNA full testing or matching, but basic haplogroups are provided.
  • 23andMe caps matches at 2000, less any matches that have opted out of matching. My matches currently number 1770.
  • 23andMe does not accept transfers from other vendors, so if you want to be in their database, you must test with 23andMe.

Reaching Out to Find Testers

Unfortunately, we only carry the mitochondrial DNA of our mother and only men carry the Y DNA of their father. That means if we want to obtain that DNA information about our other family lines, we have to find people who descend appropriately from the ancestor in question and test that person.

I’ll share with you how I search for people who descend from each ancestor. After finding that person, I explain the situation, why the different kinds of tests are important, and offer a testing scholarship for the Y or mtDNA test at Family Tree DNA if they have not already taken that test. If they’ve tested their autosomal DNA elsewhere. I also explain that they can transfer their autosomal DNA file for free too and will receive new matches.

Here’s an article with links to upload/download instructions for each testing company. Feel free to share.

Each DNA testing company has different features, but you can use all of the companies to find people descended in the appropriate way from each ancestor. It’s easier if you know how to utilize each vendor’s tools to optimize your chances of success. I’m going to step you through the search process with hints and tips for each vendor.

Finding Y DNA and Mitochondrial DNA Candidates at FamilyTreeDNA

Because FamilyTreeDNA tests for both Y and mitochondrial DNA and has for 20 years, you stand a better chance of finding a candidate there who may have already tested, so that’s where I always begin.

Y DNA

Let’s say, for example, that I need to find a male descendant of my Ferverda line in order to ask them to test for Y DNA. The person can be descended from either a close relative, if I know of one, or a more distant relative that I don’t know, but need to find through searching other ways.

Search for Surnames and Projects at Family Tree DNA

First, search the FamilyTreeDNA website for your goal surname among existing testers, and then the appropriate surname project to see if your line has already tested.

ymt ferverda

On the main page, here, scroll down to until you see the prompt, above, and enter the surname. Be sure to consider alternate spellings too.

ymt ferverda search.png

In this case, I see that there is a Ferverda surname project with 18 people, and scrolling on down, that 4 people with this specific surname have tested.

ymt results.png

However, searching for an alternate spelling, the way it’s spelled in the Netherlands, I find that another 10 people have tested.

ymt ferwerda

Of course, some may be females, but they probably know males by that surname.

First, I’m going to check the Ferverda DNA project to see if a Ferverda male from my line has tested, and if so, to what level.

Click on the project link in the search results to see the DNA Project.

ymt admin.png

Note two things. First, the administrator’s name, as you may need this later. If you click on their name, their email address is displayed.

Second, click on DNA Results and select Y DNA if you’re presented with a choice. If the project has a public facing page, and most do, you’ll see something like the following information.

ymt project

Hey look, it’s my lucky day, given that both of these men descend from my ancestor. I happen to know that they have both taken the Big Y test, because I’m the project administrator, but you won’t know that. One way to get an idea is if they have less than the full 111 markers showing, they probably haven’t taken the Big Y, because a 111 upgrade is included in the Big Y test today.

You have three options at this point to contact one of these men:

  • See if the people are on your own autosomal DNA match list, or the match lists of kits from that family that you manage. If so, you can view their email address and contact them. If you haven’t yet tested autosomally, meaning the Family Finder test, at Family Tree DNA, you can transfer autosomal tests from elsewhere, for free, which means you will be viewing matches within hours or a couple days. Otherwise, you can order a Family Finder test, of course.
  • If the person with the Ferverda or Ferwerda surname is not on your Family Finder match list, reach out to the project administrator with a note to the person you want to contact and ask the administrator to forward your email to the project member.
  • If the administrator doesn’t answer, contact Family Tree DNA support and make the same request.

Checking Family Finder, one of those people is on my match list and I’m pretty sure it’s the right person, because when I click on his profile, not only does the haplogroup match the DNA project, but so does the ancestor.

ymt ferverda profile.png

Searching Family Finder

If there isn’t a DNA project match you can identify as your direct line ancestor, you can search your Family Finder matches for the surname to find a male with that surname. If your match has a tree, see if your ancestor or ancestral line is showing, then note whether they have taken a Y DNA test. They may have taken a Y test, but have not joined a project or not entered any “earliest known ancestor.” You can see which tests they’ve taken by looking at the little tabs above their profile on their tree, or on their profile card.

ymt ferverda tree

click to enlarge

Regardless, you’re now in touch with a potential contact.

Don’t dismiss females with that surname, or people who show that surname in their ancestral surname list. Women with the surname you’re looking for may have husbands, fathers, brothers or uncles who descend from the line you are seeking.

ymt search field.png

Utilize Genetic Affairs

My ace in the hole at FamilyTreeDNA is the Genetic Affairs AutoTree and AutoPedigree function.

Genetic Affairs is a third-party tool that you can use to assist with analysis of your matches at FamilyTreeDNA.

ymt genetic affairs

click to enlarge

At Genetic Affairs, selecting AutoTree generates trees where common ancestors of you and your matches, or your matches to each other, are displayed.

Your goal is to identify people descended from a common ancestor either directly paternally through all males for Y DNA or through all females to the current generation, which can be males, for mitochondrial DNA.

This article provides step-by-step instructions for the Genetic Affairs AutoTree and AutoPedigree functions.

Mitochondrial DNA

Mitochondrial DNA lineages are a bit more challenging because the surname changes every generation and DNA projects are unlikely to help.

The AutoTree/AutoPedigree report through Genetic Affairs serves the same purpose for mitochondrial DNA – building trees that intersect with a common ancestor. I generally drop the “minimum size of the largest DNA segment shared with the match” to 7 cM for this report. My goal running this report for this purpose isn’t to analyze autosomal DNA, but to find testing candidates based on how my matches descend from a specific ancestor, so I want to include as many matches as possible.

Family Finder Can Refine Y and mtDNA Information

In some cases, a Family Finder test can refine a potential relationship between two people who match on either Y DNA or mitochondrial. Additionally, you may want to encourage, or gift, specific matches with an upgrade to see if they continue to match you at higher testing levels.

Let’s say that two men match closely on a Y DNA test, but you’d like to know how far back the common ancestor lived.

ymt y matches.png

In this instance, you can see that the second match has taken a BIg Y and a Family Finder test, but the exact match (genetic distance of 0) has not. If the first individual cannot provide much genealogy, having them take a Family Finder test would help at least rule out a relationship through second cousins and would give you at least some idea how far back in time your common ancestor may have lived. If you do match on Family Finder, you receive an estimate of your relationship and can check the match level possibilities using the DNAPainter Shared cM Tool. If they upgrade to the Big Y-700 test, you may be able to differentiate your line from theirs, or confirm when and where a split occurred – or that there is no split.

This same autosomal testing scenario works for mitochondrial DNA.

For people who have taken both tests, Family Finder plus either Y or mitochondrial DNA, the Advanced Matching menu allows you to select combinations of tests and projects to query.

ymt advanced

click to enlarge

Finding Y and Mitochondrial DNA Candidates at MyHeritage

MyHeritage provides a wonderful tool called Theories of Family Relativity (TOFR) which finds common ancestors between you and your DNA matches, even if the ancestor is not in both trees, so long as a path exists between the two testers’ trees using other trees or research documents, such as census records. Of course, you’ll need to verify accuracy.

ymt tofr.png

At MyHeritage, select DNA Matches, then “Has Theory of Family Relativity.”

ymt mh ferverda

click to enlarge

You can see that I have 65 matches with a Theory of Family Relativity. Additionally, I can then search by surname.

ymt mh ferverda tree.png

click to enlarge

If I am looking for a Ferverda Y DNA candidate, I’ve found one thanks to this TOFR.

If you don’t find a tree where your match descends from your ancestor in the desired way, you can also widen the search by de-selecting Theories of Family Relativity and instead selecting SmartMatchs or shared surname combined with the name of your ancestor. There are many search and filter combinations available.

Let’s look at a mitochondrial DNA example where I’m searching for a descendant of Elizabeth Speaks who married Samuel Clarkson/Claxton.

ymt smartmatches

click to enlarge

In this case, I have one SmartMatch, which means that someone by the name of Elizabeth Speaks is found in my matches tree. I need to look to see if it’s the RIGHT Elizabeth Speaks and if my match descends through all females to the current generation. If so, I’ve found my mitochondrial DNA candidate and I can leave them a message.

You can also view SmartMatches (without a DNA match) from your own tree.

I can go to that person in my tree, click on their profile, and see how many SmartMatches I have. Clicking on 13 SmartMatches allows me to view those matches and I can click through to the connected trees.

ymt mt speaks.png

I can also click on “research this person” to discover more.

If you’re still not successful, don’t give up quite yet, because you can search in the records for trees that shows the person whom you seek. A SmartMatch is only created if the system thinks it’s the same person in both trees. Computers are far from perfect.

ymt mh trees

click to enlarge

Narrow the search as much as possible to make it easier to find the right individual, and then view the trees for descent in the proper manner.

Another wonderful tool at MyHeritage is the Genetic Affairs AutoCluster tool, built-in for MyHeritage users.

ymt mh cluster.png

The above cluster shows that one person carries the surname of Elizabeth’s husband. Viewing the accompanying spreadsheet for the AutoCluster run reveals that indeed, I’ve already identified a couple of matches as descendants of the desired ancestral couple. The spreadsheet shows links to their trees, my notes and more.

ymt cluster ss

Clusters show you where to look. Without the cluster, I had only identified two people as descendants of this ancestral couple. I found several more candidates to evaluate and two mitochondrial candidates are found in this cluster.

Finding Y and Mitochondrial DNA Candidates at 23andMe

23andMe is a little more tricky because they don’t support either uploaded or created user trees which makes finding descendants of a particular ancestor quite challenging.

However, 23andMe attempts to create a tree of your closer relatives genetically. which you can find under “DNA Relatives,” under the Ancestry tab, then “Family Tree” at the top.

I’ve added the names of my ancestors when I can figure out who the match is. Please note that this “created tree” is seldom exactly accurate, but there are often enough hints that you’ll be able to piece together at least some of the rest.

Here’s part of my “created” tree at 23andMe. I’m at far right.

ymt23 tree.png

click to enlarge

If you’re a genealogist, your eyes are going to glaze over about now, because the “people” aren’t in the correct locations – with maternal and paternal sides of the tree swapped. Also, please note, the locations in which they place people are estimates AND 23andMe does NOT take into account or provide for half-relationships.

That said, you can still obtain candidates for Y and mitochondrial DNA testing.

In this case, I’m searching for a mitochondrial DNA candidate for Evaline Miller, my grandfather’s mother or a Y DNA candidate for the Ferverda line.

I can tell by the surname of the male match, Ferverda, that he probably descends through a son, making him a Y DNA candidate.

Both Cheryl and Laura are possible mitochondrial DNA candidates for Evaline Miller, based on this tree, depending of course on how they actually do descend.

I can contact all of my matches, but in the event that they don’t answer, I’m not entirely out of luck. If I can determine EXACTLY how the match descends, and they descend appropriately for mitochondrial DNA, I can view the match to see at least a partial haplogroup. Since 23andMe only uses relatively close matches when constructing your tree, I’m relatively likely to recognize the names of the testers and may have them in my genealogy program.

By clicking on the Ferverda male, I can see that his Y haplogroup is I-Z58. That’s not nearly as refined as the Y DNA information at Family Tree DNA, but it’s something if I have nothing else and he doesn’t answer my query that would include the offer of a Y DNA test at Family Tree DNA.

ymt 23 hap

You can search at 23andMe by surname, but unless your match has entered their ancestral surnames and you recognize surnames that fit together, without a tree, unless your match answers your query, it’s very difficult to determine how you connect.

ymt 23 search.png

You can also view “Relatives in Common,” hoping to recognize someone you know as a common match.

ymt relatives in common

Please note that 23andMe does allow testers to enter a link to a tree, but few do.

ymt tree link.png

It’s worth checking, and be sure to enter your own tree link location.

Finding Y and Mitochondrial DNA Candidates at Ancestry

Ancestry’s ThruLines provides an excellent tool to find both Y and mitochondrial DNA participants.

Ancestry organizes their ThruLines by ancestor.

ymt thrulines

click to enlarge

Select your desired Ancestor, someone whose DNA you seek. Clearly, Y DNA candidates are very easy because you simply choose any male ancestor in the correct line with the surname and look for a male match with the appropriate surname.

In this case, I’m selecting Martha Ruth Dodson, because I need her mitochondrial DNA.

ymt dodson.png

By clicking on her “card” I then see my matches assigned to her ThruLine.

Ymt ancestry thruline

Obviously, for mitochondrial DNA, I’m looking for someone descended through all females, so Martha’s daughter, Elizabeth Estes’s son Robert won’t work, but her daughter, Louisa Vannoy, at left is the perfect candidate. Thankfully, my cousin whom I match, at bottom left is descended through all females to the current generation, which can be male or female, so is a mitochondrial DNA candidate.

Finding Y and Mitochondrial DNA Candidates in Trees in General

I’ve utilized the combination of trees and DNA matches at FamilyTreeDNA through Genetic Affairs, Ancestry and MyHeritage, but you can also simply search for people who descend from the same ancestor based on their tree alone at the vendors who support trees as part of genealogical records. This includes both Ancestry and MyHeritage but also sites like Geneanet which is becoming increasingly popular, especially in Europe. (I have not worked extensively with Geneanet yet but plan to take it for a test drive soon.)

My reason for utilizing DNA matches+trees first is that the person has already been introduced to the concept that DNA can help with genealogy, and has obviously embraced DNA testing at least once. Not only that, with the assist of a Theory of Family Relativity, ThruLine or genetic Affairs automation tools, it’s much easier to find appropriate candidates.

Finding Y and Mitochondrial DNA Candidates at WikiTree

If you reach beyond DNA testing companies, WikiTree provides a valuable feature which allows people to specify that they descend from a particular ancestor, and if they have DNA tested, how they descend – including Y DNA, mitochondrial DNA and autosomal.

Here’s an example on the profile of John Y. Estes at WikiTree, one of my Estes ancestors.

ymt wiki.png

If someone descends appropriately for either Y or mitochondrial DNA line, and has taken that test, their information is listed.

In this case, there are two Y DNA testers and two autosomal, but no mitochondrial DNA which would have descended from John’s mother, of course.

You can click on the little green arrow icon to see how any DNA tested person descends from the ancestor whose profile you are accessing.

ymt wiki compare

Of course, the same surname for males is a good indication that the man in question is descended from that paternal line, but check to be sure, because some males took their mother’s surname for various reasons.

Here’s my line-of-descent from John Y. Estes. I can click on anyone else whose DNA information is listed as well to see how they descend from John. If they descend from John through all females, then they obviously descend from his wife though all females too which means they are a mitochondrial DNA candidate for her.

ymt wiki relationship.png

click to enlarge

Clicking on autosomal testers may reveal someone appropriately descended from the ancestor in question.

You can then click on any ancestor shown to view their profile, and any DNA tested descendants.

By clicking on name of the descendant whose DNA test you are interested in, you’ll be able to view their profile. Look for the Collaboration section where you can send them a private message that will be delivered by email from WikiTree.

ymt collaborate

Finding Y and Mitochondrial DNA Candidates at GedMatch

One final avenue to find Y and mitochondrial DNA candidates is through GedMatch, It’s probably the least useful option, though, because the major vendors all have some sort of tree function, except for 23andMe, and for some reason, many people have not uploaded GEDCOM files (trees) to GEDmatch.

Therefore, if you can find someone on GedMatch that tested elsewhere perhaps, such as LivingDNA who also provides a base haplogroup, or 23andMe, and they uploaded a GEDCOM file (tree) to GedMatch, you can utilize the GEDmatch “Find common ancestors” automated tree-matching functionality.

gedmatch mrca matches

click to enlarge

GEDmatch produces a list of your matches with common ancestors in their trees, allowing you to select the appropriate ancestor or lineage.

I wrote step-by-step instructions in the article, GEDmatch Introduces Automated Tree Matching.

Additionally, GEDmatch includes the Genetic Affairs AutoCluster tool in their Tier1 subscription offering,

ymt gedmatch.png

Gedmatch users who know their Y and mitochondrial haplogroup can enter that information in their profile and it will be reflected on the autosomal match list.

ymt gedmatch hap

Summary Chart

In summary, each testing vendor has a different focus and unique tools that can be used to search for Y and mitochondrial DNA candidates. Additionally, two other resources, WikiTree and GEDmatch, although not DNA testing vendors, can lead to discovering Y and mtDNA candidates as well.

I’ve created a quick-reference chart.

  Family Tree DNA MyHeritage Ancestry 23andMe Wikitree GEDmatch
Y DNA Test Yes No No No, partial haplogroup provided No test, listed by ancestor No, user entered
mtDNA Test Yes No No No, partial haplogroup provided No test, listed by ancestor No, user entered
DNA Projects Yes No No No Some Some
Strengths other than mentioned categories 20 year worldwide customer base, phased family matching European focus, SmartMatches, wide variety of filters Largest autosomal database Genetic tree beta DNA by ancestor May include users not found elsewhere who tested outside the major companies
Drawbacks No direct triangulation or tree matching No Genetic Affairs AutoTree or AutoPedigree Can’t download matches, no triangulation, clusters, AutoTree, or AutoPedigree No trees, 2000 match limit “One tree” may be incorrect Few trees, no AutoTree or AutoPedigree
Clustering Genetic Affairs Included in advanced tools No, prohibited Genetic Affairs N/A Included in Tier1
Genetic Affairs AutoTree & AutoPedigree Yes No No No, no tree support N/A No
Tree matching between users No, through Genetic Affairs Theories of Family Relativity ThruLines No Not directly MRCA common ancestors in Tier1

Now it’s your turn. Which Y and mitochondrial DNA lines can you find today?

Happy Hunting!

_____________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Products and Services

Genealogy Research

Plea to Ancestry – Rethink Match Purge Due to Deleterious Effect on African American Genealogists

I know this article is not going to be popular with some people and probably not with Ancestry, but this is something I absolutely must say. Those of us in the position of influencers with a public voice bear responsibility for doing such.

Let me also add that if you are of European heritage and you think this topic doesn’t apply to you – if you have any unidentified ancestors – it does. Don’t discount and skip over. Please read. Our voices need to be heard in unison.

Ancestry Lewis.jpg

The Bottom Line

Here’s the bottom line. Ancestry’s planned purge of smaller segments, 6-8 cM, is the exact place that African Americans (and mixed Native Americans too) find their ancestral connections. This community has few other options.

I’m sure, given the Ancestry blog post by Margo Georgiadis, Ancestry’s President and CEO on June 3rd that this detrimental effect is not understood nor intentional.

Ancestry Margo

Margo goes on to say, “At Ancestry, our products seek to democratize access to everyone’s family story and to bring people together.”

Yet, this planned match purge at the beginning of August does exactly the opposite. The outpouring of anguish from African American researchers has been palpable as they’ve described repeatedly how they use these segments to identify their genetic ancestors.

Additionally, my own experiences with discovering several African American cousins over the past few days as I’ve been working to preserve these smaller segment matches has been pronounced. I can even tell them which family they connect through. A gift them simply cannot receive in any other way – other than genetic connections

These two factors, combined, the community outcry and my own recent experiences are what have led me to write this article. In other words, I simply can’t NOT write it.

I trust and have faith that Ancestry will rethink their decision and utilize this opportunity for good and take positive action. Accordingly, I’ve provided suggestions for how Ancestry can make changes that will allow people on both sides of this equation, meaning those who want to keep those smaller segment matches and those glad to be rid of them, to benefit – and how to do this before it’s too late.

I don’t know if Ancestry has African American genealogists who are both passionate and active, or mixed-race genealogists, on their management decision-making team or in their influencer group, but they should.

I don’t think Ancestry realizes the impact of what they are doing. African American research is different. Here’s why.

African American History and Genetic Genealogy

Slavery ended in the US in the 1860s. Formerly enslaved persons who had no agency and control over their own lives or bodies then adopted surnames.

We find them in the 1870 census carrying a surname of unknown origin. Some adopted their former owner’s surname, some adopted others. Generally today, their descendants don’t know why or how their surnames came to be.

Almost all descendants of freed slaves are admixed today, a combination of African, European and sometimes Native Americans who were enslaved alongside Africans.

Closer DNA matches reflect known and unknown family in the 3 or 4 generations since 1870, generally falling in the 2nd to 4th cousin range, depending on the ages of the people at the time of emancipation and also the distance between births in subsequent generations.

Ancestry freed ancestors.png

The three red generations are the potential testers today. The cM values, the amount of potential matching DNA at those relationship levels are taken from DNAPainter, here, which is an interactive representation of Blaine Bettinger’s Shared cM Project.

Assuming we’re not dealing with an adoption or unknown parent situation, most people either know or can fairly easily piece together their family through first or second cousins.

You can see that it’s not until we get to the third and fourth cousin level that genealogists potentially encounter small segment matches. However, at that level, the average match is still significantly above the Ancestry purge threshold of 6-8 cM. In other words, we might lose some of those matches, but the closer the match, the higher the probability that we will match them (at all) and that we will match them above the purge threshold.

Looking again at the DNAPainter charts, we see that it’s not until we move further out in terms of relationships that the average drops to those lower ranges.

Ancestry DNAPainter

Here’s the challenge – relationships that occurred before the time of emancipation are only going to be reflected in relationships more distant than fourth cousins – and that is the exact range where smaller segment matches can and do come into play most often.

The more distant the relationship, the smaller the average amount of shared DNA, which means the more likely you are ONLY to be able to identify the relationship through repeated matching of other people who share that same ancestor.

Let me give you an example. If you match repeatedly to a group of people who descend from Thomas Dodson in colonial Virginia, through multiple children, especially on the same segment, you need to focus on the Dodson family in your research. If you’re a male and your Y DNA matches the Dodson line closely, that’s a huge hint. This holds for any researcher, especially for females without surnames, but it applies to all ancestral lines for African American researchers.

If an African American researcher is trying to identify their genetic ancestors, that likely includes ancestors of European origin. Yes, this is an uncomfortable topic, but it’s the unvarnished truth.

Full stop.

How Can African Americans Identify European Ancestors?

While enslaved people did not have surnames from the beginning of their history on these shores until emancipation, European families did. Male lines carried the same surname generation to generation, and female surnames changes in a predictable pattern, allowing genealogists to track them backward in time (hopefully.)

Given that African American researchers are literally “flying blind,” attempting to identify people with whom to reconnect, with no knowledge of which families or surnames, they must be able to use both DNA matches and the combined ancestral trees of their matches in order to make meaningful connections.

For more information on how this is accomplished, please read the articles here and here.

Tool or Method How it Works Available at Ancestry?
Y DNA for males Identifies the direct paternal line by surnames and also the haplogroup provides information as to the ancestral source such as European, African, Asian or Native American. No, only available at FamilyTreeDNA.
Mitochondrial DNA Identifies the direct matrilineal line. The haplogroup shows the ancestral source such as European, Native American, Asian or African. You can read about the different kinds of DNA, here. No, only available at FamilyTreeDNA
Clustering Identifies people all matching the tester and also matching to each other. No, available through Genetic Affairs and DNAGedcom before Ancestry issued a cease and desist letter to them in June.
Genetic Trees Tools to combine the trees of your matches to each other to identify common ancestors of your matches. You do not need a known tree for this to work. No, available at Genetic Affairs before Ancestry issued a cease and desist letter to them.
Downloading Match Information Including the direct ancestors for your matches. No, Ancestry does not allow this, and tools like Pedigree Thief and DNAGedcom that did provide this functionality were served with cease-and-desist orders.
Painting Segments Painting segments at DNAPainter allows the tester to identify the ancestral source of their segments. Multiple matches to people with the same ancestor indicates descent from that line. This is how I identify which line my matches are related to me through – and how I can tell my African American cousins how they are related and which family they descend from. No. Ancestry does not provide segment location information, so painting is not possible with Ancestry matches unless both people transfer to companies that provide matching segment information and a chromosome browser (MyHeritage, FamilyTreeDNA)
ThruLines at Ancestry Matches your tree to same ancestor in other people’s trees. ThruLines is available to all testers, but the tester MUST have a tree and some connection to an ancestor in their tree before this works. Potential ancestors are sometimes suggested predicated on people already in the tester’s tree connected to ancestors in their matches trees. For ThruLines to work, a connection must be in someone’s tree so a connection can be made. There are no tree links for pre-emancipation owned families. Those connections must be made by DNA.
DNA Matching Matching shows who you match genetically. Testers must validate that the match is identical by descent and not identical by chance by identifying the segment’s ancestry and confirming through either a parental match or matching to multiple cousins descending from the same ancestor at that same location. Segments of 7 cM have about a 50-50 chance of being legitimate and not false matches. Of course, that means that 50% are valid and tools can be utilized to determine which matches are and are not valid. All matches are hints, one way or another. You can read more, here. Ancestry performs matching, but does not provide segment information. Testers can, however, look for multiple matches with the same ancestors in their trees. Automated tools such as Genetic Affairs cannot be used, so this needs to be done one match at a time. The removal of smaller segment matches will remove many false matches, but will also remove many valid matches and with them, the possibility of using those matches to identify genetic ancestors several generations ago, before 1870.
Shared Matching Shows tester the people who match in common with them and another match. Ancestry only shows shared matches of “fourth cousins and closer,” meaning only 20 cM and above. This immediately eliminates many if not most relevant shared matches from before emancipation – along with any possibility of recovering that information.

The Perfect, or Imperfect, Storm

As you can see from the chart above, African American genealogists are caught in the perfect, or imperfect, storm. Many tools are not available at Ancestry at all, and some that were have been served with cease-and-desist letters.

The segments this community most desperately needs to make family connections are the very ones most in jeopardy of being removed. They need the ability to look at those matches, not just alone, but in conjunction with people they match in clusters, plus trees of those clustered matches to identify their common ancestors.

Ancestry has the largest database but provides very few tools to benefit people who are searching for unknown ancestors, especially before 1850 – meaning people who don’t have surnames to work with.

Of course, this doesn’t just apply to African American researchers, but any genealogist who is searching for women whose surnames they don’t know. This also applies to people with unknown parentage that occurred a few generations back in time.

However, the difference is that African American genealogists don’t have ANY surnames to begin with. They literally hit their brick wall at 1870 and need automated tools to breach those walls. Removing their smaller segment matches literally removes the only tool they have to work with – the small scraps and tidbits available to them.

Yes, false matches will be removed, but all of their valid matches in that range will be removed too – nullifying any possibility of discovery.

A Plan Forward

You’ve probably figured out by now that I’m no longer invited to the Ancestry group calls. I’m fine with that because I’m not in any way constrained by embargoes or expectations. I only mention this for those of you who wonder why I’m saying this now, publicly, and why I didn’t say it earlier, privately, to Ancestry. I would have, had the opportunity arisen.

That said, I want to focus on finding a way forward.

Some options are clearly off the table. I’m sure Ancestry is not going to add Y or mitochondrial DNA testing, since they did that once and destroyed that database, along with the Sorenson database later. I’m equally as sure that they are not going to provide segment location information or a chromosome browser. I know that horse is dead, but still, chromosome browser…

My goal is to identify some changes Ancestry can make quickly that will result in a win-win for all researchers. It goes without saying that if researchers are happy, they buy more kits, and eventually, Ancestry will be happier too.

Right now, there are a lot, LOT, of unhappy researchers, but not everyone. So what can we do to make everyone happier?

Immediate Solutions

  • Remove the cease and desist orders from the third-party tools like Genetic Affairs, DNAGedcom, Pedigree Thief and other third-party tools that researchers use for clustering, automated tree construction, downloading and managing matches.

This action could be implemented immediately and will provide HUGE benefits for the African American research community along with anyone who is searching for ancestors with no surnames. Who among us doesn’t have those?

  • Instead of purging small segment matches, implement a setting where people can define the threshold where they no longer see matches. The match would still appear to the other person. If I don’t want to see matches under 8 cM, I can select that level. If someone else wants to see all matches to 6 cM, they simply do nothing and see everything.
  • Continue to provide new matches to the 6 cM level. In other words, don’t just preserve what’s there today, but continue to provide this match level to genealogists.
  • Add shared matches under 20 cM so that genealogists know they do form clusters with multiple matches.

Longer-Term Solutions

  • Partner with companies like Genetic Affairs and DNAgedcom, tools that provided not just match data, but automated solutions. These wouldn’t have been so popular if they weren’t so effective.
  • Implement some form of genetic networks, like clustering. Alternatively, form alliances with and embrace the tools that already exist.

The Message Customers Hear

By serving the third-parts tools that serious genealogists used daily with cease-and-desist orders, then deleting many of our matches that can be especially useful when combined with automated tools, the message to genealogists is that our needs aren’t important and aren’t being heard.

For African American genealogists, these tools and smaller matches are the breadcrumbs, the final breadcrumb trail when there is nothing else at all that has the potential to connect them with their ancestors and connect us all together.

Let me say this again – many African Americans have nothing else.

To remove these small matches, rays of hope, is nothing short of immeasurably cruel, and should I say it, just one more instance of institutionalized racism, perpetrated without thinking. One more example of things the African American community cannot have today because of what happened to them and their ancestors in their past.

Plea

I will close this plea to Ancestry with another quote from Margaret Georgiadis from Ancestry’s blog.

Ancestry Margo 2.png

Businesses don’t get to claim commitment when convenient and then act otherwise. I hope this article has helped Ancestry to see a different perspective that they had not previously understood. Everyone makes mistakes and has to learn, companies included.

Ancestry, this ball’s in your court.

Feedback to Ancestry

I encourage you to provide feedback to Ancestry, immediately, before it’s too late.

You can do this by any or all of the following methods:

Ancestry support

Ancestry BLM.png

Speak out on social media, in groups where you are a member, or anyplace else that you can. Let’s find a solution, quickly, before it’s too late in another 10 days or so.

As John Lewis said, #goodtrouble.

Make a difference.

_____________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Products and Services

Genealogy Research

Fun DNA Stuff

  • Celebrate DNA – customized DNA themed t-shirts, bags and other items

“Earliest Known Ancestors” at Family Tree DNA in 3 Easy Steps

Why should you take the time to complete the information about your earliest known ancestor, your EKA, at Family Tree DNA?

The answer is simple – because it helps you with your genealogy and it helps others too. Genealogy, and in particular, genetic genealogy is by definition a team sport. It takes at least two to test and match – and the more, the merrier. From there, it’s all about information sharing.

Maybe the easiest way to illustrate the benefit of providing Earliest Known Ancestor information is by showing what happens if you DON’T complete the EKA field.

To be direct, you lose important opportunities to work with other genealogists and, if others don’t complete their EKA, you also lose the opportunity to see who their earliest known ancestors are. This information, when viewing your Y and mitochondrial DNA matches, shows immediately who is from your genetic line. It can also help you break down brick walls to push your own EKA back a few generations. I’ve used this tactic, successfully, repeatedly with both Y and mitochondrial DNA.

Earliest Known Ancestors Are Used 7 Ways

  • Matches – Every Y and mitochondrial DNA match displays your matches’ Earliest Known Ancestor

Here’s what your matches look like if they don’t complete their EKA information.

eka match.png

How depressing to see blanks listed for the Earliest Known Ancestor for your matches. These are exact full sequence mitochondrial matches, but no ancestors listed. A few do have trees, as indicated by the blue pedigree icon, but the ability to quickly view a list of ancestors would be so beneficial.

Looking at the matches for one of my Estes male cousins, below, you can see a much more helpful example.

eka complete

You may see a genealogical line you recognize. Or, several you don’t which may serve as a huge hint.

eka project.png

  • Surname and other types of projects, meant to attract more testers, also suffer when Earliest Known Ancestors and Countries of Origin, when known, aren’t completed.
  • Matches Maps – Another place where your Earliest Known Ancestor information will help is on the Matches Map which displays the location of your matches Earliest Known Ancestors, available for both Y DNA tests and mitochondrial DNA tests as well as Family Finder.

eka matches map

Looking for clusters of matches can be very revealing and can point your research in a specific direction. Genetic clues are indispensable, as is the information about the earliest ancestors of your matches. I am clearly related to these clusters of people in Scandinavia – but it’s up to me to figure out how, and when. It would be very useful to know of any of them share the same EKA.

Additional places where your EKA is utilized to provide information about your ancestry include:

  • Ancestral Origins: A page provided for both Y and mtDNA results where locations of your matches’ EKA are shown.
  • Haplogroup Origins: A page provided for both Y and mtDNA where locations of your haplogroup are found.

eka origins.jpg

I wrote about Ancestral Origins and Haplogroup Origins, here, and here, with lots of examples.

I wrote about the Y tree, here, which shows locations for each haplogroup. An article about the mitochondrial tree can be found here. These are the most comprehensive trees available, anyplace, and they are completely free and accessible to anyone, whether they have tested at FamilyTreeDNA or not. Science at work.

That’s 7 different ways your Earliest Known Ancestor information can benefit you – and others too.

However, this information can’t be utilized unless testers complete their EKA information.

Here’s how to enter your EKA information.

How Do You Complete Your Earliest Known Ancestor Information?

Your ancestor information lives in three separate places at FamilyTreeDNA – and they are not all interconnected meaning they don’t necessarily feed each other bidirectionally.

The information is easy to complete. We will step through each location and how to update your information.

What is Direct Paternal and Direct Maternal?

Before we go any further, let’s take just a minute and define these two terms.

When completing Earliest Known Ancestor information, you’ll be asked for your “Direct Paternal Ancestor” and “Direct Maternal Ancestor.” This does NOT mean the oldest person on each side, literally. Some people interpret that to mean the furthest person back on that side of your family. That’s NOT what it means either.

Your direct paternal ancestor is the furthest person in your tree on your father’s, father’s father’s direct paternal line. In other words, your most distant patrilineal ancestor.

Your direct maternal ancestor is the further person in your tree on your mother’s mother’s mother’s direct maternal line. This is your most distant matrilineal ancestor.

eka maternal paternal.png

In this view of my cousin’s tree, Holman Estes is the Earliest Known Ancestor on the paternal, meaning patrilineal, line. Of course, that’s also the Y DNA inheritance path too.

Sarah Jones is the Earliest Known Ancestor on the maternal, or matrilineal line. Mitochondria DNA descends down the matrilineal line.

The home person in this tree inherited the Y DNA of Holman Estes (and his patrilineal ancestors) and the mitochondrial DNA of Sarah Jones (and her matrilineal ancestors.)

Ok, let’s put this information to work.

Step 1 – Earliest Known Ancestor

When you sign on, click on the down arrow beside your name on the upper right hand corner of your personal page.

eka account settings

Click on “Account Settings.”

On the “Account Settings” page, click on “Genealogy,” then on “Earliest Known Ancestors.”

eka eka.png

In our example, above, the tester has completed the Direct Paternal Ancestor information, but not the Direct Maternal Ancestor.

Note that “Country of Origin” and “Location” are somewhat different. Location can mean something as specific as a city, county or region, along with map coordinates.

Country of Origin can mean something different.

To select a location and to complete your ancestor’s information, click on “Update Location.” If you don’t click on “Update Location,” you’ll need to save this form before exiting.

When you click on “Update Location,” the system takes you to the Matches Map screen where you can easily plot ancestral locations.

eka plot locations

In our example, we see that our tester has already entered his paternal EKA, Nicholas Ewstes in Deal, in the UK. We don’t need to do anything to that information, but we need to add a Maternal Location.

Click on “Edit Location”

eka update locations.png

You’ll see a screen where you can click to edit either the Maternal or Paternal Location. In this case, I’m selecting Maternal.

eka step 2

Enter the name of your ancestor. I tend to enter more information that will uniquely identify her to someone looking at their match list, such as when and where she lived.

eka more.png

If there’s room, I could also add “m 1849 Hayesville, Ohio to John Parr” which would further uniquely identify Sarah – especially given that her surname is Jones. If a match sees “Sarah Jones,” that doesn’t provide much context, but “Sarah Jones married in 1849 in Hayesville, Ohio to James Parr,” even if the tester doesn’t provide a tree, gives the match something to sink their teeth into.

When finished, click “Next.”

eka step 3

Enter the location and press “Search.” Longitude and latitude will be filled in for you.

eka select.png

Click “Select” if this is the correct location.

eka step 4

By changing the location name here, you could enter a historical name, for example, if the location name has changed since your ancestor lived there.

eka exit.png

You’ll see the final information before you Save and Exit.

eka both

You’ll view the map with your direct paternal ancestor and direct maternal ancestor both shown with pins on your map. This is before matching, of course.

Now, if you look back at the Direct Maternal Ancestor field under Account Settings, you’ll see the information you entered on the map, except for the Country of Origin.

eka direct maternal.png

This information doesn’t feed backwards into the EKA “Country of Origin” field, because country of origin can mean different things.

For example, my cousin’s direct maternal ancestor’s location would be United States because that’s where she lived. But is it where her line originated?

eka unknown origin

When looking at the Country of Origin dropdown box, you can see that United States can actually mean different things.

  1. Does it mean she was born here and we know her ancestors were European or African, but the specific country is uncertain?
  2. Does it mean her ancestors were Native American – and if so, do we actually know that, or is it yet unproven oral history?
  3. Or does United States simply mean that my cousin’s genealogy is stuck in Ohio?

In his case, it means stuck in Ohio. The mitochondrial haplogroup of this woman’s direct matrilineal descendants and her Matches Map tells us that her ancestors were European in origin, not Native or African.

In his case, “Unknown Origin” is not inaccurate, but by making that selection, other people won’t know if the tester really doesn’t know, or if they simply forgot to enter a location. I generally enter “United States” when the US is where I’m stuck.

Please note that the actual geographic location, including longitude and latitude, does populate from map selections.

When exiting the Direct Maternal or Direct Paternal Ancestors page, always click on the orange Save button, or it won’t.

Step 2 – Matches Map

You’ve already had a preview of this functionality in Step 1.

eka y matches map.png

The second way to populate EKA information is to select Matches Map directly from the menu on your personal page at Family Tree DNA.

eka pins

click to enlarge

I clicked on Matches Map from my cousin’s Y DNA page, so we’ll see his Y DNA Matches displayed. These pins displayed on his map are there because his matches entered their Earliest Known Ancestor information. The different colors indicate the relative closeness of matches.

His white pin that shows his own ancestor is displayed behind several other men’s pins (red arrow at right) who have also tracked their Y DNA ancestor to Deal, England and match the tester.

My cousin can update or enter his EKA information by clicking on “Update Ancestor’s Location” (red arrow at bottom) where a box allowing him to select between Paternal and Maternal will be displayed.

Please note that every pin on this map has an associated match that can be displayed by either mousing over the individual pins or by clicking on “Show Match List” in the bottom left corner.

Step 3 – Trees

Be sure to upload your tree too.

eka pedigree.png

Y DNA and mitochondrial DNA match pedigree icons looks like this, indicating your match has uploaded or created a tree.

eka pedigree ff

The Family Finder pedigree icon will be blue if a tree is provided and greyed out otherwise.

Always check your match’s tree because sometimes the Earliest Known Ancestor and the earliest ancestor in your match’s tree are not the same person.

Additional research may have been completed, but regardless of the reason for a discrepancy, you want to view the most distant person in that line.

Sometimes people get confused about who belongs in the Earliest Known Ancestor field, so a tree check is always a good idea.

  • Hint: If you see a male in the maternal field, you know they are confused. Same for a female in the paternal field.

To create or upload a GEDCOM file click on “myTree” at the top of your personal page.

download ancestry ftdna

Then, select your choice of creating a tree manually or uploading a GEDCOM file that you already created elsewhere.

eka create tree.png

If you need to download a tree from Ancestry to upload to FamilyTreeDNA, I wrote about how to do that, here.

Whether you upload or create a tree, choose yourself (assuming it’s your test, or select the person whose DNA test it is) as the home person in the tree.

eka home person

Bonus – Ancestral Surnames

Once your tree is uploaded, if you have NOT previously entered your Ancestral Surnames (under Account Settings,) uploading a GEDCOM file will populate the surnames, but not just with your direct ancestral lines. It populates ALL of the surnames from your tree. This isn’t a feature that I want. I recommend adding only direct line surnames manually or from a spreadsheet. If you have a small tree or don’t mind having surname matches not in your direct line, then allowing the surnames to auto-populate is probably fine.

eka surnames.png

If you’re wondering how Ancestral Surnames are used, the two Family Finder matches below illustrate the benefits.

eka surname list

When you have matching surnames in common, they float to the top of the list and are bolded. The first match matches the tester and they bothhave those bolded surnames in their trees.

With no matching surnames, the list is still present, but no bolding, as shown in the second match.

eka surname bold.png

You can then click on the ancestral surnames to see all of the surnames listed by that match.

If you search for matches that include a specific surname on Family Finder, that surname is displayed blue, the common surnames are bolded, and the rest aren’t.

eka surname search

By looking at these common ancestral surnames, I can often tell immediately how I’m related to my match.

eka surname blue.png

Summary

Using Earliest Known Ancestors, Matches Maps and Ancestral Surnames at Family Tree DNA is as easy a 1-2-3 and well worth the effort.

If you provided this information previously, is it still up to date? For your kit and any others you manage?

What hints are waiting for you?

Have other people uploaded their trees or added EKAs since you last checked?

You can always send an email to your matches who need to add Earliest Known Ancestors by clicking on the envelope icon. Feel free to provide them with a link to this article that explains the benefits of entering their EKA information along with step-by-step instructions.

DNA is the gift that just keeps on giving – but it can give a lot more with Earliest Known Ancestors and their locations!

_____________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Products and Services

Genealogy Research