Mitochondrial DNA: How Do I Know if I’m a Candidate to Receive a New Haplogroup?

New haplogroups, which are phylogenetic tree branches, are formed with periodic updates to the Mitotree. In the November 2025 Mitotree release, 12,773 new branches were formed, and an amazing 67,000+ people received a new haplogroup. Haplogroups are relevant for both genealogy and more distant information about your direct matrilineal ancestor and their origins.

Are You a Candidate to Receive a New Haplogroup?

Lots of people have asked how one might know if they are a candidate to receive a new haplogroup, or tree branch, or why they didn’t, so let’s talk about the three ways your haplogroup could potentially change.

To follow along, if you have taken the full sequence mitochondrial DNA test, sign in to your FamilyTreeDNA account and click on Discover on the mtDNA Results and Tools page.

After clicking on Discover, you’ll see the mtDNA Discover sidebar menu on the left. Click on Scientific Details

You Have Private Variants

The first reason you might be a candidate to receive a new haplogroup is that you have private variants. Private variants are mutations that have not already been used to form a haplogroup, hence, they are still private to you.

To see if you have private variants, click on Scientific Details on the sidebar, then on the Variants Tab.

Click any image to enlarge

You’ll see a list of haplogroups under the Placement column header. Your assigned haplogroup is noted by the red square, J1c2f in this instance.

At the top is an “F” number, which is your Haplotype. Haplotype numbers are randomly assigned, and everyone with exactly the same mitochondrial sequence will have the same haplotype number.

You can see your haplogroup and haplotype matches on your match list. If you match both, both blue circles will be checked.

In this example, you can see that beside the haplotype number, which I’ve blurred, in the Name column, it says “No private variants.” This means that all of this person’s mutations have been used to assign them to haplogroup J1c2f and the haplogroups upstream of J1c2f.

This tester cannot match anyone any more closely than the exact same haplogroup, J1c2f, and the exact same Haplotype number, which means they match exactly and have no private variants. This means there’s no material available to form a new haplogroup.

I’ve written about mitochondrial haplogroups, haplotypes and haplotype clusters, in two articles.

Let’s look at an example of someone who does have Private Variants.

This tester, who is a member of haplogroup C4c1h has one private variant, T13879g. When another tester in haplogroup C3c1h also has this variant, or mutation, they are candidates to form a new branch in the next Mitotree release.

Keep in mind that not every private variant will become a haplogroup, based on several scientific factors.

So, while our haplogroup J1c2f tester is NOT a candidate to form a new haplogroup branch due to no private variants, our C4c1h person with one high-quality private variant is.

However, private variants are only one way in which a new haplogroup might form. There are others.

The Tree Splits Upstream

Sometimes the tree splits upstream.

Looking further upstream, or back in time from haplogroup J1c2f, we see that two of the foundation haplogroups that formed J1c2f are defined by more than one mutation.

Haplogroup J1 was formed using both C462T and G3010A, bracketed in red.

Haplogroup J was formed using seven different mutations, beginning with C295T and continuing to the bottom of the screen capture, bracketed in purple.

As more people test, eventually a new tester may have C462T, but NOT G3010A, AND their downstream mutations are different too. In other words, we’re not looking at a reversal for 3010, but at a completely different haplogroup with a split at C462T as its defining mutation.

In this case, the new branch would receive the new haplogroup name, and the existing branch would remain the same. But what if this scenario happened far up the tree and changed our understanding of this portion of the tree?

In that case it’s still very unlikely that your haplogroup would change, based on existing naming structures. FamilyTreeDNA makes every effort to NOT rename existing haplogroups when these types of branching situations occur.

The Branch is Renamed

Sometimes the existing tree structure is clarified, prompting branch renaming.

Let’s look at an earlier structure of this portion of haplogroup J1c2f.

In the earlier version of the Mitotree, shown above, you can see that two mutations define haplogroup J1c2, two mutations define J1c, and there’s a haplogroup called J1c’g that is constructed using a reversal at location 152.

In the November 2025 release of the Mitotree, this exact same portion of the tree looks different. The tester is still haplogroup J1c2f, but the upstream structure has changed.

  • J1c2 is now defined by only one mutation, A188G.
  • A new haplogroup has been formed: J1c2+16519. Notice the Weight column at far right. This mutation’s confidence weighting is very low, so this haplogroup is a good candidate for refinement in future trees.

Now look at J1c where we see the same thing occurring.

  • J1c is now comprised of just T14798C.
  • A new haplogroup, J1c+185 has formed. It has a weight of 17, still in the red zone, but more confident than J1c2+16519.

Looking further down the original placement table, we see J1c’g, which is a collapsed haplogroup based on a double reversal at C152T!!. It’s gone in the most current version of the tree. You can see that haplogroup J1c’g only had a weight of 1, so it was a good candidate to be refined, eliminated, or assigned elsewhere in the tree.

None of these changes affect haplogroup J1c2f itself, meaning the tester’s assigned haplogroup. Unless they actually look at their haplogroup mutations, they won’t see any difference. This person was and still is assigned to J1c2f.

However, if someone was assigned to J1 or J1c2 before, they might have a new haplogroup name. If they were assigned to J1c’g, they definitely have a new haplogroup name.

These scenarios are repeated throughout the tree, and may be exactly why you receive a new haplogroup, even without having any private variants.

Older Versus Newer

Haplogroups that form as a result of your private variants tend to be newer, or closer in time, but not always. You never know when just the right person will test to split an upstream branch!

Regardless, all new haplogroups help refine the tree, and all refinements are important. Branches that form in more recent generations are often the most useful for genealogy.

However, that’s not always the case. “Newer” versus “older” is sometimes relative (pardon the pun.) Let’s say that you are trying to figure out which of two sisters, or cousins, born in the 1600s, you descend from.

You may desperately need an “older” haplogroup that will divide the branches of the ancestral tree.

Or maybe you want to know whether your ancestor came from Scotland or Germany, so you may need an older haplogroup yet.

Want to know if they were Celtic or from a different culture? An older haplogroup fills in cultural and genealogical blanks that no other type of testing can reach. Haplogroups pierce the veil of time.

OK, So What Should I Check?

Even if you don’t receive a new haplogroup when a new Mitotree version is released, you’re certainly not out of luck.

Some of your matches may have received a new haplogroup, further refining the genetic tree, causing them to cluster together. This should correlate with the genealogical tree.

For example, I’m desperate to identify the wife of my ancestor, who has been known affectionately for years as H2a1. She is now haplogroup H2a1ay1, but I still don’t know her name.

The haplogroup formation date range extends back to around 1820, which is slightly late, but certainly not far off either. The dates for the genetic Time Tree, and the genealogical tree may not align exactly, but the date ranges generally do. Mutations don’t occur on an exact schedule.

However, matches for the tester who represents H2a1 (now H2a1ay1) have been nicely narrowed down to two other full sequence testers. Both have this exact same haplogroup, and one of them also has the exact same haplotype. The balance of her matches are now in a more distant haplogroup.

Now I can focus on the two matches with the same haplogroup.

Even though the trees of these three testers don’t seem to intersect, some genealogical sleuthing tells me a lot.

The ancestor of one of the haplogroup matches was born in 1741, a Quaker, in Chester, Pennsylvania, and died in 1818.

The ancestor of the haplogroup plus haplotype match lived in the same Virginia County as my ancestor, and they were both Quakers, whose families attended the same church.

So we have:

  • Haplogroup match – Born a Quaker in 1741 in Chester, PA.
  • Haplogroup AND haplotype match – Lived in Frederick Co., VA in the 1780s and attended same Quaker church as the tester’s ancestor

These new haplogroups, both of the tester’s haplogroup matches, and others whose new haplogroup shows they are more distant, are critical to refining my search.

I’m so close to identifying H2a1ay1 and her parents that I can smell it!

Any self-respecting genealogist would end this article right here and get busy!

I’m outta here!!!

Don’t stop with checking your own haplogroup. Review any changes to people on your match list and view the Match Time Tree, even if you didn’t receive a new haplogroup.

While receiving a new haplogroup is exciting, sometimes refinements among people around you can be equally, if not more, important and informative.

_____________________________________________________________

Share the Love!

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

Subscribe!

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.

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

Mitotree Sprouts 12,773 NEW Branches and Includes Ancient DNA

FamilyTreeDNA has released the brand-new Mitotree, version 2025.10.24!

Mitotree has sprouted 12,773 new branches, a 30% increase in size in just seven months!

Chart courtesy of FamilyTreeDNA, click to enlarge

The new Mitotree has a total of 53,856 branches utilizing 342,000 full sequence samples from multiple sources:

  • 267,000 from FamilyTreeDNA full sequence tests
  • 50,000 from GenBank and other third-party sequences
  • 5,000 from the 1000 Genomes Project samples
  • 2,000 from miscellaneous academic studies

Care was taken to curate studies and samples from rare and underrepresented populations.

When the Mitotree is updated, new branches aren’t just tacked onto the ends of branches like leaves. That’s because new samples may split existing branches far upstream of the tips of the branches, so the entire branch may have shifted or been divided into two.

Therefore, with each new Mitotree version, the entire tree is rerun, which means a new branching structure, and the possibility of a new or refined haplogroup for every customer.

Sample Evaluation

The samples tested at FamilyTreeDNA conform to stringent quality control measures, but quality control and alignment for samples originating in other facilities are unknown.

Samples from third-party academic sources are reviewed by the R&D team for potential issues before inclusion.

Ancient Samples

The November 2025 Mitotree now incorporates more than 10,000 ancient DNA samples from archaeological sites around the world.

These samples are displayed on the mtDNA Discover Time Tree, shown above, with brown lines and little trowels.

Additionally, you’ll find ancient samples displayed on the following Discover pages:

  • Your individual Match Time Tree with your mitochondrial DNA matches when you click through to Discover from your account at FamilyTreeDNA
  • Migration Map
  • Ancient Connections
  • Classic Tree

Mouse over the sample names to read about each one.

Ancient DNA (aDNA) samples are uniquely important, because they allow us to put a stake in the ground (pardon the pun) at a specific place and time when and where that individual lived.

Ancient samples also pose unique challenges due to their age and DNA degradation. The resulting sequence may be incomplete due to lower coverage. The sequence may also contain post-mortem damage artifacts caused by a process known as deamination. On the other hand, these artifacts can also be valuable in authenticating the ancient origin of the DNA, and that the sequence is not a result of contemporary contamination.

FamilyTreeDNA cannot resequence the ancient sample itself, so must rely on the results produced by the institution that processed the ancient DNA sample.

Fortunately, the FamilyTreeDNA R&D team has developed methodologies to compensate for these issues, identify which samples can be used to construct the tree, and which samples can be reliably placed on the tree. Only the highest-quality ancient samples can be fully included in the tree construction, meaning they are allowed to split and form new branches.

In this version, more than 2,000 ancient samples were utilized for the tree, which resulted in over 500 new branches that would otherwise not have formed. In future versions, more ancient samples will be evaluated and added.

There are now more ancient samples available for mitochondrial DNA than for the Y-DNA tree. Both males and females have mitochondrial DNA, but only males have a Y chromosome. There are more ancient samples in the queue to be added to the next Mitotree version.

Innovation

Mitochondrial DNA, by its very nature, includes challenges not present in either autosomal or Y-DNA.

Innovative tree-building methodologies have been devised and implemented, including new methods for handling complex scenarios where multiple variants conflict with each other. In some cases, mutations that exhibit unstable behavior in a certain part of the tree are ignored when analyzing that portion of the tree. This, and much more, will be detailed in a future white paper.

One size does not fit all, and the team has been very focused on identifying the best fit for a variety of scenarios. These methodologies and refinements have enabled the formation of more than 4,000 branches by using previously excluded private variants.

How the New Mitotree Affects You

Watch your email for a new haplogroup notification!

Further refinement of the Mitotree, either for you or your matches, can provide you with new genealogical clues.

A new haplogroup may regroup your matches to be more genealogically relevant, and your TMRCA (Time to Most Recent Common Ancestor) estimates may have been refined.

Everyone who received their mtDNA Full Sequence test result before October 24, 2025, but whose Mitotree haplogroup was still analyzing should receive their new haplogroup within the next few days.

Many customers who have already received their Mitotree haplogroup will also receive an updated haplogroup due to changes in the tree structure.

Customers who get a Mitotree haplogroup for the first time and customers who receive an updated Mitotree haplogroup should receive automatic email notifications.

The excitement isn’t restricted only to people with new haplogroups.

Everyone should check their haplogroup results on mtDNA Discover to see whether they match any of the newly included ancient DNA samples, if their haplogroup age has changed, or if their matches on the Match Time Tree have been regrouped.

You just never know what, or who, might be waiting for you!

Great Time to Upgrade

If you or a family member took one of the earlier, partial (HVRI or HVRII only) mitochondrial DNA tests, or you’ve received a haplogroup estimate from an autosomal test at another company, now, with the holiday sales, is the perfect time to upgrade an earlier test or order a new one.

A full sequence mitochondrial DNA test is required for your most refined haplogroup, your closest matches, including ancient DNA, and the Match Time Tree, at mtDNA Discover.

If you’re taken a mitochondrial DNA test, but are uncertain about which level, sign on to your FamilyTreeDNA account and check your dashboard.

If you’ve taken the full sequence test, both the Plus and Full squares will be pink. If the Full square is grey, click on it to upgrade.

You can’t benefit from all of these new advances without a full sequence test, and you’ll match other full sequence testers who share the same ancestor at some point in time.

Mitochondrial DNA has the potential, due to tracking the direct matrilineal line, to break through brick walls that no other test can touch!

Do you have a brick wall that needs to fall?

_____________________________________________________________

Share the Love!

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

Subscribe!

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.

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

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

The Mystery of the Blue Fugates and Smiths: A Study in Blue Genes and Pedigree Collapse

The story of the Blue Fugates, an Appalachian family, is quite interesting, from a genetic perspective, a genealogical perspective, and a genetic genealogy perspective.

Who Are the Blue Fugates?

Martin Fugate, supposedly an orphan from France, and his bride, Elizabeth Smith, who had married by 1840, have long been attributed as the progenitors of the Blue Fugate Family of Troublesome Creek, in and around Perry County, Kentucky.

Their descendants were known as “The Blue Fugates” and also “The Blue People of Kentucky” because some of their children and descendants carried a recessive autosomal genetic trait, Methemoglobinemia.

Methemoglobinemia causes the skin to appear blue due to an oxygen deficiency in the red blood cells. Some people only exhibit this characteristic, or even just blue tinges in their fingernails and lips, when they are cold or agitated, such as when infants cry. Yet others are very, very blue.

Inheritance

In order for someone to exhibit the autosomal recessive trait of blueness due to Methemoglobinemia, they must inherit a copy of the gene from BOTH PARENTS. That’s why this trait is so rare.

  • If the parents have only one copy each, they are carriers and will not have the condition themselves.
  • If one parent carries either one or two copies, and the other parent does NOT carry a copy, their offspring CANNOT carry two copies of the mutation and will not be blue.
  • If both parents carry a copy, and both parents pass their copy on to their offspring, the offspring will probably exhibit some level of blueness – from just a tinge when they are cold, ill or or upset, to very, very blue.

I’m not a physician, so I’m not delving into the medical specifics of Methemoglobinemia, but suffice it to say that levels of 10-20% of methemoglobin in the blood produce blue skin, higher levels can produce more severe medical conditions, and levels beneath that may not be visually detectible.

What’s important for the genealogy aspect of this story is that both parents must carry a copy AND pass their copy on for the condition to express in their offspring.

We’ve learned a lot since the 1800s when this was first observed in various members of the Fugate family in Perry County, KY, and since the 1960s when this phenomenon was first studied in the Fugate family and their descendants. To be clear, there are also references to the blue Combs and blue Ritchies in and around Perry County – but the common factor is that they have ancestors that descend from the Fugate family AND the Smith family ancestors, both.

During my research, I’ve proven some of what was initially accepted as fact was incorrect – and I’d like to correct the record. Bonus points too, because it’s just such a great genealogy story!

My Interest

I’ve been inordinately interested in the Fugate family for a long time – but not because of their famous blueness.

The Fugate family has been found for more than 225 years alongside my Cook, Claxton, Campbell, and Dobkins families. First, in Russell County, VA, where Josiah Fugate was granted land along Sword’s Creek in 1801 that adjoined Harry Smith, Richard Smith, and others, including my brick-wall ancestor, Joel Cook. Keep in mind that we have never discovered the birth surname of Joel’s wife or Joel’s parents.

Joel’s daughter, Sarah, married James Claxton about 1799 or 1800 in Russell County, and in February of 1802, James Claxton and Zachariah Fugate, among others, were ordered to view and lay out a new road. They were clearly neighbors, living on the same road, and knew each other well. We don’t know who James’ parents were either.

The Fugates first lived adjacent to the Cook, Riley, Stephens, and Claxton families on Mockason Creek in Russell County, then later migrated with the same group of families to Claiborne County where they lived along the Powell River near the Lee County, VA line, and are very closely associated with the Dobkins and Campbell lines.

Sometime between 1802 and 1805, several Russell County families moved 110 miles down the mountain range and settled together on the Powell River in Claiborne County, TN.  About the same time, others from the same cluster moved to what would eventually become Perry County, KY.

In 1805, the Fugates were ordered as road hands on the north side of Wallen’s Ridge in Claiborne County, the part that would become Hancock County in the 1840s, along with James Claxton and several Smiths.

In 1808, James Claxton witnessed a deed to Henley Fugate and John Riley.

The unsubstantiated family rumor, repeated as fact but with no source, has always been that William Fugate married the sister of my John Campbell. If that were true, tracking the Fugates would help me track my Campbells – yet another brick wall. Hence, my early interest in the Fugate family. Until now, I’ve never solved any part of that puzzle.

In 1827, in Claiborne County, Henry Cook, road overseer, is assigned John Riley, Henly Fugate, William Fugate, Fairwick Claxton (son of James who had died in 1815), and others. These families continued to be allied, living close to each other.

In 1842, William Fugate (1799-1855), born to William Fugate and Sarah Jane Stephens in Russell County, is involved in the estate of John Campbell, born about 1772, who had died in 1838. John Campbell was the husband of Jane “Jenny” Dobkins, daughter of Jacob Dobkins (1751-1835).

William Fugate of Claiborne County signed a deposition in 1851 saying he came to Claiborne County, TN, in 1826. Claiborne County is rugged terrain, located on the south side of the Cumberland Gap, where Virginia, Tennessee, and Kentucky intersect.

In 1853, both William Fugate and Jehiel Fugate are neck-deep in lawsuits surrounding the estate of Jacob Dobkins, who died in 1835, lived on Powell River, and whose daughters married John Campbell and his brother George Campbell

I recently discovered that this William Fugate was born about 1799 in Russell County, VA, and according to his son’s death certificate, William’s wife was Nancy Riley, which makes a lot of sense, given the proximity of these families. I must admit, I’m glad to solve this, but I’m also disappointed that he wasn’t married to John Campbell’s sister.

So, why does any of this matter in the Blue Fugate story?

In part, because I knew decades ago that Martin Fugate, of the Kentucky Blue Fugates, was not an orphan from France who had somehow made his way to the eastern shores of Maryland, then to Perry County, KY by 1820 when he supposedly received a land grant. That land grant date doesn’t square with Martin’s birth year of 1820 either, nor his marriage about 1840, both of which are substantiated by the census.

You can see from the information gleaned from Russell County that the Fugate family was there well before 1800. In fact, a Martin Fugate is shown on the 1789 tax list and other Fugates were there earlier, as early as 1771, according to extracted Russell County records in the book “The Fugate Family of Russell County, Virginia” by David Faris. The Fugate descendants continued to press on westward from there. Fugate, unlike Smith, Cook, and even Campbell, is not a common surname.

“Orphan” stories are often early ways that people said “I don’t know”, without saying, “I don’t know where he came from”, so they speculated and said “maybe he was an orphan.” Then that speculation was eventually passed on as fact.

That might have been happening in Perry County in the 1960s, but in Claiborne County in the 1980s, family members were telling me, “Martin waren’t no orphan,” and would roll their eyes and sigh with great exasperation. You could tell this was far from the first time they had had to combat that story. To be clear, the Fugate family lived down along Little Sycamore Creek with my Estes, Campbell and other ancestral families. In the 1980s, I was finding the oldest people possible and talking to them.

Some records in Russell County, where the Fugates of Perry County, KY, and the Fugates of Claiborne County, TN, originated, did and do exist, so could have been researched in the 1960s, but you would have had to know where to look. No one back then knew that the Perry County Fugates originated in Russell County, so they wouldn’t have known to look there. Research wasn’t easy. If they had known to look in Russell County, they would have had to travel there in person to review records. Early records exist in Perry County, too, but in the 1960s, not even the census was available, and people simply didn’t remember back to the early to mid-1800s.

Truthfully, no one would ever have doubted those early stories that had been handed down. They were revered, in all families, and treated as gospel. Those stories were the only connection they had to their ancestors – and the generations inbetween who passed them on. Nope, no one was going to question what Grandpa or Uncle Joe said.

So, in the 1960s, when the Blue Fugates in Perry and adjacent Breathitt County, KY were first studied by Dr. Cawein and his nurse, Ruth Pendergrass, they gathered oral family history and constructed a family pedigree from that information. They documented who was blue from first-hand eye-witness accounts – which would only have stretched back into the late 1800s, best case.

It probably never occurred to anyone to validate or verify earlier information that was provided. Plus, it would have been considered rude. After all, they weren’t genealogists, and they were trying to solve a medical mystery. The information they collected did not conflict with what was known about the disease and how it was transmitted, so they had no reason to doubt its historical accuracy.

The Mystery of the Blue Fugates?

The Blue Fugates were a family renowned for their blue skin – at least some of them had blue skin. That’s part of what makes this story so interesting.

Originally, it was believed that only one progenitor couple was involved, Martin Fugate and his wife, Elizabeth Smith, but now we know there were two. Maybe I should say “at least two.”

Martin Fugate and his bride, Elizabeth Smith, whose first known child was born in 1841, according to the 1850 census, are progenitors of the Blue Fugate Family of Troublesome Creek, but they aren’t the only progenitors.

Martin was not shown in the Perry County, KY 1840 census, but two Zachariah Fugates are present, 8 Fugate families are found in neighboring Breathitt County, more than a dozen in Russell County and surrounding counties in Virginia, and four, including two William Fugates, in Claiborne County, TN. The younger of the two lived next door to John Dobkins, son of deceased Jacob Dobkins.

Martin Fugate (c1820-1899) of Perry County and his second cousin, Zachariah Fugate (1816-1864), who each married a Smith sister, are both progenitors of the Blue Fugates through their common ancestor, their great-grandfather, Martin Fugate, who was born in 1725 and died in 1803 in Russell County, VA.

Obviously, if Martin (c1820-1899) had a Fugate second cousin who also lived in Perry County, Martin wasn’t an orphan. That knowledge is due to more recently available information, like census and other data – and that’s part of what I want to correct.

In 1948, Luke Combs, from Perry County, KY, took his sick wife to the hospital, but Luke’s blueness caused the medical staff to focus on him instead, thinking he was experiencing a medical emergency. He wasn’t. His skin was just blue. In 1974, Dr Charles H. Behlen II said, ‘Luke was just as blue as Lake Louise on a cool summer day.’ The Blue Fugates were “discovered” by the rest of the world, thanks to Luke, but they were nothing new to local people, many of whom did not welcome the notoriety.

In the 1960s, hematologist Madison Cawein III, with the assistance of Ruth Pendergrass, studied 189 members of the extended Fugate family, treated their symptoms, and published his findings. He included a pedigree chart, but not everyone was keen on cooperating with Dr. Cawein’s research project.

The Fugate family history collected for the study was based on two things:

  • Personal knowledge of who respondents knew was blue
  • Remembered oral history beyond the reach of personal knowledge.

That remembered oral history reported that Martin Fugate and Elizabeth Smith’s youngest son, Zachariah Fugate (born in 1871), married his mother’s (older) sister, Mary Smith, (born about 1820), and had a family. I’ve added the dates and information in parentheses, or they would have immediately known that marriage was impossible. Or, more directly, even if they married when Zachariah was 14, Mary would have been 70 years old, and they were certainly not going to produce offspring. This is the second piece of information I want to correct. That marriage never happened, although people were accurate that:

  • Martin Fugate and his wife, Elizabeth Smith, did have a son named Zachariah Fugate
  • One Zachariah Fugate did marry Mary Smith, sister of Elizabeth Smith

It’s just that they were two different Zachariah Fugates, born 75 years apart. Same name confusion strikes again.

I constructed this census table of Martin Fugate with Elizabeth Smith, and Zachariah Fugate with Mary Smith. They lived next door to each other in Perry County – and it seemed that every family reused the same “honoring” names for their children – and had been doing such for generations.

In the 1960s, when the information was being compiled for Dr. Cawein, the census and other documents that genealogists rely on today were not readily available.

Furthermore, genetically, for the mystery Dr. Cawein was attempting to solve, it didn’t really matter, because it was still a Smith female marrying a Fugate male. I know that it made no difference today, but he wouldn’t have known that then. To track down the source of the blueness, he needed to identify who was blue and as much about their ancestors as possible.

The Zachariah Fugate (1816-1864) who married Elizabeth Smith’s sister, Mary Smith, was Martin Fugate’s second cousin by the same name, Zachariah. Both Martin (c1820-1899) and his second cousin, Zachariah (c1816-1864), married to Smith sisters, had blue children, which helps cement the fact that the responsible genes were passed down through BOTH the Fugate and Smith lines, and weren’t just random mutations or caused by environmental or other factors.

Proof

In case you’re wondering exactly how I confirmed that Martin and Zachariah did indeed marry Elizabeth and Mary Smith – their children’s birth and death records confirmed it. These records correlate with the census.

Unlike most states, Kentucky has some pre-1900 birth and death records.

Wilson Fugate’s birth in February, 1855 was recorded, naming both of his parents, Martin Fugate and Elizabeth Smith.

Martin Fugate and Elizabeth Smith’s son, Henley or Hendley, died in 1920, and his death certificate gave the names of both parents. Betty is a nickname for Elizabeth.

On the same page with Wilson Fugate’s birth, we find a birth for Zachariah Fugate and Mary Smith, too.

Hannah Fugate was born in December 1855.

Zachariah Fugate and Mary Smith’s son, Zachariah died in 1921, and his death certificate gives his parents as Zach Fugate and Polly Smith, a nickname for Mary.

There are more death records for children of both sets of parents.

Both couples, Martin Fugate and Elizabeth Smith, and Zachariah Fugate and Mary Smith, are progenitors of the Blue Fugate family.

Of Martin’s 10 known children, 4 were noticeably “blue” and lived long, healthy lives. At least two of Zachariah’s children were blue as well.

Some people reported that Martin, himself, had deep blue skin. If so, then both of his parents would have carried that genetic mutation and passed it to him.

Unfortunately, color photography didn’t exist when Martin (c1820-1899), lived, so we don’t know for sure. For Martin’s children to exhibit blue skin, they would have had to inherit a copy of the gene from both parents, so we know that Martin’s wife, Elizabeth, also inherited the mutation from one of her parents. Ditto for Zachariah Fugate and Mary Smith. The chances of two families who both carry such a rare mutation meeting AND having two of their family members marry are infinitesimally small.

Dr. Cawein’s Paper

In 1964, Dr. Cawein published his findings, but only with a pedigree chart with no names. What was included was an explanation about how remote and deep the hills and hollows were, and that out-migration was almost impossible, explaining the propensity to marry cousins.

Legend:

  • Measured – Found to have elevated methemoglobin
  • Measured – Found to have decreased methemoglobin
  • Not measured – Reported to be “blue”
  • Measured – Found to be normal

Cawein further stated that data was collected by interviewing family members who personally knew the individual in question and could say if they were actually blue.

Cawein erroneously reported that “Martin Fugate was an orphan born about 1800, landed in Maryland, obtained a land grant in Perry County, KY in 1820, and married a local gal. From 1820 to about 1930, the population consisted of small, isolated groups living in creek valleys and intermarriage was quite common.” Bless his heart.

Later, geneticist Ricky Lewis wrote about the Blue Fugates, sharing, among other things, the provenance of that “blue” family photo that circulates on the internet, revealing that it is a composite that was assembled and colorized back in 1982. She also erroneously stated that, “after extensive inbreeding in the isolated community—their son married his aunt, for example—a large pedigree of “blue people” of both sexes arose.” Bless her heart too.

Dr. Lewis is incorrect that their son married his aunt – but she’s right that intermarriage between the families is responsible for the blue descendants. In colonial America, and elsewhere, cousin marriages were fairly common – everyplace. You married who you saw and knew. You saw your family and neighbors, who were generally your extended family. No left-handed apology needed.

Pedigree collapse, sharing the same ancestors in multiple places in your tree, is quite common in genealogy, as is endogamy among isolated populations.

Today, things have changed somewhat. People move into and out of an area. The younger generation moves away a lot more and has for the past 100+ years. Most people know their first cousins, but you could easily meet a second or third cousin and never know you were related.

While early stories reported that Martin Fugate (c1820-1899) was an orphan from France, mysteriously appearing in Kentucky around 1820, later genealogical evidence as well as genetic research proves that Martin Fugate was actually born about 1820, in Russell County, VA and his ancestors, over several generations, had followed the typical migration path across Virginia into Kentucky.

We’ve also proven that Martin’s son, Zachariah (born 1871) was not the Zachariah who married Elizabeth Smith’s sister, Mary, who was 50 years old when Zachariah was born.

What else do we know about these families?

The Back Story

Compared to the Smith story, the Fugate story was “easy.”

Don’t laugh, but I spent several days compiling information and charting this in a way I could see and understand in one view.

I hesitate to share this, but I’m going to because it’s how I think. I also put together a very basic Fugate tree at Ancestry, here. Many children and siblings are missing. I was just trying to get this straight in my mind.

Click to enlarge any image

This spreadsheet is color-coded:

  • The text of each lineage has a specific color. For example, Fugates are blue.
  • Some people (or couples) are found in multiple descendants’ lines and are duplicated in the tree. Duplicated people also have a cell background color. For example, Mahala Richey (Ritchey, Ritchie) is highlighted yellow. James and Alexander Richey have green text and apricot background because they are duplicated.
  • The generation of parents who had blue children is marked with black boxes and the label “Blue Kids.”
  • Only the blue kids for this discussion are listed below those couples.
  • The bluest person was Luna Fugate (1886-1964).
  • While Luna’s husband, John Stacey, also descended from the Smith/Combs line, only one of their children expressed the blue trait. That child’s lips turned blue when they cried. John and Luna were actually related in three ways. Yes, my head hurts.
  • The last known “blue” person was Luna Fugate’s great-grandchild, whose name I’ve obfuscated.

Ok, let’s start with the blue Fugates on our spreadsheet. You’ll probably want to follow along on the chart.

Martin Fugate (1725-1803) and wife Sarah, had several children, but only two, the ones whose grandchildren married Smith sisters are known to have had blue children.

On our chart, you can see that Martin (1725-1803) is blue, and so is Son 1, William Fugate and Sarah Stephens, along with Son 2, Benjamin Fugate and Hannah Devers. Both William and Benjamin are mentioned in Martin’s estate in 1803 in Russell County, VA.

Two generations later, Martin Fugate (c1820-1899) and Elizabeth Smith had four blue children, and Zachariah Fugate (c1816-1864) and Mary Smith had at least two blue children. Furthermore, Zachariah Fugate’s sister, Hannah (1811-1877), married James Monroe Richie.

The Richey’s are green, and you can see them on both the left and right of the chart. Hannah’s husband descended from the same Richey line that Elizabeth Smith did. It was no surprise when their child, Mahala Ritchie (1854-1922), married Levi Fugate, to whom she was related three ways, they became the parents of a blue child. Their daughter, Luna Fugate, was known as “the Bluest of the Blue Fugates.”

Mahala Ritchie (1854-1922) could have inherited her blue gene (or genes) from either her mother Hannah Fugate, or her father, James Monroe Ritchie, or both. We don’t know if Hannah was blue or not.

We do know that Mahala married Levi Fugate, her third cousin through the Fugate line, and her third and fourth cousin also through the Richie and Grigsby lines, respectively. This is the perfect example of pedigree collapse.

You can see the purple Grigsby lines in the center and to the right of the pedigree chart too, with Benjamin Grigsby, highlighted in blue, being common to both lineages.

Zachariah Fugate (1816-1864) and Mary Smith had at least two blue sons, but I am not tracking them further. Suffice it to say that Blue John married Letha Smith, his first cousin, the granddaughter of Richard Smith and Nancy Elitia Combs. Lorenzo, “Blue Anze”, married a Fugate cousin, so it’s no surprise that Zachariah and Mary were also progenitor couples of the Blue Fugates.

Martin’s son, Levi Fugate, married Mahala Ritchie, mentioned above, and had Luna Fugate who would have been personally known to Dr. Cawein. Luna, pictured above, at left, was known as the bluest of the Blue Fugates.

Luna married John Stacey who some thought wasn’t related to Luna, so it was confusing why they had one child that was slightly blue. However, John turns out to be Luna’s second cousin, third cousin once removed and first cousin once removed through three different lines. His great-grandparents were Richard Smith and Nancy Combes. Since one of their children had a slight blue tinge, John, while not visibly blue himself, clearly carried the blue gene.

Where Did the Blue Gene Come From?

The parents of Elizabeth Smith and Mary Smith were Richard Smith and Nancy (Eletia) Combs. His Smith ancestors include both the Richeys and Caldwells.

James Richey (1724-1888) married Margaret Caldwell (1729-1802) and his father, Alexander Richey (1690-1749) married Jeanne Caldwell (1689-1785). While the Caldwell females weren’t closely related, Jeanne was the daughter of Joseph Alexander Caldwell (1657-1730) and Jane McGhie, and Margaret Caldwell (1729-1802) was the great-granddaughter of that couple. The Caldwells are shown in magenta, with both Richey/Caldwell couples shown as duplicates. The Richey are highlighted in apricot, and the Caldwell’s with a light grey background. It was difficult to show how these lines connect, so that’s at the very top of the pedigree chart.

When just viewing the Smith-Combs line, it’s easier to view in the Ancestry pedigree.

The Smith, Richey, Combs, Grigsby, and Caldwell lines are all repeated in different locations in the trees, such as with Hannah Fugate’s husband. These repeated ancestors make it almost impossible for us to determine where in the Smith ancestral tree that blue gene originated.

We don’t know which of these ancestral lines actually contributed the blue gene.

Can We Figure Out Where the Blue Gene Came From?

How could we potentially unravel this mystery?

We know for sure that the blue gene in the Fugate side actually descends from Martin Fugate who was born in 1725, or his wife, Sarah, whose surname is unknown, because their two great-grandchildren, Martin (c1820-1899) and Zachariah (1816-1864) who both married Smith sisters had blue children. For those two intervening generations between Martin Fugate (1725-1803) and those two great-grandsons, that blue gene was quietly being passed along, just waiting for a blue Fugate gene carrier to meet another blue gene carrier. They found them in the Smith sisters.

None of Martin (1725-1803) and Sarah’s other children were known to have had any blue children or descendants. So either they didn’t carry the blue gene, or they didn’t marry someone else who did – that we know of.

We can’t tell on the Smith side if the blue gene descends from the Smith, Richey, Grigsby or Caldwell ancestors, or maybe even an unknown ancestor.

How can we narrow this down?

If a Fugate in another geographic location married someone from one of these lineages, say Grigsby, for example, and they had blue offspring, and neither of them shared any of the other lineages, then we could narrow the blue gene in the Smith line to the Grigsby ancestor.

Unfortunately, in Perry and surrounding counties in Kentucky, that would be almost impossible due to intermarriage and pedigree collapse. Even if you “think you know” that there’s no connection through a third line, given the deep history and close proximity of the families, the possibility of unknown ancestry or an unexpected parent is always a possibility.

Discover

While the blue gene is not connected to either Y-DNA or mitochondrial DNA, we do have the Fugate’s Y-DNA haplogroup and the Smith sisters’ mitochondrial DNA.

Y-DNA

The Big Y-700 haplogroup for the Martin Fugate (c1820-1899) line is R-FTA50432, which you can see, here..

You can see the Blue Fugate Family by clicking on Notable Connections.

If you’re a male Fugate descendant who descends from anyone other than Martin Fugate (c1820-c1899), and you take a Big Y test, you may well discover a new haplogroup upstream of Martin (c1820-1899) that represents your common Fugate ancestor.

If you descend from Martin, you may find youself in either of the two haplogroups shown for Martin’s descendants, or you could split the line to form a new haplogroup.

We don’t have the mitochondrial DNA of Martin Fugate (c1820-1899), which would be the mitochondrial DNA of his mother, Nancy Noble. We also don’t have the the mtDNA of Mary (Polly) Wells, the mother of Zachariah Fugate (c1816-1864). If you descend from either of these women in a direct matrilineal line, through all women, please take a mitochondrial DNA test and reach out. FamilyTreeDNA will add it as a Notable Connection.

We do, however, have the mitochondrial DNA of Elizabeth and Mary Smith

Mitochondrial DNA of Elizabeth and Mary Smith

The mitochondrial DNA of both Elizabeth and Mary Smith follows their mother’s line – Nancy Combs through Nancy (Eletia?) Grigsby. Nancy’s mother is unknown, other than the possible first name of Margaret.

Nancy Grigsby’s descendant is haplogroup K1a61a1, which you can see here.

The Blue Fugates show under Notable Connections.

The Smith sisters’ haplogroup, K1a61a1, tells us immediately that their ancestor is European, eliminating other possibilities.

The time tree on Discover is quite interesting

Haplogroup K1a61a1 was formed about the year 1400. Descendants of this haplogroup are found in the UK, Scotland, England, several unknown locations, and one person who selected Native American, which is clearly in error. Haplogroup K is not Native American.

By focusing on the haplotype clusters, identified by the F numbers in the elongated ovals, our tester may be able to identify the mother of Nancy Grigsby, or upstream lineages that they can work back downstream to find someone who married Thomas Grigsby.

This story is far from over. In fact, a new chapter may just be beginning.

If you’re a Fugate, or a Fugate descendant, there’s still lots to learn, even if autosomal DNA is “challenging,” to say the least, thanks to pedigree collapse. Testing known females lineages can help us sort which lines are which, and reveal their hidden stories.

Other resources if you want to read more about the Fugates: The Blue People of Troublesome Creek, Fugates of Kentucky: Skin Bluer than Lake Louise, Those Old Kentucky Blues: An Interrupted Case Study, and Finding the Famous Paintings of the Blue People of Kentucky.

_____________________________________________________________

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 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

Discover’s Ancient Connections – How Are You Related?

When FamilyTreeDNA released the new Mitotree, they also introduced their new mtDNA Discover tool, which is a series of 13 reports about each haplogroup, including one titled Ancient Connections.

Ancient Connections shows you ancient relatives from your direct matrilineal line through a mitochondrial DNA test or through a Y-DNA (preferably Big Y-700) test.

Ancient Connections help you connect the present to the past based on archaeological excavations around the world and DNA sequencing of remains. Ancient Connections links you through your DNA to ancient people, cultures, and civilizations that would be impossible to discover any other way. You don’t have to wonder if it’s accurate, or which line it came from, because you know based on the test you took. Discover’s Ancient Connections track the journey of your ancestors and relatives.

Ancient Connections can be very exciting – and it’s easy to get swept away on a wave of jubilation.

Are those people your ancestors, or relatives, or what? How do you know? How can you figure it out?

So let me just answer that question generally before we step through the examples, so you can unveil your own connections.

  • You are RELATED to both Ancient and Notable Connections. Notable Connections are famous or infamous people who have lived more recently, and their relatives have been tested to identify their haplogroups.
  • It’s VERY unlikely that Ancient Connections are your direct ancestors – but someone in the line that you share IS your ancestor.
  • Many factors enter into the equation of how you are related, such as the haplogroup(s), the timeframe, and the location.
  • The sheer number of people who were living at any specific time makes it very unlikely that any one person with that haplogroup actually was your direct ancestor. They are much more likely to be your distant cousin.

Factors such as whether you share the same haplogroup, similar locations, and the timeframe make a huge difference. Everyone’s situation is different with each Ancient Connection.

Ok, are you ready for some fun???

Let’s find out how to leverage these tools.

Ancient Connections

Ancient connections are fun and can also be quite useful for genealogy.

In this article, I’m going to use a mitochondrial DNA example because full sequence testers at FamilyTreeDNA just received their new Mitotree haplogroup. mtDNA Discover was released with Mitotree, so it’s new too. However, the evaluation process is exactly the same for Y-DNA.

Everyone’s results are unique, so your mileage absolutely WILL vary. What we are going to learn here is a step-by-step analytical process to make sure you’re hearing the message from your ancestors – and interpreting it correctly.

To learn about your new mitochondrial DNA haplogroup and haplotype, read the articles:

Radegonde Lambert

Let’s start with an Acadian woman by the name of Radegonde Lambert. She’s my ancestor, and I wrote about her years ago in the article, Radegonde Lambert (1621/1629-1686/1693), European, Not Native.

At the time, that article caused a bit of a kerfluffle, along with the article, Haplogroup X2b4 is European, Not Native American, because Radegonde’s X2b4 haplogroup had been interpreted by some to mean that her matrilineal ancestors were Native American.

That often happens when a genealogical line abruptly ends and hits a brick wall. What probably began with “I wonder if…”, eventually morphed into “she was Native,” when, in fact, she was not. In Radegonde’s case, it didn’t help any that her haplogroup was X2b4, and some branches of base haplogroup X2 are in fact Native, specifically X2a, However, all branches of X2 are NOT Native, and X2b, which includes X2b4, is not.

The Acadians were French people who established a colony in what is now Nova Scotia in the 1600s. They did sometimes intermarry with the Native people, so either Native or European heritage is always a possibility, and that is exactly why DNA testing is critically important. Let’s just say we’ve had more than one surprise.

I always reevaluate my own work when new data becomes available, so let’s look to see what’s happening with Radegonde Lambert now, with her new haplogroup and mtDNA Discover.

Sign on and Identify Your Haplogroup

You can follow along here, or sign on to your account at FamilyTreeDNA.

The first step is to take note of your new Mitotree haplogroup.

Your haplogroup badge is located near the bottom right of your page after signing in.

The tester who represents Radegonde Lambert has a Legacy Haplogroup of X2b4 and has been assigned a new Mitotree haplogroup of X2b4g.

Click Through to Discover

To view your personal Discover information, click on the Discover link on your dashboard.

You can simply enter a haplogroup in the free version of mtDNA Discover, but customers receive the same categories, but significantly more information if they sign in and click through.

You can follow along on the free version of Discover for haplogroups X2b4 here, and X2b4g here.

Clicking on either the Time Tree, or the Classic Tree shows that a LOT has changed with the Mitotree update.

Each tree has its purpose. Let’s look at the Classic Tree first.

The Classic Tree

I like the Classic Tree because it’s compact, detailed and concise, all in one. Radegonde Lambert’s new haplogroup, X2b4g is a subgroup of X2b4, so let’s start there.

Click on any image to enlarge

Under haplogroup X2b4, several countries are listed, including France. There are also 7 haplotype clusters, which tell you that those testers within the cluster all match each other exactly.

It’s worth noting that the little trowels (which I thought were shovels all along) indicate ancient samples obtained from archaeological digs. In the Discover tools, you’ll find them under Ancient Connections for that haplogroup. We will review those in a minute.

In Mitotree, haplogroup X2b4 has now branched several granular and more specific sub-haplogroups.

Radegonde Lambert’s new haplogroup falls below another new haplogroup, X2b4d’g, which means that haplogroup X2b4d’g is now the parent haplogroup of both haplogroups X2b4d and X2b4g. Both fall below X2b4d’g.

Haplogroup names that include an apostrophe mean it’s an umbrella group from which the two haplogroups descend – in this case, both X2b4d and X2b4g. Apostrophe haplogroups like X2b4d’g are sometimes referred to as Inner Haplogroups.

You can read more about how to understand your haplogroup name, here.

In this case, haplogroup X2b4d’g is defined by mutation G16145A, which is found in both haplogroups X2b4d and X2b4g. Both of those haplogroup have their own defining mutations in addition to G16145A, which caused two branches to form beneath X2b4d’g.

You can see that Radegonde Lambert’s haplogroup X2b4g is defined by mutation C16301T, but right now, that really doesn’t matter for what we’re trying to accomplish.

In descending order, for Radegonde, we have haplogroups:

  • X2b4
  • X2b4d’g
  • X2b4g

Your Match Page

Looking at the tester’s match page, Radegonde’s haplotype cluster number and information about the cluster are found below the haplogroup. You can view your cluster number on:

  • Your match page
  • The Match Time Tree beside your name and those of your matches in the same haplotype cluster
  • The Scientific Details – Variants page

I wrote about haplotype clusters, here.

Click on any image to enlarge

On your match page, which is where most people look first, you are in the same haplogroup and haplotype cluster with anyone whose circle is also checked and is blue. If the little circles are not checked and blue, you don’t share either that haplogroup, haplotype cluster, or haplogroup and haplotype cluster. If you share a haplotype cluster, you will always share the same haplogroup.

Haplotype clusters are important because cluster members match on exactly the same (but less stable) mutations IN ADDITION to haplogroup-defining (more stable) mutations.

However, you may also share an identifiable ancestor with people in different haplotype clusters. Mutations, and back mutations happen – and a lot more often at some mutation locations, which is why they are considered less stable. Normally, though, your own haplotype cluster will hold your closest genealogical matches.

In Discover, you can see that Radegonde’s haplotype cluster, F585777, displays three tester-supplied countries, plus two more. Click on the little plus to expand the countries.

What you’re viewing are the Earliest Known Ancestor (EKA) countries that testers have entered for their direct matrilineal ancestor.

Let’s hope they understood the instructions, and their genealogy information was accurate.

Notice that Canada and France are both probably quite accurate for Radegonde, based on the known history of the Acadians. There were only French and Native women living in Nova Scotia in the 1600s, so Radegonde had to be one or the other.

The US may be accurate for a different tester whose earliest known ancestor (EKA) may have been found in, say, Louisiana. Perhaps that person has hit a brick wall in the US, and that’s all they know.

The US Native American flag is probably attributable to the old “Native” rumor about Radegonde, and the tester didn’t find the Canadian First Nations flag in the “Country of Origin” dropdown list. Perhaps that person has since realized that Radegonde was not Native and never thought to change their EKA designation.

The little globe with “Unknown Origins” is displayed when the tester doesn’t select anything in the “Country of Origin.”

Unfortunately, this person, who knew when Radegonde Lambert lived, did not complete any additional information, and checked the “I don’t know this information” box. Either Canada, or France would have been accurate under the circumstances. If they had tracked Radegonde back to Canada and read about her history, they knew she lived in Canada, was Acadian, and therefore French if she was not Native. Providing location information helps other testers, whose information, in turn, helps you.

Please check your EKA, and if you have learned something new, PLEASE UPDATE YOUR INFORMATION by clicking on the down arrow by your user name in the upper right hand corner, then Account Settings, then Genealogy, then Earliest Known Ancestors.

Don’t hesitate to email your matches and ask them to do the same. You may discover that you have information to share as well. Collaboration is key.

Radegonde’s Discover Haplogroup

First, let’s take a look at Radegonde’s haplogroup, X2b4g, in Discover.

The Discover Haplogroup Story landing page for haplogroup X2b4g provides a good overview. Please READ this page for your own haplogroup, including the little information boxes.

The history of Radegonde’s haplogroup, X2b4g, is her history as well. It’s not just a distant concept, but the history of a woman who is the ancestor of everyone in that haplogroup, but long before surnames. Haplogroups are the only way to lift and peer behind the veil of time to see who our ancestors were, where they lived, and the cultures they were a part of.

We can see that Radegonde’s haplogroup, X2b4g, was born in a woman who lived about 300 CE, Common (or Current) Era, meaning roughly the year 300, which is 1700 years ago, or 1300 years before Radegonde lived.

  • This means that the tester shares a common ancestor with everyone, including any X2b4g remains, between now and the year 300 when haplogroup X2b4g was born.
  • This means that everyone who shares haplogroup X2b4g has the same common female ancestor, in whom the mutation that defines haplogroup X2b4g originated. That woman, the common ancestor of everyone in haplogroup X2b4g, lived about the year 300, or 1700 years ago.
  • Your common ancestor with any one individual in this haplogroup can have lived ANYTIME between very recently (like your Mom) and the date of your haplogroup formation.
  • Many people misinterpret the haplogroup formation date to mean that’s the date of the MRCA, or most recent common ancestor, of any two people. It’s not, the haplogroup formation date is the date when everyone, all people, in the haplogroup shared ONE ancestor.
  • The MRCA, or most recent common ancestor, is your closest ancestor in this line with any one person, and the TMRCA is the “time to most recent common ancestor.” It could be your mother, or if your matrilineal first cousin tested, your MRCA is your grandmother, and the TMRCA is when your grandmother was born – not hundreds or thousands of years ago.
  • Don’t discount mitochondrial DNA testing by thinking that your common ancestor with your matches (MRCA) won’t be found before the haplogroup birth date – the year 300 in Radegonde’s case. The TMRCA for all of Radegonde’s descendants is about 1621 when she was born.
  • The haplogroup birth date, 1700 years ago, is the common ancestor for EVERYONE in the haplogroup, taken together.
  • Mitochondrial DNA is useful for BOTH recent genealogy and also reveals more distant ancestors.
  • Looking back in time helps us understand where Radegonde’s ancestors lived, which cultures they were part of, and where.

There are two ways to achieve that: Radegonde’s upstream or parent haplogroups, and Ancient Connections.

Parent Haplogroups

X2b4g split from X2b4d’g, the parent haplogroup of BOTH X2b4d and X2b4g, around 3700 years ago, or about 1700 BCE (Before Common (or Current) Era).

Looking at either the Classic Tree, the Time Tree (above) or the Match Time Tree, you can see that haplogroup X2b4g has many testers, and none provide any locations other than France, Canada, the US, unknown, and one Native in the midst of a large haplotype cluster comprised of French and Canadian locations. Due to the size of the cluster, it’s only partially displayed in the screen capture above.

You can also see that sister haplogroup X2b4d split from X2b4d’g around the year 1000, and the ancestors of those two testers are reported in Norway.

Many, but not all of the X2b4g testers are descendants of Radegonde. Even if everyone is wrong and Radegonde is not French, that doesn’t explain the other matches, nor how X2b4g’s sister haplogroup is found in Norway.

Clearly, Radegonde isn’t Native, but there’s still more evidence to consider.

Let’s dig a little deeper using Radegonde’s Ancient Connections.

Ancient Connections

While ancestor and location information are user-provided, Ancient Connections are curated from scientifically published papers. There’s no question about where those remains were found.

When signed in to your account, if you’ve taken the mtFull Sequence test, clicking on the Ancient Connections tab in Discover shows a maximum of around 30 Ancient Connections. If you’re viewing the free version of Discover, or you’ve only tested at the HVR1 or HVR1+HVR2 levels, you’ll see two of your closer and one of your most distant Ancient Connections. It’s easy to upgrade to the mtFull.

In Discover, the first group of Ancient Connections are genetically closest to you in time, and the last connections will be your most distant. Some connections may be quite rare and are noted as such.

Please keep in mind that oldest, in this case, Denisova 8 and Sima de los Huesos, will never roll off your list. However, as new studies are released and the results are added to the tree, you may well receive new, closer matches. New results are being added with each Discover update.

It’s very exciting to see your Ancient Connections, but I need to say three things, loudly.

  1. Do NOT jump to conclusions.
  2. These remains are probably NOT YOUR ANCESTORS, but definitely ARE your distant cousins.
  3. Ancient Connections ARE wonderful hints, especially when taken together with each other and additional information.

It’s VERY easy to misinterpret Ancient Connections because you’re excited. I’ve done exactly that. To keep the assumption monster from rearing its ugly head, I have to take a breath and ask myself a specific set of questions. I step through the logical analysis process that I’m sharing with you.

The first thing I always want to know is where the genetically closest set of remains was found, when, and what we know about them, so let’s start there. Keep in mind that the closest remains genetically may not be the most recent set of remains to have lived. For example, my own haplogroup will be the closest genetically, but that person may have lived 2000 years ago. An Ancient Connection in a more distant haplogroup may have lived only 1000 years ago. The closest person genetically is NOT the same as the person who lived the most recently.

Our tester, Radegonde’s descendant, has no Ancient Connections in haplogroup X2b4g or X2b4d’g, but does have two in haplogroup X2b4, so let’s start there.

Discover provides a substantial amount of information about each set of ancient remains. Click on the results you want to view, and the information appears below.

Radegonde’s first Ancient Connection is Carrowkeel 534. The graphic shows the tester, the Ancient Connection being viewed, and their shared ancestor’s haplogroup. In this case, the shared ancestor haplogroup of Carrowkeel 534 and the tester is X2b4, who lived about 5000 years ago.

It’s very easy to look at Carrowkeel 534, become smitten, and assume that this person was your ancestor.

By Shane Finan – Own work, CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=35098411

It’s especially easy if you WANT that person to be your ancestor. Carrowkeel 534 was buried in a passage tomb in County Sligo, Ireland. I’ve been there.

However, don’t let your emotions get involved – at least not yet.

This is the first example of the steps that determine that these remains are NOT YOUR ANCESTOR.

  • Carrowkeel 534 was a male, and we all know that males do not pass on their mitochondrial DNA. Well, that’s an inconvenient fact.😊
  • There are two sets of X2b4 remains in Ancient Connections. Carrowkeel 534 remains are about 4600-5000 years old, and your common ancestor with them lived about 5000 years ago. However, Radegonde was French and migration from Ireland to France is not typical.
  • The other set of X2b4 remains, Ladoga 16, lived more recently, between the years of 900 and 1200 (or 800-1100 years ago), but they are found in Russia.
  • Radegonde’s parent haplogroup, X2b4d’g was born about 3700 years ago, which excludes the Russian remains from being Radegonde’s direct ancestor.
  • Radegonde’s common ancestor with both these sets of remains lived about 5000 years ago, but these remains were not found even close to each other.

In fact, these remains, if walking, are about 3299 km (2049 miles) apart, including two major water crossings.

  • Given that Radegonde is probably French, finding her ancestor around 5000 years ago in an Irish passage tomb in County Sligo, or in a location east of St. Petersburg, is extremely unlikely.

What IS likely, though, is that X2b4d’g descendants of your common ancestor with both sets of remains, 5000 years ago, went in multiple directions, meaning:

  • Radegonde’s ancestor found their way to France and along the way incurred the mutations that define X2b4d’g and X2b4g by the year 1600 when she lived, or about four hundred years ago.
  • Another X2b4 descendant found their way to what is today Ireland between 4600 and 5000 years ago
  • A third X2b4 descendant found their way to Russia between 800-1100 years ago, and 5000 years ago

If any question remains about the genesis of Radegonde’s ancestors being Native, Ancient Connections disproves it – BUT – there’s still an opportunity for misunderstanding, which we’ll see in a few minutes.

Ancient Connections Analysis Chart

I’ve created an analysis chart, so that I can explain the findings in a logical way.

Legend:

  • Hap = Haplogroup
  • M=male
  • F=female
  • U=unknown

Please note that ancient samples are often degraded and can be missing important mutations. In other words, the tree placement may be less specific for ancient samples. Every ancient sample is reviewed by FamilyTreeDNA’s genetic anthropologist before it’s placed on the tree.

Ancient samples use carbon dating to determine ages. Sometimes, the carbon date and the calculated haplogroup age are slightly “off.” The haplogroup age is a scientific calculation based on a genetic clock and is not based on either genealogy or ancient burials. The haplogroup age may change as the tree matures and more branches are discovered.

I’m dividing this chart into sections because I want to analyze the findings between groups.

The first entry is the earliest known ancestor of the current lineage – Radegonde Lambert, who was born about 1621, or roughly 400 years ago. I’ve translated all of the years into “years ago” to avoid any confusion.

If you wish to do the same, with CE (Current or Common Era) dates, subtract the date from 2000. 300 CE= (2000-300) or1700 years ago. With BCE dates, add 2000 to the BCE number. 1000 BCE= (1000+2000) or 3000 years ago.

Connection Identity Age Years Ago Location & Cultural Group Hap Hap Age Years Ago Shared Hap Shared Hap Age Years Ago
Radegonde Lambert (F) 400 France or Canada -Acadian X2b4g 1700 X2b4 5000
Carrowkeel 534 (M) 4600-5100 Sligo, Ireland – Neolithic Europe X2b4 5000 X2b4 5000
Ladoga 16 (M) 800-1100 Ladoga, Russia Fed – Viking Russia X2b4 5000 X2b4 5000
  • Age Years Ago – When the Ancient Connection lived
  • Hap Age Years Ago – When the haplogroup of the Ancient Connection (X2b4) originated, meaning was born
  • Shared Hap Age Years Ago – When the Shared Ancestor of everyone in the Shared Haplogroup originated (was born)

In this first section, the haplogroup of the Ancient Connections and the Shared Haplogroup is the same, but that won’t be the case in the following sections. Radegonde Lambert’s haplogroup is different than her shared haplogroup with the Ancient Connections.

Let’s assume we are starting from scratch with Radegonde.

The first question we wanted to answer is whether or not Radegonde is European, presumably French like the rest of the Acadians, or if she was Native. That’s easy and quick.

Native people crossed Beringia, arriving from Asia someplace between 12,000 and 25,000 years ago in multiple waves of migration that spread throughout both North and South America.

Therefore, given that the first two samples, Carrowkeel 534 and Ladoga 16, share haplogroup X2b4, an upstream haplogroup with Radegonde Lambert, and haplogroup X2b4 was formed around 5000 years ago, the answer is that Radegonde’s X2b4 ancestor, whoever that was, clearly lived in Europe, NOT the Americas.

According to Discover, Haplogroup X2b4:

  • Was formed about 5000 years ago
  • Has 16 descendant haplogroups
  • Has 29 unnamed lineages (haplotype clusters or individuals with no match)
  • Includes testers whose ancestors are from 23 countries

The Country Frequency map shows the distribution of X2b4, including all descendant haplogroups. Please note that the percentages given are for X2b4 as a percentage of ALL haplogroups found in each colored country. Don’t be misled by the relative physical size of the US and Canada as compared to Europe.

The table view shows the total number of self-identified locations of the ancestors of people in haplogroup X2b4 and all downstream haplogroups.

The Classic Tree that we looked at earlier provides a quick view of X2b4, each descendant haplogroup and haplotype cluster, and every country provided by the 331 X2b4 testers.

For the X2b4 Ancient Connections, we’ve already determined:

  • That Radegonde’s ancestors were not Native
  • Carrowkeel 534 is a male and cannot be Radegonde’s ancestor. It’s extremely likely that Carrowkeel 534’s mother is not Radegonda’s ancestor either, based on several factors, including location.
  • Based on dates of when Ladoga 16 lived, and because he’s a male, he cannot be the ancestor of Radegonde Lambert.

Radegonda’s haplogroup was formed long before Ladoga 16 lived. Each Ancient Connection has this comparative Time Tree if you scroll down below the text.

  • Both Carrowkeel and Ladoga share an ancestor with our tester, and Radegonde, about 5000 years ago.

Think about how many descendants the X2b4 ancestor probably had over the next hundreds to thousands of years.

  • We know one thing for sure, absolutely, positively – X2b4 testers and descendant haplogroups live in 32 countries. People migrate – and with them, their haplogroups.

What can we learn about the genealogy and history of Radegonde Lambert and her ancestors?

We find the same haplogroup in multiple populations or cultures, at different times and in multiple places. Country boundaries are political and fluid. What we are looking for are patterns, or sometimes, negative proof, which is often possible at the continental level.

X2b4, excluding downstream haplogroups, is found in the following locations:

  • Bulgaria
  • Canada (2)
  • Czech Republic
  • England (2)
  • Finland (2)
  • France (3)
  • Germany (4)
  • Portugal
  • Scotland (2)
  • Slovakia (2)
  • Sweden (2)
  • UK (2)
  • Unknown (11)
  • US (2)

Note that there are three people in France with haplogroup X2b4 but no more refined haplogroup.

Looking at X2b4’s downstream haplogroups with representation in France, we find:

  • X2b4a (none)
  • X2b4b (none)
  • X2b4b1 (1)
  • X2b4d’g (none)
  • X2b4d (none)
  • X2b4g (24) – many from Radegonde’s line
  • X2b4e and subgroups (none)
  • X2b4f (none)
  • X2b4j and subgroups (none)
  • X2b4k (none)
  • X2b4l (1)
  • X2b4m (none)
  • X2b4n and subgroups (none)
  • X2b4o (none)
  • X2b4p (none)
  • X2b4r (none)
  • X2b4+16311 (none)

I was hoping that there would be an Ancient Connection for X2b4, X2b4d’g, or X2b4g someplace in or even near France – because that makes logical sense if Radegonde is from France.

All I can say is “not yet,” but new ancient sites are being excavated and papers are being released all the time.

Ok, so moving back in time, let’s see what else we can determine from the next set of Ancient Connections. Haplogroup X2b1”64 was formed about 5050 years ago.

Connection Identity Age Years Ago Location & Cultural Group Hap Hap Age Years Ago Shared Hap Shared Hap Age Years Ago
Radegonde Lambert (F) 400 France or Canada X2b4g 1700
Carrowkeel 534 (M) 5100-4600 Sligo, Ireland – Neolithic Europe X2b4 5000 X2b4 5000
Ladoga 16 (M) 800-1100 Ladoga, Russia Fed – Viking Russia X2b4 5000 X2b4 5000
Parknabinnia 186 (M) 5516-5359 Clare, Ireland – Neolithic Europe X2b1”64 5516-5259 X2b1”64 Before 5050 years ago
Rössberga 2 (M) 5339-5025 Vastergotland, Sweden – Funnel Beaker X2b1”64 5516-5259 X2b1”64 Before 5050
Rössberga 29 (M) 5366-5100 Vastergotland, Sweden – Funnel Beaker and Early Plague X2b1”64 5516-5259 X2b1”64 Before 5050
Rössberga 38 (M) 5340-5022 Vastergotland, Sweden – Funnel Beaker X2b1”64 5516-5259 X2b1”64 Before 5050
Monte Sirai 797263 (U) 2600-2400 Monte Sirai, Italy (Sardinia) – Phoenicians X2b35a1 3350 X2b1”64 5050
Bogovej 361 (F) 1000-1100 Lengeland, Denmark – Viking Denmark X2b1”64 5516-5259 X2b1”64 5050
Ladoga 410 (M) 800-1000 Leningrad Oblast, Russia – Viking Russia X2b1”64 5516-5259 X2b1”64 5050

Our first group ended with haplogroup X2b4, and our second group consists of haplogroup X2b1”64, the parent haplogroup of X2b4. X2b1”64 is a significantly larger haplogroup with many downstream branches found throughout Europe, parts of western Asia, the Levant, India, and New Zealand (which probably reflects a colonial era settler). The Country Frequency Map and Table are found here.

X2b1”64 is just slightly older than X2b4, but it’s much more widespread, even though they were born about the same time. Keep in mind that haplogroup origination dates shift as the tree is developed.

  • These seven individuals who share X2b1”64 as their haplogroup could be related to each other individually, meaning their MRCA, anytime between when they lived and when their haplogroup was formed.
  • The entire group of individuals all share the same haplogroup, so they all descend from the one woman who formed X2b1”64 about 5050 years ago. She is the shared ancestor of everyone in the haplogroup.

One X2b4 and one X2b1”64 individual are found in the same archaeological site in Russia. Their common ancestor would have lived between the time they both lived, about 800 years ago, to about 5000 years ago. It’s also possible that one of the samples could be incomplete.

A second X2b1”64 Ancient Connection is found in the Court Tomb in County Clare, Ireland, not far from the Carrowkeel 534 X2b4 site.

However, Monte Sirai is fascinating, in part because it’s not found near any other site. Monte Sirai is found all the way across France, on an island in the Tyrrhenian Sea.

It may be located “across France” today, but we don’t know that the Phoenician Monte Sirai site is connected with the Irish sites. We can’t assume that the Irish individuals arrived as descendants of the Monte Sirai people, even though it would conveniently fit our narrative – crossing France. Of course, today’s path includes ferries, which didn’t exist then, so if that trip across France did happen, it could well have taken a completely different path. We simply don’t know and there are very few samples available.

Three Ancient Connections are found in the Rössberga site in Sweden and another in  Denmark.

Adding all of the Ancient sites so far onto the map, it looks like we have two clusters, one in the northern latitudes, including Denmark, Sweden, and Russia, and one in Ireland with passage burials, plus one single Connection in Monte Sirai.

If I were to approximate a central location between all three, that might be someplace in Germany or maybe further east. But remember, this is 5000 years ago and our number of samples, as compared to the population living at the time is EXTREMELY LIMITED.

Let’s move on to the next group of Ancient Connections, who have different haplogroups but are all a subset of haplogroup X2.

Identity Age Years Ago Location & Cultural Group Hap Hap Age Years Ago Shared Hap Shared Hap Age Years Ago
Radegonde Lambert (F) 400 France or Canada X2b4g 1700
Carrowkeel 534 (M) 5100-4600 Sligo, Ireland – Neolithic Europe X2b4 5000 X2b4 5000
Ladoga 16 (M) 800-1100 Ladoga, Russia Fed – Viking Russia X2b4 5000 X2b4 5000
Parknabinnia 186 (M) 5516-5359 Clare, Ireland – Neolithic Europe X2b1”64 5516-5259 X2b1”64 Before 5050
Ross Rössberga 2 (M) 5339-5025 Vastergotland, Sweden – Funnel Beaker X2b1”64 5516-5259 X2b1”64 Before 5050
Rössberga 29 (M) 5366-5100 Vastergotland, Sweden – Funnel Beaker and Early Plague X2b1”64 5516-5259 X2b1”64 Before 5050
Rössberga 38 (M) 5340-5022 Vastergotland, Sweden – Funnel Beaker X2b1”64 5516-5259 X2b1”64 Before 5050
Monte Sirai 797263 (U) 2600-2400 Monte Sirai, Italy (Sardinia) – Phoenicians X2b35a1 3350 X2b1”64 5050
Bogovej 361 (F) 1000-1100 Lengeland, Denmark – Viking Denmark X2b1”64 5516-5259 X2b1”64 5050
Ladoga 410 (M) 800-1000 Leningrad Oblast, Russia – Viking Russia X2b1”64 5516-5259 X2b1”64 5050
Barcin 31 (M) 8236-8417 Derekoy, Turkey – Neolithic Anatolia Ceramic X2m2’5’7^ 9200 X2b”aq 13,000
Abasar 55 (M) 500-800 Abasár Bolt-tető, Abasar, Hungary – Medieval Hungary X2m1e 5350 X2b”aq 13,000
Gerdrup 214 3779-3889 Gerdrup, Sealand, Denmark – Middle Bronze Age X2c1 3400 X2+225 13,000
Sweden Skara 275 800-1100 Varnhem, Skara, Sweden – Viking Sweden X2c1 3400 X2+225 13,000
Kopparsvik 225 950-1100 Gotland, Sweden – Viking Sweden X2z 5650 X2+225 13,000
Sandomierz 494 900-1100 Sandomierz, Poland – Viking Poland X2c2b 1650 X2+225 13,000
Kennewick man 8390-9250 Kennewick, Washington – Native American X2a2’3’4^ 10,450 X2 13,000
Roopkund 39 80-306 Roopkund Lake, Uttarakhand, India – Historical India X2d 13,000 X2 13,000

The next several Ancient Connections have haplogroups that are a subgroup of haplogroup X2. These people lived sometime between 500 years ago in Hungary, and 8390-9250 years ago when Kennewick Man lived in the present-day state of Washington in the US. Kennewick Man merits his own discussion, so let’s set him aside briefly while we discuss the others.

The important information to be gleaned here isn’t when these people lived, but when Radegonde shared a common ancestor with each of them. The shared haplogroup with all of these individuals was born about 13,000 years ago.

Looking at the map again, and omitting both X2 samples, we can see that the descendants of that shared ancestor 13,000 years ago are found more widely dispersed.

Including these additional burials on our map, it looks like we have a rather large Swedish and Viking cluster, where several of the older burials occurred prior to the Viking culture. We have a Southeastern Europe cluster, our two Irish tomb burials, and our remaining single Monte Sirai Phoenician burial on the island of Sardinia.

Stepping back one more haplogroup to X2, which was born about the same time, we add a burial in India, and Kennewick Man.

The Migration Map

The Migration map in Discover provides two different features.

  • The first is the literal migration map for the various ancestral haplogroups as they migrated out of Africa, if in fact yours did, culminating in your base haplogroup. In this case, the base haplogroup is X2, which is shown with the little red circle placed by FamilyTreeDNA. I’ve added the red squares, text and arrows for emphasis.
  • The second feature is the mapped Ancient Connections, shown with little brown trowels. Clicking on each one opens a popup box.

After haplogroup X2 was formed, it split into haplogroups X2a and X2b.

The X2a group, Kennewick Man’s ancestors, made their way eastward, across eastern Russia to Beringia where they crossed into the Americas.

They either crossed Beringia, follow the Pacific coastline, or both, eventually making their way inland, probably along the Hood River, to where Kennewick Man was found some 2,800 years later on the banks of the Kennewick River.

The X2b group made their way westward, across western Europe to a location, probably France, where Radegonde Lamberts’ ancestors lived, and where Radegonde set sail for Nova Scotia.

After being separated for nearly 13,000 years, the descendants of the single woman who founded haplogroup X2 and lived someplace in central Asia around 13,000 years ago would find themselves on opposite coasts of the same continent.

So, no, Radegonde Lambert was not Native American, but her 600th matrilineal cousin or so, Kennewick Man, absolutely was.

Radegonde Lambert and Kennewick Man

Here’s where confirmation bias can rear its ugly head. If you’re just scanning the Ancient Connections and see Kennewick Man, it would be easy to jump to conclusions, leap for joy, slap a stamp of “confirmed Native American” on Radegonde Lambert, and never look further. And if one were to do that, they would be wrong.

Let’s work through our evaluation process using Discover.

Radegonde Lambert and Kinnewick Man, an early Native American man whose remains were found Kennewick, Washington in 1996, are both members of the broader haplogroup X2. Kennewick Man lived between 8290 and 9350 years ago, and their shared ancestor lived about 13,000 years ago – in Asia, where mitochondrial haplogroup X2 originated. This is the perfect example of one descendant line of a haplogroup, X2 in this case, going in one direction and a second one traveling in the opposite direction.

Two small groups of people were probably pursuing better hunting grounds, but I can’t help but think of a tundra version of the Hatfields and McCoys and cousin spats.

“I’m going this way. There are better fish on that side of the lake, and I won’t have to put up with you.”

“Fine, I’m going that way. There are more bears and better hunting up there anyway.”

Their wives, who are sisters, “Wait, when will I ever see my sister again?”

One went east and one went west.

X2a became Native American and X2b became European.

Looking back at our information about Kennewick Man, his haplogroup was born significantly before he lived.

He was born about 8390-9250 years ago, so let’s say 8820 years ago, and his haplogroup was born 10,500 years ago, so about 1680 years before he lived. That means there were many generations of women who carried that haplogroup before Kennewick Man.

Let’s Compare

Discover has a compare feature.

I want to Compare Radegonde Lambert’s haplogroup with Kennewick Man’s haplogroup X2a2’3’4^.

The Compare tool uses the haplogroup you are viewing, and you enter a second haplogroup to compare with the first.

The ancestral path to the shared ancestor, meaning their shared haplogroup, is given for each haplogroup entered. That’s X2 in this case. Then, from the shared haplogroup back in time to Mitochondrial Eve.

I prefer to view this information in table format, so I created a chart and rounded the haplogroup ages above X2.

Hap Age – Years Ago Radegonde’s Line Shared Ancestors and Haplogroups Kennewick’s Line Hap Age – Years Ago
143,000 mt-Eve
130,000 L1”7
119,000 L2”7
99,000 L2’3’4’6
92,000 L3’4’6
73,500 L3’4
61,000 L3
53,000 N
53,000 N+8701
25,000 X
22,500 X1’2’3’7’8
13,000 X2 – Asia
13,000 X2+225 X2a 10,500
12,900 X2b”aq X2a2’3’4^ 10,400 Kennewick Man born c 8800 years ago
11,000 X2b
5,500 X2b1”64
5,000 X2b4
1,900 X2b4d’g
Radegonde Lambert born c 1661 – 400 years ago 1,700 X2b4g

More Ancient Connections

Radegonde Lambert’s matrilineal descendants have an additional dozen Ancient Connections that are found in upstream haplogroup N-8701. Their shared ancestors with Radegonde reach back to 53,000 years ago in a world far different than the one we inhabit today. I’m not going to list or discuss them, except for one.

Identity Age Years Ago Location & Cultural Group Hap Hap Age Years Ago Shared Hap Shared Hap Age Years Ago
Radegonde Lambert (F) 400 France or Canada X2b4g 1700
Carrowkeel 534 (M) 5100-4600 Sligo, Ireland – Neolithic Europe X2b4 5000 X2b4 5000
Ladoga 16 (M) 800-1100 Ladoga, Russia Fed – Viking Russia X2b4 5000 X2b4 5000
Parknabinnia 186 (M) 5516-5359 Clare, Ireland – Neolithic Europe X2b1”64 5516-5259 X2b1”64 Before 5050
Rössberga 2 (M) 5339-5025 Vastergotland, Sweden – Funnel Beaker X2b1”64 5516-5259 X2b1”64 Before 5050
Rössberga 29 (M) 5366-5100 Vastergotland, Sweden – Funnel Beaker and Early Plague X2b1”64 5516-5259 X2b1”64 Before 5050
Rössberga 38 (M) 5340-5022 Vastergotland, Sweden – Funnel Beaker X2b1”64 5516-5259 X2b1”64 Before 5050
Monte Sirai 797263 (U) 2600-2400 Monte Sirai, Italy (Sardinia) – Phoenicians X2b35a1 3350 X2b1”64 5050
Bogovej 361 (F) 1000-1100 Lengeland, Denmark – Viking Denmark X2b1”64 5516-5259 X2b1”64 5050
Ladoga 410 (M) 800-1000 Leningrad Oblast, Russia – Viking Russia X2b1”64 5516-5259 X2b1”64 5050
Barcin 31 (M) 8236-8417 Derekoy, Turkey – Neolithic Anatolia Ceramic X2m2’5’7^ 9200 X2b”aq 13,000
Abasar 55 (M) 500-800 Abasár Bolt-tető, Abasar, Hungary – Medieval Hungary X2m1e 5350 X2b”aq 13,000
Gerdrup 214 3779-3889 Gerdrup, Sealand, Denmark – Middle Bronze Age X2c1 3400 X2+225 13,000
Kopparsvik 225 950-1100 Gotland, Sweden – Viking Sweden X2z 5650 X2+225 13,000
Sandomierz 494 900-1100 Sandomierz, Poland – Viking Poland X2c2b 1650 X2+225 13,000
Sweden Skara 275 800-1100 Varnhem, Skara, Sweden – Viking Sweden X2c1 3400 X2+225 13,000
Kennewick man 8390-9250 Kennewick, Washington – Native American X2a2’3’4^ 10,450 X2 13,000
Roopkund 39 80-306 Roopkund Lake, Uttarakhand, India – Historical India X2d 13,000 X2 13,000
Ranis 10 43,500-47,000 Ranis, Germany – LRJ Hunger Gatherer N3’10 53,000 N+8701 53,000
Zlatý kůň woman 47,000 Czech Republic – N+8701 53,000 N+8701 53,000

Zlatý kůň Woman

Zlatý kůň Woman lived some 43,000 years ago and her remains were discovered in the Czech Republic in 1950.

Believed to be the first anatomically modern human to be genetically sequenced, she carried about 3% Neanderthal DNA. Europeans, Asians and indigenous Americans carry Neanderthal DNA as well.

Unlike many early remains, Zlatý kůň Woman’s facial bones have been scanned and her face approximately reconstructed.

There’s something magical about viewing a likeness of a human that lived more than 40,000 years ago, and to whom I’m at least peripherally related.

Like all other Ancient Connections, it’s unlikely that I descend from Zlatý kůň Woman herself, but she is assuredly my very distant cousin.

What else do we know about Zlatý kůň Woman? Quoting from her Ancient Connection:

She lived during one of the coldest periods of the last ice age, surviving in harsh tundra conditions as part of a small hunter-gatherer group. She died as a young adult, though the cause of death remains unknown.

Her brain cavity was larger than that of modern humans in the comparative database, another trait showing Neanderthal affinity. While the exact colors of her features cannot be determined from available evidence, researchers created both a scientific grayscale model and a speculative version showing her with dark curly hair and brown eyes.

Zlatý kůň Woman may or may not have direct descendants today, but her haplogroup ancestors certainly do, and Radegonde Lambert is one of them, which means Radegonde’s matrilineal ancestors and descendants are too.

Ancient Connections for Genealogy

While Ancient Connections are fun, they are more than just amusing.

You are related through your direct matrilineal (mitochondrial) line to every one of your mtDNA Discover Ancient Connections. Everyone, males and females, can take a mitochondrial DNA test.

I find people to test for the mitochondrial DNA of each of my ancestral lines – like Radegonde Lambert, for example. I wrote about various methodologies to find your lineages, or people to test for them, in the article, Lineages Versus Ancestors – How to Find and Leverage Yours.

Radegonde’s mitochondrial DNA is the only key I have into her past, both recent and distant. It’s the only prayer I have of breaking through that brick wall, now or in the future.

Interpreted correctly, and with some luck, the closer Ancient Connections can provide genealogical insight into the origins of our ancestors. Not just one ancestor, but their entire lineage. While we will never know their names, we can learn about their cultural origins – whether they were Vikings, Phoenicians or perhaps early Irish buried in Passage Graves.

On a different line, an Ancient Connection burial with an exact haplogroup match was discovered beside the Roman road outside the European town where my ancestral line was believed to have been born.

Ancient Connections are one small glimpse into the pre-history of our genetic line. There are many pieces that are missing and will, in time, be filled in by ancient remains, Notable Connections, and present-day testers.

Check your matches and your Ancient Connections often. You never know when that magic piece of information you desperately need will appear.

What is waiting for you?

_____________________________________________________________

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 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

Mitotree is Born

Mitotree is born and I can hardly contain my excitement.

The Million Mito R&D team members, along with many others at FamilyTreeDNA, are proud to introduce the new Mitotree and mtDNA Discover, which were brought to life thanks to one pivotal entrepreneurial figure, Bennett Greenspan, whose support and vision set the ball in motion and made Mitotree possible.

Left to right, the Million Mito science team is:

  • Goran Runfeldt, Head of R&D at FamilyTreeDNA
  • Dr. Paul Maier, Senior Population Geneticist at FamilyTreeDNA
  • Roberta Estes, DNAexplain, scientist, blogger, author, genetic genealogist, and Genographic Affiliate Researcher
  • Dr. Miguel Vilar, Genetic Anthropologist, Lead Scientist with the Genographic Project, and Professor at the University of Maryland
  • Bennett Greenspan, President Emeritus of FamilyTreeDNA, and avid genealogist
  • John Detsikas, Front End Developer who is responsible for the user interface for both Y-DNA Discover and now mtDNA Discover

The Million Mito Project Inception

The Million Mito Project was launched at RootsTech 2020 and encouraged people to test their mitochondrial DNA, both for their genealogy and to help build the database. More than a million samples were candidates, but only high-quality, full sequence results were used. In the process of building the tree, additional samples were incorporated from other public sources for tree construction.

Drum Roll – The Mitotree

A beta version of the Mitotree is being released today, and boy, is this a big deal.

Before we discuss the rest of what’s coming, I need to mention that the Mitotree is now evergreen, meaning that the tree will be updated periodically, as will mtDNA Discover. This lifetime value is included with the cost of your test, so there’s nothing more to purchase.

Haplogroups will change from time to time, as the tree does, so don’t fall in love with yours, and definitely, no tattoos😊

I’m going to be speaking in terms of “we,” meaning the Million Mito team who built the Mitotree and mtDNA Discover, plus an amazing team of FamilyTreeDNA folks who were absolutely essential in getting this out the door and to you.

The Mitotree is new from the ground up, and yes, haplogroup naming consistency with PhyloTree has been maintained where possible.

One of the unanticipated challenges we encountered was that the 2016 PhyloTree had to be recreated, essentially reverse engineered, to determine the rules they used regarding mutations for haplogroup creation. In other words, which mutations were valid and reliable, which weren’t, determining their relative importance, and so forth.

After the existing 2016 tree was recreated, the next hurdle to overcome was that none of the existing phylogenetic software used in academia would scale from 24,000 samples and 5500 subclades to more than a quarter million samples and 40,000 haplogroups, so that software had to be designed and written by R&D team members.

More information about this process will be forthcoming shortly, and a paper will be published with our methodology, but for right now, let’s look at the user experience and what’s being released now.

Here’s what’s coming today and over the next few days.

The beta Mitotree includes:

  • Over 40,000 branches
  • Over 250,000 mtFull Sequences from FTDNA
  • Over 10,000 third-party full sequences from GenBank, 1000 Genomes, etc.
  • Over 1000 Ancient Connections
  • Over 100 Notable Connections

More is on the way.

The new Mitotree is the tree provided in several formats within mtDNA Discover. You can view the public version of the tree, here, or sign on to your FamilyTreeDNA account and click through from your dashboard to see more.

Today’s Releases

The Mitotree doesn’t exist in a vacuum, so several updates and new features will be rolling out today.

  • mtDNA Discover, which includes the new Mitotree
  • New customer haplogroups for those who have taken mtFull sequence tests
  • New mtDNA matches page

New Haplogroups

New haplogroups have been calculated for FamilyTreeDNA customers who have taken the full sequence test. Those who have taken only the HVR1 or HVR1/HVR2 tests are encouraged to upgrade to the full sequence test.

Not everyone will receive a new Mitotree haplogroup that is different from their classic haplogroup, but most people will. Your original haplogroup is displayed with the classic tag, and the new Mitotree haplogroup with the beta tag.

If your classic and Mitotree haplogroups are the same, it means that either you have no more private variants (mutations) available to form a new haplogroup, or no one else from your lineage has tested yet.

New mtDNA Matches Page

If you click on your mtDNA matches, you’ll notice that the page has been redesigned to look and function like the other FamilyTreeDNA match pages.

If you click to view your matches, you’ll be able to view both the “old” classic haplogroup, and your matches’ new Mitotree haplogroup, plus a new haplotype if they have one. We will talk about haplotypes in a minute.

The people you match are the same as before, but matches may be recalculated in the future.

If you click through to the new mtDNA Discover from your dashboard, you’ll be able to view the public portion of mtDNA Discover, plus the additional customized information provided to FamilyTreeDNA mtFull sequence customers.

mtDNA Discover

If you have taken a full sequence test, sign on to your account to view your new haplogroup, then click on the new mtDNA Discover icon on your dashboard.

If you haven’t taken the mtFull sequence test, but the partial HVR1 or HVR2 versions, you can still view mtDNA Discover on your dashboard, but without the mtFull customization.

Customization that occurs exclusively for FamilyTreeDNA mtFull sequence customers includes:

  • Most detailed placement of your branch on Mitotree
  • Haplotype clusters
  • Additional Ancient Connections
  • Additional Notable Connections
  • The Match Time Tree
  • Globetrekker (coming soon)
  • The Group Time Tree (coming soon)

mtDNA Discover is similar to Y-DNA Discover.

You’ll be able to view a dozen new reports about your haplogroup in addition to the tools provided on your dashboard.

The new Mitotree can be viewed in several formats, each with its unique benefit.

  1. Time Tree – a genetic tree that shows when each haplogroup was formed, plus a country flag for where present-day testers report as the location of their earliest known ancestor (EKA)
  2. Classic Tree – a more traditional view of a phylogenetic tree, including the number of testers on each branch, the variants, or mutations that define the haplogroup, the era and approximate date of formation, and other details about the tree topology
  3. Scientific Details Variants Tab – shows the variants that differ in each haplogroup as you reach back in time
  4. Ancestral Path for the selected haplogroup – outlines your path back to early humans, including Denisovans.
  5. Match Time Tree for you and your matches (must be signed in to your account and click on mtDNA Discover icon)
  6. Group Time Tree (coming soon) for those who have joined projects

Match Time Tree

The Match Time Tree is extremely useful because it overlays your matches, plus their earliest known ancestors (EKA), on a genetic Time Tree, by haplogroup and haplotype, so you can see how you may be related, and when.

You can also see your matches that have now fallen into neighboring haplogroups, which suggests that they probably aren’t as genealogically close as people in your haplogroup. However, that’s not always the case, because mutations can occur at any time.

Haplotype Clusters

A haplotype cluster is a new concept introduced specifically for genealogists with the new Mitotree. Haplotypes are identified by numbered “F” groups. Three are shown, below.

There may be groups of people within a haplogroup that have exactly the same mutations, or genetic signature, and no additional mutations. Still, they may not form a new haplogroup. There could be several reasons for not forming a new haplogroup, including known SNP locations where mutations occur that are known to be unstable, such as location  315, which tends to accumulate random insertions and is ignored because of its known instability.

When multiple people share an exactly identical signature, meaning all of the same mutations, they are shown within a haplotype “F” cluster to provide additional specificity to the tree.

The haplotype has been designed to provide additional granularity to the tree and genealogically relevant information. The haplotype “Fxxxxxx” numbers are randomly generated and have no special meaning.

A word of caution here. While the haplotype sequences are identical, it is still possible that another tester from outside the cluster could be a closer relative. For example, they could have accumulated a fast mutating SNP in the last few generations, which would give them a different signature.

Someone who is actually genealogically close to you may be in a different haplotype, or no haplotype at all because no one matches them exactly. For example, if your aunt or sister has a heteroplasmy, they are a close relative and will be in your haplogroup, but won’t be in your haplotype cluster because of the heteroplasmy. So don’t ignore matches who aren’t in your haplotype.

In the above example, under haplogroup V71b, there is one group of three people of unknown origin, meaning they didn’t enter any location for their earliest known ancestor, plus haplotype F9712482 – all of whom are identical matches to each other, but don’t form a new haplogroup.

Beneath V71b is haplogroup V71b1 with nine people, plus two haplotype clusters. F1965416 consists of two people, and F8189900 consists of 16 people.

You can also see haplotype clusters bracketed on any of the Time Trees in mtDNA Discover as well.

More to Come

There’s more information to come in the next few days and weeks, and at RootsTech. I’ll be writing articles when I get back.

For now, take a look to see if you have a new haplogroup. The new haplogroup rollout is being staggered, and you should receive an email when yours has been posted. But there’s no need to wait. Go ahead, sign in and check now, check out mtDNA Discover, and have fun.

Guaranteed, you’ll learn something new, and you may discover the key to a new ancestor!

Resources

Here are additional resources about the new Mitotree, mtDNA Discover, and the associated updates:

_____________________________________________________________

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 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

Leave No Stone Unturned, No Ancestor Behind: 10 Easy Steps to Capture DNA Clues

There’s a lot, a whole lot that DNA testing can tell you. Not just your own tests, but the genetic information carried by your relatives that you do not.

Recently, I’ve been reviewing my brick walls, which led me to realize there are several ancestors who are missing their mitochondrial DNA and/or Y-DNA  results. I need these to learn more about my ancestors that can’t be revealed any other way – and to break down those pesky brick walls.

I’ve solved two mysteries recently, one thanks to a Big Y-700 test, and a second very unexpectedly thanks to mitochondrial DNA – both thanks to cousins who tested. These revelations were very encouraging, especially since there’s no way other than DNA for me to break through these brick walls. The mitochondrial test had been sitting there, waiting for what seemed like forever until just the right other person tested.

I am in the process of unlocking several brick-walled ancestors by providing testing scholarships to people who are appropriately descended from known ancestors in those lines.

Don’t leave information on the table. If I were to tell you there even MIGHT be a book available about your family, you’d overturn Heaven and Earth to find it – but you don’t need to do that. All you need to do is order DNA tests for cousins.

All cousins can provide useful autosomal DNA results, but you do need to find appropriate cousins for Y-DNA and mitochondrial DNA testing.

I’m sharing the steps for how I accomplish this! You’ll be amazed at what’s out there – and someone may already have tested!

Take Advantage of the Holidays

I’m sharing NOW because it’s the holidays and you’re likely to gather with people you don’t see any other time – and because the best sale of the year for both Y-DNA and mitochondrial DNA lasts from now through the end of the year.

These two factors combined mean strike while the iron is hot.

Prices for new tests and bundles are at an all-time low.

If you or your relatives have already taken a lower-level test, now is the time to upgrade to either the Big Y-700 or the mtFull Sequence test.

Step 1 – Test Yourself and Your Known Family

If you’re a male, order both the Big Y-700 test and mitochondrial DNA tests.

Be sure to click on “See More” for more useful tools.

When you receive your results, be sure to click on all of the tabs in your results, and do the same by clicking through to Discover from your account. Discover has 13 more goodies for you to help with your genealogy.

Both your personal page and Discover are essentially chapters of your own personal book about your DNA results. 25 very interesting chapters, to be precise, that are uniquely you.

I’ve written about understanding Y-DNA results here, and mitochondrial results here. My book, Complete Guide to FamilyTreeDNA, covers both along with Discover.

Discover provides robust information for Y-DNA haplogroups. If you’ve taken a Big Y-700 test, you’ll want to click through from your page to receive additional, personalized and more robust information than is available through the free public Discover tool. That said, the public version of Discover is an amazing tool for everyone.

After the new Mitotree is released for mitochondrial DNA, mitochondrial haplogroups will be available in Discover too.

I can’t even begin to stress how important these tools are – in particular the Time Tree, the Group Time Tree for members of group projects, and the Match Time Tree for your own matches.

Who Can Test For What?

Once you’ve tested yourself, you will want to take a look in your pedigree chart at branches further up your tree to see who can be tested to represent specific ancestors.

Let’s begin with my father’s side.

A mother contributes her mitochondrial DNA to all of her children, so your father carries the mitochondrial DNA of his mother.

If you’re a female, and your father is available to test, you’ll want to test BOTH his mitochondrial DNA and Y-DNA, because there’s no way for you to obtain that information from your own test. Females don’t have a Y chromosome, and men don’t pass on their mitochondrial DNA.

If you’re a male, you can test your own mitochondrial DNA and Y-DNA, but you’ll need to test your father’s mitochondrial DNA to obtain his mother’s. You might still want to test your father’s Y-DNA, however, because you may discover a personal family haplogroup. How cool is that??!! Your own tiny branch on the tree of mankind!

Your father’s mitochondrial DNA provides you with mitochondrial matches and haplogroup information for your paternal grandmother – in this case, Ollie Bolton.

If your father and his siblings can’t test, then all of the children of your paternal aunts carry your paternal grandmother’s mitochondrial DNA.

If they have no children or they can’t test, then the children of Ollie Bolton’s mother, Margaret Claxton/Clarkson all carry her mitochondrial DNA, and the children of Ollie’s sisters continue the line of descent through all daughters to the current generation.

The male children of Joseph “Dode” Bolton and Margaret Claxton carry his Y-DNA. Fortunately, that’s not one of our missing haplogroups.

Yes, you may have to climb up your tree and climb down various branches to find a testing candidate.

One of the reasons I’m using this example is because, while I have a high-level haplogroup for my grandmother, Ollie Bolton, we need a full sequence tester – and I’m offering a mitochondrial DNA testing scholarship for anyone descending from Margaret Claxton (or her direct female ancestors) through all females to the current generation, which can be male.

Ok, now let’s switch to the maternal side of your tree.

On the other side of your tree, your maternal grandfather or your mother’s brothers will provide the Y-DNA of your mother’s father’s line. Your mother’s uncles or their sons will provide your grandfather’s Y-DNA line, too. In this case, that’s John Whitney Ferverda, who carries the Y-DNA of his father, Hiram Bauke Ferverda/Ferwerda.

Your maternal grandfather or his siblings will provide the mitochondrial DNA of their mother, Evaline Louise Miller.

If they are deceased or can’t test, for mitochondrial DNA, look to the children of Evaline Miller’s daughters or their descendants through all females to the current generation, which can be male.

And yes, in case you’re wondering, I do need Evaline Miller’s mitochondrial line too and am offering a scholarship.

You might have noticed that I’ve been inching my way up my tree. All of my immediate relatives have passed over already, so I’m now looking for testers that I don’t know but who I’m related to.

If you’re seeing family members anytime soon, figure out if their Y-DNA, mitochondrial DNA, or autosomal DNA would be useful for your common genealogy. Take advantage of the opportunity.

Next, you’ll want to figure out which ancestors need haplogroups and locate appropriate cousins.

Step 2 – Identify Ancestors Who Need Haplogroups

Peruse your tree to determine which of your ancestors you need haplogroup information for. To make it easy, on my computer, but never in a public tree anyplace, I store the haplogroup of my ancestor as a “middle name” so I can easily see which ones I have and which ones I need. Sometimes, I have a high-level haplogroup and either need a new tester or someone to upgrade.

Sometimes, I have one tester from a line but need a second for confirmation.

In this example, I’m not missing confirmation on any Y-DNA haplogroups (although I am further upstream on different lines,) but I do need four different mitochondrial DNA lineages.

For easy reference, make a list of all of the lines you can’t confirm with two testers from different children of the same ancestor.

You just might get lucky and discover that someone has already tested!

Step 3 – Check FamilyTreeDNA Projects

Check FamilyTreeDNA Projects to see if someone has already tested to represent those ancestors on your list.

Click here for the Group Project Search. It’s located at the very bottom of the main FamilyTreeDNA page in the footer.

I’m going to use Estes as an example since I’m the volunteer administrator of that project and am very familiar with the lineages.

I’m searching for projects that include the surname Estes.

The projects displayed on the list are projects where the volunteer administrators listed Estes as a possible surname of interest. It doesn’t mean those projects will be of interest to everyone or every line with that surname, but evaluate each project listed.

You probably want the surname project, but if there’s not a surname project for your surname, try alternate spellings or consider checking other projects.

You can see at the bottom that 384 people of both sexes by the surname of Estes have tested at FamilyTreeDNA.

Now, let’s look at the Estes project. Note that not everyone with the Estes surname has joined the Estes project.

I’ve clicked on the “Estes” link which takes me to an additional information page where I can read a description and click to view the project.

For the Estes project, you do not have to join to view the results. Nor does your surname have to be Estes. All Estes descendants of any line are welcome. Everyone can benefit from the Advanced Matching within project feature to see who else you match within the project by selecting a wide range of individual and combined filters.

Click on the Project Website link shown in the search results.

If you’re searching for a male Estes ancestor, you’ll want to review the project’s Y-DNA Results and the Group Time Tree, for sure, and possibly the Map as well.

Let’s pretend I’m trying to determine if anyone has tested who descends from my ancestor, Abraham Estes, the founding Estes ancestor in Virginia who arrived in the mid-1600s.

In the Estes project, the volunteer administrator has divided the Estes male participants by sons of Abraham, the immigrant. Only three are shown here, but there are several.

Some of the participants have completed their Earliest Known Ancestor information, in the red box. Sometimes people don’t think to update these when they make breakthroughs.

If you descend from Abraham’s son, Sylvester, three men have taken the Big Y-700. That’s the test results you need.

If you descend from Abraham’s son, Abraham, no project participants have taken the Big-Y test to represent that line, although six people have tested, so that’s great news. Maybe you can offer an upgrade scholarship to one or some of those men.

In other words, to establish the haplogroup for that lineage, at least two men need to test or upgrade to the Big Y-700, preferably through two different sons of the common ancestor. A new, more defining haplogroup is often formed every two or three generations for Y-DNA.

Your genetic pedigree chart looks a lot like your genealogy pedigree chart.

Click any image to enlarge

The project Group Time Tree shows selected groups of men who have taken Big Y tests, along with their Earliest Known Ancestor, if they’ve provided the information. This is one of the reasons why the Big Y-700 is so critically important to genealogy. The time granularity is amazing and can answer the question of whether men by the same surname descend from the same common ancestor – and when.

If you’ve taken a Family Finder autosomal test at FamilyTreeDNA, or uploaded an autosomal file from another vendor, you may match one of these men or another male that descends from the Estes line if they, too, have taken an autosomal test.

This same process applies to mitochondrial DNA, but generally surname projects aren’t (as) relevant for mitochondrial DNA since the surname changes every generation. However, sometimes other projects, such as the Acadian AmerIndian Project are quite beneficial if you have Acadian ancestry, or a geographic or regional project like the French Heritage Project, or something like the American Indian Project.

Another great way to find testers is by utilizing your Family Finder test.

Step 4 – Family Finder at FamilyTreeDNA

The next step is to see if you match anyone with the surname you’re searching for by using your autosomal test results, so select your Family Finder Matches.

At FamilyTreeDNA you’ll want to search your matches by the surname you seek. This surname search lists any tester who has that surname, or anyone who has entered that surname in their surname list. Please note that this search does NOT read ancestors in your matches’ trees. You’ll still need to view trees.

Reviewing the 32 Estes Family Finder matches reveals several men, but one man with the Estes surname has already taken a Y-DNA 25-marker test, so he would be an excellent candidate to offer a Big Y-700 upgrade scholarship. If he’s not interested or doesn’t respond, there are several more men to contact.

Click on your match’s name to display the profile card, along with the Earliest Known Ancestors, both Y-DNA and mitochondrial DNA haplogroups if they have tested, and the assigned haplogroup based on their testing level.

Craft an email and offer a testing scholarship. This will help both of you. I’ll provide a sample email at the end of this article.

If you match a female with an Estes surname, her father, brother, uncle or cousin may either have already tested or be willing.

If you match someone who has a different surname, that means they have an Estes surname in their surname list and may know a potential tester. If your match has a tree, click to check.

I’ve found that matching through a company where you’ve both tested is the easiest way to encourage someone to take an additional test, but certainly, it’s not the only way.

Step 5 – WikiTree

WikiTree is a quick and easy way to see if anyone has taken Y-DNA or mitochondrial DNA test that should reflect a particular ancestor’s Y-DNA or mitochondrial DNA.

I just googled “Moses Estes 1711-1787 WikiTree” and clicked to view.

Each ancestor includes both Y-DNA and mitochondrial DNA information, in addition to people who descend from that ancestor through only autosomal lines.

In this case, two men have provided their Y-DNA results that pertain to Moses Estes. They have tested at different levels, which is why they have different haplogroups. That doesn’t mean either is “wrong,” one is just more refined than the other. You can correlate their kit number with the Estes surname project. People often don’t update their haplogroup information at WikiTree when it’s updated at FamilyTreeDNA.

Please note that if the genealogy is wrong, either at WikiTree or individually, the haplogroup may not reflect the appropriate lineage for the ancestor. Check to be sure that there’s no conflict showing between two testers for the same ancestor. For example, the same ancestor clearly can’t have two different base haplogroups, like E and R. The Discover Compare tool can help you evaluate if two haplogroups are in the same part of the Y-DNA tree.

When possible, it’s always best to test a close family member to represent your lineage even if someone else has already tested.

Scan down the list of autosomal testers for that ancestor to see if there’s someone with the Estes surname.

WikiTree provides additional tools to find descendants.

Sign in to WikiTree. You’ll see the ID of the profile you’re viewing – in this case – Estes-167. Click the down arrow and select “Descendants.”

This view shows all descendants through five generations, but you can click on DNA Descendants to see only Y-DNA descendants, X-DNA, or mitochondrial DNA descendants for female ancestors.

You may find people who are living and have added themselves who you can contact to offer a DNA testing scholarship.

Step 6 – MyHeritage

At MyHeritage, you can also search your DNA matches by surname.

Click on “Review DNA Match” to view more detail, including locations. Look to see if you have a Theory of Family Relativity Match which suggests how you may be related. That’s golden!

There’s no Y-DNA information at MyHeritage, BUT, you can search by surname and view DNA matches that either carry that surname or have that surname in their tree as an ancestor.

I have a total of 75 “Estes” matches, and other than the kits that I manage, searching through my matches shows:

  • Two Estes men connected to the same small tree, but that’s OK, I’m a genealogist!

  • One Estes male match with a Theory of Family Relativity. My lucky day!

You can contact your match easily through the MyHeritage messaging system and offer a DNA testing scholarship at FamilyTreeDNA. You may also want to share your email address.

MyHeritage customers may not be familiar with Y-DNA or mitochondrial DNA testing, so you might want to share this article about the 4 Kinds of DNA for Genealogy.

MyHeritage testers can also upload their DNA file to FamilyTreeDNA for free to receive autosomal matches plus a complimentary mid-range Y-DNA haplogroup. This free haplogroup is not even close to the detailed resolution of a Big Y-700 test, but it’s something, and it may well be an enticing first step for people who are only familiar with autosomal testing.

Step 7 – At Ancestry

At Ancestry, select DNA Matches and then search by surname.

You can search by the surname of the tester, which is very useful, or by people who have Estes in their trees.

I started with the surname Estes, because it’s the most straightforward and I may find a perfect male candidate for Y-DNA. If someone’s “screen name” doesn’t show as Estes, they won’t appear in the results of this search. In other words, if your Ancestry screen name is “robertaestes” you won’t show in this search, but “Roberta Estes” will.

For mitochondrial DNA, you would want to search for the surname in your matches’ trees. Unfortunately, you cannot search for the specific ancestor in someone’s tree, at least not directly.

Of my 19 Estes surname matches, ten are males, and of them:

  • Three have unlinked trees
  • Three have very small linked trees, but I can work on extending those if need be
  • Three have public linked trees AND a common ancestor, which means ThruLines

I can review which ancestor we share by clicking on my match’s name

The Estes side of this man’s tree has only one person and is marked “private,” but Ancestry has suggested common ancestors based on other people’s trees. (Yes, I know trees are dicey, but bear with me.)

It’s also worth mentioning that you can be related through multiple lines. I share surnames from Acadian lines with this man, but that really doesn’t matter here because I’m only using autosomal matching to find an Estes male.

Click on “View Relationship” to see our common Estes ancestor’s ThruLine.

The ThruLine shows how Ancestry thinks we’re related on the Estes line.

I can also click on “View ThruLines” to see all Thrulines for John R. Estes, which shows four additional males, some of which did NOT appear in the Estes surname search, and some of which don’t appear further up the tree. In other words, check all Estes ThruLine ancestor generations.

Don’t rely solely on Ancestry’s surname search.

Go directly to your ThruLines on the DNA menu.

Ancestry only reaches back seven generations, which for me is Moses Estes and Luremia Combs. Moses has 95 matches, but he has been given some incorrect children. Again, for this purpose, it doesn’t matter. Within all ThruLine matches, I found three Estes males who all descend through John R. Estes. Check every generation.

However, Luremia Combs shows promise for mitochondrial DNA descendants. Unfortunately, only two of her daughters are represented in ThruLines, and both of their descendants descend through Luremia’s grandsons. That’s too bad, because I need Luremia’s mitochondrial DNA line.

It’s easy to message your Ancestry matches. You may want to mention that they can upload their DNA file to FamilyTreeDNA for free where they will receive more matches and males will receive a complimentary mid-level Y-DNA haplogroup.

Please note that, in general, ThruLines need to be evaluated very carefully and are prone to errors, especially if you accept Ancestry’s suggestions of ancestors instead of carefully building out your own tree. Regardless, you can still find Estes cousin matches in your match list and by using ThruLines to find people that do not show up in an “Estes” match search.

Step 8 – At 23andMe

At 23andMe, you can search for anyone who either has the Estes surname or has included that surname in their “Family surnames” list. Keep in mind that your matches at 23andMe are restricted to either 1500 if you don’t have a subscripition, or about 4500 if you do have a subscription.

On my match list, I have two males with the Estes surname.

23andMe provides a mid-level Y-DNA haplogroup. You can’t use this to confirm the lineage when comparing with FamilyTreeDNA, especially given that 23andMe provides no genealogy or user-provided tree, but it is a clue.

Both Estes men at 23andMe have Y-DNA haplogroup R-CTS241. You could use this in some cases to potentially eliminate these matches at 23andMe. For example, if men in your lineage in the Estes project are in haplogroup R and your 23andMe matches are showing as haplogroup E, or any other base haplogroup, their common ancestor is tens of thousands of years ago.

Comparing the 23andMe haplogroup, which in this case is about 4500 years old, to contemporary testers who have taken the Big Y-700, which reaches within a few generations, isn’t terribly useful. These matches are extremely useful to identify individuals to reach out to for further information and potentially offer a Y-DNA testing scholarship at FamilyTreeDNA.

Remember, this also applies to females who have included Estes in their family surnames, given that they may have Estes male relatives.

By clicking to view your match, you can see if they have provided Family Background information, including a link to a family tree someplace.

Sometimes, there’s great information here, and other times, nothing.

You can’t verify this lineage without genealogy information.

I suggest leaving a genealogy-focused message, including where they can see your tree in addition to your Estes connection. Also include your e-mail.

You may want to say that if they descend appropriately, you have a Y-DNA or mitochondrial DNA testing scholarship, or you may want to wait to see how they descend. You can also ask if they have already taken a Y-DNA or mitochondrial DNA test at FamilyTreeDNA.

Step 9 – FamilySearch and Relatives at RootsTech

We’re getting ready for RootsTech 2025 which takes place in March. In the month or so before the last two RootsTechs, FamilySearch provided an absolutely wonderful tool called “Relatives at RootsTech.”

I’ve written about this several times, but essentially, you can see, by ancestor, other people who are registered both in-person and virtually for RootsTech, and how they descend.

Here’s an example.

In both years, I’ve found several people who descended from common ancestors AND were very willing to take the relevant DNA test. That’s a huge win-win for everyone.

The best part is that because these people have freshly registered for RootsTech, the reply rate is almost 100%.

I’ll write about this as soon as RootsTech makes it available this year. Fingers crossed that they do!

Step 10 – Social Media

Social media wouldn’t be my first choice to find DNA testers, but I have found perfectly willing cousins this way. You may be less successful on Facebook or other social media platforms, but if you’re striking out elsewhere, there’s absolutely no downside to trying.

You can enter a surname and search on Facebook, but I prefer to do a Google search like “Estes genealogy on Facebook” or even just “Estes genealogy,” which will produce far more widespread information, some of which may be irrelevant.

That Facebook Google search provided the names of two groups. People join groups because they have an interest, and I’ve had good luck in Facebook genealogy groups.

A Search of “Estes” on Facebook itself, then selecting “people” provided a list of Estes Facebook users.

I’ve had far better luck by joining a group that is focused on Estes genealogy, or even a county genealogy group that includes Estes families, than individuals. People who join any Estes group or project likely have an interest in that surname.

If you have a common surname, or there’s a park named after your surname, like Estes Park, you’ll probably want to focus by using Google searches for Estes genealogy.

The Descendants of Abraham Estes Facebook group has 222 members, of whom at least 31 are males with the Estes surname. Facebook just might be an underestimated resource.

If there isn’t a genealogy-focused group for your surname, you might want to consider starting one and encouraging people to join.

It can’t hurt, and it just might help. Before you start reaching out to random people on Facebook, please do a privacy checkup – I wrote about how, here.

Sale Prices

Remember, the sale prices at FamilyTreeDNA for new tests and upgrades last through year-end.

In my experience, it’s best to test as soon as someone agrees. You never know what will happen otherwise. I’ve had people pass away before they could swab. And yes, we’ve done funeral home swabs, too.

There’s no one-size-fits-all, but here’s a rough draft contact letter.

Potential Contact Letter

You’ll want to include several critical pieces of information.

Essentially:

  • Introduce yourself
  • Say their full name on their test AND the testing company in the title of an email. I manage many tests and if I receive an email that says, “Hi, can you tell me how we match” without telling me which person they match, I can’t even begin to answer.
  • Explain your genealogy connection
  • State your purpose in writing
  • Explain how a specific test will help them too
  • Offer to answer questions

Be sure to modify this letter to reflect your own voice and circumstances. You don’t want this to read like a form letter.

Dear cousin (insert their full name here,)

It was so nice to find our DNA match at <company name> (or we share a common ancestor, or appropriate circumstance.) (If you are managing someone else’s kit, say the name of who they match and explain that you manage their DNA kit.)

I descend from (ancestor plus birth and death date) who lived in Halifax County, Virginia and was married to (spouse.) You can view my tree at (insert link that does not require a subscription for viewing unless you match them on that platform. I use MyHeritage because everyone can view their trees)

I would very much like to confirm that our line descends from Abraham Estes (or relevant information meaning your reason for wanting them to test.)

Given that my surname is x (or I’m a female), we need to test the Y-DNA of a male who is descended from (ancestor) through all males to the current generation. (Or mitochondrial DNA descended through females to the current generation which can be male.)

FamilyTreeDNA provides this testing and shows who you match on that specific line using the Y chromosome (mitochondrial DNA).

This testing may connect us with earlier ancestors. Genetics can be used to determine when we share common Estes ancestors with others who test, where we come from overseas, and when. Even if we match ancient DNA samples that may tell us where our ancestors lived before surnames. In other words, where did we come from?

(Include a nice paragraph, but not a book about your ancestral lineage here.)

I have a DNA testing scholarship for someone from this line and you are the perfect candidate. I would like to take advantage of the current sales. If you’re interested, I only need two things from you.

First, permission so that I can order (or upgrade) and pay for the test, and second, an address where to send the test (unless it’s an upgrade). (If it’s an upgrade at FamilyTreeDNA, they can use a stored sample or will sent them a new kit if there’s not enough DNA.)

If you have any questions, please let me know. I’m very excited that we may be able to learn more about our heritage.

Please email me at xxx or call me at xxx if you have questions.

Your name

I know one person who offers to review results over Zoom. Someone else stresses that the tester’s email is attached to their test and they are always in control of their results. Another person asks them to join a project they manage to assure that they can follow their matches over time.

Customize this communication in your own voice and to fit the circumstances of each match.

It’s just me, but since I’m ordering while the tests are on sale, unless the person uploads their DNA file from another vendor, I add on a Family Finder test too and explain why. You never know if they will match you or another cousin, and they may have that match that eventually breaks down the next brick wall. Shared matches are powerful evidence and it’s a lot easier to add that test on now than try to contact them again later.

You Don’t Know What You Don’t Know

Which ancestors do you need Y-DNA or mitochondrial DNA results for? Methodically check each line.

There’s so much to learn. Don’t leave information on the table by virtue of omission.

Leave no stone unturned!

You don’t know what you don’t know.

Who’s waiting out there for you?

____________________________________________________________

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 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

Announcing: The Complete Guide to FamilyTreeDNA; Y-DNA, Mitochondrial, Autosomal and X-DNA

I’m so very pleased to announce the publication of my new book, The Complete Guide to FamilyTreeDNA – Y-DNA, Mitochondrial, Autosomal and X-DNA.

For the first time, the publisher, Genealogical.com, is making the full-color, searchable e-book version available before the hardcopy print version, here. The e-book version can be read using your favorite e-book reader such as Kindle or iBooks.

Update: The hardcopy version was released at the end of May and is available from the publisher in the US and from Amazon internationally.

This book is about more than how to use the FamilyTreeDNA products and interpreting their genealogical meaning, it’s also a primer on the four different types of DNA used for genealogy and how they work:

  • Autosomal DNA
  • Mitochondrial DNA
  • Y-DNA
  • X-DNA

There’s a LOT here, as shown by the table of contents, below

This book is chocked full of great information in one place. As an added bonus, the DNA glossary is 18 pages long.

I really hope you enjoy my new book, in whatever format you prefer.

_____________________________________________________________

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 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 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

Bennett Greenspan: Meet My Extended Family & Discover Extraordinary Deep Heritage

“My ancestors are in my soul. I can’t get them out of my mind.”

Bennett Greenspan

“And yes, I brake for cemeteries.”

Bennett Greenspan gave an incredibly interesting presentation at the 15th International Genetic Genealogy Conference held by FamilyTreeDNA in November 2023. Since his retirement in January 2021, he has been able to focus on his genealogy. Once a genealogist, always a genealogist.

Bennett said some things I hadn’t thought about, and now I’m viewing Y-DNA matches with a different perspective – based on how he’s using his results.

Ever since I met him, Bennett’s focus has been to use genetics to unravel his complex Jewish heritage.

The questions that drive Bennett are the same ones that motivate most genealogists:

  1. Who are we?
  2. Where did we come from?
  3. Where were we before we were there?
  4. How did my ancestors get there?

Bennett “lost his family lines” before the mid-1800s due to his Jewish heritage, exacerbated in the 1930s by the devastation wrought by the Holocaust. Families were either killed or scattered to survive. It has been through Y-DNA in particular that he has been able to establish unquestionable and confirmed connections with other Greenspan men, sometimes by similar but different surnames, like Green, and sometimes with other surnames entirely.

When Bennett first started down this path, he tested more than 62 men before actually finding one a decade later that matched his Y-DNA. Bennet commented that it was “a little frustrating.”

Persistence is the key, and sometimes, genealogy is a waiting game, but that’s small comfort to genealogists during that unproductive waiting period.

Eventually, Bennett reassembled his family, at least somewhat, but it was a long journey. Here’s Bennett’s incredible story, including surprises, as he tells it.

Bennett discovered genealogy at age 12 and, like many genealogists, created a pedigree chart by talking to his family.

I love the mark-outs. How many of us still have our first chart with its edits?

This is the young Bennett Greenspan, whose interest in genealogy would one day unlock secrets for all of us!

It was a long way from a decade with no matches to finding his genetic kin in Ukraine.

The Big Y-700 Time Tree shows Bennett’s lineage in Ukraine, but stepping back in time, some descendants of his ancestors are found in adjacent locations.

Bennett was passionately discussing his matches on the time tree and in the Greenspan project, so I visited the Greenspan DNA Project, where the earliest known ancestors of Bennett’s Big Y matches are shown on the Group Time Tree.

Bennett’s closest matches are shown as descendants of haplogroup J-ZS1718. He has additional matches who are not in the Greenspan project. Since this is the Group Time Tree, it only displays the people in that project, along with their earliest known ancestors, Isaac and Usher Greenspan.

12-Marker Matches

Bennett never fails to amaze me. He said something very important and profound about 12-marker matches that I really hadn’t thought about – at least not this way.

As a community, we are often guilty of discounting 12-marker matches, those that don’t match us at 25-markers or above, or with different surnames, as “too far back in time” or otherwise irrelevant. I always look at the names and earliest known ancestors of 12-marker matches, because that person may have tested back in the day when fewer markers were available. But if I don’t recognize something, I move on.

However, Bennett said that, ”Y-12 matches reach back to a common ancestor. 12-marker matches are not a quirk. They are related to you, just further back in time. You share a common ancestor with them, someplace. They may be more distant, but they are still your close matches.”

I’ve been in too much of a hurry for a quick win, and ignoring the (apparently not so) obvious.

Determining when and where their ancestors lived also paves the way to discover yours. Your Y-DNA and theirs were in the same place at the same time.

Of Bennett’s 171 12-marker matches, 107 have upgraded to the Big Y, probably mostly due to his encouragement. This benefits both them and Bennett by fleshing out the history of that entire group of men, including how they got to where they are found in the first available records. The Time Tree shows when Big Y testers shared a common ancestor, and based on Earliest Known Ancestor (EKA) locations, where. This provides further information about the lives of ancestors before contemporary records – in other words – people that we can never identify by name. It’s a window into ancestors before surnames.

Bennett notes that testers need to know their ancestral village or location to be most useful within the project, and of course, they need to enter their EKA information. Location information is how the Migration Map, Matches Map, and Discover tools, including the Time Tree, are built.

What Happened in Spain?

Bennett’s ancestors and those of his 12-marker matches are found in Spain, and as Bennett says, “One son stayed and one left about the year 296.”

While we have no idea of their names, based on the Time Tree combined with the cluster of earliest known ancestors, we know that they were in Spain, and when.

Their family story is revealed in the bifurcation of the tree found beneath haplogroup J-L823, formed about 296 CE. One line stayed in Spain, and Bennett’s line migrated to eastern Europe where that man’s descendants, including Bennett’s family, are found in the Russian Federation, Belarus, Poland, Lithuania, Sweden, Slovakia, Ukraine, Germany, Romania, the Czech Republic, and other eastern European locations. The closer to you in the tree and in time, the more relevant to your more recent ancestral story.

However, Bennett’s deeper ancestry, the migration of his ancestors to Spain, was only revealed by testing those more distantly related men. Those same men could well have been ignored entirely because they only matched at 12 markers.

According to Bennett, “Y-12 markers are important because these are the men most closely related to you in a database of 1 million men.”

How incredibly profound. How much have I been cavalierly overlooking?

How does this actually apply to Bennett’s results?

Bennett’s Spanish Matches

Bennett has the following STR panel matches who indicate that their EKA are from Spain. You can see that they match Bennett on a variety of panels.

  • X = yes, match
  • No = no match
  • Blank = not tested at that level.

In the Big Y GD column, the genetic distance (GD) is displayed as 15/660 where 15 is the number of mismatches, or the cumulative genetic distance ABOVE the 111 panel, and 660 is the number of STR markers above 111 with results.

The Big Y-500 test guaranteed a minimum of 500 total STR markers, and the Big Y-700 guarantees a minimum of 700 total STR markers, plus multiple scans of the balance of the Y chromosome for SNP mutations that define haplogroups. Testers don’t receive the same number of markers because the scan technology sometimes doesn’t read a specific location.

Tester 12 25 37 67 111 Big Y Test Big Y GD Big Y Match Haplogroup
AA X X X No No Yes 15/660 No J-FTD8826
DT X X No No X Yes 17/664 No J-FTE50318
JG X X No No
AR No No X X No No
ELR X X X No No
EL X X Yes 17/666 No J-FTE50318
GC X X X X No No
JC X No No
JLG X X No No No Yes 14/662 No J-FTE23540
MF X X No X No Yes 15/665 No J-FTD91126
MT X X X X No No
BE X X X X X Yes 20/664 No J-BY1795
DR X X X X X Yes 16/660 No J-FTC87344
EC X X X X X Yes 15/665 No J-FTC87344
GM X X No No No Yes 16/650 No J-FTD28153
GM X X X X No Yes 17/664 No J-FTD11019
LS X X No No No Yes 18/666 No J-FTD28153
NE X X X X X Yes 23/597 No J-BY1795
NC X No No
RR X X X No X Yes 22/659 No J-BY1795
TT X X X X X Yes 16/647 No J-FTC87344
XG X X X No No Yes 17/523 No J-BY167283
JA X X No No No Yes 15/646 No J-FTD11019

Of those 23 Spanish matches, sixteen have upgraded to Big Y tests, 14 of which are Big Y-700s, resulting in nine different haplogroups, all of which are descendants of Haplogroup J-L823. How cool is that?

The “Nos” in the Big Y Match Column aren’t mistakes. That’s right – none of these men match Bennett on the Big Y test, meaning they had more than a 30 mutation difference between them and Bennett on the Big Y test.

At first glance, you’d think that Bennett would have been disappointed, but that’s not the case at all! In fact, it was the information provided by these distant Spanish matches that provided Bennett with the information that his line had split sometime around the year 296 CE, with one branch remaining in Spain and his branch migrating to Eastern Europe, where he has lots of matches.

DNA Plus History

What was happening in Spain or the Iberian peninsula that involved the Jewish people about that time? Historical records exist of Jews living in that region before the fall of the Second Temple in about 70 CE, including records of Jews being expelled from Rome in 139 for their “corrupting influence.”

Furthermore, the Ancient DNA Connections for haplogroup J-L823, the most recent common ancestor (MRCA) for all of those branches, includes connections to multiple burials from:

  • Lebanon
  • Iran
  • Rome (from 1-400 CE)
  • Turkey
  • Jordan

Clearly, Bennett’s ancestor was in the Iberian peninsula around or before 296 CE. One branch stayed, winding up in Spain, and one headed for Europe.

Without these matches, some who didn’t match above the 12 or 25 marker level, how would Bennett have EVER known that his Jewish ancestors left the Middle East for Spain in the early years? How would he have known they migrated from Spain to Eastern Europe, and how would he have known that his line did not migrate directly from the Levant to Eastern Europe in the 9th century?

Big Y matches are typically within about 1500 years, but non-matches are still INCREDIBLY valuable. Without them, you can’t completely assemble your family story.

I noticed on the Time Tree that in Bennett’s Eastern European line, one of his ancestor’s brother lineages includes the Katzenellenbogen Rabbinic Lineage derived from ancient DNA samples.

Bennett’s successes have resulted from contacting his matches and encouraging upgrades. So how did he do it? What’s the magic sauce?

Contacting Matches

How to contact matches successfully is a question I see often. In fact, FamilyTreeDNA recently wrote about that in an article, here.

Bennett’s methodology for contacting his matches to encourage an upgrade is that he sends an email explaining why he’s encouraging them to upgrade, followed by a 2nd email three days later.

Bennett tells the recipient that we are at an inflection point in time. “It’s winter, the wind is blowing hard, and many of the leaves are gone.”

In other words, we need to cast the net wider and capture what we can, while we can. Unfortunately, many early testers have died, and with them, chapters of history are perishing.

Collaboration is key. In addition to encouraging upgrades, Bennett also offers Zoom calls to these groups of men to explain the results if they are interested.

What a GREAT idea! I need to begin offering that as well.

Upgrade Request

Bennett reaches out to his matches at various levels, but he expects his closer STR matches, meaning at the 67 and 111 marker level with the fewest mismatches, to match him on a Big Y-700 test and connect someplace between 300-600 years ago, which helps everyone flesh out their tree.

Bennett’s email:

Hello <name>,

Since you have already made a sizable investment in your Y-DNA, you now know that we come from the dominant male Middle Eastern group (Haplogroup J) of men who <subject here>.

What’s really neat is that our Y-DNA has recently been found in an archaeological site in Northwestern Jordan dated to about 4200 years ago. I know this because I upgraded to the Big Y, which tests SNPs, looking at several million locations on the Y chromosome of each man.

One academic customer recently compared this new technology as the difference between looking into space with binoculars versus the Hubble Telescope.

I don’t know if you are familiar with your list of matches at the highest level you’ve tested for, either Y-67 or Y-111. If you are, you should recognize my name and the names of others who have taken the Big Y test.

You’ll see what you’ll gain by letting me upgrade your test for you and determining whether you are related to my line – probably between about 200 years and 500 years.

This might be the second time that I have written to you on this matter; can I presume if I don’t hear from you that you’re not really interested in the Y-DNA subject anymore?

Can I run the test so that I can see how closely we are related – at my expense? (Of course, you get to see how closely related we are, too).

Please reply to me and say “yes.” You don’t even have to put a 🙂 if you don’t want to.

I started this company and this industry over 20 years ago. I predict that you will be happy with the history of YOU that this upgrade will uncover.

Best,

Bennett Greenspan

As you can see, this email can easily be personalized further and adapted to matches at the 37, 25, and 12 marker levels – or even Family Finder matches, now that intermediate-range haplogroups are being reported.

What’s Next?

I’m going back to every one of the kits I sponsored or that represent descendants of one of my ancestors to review their matches again – focusing not just on the closest matches with common surnames, but also on locations – and specifically at lower matching levels. I’ll also be checking their Family Finder matches for male surname matches, or similar surnames.

As is evident from Bennett’s tests, an entire mine of diamonds is out there, just waiting to be unearthed by a Big Y test.

And to think that some people have been advising people to ignore 12-marker matches out-of-hand because they are “entirely irrelevant.” They aren’t – for two reasons.

  1. First, some early testers only tested to that level
  2. Second, because of the deeper history that Big Y tests from those matches will uncover

You can view your Y-DNA matches, upgrade your own Y-DNA test, or order a Big Y-700 test if you haven’t yet tested by clicking here. What’s your next step?

_____________________________________________________________

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 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 Book

Genealogy Books

Genealogy Research

FamilyTreeDNA 2023 Update – Past, Present and Future

At the FamilyTreeDNA International Conference on Genetic Genealogy, held November 3-5 in Houston for group project administrators, product and feature updates were scattered across both days in various presentations.

I’ve combined the updates from FamilyTreeDNA into one article.

I’ve already written two articles that pertain to the conference.

FamilyTreeDNA has already begun rolling the new Y DNA haplogroups from Family Finder autosomal tests, which I wrote about here:

I still have at least two more articles to publish from this conference that was chocked full of wonderful information from a wide range of talented speakers.

Past, Present, and Future with Katy Rowe-Schurwanz

Katy Rowe-Schurwanz, FamilyTreeDNA’s Product Manager, provided an update on what has been accomplished in the four and a half years since the last conference, what’s underway now, and her wish list for 2024.

Please note the word “wish list.” Wish list items are NOT commitments.

Recent Milestones

A lot has been happening at FamilyTreeDNA since the last conference.

Acquisition and Wellness Bundles

As everyone is aware, at the end of 2020, myDNA acquired Gene by Gene, the parent company of FamilyTreeDNA, which included the lab. As a result, the FamilyTreeDNA product menu has expanded, and wellness bundles are now available for FamilyTreeDNA customers.

If you’re interested, you can order the Wellness product in a bundle with a Family Finder test, here.

You can add the Wellness product for $39 if you’ve already tested.

New TIP (Time Prediction) STR Report

Did you notice that the old TIP report for Y DNA STR markers was replaced with an updated version several months ago?

To view the new report, sign on and select your Y DNA matches. At the far right of each match you’ll see these three icons representing a pedigree chart, notes, and the TIP (Time Predictor) report.

The updated TIP report includes wonderful new graphs and age estimates for each match category, which you can read about, here. Each category, such as 67-marker matches, has time estimates in which a common ancestor might have lived at each possible genetic distance.

Math is our friend, and thankfully, someone else has done it for us!

Please note that the Big Y SNP dates are MUCH more accurate for a variety of reasons, not limited to the instability and rapid mutation rate of STR mutations.

MyOrigins3

MyOrigins3, FamilyTreeDNA’s ethnicity offering, added over 60 new reference populations for a total of 90, plus chromosome painting. You can read about MyOrigins features here, and the white paper, here.

This is one of my favorite improvements because it allows me to identify the segment location of my population ancestries, which in turn allows me to identify people who share my minority segments such as Native American and African.

Due to a lack of records, these relationships are often exceedingly difficult to identify, and MyOrigins3 helps immensely.

Additional Releases

Additional products and features released since the last conference include:

Discover

Released in July 2022, Discover is the amazing new free product that details your ancestor’s Y DNA “story” and his walk through time and across the globe.

In the past 18 months, all of the Discover features are new, so I’m only making a brief list here. The great thing is that everyone can use Discover if you know or can discover (pardon the pun) the haplogroup of your ancestral lines. Surname projects are often beneficial for finding your lineages.

  • Haplogroup Story includes haplogroup location, ages derived from the earliest known ancestor (EKA) of your matches, and ancient DNA samples. Please be sure you’ve entered or updated your EKA, and that the information is current. You can find instructions for how to update or add your EKA here.
  • A recent addition to the haplogroup story includes Haplogroup Badges.
  • Country Frequency showing where this haplogroup is found with either a table view or an interactive map
  • Famous and infamous Notable Connections, including Mayflower passengers, Patriots from the American Revolution, US presidents, royal houses, artists, musicians, authors, pirates, sports figures, scientists, and more.

If you know of a proven connection to a notable figure, contact customer support and let them know! Notable connections are added every week.

One famous Discover connection is Ludwig von Beethoven which resulted from a joint academic study between FamilyTreeDNA and academic researchers. It’s quite a story and includes both a mystery and misattributed parentage. You can see if you match on Discover and read about the study, here.

  • Updated Migration Map, including locations of select ancient DNA sites
  • The Time Tree, probably the most popular Discover report, shows the most current version of the Y DNA phylotree, updated weekly, plus scientifically calculated ages for each branch. Tree node locations are determined by your matches and their EKA countries of origin. I wrote about the Time Tree, here.
  • Anticipated in early 2024, the EKA and block tree matches will also be shown on the Time Tree in Discover for individual Big Y testers, meaning they will need to sign in through their kits.
  • The Group Time Tree, visible through group projects, takes the Time Tree a step further by including the names of the EKA of each person on the Time Tree within a specific project. Information is only displayed for project members who have given permission to include their data. You can select specific project groupings to view, or the entire project. I wrote about the Group Time Tree here and here.
  • Globetrekker is an exclusive Big Y mapping feature discussed here, here, here, and here.
  • Ancient Connections includes more than 6,100 ancient Y DNA results from across the globe, which have been individually analyzed and added for matching in Discover. Ancient Connections serve to anchor haplogroups and provide important clues about matches, migration paths and culture. New connections are added weekly or as academic papers with adequate Y DNA coverage are released.
  • Your Ancestral Path, which lists the haplogroups through every step from the tester back to Y Adam and beyond. Additional information for each haplogroup in your path includes “Time Passed” between haplogroups, and “Immediate Descendants,” meaning haplogroups that descend from each subclade. New columns recently added include “Tested Modern Descendants” and “Ancient Connections.”
  • Suggested Projects include surname, haplogroup, and geographic projects. Katy said that people joining projects are more likely to collaborate and upgrade their tests. You can also see which projects other men with this haplogroup have joined, which may well be projects you want to join too.
  • Scientific Details provides additional information, such as each branch’s confidence intervals and equivalent variables (SNPs). You can read more here.
  • Compare Haplogroups is the most recent new feature, added just last month, which allows you to enter any two haplogroups and compare them to determine their most recent common ancestral haplogroup. You can read about Compare Haplogroups, here.

Please note that the Studies feature is coming soon, providing information about studies whose data has been included in Discover.

You can read about Discover here, here, here, and here.

If you’re interested, FamilyTreeDNA has released a one-minute introduction to Y DNA and Discover that would interest new testers, here.

Earliest Known Ancestor (EKA) Improvement

Another improvement is that the earliest known ancestor is MUCH easier to enter now, and the process has been simplified. The EKAs are critical for Discover, so PLEASE be sure you’ve entered and updated your EKA.

Under the dropdown beside your name in the upper right-hand corner of your personal page, select Account Settings, then Genealogy and Earliest Known Ancestors. Complete the information, then click on “Update Location” to find or enter the location on a map to record the coordinates.

It’s easy. Just type or drop a pin and “Save.”

Saving will take you back to the original EKA page. Save that page, too.

Recommended Projects on Haplogroups & SNPs Page

You’re probably aware that Discover suggests projects for Y DNA testers to join, but recommended haplogroup projects are available on each tester’s pages, under the Y DNA Haplotree & SNPs page, in the Y DNA STR results section.

If there isn’t a project for your immediate haplogroup, just scroll up to find the closest upstream project. You can also view this page by Variants, Surnames and Countries.

This is a super easy tool to use to view which surnames are clustered with and upstream of your haplogroup. With Family Finder haplogroups being assigned now, I check my upstream haplogroups almost daily to see what has been added.

For example, my Big Y Estes results are ten branches below R-DF49, but several men, including Estes testers, have been assigned at this level, thanks to Y DNA haplogroups from Family Finder testing. I can now look for these haplogroups in the STR and Family Finder matches lists and see if those men are receptive to Big Y testing.

Abandoned Projects

Sometimes group project administrators can no longer function in that capacity, resulting in the project becoming abandoned. FamilyTreeDNA has implemented a feature to help remedy that situation.

If you discover an abandoned project, you can adopt the project, spruce things up, and select the new project settings. Furthermore, administrators can choose to display this message to recruit co-administrators. I need to do this for several projects where I have no co-admin.

If you are looking for help with your project, you can choose to display the button
through the Project Profile page in GAP. For non-project administrators, if you’d like to help, please email the current project administrators.

New Kit Manager Feature

FamilyTreeDNA has added a “Kit Manager” feature so that an individual can designate another person as the manager of their kit.

This new setting provides an avenue for you to designate someone else as the manager of your DNA test. This alerts FamilyTreeDNA that they can share information with both of you – essentially treating your designated kit manager the same as you.

If you’re the kit manager for someone else, you NEED to be sure this is completed. If that person is unavailable for some reason, and support needs to verify that you have legitimate access to this kit, this form and the Beneficiary form are the ONLY ways they can do that.

If your family member has simply given you their kit number and password, and for some reason, a password reset is required, and their email address is the primary contact – you may be shut out of this kit if you don’t complete this form.

Beneficiary Page

Additionally, everyone needs to be sure to complete the Beneficiary page so that in the event of your demise, FamilyTreeDNA knows who you’ve designated to access and manage your DNA account in perpetuity. If you’ve inherited a kit, you need to add a beneficiary to take over in the event of your death as well.

What is FamilyTreeDNA working on now?

Currently in the Works

Katy moved on to what’s currently underway.

Privacy and Security

Clearly, the unauthorized customer data exposure breach at 23andMe has reverberated through the entire online community, not just genetic genealogy. You can read about the incident here, here, here, and here.

FamilyTreeDNA has already taken several steps, and others are in development and will be released shortly.

Clearly, in this fast-moving situation, everything is subject to change.

Here’s what has happened and is currently planned as of today:

  • Group Project Administrators will be required to reset their password soon.

Why is this necessary?

Unauthorized access was gained to 23andMe accounts by people using the same password for multiple accounts, combined with their email as their user ID. Many people use the same password for every account so that they can remember it. That means that all a hacker needs to do is breach one account, and they can use that same information to “legitimately” sign in to other accounts. There is no way for the vendor to recognize this as unauthorized since they have both your user ID and password.

That’s exactly what happened at 23andMe. In other breaches, this information was exposed, and hackers simply tried the same username and password combination at 23andMe, exposing the entire account of the person whose account they signed in “as.” This includes all of their matches, genetic tree, shared matches, matches of matches, ethnicity, and segments. They could also have downloaded both the match list and the raw DNA file of the compromised account.

At FamilyTreeDNA, project administrators can select their own username, which could be their email, so they will be required to reset their password.

Additional precautions have been put in place on an interim basis:

  • A pause in the ability to download match and segment information.
  • A pause in accepting 23andMe uploads.

Administrators will also be required to use two-factor authentication (2FA.) To date, two of the four major vendors are requiring 2FA. I would not be surprised to see it more broadly. Facebook recently required me to implement 2FA there, too, due to the “reach” of my postings, but 2FA is not required of everyone on Facebook.

Please note that if you received an email or message that is supposedly from any vendor requiring 2FA, GO DIRECTLY TO THAT VENDOR SITE AND SIGN IN.  Never click on a link in an email you weren’t expecting. Bad actors exploit everything.

Customers who are not signing in as administrators are not required to implement 2FA, nor will they be required to reset their password.

Personally, I will implement 2FA as soon as it’s available.

While 2FA is an extra step, it’s easy to get used to, and it has already literally saved one of my friends from an authorized hack on their primary and backup email accounts this week. Another friend just lost their entire account on Facebook because someone signed in as them. Their account was gone within 15 minutes.

2FA is one of those things you don’t appreciate (at all) until it saves you, and then, suddenly, you’re incredibly grateful.

At this point in time, FamilyTreeDNA users will NOT be required to do a password reset or implement 2FA. This is because customers use a kit number for sign-in and not a username or email address. I would strongly recommend changing your password to something “not easy.” Never reuse passwords between accounts.

I really, really want you to visit this link at TechRepublic and scroll down to Figure A, which shows how long it takes a hacker to crack your password. I guarantee you, it’s MUCH quicker than you’d ever expect.

Kim Komando wrote about this topic two years ago, so compare the two charts to see how much easier this has become in just two years.

Again, if you receive an email about resetting your password, don’t click on a link. Sign in independently to the vendor’s system, but DO reset your password.

FamilyTreeDNA also engages in additional security efforts, such as ongoing penetration testing.

New Permissions

Additionally, at FamilyTreeDNA, changes were already in the works to separate out at least two permissions that testers can opt-in to without granting project administrators Advanced rights.

  • Download data
  • Purchase tests

The ability to purchase tests can be very important because it allows administrators to order and pay for tests or upgrades on behalf of this tester anytime in the future.

Family Finder Haplogroups

FamilyTreeDNA has already begun releasing mid-level Y DNA haplogroups for autosomal testers in a staggered rollout of several thousand a day.

I wrote about this in the article, FamilyTreeDNA Provides Y DNA Haplogroups from Family Finder Autosomal Tests, so I’m not repeating all of that information here – just highlights.

  • The Family Finder haplogroup rollout is being staggered and began with customers on the most recent version of the testing chip, which was implemented in March of 2019.
  • Last will be transfers/uploads from third parties.
  • Haplogroups resulting from tests performed in the FTDNA labs will be visible to matches and within projects. They will also be used in both Discover and the haplotree statistics. This includes Family Finder plus MyHeritage and Vitagene uploads.
  • Both MyHeritage and Vitagene are uploaded or “transferred” via an intracompany secure link, meaning FamilyTreeDNA knows that their information is credible and has not been manipulated.
  • Haplogroups derived from tests performed elsewhere will only be visible to the user or a group administrator viewing a kit within a project. They will not be visible to matches or used in trees or for statistics.
  • Any man who has taken a Y DNA STR test will receive a SNP-confirmed, updated haplogroup from their Family Finder test that replaces their predicted haplogroup from the STR test.

Please read this article for more information.

New Discover Tools and Updates

Discover content continues to be updated, and new features are added regularly, creating an increasingly robust user experience.

Soon, group administrators will be able to view all Discover features (like Globetrekker) when viewing kits of project members who have granted an appropriate level of access.

Ancient and Notable connects are added weekly, and a new feature, Study Connections, will be added shortly.

Study Connections is a feature requested by customers that will show you which study your academic matches came from. Today, those results are used in the Y DNA tree, but the source is not detailed.

Anticipated in early 2024, the EKA and block tree matches will also be shown on the Time Tree in Discover for individual Big Y testers (not publicly).

Big Y FaceBook Group

FamilyTreeDNA has ramped up its social media presence. They launched the Big Y Facebook group in July 2023, here, which currently has just under 9000 members. Several project administrators have volunteered their time to help manage the group.

FamilyTreeDNA Blog

In addition, FamilyTreeDNA is publishing at least one blog article each week, and sometimes more. You can view or subscribe here. Some articles are written by FamilyTreeDNA staff, but project administrators and customers author other content.

Multi-Language Support

Translation of the main FamilyTreeDNA website and results pages to Spanish has begun, with more languages planned soon.

Paypal, Payments, and Gift Cards

Paypal has been added as a payment selection, along with a PayPal option that provides the ability to make payments.

Additionally, a gift card can be purchased from the main page.

Million Mito Project & Mitotree

Work on the Million Mito Project is ongoing.

The Million Mito Project was launched in 2020 as a collaborative effort between FamilyTreeDNA’s Research & Development Team and the scientific portion of the Genographic Project. I’m a team member and wrote about the Million Mito Project, here.

We’re picking up from where the Phylotree left off in 2016, analyzing 20 times more mtDNA full sequences and reimagining the mtDNA Haplotree. By examining more mtDNA data and applying the processes that allowed FamilyTreeDNA to build the world’s largest Y DNA Haplotree, we can also create the world’s largest Mitotree.

In 2022, the first update was released, authored by the Million Mito team, with the discovery of haplogroup L7. You can read about this amazing discovery rooted deep in the tree here, here, and here. (Full disclosure: I’m a co-author.)

Not only that, but “Nature Scientific Reports” selected this article as one of five named Editor’s Choice in the Mitogenomics category, here. In the science world, that’s a HUGE deal – like the genetic Emmy.

Here’s one example of the type of improvements that can be expected. Currently, the formation of haplogroup U5a2b2a reaches back to about 5000 years ago, but after reanalysis, current branches originated between 500 and 2,500 years ago, and testers are clustered more closely together.

This is SOOO exciting!!!

Just as Discover for Y DNA results was built one feature at a time, the same will be true for MitoDiscover. That’s my name, not theirs.

As the new Mitotree is rolled out, the user interface will also be updated, and matching will function somewhat differently. Specifically, it’s expected that many more haplogroups will be named, so today’s matching that requires an exact haplogroup match to be a full sequence match will no longer work. That and other matching adjustments will need to be made.

I can hardly wait. I have so many results I need to be able to view in a tree format and to place in a timeframe.

You can be included in this exciting project, learn more about your matrilineal (mother’s) line, and hopefully break down some of those brick walls by taking the full sequence mitochondrial DNA test, here.

After the new Mitotree is rolled out and the Y DNA Family Finder haplogroups are completed, Family Finder customers, where possible, will also receive at least a basic-level mitochondrial haplogroup. Not all upload files from other vendors include mtDNA SNPs in their autosomal files. The mitochondrial Family Finder haplogroup feature isn’t expected until sometime in 2025, after the new tree and MitoDiscover are complete.

The Future

What’s coming later in 2024, or is ongoing?

Privacy Laws

Most people aren’t aware of the new privacy laws in various states, each of which has to be evaluated and complied with.

The effects of these changes will be felt in various areas as they are implemented.

New Kits Opted Out of IGG

Since late August, all new FTDNA kits are automatically opted OUT of Investigative Genetic Genealogy (IGG) by default.

Regular matching consent and IGG matching consent have been separated during onboarding.

Biobanking Separate Consent

Another consent change is to have your sample biobanked. FamilyTreeDNA has always maintained your sample for “roughly 25 years.” You could always ask to have your sample destroyed, but going forward, you will be asked initially if you want your sample to be retained (biobanked.) It’s still free.

Remember, if someone declines the biobanking option, their DNA will be disposed of after testing. They can’t order upgrades without submitting a new sample. Neither can their family after they’re gone. I ordered my mother’s Family Finder test many years after she had gone on to meet our ancestors – and I’m incredibly grateful every single day.

MyHeritage Tree Integration

An exciting change coming next year is tree integration with MyHeritage.

And no, before any rumors get started, FAMILYTREEDNA IS NOT MERGING WITH MYHERITAGE. It’s a beneficial marriage of convenience for both parties.

In essence, one of the primary focuses of MyHeritage is trees, and they do that very well. FamilyTreeDNA is focused on DNA testing and their existing trees have had issues for years. MyHeritage trees are excellent, support pedigree collapse, provide search capabilities that are NOT case sensitive, SmartMatching, and much more.

If you don’t have a MyHeritage account, creating one is free, and you will be able to either port your existing FamilyTreeDNA tree, or begin one there. If you’re already a MyHeritage member, FamilyTreeDNA and MyHeritage are planning together for a smooth integration for you. More detailed information will be forthcoming as the integration progressed and is released to customers.

You’ll be able to connect multiple kits to your tree at MyHeritage, just like you can at FamilyTreeDNA today, which enables family matching, aka bucketing.

You can also have an unlimited number of different trees at MyHeritage on the same account. You’re not limited to one.

After you link your initial FamilyTreeDNA kit to the proper person in your MyHeritage tree, you’ll be able to relink any currently linked kits.

MyHeritage will NOT receive any DNA information or match information from FamilyTreeDNA, and yes, you’ll be able to use the same tree independently at MyHeritage for their DNA matching.

You’ll still be able to view your matches’ trees, except it will actually be the MyHeritage tree that will be opened at FamilyTreeDNA in a new tab.

To the best of my knowledge, this is a win-win-win, and customers of both companies aren’t losing anything.

One concern is that some FamilyTreeDNA testers have passed away and cannot transition their tree, so a view-only copy of their tree will remain at FamilyTreeDNA so that their matches can still see their tree.

Big Y Infrastructure

Katy mentioned that internal discussions are taking place to see what changes could be made to improve things like matching and test processing times.

No changes are planned for SNP or STR coverage, but discussions are taking place about a potential update to the Telomere to Telomere (T2T) reference. No promises about if or when this might occur. The last part of the human genome to be fully sequenced, the T2T reference model includes the notoriously messy and unreliable region of the Y chromosome with many repeats, duplications, gaps, and deletions. Some data from this region is probably salvageable but has previously been omitted due to the inherent problems.

I’m not sure this shouldn’t be in the next section, the Wishlist.

Wishlist

There are lots of good things on the Wishlist – all of which I’d love.

I’d have difficulty prioritizing, but I’d really appreciate some Family Finder features in addition to the items already discussed. I’d also like to see some GAP (administrator) tool updates.

Which items do you want to see most?

Katy said that FamilyTreeDNA is NOT planning to offer a Whole Genome Sequencing (WGS) test anytime soon. So, if you’re holding your breath, please don’t. Based on what Katy did say, WGS is very clearly not a consideration in 2024 and I don’t expect to see it in 2025 either unless something changes drastically in terms of technology AND pricing.

While WGS prices have come down, those consumer tests are NOT scanned at the depth and quality required for advanced tests like the Big Y or even Family Finder. Normally consumer-grade WGS tests are scanned between 2 and 10 times, where the FamilyTreeDNA lab scans up to 30 times in order to obtain a quality read. 30X scans are in the same category as medical or clinical grade whole genome scans. Significantly higher quality scans mean significantly higher prices, too, so WGS isn’t ready for genealogy prime time yet.

Additionally, commercially available WGS tests are returned to the customer “as is,” and you’re left to extract the relevant SNPs and arrange them into files, or find someone else to do that. Not to mention, in order to preserve the integrity of their database, FamilyTreeDNA does not accept Y or mitochondrial DNA uploads.

Recently, I saw two WGS files with a 20-25% no-call rate for the autosomal SNPs required for the Family Finder test. Needless to say, that’s completely unacceptable. Some tools attempt to “fix” that mess by filling in the blanks in the format of either a 23andMe or Ancestry file so you can upload to vendors, but that means you’re receiving VERY unreliable matches.

The reason none of the major four vendors offer WGS testing for genealogists is because it’s not financially feasible nor technologically beneficial. The raw data file alone won’t fit on most home computers. WGS is just not soup yet, and it won’t be for the general consuming public, including relevant tools, for at least a few years.

I’ve had my whole genome sequenced, and trust me, I wish it were feasible now, but it just isn’t.

Suggestions Welcomed

Katy said that if you have suggestions for items NOT on the wishlist today to contact her through support.

I would add that if you wish to emphasize any specific feature or need above others, please send that feedback, politely, to support as well.

Katy ended by thanking the various teams and individuals whose joint efforts together produce the products we use and enjoy today.

Lab Update

Normally, DNA testing companies don’t provide lab updates, but this conference is focused on group project administrators, who are often the most dedicated to DNA testing.

A lab update has become a tradition over the years.

Linda Jones, Lab Manager, provided a lab update.

You may or may not know that the FamilyTreeDNA lab shifted gears and stepped up to handle Covid testing.

Supply-chain shortages interfered, but the lab ran 24×7 between 2020 and 2022.

Today, the lab continues to make improvements to processes with the goal of delivering the highest quality results in a timely manner.

On Monday, after the conference, attendees could sign up for a lab tour. You might say we are a rather geeky bunch and really enjoy the science behind the scenes.

Q&A and Thank You

At the end of the conference, the FamilyTreeDNA management team answered questions from attendees.

Left to right, Daniel Au, CTO; Linda Jones, Lab Manager; Katy Rowe-Schurwanz, Product Manager; Clayton Conder, VP Marketing; Goran Runfeldt, Head of R&D; and Andrew Gefre, Development Manager. Not pictured, Jeremy Balkin, Support Manager; Kelly Jenkins, VP of Operations; and Janine Cloud, Group Projects Manager. Janine is also responsible for conferences and events, without whom there would have been no 2023 FamilyTreeDNA conference. Janine, I can’t thank you enough!

A huge thanks to all of these people and many others, including the presenters, CSRs,  IT, and other FamilyTreeDNA team members for their support during the conference, enabling us to enjoy the conference and replenish the well of knowledge.

_____________________________________________________________

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 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 Book

Genealogy Books

Genealogy Research