Mitochondrial DNA A–Z: A Step-by-Step Guide to Matches, Mitotree, and mtDNA Discover

People have been asking for a step-by-step guide for mitochondrial DNA, and here it is!

This article steps testers through all their results, page by page, including a dozen Discover reports, explaining what the information in each tool means. There’s SO MUCH great content provided, and you’ll want to absorb every tidbit.

This is meant to be a roadmap for you – a recipe card to follow to get the most out of your results.

You can either read through this article once, then sign on to your own account, or sign on now and follow along. Yes, this article is long, but it’s also a one-stop shop when you want information about any page or feature. Refer back to this article as needed, and feel free to forward it to others when they receive their results.

I’ve also provided additional resources for you at each step of the way, along with many tips and suggestions to help you help yourself.

I’m using the LeJeune sisters of Acadia as my example – in part because there were several questions about their heritage – including whether they were actually sisters, whether they were Native American, and if a third woman was also a sister.

Think about why you tested, and what you hope to learn so you know where to focus.

Everyone has their own motivation for testing, and we all want to extract as much information as possible. Some answers are genetic – thanks to mitochondrial, Y-DNA, and autosomal testing. Some answers are historical and genealogical. All of them need to mesh nicely together and confirm each other.

When they don’t, if they don’t, we need to understand how to discern the truth.

Every Ancestor Has a Mitochondrial DNA Story to Tell You

Sometimes it’s not our own results we’re analyzing, but the results of another tester – a cousin whose mitochondrial DNA represents a particular shared ancestor. We aren’t restricted to just our own mitochondrial DNA to decipher our ancestors’ stories.

What messages and secrets do those ancestors have to tell us? Our results read like the very best mystery novel ever – except it’s not a novel – it’s fact. And it’s ours!

Mitochondrial DNA is only passed from mothers to their children, never admixed or combined with the DNA of the father, so your mitochondrial DNA today is either exactly the same as that of your ancestors a few generations ago, or very close if a mutation has occurred between when they lived and today’s tester.

One of mitochondrial DNA’s strengths is that it can reach far back in time, it’s message undiluted and uninterrupted by recombination.

The messages from our ancestors are very clear. We just need to understand how to hear what they are telling us.

Step-by-Step Soup to Nuts

We will analyze the mitochondrial DNA results of multiple testers who descend from the LeJeune sisters, Edmee and Catherine, born in 1624 and 1633, respectively, to see what they have to tell their descendants. For a very long time, rumors abounded that their mother was Native American, so we will keep that in mind as we review all matching, Mitotree and mtDNA Discover tools provided by FamilyTreeDNA.

We will also learn how to evaluate seemingly conflicting information.

Soup to nuts – we will incorporate every sliver of information along the way and extract every morsel that can help you. Think of this article as your recipe and the reports and information as ingredients!

To be clear, you don’t HAVE to read all of this or decipher anything if you don’t want to. You can just glance at the matches and be on your way – but if you do – you’re leaving an incredible amount of useful information on the table, along with MANY hints that you can’t find elsewhere.

If there was an out-of-print book about this ancestral line in a rare book collection someplace, as a genealogist, you would drive half-way across the country to access that information. This is your rare book, that updates itself, and you don’t have to do anything other than take a mitochondrial DNA test, or find a cousin to take one for lines you don’t carry..

Come along and join the fun! Your ancestors are waiting!

The LeJeune Question

Recently, I wrote about my ancestor Catherine LeJeune, who was born about 1633, probably in France before her family settled in Acadia, present-day Nova Scotia.

The identity of her parents has been hotly contested and widely debated for a long time.

I intentionally did not address her DNA results in that article because I wanted to establish the historical facts about her life and address her mitochondrial DNA separately. The process we are following to analyze her DNA results is the same process everyone should follow, which is why we are taking this step-by-step approach, complete with detailed explanations.

Often, when people hit a brick wall with an ancestor, especially during European colonization of the Americas, someone suggests that the person surely “must be” Native American. Lack of records is interpreted to add layers of evidence, when, in fact, absence of evidence is not evidence of absence.

For example, for many of the earliest French Acadians, birth and baptism records have NOT been located in France, where massive record loss has been experienced.

Additionally, not all records that do exist have been indexed, transcribed, or digitized. Many are damaged and/or nearly impossible to read. Lack of records does NOT mean that those settlers weren’t French, or in this case, it does NOT indicate that they were Native American. It simply means we are lacking that piece of evidence.

Enter mitochondrial DNA.

This article is focused on how to use mitochondrial DNA to decode these messages from our ancestors. I’m providing a very short summary of the relevant historical factors about the LeJeune sisters so readers can keep this in mind as we review the 17+ tools waiting for us when mitochondrial DNA results are ready.

The First Acadian Settlers

The Acadians were French settlers in what is today Nova Scotia. The first Acadians arrived in LaHeve (LaHave), on the southern coast of Acadia, in 1632 after Acadia was returned to France from English control. There may or may not have been any French families in the original group, but if so, very few. In 1636, another group of settlers arrived, but no LeJeune is on the roster.

At the end of 1636, the fledgling Acadian colony was moved from LaHeve, on the southern coast, to Port Royal, a more protected environment.

While we don’t know exactly when the family of Catherine and Edmee LeJeune arrived, we can bracket the dates. We know that Catherine’s sister, Edmee LeJeune, born about 1624, married another settler, Francois Gautrot, about 1644 in Port Royal, so they had arrived by that time.

Edmee’s 1624 birth year is important for two reasons. First, there were no French settlers in the part of Acadia that became Nova Scotia in 1624, so that clearly demonstrates that Edmee was born in France.

It’s unlikely that Catherine was born in Acadia in 1633 given that the first known families arrived in 1636, and we have their names from the ship roster. Pierre Martin was on the 1636 ship, and Acadian history tells us that his son, Mathieu Martin, was the first French child born in Acadia, about 1636, based on the 1671 census.

We also know that there was an early Acadian man, Jean LeJeune, who was granted land at BelleIsle, near Port Royal, among other Acadian families, but he was deceased before the first Acadian census in 1671. Acadia was under English control again from 1654 to 1670, so Jean LeJeune’s land grant had to have occurred after 1636 and prior to 1654, and is where Catherine LeJeune is found as an adult.

Another source of confusion is that there is a third LeJeune woman, Jeanne LeJeune dit Briard, born about 1659. Her daughter, Catherine Joseph’s 1720 marriage record in Port Royal refers to her mother, Jeanne, as being “d’un nation sauvagé”, giving her parents’ names as Francois Joseph and Jeanne LeJeune “of the Indian Nation.” Jeanne LeJeune dit Briard lived with her first husband in Port Royal, but had relocated to LaHeve by 1708.

You can see why this led to confusion about LeJeune females.

Another male, Pierre LeJeune was associated with LaHeve, which suggests he may have been awarded land there, possibly before the colony moved to Port Royal. One of the reasons that the rumor that Catherine LeJeune had a Native mother is so persistent is the belief that Pierre came over early, as a laborer or soldier, and married a Native woman because there weren’t any European women available.

Pierre may well have arrived as a single man, but there is no shred of evidence to suggest Pierre is the father of the sisters, Catherine LeJeune and Edmee LeJeune. In fact, given that Jeanne was born about 1659, Pierre, if he was her father, may have been born as late as 1627, which makes it impossible for him to have been Catherine and Edmee’s father.

That speculation was before the advent of DNA testing, and before Stephen White discovered that there was also a Jean LeJeune who was awarded land exactly where Catherine is known to have been living a few years later.

While it would be nice to unravel this entire cat’s cradle of confusion, the questions we are seeking to answer definitively here are:

  • Are Catherine LeJeune (born 1633) and Edmee LeJeune (born 1624) actually sisters?
  • Is the mother of Catherine LeJeune and her sister, Edmee LeJeune, Native American or European?
  • Is Jeanne LeJeune dit Briard, born about 1659, “d’un nation sauvagé” another sister of the LeJeune sisters?
  • What else is revealed about the LeJeune sisters and their ancestors? Is there something else we should know?

I’ll provide a summary of the combined evidence after our step-by-step mitochondrial analysis.

Testing for Sisters

Mitochondrial DNA is passed from mothers to all of their children, but only females pass it on.

Since we have two LeJeune females, believed to be sisters, we need mitochondrial DNA from direct matrilineal testers for each woman. This is particularly important because we know unquestionably that Edmee was born in France in 1624, prior to Acadian settlement in New France, so her DNA should be European. If they match, it means that Catherine was born to the same mother who was not Native. If they don’t match, there’s a different message.

In some cases, a match might mean that they were born to females related on the matrilineal line, like first cousins, for example. But in the early days of Acadia, there were no European females other than the handful, less than a dozen, who arrived on the Saint-Jehan in 1636.

Fortunately, we have multiple testers for each woman in two DNA projects at FamilyTreeDNA, the only DNA testing company that provides mitochondrial DNA testing and matching. Testers can join special interest projects, and both the Mothers of Acadia Project, and the Acadian AmerIndian Project have testers who descend from the LeJeune sisters.

I’ve identified 28 descendants of Catherine, and 25 from Edmee, giving us a total of 53 known matrilineal descendants to work with. Not all are shown publicly, in projects. Catherine has a known total of 14 testers, and Edmee has 17 that are shown publicly. All testers are members of haplogroup U6a7a1a.

The fact that the descendants of these women match each other, often exactly, combined with Catholic parish register dispensations for their descendants, when taken together, prove conclusively that Catherine and Edmee were sisters, not paternal half-sisters.

Let’s look at each piece of evidence.

Mitochondrial DNA Results

When the lab finishes processing the mtFull test, the results are posted to the account of the test taker.

Click on any image to enlarge

You’ll see the Maternal Line Ancestry section which displays your mitochondrial mtDNA Results.

The three tabs we will be primarily working with are:

  • mtDNA Matches
  • Matches Maps
  • Discover Haplogroup Reports, which includes another dozen+ reports and an updated Migration Map
  • Advanced Matching

At the bottom right of your page, you’ll see two haplogroup badges.

The one at right is called the “Legacy” haplogroup, which means the haplogroup you were assigned prior to the release of the new Mitotree.

The Mitotree mtDNA Haplogroup, with the green “Beta” at the bottom, is the new Mitotree haplogroup, which I wrote about in a series of articles:

Your old Legacy haplogroup will never change, because it’s the 2016 version that was not updated by the previous tree-keepers. That’s why the FamilyTreeDNA R&D team, me included, developed and birthed the new Mitotree. There were thousands of new haplogroups that could be defined to kick-start our genealogy, so we did.

The mitochondrial tree went from about 5000 branches to over 40,000 in the new Mitotree, each providing additional information to testers.

Not everyone received a new haplogroup, but about 75% of testers did, and another new Mitotree version will be released soon. In order to receive a new haplogroup, testers needed to:

  • Have at least one qualifying, stable mutation that had not been previously used to define a haplogroup
  • Match at least one other person in the same haplogroup branch with the same mutation(s)

In the case of the LeJeune sisters, there were no mutations that met all of the qualifications, so their known descendants did not receive a new haplogroup. That’s fine, though, because it’s not the name but the messages held by the information that’s important – and there’s a LOT to work with.

Let’s start with matches.

Matches

Of course, the first thing everyone does is click to see their matches.

The default is Detail View, but I prefer Table View (top left) because you can see more matches on the same page.

Catherine’s descendant whose matches are shown here has 108 Full Sequence matches, which are labeled as the “Coding Region.” The Coding Regions is the mtFULL test and includes both the HVR1 and HVR2 regions. Viewing Coding Region matches means they have taken the mtFull test, which sequences all 16,569 locations of the mitochondria.

When you click on the “Coding Region”, you are seeing matches to people who took all three test levels, not just the first one or two.

There are three test levels to view:

  1. HVR1
  2. HVR1+HVR2 both
  3. Coding Region, which is in addition to the HVR1+HVR2 regions

You can no longer order three different test levels today, although at one time you could. As costs decreased, it no longer made sense to offer multiple testing levels, and often the HVR1 or HVR1+HVR2 results, which only tested about 500 locations each, would confuse people.

People at the lower HVR1 or HVR1+HVR2 levels, known as mtPlus, can upgrade to the complete mtFull level, and should.

However, because some people only tested at those lower levels, matches are still shown at three levels, with different match thresholds for each level.

Matches at the HVR1 or HVR1+HVR2 levels *might* be entirely irrelevant, reaching back thousands of years. They could also be much more current, and critical to your genealogy, so don’t assume. Just one unstable mutation can cause a mismatch though, and at lower levels, cause you not to match someone with the same ancestor, which is why the full sequence test is so critically important.

For some testers, matches at lower levels sometimes provide the ONLY match to your known ancestor. So don’t skip over them. If you find a critical match there, you can email the tester to see if they will upgrade to the mtFull test.

People who test only at the HVR1 or HVR1+HVR2 level receive a more refined haplogroup after they upgrade, so the haplogroups between the HVR1/HVR2 testers and the full sequence test won’t match exactly. For the LeJeune sisters, the haplogroup for HVR1/HVR2-only testers is U6a and for full sequence testers, it’s U6a7a1a.

While full sequence matches are wonderful, if you’re searching for a particular ancestor and the ONLY place they appear is the HVR1 or HVR1+HVR2 testing levels, you’ll want to pursue the match. You may also want to evaluate lower level matches if their ancestors are from a specific location – like France – even if their earliest known ancestor (EKA) is not your ancestor.

To view your  HVR1 or HVR1+HVR2 matches, just click on either of those links. You’ll see ALL of the results, including everyone who took the full sequence test. In this case, that means that the 217 HVR1 (hypervariable region 1) results will include the 120 coding region (full sequence) tests. I’ve already looked through the full sequence matches, so that’s not what I want.

If you ONLY want to see testers who did NOT take the Full Sequence test, use the Filter option. Select Filter, then the features you seek.

Fortunately, the LeJeune sisters have lots of known descendants at the mtFull level to work with, so we will focus on their full sequence matches.

Your Focus

On the matches page, you’ll be immediately interested in two fields:

  • Maternal Earliest Known Ancestor (EKA) – the direct matrilineal ancestor of your match – unless they got confused and entered someone else
  • Their Tree

Viewing the first several matches only produced one match to someone whose earliest known ancestor (EKA) is listed as Catherine or Edmee LeJeune, but perhaps the next group will be more productive. Note that females’ EKAs, earliest known ancestors, are sometimes challenging, given surname changes. So unfamiliar EKAs could represent generational differences and sometimes offer other hints based on their information.

Shifting to the detail view for a minute, you’ll want to review the genetic distance,  meaning whether you’re an exact match or not.

If you’re not an exact match, a genetic distance of “1 step” means that you match except for one mutation at a specific location.

If you have a genetic distance greater than 3, meaning 4 mutations or more, you won’t be shown as a match on this match list. However, you can still be a haplogroup match, which we’ll discuss in the Discover section.

Essentially, with more than 3 mutations difference, it’s unlikely (but not impossible) that your match is genealogically relevant – meaning you probably won’t be able to identify your most recent common ancestor (MRCA).

However, that doesn’t mean that haplogroup-only matches can’t provide important clues, and we will look under every rock!

A Slight Detour – Confirmation Bias

This is a good place to mention that both ancestors and their location (country) of origin are provided by (some) testers to the best of their ability and understanding.

This tester selected “United States Native American” as the location for their earliest known ancestor. We don’t know why they entered that information. It could be that:

  • The tester did not understand that the maternal country of origin means the direct MATRILINEAL line, not just someplace on the maternal side
  • Selina Sinott was Native on her father’s side, or any line OTHER than her direct matrilineal line.
  • They relied on oral history or made a guess
  • They found the information in someone else’s tree
  • They found all of the LeJeune information confusing (because it is)

The tester has provided no tree, so we can’t do any sleuthing here, but an Ancestry search shows a woman by that name born in 1855 in Starksboro, VT to Louis Senott and Victoria Reya. A further search on Victoria leads me to Marie Lussier who leads me to Marguerite Michel who leads me to Marie Anne Lord (Lore, Laure), who lived in Acadia, whose ancestor is…drum roll…Catherine LeJeune. You get the idea.

Yes, you may need to extend other people’s trees.

The Point

However, and this is the point – if you’re looking for confirmation that the LeJeune sisters were Native American, this ONE tester who entered Native American for an unknown reason is NOT the confirmation you’re looking for. Don’t get sucked into confirmation bias, or into categorically believing what someone else entered without additional information.

You need haplogroup confirmation, but, in this case, you don’t have it. However, if you’re new to genetic genealogy, you don’t know that yet, so hold on. We’re still getting there. This is why we need to review all of the reports.

And trust me, I’m not being critical because there isn’t a single seasoned genealogist who has NOT fallen down the rathole of excited confirmation bias or accepting information without further analysis – me included. We all need to actively guard against it, all the time. Confirm and weigh all of the evidence we do have, and seek missing evidence.

Let’s go back to the match results.

Matches – Haplogroups and Haplotypes

Scrolling down the Table View, the next group of matches shows many more matches to descendants of both Catherine and Edmee LeJeune.

Next, you’ll notice that there’s a Mitotree haplogroup, U6a7a1a, AND an F number. In this case, they are both checked in blue, which means you share the exact same haplogroup with that tester, and the exact same haplotype cluster, which is the F number.

I wrote about haplotype clusters, here.

If NEITHER box is checked, you don’t share either the haplogroup nor the haplotype cluster.

You can match the haplogroup, but not the haplotype cluster, which means the haplogroup box will be checked, but the haplotype cluster will not. If you share the same haplotype cluster, you WILL share the same haplogroup, but the reverse is not true.

What is a Haplotype Cluster, and why do they matter?

Haplotype Clusters

We need to talk about exact matches and what they mean. Yes, I know it seems intuitive, but it isn’t.

There are three types of matches

  • Matching and Genetic Distance on your Match List
  • Haplotype matching
  • Haplogroup matching

Without getting (too much) into the weeds, an Exact Match in the Genetic Distance column on your match list excludes locations 309 and 315 because they are too unstable to be considered reliable for matching. So, 309 and 315 are EXCLUDED from this type of matching. In other words, you may or may not match at either or both of those locations. They are ignored for matching on your match list.

Locations 309 and 315 are also EXCLUDED from haplogroup definitions.

A haplotype F cluster match indicates that everyone in that cluster is an exact match, taking into consideration EVERY mutation, INCLUDING 309 and 315.

309 and 315 Why
Matching and Genetic Distance Excluded Unstable, probably not genealogically relevant and may be deceptive, leading you down a rathole
Haplogroup Definition Excluded Too unstable for tree branching and definition
Haplotype F Clusters Included Might be genealogically useful, so everyone can evaluate the rathole for themselves

Some people think that if they don’t match someone exactly, they can’t have the same ancestor as people who do match exactly, but that’s not true. “Mutations happen” whenever they darned well please. Downstream mutations in stable locations that match between two or more testers will form their own haplogroup branch.

The most distant matches are shown on the last match page, and as you can see below, some descendants of Catherine and Edmee LeJeune have a 1-step difference with our tester, meaning a genetic distance of one, or one mutation (disregarding 309 and 315). One match has a 2-step mutation.

The fact that their F numbers are not the same tells you that their mutations are different from each other, too. If two of those people also matched each other, their F# would be identical.

The mutations that do not (yet) form a haplogroup, and are included in your haplotype cluster, are called Private Variants, and you cannot see the private variants of other people. Clearly, you and anyone in your haplotype cluster share all of the same mutations, including Private Variants.

Evaluating Trees and EKAs

By reviewing the matches, their EKAs, and the trees for the matches of Catherine’s descendants, I was able to create a little mini-tree of sorts. Keep in mind that not everyone with an EKA has a tree, and certainly not everyone who uploaded a tree listed an EKA. So be sure to check both resources. Here’s how to add your EKA, and a one-minute video, here.

The good news is that if your match has a WikiTree link when you click on their tree icon, you know their tree actually reaches back to either Edmee or Catherine if that’s their ancestor, and you’re not dealing with a frustrating, truncated two or three-generation tree, or a private tree. You can add your WikiTree link at FamilyTreeDNA here, in addition to any other tree you’ve linked.

Takeaways from Matches

  • You can identify your common ancestor with other testers. By viewing people’s trees and emailing other testers, you can often reconstruct the trees from the tester back through either Catherine or Edmee LeJeune.
  • Your primary focus should be on the people in your haplotype cluster, but don’t neglect other clusters where you may find descendants of your ancestor.
  • If you see a male EKA name, or something other than a female name in the EKA field, like a location, the tester was confused. Only females pass their mitochondrial DNA to their descendants.
  • If you’re searching for an ancestor whose mitochondrial DNA you don’t carry, use projects and WikiTree to see if you can determine if someone has tested from that line. From viewing the project results, I already knew that the LeJeune sisters had several descendants who had tested.
  • If you’re searching for your ancestor on your match list, and you don’t find them in the full sequence results, use the filter to view people who ONLY took the HVR1 and HVR1+HVR2 tests to see if the results you seek are there. They won’t be on your full sequence match list because they didn’t test at that level. Testers at the lower levels will only have a partial, estimated haplogroup – in this case, U6a.
  • For Edmee and Catherine LeJeune, we have enough testers to ensure that we don’t have just one or two people with the same erroneous genealogy. If you do find someone in a project or at WikiTree claiming descent from the same ancestor, but with a different haplogroup, you’ll need to focus on additional research to verify each step for all testers.

Resources:

Matches Maps

The Matches Map is a great visual resource. That “picture is worth 1000 words” tidbit of wisdom definitely applies here.

Clicking on the Matches Maps displays the locations that your matches entered for their EKA.

In the upper left-hand corner, select “Full Sequence,” and only the full sequence matches will be displayed on the map. All full sequence testers also have HVR1/HVR2 results, so those results will be displayed under that selection, along with people who ONLY took the HVR1 or HVR1/HVR2 tests.

We know that the Acadians originally came from France, and their descendants were forcibly expelled from Nova Scotia in 1755. Families found themselves scattered to various locations along the eastern seaboard, culminating with settlements in Louisiana, Quebec, and in some cases, back in France, so this match distribution makes sense in that context.

Be sure to enlarge the map in case pins are on top of or obscuring each other.

Some people from other locations may be a match, too. Reviewing their information may assist with breaking down the next brick wall. Sometimes, additional analysis reveals that the tester providing the information was confused about what to complete, e.g., male names, and you should disregard that pin.

Takeaways from the Matches Map

  • These results make sense for the LeJeune sisters. I would specifically look for testers with other French EKAs, just in case their information can provide a (desperately needed) clue as to where the LeJeune family was from in France.

  • Reviewing other matches in unexpected locations may provide clues about where ancestors of your ancestor came from, or in this case, where descendants of the LeJeune sisters wound up – such as Marie Josephe Surette in Salem, Massachusetts, Catherine LeJeune’s great-granddaughter.
  • Finding large clusters of pins in an unexpected location suggests a story waiting to be uncovered. My matrilineal ancestor was confirmed in church records in Wirbenz, Germany, in 1647 when she married, but the fact that almost all of my full sequence matches are in Scandinavia, clustered in Sweden and Norway, suggests an untold story, probably involving the 30 Years War in Germany that saw Swedish troop movement in the area where my ancestor lived.
  • For my own mitochondrial DNA test, by viewing trees, EKAs, and other hints, including email addresses, I was able to identify at least a country for 30 of 36 full sequence matches and created my own Google map.
  • You can often add to the locations by creating your own map and including everyone’s results.

Resources:

Mitochondrial DNA Part 4 – Techniques for Doubling Your Useful Matches

Mitochondrial DNA Myth – Mitochondrial DNA is not Useful because the Haplogroups are “Too Old”

Before we move to the Discover Reports, I’m going to dispel a myth about haplogroups, ages, genealogical usefulness, and most recent common ancestors known as MRCAs.

Let me start by saying this out loud. YES, MITOCHONDRIAL DNA IS USEFUL FOR GENEALOGY and NO, OLDER HAPLOGROUPS DO NOT PREVENT MITOCHONDRIAL DNA FROM BEING USEFUL.

Here’s why.

The most recent common ancestor (MRCA) is the person who is the closest common ancestor of any two people.

For example, the mitochondrial DNA MRCA of you and your sibling is your mother.

For your mother and her first cousin, the mitochondrial MRCA is their grandmother on the same side, assuming they both descend from a different daughter. Both daughters carry their mother’s undiluted mitochondrial DNA.

A common complaint about mitochondrial DNA is that “it’s not genealogically useful because the haplogroups are so old” – which is absolutely untrue.

Let’s unravel this a bit more.

The MRCA of a GROUP of people is the first common ancestor of EVERY person in the group with each other.

So, if you’re looking at your tree, the MRCA of you, your sibling, and your mother’s 1C in the example above is also your mother’s grandmother, because your mother’s grandmother is the first person in your tree that ALL of the people in the comparison group descend from.

Taking this even further back in time, your mother’s GGG-grandmother is the MRCA for these five people bolded, and maybe a lot more descendants, too.

At that distance in your tree, you may or may not know the name of the GGG-grandmother and you probably don’t know all of her descendants either.

Eventually, you will hit a genealogical brick wall, but the descendants of that unknown “grandmother” will still match. You have NOT hit a genetic brick wall.

A haplogroup name is assigned to the woman who had a mutation that forms a new haplogroup branch, and she is the MRCA of every person in that haplogroup and all descendant haplogroups.

However, and this is important, the MRCA of any two people, or a group of people may very well be downstream, in your tree, of that haplogroup mother.

As you can clearly see from our example, there are four different MRCAs, depending on who you are comparing with each other.

  • Mom – MRCA of you and your sibling
  • Grandmother – MRCA of you, your sibling, your mom and your mom’s 1C
  • GGG-Grandmother – MRCA of all five bolded descendants
  • Haplogroup formation – MRCA of ALL tested descendants, and all downstream haplogroups, many of whom are not pictured

Many of the testers may, and probably do, form haplotype clusters beneath this haplogroup.

When you are seeking a common ancestor, you really don’t care when everyone in that haplogroup was related, what you seek is the common ancestor between you and another person, or group of people.

If the haplogroup is formed more recently in time, it may define a specific lineage, and in that case, you will care because that haplogroup equates to a woman you can identify genealogically. For example, let’s say that one of Catherine LeJeune’s children formed a specific haplogroup. That would be important because it would be easy to assign testers with that haplogroup to their appropriate lineage. That may well be the case for the two people in haplogroup U6a7a1a2, but lack of a more recent haplogroup for the other testers does not hinder our analysis or reduce mitochondrial DNA’s benefits.

That said, the more people who test, the more possibilities for downstream haplogroup formation. Currently, haplogroup U6a7a1a has 34 unnamed lineages, just waiting for more testers.

Haplogroup ages are useful in a number of ways, but haplogroup usefulness is IN NO WAY DEPRICATED BY THEIR AGE. The haplogroup age is when every single person in that haplogroup shares a common ancestor. That might be useful to know, but it’s not a barrier to genealogy. Unfortunately, hearing that persistent myth causes people to become discouraged, give up and not even bother to test, which is clearly self-defeating behavior. You’ll never know what you don’t know, and you won’t know if you don’t test. That’s my mantra!

The LeJeune sisters provide a clear example.

OK, now on to Discover.

mtDNA Discover

Next, we are going to click through from the mtDNA Results and Tools area on your personal page to Discover Haplogroup Reports. These reports are chapters in your own personal book, handed down from your ancestors.

Discover is also a freely available public tool, but you’ll receive additional and personalized information by clicking through when you are signed into your page at FamilyTreeDNA. Only a subset is available publicly.

mtDNA Discover was released with the new Mitotree and provides fresh information weekly.

Think of Discover as a set of a dozen reports just for your results, with one more, Globetrekker, an interactive haplogroup map, coming soon.

Resources:

When you click through to Discover from your results, Discover defaults to your haplogroup. In this case, that’s U6a7a1a for the LeJeune sisters.

Let’s begin with the first report, Haplogroup Story.

Haplogroup Story

The Haplogroup Story is a landing page that summarizes information about your ancestor’s haplogroup relevant to understanding your ancestor’s history. Please take the time to actually READ the Discover reports, including the information buttons, not just skim them.

Think of Discover as your own personalized book about your ancestors – so you don’t want to miss a word.

You’ll see facts on the left, each one with a little “i” button. Click there or mouse over for more information about how that fact was determined.

When we’re talking about haplogroup U6a7a1a, it sounds impersonal, but we’re really talking about an actual person whose name, in this case, we will never know. We can determine the ancestor of some haplogroups that formed within a genealogical timeframe. The LeJeune ancestor in question is the person in whose generation the final mutation in a long string of mutations created the final “a” in haplogroup U6a7a1a.

Think of these as a long line of breadcrumbs. By following them backwards in time and determining when and where those breadcrumbs were dropped, meaning when and where the mutation occurred, we begin to understand the history of our ancestor – where she was, when, and which cultures and events shaped her life.

U6a7a1a was formed, meaning this ancestor was born, about 50 CE, so about 1950 years ago. This means that the ancestor of ANY ONE PERSON with this haplogroup could have lived anytime between the year 50 CE and the year of their mother’s birth.

This is VERY important, because there is an incredible amount of  misunderstanding about haplogroup ages and what they mean to you.

The year 50 CE is the year that the common ancestor of EVERY PERSON in the haplogroup was born, NOT the year that the common ancestor of any two or more people was born.

By way of illustration, the LeJeune sisters were born in about 1624 and 1633, respectively, not 50 CE, and their most recent common ancestor (MRCA) is their mother, who would have been born between about 1590 and 1608, based on their birth years.

For reference, I’ve created this genealogical tree from individuals who took the mitochondrial DNA test and have identified their mitochondrial lineage on the LeJeune mother’s profile at Wikitree

You can see that both Edmee and Catherine have mitochondrial DNA testers through multiple daughters. I’ve color coded the MRCA individuals within each group, and of course their mother is the MRCA between any two people who each descend from Edmee and Catherine.

Mitochondrial DNA matches to the LeJeune sisters’ descendants could be related to each other anywhere from the current generation (parent/child) to when the haplogroup formed, about 50 CE.

You can easily see that all of these testers, even compared with their most distant relatives in the group, share a common ancestor born between 1590 and about 1608. Other people when compared within the group share MCRAs born about 1717 (blue), 1778 (peach), 1752 (green), 1684 (pink), 1658 (mustard), and 1633 (red).

Soooooo…a haplogroup born in 50 CE does NOT mean that you won’t be able to find any genealogical connection because your common ancestor with another tester was born more than 1900 years ago. It means that the common ancestor of EVERYONE who is a member of haplogroup U6a7a1a (and downstream haplogroups) was born about 50 CE.

The parent haplogroup of U6a7a1a is haplogroup U6a7a1, which was born about 1450 BCE, or about 3450 years ago.

In the graphic, I’ve shown other unknown genealogical lineages from U6a7a1 and also downstream haplogroups.

Haplogroup U6a7a1 is the MRCA, or most recent common ancestor of haplogroup U6a7a1a, and anyone who descends from haplogroup U6a7a1 or any of the 23 downstream lineages from U6a7a1, including 5 descendant haplogroups and 18 unnamed lineages.

The LeJeune haplogroup, U6a7a1a, has 35 descendant lineages. One downstream haplogroup has already been identified – U6a7a1a2 – which means two or more people share at least one common, stable, mutation, in addition to the mutations that form U6a7a1a. Thirty-four other lineages are as yet unnamed.

The fact that there are 34 unnamed lineages means that people with one or more private variants, or unique mutations, are candidates for a new branch to form when someone else tests and matches them, including those variants.

You’re a candidate for a new haplogroup in the future if no one else matches your haplotype cluster number, or, potentially, as the tree splits and branches upstream.

When a second person in a lineage tests, those two people will not only share a common haplotype cluster F#, they will share a new haplogroup too if their common mutation is not excluded because it’s unstable and therefore unreliable.

There are 127 members of haplogroup U6a7a1a today, and their EKAs are noted as being from France, Canada, the US, and other countries that we’ll view on other pages.

Haplogroup U6a7a1a has been assigned two Discover badges:

  • Imperial Age – “an age noted for the formation and global impact of expansive empires in many parts of the world.” In other words, colonization, which is certainly true of the French who battled with the English to colonize New England, Acadia, and New France.
  • mtFull Confirmed (for testers only)

Additionally, the LeJeune sisters have one Rare Notable Connection, and three Rare Ancient Connections, all of which may shed light on their history.

Takeaways from the Haplogroup Story

  • The Haplogroup Story provides an overview of the haplogroup
  • You can easily see how many testers fall into this haplogroup and where they have indicated as the origin of their matrilineal line.
  • The haplogroup may have several new haplogroup seeds – 34 in this case – the number of unnamed lineages
  • You can share this or other Discover pages with others by using the “share page” link in the upper right-hand corner.
  • Don’t be discouraged by the age of the haplogroup, whether it’s recent or older.

Next, let’s look at Country Frequency.

Country Frequency

Country Frequency shows the locations where testers in haplogroup U6a7a1a indicate that their EKA, or earliest known matrilineal ancestor, is found. The Country Frequency information is NOT limited to just your matches, but all testers in haplogroup U6a7a1a, some of whom may not be on your match list. Remember, only people with 3 mutations difference, or fewer, are on your match list.

Haplogroup distribution around the world is very informative as to where your ancestors came from.

There are two tabs under Country Frequency, and I’d like to start with the second one – Table View.

Table View displays all of the user-provided country locations. Note that the Haplogroup Frequency is the percentage of total testers in which this haplogroup is found in this particular country. These frequencies are almost always quite small and are location-based, NOT haplogroup based.

There are now 40,000 haplogroups, and in haplogroup U, the LeJeune sisters are 6 branches down the tree with U6a7a1a.

In total, 127 testers are members of haplogroup U6a7a1a, and 42 of those claim that their ancestor is from France, which comprises 1% of the people who have taken the full sequence mitochondrial DNA test whose ancestor is from that location.

Let’s do the math so you can see how this is calculated and why it’s typically so small. For our example, let’s say that 8000 people in the database have said their matrilineal ancestor is from France. Of the 127 haplogroup U6a7a1a members, 42 say their ancestor is from France. Divide 42 by 8,000, which is 0.00525, and round to the nearest percentage – which is 1%.

The best aspect of this page is that you can see a nice summary of the locations where people indicate that their earliest known U6a7a1a ancestor was found.

Please note that the last entry, “Unknown Origins,” is the bucket that everyone who doesn’t provide a location falls into. That row is not a total but includes everyone who didn’t provide location information.

These location results make sense for the LeJeune sisters – maybe except for Ireland and Belgium. Some people don’t understand the directions, meaning that a matrilineal ancestor or direct maternal ancestor is NOT your literal “oldest” ancestor on your mother’s side of the tree who lived to be 105, but your mother-to-mother-to-mother-to-mother ancestor, so check to see if these people with unusual locations are in your match list and view their tree or reach out to them.

We don’t know why the person who selected Native American made that choice, but I’d bet it has to do with confusion about the “other” LeJeune female, Jeanne LeJeune dit Briard. Based on Catherine and her sister, Edmee LeJeune’s haplogroup through more than 50 testers, U6a7a1a, Native is incorrect.

Of course, that tester wouldn’t have known that if they completed their EKA information before they tested. Perhaps they entered information based on the stories they had heard, or flawed genealogy, and didn’t think to go back and correct it when their results were ready, indicating that Native was mistaken.

On the “Map View” tab, the locations are shown using a heat map, where the highest percentages are the darkest. Here, both France and Canada are the darkest because that’s the most common selection for this haplogroup with 1% each, while the rest of the countries registered with less <1%.

These colors are comparative to each other, meaning that there is no hard and fast line in the sand that says some percentage or greater is always red.

To summarize these two tables, because this is important:

  • The Table View shows you how many people selected a specific country for their ancestor’s location, but the frequency is almost always very low because it’s based on the total number of testers in the entire database, comprised of all haplogroups, with ancestors from that country.
  • The Map View shows you a heat map for how frequently a particular location was selected, as compared to other locations, for this haplogroup.

To view the difference between adjacent haplogroups, I always compare at least one haplogroup upstream. In this case, that’s the parent haplogroup, U6a7a1.

The Parent Haplogroup

If you look at haplogroup U6a7a1, just one haplogroup upstream, you’ll see that for Mauritania, the total number of U6a7a1 descendants tested is only “1”, but the haplogroup frequency in Mauritania is 10% which means that there are only 10 people who have been tested in the database altogether from Mauritania – and one person is haplogroup U6a7a1.

However, due to substantial under-sampling of the Mauritania population, the frequency for Mauritania, 10%, is higher than any other location.

Also, remember, these are user-reported ancestor locations, and we have no idea if or how these people determined that their ancestor is actually from Mauritania.

Please only enter actual known locations. For example, we don’t want haplogroup U6a7a1 members to look at this informatoin, then add Mauritania as their location because now they “know” that their ancestor is from Mauritania.

On the Map View, Mauritania is dark red because the percentage is so high – never mind that there are only 10 testers who report matrilineal ancestors from there, and only one was U6a7a1.

This map illustrates one reason why taking the full sequence test is important. Viewing partial haplogroups can be deceiving.

Catherine and Edmee LeJeune’s matrilineal descendants who only tested at the HVR1 or HVR1+HVR2 level receive a predicted haplogroup of U6a, born about 21,000 years ago. That’s because the full 16,569 locations of the mitochondria need to be tested in order to obtain a full haplogroup, as opposed to about 500 locations in the HVR1 and HVR1/2, each, respectively.

U6a – The Result for HVR1/HVR2-Only Testers

So, let’s look at what haplogroup U6a reveals, given that it’s what early LeJeune descendants who ordered the lower-level tests will see.

In the Table View for U6a, below, you see that the top 5 counties listed by haplogroup frequency are five North African countries.

A total of 801 people are assigned to haplogroup U6a, meaning the majority, 757, report their ancestors to be from someplace else. If two people from the Western Sahara (Sahrawi) comprise 67% of the people who tested, we know there are only three people who have tested and selected that location for their ancestors.

If you didn’t understand how the display works, you’d look at this report and see that the “top 5” countries are North African, and it would be easy to interpret this to mean that’s where Catherine and Edmee’s ancestors are from. That’s exactly how some people have interpreted their results.

Scrolling on down the Table View, 50 testers report France, and 10 report the US, respectively, with France showing a Haplogroup Frequency of 1% and the US <1%.

The balance of U6a testers’ ancestors are from a total of 57 other countries, plus another 366 who did not select a location. Not to mention that U6a was born 21,000 years ago, and a lot has happened between then and the 1620/1630s when Catherine and Edmee were born to a French mother.

The real “problem” of course is that haplogroup U6a is only a partial haplogroup.

The U6a map shows the highest frequency based on the number of testers per country, which is why it’s dark red, but the Table View reports that the actual number of U6a testers reporting any specific country. France has 50. Next is the US, also with 50, which often means people are brick-walled here. You can view the U6a table for yourself, here.

Why is this relevant for Catherine and Edmee LeJeune? It’s very easy to misinterpret the map, and for anyone viewing U6a results instead of U6a7a1a results, it’s potentially genealogically misleading.

Use Country Frequency with discretion and a full understanding of what you’re viewing, especially for partial haplogroups from HVR1/HVR2 results or autosomal results from any vendor.

If someone tells you that the LeJeune sisters are from someplace other than France, ask where they found the information. If they mention Africa, Morocco or Portugal, you’ll know precisely where they derived the information.

This information is also available on your Maternal Line Ancestry page, under “See More,” just beneath the Matches tab. Haplogroup Origins and Ancestral Origins present the same information in a different format.

Discover is a significant improvement over those reports, but you’ll still need to read carefully, understand the message, and digest the information.

Takeaways from Country Frequency

  • Evaluate the results carefully and be sure to understand how the reports work.
  • Use complete, not partial haplogroups when possible.
  • The Haplogroup Frequency is the number of people assigned to this haplogroup divided by the entire number of people in the database who report that country location for their matrilineal ancestor. It is NOT the percentage of people in ONLY haplogroup U6a7a1a from a specific country.
  • Table view shows the number of testers with this haplogroup, with the percentage calculated per the number of people who have tested in that country location.
  • The Map shows the highest frequency based on the number of testers per country.
  • Use the map in conjunction with the haplogroup age to better understand the context of the message.

Globetrekker, which has not yet been released, will help by tracking your ancestors’ paths from their genesis in Africa to where you initially find that lineage.

Before we move on to the Mitotree, let’s take a minute to understand genetic trees.

About Genetic Trees

The Mitotree is a genetic tree, also called a phylogenetic tree, that generally correlates relatively closely with a genealogical tree. The more testers in a particular haplogroup, the more accurate the tree.

FamilyTreeDNA provides this disclaimer information about the genetic tree. The Mitotree you see is a nice and neat published tree. The process of building the tree is somewhat like making sausage – messy. In this case, the more ingredients, the better the result.

The more people that test, the more genetic information is available to build and expand the tree, and the more accurate it becomes.

The recent Mitotree releases have moved the haplogroup “dates” for the LeJeune sisters from about 21,000 years ago for HVR1/HVR2 U6a testers to 50 CE for full sequence testers, and this may well be refined in future tree releases.

Mutations

Mutations and how to interpret them can be tricky – and this short section is meant to be general, not specific.

Sometimes mutations occur, then reverse themselves, forming a “back mutation”, which is usually counted as a branch defining a new haplogroup. If a back mutation happens repeatedly in the same haplogroup, like a drunken sailor staggering back and forth, that mutation is then omitted from haplogroup branch formation, but is still counted as a mismatch between two testers.

A heteroplasmy is the presence of two or more distinct results for a specific location in different mitochondria in our bodies. Heteroplasmy readings often “come and go” in results for different family members, because they are found at varying threshold levels in different family members, causing mismatches. Heteroplasmies are currently counted only if any person has 20% or greater of two different nucleotides. So, if you have a 19% heteroplasmy read for a particular location, and your sister has 21%, you will “not” have a heteroplasmic condition reported, but she will, and the location will be reported as a mismatch.

If you have a heteroplasmy and another family member does not, or vice versa, it’s counted as as a “mismatch,” meaning you and that family member will find yourselves in different haplotype clusters. Hetroplasmies do not presently define new tree branches. I wrote about heteroplasmies, here.

Takeaways from the Genetic Tree Disclaimer

  • DNA is fluid, mutations happen, and all mutations are not created equal.
  • Thankfully, you really don’t need to understand the nitty-gritty underpinnings of this because the scientists at FamilyTreeDNA have translated your results into reports and features that take all of this into consideration.
  • Testing more people helps refine the tree, which fills in the genetic blanks, refining the dates, and expanding branches of the tree.

Resources:

Ok, now let’s look at the Time Tree

Time Tree

The Time Tree displays your haplogroup on the Mitotree timeline. In other words, it shows us how old the haplogroup is in relation to other haplogroups, and testers.

The Time Tree displays the country locations of the ancestors of testers who are members of that and descendant or nearby haplogroups. You can view the haplogroup U6a7a1a Time Tree, here, and follow along if you wish. Of course, keep in mind that the tree is a living, evolving entity and will change and evolve over time as updated tree versions are released.

Mousing over the little black profile image, which is the person in whom this haplogroup was born, pops up information about the haplogroup. Additionally, you’ll see black bars with a hashed line between them. This is the range of the haplogroup formation date. Additional details about the range can be found on the Scientific Details tab, which we’ll visit shortly.

On your Matches tab, remember that each match has both a haplogroup and a haplogroup cluster F# listed.

On the Time Tree, individual testers are shown at right, with their selected country of origin. In this case, you’ll see the person who selected “Native American” at the top, followed by France, Canada, the US, and other flags.

Haplogroup U6a7a1a includes several haplotype clusters, designated by the rounded red brackets. In this view, we can see several people who have haplotype cluster matches. Everyone has a haplotype assignment, but a haplotype cluster is not formed until two people match exactly.

In the Time Tree view, above, you can see two clusters with two members each, and the top of a third cluster at the bottom.

In case you’re wondering why some of the globes are offset a bit, they positionally reflect the birth era of the tester, rounded to the closest 25 years, if the birth year is provided under Account Settings. If not, the current tester position defaults to 1950.

Scrolling down to the next portion of the window shows that the third cluster is VERY large. Inside the cluster, we see Belgium, Canada, and France, but we aren’t even halfway through the cluster yet.

Continuing to scroll, we see the cluster number, F7753329, in the middle of the cluster, along with the French flag, two from Ireland, four from the US, and the beginning of the large unknown group.

In this fourth screenshot, at the bottom of the display, we see the balance of haplotype cluster #F7753329, along with eight more people who are not members of that haplotype cluster, nor any other haplotype cluster.

Finally, at the bottom, we find haplogroup U6a7a1a2, a descendant haplogroup of U6a7a1a. Are they descendants of the LeJeune sisters?

Looking back at our tester’s match list, the two people who belong to the new haplogroup U6a7a1a2 haven’t provided any genealogical information. No EKA or tree, unfortunately. The haplogroup formation date is estimated as about 1483, but the range extends from about 1244-1679 at the 95th percentile. In other words, these two people could be descendants of:

  • Either Catherine or Edmee LeJeune, but not both, since all of their descendants would be in U6a7a1a2.
  • An unknown sister to Catherine and Edmee.
  • A descendant line of an ancestor upstream of Catherine and Edmee.

Takeaways from the Time Tree

  • The visualization of the matches and haplotype clusters illustrates that the majority of the haplogroup members are in the same haplogroup cluster.
  • Given that two women, sisters, are involved, we can infer that all of the mutations in this haplotype cluster were common to their mother as well.
  • Haplotype cluster #F7753329 includes 19 testers from Catherine and 17 from Edmee.
  • Downstream haplogroup U6a7a1a2 was born in a daughter of haplogroup U6a7a1a, as early as 1244 or as late as 1679. Genealogy information from the two testers could potentially tell us who the mutation arose in, and when.
  • As more haplogroup U6a7a1a2 testers provide information, the better the information about the haplogroup will become, and the formation date can be further refined.

Smaller haplotype clusters have a story to tell too, but for those, we’ll move to the Match Time Tree.

Match Time Tree

The Match Time Tree is one of my favorite reports and displays your matches on the Time Tree. This feature is only available for testers, and you must be signed in to view your Match Time Tree.

By selecting “Share Mode”, the system obfuscates first names and photos so you can share without revealing the identity of your matches. I wrote about using “Share Mode” here. I have further blurred surnames for this article.

The Match Time Tree incorporates the tree view, with time, the names of your matches PLUS their EKA name and country, assuming they have entered that information. This is one of the reasons why the EKA information is so important.

This display is slightly different than the Time Tree, because it’s one of the features you only receive if you’ve taken the mtFull test and click through to Discover from your account.

The Time Tree view is the same for everyone, but the Match Time Tree is customized for each tester.

Your result is shown first, along with your haplotype cluster if you are a member of one.

You can easily see the names of the EKAs below the obfuscated testers’ names.

While we immediately know that descendants of both Catherine and Edmee are found in the large cluster #F7753329, we don’t yet know which ancestors are included in other haplotype clusters.

Haplogroup U6a7a1a includes two smaller haplotype clusters with 2 people each.

We know a few things about each of these clusters:

  • The people in each cluster have mutations that separate them from everyone else except the other person in their cluster
  • The results are identical matches to the other person in the cluster, including less reliable locations such as 309 and 315
  • There are other locations that are excluded from haplogroup formation, but are included in matching, unlike 309 and 315.
  • Given that they match only each other exactly, AND they did not form a new haplogroup, we know that their common unique mutation that causes them to match only each other exactly is unreliable or unstable, regardless of whether it’s 309, 315, a heteroplasmy, or another marker on the list of filtered or excluded variants.

Only the tester can see their own mutations. By inference, they know the mutations of the people in their haplotype cluster, because they match exactly.

If you’re a member of a cluster and you’re seeking to determine your common ancestor, you’ll want to analyze each cluster. I’ve provided two examples, below, one each for the red and purple clusters.

Red Haplotype Cluster #F3714849

Only one person in the red cluster has included their EKA, and the tree of the second person only reaches to three generations. Tracking that line backwards was not straightforward due to the 1755 expulsion of the Acadians from Nova Scotia.

The second person listed their EKA as Edmee LeJeune, but they have a private tree at MyHeritage, so their matches can’t see anything. I wonder if they realize that their matches can’t view their tree.

We are left to wonder if both people descend from Edmee LeJeune, and more specifically, a common ancestor more recently – or if the unstable mutation that they share with each other is simply happenstance.

E-mailing these testers would be a good idea.

Purple Haplotype Cluster #F2149611

Evaluating the purple cluster reveals that the common ancestor is Catherine LeJeune. The question is twofold – how are these two people related downstream from Catherine, and how unstable is their common mutation or mutations.

Fortunately, both people have nice trees that track all the way back to Catherine.

Unfortunately, their MRCA is Francoise, the daughter of Catherine. I say unfortunately, because two additional testers also descend from Francoise, and they don’t have the haplotype cluster mutation. This tells us that the cluster mutation is unreliable and probably not genealogically relevant because it occurred in two of Francoise’s children’s lines independently, but not all four.

In other words, that specific mutation just happened to occur in those two people.

This is exactly why some mutations are not relied upon for haplogroup definition.

Takeaways from the Match Time Tree

  • The time tree is a wonderful visualization tool that shows all of your matches, their EKAs and countries, if provided, in haplotype clusters, on the Time Tree. This makes it easy to see how closely people are related and groups them together.
  • On your match page, you can easily click through to view your matches’ trees.
  • You can use both haplotype clusters (sometimes reliable) and downstream haplogroups (reliable) to identify and define lineages on your family tree. For example, if a third person matches the two in haplogroup U6a7a1a2, the child haplogroup of U6a7a1a, and you could determine the common ancestor of any two of the three, you have a good idea of the genealogical placement of the third person as well.
  • You know that if people form a haplotype cluster, but not a new haplogroup, that their common haplotype cluster-defining mutation is less reliable and may not be genealogically relevant.
  • On the other hand, those less reliable mutations may not be reliable enough for haplogroup definition, but may be relevant to your genealogy and could possibly define lineage splits. Notice all my weasel words like “may,” “may not” and “possibly.” Also, remember our purple cluster example where we know that the mutation in question probably formed independently and is simply chance.
  • I can’t unravel the ancestors of the red cluster – and if I were one of those two people, especially if I didn’t know who my ancestor was, I’d care a lot that the other person didn’t provide a useful tree. Don’t forget that you can always reach out via email, offer to collaborate, and ask nicely for information.
  • We need EKAs, so please encourage your matches to enter their EKA, upload a tree or link to a MyHeritage tree, and enter a Wikitree ID in their FamilyTreeDNA profile, all of which help to identify common ancestors.

Resources:

Classic Tree

FamilyTreeDNA invented the Time Tree and Match Time Tree to display your results in a genealogically friendly way, but there is important information to be gleaned from other tree formats as well.

The Classic Tree presents the Mitotree, haplogroup and haplotype information in the more traditional format of viewing phylogenetic trees, combining their beneficial features. There’s a lot packed in here.

In this default view, all of the Display Options are enabled. We are viewing the LeJeune haplogroup, U6a7a1a, with additional information that lots of people miss.

The countries identified as the location of testers’ earliest known ancestors (EKA) are shown.

Listed just beneath the haplogroup name, five people are members of this haplogroup and are NOT in a haplotype cluster with anyone else, meaning they have unique mutations. When someone else tests and matches them, depending on their mutation(s), a new haplogroup may be formed. If they match exactly, then at least a new haplotype cluster will be formed.

Portions of three haplotype clusters are shown in this screenshot, designated by the F numbers in the little boxes.

Additional information is available by mousing over the images to the right of the haplogroup name.

Mousing over the badge explains the era in which the haplogroup was born. Rapid expansion was taking place, meaning that people were moving into new areas.

Mousing over the date explains that the scientists behind the Mitotree are 95% certain about the date range of the birth of this haplogroup, rounded to 50 CE. Remember, your common ancestor with ALL haplogroup members reaches back to this approximate date, but your common ancestor with any one, or a group, of testers is sometime between the haplogroup formation date, 50 CE, and the present day.

Mousing over the year shows the confidence level, and the date range at that level. These dates will probably be refined somewhat in the future.

If haplogroup members have private variants, it’s likely or at least possible that a new branch will split from this one as more people test

Mousing over the star displays the confidence level of the structure of this portion of the Mitotree based on what could be either confusing or conflicting mutations in the tree. For haplogroup U6a7a1a, there’s no question about the topology, because it has a 10 of 10 confidence rating. In other words, this branch is very stable and not going to fall off the tree.

Every haplogroup is defined by at least one mutation that is absent in upstream branches of the tree. Mutations are called variants, because they define how this sample, or branch, varies from the rest of the branches in the Mitotree.

These two mutations, A2672G and T11929C, are the haplogroup-defining mutations for U6a7a1a. Everyone in haplogroup U6a7a1a will have these two mutations in addition to all of the mutations that define directly upstream haplogroups (with extremely rare exceptions). Haplogroup-defining mutations are additive.

There may be more haplogroup-defining mutations than are displayed, so click on the little paper icons to copy to your clipboard.

You can view upstream haplogroups and downstream haplogroups, if there are any, by following the back arrows to upstream haplogroups, and lines to downstream haplogroups.

For example, I clicked on the arrow beside haplogroup U6a7a1a to view its parent haplogroup, U6a7a1, and a second time to view its parent, haplogroup U6a7a. If I click on the back arrow for U6a7a, I’ll continue to climb up the tree.

Beneath U6a7a, you can see the haplogroup branches, U6a7a1a and U6a7a2.

Beneath U6a7a1, you’ll notice:

  • People who don’t share haplotype clusters with anyone
  • Three haplotype clusters
  • Five descendant haplogroups from U6a7a1, including the LeJeune sister’s haplogroup U6a7a1a.

To expand any haplogroup, just click on the “+”.

You may see icons that are unfamiliar. Mouse over the image or click on the “Show Legend” slider at upper right to reveal the decoder ring, I mean, legend.

You can read more about the symbols and how haplogroups are named, here, and see more about types of mutations in the Scientific Details section.

Takeaways from the Classic Tree

  • The Classic Tree provides a quick summary that includes important aspects of a haplogroup, including when it was formed, which mutations caused it’s formation, and each branch’s confidence level.
  • It’s easy to back your way up the tree to see where your ancestor’s founding haplogroups were located, which speaks to your ancestor’s history. Patterns, paths, and consistency are the key.
  • Ancient DNA locations in your tree can provide a very specific location where a haplogroup was found at a given point in time, but that doesn’t necessarily mean that’s where the haplogroup was born, or that they are your ancestor. We will get to that shortly.
  • You can share this page with others using the “Share Page” function at the top right.

Ancestral Path

The Ancestral Path is a stepping-stone chart where you can view essential information about each haplogroup in one row, including:

  • Age and era
  • Number of years between haplogroups
  • Number of subclades
  • Number of modern-day testers who belong to this haplogroup
  • Number of Ancient Connections that belong to this haplogroup, including all downstream haplogroups

This “at a glance” history of your haplogroup is the “at a glance” history of your ancestors.

The number in the column titled “Immediate Descendants”, which is the number of descendant haplogroups, tells a story.

If you see a large, or “larger” number there, that indicates that several “child” haplogroups have been identified. Translated, this means that nothing universally terrible has occurred to wipe most of the line out, like a volcano erupting, or a famine or plague that would constitute a constraining bottleneck event. Your ancestors’ children survived and apparently thrived, creating many descendant downstream haplogroups, known as an expansion event.

If you see a smaller number, such as rows 5, 7, 8, 9, and 13, each of which have only two surviving branches, yours and another, several branches probably didn’t survive to the present day. This may reflect a bottleneck where only a few people survived or the lines became extinct over time, having no descendants today. Either that, or the right people haven’t yet tested. Perhaps they are living in a particularly undersampled region of the world, a tiny village someplace, or there aren’t many left.

The two most recent haplogroups have the most subclades, indicating that your ancestors were successfully reproducing in the not-too-distant past. Mutations occurred because they randomly do, creating new haplogroups, and several haplogroup members have tested today. Hopefully, genealogy can connect us further.

The next column, “Tested Modern Descendants,” tallies the total number of testers as it rolls up the tree. So, each haplogroup includes the testers in its downstream (child) haplogroups. The 127 people in haplogroup U6a7a1a include the two people in haplogroup U6a7a1a2, and the 226 people in haplogroup U6a7a1 include the 127 people in haplogroup U6a7a1a.

Looking at other types of trees and resources for each haplogroup can suggest where our ancestors were at that time, perhaps correlating with world or regional history that pertains to the lives of those ancestors.

In our case, the LeJeune sisters’ ancestors did well between 3450 years ago through the formation of U6a7a1a, about 1950 years ago. 3500 years ago, in Europe, settlements were being fortified, leadership was emerging as complex social patterns formed, and trade networks developed that spanned the continent and beyond.

Between 20,000 and 3,450 years ago, not so much. This correlates to the time when early European farmers were moving from Anatolia, bringing agriculture to Europe en masse. However, they were not the first people in Europe. Early modern humans arrived and lived in small groups about 50,000 years ago.

And they very nearly didn’t survive. Many lines perished.

Takeaways from the Ancestral Path

  • The Ancestral Path shows the stepping stones back to Mitochondrial Eve, dropping hints along the way where expansions occurred, meaning that your ancestors were particularly successful, or conversely, where a bottleneck occurred and the lineage was in jeopardy of extinction.
  • In some cases, where a lot of time has passed between haplogroups, such as 8,000 years between U and U6, we’re seeing the effect of lineages dying out. However, with each new tester, there’s the possibility of a previously undiscovered branch split being discovered. That’s precisely what happened with haplogroup L7.

Migration Map

The Discover Migration Map shows the path that your ancestor took out of Africa, and where your base ancestral haplogroup was formed.

Mousing over the little red circle displays the haplogroup, and the area where it originated. Based on this location where U6 was found some 31,000 years ago, we would expect to find U6 and subgroups scattered across North Africa, the Levant, and of course, parts of Eurasia and Europe.

It’s interesting that, based on what we know using multiple tools, it appears that haplogroup U initially crossed between the Horn of Africa and the Arabian Peninsula, at the present-day Strait of Bab-el-Mandeb. Today, that crossing is about 15 nautical miles, but the sea level was much lower during earlier times in history, including the last glacial maximum. Humans would have seen land across the water, and could potentially have swum, drifted, or perhaps used early boats.

Over the next 10,000+ years, haplogroup U trekked across the Arabian peninsula into what is present-day Iran, probably moving slowly, generation by generation, then turning back westward, likely in a small group of hunter-gatherers, crossing the Nile Delta into North Africa, present-day Egypt.

They probably fished along the Nile. Food would have been plentiful along rivers and the sea.

It’s exciting to know that the ancestors of the LeJeune sisters lived right here, perhaps for millennia.

There’s more, however.

The Migration Map shows the location of the genetically closest Ancient DNA results to your haplogroup, obtained from archaeological excavations. This mapped information essentially anchors haplogroup branches in locations in both space and time.

Ancient DNA samples are represented by tiny brown trowels. Clicking on each trowel provides summary information about the associated sample(s) in that location.

Takeaways from the Migration Map

  • Scientists have estimated the location where your base haplogroup originated. For the LeJeune sisters, that’s haplogroup U6 in North Africa along the Mediterranean Sea.
  • The trowels show the locations of the genetically closest archaeological samples, aka Ancient Connections, in the FamilyTreeDNA data base.
  • These Ancient Connections displayed on the map may change. New samples are added regularly, so your older samples, except for the oldest two, which remain in place for each tester, will roll off your list when genetically closer Ancient Connections become available.
  • There are no Ancient Connections for the LeJeune sisters in France today, but keep in mind that Europe is closely connected. Today’s French border is only about 25 miles as the crow flies from Goyet, Belgium. France, sea to sea, is only about 500 miles across, and at its closest two points, less than 250 miles.
  • Samples found at these locations span a large timeframe.

There’s a LOT more information to be found in the Ancient Connections.

Ancient Connections

Ancient Connections is one of my favorite Discover features. This information would never have been available, nor synthesized into a usable format, prior to the introduction of Mitotree and mtDNA Discover. Ancient Connections unite archaeology with genealogy.

  • The first thing I need to say about Ancient Connections is that it’s unlikely that these individuals are YOUR direct ancestors. Unlikely does not mean impossible, but several factors, such as location and timeframe need to be considered.
  • What is certain is that, based on their mitochondrial haplogroup, you SHARE a common ancestor at some point in time.
  • Ancient samples can be degraded, with missing genetic location coverage. That means that not every mutation or variant may be able to be read.
  • Different labs maintain different quality criteria, and location alignments may vary, at least somewhat, lab to lab. While this is always true, it’s particularly relevant when comparing ancient DNA results which are already degraded.
  • Samples are dated by archaeologists using a variety of methodologies. FamilyTreeDNA relies on the dates and historical eras provided in the academic papers, but those dates may be a range, or contain errors.
  • Obtaining information from ancient DNA samples isn’t as easy or straightforward as testing living people.

However, the resulting information is still VERY useful and incredibly interesting – filling in blanks with data that could never be discerned otherwise.

Many people mistakenly assume that these Ancient Connections are their ancestors, and most of the time, not only is that not the case, it’s also impossible. For example, a woman who lived in 1725 cannot be the ancestor of two sisters who were born in 1624 and 1633, respectively.

When you click on Ancient Connections, you see a maximum of about 30 Ancient Connections. Information about the genetically closest burial is displayed first, with the most distant last on the list.

Please note that the final two are the oldest and will (likely) never change, or “roll off” your list, unless an even older sample is discovered. When new samples become available and are genetically closer, the oldest other samples, other than the oldest two, do roll off to make space for the closer haplogroups and their corresponding samples.

Obviously, you’ll want to read every word about these burials, because nuggets are buried there. I strongly encourage you to read the associated papers, because these publications reveal snippets of the lives of your haplogroup ancestors and their descendants.

The small pedigree at right illustrates the relationship between the ancient sample and the haplogroup of the tester. Three things are listed:

  1. El Agujero 8, the name assigned by the authors of the paper that published the information about this ancient sample
  2. The haplogroup of the LeJeune descendant who tested
  3. The haplogroup of their common ancestor.

If no haplogroup is specifically stated for the ancient sample, the sample is the same haplogroup as the common shared ancestor (MRCA), meaning the tester and the ancient sample share the same haplogroup.

The Time Tree beneath the description shows the tester’s haplogroup, (or the haplogroup being queried), the ancient sample, and their common ancestral haplogroup.

Let’s analyze this first sample, El Agujero 8.

  • The person whose remains were sampled lived about 1375 years ago (I’ve averaged the range), in the Canary Islands, and is part of the Guanche culture.
  • The Guanche are the indigenous people of the Canary Islands, already established there before the arrival of Europeans and the Spanish conquest of the 1400s.
  • The Guanche people are believed to have arrived in the Canaries sometime in the first millennium BCE (2000-3000 years ago) and were related to the Berbers of North Africa.
  • This makes sense if you consider the Migration map and geographic proximity.
  • Haplogroup U6a7a1, the haplogroup of El Agujero 8, is the shared ancestral haplogroup with the LeJeune sisters.
  • That woman, U6a7a1, lived around 1450 BCE, or 3450 years ago, probably someplace in North Africa, the Mediterranean basin, or even in the Nile Delta region, given the correlation between the Canary Islands settlement, the Berbers, and the Migration Map.
  • This does NOT mean that the ancestor of the LeJeune sisters lived in the Canary Islands. It means that a descendant of their MRCA, haplogroup U6a6a1, the shared common ancestor with the LeJeune sisters, lived in the Canary Islands.

Ancient Connections Chart Analysis Methodology

I create an Ancient Connection chart for each haplogroup I’m dealing with. We’re analyzing the LeJeune sisters today, but I track and analyze the haplogroup for every ancestor whose haplogroup I can find, or for whom I can find a descendant to test.

In this chart, YA=years ago and is based on the year 2000. KYA=thousand years ago, so 10 KYA is 10,000 years ago.

Name Person Lived Location & Culture Haplogroup, Date & Age Shared (MRCA) Haplogroup, Date & Age Note
LeJeune Sisters Born 1624 & 1633 French Acadian U6a7a1a,

50 CE,

1950 YA

U6a7a1a,

50 CE,

1950 YA

In Acadia by 1643/44
El Agujero 8 1375 CE Canary Islands, Guanche U6a7a1

1450 BCE, 3450 YA

U6a7a1 1450 BCE, 3450 YA Guanche arrived in Canaries in 1st millennium BCE, related to Berbers
Djebba 20824 6000 BCE Jebba, Bājah, Tunisia, Neolithic U6a3f3’4’5

c 5000 BCE, 7000 YA

U6a1”9

19,000 BCE, 21,000 YA

This archaeology site is on the northernmost point of North Africa
Djebba 20825 5900 BCE Djebba, Bājah, Tunisia, Neolithic U6a1”9

19,000 BCE, 21,000 YA

U6a1”9

19,000 BCE, 21,000 YA

This archaeology site is on the northernmost point of North Africa
Egyptian Mummy 2973 200 BCE Abusir el-Meleq, Giza, Egypt, Ptolemaic Kingdom U6a3h^,

1450 BCE,

3450 YA

U6a1”9

19,000 BCE, 21,000 YA

Nile Delta probably, paper says they share ancestry with near easterners
Egyptian Mummy 2888 100 BCE Abusir el-Meleq, Giza, Egypt, Ptolemaic Kingdom U6a2a’c,

11,000 BCE,

13,000 YA

U6a1”9

19,000 BCE, 21,000 YA

Nile Delta probably, paper says they share ancestry with near easterners
Segorbe Giant (6’3”) 1050 CE Plaza del Almudín, Valencia, Spain, Islamic necropolis burial U6a1a1, 14,000 BCE, 16,000 YA

 

U6a1”9

19,000 BCE, 21,000 YA

Paper says his genetic makeup is Berber and Islamic Spain, buried in Islamic style on right side facing Mecca.
Sweden Skara 1050 CE Varnhem, Skara, Sweden, Viking Swedish culture U6a1a3a, 7350 BCE, 9350 YA, U6a1”9

19,000 BCE, 21,000 YA

Viking burial

 

Chapelfield 696 1180 CE Chapelfield, Norwich, England, Ashkenazi Jewish Medieval age U6a1b1b. 400 BCE,

2400 YA

 

U6a1”9

19,000 BCE, 21,000KYA

Possibly the 1190 antisemitic Norwich massacre
Montana Mina 38 1200 CE Montana Mina, Lanzarote, Spain (Canary Islands), Guanche culture U6a1a1b1 U6a1”9

19,000 BCE, 21,000 YA

Guanche arrived in Canaries in 1st millennium BCE, related to Berbers
Amina 1725 CE Gaillard Center, Charleston, South Carolina, Enslaved African American burials U6a5b’f’g,

9550 BCE, 11,550 YA,

U6a1”9

19,000 BCE, 21,000 YA

Remains of pre-Civil War enslaved Africans unearthed in Charleston, SC
Doukanet el Khoutifa 22577 4400 BCE Doukanet el Khoutifa, Mars, Tunisia, Maghrebi cultural group U6b,

6500 BCE, 8500 YA

 

U6a’b’d’e, 23,000 BCE, 25,000 YA Late Stone Age, shows some admixture with European Hunter-Gatherers, possibly back and forth from Sicily
Guanche 12 625 CE Tenerife, Spain (Canary Islands), Guanche, Medieval U6b1a1’6’8’9, 1 BCE,

2100 YA

U6a’b’d’e, 23,000 BCE, 25,000 YA Guanche arrived in the Canaries in 1st millennium BCE, related to Berbers
Guanche 14 775 CE Tenerife, Spain (Canary Islands), Guanche, Medieval U6b1a1’6’8’9, 1 BCE,

2100 YA

U6a’b’d’e, 23,000 BCE, 25,000 YA Ditto above
Antocojo 27 875 CE Antocojo, La Gomera, Spain (Canary Islands) U6b1a1’6’8’9, 1 BCE,

2100 YA

U6a’b’d’e, 23,000 BCE, 25,000 YA Ditto above
Guanche 13 900 CE Cave, Tenerife, Spain (Canary Islands), Medieval U6b1a1’6’8’9, 1 BCE,

2100 YA

U6a’b’d’e, 23,000 BCE, 25,000 YA Ditto above
Guanche 1 1090 CE Cave, Tenerife, Spain (Canary Islands), Medieval U6b1a1’6’8’9, 1 BCE,

2100 YA

U6a’b’d’e, 23,000 BCE, 25,000 YA Ditto above
Barranco Majona 30 1325 CE Barranco Majona, La Gomera, Spain (Canary Islands), Guanche late Medieval U6b1a1’6’8’9, 1 BCE,

2100 YA

U6a’b’d’e, 23,000 BCE, 25,000 YA Ditto above
Kostenki 14 36,000 BCE Markina Gora, Kostyonki, Voronezh Oblast, Russia U2,

43,000 BCE, 45,000 YA

 

U,

43,000 BCE, 45,000 YA

European/Asian steppe earliest hunter-gatherers. Farming didn’t arrive until 10 KYA. Admixture from Asia as well.
Kostenki 12 31,000 BCE Volkovskaya, Voronezh region, Russian Federation. U2c’e,

43,000 BCE, 45,000 YA

 

U,

43,000 BCE, 45,000 YA

Early hunter-gatherer
Krems 3 29,000 BCE Wachtberg in Krems, Lower Austria, Austria, Gravettian culture U5,

32,000 BCE,

34,000 YA

U,

43,000 BCE, 45,000 YA

Endured the ice age, sophisticated toolmaking, Venus figures, mobile lifestyle, mammoth hunters
Krems Twin 1 28,800 BCE Left bank of the Danube, Krems-Wachtberg, Austria, Gravettian culture U5,

32,000 BCE,

34,000 YA

U,

43,000 BCE, 45,000 YA

Double grave for twins, 1 newborn, one age about 50 days
Krems Twin 2 28,800 BCE Left bank of the Danube, Krems-Wachtberg, Austria, Gravettian culture U5,

32,000 BCE,

34,000 YA

U,

43,000 BCE, 45,000 YA

Ditto above
Vestonice 13 28,900 BCE Pavlovské Hills, South Moravia, Czech Republic, Grevettian culture U8b^,

37,000 BCE, 39,000 YA

 

U,

43,000 BCE, 45,000 YA

Ice Age Europe, few samples before farming introduced. Believe these Gravettian individuals are from a single founder population before being displaced across a wide European region.
Vestonice 14 28,900 BCE Dolni Vestonice, Brezi, Czech Republic, Gravettian culture U5,

32,000 BCE,

34,000 YA

U,

43,000 BCE, 45,000 YA

Ditto above
Vestonice 16 28,900 BCE Dolni Vestonice, Brezi, Czech Republic, Gravettian culture U5,

32,000 BCE,

34,000 YA

U,

43,000 BCE, 45,000 YA

Ditto above
Grotta delle Mura child 15,100 BCE Grotta delle Mura, Bari, Italy, Paleolithic Italian culture U2”10,

43,000 BCE, 45,000 YA

U,

43,000 BCE, 45,000 YA

This baby, interred in a small shoreline cave, was less than 9 months old and had blue eyes
Goyette Q2 13,100 BCE Troisième Caverne, Goyet, Belgium, Magdaleian culture named after the La Madeleine rock shelter in France U8a,

10,000 BCE,

12,000 YA

 

U,

43,000 BCE, 45,000 YA

These hunter-gatherer people may have been responsible for the repopulation of Northern Europe. Cave art, such as that at Altamira, in Northern Spain is attributed to the Magdalenian culture.
Villabruna 1 12,000 BCE Villabruna, Italy, Paleolithic culture U5b2b,

9700 BCE,

11,700 YA

 

U,

43,000 BCE, 45,000 YA

Rock shelter in northern Italy where this man was buried with grave goods typical of a hunter and covered in painted stones with drawings. The walls were painted in red ochre.
Oberkasel 998 12,000 BCE Oberkassel , Bonn, Germany, Western Hunter-Gatherer culture U5b1 U,

43,000 BCE, 45,000 YA

Double burial found in a quarry with 2 domesticated dogs and grave goods. Genis classification was uncertain initially as they were deemed, “close to Neanderthals.”

Creating a chart serves multiple functions.

  1. First, it allows you to track connections methodically. As more become available, older ones fall off the list, but not off your chart.
  2. Second, it allows you to analyze the results more carefully.
  3. Third, it “encourages” you to spend enough time with these ancient humans to understand and absorb information about their lives, travels, and migrations – all of which relate in some way to your ancestors.

When creating this chart, I looked up every shared haplogroup to determine their location and what could be discerned about each one, because their story is the history of the LeJeune sisters, and my history too.

Ok, so I can’t help myself for a minute here. Bear with me while we go on a little Ancient Connections tour. After all, history dovetails with genetics.

How cool is it that the LeJeune sisters’ ancestor, around 20,000 years ago, who lived someplace in the Nile Delta, gave birth to the next 1000 (or so) generations?

Of course, the Great Pyramids weren’t there yet. They were built abotu 4600 years ago.

Those women gave birth to two women about 2200 years ago whose mummified remains were found in the Pyramids at Giza. The associated paper described Egypt in this timeframe as a cultural crossroads which both suffered and benefitted from foreign trade, conquest and immigration from both the Greeks and Romans.

You can read more about burials from this timeframe in The Beautiful Burial in Roman Egypt, here. A crossroads is not exactly what I was expecting, but reading the papers is critically important in understanding the context of the remains. This book is but one of 70 references provided in the paper.

Some burials have already been excavated, and work continues in the expansive pyramid complex.

The Egyptian sun is unforgiving, but Giza eventually gives up her secrets. Will more distant cousins of the LeJeune sisters be discovered as burial chambers continue to be excavated?

We know little about the lives of the women interred at Giza, but the life of another Ancient Connection, Amina, strikes chords much closer to home.

Amina, an enslaved woman, is another descendant of that woman who lived 20,000 years ago. She too is related to the Giza mummies.

Amina was discovered in a previously unknown burial ground in downtown Charleston, SC, that held the remains of enslaved people who had been brought, shackled, from Africa to be sold. Amina’s remains convey her story – that she was kidnapped, forced into the Middle Passage, and miraculously survived. She succumbed around 1725 in Charleston, SC, near the wharf, probably where her prison ship docked.

Charleston was a seaport where more than a quarter million enslaved people disembarked at Gadsden’s Wharf, awaiting their fate on the auction block. The location where Amina’s burial was found is only about 1000 feet from the wharf and is now, appropriately, considered sacred ground. Ohhh, how I’d like to share this information with Amina.

A hundred years earlier, a different ancestor of that women who lived 20,000 years ago gave birth to the mother of the LeJeune sisters, someplace in France.

Moving further back in time, another distant cousin was unearthed at the Kostyonki–Borshchyovo archaeological complex near the Don River in Russia.

Photographed by Andreas Franzkowiak (User:Bullenwächter) – Archäologisches Museum Hamburg und Stadtmuseum Harburg, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=58260865

Markina Gora is an incredibly famous location yielding both specimens included here, as well as this famous Venus figurine from the Gravettian culture, dating from about 27,000 years ago.

Bust of Kostenki 14 reconstructed from the burial.

The earliest of these hunter-gatherers in Europe, believed to be a small group of humans, interbred with Neanderthals. Kostenki 14 carried Neanderthal introgression dating back to about 54,000 years ago.

A layer of volcanic ash, thought to be from a volcano near Naples that erupted about 39,000 years ago, is found above the remains, speaking to events that our ancestors survived after this man lived.

I know we’ve traveled far back in history from the LeJeune sisters, but these ancient humans, the MRCA of each upstream haplogroup, are our ancestors, too.

What does all this mean?

At first glance, it’s easy to assume that all of the locations are relevant to our direct ancestors. Not only that, many people assume that all of these people ARE our ancestors. They aren’t.

Creating the Ancient Conenctions Chart should help you gain perspective about how these people are related to you, your ancestors, and each other.

Each individual person is connected to you and your ancestors in various ways – and their stories weave into yours.

Discover provides everyone has a mini-Timeline for each Ancient Connection. It’s easy to see that the tester, who tested in the modern era, since the year 1950, is not descended from El Agujaro 8, who lived in the 1300s and whose common (shared) haplogroup with the tester, U6a7a1, was born between 2100 BCE and 900 BCE, or between 4100 and 2900 years ago. The most probable date is about 3450 years ago.

The Timeline for each ancient sample includes:

  1. Your haplogroup’s mean birth year
  2. Ancient Connection’s birth year
  3. Ancient Connection’s haplogroup mean birth year, if different from the common haplogroup (in the example above, 3 and 4 are the same)
  4. Birth year of your common ancestor (MRCA), which is your common haplogroup

It’s easy to see the relevant information for each sample, but it’s not easy to visualize the trees together, so I’m creating a “rough” tree in Excel to help visualize the “big picture”, meaning all of the Ancient Connections.

How Do I Know Which Ancient Connections Even MIGHT Be My Ancestors and How We Are All Related?

That’s a great question and is exactly why I created this chart in an ancient haplogroup spreadsheet.

Click on any image to enlarge

In this chart, you can see the LeJeune sisters, in red, at the bottom, and their direct line hereditary haplogroups, in purple, descending from haplogroup U at the top.

Branching to the left and right from intersections with their purple hereditary haplogroups are other branches that the LeJeune sisters don’t share directly. However, the ancient remains that carry those haplogroups are “haplocousins” at a distant point in time, with our LeJeune sisters.

There only two burials that carry the same ancestral haplogroup as the LeJeune sisters:

  1. El Agujero 8, haplogroup U6a7a1 who lived in the Canary Islands in the year 1275
  2. Djebba 20825, who lived in Tunisia about 6,100 years ago

Clearly, Djebba, with a common haplogroup that lived about 21,000 years ago cannot be the ancestor of the LeJeune sisters, but they share a common ancestor. If Djebba was an ancestor of the LeJeune sisters, then Djebba would also descend from haplogroup U6a7, born about 20,600 years ago, like the LeJeune sisters do.

A cursory glance might suggest that since the sample, El Agujero 8 lived in the Canary Islands about 1275, haplogroup U6a7a1 was born there. However, if you read the papers associated with all of the samples found in the Canaries, Tunisia, Spain and other locations, you’ll discover that these populations moved back and forth across the Mediterranean. You’ll also discover that the earliest European haplogroup U samples found in Europe are believed to be the founders of haplogroup U in Europe. It’s possible that U6 dispersed into Italy and Spain, regions with significant exchange with North Africa.

It’s extremely unlikely that El Agujero 8, who lived about the year 1275 CE, was the ancestor of the LeJeune sisters, but it’s not entirely impossible. What’s more likely is that they descended from a common population that moved between Spain, the Canaries, and North Africa where other similar burials are found, like Tunisia. We know that Rome largely conquered France during the Gallic Wars (56-50 BCE), so it’s not terribly surprising that we find haplogroup U6a7a1 and descendants scattered throughout Europe, the Iberian peninsula, the Roman empire, and North Africa.

Sometime between the birth of haplogroup U6a7a1, about 3450 years ago, the descendants of that woman found their way both to France before the 1600s and also to the Canaries before 1275.

Takeaways from Ancient Connections

  • I recommend that you read the associated academic papers and publications that provide the Ancient Connections mitochondrial haplogroups. Those publications are chock full of important cultural information.
  • Globetrekker, which won’t be released until some time after the next release of the Mitotree, will help with tracking the path of your ancestors, especially where it’s complex and uncertain.
  • The “haplosisters” and “haplocousins” of the French LeJeune sisters are quite diverse, including Egyptian pyramid burials in Giza, a Muslim necropolis burial in Spain, a Viking in Sweden, indigenous Canary Islanders, a Tunisian site on the Northern-most tip of Africa, a Jewish burial in England, an enslaved woman in South Carolina, the Markina Gora site in Russia, caves in Austria, the Czech Republic, Belgium, Germany and Italy.
  • Ancient Connections are more than just interesting. On another genealogical line, I found a necropolis burial with my ancestor’s haplogroup located about 9 km from where my ancestor is believed to have lived, dating from just a few hundred years earlier.
  • FamilyTreeDNA adds more Ancient Connections weekly.

Resources

Notable Connections

Notable Connections are similar to Ancient Connections, except they are generally based on modern-day or relatively contemporary testers and associated genealogy. Some samples are included in both categories.

Three Notable Connections are included with the public version of Discover, and additional Notable Connections are provided, when available, for testers who click through from their account.

Some Notable Connections may be close enough in time to be useful for genealogy based on their haplogroup, their haplogroup history, and the tester’s history as well.

In this case, the closest two Notable Connections are both included in Ancient Connections, so we know that the rest won’t be closer in time.

The common ancestor, meaning common haplogroup, of Cheddar Man and the rest, reaches all the way back to haplogroup U, born about 45,000 years ago, so these particular Notable Connections can be considered “fun facts.”

However, if the first (closest) notable connection was a famous person who lived in France in the 1600s, and was the same or a close haplogroup, that could be VERY beneficial information.

Takeaways from Notable Connections

  • Mostly, Notable Connections are just for fun – a way to meet your haplocousins.
  • Notable Connections are a nice way to emphasize that we are all connected – it’s only a matter of how far back in time.
  • That said, based on the haplogroup, location and date, you may find Notable Connections that hold hints relevant to your ancestry.

Scientific Details

Scientific Details includes two pages: Age Estimates and Variants.

Scientific Details Age Estimates

Haplogroup ages are calculated using a molecular clock that estimates when the mutation defining a particular haplogroup first arose in a woman.

Since we can’t go back in time, test everyone, and count every single generation between then and now – scientists have to reconstruct the phylogenetic tree.

The more people who test, the more actual samples available to use to construct and refine the Mitotree.

The “mean” is the date calculated as the most likely haplogroup formation date.

The next most likely haplogroup formation range is the 68% band. As you can see, it’s closest to the center.

The 95% and 99% likelihood bands are most distant.

I know that 99% sounds “better” than 68%, but in this case, it isn’t. In fact, it’s just the opposite – 99% takes in the widest range, so it includes nearly all possibile dates, but the center of the range is the location most likely to be accurate.

The full certainty range is the entire 100% range, but is extremely broad. The mean is  the date I normally use, UNLESS WE ARE DEALING WITH CONTEMPORARY DATES.

For example, if the LeJeune sisters’ haplogroup was formed in 1550 CE at the mean, I’d be looking at the entire range. Do their approximate birth years of 1624 and 1633 fall into the 68% range, or the 95% range, and what are the years that define those ranges?

Scientific Details Variants

Next, click on the Variants tab.

To view your haplotype cluster, the F#, and your private variants, slide “Show private variants” at upper right above the black bar to “on.” This feature is only available for testers who sign in and click through to mtDNA Discover from their page.

The Variants tab provides lots of information, beginning with a summary of your:

  • Haplotype cluster F number, which I’ve blurred
  • Private variants, if any
  • End-of-branch haplogroup information

The most granular information is shown first.

Your haplotype cluster number is listed along with any private variants available to form a new haplogroup. In this case, there are no private variants for these haplotype cluster members. Every cluster is different.

Just beneath that, listed individually, are the variants, aka SNPs, aka mutations that identify each haplogroup. The haplogroup with the red square is yours.

Everyone in this haplogroup shares these two mutations: A2672G and T11929C. Because two variants define this haplogroup, it’s possible that one day it will split if future testers have one but not the other variant.

Information in the following columns provides details about each mutation. For example, the first mutation shown for haplogroup U6a7a1a is a transition type SNP mutation in the coding region, meaning it’s only reported in the full sequence test, where the A (Adenine) nucleotide, which is ancestral, mutated to a G (Guanine) nucleotide which is derived. This is essentially before (reference) and after (derived).

If you mouse over the Weight column, you’ll see a brief explanation of how each mutation is ranked. Essentially, rarer mutation types and locations are given more weight than common or less stable mutation types and/or locations.

Mutations with orange and red colors are less stable than green mutations.

Following this list from top to bottom essentially moves you back in time from the most recently born haplogroup, yours, to haplogroup L1”7, the first haplogroup in this line to branch from Mitochondrial Eve, our common ancestor who lived about 143,000 years ago in Africa.

View More

Clicking on the “View More” dropdown exposes additional information about the various types of mutations and Filtered Variants. Filtered Variants, in the current version of the Mitotree, are locations combined with specific mutation types that are excluded from branch formation.

Please note that this list may change from time to time as the tree is updated.

Takeaways from Scientific Details

  • Based on the Age Estimate for haplogroup U6a7a1a, it’s most likely to have formed about the year 29, but could have formed anytime between about 186 BCE and 230 CE. While this range may not be terribly relevant for older haplogroups, ranges are very important for haplogroups formed in a genealogical era.
  • People who are members of this example haplotype cluster do not have any private variants, so they are not candidates to receive a new haplogroup unless the upstream tree structure itself changes, which is always possible.
  • A significant amount of additional scientific information is available on these two tabs.
  • A list of locations currently excluded from haplogroup formation is displayed by clicking on the “View more” dropdown, along with information about various types of mutations. This list will probably change from time to time as the tree is refined.

Compare

Compare is a feature that allows you to compare two haplogroups side by side.

Let’s say we have an additional woman named LeJeune in Acadia, aside from Catherine and Edmee. As it happens, we do, and for a very long time, assumptions were made that these three women were all sisters.

Jeanne LeJeune dit Briard was born about 1659 and died after 1708. She is the daughter of unknown parents, but her father is purported to be Pierre LeJeune born about 1656, but there’s no conclusive evidence about any of that.

Jeanne LeJeune dit Briard married twice, first to Francois Joseph. Their daughter, Catherine Joseph’s marriage record in 1720 lists Jeanne, Catherine’s mother, as “of the Indian Nation.”

Several direct matrilineal descendants of Jeanne LeJeune dit Briard have joined the Acadian AmerIndian DNA Project, revealing her new Mitotree haplogroup as haplogroup A2f1a4+12092, which is Native American.

If Jeanne LeJeune dit Briard born about 1659, and Edmee and Catherine LeJeune, born about 1624 and 1633, respectively, are full or matrilineal half-siblings, their mitochondrial DNA haplogroups would match, or very closely if a new branch had formed in a descendant since they lived.

Let’s use the Compare feature to see if these two haplogroups are even remotely close to each other.

Click on “Compare.”

The first haplogroup is the one you’re searching from, and you’ll choose the one to compare to.

Click on “Search a haplogroup” and either select or type a haplogroup.

The two haplogroups are shown in the little pedigree chart. The origin dates of both haplogroups are shown, with their common shared ancestor (MRCA) positioned at the top. The most recent common, or shared, ancestor between Jeanne LeJeune dit Briard, who was “of the Indian Nation” and Catherine and Edmee LeJeune is haplogroup N+8701, a woman born about 53,000 years ago.

There is absolutely NO QUESTION that these three women DO NOT share the same mother.

Jeanne LeJeune dit Briard is matrilineally Native, and sisters Caterine and Edmee LeJeune are matrilineally European.

Takeaways from Compare

  • The MRCA between Jeanne LeJeune dit Briard and sisters, Edmee and Catherine LeJeune is about 53,000 years ago.
  • Jeanne was clearly not their full or maternal sister.
  • Compare provides an easy way to compare two haplogroups.

Suggested Projects

Projects at FamilyTreeDNA are run by volunteer project administrators. Some projects are publicly viewable, and some are not. Some project results pages are only visible to project members or are completely private, based on settings selected by the administrator.

When testers join projects, they can elect to include or exclude their results from the public project display pages, along with other options.

The “Suggested Projects” report in Discover provides a compilation of projects that others with the haplogroup you’re viewing have joined. Keep in mind that they might NOT have joined due to their mitochondrial DNA. They may have joined because of other genealogical lines.

While these projects aren’t actually “suggested”, per se, for you to join, they may be quite relevant. Viewing projects that other people with this haplogroup have joined can sometimes provide clues about the history of the haplogroup, or their ancestors, and therefore, your ancestors’ journey.

Remember, you (probably) won’t match everyone in your haplogroup on your matches page, or the Match Time Tree, so projects are another avenue to view information about the ancestors and locations of other people in this haplogroup. The projects themselves may provide clues. The haplogroup projects will be relevant to either your haplogroup, or a partial upstream haplogroup.

The haplogroup U6 project includes multiple U6 daughter haplogroups, not just U6a7a1a, and includes testers whose ancestors are from many locations.

The U6 project has labeled one group of 38 members the “Acadian cluster.” Of course, we find many descendants of Catherine and Edmee LeJeune here, along with testers who list their earliest known ancestor (EKA) as a non-Acadian woman from a different location.

The ancestors of Martha Hughes, who lived in Lynn, Massachusetts, and Mary Grant from Bathhurst, New Brunswick may well be descendants of Edmee or Catherine.

Or, perhaps they are a descendant of another person who might be a connection back to France. If you’re the Hughes or Grant tester, you may just have tested your way through a brick wall – and found your way to your LeJeune ancestors. If you’re a LeJeune descendant, you might have found a link through one of those women to France. Clearly, in either case, additional research is warranted.

For descendants of Catherine and Edmee, you’re looking for other testers, probably from France, whose ancestors are unknown or different from Edmee and Catherine. That doesn’t mean their genealogy is accurate, but it does merit investigation.

Check to see if someone with that EKA is on your match list, then check their tree.

For Catherine and Edmee LeJeune, other than Martha and Mary, above, there was only one EKA name of interest – a name of royalty born in 1606. However, research on Marie Bourbon shows that she was not the mother of the LeJeune sisters, so that tester is either incorrect, or confused about what was supposed to be entered in the EKA field – the earliest known direct matrilineal ancestor.

You may also find people in these projects who share your ancestor, but have not upgraded to the full sequence test. They will have a shorter version of the haplogroup – in this case, just U6a. If they are on your match list and their results are important to your research, you can reach out to them and ask if they will upgrade.

If you’re working on an ancestor whose mitochondrial DNA you don’t carry, you can contact the project administrator and ask them to contact that person, offering an upgrade.

Takeaways from Suggested Projects

  • Suggested Projects is a compilation of projects that other people with this haplogroup have joined. Haplogroup-specific projects will be relevant, but others may or may not be.
  • Testers may have joined other projects based on different lineages that are not related to their mitochondrial line.

We’re finished reviewing the 12 Discover reports, but we aren’t finished yet with the LeJeune analysis.

Another wonderful feature offered by FamilyTreeDNA is Advanced Matching, which allows you to search using combinations of tests and criteria. You’ll find Advanced Matching on your dashboard.

Advanced Matching

Advanced Matching, found under “Additional Tests and Tools,” is a matching tool for mitochondrial DNA and other tests that is often overlooked.

You select any combination of tests to view people who match you on ALL of the combined tests or criteria.

Be sure to select “yes” for “show only people I match in all selected tests,” which means BOTH tests. Let’s say you match 10 people on both the mitochondrial DNA and Family Finder tests. By selecting “Yes,” you’ll see only those 10 people. Otherwise you’ll get the list of everyone who matches you on both tests individually. If you have 100 mitochondrial matches, and 2000 autosomal matches, you’ll see all 2100 people – which is not at all what you want. You wanted ONLY the people who match you on both tests – so be sure to select “yes.”

The combination of the FMS, full sequence test, plus Family Finder displays just the people you match on both tests – but keep in mind that it’s certainly possible that you match those people because of different ancestors. This does NOT mean you match on both tests thanks to the LeJeune sisters. You could match another tester because of a different Acadian, or other, ancestor.

This is especially true in endogamous populations, or groups, like the Acadians, with a significant degree of pedigree collapse.

Advanced Matching Tip

You can also select to match within specific projects. This may be especially useful for people who don’t carry the mitochondrial DNA of the LeJeune sisters, but descend from them.

Switching to my own test, I’ve selected Family Finder, and the Acadian AmerIndian Project, which means I’ll see everyone who matches me on the Family Finder test AND is a member of that project.

Given that I’ve already identified the haplogroup of Catherine LeJeune, I can use known haplogroups to filter autosomal matches, especially in focused projects such as the Acadian AmerIndian Project. This helps immensely to identify at least one way you’re related to other testers.

By clicking on the match’s name, I can see their EKA information. By clicking on their trees, I can verify the ancestral line of descent.

Of course, in Acadian genealogy, I’m probably related to these cousins through more than one ancestor, but using Advanced Matching, then sorting by haplogroup is a great way to identify at least one common ancestor!

Takeaways from Advanced Matching

  • Advanced Matching is a wonderful tool, but make sure you’re using it correctly. Click “Yes” to “Show only people I match in all selected tests.” Please note that if you select all three levels of mtDNA test, and you don’t match at the HVR1 level due to a mutation, that person won’t be shown as a match because you don’t match them on all test levels selected. I only select “FMS” and then my second test.
  • You may match someone on either Y-DNA or mitochondrial DNA and the autosomal Family Finder through different ancestral lines.
  • Advanced Matching is a great way to see who you match within a project of specific interest – like the Acadian AmerIndian Project for the LeJeune sisters.
  • You will match people outside of projects, so don’t limit your analysis.

Drum Roll – LeJeune Analysis

It’s finally time to wrap up our analysis.

The original questions we wanted to answer were:

  • Were Edmee and Catherine LeJeune actually sisters?
  • Was their mother Native American?
  • Was the third woman, Jeanne LeJeune dit Briard, also their sister?
  • Are there any other surprises we need to know about?

We now have answers, so let’s review our evidence.

  • Based on the haplogroup of Edmee and Catherine LeJeune both, U6a7a1a, which is clearly NOT of Native American origin, we can conclude that they are NOT Native American through their matrilineal side.
  • Native American haplogroups are subsets of five base haplogroups, and U is not one of them.

There’s other information to be gleaned as well.

  • Based on the haplogroup of Jeanne LeJeune dit Briard, A2f1a4+12092, plus her daughter’s marriage record, we can conclude that (at least) her mother was Native American.
  • Based on Jeanne’s Native American haplogroup alone, we can conclude that she is not the full sister of the Catherine and Edmee LeJeune.
  • Based on Jeanne’s birth date, about 1659, it’s clear that she cannot be the full sibling of Catherine born about 1633, and Edmee LeJeune, born about 1624, and was probably a generation too late to be their paternal half sister. Later lack of dispensations also suggests that they were not half-siblings.
  • Based on the known Acadian history, confirmed by contemporaneous records, we can state conclusively that Edmee LeJeune was born in France and Catherine probably was as well. The first Acadian settlement did not occur until 1632, and the first known families arrived in 1636.
  • Based on the fact that Catherine and Edmee’s haplogroups match, and many of their descendants’ mitochondrial DNA matches exactly, combined with later dispensations, we can conclude that Catherine and Edmee were sisters.
  • We can conclusively determine that Catherine and Edmee were NOT Native on their matrilineal side, and given that they were born in France, their father would have been European as well. However, we cannot determine whether their descendants married someone who was either Native or partially Native.
  • We know that information for partial haplogroup U6a, provided for HVR1 and HVR1+HVR2-only testers is not necessarily relevant for full sequence haplogroup U6a7a1a.
  • The recent Mitotree release has moved the haplogroup “dates” for the LeJeune sisters from about 21,000 years ago for HVR1/HVR2 U6a testers to 50 CE for full sequence testers,. These dates may well be refined in future tree releases.
  • Having multiple testers has provided us with an avenue to garner a massive amount of information about the LeJeune sisters, in spite of the fact that their haplogroup was born about 50 CE.
  • The LeJeune sisters are related to, but not descended from many very interesting Ancient Connections. Using our Ancient Connections spreadsheet, we can rule out all but one Ancient Connection as being a direct ancestor of the LeJeune sisters, but they are all “haplocousins,” and share common ancestors with the sisters.
  • While we cannot rule out the genetically closest Ancient Connection, El Agujero 8, who lived about 1275 CE in the Canary Islands as their direct ancestor, it’s very unlikely. It’s more probable that they share a common ancestor in haplogroup U6a7a1 who lived about 3450 years ago, whose descendants spread both into France by the 1600s and the Canary Islands by the 1200s.

By now, you’re probably thinking to yourself that you know more about my ancestors than your own. The good news is that mitochodnrial DNA testing and mtDNA Discover is available for everyone – so you can learn as much or more about your own ancestors.

Spread Encouragement – Be a Positive Nellie!

Unfortunately, sometimes people are discouraged from mitochondrial DNA testing because they are told that mitochondrial haplogroups are “too old,” and matches “are too distant.” Remember that the MRCA of any two people, or groups of people is sometime between the haplogroup formation date, and the current generation – and that’s the information we seek for genealogy.

Furthermore, it’s those distant matches, beyond the reach of autosomal matching, that we need to break down many brick walls – especially for female ancstors. I offer testing scholarships for ancestors whose mitochondrial DNA is not yet represented. It’s information I can’t obtain any other way, and I’ve broken through many brick walls!

We don’t know what we don’t know, and we’ll never know unless we take the test.

Imagine how much could be gained and how many brick walls would fall if everyone who has tested their autosomal DNA would also take a mitochondrial DNA test.

Which ancestors mitochodrial DNA do you need? The best place to start is with your own, plus your father’s, which gives you both grandmother’s mtDNA and directly up those lines until you hit that brick wall that needs to fall.

Additional Resources

Roberta’s Books:

_____________________________________________________________

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an e-mail whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the affiliate 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 Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Welcome to the New FamilyTreeDNA® mtDNA Group

If you are a member of the Mitochondrial DNA for Genealogy Facebook group that I started when we launched the Million Mito Project, you may have noticed something new.

Not only does the group have a new name, FamilyTreeDNA® mtDNA Group, and an updated map, but it’s also now the official FamilyTreeDNA mitochondrial DNA group. A company-sponsored group provides one official, moderated, social media platform for mitochondrial DNA discussions and ongoing education.

I’m very pleased to “bequeath” this group to FamilyTreeDNA. It’s the perfect time, too, with the Mitotree release and full sequence testers receiving new haplogroups, along with the mtDNA Discover reports. Have you checked your new haplogroup – and mtDNA Discover?

I’m still an administrator, but I have been joined by several talented people from FamilyTreeDNA, including Million Mito Team members. We’ve assembled the best group possible to educate and answer questions.

You probably know that FamilyTreeDNA has an official Big-Y DNA group as well, here, where people can engage in conversation and education about Big-Y testing and results and how to use them for genealogy. This is the companion mitochondrial DNA group.

This FamilyTreeDNA® mtDNA Group is a private group, but anyone is welcome to join – whether you’ve already tested or are just thinking about it. It’s the “go to” place to learn about mitochondrial DNA.

Everyone can test their own mitochondrial DNA, so take a test, come on over, and join the fun, here.

See you soon!

_____________________________________________________________

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me 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 Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Ancestry’s ThruLines Are a Hot Mess Right Now – But Here Are Some Great Alternatives

Right now, ThruLines at Ancestry is one hot mess.

Aside from the inherent frustration, especially over a holiday weekend when many people had planned to work on their genealogy, I’d like to say, “don’t panic.”

I don’t have any inside information about what’s going on at Ancestry, and I’ve attempted to make contact through their support page with no luck. They make talking to a person exceedingly difficult; plus, it’s a holiday weekend, and they are probably inundated.

Regardless, I have an idea of what is happening. Ancestry has been in the midst of recalculating “things,” perhaps in relation to their other changes, which I’ll write about separately in a few days.

In any event, Ancestry SURELY MUST KNOW there’s a significant problem because I imagine thousands of their customers are screaming right about now. Adding another voice won’t be helpful.

Symptoms

  • You may not have ThruLines at all.
  • If you do have ThruLines, don’t trust the information, or more to the point, don’t trust that it’s in any way complete.

I have two tests at Ancestry, both connected to different trees so that my matches and Thrulines are calculated separately for each test.

Test One

My first Ancestry test is connected to my primary tree. I’ve been amassing Thrulines cousins ever since the feature was released. I have hundreds of cousin matches descended from some of my more prolific ancestors.

Additionally, my sister’s grandchildren have tested, as have other close relatives who have connected their tests to their trees.

Today, those people are still showing on my match list, but are NOT showing as matches in ThruLines. None of them. Most of my ThruLines ancestors are showing zero matches, and the rest are only showing very few. Ancestors who had hundreds before now have 2, for example.

Here’s an example with my cousin, Erik.

My grandfather, William George Estes, shown in Erik’s tree, above, is his great-grandfather. Erik is my half first cousin, once removed, and we share 417 cM over 16 segments.

Yet, looking at my ThruLine for William George Estes, neither he nor my other cousins are shown as matches. Same for William George’s parents, and so forth.

ThruLines is VERY ill right now.

Test Two

My second DNA test at Ancestry is even worse. There are no ThruLines calculated, even though my DNA is tree-attached, and I had ThruLines previously.

I see this message now, and I can’t even begin to tell you how irritating this is – in part because it suggests the problem is my fault. It’s clearly not. My tree hasn’t changed one bit. I’m not alone, either. I’ve seen other people posting this same message.

And yes, if you’re thinking that there is absolutely no excuse for this – you’re right.

However, outrage isn’t good for us and won’t help – so let’s all do something else fun and productive instead.

Productive Genealogy Plans

Here are some productive suggestions.

At MyHeritage:

At FamilyTreeDNA:

  • Build your haplogroup pedigree chart by locating people through different companies descended from each ancestor in your tree through the appropriate line of descent, and see if they have or will take a Y-DNA or mtDNA test.
  • Tests are on sale right now, and there’s no subscription required at FamilyTreeDNA for anything.
  • Check Y-DNA and mtDNA tests to see if there are new matches and if you share a common ancestor.

At 23andMe:

  • Check for new matches and triangulation.
  • Check to see if 23andMe has added any of your new matches to your genetic tree.

Remember, the parental sides are typically accurate, but the exact placement may not be, and 23andMe deals poorly with half-relationships. It’s certainly still worth checking though, because 23andMe does a lot of heavy lifting for you.

DNAPainter

For me, the most productive thing to do this weekend would be to copy the segment information from new matches with whom I can identify common ancestors at FamilyTreeDNA, MyHeritage and 23andMe – the vendors who provide segment data – and paint those segments to DNAPainter.

Not only does DNAPainter allow me to consolidate my match data in one place, DNAPainter provides the ability for me to confirm ancestors through triangulation, and to assign unknown matches to ancestors as well.

As you can see, I’ve successfully assigned about 90% of my segments to an ancestor, meaning I’ve confirmed descent from that ancestor based on my autosomal matches’ descent from that same ancestor – preferably through another child. Will new matches propel me to 91%? I hope so.

What percentage can you or have you been able to assign?

If you need help getting started, or ideas, I’ve written about DNAPainter several times and provided a compiled resource library of those articles, here.

Have fun!!!

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

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 Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Mother’s Day Visitation Two Decades Out

I hope that you are enjoying Mother’s Day, whether you’re the Mom being honored, you’re honoring your mother, or you’re one of the millions who “mother” and love others, one way or another.

I didn’t have time to complete my normal article for today, but I certainly didn’t want to let Mother’s Day pass without acknowledgment.

I didn’t get my article finished because, let’s just say, I’ve been extremely busy with something VERY interesting.

I can’t tell you everything, but I can tell you a little!

Just a couple of days ago, I was able to visit Mom once again in the freezer at FamilyTreeDNA.

Mom’s DNA has been housed there since 2003, when she swabbed for her first DNA test. It’s so hard to believe that was two decades ago. So much has changed.

That stored DNA sample allowed me to upgrade Mom to the Family Finder test in 2012, six years after she passed away.

In 2013, I visited Mom at FamilyTreeDNA in the freezer and realized, as I looked in that little window, that there was more of my mother in that freezer than anywhere else on earth. My DNA is in there too, with her, just sayin’. I won’t be buried beside her in the soil, but I am near her in that freezer every day. Somebody has to keep an eye on her!

In intervening years, FamilyTreeDNA purchased a larger freezer and moved Mom from the earlier location across the room to the larger cryo-preservation cemetery – I mean freezer.

Now, Mom, with a few million of her friends and several thousand of our relatives, is partying it up in there when no one is looking.

Time Capsule

Every time I stare through that window, it’s like peering backward into a time capsule. I wonder, if all the Y-DNA was processed at the Big Y-700 level, how much of the entire Y-DNA phylogenetic tree would we be able to reconstruct?

People often skip testing mitochondrial DNA, passed from mothers to all their children, thinking it won’t be genealogically useful. I assure you, that’s not always the case. Furthermore, if you don’t test, DNA can never be useful. Every single person has mitochondrial DNA, so just imagine how much of the mitochondrial tree would be created if every one of those samples was tested at or upgraded to the full sequence level.

How many dead ends are in that freezer, meaning no living people carry that line anymore? I’m one of those people because I have no grandchildren through my daughter. Mom’s, her mother’s, and my mitochondrial DNA dies with my generation.

Based on my mitochondrial DNA sequence, meaning my mutations, I’ll VERY likely have a new haplogroup when the Million Mito Project rolls out, and even more likely that it will be at least three branches down the tree, closer in time.

What pieces of our human history will be lost if the people in that freezer don’t test their mitochondrial DNA at the full sequence level? The full sequence is needed to construct the mitochondrial tree of all humanity.

How many more matches would we have if everyone in that freezer had a Family Finder test? How many brick walls would fall? How many mysteries would be solved? Would we be able to reconstruct the DNA of our ancestors from their descendants?

What happens if we never open that time capsule, individually and collectively?

“Just Do It”

I had to pinch myself, though. As I stood in that lab, viewing through that window what I considered a sacred and hallowed space for Mom and humanity as well, I was reminded of what Mom said to me not long before she died. In fact, I can hear her frail voice.

“You need to do that.” 

What was “that”?

“That” was transforming her DNA results into a story – her story, her history and genealogy – and how she connected with the story of all humankind. Her “story” revealed her history, our history, even before genealogy, connecting with her soul. She could touch people whose names she would never know, but who contributed their mitochondrial DNA to her. It brought them alive.

I had an entire litany of sensible, level-headed reasons why I could never “do that,” beginning with the fact that I already had a career and owned a business. I had a family, children, and responsibilities – nope – no can do, Mom.

Not to be deterred, Mom gently stopped me in the process of listing all the perfectly logical and valid reasons why that would never work and told me that all of that was just preparing me for what I was “supposed to do,” and I needed to “just do it.” This was nothing like the mother I knew, always conservative in her advice and never wanting me to step out, even a little bit, onto an unstable limb. Let alone leap off the cliff of uncertainty with absolutely no safety net.

What had happened to my mother?

I simply couldn’t make her understand – all those years ago.

Then, my gaze drifts back to the present, and I remember that I’m staring into a freezer, not a time machine. Mom has already had all the tests available today. But many of her frozen neighbors have not.

As I stood, looking into that window, into the past, and perhaps into the future, I was afraid to turn around.

People were standing behind me, filming. I didn’t want anyone to see those tears slipping down my cheeks. After all, I had simply been looking at a window, right? Just a window. Not a cemetery. Not a portal. Not a time machine, no reason for tears – unless you understand the magnitude of what the freezer holds.

I so hoped that those hot tears didn’t entirely ruin my makeup, or that I could at least escape to the restroom to fix it without being noticed.

The Greatest Journey

On the way to the restroom, I saw this framed magazine, a wink and a nod from Mom, I’m sure. Indeed, our DNA is the greatest journey ever told, ever embarked upon, and the story is not yet entirely written. Mom said DNA would change the world as we know it, and she was right.

Mom, I found a way – or maybe fate found me back in 2004. That fateful fork in the road, although I’m not sure I even realized I had slipped onto that road untaken until it was too late to turn back.

Maybe Mom pushed those buttons from the other side, because I’ve been passionately “doing that” one way or another now for almost two decades. And finally, finally, we are going to be able to tell a larger story.

You and me, Mom. Hand in hand with our cousins. All of them – on every continent around the world.

Making history is on the horizon. DNA rocks. Here’s to all the mothers!!!

Thank You

Happy Mother’s Day, Mom. I love and miss you oh so much. And, while I wasn’t at the time, I’m – ahem – so incredibly grateful for the swift kick in the behind called encouragement.

But then, isn’t that the age-old story of motherhood?

Until next time Mom, you behave in there!

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

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 Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

ThruLines Suggests Potential Ancestors – How Accurate Are They?

I wanted to evaluate the accuracy of Ancestry’s ThruLines suggested Potential Ancestors when compared with a tree I know is accurate. I conducted an experiment where I created a small tree on Ancestry for a DNA tester that included only the first two generations, meaning grandparents and great-grandparents.

Click to enlarge any image.

This gave Ancestry enough data to work with and means that for the upstream ancestors, Ancestry’s ThruLines suggested specific people as ancestors.

How well did Ancestry do? Are the Potential Ancestors suggested by Ancestry accurate? How do they make those suggestions anyway? Are they useful?

I do have a second, completely separate, full tree connected to my other DNA test, and I do know who those ancestors are, or, in some cases, I know who they aren’t. I’ve had the privilege of working intensively on my genealogy for decades, so I can easily compare what is known and proven, or what has been disproven, to Ancestry’s suggested Potential Ancestors.

We’ll start with the great-grandparents’ generation, but first, let’s talk about how ThruLines works. I’ve previously written about ThruLines here and here.

How ThruLines Works

ThruLines is a tool for people who have taken an AncestryDNA test and who link themselves to their position on their tree. Linking is a critical step. If you don’t link the DNA test to the proper profile, the tester won’t have ThruLines. I provided step-by-step instructions, here.

I want to emphasize this again, ThruLines is a TOOL, not an answer. It may or may not be accurate and it’s entirely UP TO YOU to take that hint, run with it, and verify or disprove. Ancestry is providing you with a hint.

Essentially, the more ancestors that you provide to Ancestry, generally, the better they can do when suggesting additional Potential Ancestors. They do need something to work with. I wrote about that in the article Optimizing Your Tree at Ancestry for More Hints and DNA ThruLines.

If you don’t provide at least your parents and at least your grandparents in a tree, it’s unlikely that Ancestry will be able to provide Potential Ancestors for you.

I added two generations above the parents in this experiment in order to provide Ancestry with a significant “hook” to latch onto to connect with:

  • Other DNA testers who match the tester AND
  • Other people’s trees, whether the tree-owners have tested their DNA or not

So yes, to be clear, Ancestry DOES:

  • Use the trees of other people whose DNA you match AND have the same ancestors in their tree
  • Along with the trees of people you don’t match (or who haven’t DNA tested,) to propose ancestors for you

ThruLines only reaches back to ancestors within 7 generations, meaning the ancestor is the tester’s 5th great-grandparent or closer.

Most suggested Potential Ancestors in ThruLines have descendants who have tested and are DNA matches to you, but not necessarily all.

On your tree itself, the ThruLines “3 people” icon shows on the ancestors that have Thrulines.

Click to enlarge

Looking at this graphic of my tree, you can see that ThruLines ends at the 7th generation, but Potential Ancestors continue to be suggested beyond 7 generations. Note generation 9, below, which is beyond ThruLines but has Potential Ancestors suggested based entirely on other people’s trees.

ThruLines stops at 7 generations, but Potential Ancestor suggestions do not.

In the above example, in generation 7, Michael McDowell (1720-1755) is a known ancestor and has a ThruLine, but his wife is unknown. Ancestry has suggested a Potential Mother for Michael McDowell (1747-1840) who is also the spouse of Michael McDowell (1720-1755).

Here’s the ThruLines suggestion for Michael McDowell’s wife.

Ironically, there are no DNA matches for either Michael or Eleanor. However, there are DNA matches for their child who clearly descends from Michael. This may be an example of a situation where the other testers are beyond the 7th generation, so they don’t show as matches for our tester in Michael’s generation. The other possibility, of course, is a glitch in ThruLines.

(For those familiar with the Michael McDowell (1720-1755) lineage, Eleanor is his mother, not his wife. His wife is unknown, so this Potential Ancestor is incorrect.)

Potential Ancestors Without DNA Matches

A person may still be suggested as a Potential Ancestor even without any DNA matches.

I have seen situations where a parent has DNA matches to several ThruLine ancestors, but their child has the same suggested ancestor with zero DNA matches listed because the child and the match are one generation too far removed to be listed as a DNA match on ThruLines.

Yet, if you search the child’s match list for the individual listed as a DNA match to their parent through that ancestor, that match is also on the child’s match list.

In the chart that follows, you can see that ancestors in the midrange of generations have many DNA matches, but as you approach the 7th generation, the number of matches drops significantly, and some even have zero. That’s because both people of a match pair have to be within the generational boundary for ThruLines to list them as matches.

In some cases, the ancestor is not suggested for the child in ThruLines because the ancestor is the 6th great-grandparent of the child. If you look directly at the child’s tree, the Potential Ancestor may be suggested there.

Points to Remember

  • The difference between ThruLines and Potential Ancestors is that Potential Ancestors are still suggested beyond the hard 7 generation or 5 GG boundary for ThruLines.
  • ThruLines may suggest Potential Ancestors with or without DNA matches.
  • Potential Ancestors, either within or beyond ThruLines must connect to someone in your tree, or another Potential Ancestor or ancestors who connect to someone in your tree.

Incorrect Ancestors and Discrepancies

An incorrect ancestor can be listed in multiple people’s trees, and Ancestry will suggest that incorrect ancestor for you based on the associated trees. At one point, I did a survey of the number of people who had the incorrect Virginia wife listed for my ancestor, Abraham Estes, and the first 150 trees I viewed had the wrong wife. We have church record proof of her death in England before his children were born by his colonial Virginia wife. Garbage in, garbage out.

That doesn’t mean those trees aren’t useful. In some cases, the information “saved” to that person in those incorrect trees shows you exactly what is out there and can’t be correct. For example, if there is a death record and burial for someone, they can’t also be alive 50 years later in another location. Or someone born in 1780 can’t have been a Revolutionary War veteran. Sometimes you’ll discover same name confusion, or multiple people who have been conflated into one. Other times, you may actually find valid hints for your own ancestor misplaced in someone else’s tree. Always evaluate.

You “should” have the same number of matches to the man and woman of a couple if neither of them had descendants with another partner, but sometimes that doesn’t happen. I would presume that’s due to tree discrepancies among your matches or other trees on Ancestry.

If the same ancestor is listed with multiple name spellings or similar differences, I have no idea how Ancestry determines which version to present to you as a Potential Ancestor. That’s why ThruLines are hints. Ancestry does show you the various trees they utilized and allows you to peruse them for hints for that suggested ancestor.

Just click on the Evaluate button. Unfortunately, neither of these trees have any records for this ancestor.

If you click on the tree, you are then given the opportunity to add Eleanor (meaning the potential ancestor) to your tree from their tree.

I STRONGLY, STRONGLY suggest that you DO NOT do this. By adding information directly from other people’s trees, you’re introducing any errors from their tree into your tree as well.

If you click through to their tree, you’ll often find that they used someone else’s tree as their “source,” so misinformation propagates easily. Seeing “Ancestry Family Trees” as a source, especially in multiple records, provides you with an idea of the research style of that tree owner. This also conveys the message to less-experienced researchers that copy/pasting from other trees is a valid source.

Use this information provided as hints and do your own research and evaluation.

Where Do Potential Ancestors Come From?

Let’s view an example of an incorrect Potential Ancestor suggestion and proof-steps you can utilize to help validate or potentially disprove the suggestion.

We know that George Middleton Clarkston/Clarkson is NOT the father of James Lee Clarkson based on Y-DNA testing where the descendants of the two men not only don’t match, they have a completely different haplogroup. They do not share a common paternal ancestor. Furthermore, proven descendant groups of both men do not have autosomal DNA matches.

However, George Middleton Clarkson is suggested as a Potential Ancestor in ThruLines as the father of James Lee Clarkson.

Mousing over the ThruLines placard shows 98 DNA matches to other people who claim descent from George Middleton Clarkson. How is it possible to have 98 matches with descendants of George Middleton Clarkson, yet he’s not my ancestor?

Many people just see that “98,” which is a high number and think, “well, of course he’s my ancestor, otherwise, I wouldn’t match all those descendants.” It’s not that simple or straightforward though. It’s certainly possible to all be wrong together, especially if you’re dealing with long-held assumptions in the genealogy community and trees copies from other people’s trees for decades.

To view the ThruLine detail for George Middleton Clarkson, just click on the placard.

The ThruLine for George Middleton Clarkson has three attributed children with DNA matches. Let’s evaluate.

  • ThruLines Child 1 is my own James Lee Clarkson that has been erroneously attached to George Middleton Clarkson. However, the Y-DNA of the three various lines, above, does not match. That erroneous connection alone counts for 80 of those 98 matches. If all of those people who match me do descend from our common ancestor, James, those matches all make sense.

According to early histories, James Lee Clarkson was believed to be George’s son based on geographic proximity between the state of Franklin in eastern Tennessee and Russell County, Virginia, but then came DNA testing which said otherwise.

This DNA grouping from the Clarkson/Claxton DNA Project at FamilyTreeDNA shows that the men, above, which includes descendants of James Lee Claxton/Clarkson, all match each other.

  • ThruLines Child 2 is Thomas Clarkston who has 17 DNA matches through 7 of his children.

By clicking on the green evaluate button for Thomas, we see that two of the DNA related trees have records, but three do not.

The first tree is quite interesting for a number of reasons.

  1. Thomas Clarkson is found in Lee County, VA, in relatively close proximity to where James Lee Clarkson is first found in Russell County, VA as an adult in 1795.
  2. There is no actual documentation to connect Thomas Clarkson with George Middleton Clarkson who was hung in 1787 in the lost State of Franklin, Tennessee, now Washington and Greene Counties in Tennessee. It has been “accepted” for years that Thomas descends from George Middleton based on information reportedly passed down within that family long before the internet.

The Claxton/Clarkson DNA Project at FamilyTreeDNA shows the Thomas lineage. This lineage reaches back into England based on Y-DNA matches – a huge and important hint for the Thomas descendants that they won’t be able to obtain anyplace else.

Note that Thomas’s Y-DNA does not match that of James Lee Clarkson/Claxton which means these people must match me through a different line. That’s not surprising given that many of the families of this region intermarried for generations.

  • ThruLines Child 3 is David Claxton, who has one DNA match, so let’s look at that by clicking on the green evaluate button.

You’ll see that this ancestor through David Claxton was recommended based on:

  • One DNA match with a tree with 0 source records, and
  • Zero Ancestry member trees of people whose DNA I don’t match, or that haven’t DNA tested

Checking this tree shows no sources for the following generations either, so I have no way to evaluate the accurace of the tree.

However, I did track his descendants for a generation or so and found them in Wilson County, TN, which allowed me to find them in the Clarkson/Claxton Y DNA Project at FamilyTreeDNA.

In the Clarkson/Claxton DNA project, we see that this David Claxton of Wilson County, TN is in a third DNA group that does not match either the James Lee Claxton or the Thomas Claxton line.

Furthermore, look at the hints for the descendants of David Claxton based on the Y-DNA matches. This link appears to reach back to a Clayton in Kirkington, Yorkshire.

ThruLines Conflation

In this case, three men of similar or the same surnames were cobbled together as sons of George Middleton Clarkson where clearly, based on Y-DNA testing, those three men are not related to each other paternally and do not share a common paternal ancestor. They cannot all three be descendants of George Middleton Clarkson.

It’s amazing how much is missed and erroneously inferred by NOT testing Y-DNA. In very short order, we just proved that the ThruLine that connected all three of these men to George Middleton Clarkson as their ancestor is inaccurate.

In defense of Ancestry, they simply used user-submitted erroneous trees – but you have it within YOUR power to search further, and to utilize Y-DNA or mitochondrial DNA testing for additional clarification. This Clarkson/Claxton information was freely available, publicly, by just checking.

You can find surname or other projects at FamilyTreeDNA, by scrolling down, here, or simply google “<surname you seek> DNA Project.”

How Can These People All Match the Tester?

If we know that the male Claxton/Clarkson line is not the link between these matches, then why and how do these people all DNA match the tester? That’s a great question.

It’s possible that:

  • They match the tester through a different ancestor
  • There has been a genetic disconnect in the Claxton/Clarkson line and the match is through the mother, not the Claxton/Clarkson male
  • Some of the other testers’ genealogy is in error by including George Middleton Clarkson in their trees
  • People accept the George Middleton Clarkson suggestion, adding him to their tree, propagating erroneous information
  • The descendants of James Lee Clarkson/Claxton match because he is their common ancestor, but connecting him to George Middleton Clarkson is erroneous
  • The 15 cM match (and potentially others) is identical by chance
  • The Y-DNA disproved this possibility in this case. In other cases, the matches could have been from the same biological Clarkson/Claxton line, but the testers have their ancestor incorrectly attached to George Middleton Clarkson/Claxton. In this case, we can’t say which of David Claxton, James Lee Claxton and/or Thomas Claxton are or are not individually erroneously connected to George Middleton Clarkson, but we know for a fact that David’s, James’ and Thomas’s descendant’s Y-DNA does not match each other, so they can’t all three be descendants of George Middleton Clarkston. Furthermore, there is no solid evidence that ANY of these three men are his descendant. We know that these three men do not share a common direct paternal ancestor.

I recommend for every male line that you check the relevant Y-DNA project at FamilyTreeDNA and see if the information there confirms or conflicts with a suggested ancestor, or if a descendant hasn’t yet tested. I also STRONGLY recommend that a male in the relevant surname line that carries that surname be asked to test in order to verify the lineage.

ThruLine Ranking

I’m going to rank Ancestry’s suggested Potential Ancestors by awarding points for accuracy on their Potential Ancestor ThruLines suggestions and subtracting points for incorrect Potential Ancestor suggestions. This chart is at the end with links to my 52 Ancestor’s articles for those ancestors.

OK, let’s take a look, beginning with the great-grandparent generation.

Great-Grandparents

I entered all of these ancestors and they are connected to their children, the tester’s grandparents. They are not connected to their parents for purposes of this article, although I do know who the parents are, so let’s see how Ancestry does making Potential Ancestor suggestions through ThruLines.

Ancestors (above example) that are NOT framed by a dotted line and who are NOT labeled as a “Potential Ancestor” have been connected in their tree by the DNA tester, meaning you.

The next generations, below, are all framed by dotted lines, meaning they are Potential Ancestor suggestions provided by Ancestry. Potential Ancestors are always clearly marked with the green bar.

Eight 2nd Great Grandparents

In this generation, because I have not connected them, Ancestry has suggested Potential Ancestors for all sixteen 2X Great-Grandparents.

I’ve provided gold stars for the correct ancestor information meaning both the name and the birth and death date within a year or a decade when they died between census years.

Of these 16, three are completely accurate and the rest were at least partially accurate.

I repeated this process for each one of the suggested Potential Ancestors in the 3rd, 4th and 5th great grandparent categories as well, completing a ranking chart as I went.

Ranking Chart

I’ve ranked Ancestry’s accuracy in their Potential Ancestor recommendations.

  • +2 points means the name AND birth and death years are accurate within a year or decade if they died within a census boundary
  • +1 point means that EITHER the name OR the birth and death dates are (mostly) accurate, but not both
  • 0 means uncertain, so neither positive or negative
  • -1 point means that NEITHER the name NOR birth and death dates are accurate but it’s clear that this is meant to be the correct person. In other words, with some work, this hint could point you in the right direction, but in and of itself, it is inaccurate.
  • -2 means that the person suggested is the wrong person

I’ve been generous where there was some question. I’ve linked these ancestors where I’ve written their 52 Ancestors stories. [LNU] means last name unknown. It’s worth noting that one of the trees Ancestry has available to utilize for Potential Ancestors is my own accurate tree with many source documents for my ancestors.

# Generation Ancestry Name & Birth/Death Years Correct Name & Birth/Death Years # Matches Points Awarded Y or mtDNA Confirmed
1 2nd GGP John R. Estes 1788-1885 John. R. Estes 1787-1885 110 2 Yes
2 2nd GGP Nancy Ann Moore 1789-1865 Ann Moore or Nancy Ann Moore c1785-1860/1870 112 1 Need mtDNA through all females
3 2nd GGP Lazarus Dotson 1785-1861 Lazarus Dodson 1795-1861 46 -1 Yes
4 2nd GGP Elizabeth Campbell 1802-1842 Elizabeth Campbell c 1802-1827/1830 46 1 Yes
5 2nd GGP Elijah R. Vannoy 1782-1850 Elijah Vannoy 1784-1850s 82 -1 Yes
6 2nd GGP Rebecca Lois McNeil 1781-1839 Lois McNiel c1786-c1830s 81 -1 Yes
7 2nd GGP William Crumley ?-1859 William Crumley 1788-1859 97 1 Yes
8 2nd GGP Lydia Brown Crumley 1796-1847 Lydia Brown c1781-1830/1840 112 -1 Yes
9 2nd GGP Henry Bolton 1741-1846 Henry Frederick Bolton 1762-1846 152 -1 Yes
10 2nd GGP Nancy Mann 1777-1841 Nancy Mann c1780-1841 134 1 Yes
11 2nd GGP William Herrel 1803-1859 William Harrell/Herrell c1790-1859 31 1 Yes
12 2nd GGP Mary McDowell 1785-1871 Mary McDowell 1785-after 1872 45 2 Yes
13 2nd GGP Fairwick Clarkson 1800-1874 Fairwix/Fairwick Clarkson/Claxton 1799/1800-1874 82 2 Yes
14 2nd GGP Agnes Sander Muncy 1803-1880 Agnes Muncy 1803-after 1880 106 1 Yes
15 2nd GGP Thomas Charles Speak 1805-1843 Charles Speak 1804/1805-1840/1850 60 1 Yes
16 2nd GGP Ann McKee 1805-1860 Ann McKee 1804/1805-1840/1850 60 1 Yes
17 3rd GGP George M. Estes 1763-1859 George Estes 1763-1859 76 1 Yes
18 3rd GGP Mary C. Younger 1766-1850 Mary Younger c1766-1820/1830 75 -1 Yes
19 3rd GGP William Moore 1756-1810 William Moore 1750-1826 72 1 Yes
20 3rd GGP Susannah Harwell 1748-1795 Lucy [LNU] 1754-1832 69 -2 Need Lucy’s mtDNA through all females
21 3rd GGP Lazarous Dotson 1760-1826 Lazarus Dodson 1760-1826 42 1 Yes
22 3rd GGP Janet Jane Campbell 1762-1826 Jane [LNU] c1760-1830/1840 38 -2 Need mtDNA through all females
23 3rd GGP John Campbell 1772-1836 John Campbell c1772-1838 65 1 Yes
24 3rd GGP Jane Dobkins 1780-1860 Jane Dobkins c1780-c1860 22 2 Yes
25 3rd GGP Francis Vanoy/Vannoy 1746-1822 Daniel Vannoy 1752-after 1794 76 -2 Yes
26 3rd GGP Millicent “Millie” Henderson 1755-1822 Sarah Hickerson 1752/1760-before 1820 76 -2 Need mtDNA through all females
27 3rd GGP William McNeil/McNeal 1760-1830 William McNiel c1760-c1817 116 1 Yes
28 3rd GGP Elizabeth Shepherd McNeil 1766-1820 Elizabeth Shepherd 1766-1830/1840 115 -1 Yes
29 3rd GGP William Crumley 1767-1837 William Crumley c1767-c1839 59 1 Yes
30 3rd GGP Hannah Hanner “Hammer” 1770-1814 unknown 60 -2 Have her mtDNA
31 3rd GGP Jotham Sylvanis Brown 1765-1859 Jotham Brown c1740-c1799 100 -2 Yes
32 3rd GGP Ruth Johnston Brown Phoebe Cole 1747-1802 97 -2 Incorrect person but have correct mtDNA
33 3rd GGP Henry Bolton 1720-1757 Henry Bolton 1729-1765 88 1 Yes
34 3rd GGP Sarah Corry 1729-1797 Sarah Corry 1729-1797 80 2 Need mtDNA through all females
35 3rd GGP Robert James Mann 1753-1801 James Mann 1745-? 77 -1 Need Y-DNA
36 3rd GGP Mary Jane Wilson 1760-1801 Mary Brittain Cantrell c1755-? 80 -2 Incorrect but have correct mtDNA
37 3rd GGP John Herrell 1761-1829 John Harrold c1750-1825 19 -1 Yes
38 3rd GGP Hallie Mary [LNU] c1750-1826 18 -2 Need mtDNA through all females
39 3rd GGP Michael McDowell-McDaniel 1737-1834 Michael McDowell c17471840 25 -2 Yes
40 3rd GGP Sarah Isabel “Liza” Hall Isabel [LNU] c1753-1840/1850 27 -2 Need mtDNA through all females
41 3rd GGP James Lee Clarkson 1775-1815 James Lee Clarkson c1775-1815 170 2 Yes
42 3rd GGP Sarah Helloms Cook 1775-1863 Sarah Cook 1775-1863 188 1 Yes
43 3rd GGP Samuel Munsey-Muncy 1767-1830 Samuel Muncy after 1755-before 1820 108 1 Yes
44 3rd GGP Anne W. Workman 1768-1830 Anne Nancy Workman 1760/1761-after 1860 107 -1 Yes
45 3rd GGP Rev. Nicholas Speak 1782-1852 Nicholas Speak/Speaks 1782-1852 93 2 Yes
46 3rd GGP Sarah Faires Speak 1782-1865 Sarah Faires 1786-1865 93 -1 Yes
47 3rd GGP Andrew McKee 1760-1814 Andrew McKee c1760-1814 86 2 Yes
48 3rd GGP Elizabeth 1765-1839 Elizabeth [LNU] c1767-1838 88 2 Yes
49 4th GGP Moses Estes 1742-1815 Moses Estes c1742-1813 27 1 Yes
50 4th GGP Luremia Susannah Combes 1747-1815 Luremia Combs c1740-c1820 33 -1 Need mtDNA through all females
51 4th GGP Marcus Younger 1735-1816 Marcus Younger 1730/1740-1816 30 2 Yes
52 4th GGP Susanna Hart* 1725-1806 Susanna [possibly] Hart c1740-before 1805 26 -1 Yes
53 4th GGP William Moore 1725-1757 James Moore c1718-c1798 25 -2 Yes
54 4th GGP Margaret Hudspeth 1725-1808 Mary Rice c1723-c1778/1781 26 -2 Need Mary Rice mtDNA through all females
55 4th GGP Samuel “Little Sam” Harwell 1716-1793 Incorrect 36 -2
56 4th GGP Abigail Anne Jackson 1712-1793 Incorrect 33 -2
57 4th GGP Rawleigh “Rolly” Dodson 1730-1793 Raleigh Dodson 1730-c1794 19 2 Yes
58 4th GGP Elizabeth Mary Booth 1728-1793 Mary [LNU] c1730-1807/1808 27 -2 Need Mary’s mtDNA through all females
59 4th GGP Nancy Ann Steele 1728-1836 Unknown mother of Jane [LNU], wife of Lazarus Dodson 16 -2 Need Jane’s mtDNA through all females
60 4th GGP James Campbell 1742-1931 Charles Campbell c1750-c1825 28 -2 Y DNA confirmed NOT this line
61 4th GGP Letitia Allison 1759-1844 Incorrect 31 -2
62 4th GGP Jacob Dobkins 1750-1833 Jacob Dobkins 1751-1835 91 1 Yes
63 4th GGP Dorcas (Darcas) Johnson 1750-1831 Darcus Johnson c1750-c1835 92 2 Yes
64 4th GGP John Francis Vannoy 1719-1778 John Francis Vannoy 1719-1778 47 2 Yes
65 4th GGP Susannah Baker Anderson 1720-1816 Susannah Anderson c1721-c1816 59 2 Need mtDNA through all females
66 4th GGP Thomas Hildreth Henderson 1736-1806 Charles Hickerson c1725-before 1793 37 -2 Have Hickerson Y-DNA
67 4th GGP Mary Frances “Frankie” McIntire 1735-1811 Mary Lytle c1730-before 1794 37 -2 Need mtDNA from all females
68 4th GGP Rev. George W. McNeil 1720-1805 George McNiel c1720-1805 143 1 Yes
69 4th GGP Mary Sarah Coates 1732-1782 Sarah/Sallie or Mary [maybe] Coates c1740-1782/1787 139 1 Need mtDNA through all females
70 4th GGP John James Sheppard Shepherd 1734-1810 Robert Shepherd 1739-1817 136 -2 Have Shepherd Y-DNA
71 4th GGP Sarah Ann Rash 1732-1810 Sarah Rash 1748-1829 178 -1 Yes
72 4th GGP John Crumbley 1737-1794 William Crumley 1736-1793 77 -2 Have Crumley Y-DNA
73 4th GGP Hannah Mercer 1742-1774 Hannah Mercer c1740-c1773 73 2 Yes
74 4th GGP John Hanner (Hainer) Incorrect 19 -2
75 4th GGP Jotham Brown 1740-1799 Incorrect 183 -2 Have Brown Y-DNA
76 4th GGP Phoebe Ellen Johnston 1742-1810 Incorrect 182 -2
77 4th GGP Moses Johnston 1746-1828 Incorrect 45 -2
78 4th GGP Eleanor Havis 1753-1837 Incorrect 47 -2
79 4th GGP Henry Boulton 1693-1737 John Bolton before 1693-after 1729 23 -2 Have Bolton Y-DNA
80 4th GGP Elizabeth Bryan 1658-1742 Elizabeth Goaring 1795-1729 22 -2 Need mtDNA through all females
81 4th GGP Thomas Curry (Corry) 1705-1729 Thomas Curry 1705-1729 25 2 Need Curry Y-DNA
82 4th GGP Monique “Moniky” Curry 1704-1729 Monique Demazares 1705-1729 25 1 Need mtDNA through all females
83 4th GGP Robert James Mann 1740-1787 John Mann 1725-1774 26 -2 Need Mann Y-DNA
84 4th GGP Sarah Susannah McCloskey 1716-1797 Frances Carpenter 1728-1833 28 -2 Need mtDNA through all females
85 4th GGP Benjamin “Col. Ben” Colonel Wilson 1733-1814 Incorrect 28 -2
86 4th GGP Mary Ann Seay 1735-1814 Incorrect 29 -2
87 4th GGP John Hugh McDowell 1695-1742 Michael McDowell c1720-after 1755 7 -2 Incorrect but have correct Y-DNA McDowell Y-DNA
88 4th GGP Mary Magdalena Woods 1705-1800 Incorrect 8 -2
89 4th GGP Ebenezer Hall 1721-1801 Incorrect 6 -2
90 4th GGP Dorcas Abbott Hall 1728-1797 Incorrect 6 -2
91 4th GGP George Middleton Clarkston/Clarkson 1745-1787 Incorrect 98 -2 Incorrect but have correct Clarkson Y-DNA
92 4th GGP Catherine Middleton 1764-1855 Incorrect 94 -2
93 4th GGP William Henry Cook 1750-1920 Joel Cook before 1755 – ? 83 -2 Need Cook Y-DNA
94 4th GGP Elizabeth Wall 1747-1826 Alcy [LNU] c 1755-? 91 -2 Yes
95 4th GGP Obediah Samuel Muncy 1735-1806 Samuel Muncy 1740-1799 33 -1 Yes
96 4th GGP UFN Obediah Muncy wife Unknowen (sic) 1728-1843 Agnes Craven 1745-1811 27 -2 Need Agnes Craven Need mtDNA through all females
97 4th GGP Joseph Workman 1732-1813 Joseph Workman c1736-c1813 64 2 Yes
98 4th GGP Phoebe McRay McMahon 1745-1826 Phoebe McMahon c1741-after 1815 64 1 Yes
99 4th GGP Charles Beckworth Speake/Speaks 1741-1794 Charles Speake c1731-1794 47 1 Yes
100 4th GGP Jane Connor 1742-1789 Incorrect, unknown first wife 40 -2 Need mtDNA through all females
101 4th GGP Gideon Farris 1748-1818 Gideon Faires before 1749-1821 54 -1 Yes
102 4th GGP Sarah Elizabeth McSpadden 1745-1821 Sarah McSpadden c1745-c1820 55 1 Yes
103 4th GGP Hugh McKee 1720-1795 Unknown 34 -2
104 4th GGP Mary Nesbit 1732-1795 Unknown 35 -2
105 4th GGP Private (sic) Unknown father of Elizabeth, wife of Andrew McKee 35 -2
106 4th GGP Anna Elizabeth Carney [wife of “private”] Incorrect 35 -2
107 5th GGP Moses Estes 1711-1788 Moses Estes 1711-1787 13 2 Yes
108 5th GGP Elizabeth Jones “Betty” Webb 1718-1782 Elizabeth [LNU] 1715/1720-1772/1782 5 -2 No known daughters
109 5th GGP George W. Combs 1714-1798 John Combs 1705-1762 6 -2 Need Combs Y-DNA
110 5th GGP Phebe Wade ?-1830 Incorrect 6 -2 Need mtDNA of John Combs first wife through all females
111 5th GGP Sarah Ferguson 1700-1781 Incorrect 3 -2
112 5th GGP Anthony Hart 1700-? Possibly Anthony Hart but no evidence 3 0
113 5th GGP Charles Rev. Moore 1685-1734 Incorrect 4 -2
114 5th GGP Mary Margaret Barry Moore 1690-1748 Incorrect 4 -2
115 5th GGP Ralph Hudspeth II* 1690-1776 Incorrect 9 -2
116 5th GGP Mary Carter 1699-1737 Incorrect 3 -2
117 5th GGP Samuel Harwell 1674-1767 Incorrect 3 -2
118 5th GGP Mary Ann Coleman*8th Ggm (sic) 1678-1723 incorrect 6 -2
119 5th GGP Ambrose (Sar) Jackson 1695-1745 Incorrect 6 -2
120 5th GGP Anne Amy Wyche 1692-1765 Incorrect 6 -2
121 5th GGP George E Dodson (DNA) (sic) 1702-1770 George Dodson 1702-after 1756 23 -1 Yes
122 5th GGP Margaret Dogett Dagord 1708-1770 Margaret Dagord 1708-? 24 1 Need mtDNA through all females
123 5th GGP James Booth 1700-1741 Incorrect 4 -2
124 5th GGP Frances Dale Booth (15great aunt) (sic) 1688-1777 Incorrect 3 -2
125 5th GGP Samuel Scurlock Steele 1709-1790 Incorrect 2 -2
126 5th GGP Robert R. Campbell 1718-1810 Incorrect 34 -2
127 5th GGP Lady: Letitia Crockett 1719-1760 Incorrect 8 -2
128 5th GGP John A. Dobkins 1717-1783 John Dobkins c1710-c1788 20 1 Yes
129 5th GGP Mary Elizabeth Betty Moore 1739-1815 Elizabeth [LNU] c1711-? 20 -2 Need mtDNA through all females
130 5th GGP Peter Johnson 1715-1796 Peter Johnson/Johnston c1720-c1794 0 1 Yes
131 5th GGP Mary Polly Phillips 1729-1790 Mary Polly Phillips c1726-? 1 2 Need mtDNA through all females
132 5th GGP Francis Janzen Vannoy Van Noy 1688-1774 Francis Vannoy 1688-1774 8 1 Yes
133 5th GGP Rebecca Anna Catherine Anderson 1698-1785 Rebecca Annahh Andriesen/ Anderson 1697-1727 13 -1 Need mtDNA through all females
134 5th GGP Cornelius Anderson (Andriessen) 1670-1724 Kornelis Andriesen 1670-1724 5 2 Yes
135 5th GGP Annetje Annah Opdyck 1670-1746 Annetje Opdyck c1675-after 1746 5 2 Need mtDNA through all females
136 5th GGP Thomas Hildret Henderson 1715-1794 Incorrect

 

3 -2
137 5th GGP Mary Frisby 1709-1794 Incorrect 3 -2
138 5th GGP Alexander (Alex) McEntire 1707-1802 Incorrect 12 -2
139 5th GGP Hannah Janet McPherson 1711-1792 Incorrect 15 -2
140 5th GGP Thomas James McNeil 1699-1803 Incorrect 25 -2
141 5th GGP Mary Hannah Parsons 1697-1784 Incorrect 27 -2
142 5th GGP John Coates 1699-1732 Incorrect 21 -2
143 5th GGP Sarah Ann Titcombe 1710-1732 Incorrect 22 -2
144 5th GGP George Sheppard, Shepherd 1716-1751 George Shepherd c1700-1751 42 1 Have Shepherd Y-DNA
145 5th GGP Elizabeth Mary Angelicke Day (Daye) 1699-? Elizabeth Mary Angelica Daye 1699-after 1750 41 1 Need mtDNA through all females
146 5th GGP Joseph Rash 1722-1776 Joseph Rash before 1728-c1767 36 1 Yes
147 5th GGP Mary Warren 1726-1792 Mary Warren 1726-? 36 1 Yes
148 5th GGP James L Crumley/Cromley 1712-1784 James Crumley c1711-1764 11 -1 Yes
149 5th GGP Catherine Bowen Gilkey 1712-1784 Catherine [LNU] c1712-c1790 11 -1 Need mtDNA through all females
150 5th GGP Edward Willis Mercer 1704-1763 Edward Mercer 1704-1763 5 1 Yes
151 5th GGP Ann Lueretias Coats 1710-1763 Ann [LNU] 1699/1705-c1786/1790 5 -2 Need mtDNA through all females
152 5th GGP Daniel Brown 1710-1798 Incorrect 39 -2
153 5th GGP Mary Brown 1717-1777 Incorrect 40 -2
154 5th GGP Zopher “Elder” Johnson/Johnston* 1700-1804 Incorrect 51 -2
155 5th GGP Elizabeth Williamson Cooper 1703-1794 Incorrect 49 -2
156 5th GGP Joseph Benjamin Johnson (6th ggf) (sic) 1709-1795 Incorrect 3 -2
157 5th GGP Elizabeth Shepard 1709-1786 Incorrect 3 -2
158 5th GGP John (Boulware) Havis (Rev/war) (sic) 1728-1807 Incorrect 4 -2
159 5th GGP Susannah Gentile Boullier (Boulware) 1733-1817 Incorrect 3 -2
160 5th GGP Henry Boulton Jr. 1652-1720 Incorrect 22 -2
161 5th GGP Elizabeth Bryan 1658-1742 Incorrect, linked in two generations Duplicate not processing -2
162 5th GGP Norton Bryan 1634-1672 Incorrect 2 -2
163 5th GGP Elizabeth Middlemore 1640-1658 Incorrect 2 -2
164 5th GGP Guillam Demazure 1685-1706 Guillam Demazares before 1685-after 1705 2 2 Need Y-DNA
165 5th GGP Marie Demazure 1686-1705 Marie [LNU] before 1686-after 1705 2 1 Need mtDNA through all females
166 5th GGP John Robert Mann {Minnis} 1711-1772 Incorrect 3 -2
167 5th GGP Anne Vincent 1711-1747 Incorrect 3 -2
168 5th GGP Joseph David McCluskey 1693-1756 Incorrect 3 -2
169 5th GGP Barbara S Rohlflag 1695-1755 Incorrect 3 -2
170 5th GGP Willis Wilson, Jr. 1710-1794 Incorrect 4 -2
171 5th GGP Elizabeth Goodrich ?-1789 Incorrect 4 -2
172 5th GGP Reverend James Matthew Seay 1696-1757 Incorrect 7 -2
173 5th GGP Elizabeth (James M Seay) Wilson or Lewis 1696-1752 Incorrect 6 -2
174 5th GGP Ephriam Samuel McDowell 1673-1774 Murtough McDowell before 1700-1752 0 -2 Yes
175 5th GGP Margaret Elizabeth Irvine 1674-1728 Eleanor [LNU] before 1700-after 1730 1 -2 Need mtDNA through all females
176 5th GGP Michael Marion Woods 1684-1782 Incorrect 9 -2
177 5th GGP Mary Catherine Woods 1690-1742 Incorrect 9 -2
178 5th GGP Joseph Hall 1680-1750 Incorrect 0 -2
179 5th GGP Sarah Kimball Hall Haley 1686-1752 Incorrect 0 -2
180 5th GGP Edward Abbott 1702-759 Incorrect 0 -2
181 5th GGP Dorcas Mehitable Chandler 1704-1748 Incorrect 0 -2
182 5th GGP James Anderson Clarkston 1717-1816 Incorrect 17 -2
183 5th GGP Thomasina Elizabeth Middleton 1720-1796 Incorrect 17 -2
184 5th GGP Harlace Middleton Incorrect 5 -2
185 5th GGP Capt. Vallentine Felty Kuke Cook 1730-1797 Incorrect 25 -2
186 5th GGP Michael Wall 1728-1749 Incorrect 11 -2
187 5th GGP Rebecca Chapman 1725-1791 Incorrect 11 -2
188 5th GGP Samuel Scott Muncy 1712-1786 Samuel Muncy 1712-after 1798 50 -1 Yes
189 5th GGP Mary Daughtery Skidmore 1710-1797 Mary Skidmore c1710-1811 51 -1 Need mtDNA through all females
190 5th GGP Abraham Woertman Workman 1709-1749 Abraham Workman 1709-1813 26 1 Yes
191 5th GGP Hannah Annetje (Smith) Workman 1706-1747 Annetie Smith 1714-? 26 1 Need mtDNA through all females
192 5th GGP Hugh McMahon 1699-1749 Hugh McMahon 1699-1749 17 2 Need Y-DNA
193 5th GGP Agnas Norton 1699-1747 Agnas Norton after 1700-? 17 2 Need mtDNA through all females
194 5th GGP Thomas Bowling Speake V 1698-1765 Thomas Speak c1634-1681 11 -2 Yes
195 5th GGP Jane Barton/Brisco Smoote 1714-1760 Elizabeth Bowling 1641-before 1692 12 -2 No known daughters
196 5th GGP William Farris 1714-1776 William Faires/Farris before 1728-1776 11 1 Yes
197 5th GGP Deborah Johnson Faries 1734-1812 Deborah [LNU] 1734-1812 11 1 Need mtDNA through all females
198 5th GGP Thomas of Borden’s Grant McSpadden 1720-1765 Thomas McSpadden c1721-1785 19 1 Yes
199 5th GGP Mary Dorothy Edmondson (Edmundson, Edmiston, Edmisten) 1721-1786 Dorothy [possibly Edmiston] 1721-? 28 1 Yes
200 5th GGP Thomas Alexander McKee, Sr 1693-1769 Incorrect 7 -2
201 5th GGP Tecumseh Margaret Opessa Pekowi 1695-1780 Incorrect 6 -2
202 5th GGP Thomas F Nesbit 1707-1783 Incorrect 7 -2
203 5th GGP Jean McKee 1707-1790 Incorrect 7 -2
Total -163

Please note that I will provide a free Y-DNA testing scholarship at FamilyTreeDNA for any male descending through all men from the male ancestor where it’s noted that Y-DNA is needed. Y-DNA is typically the surname line in most western countries.

I will also provide a mitochondrial DNA testing scholarship at FamilyTreeDNA for anyone who descends from the women where it’s noted that mitochondrial DNA is needed. Mitochondrial DNA passes through all females to the current generation, which can be male or female.

If this is you or a family member, please reach out to me.

The Scores

Of the 203 ancestors for which Ancestry provided a Potential Ancestor, they could have amassed a total of 406 points if each one provided an accurate name and accurate birth and death dates within a reasonable margin. If they were completely wrong on every one, they could have earned a negative score of -406.

Ancestry’s ThruLine accuracy score was -163, meaning they were wrong more than right. Zero was the break-even point where there was equally as much accurate information as inaccurate.

In fairness though, the older ancestors are more likely to be wrong than the more recent ones, and there are more older ancestors given that ancestors double in each generation. Once Ancestry provided a wrong ancestor, they continued down that wrong path on up the tree, so once the path was incorrect, it never recovered.

Regardless of why, Ancestry suggested incorrect information, and as we know, many people take that information to heart as gospel. In fact, many people even call these *TrueLines* instead of *ThruLines*.

Ok, how did Ancestry do?

Category Total Percent
+2 – Both Name and Date Accurate or Within Range 24 11.82%
+1 – Name and/or Date Partly Accurate 41 20.2%
0 – Uncertain 1 0.49%
-1 – Neither Name nor Date Accurate, but Enough Context to Figure Out With Research 22 10.84%
-2 – Inaccurate, the wrong person 115 56.65%

 Take Aways – Lessons Learned

This leads us to the lessons learned portion.

  • Never, ever, take ThruLines or Potential Ancestors at face value. They are hints and nothing more. Ancestry states that “ThruLines uses Ancestry trees to suggest how you may be related to your DNA matches through common ancestors.” (Bolding is mine.)
  • Verify everything.
  • Never simply copy something from another tree or accept a hint of any kind without a thorough evaluation. No, your ancestor probably did not zigzag back and forth across the country every other year in the 1800s. If you think they did, then you’ll need lots of information to prove that unusual circumstance. Extraordinary circumstances require extraordinary proof.
  • Never add extraneous “things” to names like “DNA match” or name someone “Private,” unless, of course, that was actually their name. Extraneous “pieces” in names confuses Ancestry’s search routines too, so you’re hurting your own chances of finding relevant information about your ancestor, not to mention ThruLines for others.
  • Naming someone “Private” isn’t useful if they are attached to other non-private people as ancestors, siblings and descendants. Just sayin…
  • Once the first incorrect ancestor is suggested, ThruLines continues to go up the incorrect tree.
  • In the the older or oldest generations, a small number of DNA matches for a particular ancestor may simply mean that lots of people are beyond the ThruLines match reporting thresholds. Unfortunately, Ancestry does NOT have a function where you can hunt for matches by ancestor.
  • In the the older or oldest generations, a small number of DNA matches may also mean it’s either the wrong ancestor, or they have few descendants, or few have tested.
  • The number of matches, in either direction, is not directly predictive of the accuracy of the suggested ancestor.
  • One of the best ways to validate ancestor accuracy is to match other descendants through multiple children of the ancestor, assuming that the children have been assigned to that ancestor properly. Recall George Middleton Clarkson where the three male children assigned to him do not have the same Y-DNA.
  • Another validation technique is to also match descendants of both parents of the ancestor(s) in question, through multiple children.
  • Remember that paper trail documentation is an extremely important aspect of genealogy.
  • Do not rely on trees without sources, or on trees with sources without verifying that every source is actually referencing this specific person.
  • Same name confusion is a very real issue.
  • For male ancestors, always check the Y-DNA projects at FamilyTreeDNA to verify that males attached as children have descendants with matching Y-DNA.
  • Always test males for their surname line. You never know when you’ll either prove or disprove a long-held belief, or discover that someplace, there has been a biological break in that line.
  • Y-DNA matches can provide extremely valuable information on earlier ancestral lines which may lead to breaking through your brick wall.
  • Mitochondrial DNA testing and matching of descendants is sometimes the only way of proving maternity or discovering matches to earlier ancestors.
  • Both Y-DNA and mitochondrial DNA, via haplogroups, can provide origins information for that one specific line, meaning you don’t have to try to figure out which ancestor contributed some percentage of ethnicity or population-based DNA.
  • Everyone can test their mitochondrial DNA, inherited from their direct matrilineal line, and men can test their Y-DNA, which is their surname line.
  • Remember that ThruLines can only be as good as the trees upon which it relies.
  • Review the source trees for each Potential Ancestor provided, evaluating each source carefully, including notes, images and web links. You just never know where that diamond is hiding.

How Can Ancestry Improve ThruLines, Potential Ancestors and Provide Customers with Better Tools?

To improve ThruLines and/or Potential Ancestors, Ancestry could:

  • My #1 request would be to implement a “search by ancestor” feature for DNA matches. This would be especially beneficial for situations where matches are beyond the 5GG threshold, or if someone is testing a hypothesis to see if they match descendants of a particular person.
  • Provide a “dismiss” function, or even a function where a customer could provide a reason why they don’t believe a connection or suggestion is accurate. This could travel with that link for other users as well so people can benefit from commentary from and collaboration with others.
  • Provide all DNA matches to people who share a specific ancestor, even if one person is beyond the 5 GG level. Currently, if both people are beyond that threshold, the match won’t show for either, so that’s no problem. The hybrid way it works today is both confusing and misleading and the hard cutoff obfuscates matches that have the potential to be extremely useful. Often this is further exacerbated by the 20 cM thresold limit on shared matches.
  • Add a feature similar to the now defunct NADs (New Ancestor Discoveries) where Ancestry shows you a group of your matches that descend from common ancestors, but those ancestors are NOT connected to anyone in your tree. However, DO NOT name the tool New Ancestor Discoveries because these people may not be, and often are not, your ancestors. If you’re related to a group of people who all have these people in THEIR tree as ancestors, that alone is a powerful hint. You might be descended from their ancestors, from the spouse of one of their children – something. But it’s information to work with when you have brick walls where Ancestry cannot connect someone as a potential ancestor directly to someone in your tree. Even locations of those brick-wall-breaker possible ancestors would be a clue. In fact, it’s not terribly different than the Potential Ancestors today, except today’s Potential Ancestors are entirely tree based (beyond ThruLines) and dependent upon connecting with someone in your tree. These new Brick-Wall-Breaker Potential Ancestors are (1.) NOT connected to your tree, and (2.) are all a result of DNA matches with people who have these ancestors in their tree.
  • If you already map your segment information at DNAPainter, the Brick-Wall-Breaker ancestral lineage connection would be immediately evident if Ancestry provided DNA segment location information. In other words, there are answers and significant hints that could be available to Ancestry’s customers.
  • Extend ThruLines for (at least) another two generations. Today ThruLines ends at the point that many people begin running into brick walls about the time the US census began. Using a 25-year generation, the current algorithm gives you 175 years (about 1825 starting with the year 2000), and a 30-year generation gives you 210 years (about 1790). Extending that two additional generations would give testers two more generations, several more Potential Ancestors, and 50-60 more years, approaching or reaching across the US colonial threshold.
  • Extending ThruLines and adding that Brick-Wall-Breaker functionality wouldn’t be nearly as important if customers could search by ancestor and download their match with direct ancestor information, similar to the other vendors, but since we can’t, we’re completely reliant on ThruLines and Potential Ancestors for automated connections by ancestor. Downloading your match list including a list of each person’s direct ancestors and matching segments would provide resources for many of these customer needs, without Ancestry having to do significant major development. If nothing else, it could be an interim stepping-stone.

_____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

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 Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

The Best of 2022

It’s that time of year where we look both backward and forward.

Thank you for your continued readership! Another year under our belts!

I always find it interesting to review the articles you found most interesting this past year.

In total, I published 97 articles in 2022, of which 56 were directly instructional about genetic genealogy. I say “directly instructional,” because, as you know, the 52 Ancestors series of articles are instructional too, but told through the lives of my ancestors. That leaves 41 articles that were either 52 Ancestors articles, or general in nature.

It has been quite a year.

2022 Highlights

In a way, writing these articles serves as a journal for the genetic genealogy community. I never realized that until I began scanning titles a year at a time.

Highlights of 2022 include:

Which articles were your favorites that were published in 2022, and why?

Your Favorites

Often, the topics I select for articles are directly related to your comments, questions and suggestions, especially if I haven’t covered the topic previously, or it needs to be featured again. Things change in this industry, often. That’s a good thing!

However, some articles become forever favorites. Current articles don’t have enough time to amass the number of views accumulated over years for articles published earlier, so recently published articles are often NOT found in the all-time favorites list.

Based on views, what are my readers’ favorites and what do they find most useful?

In the chart below, the 2022 ranking is not just the ranking of articles published in 2022, but the ranking of all articles based on 2022 views alone. Not surprisingly, six of the 15 favorite 2022 articles were published in 2022.

The All-Time Ranking is the ranking for those 2022 favorites IF they fell within the top 15 in the forever ranking, over the entire decade+ that this blog has existed.

Drum roll please!!!

Article Title Publication Date 2022 Ranking All-Time Ranking
Concepts – Calculating Ethnicity Percentages January 2017 1 2
Proving Native American Ancestry Using DNA December 2012 2 1
Ancestral DNA Percentages – How Much of Them in in You? June 2017 3 5
AutoKinship at GEDmatch by Genetic Affairs February 2022 4
442 Ancient Viking Skeletons Hold DNA Surprises – Does Your Y or Mitochondrial DNA Match? Daily Updates Here September 2020 5
The Origins of Zana of Abkhazia July 2021 6
Full or Half Siblings April 2019 7 15
Ancestry Rearranged the Furniture January 2022 8
DNA from 459 Ancient British Isles Burials Reveals Relationships – Does Yours Match? February 2022 9
DNA Inherited from Grandparents and Great-Grandparents January 2020 10
Ancestry Only Shows Shared Matches of 20 cM and Greater – What That Means & Why It Matters May 2022 11
How Much Indian Do I Have in Me??? June 2015 12 8
Top Ten RootsTech 2022 DNA Sessions + All DNA Session Links March 2022 13
FamilyTreeDNA DISCOVER Launches – Including Y DNA Haplogroup Ages June 2022 14
Ancient Ireland’s Y and Mitochondrial DNA – Do You Match??? November 2020 15

2023 Suggestions

I have a few articles already in the works for 2023, including some surprises. I’ll unveil one very soon.

We will be starting out with:

  • Information about RootsTech where I’ll be giving at least 7 presentations, in person, and probably doing a book signing too. Yes, I know, 7 sessions – what was I thinking? I’ve just missed everyone so very much.
  • An article about how accurately Ancestry’s ThruLines predicts Potential Ancestors and a few ways to prove, or disprove, accuracy.
  • The continuation of the “In Search Of” series.

As always, I’m open for 2023 suggestions.

In the comments, let me know what topics you’d like to see.

_____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

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 Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

“Nature scientific reports” 2022 Editor’s Choice Collection – We Made It!!!!

You’ll excuse me while I jump for joy and do a happy dance. You might say I’m over the moon, pardon the pun. There’s nothing to lift your spirits quite like a pleasant surprise!I

In June, when our article, African mitochondrial haplogroup L7: a 100,000-year-old maternal human lineage discovered through reassessment and new sequencing was published, you may or may not have noticed that the journal name was “nature, scientific reports.” No, they don’t capitalize the words in the journal’s title.

I know I didn’t mention how difficult is it to get published in this particular journal, so you’ll just have to trust me about how many grey hairs I can attribute to that process.

Taking that into account, imagine my surprise today when I discovered our paper in the Editor’s Choice collection for 2022. That’s not only amazing, it was entirely unexpected. Ironically, they didn’t notify the authors, so we found out quite by accident.

“Congratulations!!!”

“For what?”

“Editor’s Choice”

“Editor’s Choice for what? Where?”

“Nature scientific reports – the Editor’s Choice articles for 2022. Your L7 paper. It’s there in Ancient DNA.”

“WHAT?????”

I had to look right away, of course, never mind that I was standing in line at the bank at the time. I hope they didn’t notice the strange woman giving out a little yelp and accompanying leap. Ok, maybe it was a tiny leap, more like a happy hop, but it still counts.

Here, you can look too!

I was dumbstruck. Truth be told, I didn’t even realize there WAS a yearly Editor’s Choice collection. My bad. I probably shouldn’t admit that😊

The editor’s intro mentions that Svante Pääbo won the Nobel Prize in Physiology or Medicine this year for his work over the past several years on sequencing the genomes of extinct hominins, founding the field of paleogenetics.

Excuse my fan-girl exuberance, but it has truly been a banner year for genetics. I can’t help but be incredibly geeked! I had to read the announcement two or three times to be sure I was seeing what I was seeing.

Our paper was selected as one of 5 in the Mitogenomics section of the ancient DNA category and has accumulated just over 9700+ views which is actually amazing for a scientific paper. So, thank you everyone who read it. I’m glad we made the paper “open access,” which means free.

I wrote about our discovery, here and we published a video, here, but our paper is slightly different than the ancient DNA of the other papers in that category. The other papers utilize DNA extracted from ancient remains, but the “ancient DNA” of haplogroup L7, reaching back 100,000 years, was discovered in living people, with the exception of one 16,000-year-old ancient sample from Malawi that had initially been misclassified as L5, but has since been moved to L7.

That’s super-exciting because we know that this hen’s-teeth rare lineage still exists in a few people. Maybe you’re one of them. Maybe you carry a different but equally-as-rare mitochondrial lineage – your mother’s direct maternal line.

I hope you’ll test your mitochondrial DNA, here, to see what secrets are waiting for you.

_____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

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 Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

DNA Black Friday is Here

Yes, I know it’s not Friday yet, but the DNA Black Friday sales have started, and sale dates are limited, so here we go.

These are the best prices I’ve ever seen at both FamilyTreeDNA and MyHeritage. If you’ve been waiting to purchase a DNA test for that special someone, there’s never been a better time.

Remember, to jump-start your genetic genealogy, test close or targeted relatives in addition to yourself:

  • Parents, or if both parents are not available, full and half-siblings
  • If neither parents nor siblings are available, your siblings’ descendants
  • Grandparents or descendants of your grandparents – aunts, uncles, or their descendants
  • Cousins descended from great-grandparents or other known ancestors
  • Y and mitochondrial DNA descendants of specific, targeted ancestors

For yourself, you’ll want to fish in all the ponds by taking an autosomal test or uploading a DNA file to each of the four vendors. Upload/download instructions are available here.

Everyone can test their own mitochondrial DNA to learn about your mother’s direct matrilineal line, and males can test their Y-DNA to unveil information about their patrilineal or surname line. Women, you can test your father’s, brother’s, or paternal uncle’s Y-DNA.

I’ve written a DNA explainer article, 4 Kinds of DNA for Genetic Genealogy, which you might find helpful. Please feel free to pass it on.

Vendor Offerings

FamilyTreeDNA

Free shipping within the US for orders of $79 or more

FamilyTreeDNA is the only major testing company that offers multiple types of tests, meaning Y-DNA, mitochondrial and autosomal. You can also get your toes wet with introductory level tests for Y DNA (37 and 111 marker tests), or you can go for the big gun right away with the Big Y-700.

This means that if you’ve purchased tests in the past, you can upgrade now. Upgrade pricing is shown below. Click here to sign on to your account to purchase an upgrade or additional product.

At FamilyTreeDNA, by taking advantage of autosomal plus Y-DNA and mitochondrial DNA, you will get to know your ancestors in ways not possible elsewhere. You can even identify or track them using your myOrigins painted ethnicity segments.

FamilyTreeDNA divides your Family Finder matches maternal and paternally for you if you create or upload a tree and link known testers. How cool is this?!!!

MyHeritage

The MyHeritage DNA test is on sale for $36, the best autosomal test price I’ve ever seen anyplace.

MyHeritage has a significant European presence and I find European matches at MyHeritage that aren’t anyplace else. MyHeritage utilizes user trees and DNA matches to construct Theories of Family Relativity that shows how you and your matches may be related.

Remember, you can upload the raw data file from the MyHeritage DNA test to both FamilyTreeDNA and GEDmatch for free.

Free shipping on 2 kits or more.

This sale ends at the end-of-day on Black Friday.

You can combine your DNA test with a MyHeritage records subscription with a free trial, here.

Ancestry

The AncestryDNA test is $59, here. With Ancestry’s super-size DNA database, you’re sure to get lots of matches and hints via ThruLines.

You can get free shipping if you’re an Amazon Prime member.

If you order an AncestryDNA test, you can upload the raw DNA file to FamilyTreeDNA, MyHeritage and GEDmatch for free. Unfortunately, Ancestry does not accept uploads from other vendors.

23andMe

The 23andMe Ancestry + Traits DNA test is $79, here. 23andMe is well known for its Ancestry Composition (ethnicity) results and one-of-a-kind genetic tree.

The 23andMe Ancestry + Traits + Health test is now $99, here.

You can get free shipping if you’re an Amazon Prime member.

If you order either of the 23andMe tests, you can upload the raw data file to FamilyTreeDNA, MyHeritage, and GEDmatch for free. Unfortunately, 23andMe does not accept uploads from other vendors.

Can’t Wait!!

This is always my favorite time of the year because I know that beginning soon, we will all be receiving lots of new matches from people who purchased or received DNA tests during the holiday season.

  • What can you do to enhance your genealogy?
  • Have you ordered Y and mitochondrial DNA tests for yourself and people who carry the Y and mitochondrial DNA of your ancestors?
  • Are you in all of the autosomal databases?
  • Who are you ordering tests for?

_____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

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 Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Native American: Is She or Isn’t She?

Many people have an oral history that a specific female ancestor is Native American.

Autosomal DNA results may or may not show some percentage of Native American ancestry. If your results DO include a percentage of Native American, you still need to figure out which ancestors were Native. Where did that piece of your genetic heritage come from?

If your results don’t include Native ancestry, that doesn’t necessarily mean you don’t have a Native Ancestor. Sometimes you just didn’t inherit a discernable segment of DNA from that ancestor, or maybe the vendor you tested with didn’t pick that up.

Be sure to upload your raw DNA file to both FamilyTreeDNA and MyHeritage for free to gain another perspective. Here’s my free step-by-step guide for downloading and uploading your DNA files from and to all the major vendors.

FamilyTreeDNA provides painted segment information as well that shows you which segments are Native American.

One of my challenges is that I do have Native American autosomal DNA segments. Determining where they came from has been challenging, although the ethnicity chromosome painting at FamilyTreeDNA has been very useful in confirming the source of those segments.

Is there a way to augment autosomal results and be more specific and directed in my search? Can I focus on an individual ancestor? Especially females who are particularly difficult to research, given name changes in each generation?

Yes, you can.

Chasing the Truth

Sometimes, especially historically, when a female ancestor’s genealogy wasn’t known, people presumed that they must have been Native American. I’ve come across this several times now.

The good news is that using mitochondrial DNA, you can find out conclusively if you test someone who descends from that woman through all females to the current generation, which can be male.

I had Native American oral history connected to two ancestors, both of whom I was able to confirm or refute by finding a cousin who inherited that ancestor’s mitochondrial DNA and agreed to test. Women give their mitochondrial DNA to both sexes of their children, but only daughters pass it on. In the current generation, males or females can test.

I also found an unexpected ancestor who was Native. I had no oral history about her – so you just never know what you’ll discover.

Sarah Faires

Oral history in some descendant families indicated that Sarah Faires’s was Native American, possibly because her ancestors were unknown. There was a supposition that “she must have been Native.”

We were able to obtain the mitochondrial DNA of Sarah whose haplogroup turned out to be H49a1, so clearly not Native.

If Sarah’s direct maternal line (her mother, her mother, her mother, on up her tree) had been Native American, she would have fallen into subclades of haplogroup A, B, C, D or X, although not all of those subclades are Native.

You can view the entire list of Native American mitochondrial DNA haplogroups, here and you can view H49a1 on the public mitochondrial haplotree, here.

H49a1 is most frequently found in Germany, followed by Sweden, England and Denmark.

Elizabeth Vannoy

My father’s grandmother, Elizabeth Vannoy, was reported to be Cherokee, both orally and in several letters between family members.

One of my first genealogy goals was to prove that history, but I wound up eventually doing just the opposite.

Elizabeth Vannoy’s mitochondrial DNA haplogroup is J1c2c, not Native.

Haplogroup J1c2c is found most often in England, France, Sweden and Hungary.

I was able to connect Elizabeth to her parents. Then, eventually, thanks to mitochondrial DNA, working with a cousin, we connected another four maternal generations conclusively, and I’m still working on the fifth generation.

Anne Marie Rimbault

My cousin had no idea that her ancestor, Anne Marie, born about 1631, in Acadia, wife of Rene Rimbault, was Native American when she tested her mitochondrial DNA.

Mitochondrial DNA results explained why Anne Marie’s parents had never been identified in the French records. She was Native American – a member of the Mi’kmaq tribe that intermarried with the French men in the Acadian settlement, proven by her A2f1a haplogroup.

Haplogroup A2f1a is shown on the mitochondrial haplotree as First Nations in Canada and Native American in the US, plus one French flag reflecting a tester who only knew that her ancestor was French-Canadian and believed she had come from France.

Her mitochondrial DNA matches are scattered across the Northern US and Canada, but her closest matches are found in the Acadian and French-Canadian communities.

Is She, or Isn’t She?

Testing your own mitochondrial DNA if you think your direct maternal ancestor may be Native will unquestionably answer that question. Finding a mitochondrial DNA candidate for each of your ancestral lines will reveal which ancestor is Native, or you can target test to see if any specific ancestor is Native.

Unlike autosomal DNA, mitochondrial DNA never loses its potency and doesn’t mix with the DNA of the father. The segments aren’t divided in each generation and don’t wash out over time.

Do you have oral history about female Native American ancestors? Do you have ancestors whose parents are unknown? Mitochondrial DNA testing will resolve that question, plus provide matching with other testers. You don’t know what you don’t know.

If you’re interested in learning more about how to find your Native American ancestors, you might enjoy my book, DNA for Native American Genealogy. There’s lots of information there, including search tips, ancient DNA, maps and known tribes by haplogroup.

Do you have female ancestors who might be Native American?

____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

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 Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

DNA: In Search of…Signs of Endogamy

This is the fourth in our series of articles about searching for unknown close family members, specifically; parents, grandparents, or siblings. However, these same techniques can be applied by genealogists to ancestors further back in time as well.

In this article, we discuss endogamy – how to determine if you have it, from what population, and how to follow the road signs.

After introductions, we will be covering the following topics:

  • Pedigree collapse and endogamy
  • Endogamous groups
  • The challenge(s) of endogamy
  • Endogamy and unknown close relatives (parents, grandparents)
  • Ethnicity and Populations
  • Matches
  • AutoClusters
  • Endogamous Relationships
  • Endogamous DNA Segments
  • “Are Your Parents Related?” Tool
  • Surnames
  • Projects
  • Locations
  • Y DNA, Mitochondrial DNA, and Endogamy
  • Endogamy Tools Summary Tables
    • Summary of Endogamy Tools by Vendor
    • Summary of Endogamous Populations Identified by Each Tool
    • Summary of Tools to Assist People Seeking Unknown Parents and Grandparents

What Is Endogamy and Why Does It Matter?

Endogamy occurs when a group or population of people intermarry among themselves for an extended period of time, without the introduction of many or any people from outside of that population.

The effect of this continual intermarriage is that the founders’ DNA simply gets passed around and around, eventually in small segments.

That happens because there is no “other” DNA to draw from within the population. Knowing or determining that you have endogamy helps make sense of DNA matching patterns, and those patterns can lead you to unknown relatives, both close and distant.

This Article

This article serves two purposes.

  • This article is educational and relevant for all researchers. We discuss endogamy using multiple tools and examples from known endogamous people and populations.
  • In order to be able to discern endogamy when we don’t know who our parents or grandparents are, we need to know what signs and signals to look for, and why, which is based on what endogamy looks like in people who know their heritage.

There’s no crystal ball – no definitive “one-way” arrow, but there are a series of indications that suggest endogamy.

Depending on the endogamous population you’re dealing with, those signs aren’t always the same.

If you’re sighing now, I understand – but that’s exactly WHY I wrote this article.

We’re covering a lot of ground, but these road markers are invaluable diagnostic tools.

I’ve previously written about endogamy in the articles:

Let’s start with definitions.

Pedigree Collapse and Endogamy

Pedigree collapse isn’t the same as endogamy. Pedigree collapse is when you have ancestors that repeat in your tree.

In this example, the parents of our DNA tester are first cousins, which means the tester shares great-grandparents on both sides and, of course, the same ancestors from there on back in their tree.

This also means they share more of those ancestors’ DNA than they would normally share.

John Smith and Mary Johnson are both in the tree twice, in the same position as great-grandparents. Normally, Tester Smith would carry approximately 12.5% of each of his great-grandparents’ DNA, assuming for illustration purposes that exactly 50% of each ancestor’s DNA is passed in each generation. In this case, due to pedigree collapse, 25% of Tester Smith’s DNA descends from John Smith, and another 25% descends from Mary Johnson, double what it would normally be. 25% is the amount of DNA contribution normally inherited from grandparents, not great-grandparents.

While we may find first cousin marriages a bit eyebrow-raising today, they were quite common in the past. Both laws and customs varied with the country, time, social norms, and religion.

Pedigree Collapse and Endogamy is NOT the Same

You might think that pedigree collapse and endogamy is one and the same, but there’s a difference. Pedigree collapse can lead to endogamy, but it takes more than one instance of pedigree collapse to morph into endogamy within a population. Population is the key word for endogamy.

The main difference is that pedigree collapse occurs with known ancestors in more recent generations for one person, while endogamy is longer-term and systemic in a group of people.

Picture a group of people, all descended from Tester Smith’s great-grandparents intermarrying. Now you have the beginnings of endogamy. A couple hundred or a few hundred years later, you have true endogamy.

In other words, endogamy is pedigree collapse on a larger scale – think of a village or a church.

My ancestors’ village of Schnait, in Germany, is shown above in 1685. One church and maybe 30 or 40 homes. According to church and other records, the same families had inhabited this village, and region, for generations. It’s a sure bet that both pedigree collapse and endogamy existed in this small community.

If pedigree collapse happens over and over again because there are no other people within the community to marry, then you have endogamy. In other words, with endogamy, you assuredly DO have historical pedigree collapse, generally back in time, often before you can identify those specific ancestors – because everyone descends from the same set of founders.

Endogamy Doesn’t Necessarily Indicate Recent Pedigree Collapse

With deep, historic endogamy, you don’t necessarily have recent pedigree collapse, and in fact, many people do not. Jewish people are a good example of this phenomenon. They shared ancestors for hundreds or thousands of years, depending on which group we are referring to, but in recent, known, generations, many Jewish people aren’t related. Still, their DNA often matches each other.

The good news is that there are telltale signs and signals of endogamy.

The bad news is that not all of these are obvious, meaning as an aid to people seeking clues about unknown close relatives, and other “signs” aren’t what they are believed to be.

Let’s step through each endogamy identifier, or “hint,” and then we will review how we can best utilize this information.

First, let’s take a look at groups that are considered to be endogamous.

Endogamous Groups

Jewish PeopleSpecifically groups that were isolated from other groups of Jewish (and other) people; Ashkenazi (Germany, Northern France, and diaspora), Sephardic (Spanish, Iberia, and diaspora), Mizrahi (Israel, Middle Eastern, and diaspora,) Ethiopian Jews, and possibly Jews from other locations such as Mountain Jews from Kazakhstan and the Caucasus.

AcadiansDescendants of about 60 French families who settled in “Acadia” beginning about 1604, primarily on the island of Nova Scotia, and intermarried among themselves and with the Mi’kmaq people. Expelled by the English in 1755, they were scattered in groups to various diasporic regions where they continued to intermarry and where their descendants are found today. Some Acadians became the Cajuns of Louisiana.

Anabaptist Protestant FaithsAmish, Mennonite, and Brethren (Dunkards) and their offshoots are Protestant religious sects founded in Europe in the 14th, 15th, and 16th centuries on the principle of baptizing only adults or people who are old enough to choose to follow the faith, or rebaptizing people who had been previously baptized as children. These Anabaptist faiths tend to marry within their own group or church and often expel those who marry outside of the faith. Many emigrated to the American colonies and elsewhere, seeking religious freedom. Occasionally those groups would locate in close proximity and intermarry, but not marry outside of other Anabaptist denominations.

Native American (Indigenous) People – all indigenous peoples found in North and South America before European colonization descended from a small number of original founders who probably arrived at multiple times.

Indigenous Pacific Islanders – Including indigenous peoples of Australia, New Zealand, and Hawaii prior to colonization. They are probably equally as endogamous as Native American people, but I don’t have specific examples to share.

Villages – European or other villages with little inflow or whose residents were restricted from leaving over hundreds of years.

Other groups may have significant multiple lines of pedigree collapse and therefore become endogamous over time. Some people from Newfoundland, French Canadians, and Mormons (Church of Jesus Christ of Latter-Day Saints) come to mind.

Endogamy is a process that occurs over time.

Endogamy and Unknown Relatives

If you know who your relatives are, you may already know you’re from an endogamous population, but if you’re searching for close relatives, it’s helpful to be able to determine if you have endogamous heritage, at least in recent generations.

If you know nothing about either parent, some of these tools won’t help you, at least not initially, but others will. However, as you add to your knowledge base, the other tools will become more useful.

If you know the identity of one parent, this process becomes at least somewhat easier.

In future articles, we will search specifically for parents and each of your four grandparents. In this article, I’ll review each of the diagnostic tools and techniques you can use to determine if you have endogamy, and perhaps pinpoint the source.

The Challenge

People with endogamous heritage are related in multiple, unknown ways, over many generations. They may also be related in known ways in recent generations.

If both of your parents share the SAME endogamous culture or group of relatives:

  • You may have significantly more autosomal DNA matches than people without endogamy, unless that group of people is under-sampled. Jewish people have significantly more matches, but Native people have fewer due to under-sampling.
  • You may experience a higher-than-normal cM (centiMorgan) total for estimated relationships, especially more distant relationships, 3C and beyond.
  • You will have many matches related to you on both your maternal and paternal sides.
  • Parts of your autosomal DNA will be the same on both your mother’s and father’s sides, meaning your DNA will be fully identical in some locations. (I’ll explain more in a minute.)

If either (or both) of your parents are from an endogamous population, you:

  • Will, in some cases, carry identifying Y and mitochondrial DNA that points to a specific endogamous group. This is true for Native people, can be true for Jewish people and Pacific Islanders, but is not true for Anabaptist people.

One Size Does NOT Fit All

Please note that there is no “one size fits all.”

Each or any of these tools may provide relevant hints, depending on:

  • Your heritage
  • How many other people have tested from the relevant population group
  • How many close or distant relatives have tested
  • If your parents share the same heritage
  • Your unique DNA inheritance pattern
  • If your parents, individually, were fully endogamous or only partly endogamous, and how far back generationally that endogamy occurred

For example, in my own genealogy, my maternal grandmother’s father was Acadian on his father’s side. While I’m not fully endogamous, I have significantly more matches through that line proportionally than on my other lines.

I have Brethren endogamy on my mother’s side via her paternal grandmother.

Endogamous ancestors are shown with red stars on my mother’s pedigree chart, above. However, please note that her maternal and paternal endogamous ancestors are not from the same endogamous population.

However, I STILL have fewer matches on my mother’s side in total than on my father’s side because my mother has recent Dutch and recent German immigrants which reduces her total number of matches. Neither of those lines have had as much time to produce descendants in the US, and Europe is under-sampled when compared with the US where more people tend to take DNA tests because they are searching for where they came from.

My father’s ancestors have been in the US since it was a British Colony, and I have many more cousins who have tested on his side than mother’s.

If you looked at my pedigree chart and thought to yourself, “that’s messy,” you’d be right.

The “endogamy means more matches” axiom does not hold true for me, comparatively, between my parents – in part because my mother’s German and Dutch lines are such recent immigrants.

The number of matches alone isn’t going to tell this story.

We are going to need to look at several pieces and parts for more information. Let’s start with ethnicity.

Ethnicity and Populations

Ethnicity can be a double-edged sword. It can tell you exactly nothing you couldn’t discern by looking in the mirror, or, conversely, it can be a wealth of information.

Ethnicity reveals the parts of the world where your ancestors originated. When searching for recent ancestors, you’re most interested in majority ethnicity, meaning the 50% of your DNA that you received from each of your parents.

Ethnicity results at each vendor are easy to find and relatively easy to understand.

This individual at FamilyTreeDNA is 100% Ashkenazi Jewish.

If they were 50% Jewish, we could then estimate, and that’s an important word, that either one of their parents was fully Jewish, and not the other, or that two of their grandparents were Jewish, although not necessarily on the same side.

On the other hand, my mother’s ethnicity, shown below, has nothing remarkable that would point to any majority endogamous population, yet she has two.

The only hint of endogamy from ethnicity would be her ~1% Americas, and that isn’t relevant for finding close relatives. However, minority ancestry is very relevant for identifying Native ancestors, which I wrote about, here.

You can correlate or track your ethnicity segments to specific ancestors, which I discussed in the article, Native American & Minority Ancestors Identified Using DNAPainter Plus Ethnicity Segments, here.

Since I wrote that article, FamilyTreeDNA has added the feature of ethnicity or population Chromosome Painting, based on where each of your populations fall on your chromosomes.

In this example on chromosome 1, I have European ancestry (blue,) except for the pink Native segment, which occurs on the following segment in the same location on my mother’s chromosome 1 as well.

Both 23andMe, and FamilyTreeDNA provide chromosome painting AND the associated segment information so you can identify the relevant ancestors.

Ancestry is in the process of rolling out an ethnicity painting feature, BUT, it has no segment or associated matching information. While it’s interesting eye candy, it’s not terribly useful beyond the ethnicity information that Ancestry already provides. However, Jonny Perl at DNAPainter has devised a way to estimate Ancestry’s start and stop locations, here. Way to go Jonny!

Now all you need to do is convince your Ancestry matches to upload their DNA file to one of the three databases, FamilyTreeDNA, MyHeritage, and GEDMatch, that accept transfers, aka uploads. This allows matching with segment data so that you can identify who matches you on that segment, track your ancestors, and paint your ancestral segments at DNAPainter.

I provided step-by-step instructions, here, for downloading your raw DNA file from each vendor in order to upload the file to another vendor.

Ethnicity Sides

Three of the four DNA testing vendors, 23andMe, FamilyTreeDNA, and recently, Ancestry, attempt to phase your ethnicity DNA, meaning to assign it to one parental “side” or the other – both in total and on each chromosome.

Here’s Ancestry’s SideView, where your DNA is estimated to belong to parent 1 and parent 2. I detailed how to determine which side is which, here, and while that article was written specifically pertaining to Ancestry’s SideView, the technique is relevant for all the vendors who attempt to divide your DNA into parents, a technique known as phasing.

I say “attempt” because phasing may or may not be accurate, meaning the top chromosome may not always be parent 1, and the bottom chromosome may not always be chromosome 2.

Here’s an example at 23andMe.

See the two yellow segments. They are both assigned as Native. I happen to know one is from the mother and one is from the father, yet they are both displayed on the “top” chromosome, which one would interpret to be the same parent.

I am absolutely positive this is not the case because this is a close family member, and I have the DNA of the parent who contributed the Native segment on chromosome 1, on the top chromosome. That parent does not have a Native segment on chromosome 2 to contribute. So that Native segment had to be contributed by the other parent, but it’s also shown on the top chromosome.

The DNA segments circled in purple belong together on the same “side” and were contributed to the tester by the same parent. The Native segment on chromosome 2 abuts a purple African segment, suggesting perhaps that the ancestor who contributed that segment was mixed between those ethnicities. In the US, that suggests enslavement.

The other African segments, circled, are shown on the second chromosome in each pair.

To be clear, parent 1 is not assigned by the vendors to either mother or father and will differ by person. Your parent 1, or the parent on the top chromosome may be your mother and another person’s parent 1 may be their father.

As shown in this example, parents can vary by chromosome, a phenomenon known as “strand swap.” Occasionally, the DNA can even be swapped within a chromosome assignment.

You can, however, get an idea of the division of your DNA at any specific location. As shown above, you can only have a maximum of two populations of DNA on any one chromosome location.

In our example above, this person’s majority ancestry is European (blue.) On each chromosome where we find a minority segment, the opposite chromosome in the same location is European, meaning blue.

Let’s look at another example.

At FamilyTreeDNA, the person whose ethnicity painting is shown below has a Native American (pink) ancestor on their father’s side. FamilyTreeDNA has correctly phased or identified their Native segments as all belonging to the second chromosome in each pair.

Looking at chromosome 18, for example, most of their father’s chromosome is Native American (pink). The other parent’s chromosome is European (dark blue) at those same locations.

If one of the parents was of one ethnicity, and the other parent is a completely different ethnicity, then one bar of each chromosome would be all pink, for example, and one would be entirely blue, representing the other ethnicity.

Phasing ethnicity or populations to maternal and paternal sides is not foolproof, and each chromosome is phased individually.

Ethnicity can, in some cases, give you a really good idea of what you’re dealing with in terms of heritage and endogamy.

If someone had an Ashkenazi Jewish father and European mother, for example, one copy of each chromosome would be yellow (Ashkenazi Jewish), and one would be blue (European.)

However, if each of their parents were half European Jewish and half European (not Jewish), then their different colored segments would be scattered across their entire set of chromosomes.

In this case, both of the tester’s parents are mixed – European Jewish (green) and Western Europe (blue.) We know both parents are admixed from the same two populations because in some locations, both parents contributed blue (Western Europe), and in other locations, both contributed Jewish (green) segments.

Both MyHeritage and Ancestry provide a secondary tool that’s connected to ethnicity, but different and generally in more recent times.

Ancestry’s DNA Communities

While your ethnicity may not point to anything terribly exciting in terms of endogamy, Genetic Communities might. Ancestry says that a DNA Community is a group of people who share DNA because their relatives recently lived in the same place at the same time, and that communities are much smaller than ethnicity regions and reach back only about 50-300 years.

Based on the ancestors’ locations in the trees of me and my matches, Ancestry has determined that I’m connected to two communities. In my case, the blue group is clearly my father’s line. The orange group could be either parent, or even a combination of both.

My endogamous Brethren could be showing up in Maryland, Pennsylvania, and Ohio, but it’s uncertain, in part, because my father’s ancestral lines are found in Virginia, West Virginia, and Maryland too.

These aren’t useful for me, but they may be more useful for fully endogamous people, especially in conjunction with ethnicity.

My Acadian cousin’s European ethnicity isn’t informative.

However, viewing his DNA Communities puts his French heritage into perspective, especially combined with his match surnames.

I wrote about DNA Communities when it was introduced with the name Genetic Communities, here.

MyHeritage’s Genetic Groups

MyHeritage also provides a similar feature that shows where my matches’ ancestors lived in the same locations as mine.

One difference, though, is that testers can adjust their ethnicity results confidence level from high, above, to low, below where one of my Genetic Groups overlaps my ethnicity in the Netherlands.

You can also sort your matches by Genetic Groups.

The results show you not only who is in the group, but how many of your matches are in that group too, which provides perspective.

I wrote about Genetic Groups, here.

Next, let’s look at how endogamy affects your matches.

Matches

The number of matches that a person has who is from an entirely endogamous community and a person with no endogamy may be quite different.

FamilyTreeDNA provides a Family Matching feature that triangulates your matches and assigns them to your paternal or maternal side by using known matches that you have linked to their profile cards in your tree. You must link people for the Family Matching feature known as “bucketing” to be enabled.

The people you link are then processed for shared matches on the same chromosome segment(s). Triangulated individuals are then deposited in your maternal, paternal, and both buckets.

Obviously, your two parents are the best people to link, but if they haven’t tested (or uploaded their DNA file from another vendor) and you have other known relatives, link them using the Family Tree tab at the top of your personal page.

I uploaded my Ancestry V4 kit to use as an example for linking. Let’s pretend that’s my sister. If I had not already linked my Ancestry V4 kit to “my sister’s” profile card, I’d want to do that and link other known individuals the same way. Just drag and drop the match to the correct profile card.

Note that a full or half sibling will be listed as such at FamilyTreeDNA, but an identical twin will show as a potential parent/child match to you. You’re much more likely to find a parent than an identical twin, but just be aware.

I’ve created a table of FamilyTreeDNA bucketed match results, by category, comparing the number of matches in endogamous categories with non-endogamous.

Total Matches Maternal Matches Paternal Matches Both % Both % DNA Unassigned
100% Jewish 34,637 11,329 10,416 4,806 13.9 23.3
100% Jewish 32,973 10,700 9,858 4,606 14 23.7
100% Jewish 32,255 9,060 10,970 3,892 12 25.8
75% Jewish 24,232 11,846 Only mother linked Only mother linked Only mother linked
100% Acadian 8093 3826 2299 1062 13 11
100% Acadian 7828 3763 1825 923 11.8 17
Not Endogamous 6760 3845 1909 13 0.19 14.5
Not Endogamous 7723 1470 3317 6 0.08 38
100% Native American 1,115 Unlinked Unlinked Unlinked
100% Native American 885 290 Unknown Can’t calculate without at least one link on both sides

The 100% Jewish, Acadian, and Not Endogamous testers both have linked their parents, so their matches, if valid (meaning not identical by chance, which I discussed here,) will match them plus one or the other parent.

One person is 75% Jewish and has only linked their Jewish mother.

The Native people have not tested their parents, and the first Native person has not linked anyone in their tree. The second Native person has only linked a few maternal matches, but their mother has not tested. They are seeking their father.

It’s very difficult to find people who are fully Native as testers. Furthermore, Native people are under-sampled. If anyone knows of fully Native (or other endogamous) people who have tested and linked their parents or known relatives in their trees, and will allow me to use their total match numbers anonymously, please let me know.

As you can see, Jewish, Acadian, and Native people are 100% endogamous, but many more Jewish people than Native people have tested, so you CAN’T judge endogamy by the total number of matches alone.

In fact, in order:

  • Fully Jewish testers have about 4-5 times as many matches as the Acadian and Non-endogamous testers
  • Acadian and Non-endogamous testers have about 5-6 times as many matches as the Native American testers
  • Fully Jewish people have about 30 times more matches than the Native American testers

If a person’s endogamy with a particular population is only on their maternal or paternal side, they won’t have a significant number of people related to both sides, meaning few people will fall into the “Both” bucket. People that will always be found in the ”Both” bucket are full siblings and their descendants, along with descendants of the tester, assuming their match is linked to their profiles in the tester’s tree.

In the case of our Jewish testers, you can easily see that the “Both” bucket is very high. The Acadians are also higher than one would reasonably expect without endogamy. A non-endogamous person might have a few matches on both sides, assuming the parents are not related to each other.

A high number of “Both” matches is a very good indicator of endogamy within the same population on both parents’ sides.

The percentage of people who are assigned to the “Both” bucket is between 11% and 14% in the endogamous groups, and less than 1% in the non-endogamous group, so statistically not relevant.

As demonstrated by the Native people compared to the Jewish testers, the total number of matches can be deceiving.

However, being related to both parents, as indicated by the “Both” bucket, unless you have pedigree collapse, is a good indicator of endogamy.

Of course, if you don’t know who your relatives are, you can’t link them in your tree, so this type of “hunt” won’t generally help people seeking their close family members.

However, you may notice that you’re matching people PLUS both of their parents. If that’s the case, start asking questions of those matches about their heritage.

A very high number of total matches, as compared to non-endogamous people, combined with some other hints might well point to Jewish heritage.

I included the % DNA Unassigned category because this category, when both parents are linked, is the percentage of matches by chance, meaning the match doesn’t match either of the tester’s parents. All of the people with people listed in “Both” categories have linked both of their parents, not just maternal and paternal relatives.

Matching Location at MyHeritage

MyHeritage provides a matching function by location. Please note that it’s the location of the tester, but that may still be quite useful.

The locations are shown in the most-matches to least-matches order. Clicking on the location shows the people who match you who are from that location. This would be the most useful in situations where recent immigration has occurred. In my case, my great-grandfather from the Netherlands arrived in the 1860s, and my German ancestors arrived in the 1850s. Neither of those groups are endogamous, though, unless it would be on a village level.

AutoClusters

Let’s shift to Genetic Affairs, a third-party tool available to everyone.

Using their AutoCluster function, Genetic Affairs clusters your matches together who match both each other and you.

This is an example of the first few clusters in my AutoCluster. You can see that I have several colored clusters of various sizes, but none are huge.

Compare that to the following endogamous cluster, sample courtesy of EJ Blom at Genetic Affairs.

If your AutoCluster at Genetic Affairs looks something like this, a huge orange blob in the upper left hand corner, you’re dealing with endogamy.

Please also note that the size of your cluster is also a function of both the number of testers and the match threshold you select. I always begin by using the defaults. I wrote about using Genetic Affairs, here.

If you tested at or transferred to MyHeritage, they too license AutoClusters, but have optimized the algorithm to tease out endogamous matches so that their Jewish customers, in particular, don’t wind up with a huge orange block of interrelated people.

You won’t see the “endogamy signature” huge cluster in the corner, so you’re less likely to be able to discern endogamy from a MyHeritage cluster alone.

The commonality between these Jewish clusters at MyHeritage is that they all tend to be rather uniform in size and small, with lots of grey connecting almost all the blocks.

Grey cells indicate people who match people in two colored groups. In other words, there is often no clear division in clusters between the mother’s side and the father’s side in Jewish clusters.

In non-endogamous situations, even if you can’t identify the parents, the clusters should still fall into two sides, meaning a group of clusters for each parent’s side that are not related to each other.

You can read more about Genetic Affairs clusters and their tools, here. DNAGedcom.com also provides a clustering tool.

Endogamous Relationships

Endogamous estimated relationships are sometimes high. Please note the word, “sometimes.”

Using the Shared cM Project tool relationship chart, here, at DNAPainter, people with heavy endogamy will discover that estimated relationships MAY be on the high side, or the relationships may, perhaps, be estimated too “close” in time. That’s especially true for more distant relationships, but surprisingly, it’s not always true. The randomness of inheritance still comes into play, and so do potential unknown relatives. Hence, the words “may” are bolded and underscored.

Unfortunately, it’s often stated as “conventional wisdom” that Jewish matches are “always” high, and first cousins appear as siblings. Let’s see what the actual data says.

At DNAPainter, you can either enter the amount of shared DNA (cM), or the percent of shared DNA, or just use the chart provided.

I’ve assembled a compilation of close relationships in kits that I have access to or from people who were generous enough to share their results for this article.

I’ve used Jewish results, which is a highly endogamous population, compared with non-endogamous testers.

The “Jewish Actual” column reports the total amount of shared DNA with that person. In other words, someone to their grandparent. The Average Range is the average plus the range from DNAPainter. The Percent Difference is the % difference between the actual number and the DNAPainter average.

You’ll see fully Jewish testers, at left, matching with their family members, and a Non-endogamous person, at right, matching with their same relative.

Relationship Jewish Actual Percent Difference than Average Average -Range Non-endogamous Actual Percent Difference than Average
Grandparent 2141 22 1754 (984-2482) 1742 <1 lower
Grandparent 1902 8.5 1754 (984-2482) 1973 12
Sibling 3039 16 2613 (1613-3488) 2515 3.5 lower
Sibling 2724 4 2613 (1613-3488) 2761 5.5
Half-Sibling 2184 24 1759 (1160-2436) 2127 21
Half-Sibling 2128 21 1759 (1160-2436) 2352 34
Aunt/Uncle 2066 18.5 1741 (1201-2282) 1849 6
Aunt/Uncle 2031 16.5 1741 (1201-2282) 2097 20
1C 1119 29 866 (396-1397) 959 11
1C 909 5 866 (396-1397) 789 9 lower
1C1R 514 19 433 (102-980) 467 8
1C1R 459 6 433 (102-980) 395 9 lower

These totals are from FamilyTreeDNA except one from GEDMatch (one Jewish Half-sibling).

Totals may vary by vendor, even when matching with the same person. 23andMe includes the X segments in the total cMs and also counts fully identical segments twice. MyHeritage imputation seems to err on the generous side.

However, in these dozen examples:

  • You can see that the Jewish actual amount of DNA shared is always more than the average in the estimate.
  • The red means the overage is more than 100 cM larger.
  • The percentage difference is probably more meaningful because 100 cM is a smaller percentage of a 1754 grandparent connection than compared to a 433 cM 1C1R.

However, you can’t tell anything about endogamy by just looking at any one sample, because:

  • Some of the Non-Endogamous matches are high too. That’s just the way of random inheritance.
  • All of the actual Jewish match numbers are within the published ranges, but on the high side.

Furthermore, it can get more complex.

Half Endogamous

I requested assistance from Jewish genealogy researchers, and a lovely lady, Sharon, reached out, compiled her segment information, and shared it with me, granting permission to share with you. A HUGE thank you to Sharon!

Sharon is half-Jewish via one parent, and her half-sibling is fully Jewish. Their half-sibling match to each other at Ancestry is 1756 cM with a longest segment of 164 cM.

How does Jewish matching vary if you’re half-Jewish versus fully Jewish? Let’s look at 21 people who match both Sharon and her fully Jewish half-sibling.

Sharon shared the differences in 21 known Jewish matches with her and her half-sibling. I’ve added the Relationship Estimate Range from DNAPainter and colorized the highest of the two matches in yellow. Bolding in the total cM column shows a value above the average range for that relationship.

Total Matching cMs is on the left, with Longest Segment on the right.

While this is clearly not a scientific study, it is a representative sample.

The fully Jewish sibling carries more Jewish DNA, which is available for other Jewish matches to match as a function of endogamy (identical by chance/population), so I would have expected the fully Jewish sibling to match most if not all Jewish testers at a higher level than the half-Jewish sibling.

However, that’s not universally what we see.

The fully Jewish sibling is not always the sibling with the highest number of matches to the other Jewish testers, although the half-Jewish tester has the larger “Longest Segment” more often than not.

Approximately two-thirds of the time (13/21), the fully Jewish person does have a higher total matching cM, but about one-third of the time (8/21), the half-Jewish sibling has a higher matching cM.

About one-fourth of the time (5/21), the fully Jewish sibling has the longest matching segment, and about two-thirds of the time (13/21), the half-Jewish sibling does. In three cases, or about 14% of the time, the longest segment is equal which may indicate that it’s the same segment.

Because of endogamy, Jewish matches are more likely to have:

  • Larger than average total cM for the specific relationship
  • More and smaller matching segments

However, as we have seen, neither of those are definitive, nor always true. Jewish matches and relationships are not always overestimated.

Ancestry and Timber

Please note that Ancestry downweights some matches by removing some segments using their Timber algorithm. Based on my matches and other accounts that I manage, Ancestry does not downweight in the 2-3rd cousin category, which is 90 cM and above, but they do begin downweighting in the 3-4th cousin category, below 90 cM, where my “Extended Family” category begins.

If you’ve tested at Ancestry, you can check for yourself.

By clicking on the amount of DNA you share with your match on your match list at Ancestry, shown above, you will be taken to another page where you will be able to view the unweighted shared DNA with that match, meaning the amount of DNA shared before the downweighting and removal of some segments, shown below.

Given the downweighting, and the information in the spreadsheet provided by Sharon, it doesn’t appear that any of those matches would have been in a category to be downweighted.

Therefore, for these and other close matches, Timber wouldn’t be a factor, but would potentially be in more distant matches.

Endogamous Segments

Endogamous matches tend to have smaller and more segments. Small amounts of matching DNA tend to skew the total DNA cM upwards.

How and why does this happen?

Ancestral DNA from further back in time tends to be broken into smaller segments.

Sometimes, especially in endogamous situations, two smaller segments, at one time separated from each other, manage to join back together again and form a match, but the match is only due to ancestral segments – not because of a recent ancestor.

Please note that different vendors have different minimum matching cM thresholds, so smaller matches may not be available at all vendors. Remember that factors like Timber and imputation can affect matching as well.

Let’s take a look at an example. I’ve created a chart where two ancestors have their blue and pink DNA broken into 4 cM segments.

They have children, a blue child and a pink child, and the two children, shown above, each inherited the same blue 4 cM segment and the same pink 4 cM segment from their respective parents. The other unlabeled pink and blue segments are not inherited by these two children, so those unlabeled segments are irrelevant in this example.

The parents may have had other children who inherited those same 4 cM labeled pink and blue segments as well, and if not, the parents’ siblings were probably passing at least some of the same DNA down to their descendants too.

The blue and pink children had children, and their children had children – for several generations.

Time passed, and their descendants became an endogamous community. Those pink and blue 4 cM segments may at some time be lost during recombination in the descendants of each of their children, shown by “Lost pink” and “Lost blue.”

However, because there is only a very limited amount of DNA within the endogamous community, their descendants may regain those same segments again from their “other parent” during recombination, downstream.

In each generation, the DNA of the descendant carrying the original blue or pink DNA segment is recombined with their partner. Given that the partners are both members of the same endogamous community, the two people may have the same pink and/or blue DNA segments. If one parent doesn’t carry the pink 4 cM segment, for example, their offspring may receive that ancestral pink segment from the other parent.

They could potentially, and sometimes do, receive that ancestral segment from both parents.

In our example, the descendants of the blue child, at left, lost the pink 4 cM segment in generation 3, but a few generations later, in generation 11, that descendant child inherited that same pink 4 cM segment from their other parent. Therefore, both the 4 cM blue and 4 cM pink segments are now available to be inherited by the descendants in that line. I’ve shown the opposite scenario in the generational inheritance at right where the blue segment is lost and regained.

Once rejoined, that pink and blue segment can be passed along together for generations.

The important part, though, is that once those two segments butt up against each other again during recombination, they aren’t just two separate 4 cM segments, but one segment that is 8 cM long – that is now equal to or above the vendors’ matching threshold.

This is why people descended from endogamous populations often have the following matching characteristics:

  • More matches
  • Many smaller segment matches
  • Their total cM is often broken into more, smaller segments

What does more, smaller segments, look like, exactly?

More, Smaller Segments

All of our vendors except Ancestry have a chromosome browser for their customers to compare their DNA to that of their matches visually.

Let’s take a look at some examples of what endogamous and non-endogamous matches look like.

For example, here’s a screen shot of a random Jewish second cousin match – 298 cM total, divided into 12 segments, with a longest segment of 58 cM,

A second Jewish 2C with 323 cM total, across 19 segments, with a 69 cM longest block.

A fully Acadian 2C match with 600 cM total, across 27 segments, with a longest segment of 69 cM.

A second Acadian 2C with 332 cM total, across 20 segments, with a longest segment of 42 cM.

Next, a non-endogamous 2C match with 217 cM, across 7 segments, with a longest segment of 72 cM.

Here’s another non-endogamous 2C example, with 169 shared cM, across 6 segments, with a longest segment of 70 cM.

Here’s the second cousin data in a summary table. The take-away from this is the proportion of total segments

Tester Population Total cM Longest Block Total Segments
Jewish 2C 298 58 12
Jewish 2C 323 69 19
Acadian 2C 600 69 27
Acadian 2C 332 42 20
Non-endogamous 2C 217 72 7
Non-endogamous 2C 169 70 6

You can see more examples and comparisons between Native American, Jewish and non-endogamous DNA individuals in the article, Concepts – Endogamy and DNA Segments.

I suspect that a savvy mathematician could predict endogamy based on longest block and total segment information.

Lara Diamond, a mathematician, who writes at Lara’s Jewnealogy might be up for this challenge. She just published compiled matching and segment information in her Ashkenazic Shared DNA Survey Results for those who are interested. You can also contribute to Laura’s data, here.

Endogamy, Segments, and Distant Relationships

While not relevant to searching for close relatives, heavily endogamous matches 3C and more distant, to quote one of my Jewish friends, “dissolve into a quagmire of endogamy and are exceedingly difficult to unravel.”

In my own Acadian endogamous line, I often simply have to label them “Acadian” because the DNA tracks back to so many ancestors in different lines. In other words, I can’t tell which ancestor the match is actually pointing to because the same DNA segments or segments is/are carried by several ancestors and their descendants due to founder effect.

The difference with the Acadians is that we can actually identify many or most of them, at least at some point in time. As my cousin, Paul LeBlanc, once said, if you’re related to one Acadian, you’re related to all Acadians. Then he proceeded to tell me that he and I are related 137 different ways. My head hurts!

It’s no wonder that endogamy is incredibly difficult beyond the first few generations when it turns into something like multi-colored jello soup.

“Are Your Parents Related?” Tool

There’s another tool that you can utilize to determine if your parents are related to each other.

To determine if your parents are related to each other, you need to know about ROH, or Runs of Homozygosity (ROH).

ROH means that the DNA on both strands or copies of the same chromosome is identical.

For a few locations in a row, ROH can easily happen just by chance, but the longer the segment, the less likely that commonality occurs simply by chance.

The good news is that you don’t need to know the identity of either of your parents. You don’t need either of your parent’s DNA tests – just your own. You’ll need to upload your DNA file to GEDmatch, which is free.

Click on “Are your parents related?”

GEDMatch analyzes your DNA to see if any of your DNA, above a reasonable matching threshold, is identical on both strands, indicating that you inherited the exact same DNA from both of your parents.

A legitimate match, meaning one that’s not by chance, will include many contiguous matching locations, generally a minimum of 500 SNPs or locations in a row. GEDmatch’s minimum threshold for identifying identical ancestral DNA (ROH) is 200 cM.

Here’s my result, including the graphic for the first two chromosomes. Notice the tiny green bars that show identical by chance tiny sliver segments.

I have no significant identical DNA, meaning my parents are not related to each other.

Next, let’s look at an endogamous example where there are small, completely identical segments across a person’s chromosome

This person’s Acadian parents are related to each other, but distantly.

Next, let’s look at a Jewish person’s results.

You’ll notice larger green matching ROH, but not over 200 contiguous SNPs and 7 cM.

GEDMatch reports that this Jewish person’s parents are probably not related within recent generations, but it’s clear that they do share DNA in common.

People whose parents are distantly related have relatively small, scattered matching segments. However, if you’re seeing larger ROH segments that would be large enough to match in a genealogical setting, meaning multiple greater than 7 cM and 500 SNPs,, you may be dealing with a different type of situation where cousins have married in recent generations. The larger the matching segments, generally, the closer in time.

Blogger Kitty Cooper wrote an article, here, about discovering that your parents are related at the first cousin level, and what their GEDMatch “Are Your Parents Related” results look like.

Let’s look for more clues.

Surnames

There MAY be an endogamy clue in the surnames of the people you match.

Viewing surnames is easier if you download your match list, which you can do at every vendor except Ancestry. I’m not referring to the segment data, but the information about your matches themselves.

I provided instructions in the recent article, How to Download Your DNA Match Lists and Segment Files, here.

If you suspect endogamy for any reason, look at your closest matches and see if there is a discernable trend in the surnames, or locations, or any commonality between your matches to each other.

For example, Jewish, Acadian, and Native surnames may be recognizable, as may locations.

You can evaluate in either or both of two ways:

  • The surnames of your closest matches. Closest matches listed first will be your default match order.
  • Your most frequently occurring surnames, minus extremely common names like Smith, Jones, etc., unless they are also in your closest matches. To utilize this type of matching, sort the spreadsheet in surname order and then scan or count the number of people with each surname.

Here are some examples from our testers.

Jewish – Closest surname matches.

  • Roth
  • Weiss
  • Goldman
  • Schonwald
  • Levi
  • Cohen
  • Slavin
  • Goodman
  • Sender
  • Trebatch

Acadian – Closest surname matches.

  • Bergeron
  • Hebert
  • Bergeron
  • Marcum
  • Muise
  • Legere
  • Gaudet
  • Perry
  • Verlander
  • Trombley

Native American – Closest surname matches.

  • Ortega
  • Begay
  • Valentine
  • Hayes
  • Montoya
  • Sun Bear
  • Martin
  • Tsosie
  • Chiquito
  • Yazzie

You may recognize these categories of surnames immediately.

If not, Google is your friend. Eliminate common surnames, then Google for a few together at a time and see what emerges.

The most unusual surnames are likely your best bets.

Projects

Another way to get some idea of what groups people with these surnames might belong to is to enter the surname in the FamilyTreeDNA surname search.

Go to the main FamilyTreeDNA page, but DO NOT sign on.

Scroll down until you see this image.

Type the surname into the search box. You’ll see how many people have tested with that surname, along with projects where project administrators have included that surname indicating that the project may be of interest to at least some people with that surname.

Here’s a portion of the project list for Cohen, a traditional Jewish surname.

These results are for Muise, an Acadian surname.

Clicking through to relevant surname projects, and potentially contacting the volunteer project administrator can go a very long way in helping you gather and sift information. Clearly, they have an interest in this topic.

For example, here’s the Muise surname in the Acadian AmerIndian project. Two great hints here – Acadian heritage and Halifax, Nova Scotia.

Repeat for the balance of surnames on your list to look for commonalities, including locations on the public project pages.

Locations

Some of the vendor match files include location information. Each person on your match list will have the opportunity at the vendor where they tested to include location information in a variety of ways, either for their ancestors or themselves.

Where possible, it’s easiest to sort or scan the download file for this type of information.

Ancestry does not provide or facilitate a match list, but you can still create your own for your closest 20 or 30 matches in a spreadsheet.

MyHeritage provides common surname and ancestral location information for every match. How cool is that!

Y DNA, Mitochondrial DNA, and Endogamy

Haplogroups for both Y and mitochondrial DNA can indicate and sometimes confirm endogamy. In other cases, the haplogroup won’t help, but the matches and their location information just might.

FamilyTreeDNA is the only vendor that provides Y DNA and mitochondrial DNA tests that include highly granular haplogroups along with matches and additional tools.

23andMe provides high-level haplogroups which may or may not be adequate to pinpoint a haplogroup that indicates endogamy.

Of course, only males carry Y DNA that tracks to the direct paternal (surname) line, but everyone carries their mother’s mitochondrial DNA that represents their mother’s mother’s mother’s, or direct matrilineal line.

Some haplogroups are known to be closely associated with particular ethnicities or populations, like Native Americans, Pacific Islanders, and some Jewish people.

Haplogroups reach back in time before genealogy and can give us a sense of community that’s not available by either looking in the mirror or through traditional records.

This Native American man is a member of high-level haplogroup Q-M242. However, some men who carry this haplogroup are not Native, but are of European or Middle Eastern origin.

I entered the haplogroup in the FamilyTreeDNA Discover tool, which I wrote about, here.

Checking the information about this haplogroup reveals that their common ancestor descended from an Asian man about 30,000 years ago.

The migration path in the Americans explains why this person would have an endogamous heritage.

Our tester would receive a much more refined haplogroup if he upgraded to the Big Y test at FamilyTreeDNA, which would remove all doubt.

However, even without additional testing, information about his matches at FamilyTreeDNA may be very illuminating.

The Q-M242 Native man’s Y DNA matches men with more granular haplogroups, shown above, at left. On the Haplogroup Origins report, you can see that these people have all selected the “US (Native American)” country option.

Another useful tool would be to check the public Y haplotree, here, and the public mitochondrial tree here, for self-reported ancestor location information for a specific haplogroup.

Here’s an example of mitochondrial haplogroup A2 and a few subclades on the public mitochondrial tree. You can see that the haplogroup is found in Mexico, the US (Native,) Canada, and many additional Caribbean, South, and Central American countries.

Of course, Y DNA and mitochondrial DNA (mtDNA) tell a laser-focused story of one specific line, each. The great news, if you’re seeking information about your mother or father, the Y is your father’s direct paternal (surname) line, and mitochondrial is your mother’s direct matrilineal line.

Y and mitochondrial DNA results combined with ethnicity, autosomal matching, and the wide range of other tools that open doors, you will be able to reveal a great deal of information about whether you have endogamous heritage or not – and if so, from where.

I’ve provided a resource for stepping through and interpreting your Y DNA results, here, and mitochondrial DNA, here.

Discover for Y DNA Only

If you’re a female, you may feel left out of Y DNA testing and what it can tell you about your heritage. However, there’s a back door.

You can utilize the Y DNA haplogroups of your closest autosomal matches at both FamilyTreeDNA and 23andMe to reveal information

Haplogroup information is available in the download files for both vendors, in addition to the Family Finder table view, below, at FamilyTreeDNA, or on your individual matches profile cards at both 23andMe and FamilyTreeDNA.

You can enter any Y DNA haplogroup in the FamilyTreeDNA Discover tool, here.

You’ll be treated to:

  • Your Haplogroup Story – how many testers have this haplogroup (so far), where the haplogroup is from, and the haplogroup’s age. In this case, the haplogroup was born in the Netherlands about 250 years ago, give or take 200 years. I know that it was 1806 or earlier based on the common ancestor of the men who tested.
  • Country Frequency – heat map of where the haplogroup is found in the world.
  • Notable Connections – famous and infamous (this haplogroup’s closest notable person is Leo Tolstoy).
  • Migration Map – migration path out of Africa and through the rest of the world.
  • Ancient Connections – ancient burials. His closest ancient match is from about 1000 years ago in Ukraine. Their shared ancestor lived about 2000 years ago.
  • Suggested Projects – based on the surname, projects that other matches have joined, and haplogroups.
  • Scientific Details – age estimates, confidence intervals, graphs, and the mutations that define this haplogroup.

I wrote about the Discover tool in the article, FamilyTreeDNA DISCOVER Launches – Including Y DNA Haplogroup Ages.

Endogamy Tools Summary Tables

Endogamy is a tough nut sometimes, especially if you’re starting from scratch. In order to make this topic a bit easier and to create a reference tool for you, I’ve created three summary tables.

  • Various endogamy-related tools available at each vendor which will or may assist with evaluating endogamy
  • Tools and their ability to detect endogamy in different groups
  • Tools best suited to assist people seeking information about unknown parents or grandparents

Summary of Endogamy Tools by Vendor

Please note that GEDMatch is not a DNA testing vendor, but they accept uploads and do have some tools that the testing vendors do not.

 Tool 23andMe Ancestry FamilyTreeDNA MyHeritage GEDMatch
Ethnicity Yes Yes Yes Yes Use the vendors
Ethnicity Painting Yes + segments Yes, limited Yes + segments Yes
Ethnicity Phasing Yes Partial Yes No
DNA Communities No Yes No No
Genetic Groups No No No Yes
Family Matching aka Bucketing No No Yes No
Chromosome Browser Yes No Yes Yes Yes
AutoClusters Through Genetic Affairs No Through Genetic Affairs Yes, included Yes, with subscription
Match List Download Yes, restricted # of matches No Yes Yes Yes
Projects No No Yes No
Y DNA High-level haplogroup only No Yes, full haplogroup with Big Y, matching, tools, Discover No
Mitochondrial DNA High-level haplogroup only No Yes, full haplogroup with mtFull, matching, tools No
Public Y Tree No No Yes No
Public Mito Tree No No Yes No
Discover Y DNA – public No No Yes No
ROH No No No No Yes

Summary of Endogamous Populations Identified by Each Tool

The following chart provides a guideline for which tools are useful for the following types of endogamous groups. Bolded tools require that both parents be descended from the same endogamous group, but several other tools give more definitive results with higher amounts of endogamy.

Y and mitochondrial DNA testing are not affected by admixture, autosomal DNA or anything from the “other” parent.

Tool Jewish Acadian Anabaptist Native Other/General
Ethnicity Yes No No Yes Pacific Islander
Ethnicity Painting Yes No No Yes Pacific Islander
Ethnicity Phasing Yes, if different No No Yes, if different Pacific Islander, if different
DNA Communities Yes Possibly Possibly Yes Pacific Islander
Genetic Groups Yes Possibly Possibly Yes Pacific Islander
Family Matching aka Bucketing Yes Yes Possibly Yes Pacific Islander
Chromosome Browser Possibly Possibly Yes, once segments or ancestors identified Possibly Pacific Islander, possibly
Total Matches Yes, compared to non-endogamous No No No No, unknown
AutoClusters Yes Yes Uncertain, probably Yes Pacific Islander
Estimated Relationships High Not always Sometimes No Sometimes Uncertain, probably
Relationship Range High Possibly, sometimes Possibly Possibly Possibly Pacific Islander, possibly
More, Smaller Segments Yes Yes Probably Yes Pacific Islander, probably
Parents Related Some but minimal Possibly Uncertain Probably similar to Jewish Uncertain, Possibly
Surnames Probably Probably Probably Not Possibly Possibly
Locations Possibly Probably Probably Not Probably Probably Pacific Islander
Projects Probably Probably Possibly Possibly Probably Pacific Islander
Y DNA Yes, often Yes, often No Yes Pacific Islander
Mitochondrial DNA Yes, often Sometimes No Yes Pacific Islander
Y public tree Probably not alone No No Yes Pacific Islander
MtDNA public tree Probably not No No Yes Pacific Islander
Y DNA Discover Yes Possibly Probably not, maybe projects Yes Pacific Islander

Summary of Endogamy Tools to Assist People Seeking Unknown Parents and Grandparents

This table provides a summary of when each of the various tools can be useful to:

  • People seeking unknown close relatives
  • People who already know who their close relatives are, but are seeking additional information or clues about their genealogy

I considered rating these on a 1 to 10 scale, but the relative usefulness of these tools is dependent on many factors, so different tools will be more or less useful to different people.

For example, ethnicity is very useful if someone is admixed from different populations, or even 100% of a specific endogamous population. It’s less useful if the tester is 100% European, regardless of whether they are seeking close relatives or not. Conversely, even “vanilla” ethnicity can be used to rule out majority or recent admixture with many populations.

Tools Unknown Close Relative Seekers Known Close Relatives – Enhance Genealogy
Ethnicity Yes, to identify or rule out populations Yes
Ethnicity Painting Yes, possibly, depending on population Yes, possibly, depending on population
Ethnicity Phasing Yes, possibly, depending on population Yes, possibly, depending on population
DNA Communities Yes, possibly, depending on population Yes, possibly, depending on population
Genetic Groups Possibly, depending on population Possibly, depending on population
Family Matching aka Bucketing Not if parents are entirely unknown, but yes if one parent is known Yes
Chromosome Browser Unlikely Yes
AutoClusters Yes Yes, especially at MyHeritage if Jewish
Estimated Relationships High Not No
Relationship Range High Not reliably No
More, Smaller Segments Unlikely Unlikely other than confirmation
Match List Download Yes Yes
Surnames Yes Yes
Locations Yes Yes
Projects Yes Yes
Y DNA Yes, males only, direct paternal line, identifies surname lineage Yes, males only, direct paternal line, identifies and correctly places surname lineage
Mitochondrial DNA Yes, both sexes, direct matrilineal line only Yes, both sexes, direct matrilineal line only
Public Y Tree Yes for locations Yes for locations
Public Mito Tree Yes for locations Yes for locations
Discover Y DNA Yes, for heritage information Yes, for heritage information
Parents Related – ROH Possibly Less useful

Acknowledgments

A HUGE thank you to several people who contributed images and information in order to provide accurate and expanded information on the topic of endogamy. Many did not want to be mentioned by name, but you know who you are!!!

If you have information to add, please post in the comments.

_____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

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 Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research