FOCUS: Step 3 – Breaking Through Brick Walls Using Y-DNA and Mitochondrial DNA

In the first three articles of this series, we:

  1. Selected a brick-walled ancestor we’d like to find
  2. Learned how to overcome the hurdle of DNA matches without trees
  3. Discussed methods to locate our ancestors’ mitochondrial DNA (mtDNA) and Y-DNA

I suggest reading these articles in order.

In this article, we’re going to learn how to use mitochondrial DNA or Y-DNA to help identify the ancestor you’re seeking.

Multiple Levels of Information

Mitochondrial DNA and Y-DNA testers receive important information that includes matching with other testers, several interpretive tools and reports, and a haplogroup which is the key to unlocking the past.

Since people have tested at varying levels, or maybe they’ve simply obtained a partial haplogroup from autosomal testing, you may encounter varying levels of information about the same ancestor.

As we noted in Finding the Y-DNA and Mitochondrial DNA of Your Ancestors, you could be working with:

  • The most refined haplogroup possible if you or the tester has tested at either the mtFull or the Big Y-700 test level at FamilyTreeDNA.
  • A full haplogroup, whether you have access through the tester’s account, which provides additional tools, such as matches, or access to the haplogroup only, meaning not directly through the tester’s account.
  • A partial haplogroup if the tester has tested at a lower level, or the haplogroup was determined through an autosomal DNA test. Autosomal tests only provide partial haplogroups.
  • Minimum information, meaning an unknown haplogroup level without access to the tester’s account information.

All of these can be useful, but for our example, we’re assuming account-level access along with the highest testing level, which provides the most refined haplogroup possible.

Also note that both Y-DNA at the Big Y-700 level and mitochondrial DNA haplogroups at the mtFull level are evergreen. This means that when more people’s test results produce additional mutations that you share, and that qualify for a new haplogroup, you’ll automatically receive that new haplogroup.

New Y-DNA haplogroups are typically added within a few days or a couple of weeks after the new tester’s results are complete. For mitochondrial DNA, an updated Mitotree is calculated every few weeks, and your haplogroup may be refined from time to time.

Matches are the Backbone of DNA Testing

As with all types of DNA testing, matches are critically important.

With Y-DNA matching, the tester typically has the benefit of a recognizable, or at least similar, surname on their match list. However, that’s not always the case.

I’m starting with the results of one of my Estes cousins who has taken the Big Y-700 test as an example because it affords me the opportunity to review all of the genealogical benefits of the highest testing level.

My cousin’s Big Y-700 haplogroup is R-ZS3700, which was formed about 1750 CE. Note that all haplogroup origin dates are actually a range.

Using the results of Big Y-700 testers combined with genealogy, we know exactly which of the Estes males developed that mutation.

Prior to taking the Big Y-700 test, my cousin’s predicted haplogroup based on STR testing was R-M269, a difference of about 6,200 years.

If you’re a new tester, a haplogroup from 6,450 years ago versus one that places you directly as a descendant of Moses Estes, born in 1711 in King and Queen County, Virginia, is night and day.

Y-DNA Testing and Matching Levels

All Y-DNA testers receive the regular STR (Short Tandem Repeat) panel matches at the level they’ve purchased – ranging from 12-111 markers, including all markers beneath that level.

Testers at the now obsolete Big Y-500 and current Big Y-700 level also receive 500 and 700 STR markers, but the SNPs (Single Nucleotide Polymorphisms) revealed at this level of testing greatly overshadow the usefulness of those additional STR markers.

Men who take the Big Y-700 test receive Big Y-700 SNP matching separately from STR panel matching on their dashboard.

12-111 STR Panel Matches

Clicking on “Y-DNA Matches” under “Y-DNA Results and Tools” shows the tester’s STR panel matches at various levels. Big Y testers should not ignore these because not all people have tested at the Big Y-700 level.

Click any image to enlarge

At the top of the matching display, note that the STR match levels are shown. Matching defaults to the testing level of the tester. In this case, my cousin took the Big Y-700 test, so the matches he’ll see first are his 40 111-marker matches.

Not everyone has tested at that level.

The very first Y-DNA test offered in this industry 26 years ago was at FamilyTreeDNA and was only 12 markers. It was revolutionary at the time, affording genealogists the ability to determine if two men with the same surname were descended from the same paternal line. This also means that FamilyTreeDNA has men in their database that testers can match today who tested a generation ago, many of whom have since passed away.

Over the years, the tests have expanded and improved. Today, men can purchase the introductory 37-marker test, which includes the 12- and 25-marker levels, or the 111-marker test, which includes all the lower levels. Big Y-700 testers receive everything, plus a substantial amount of additional information not available with the STR tests.

Notice that our Estes tester has 40 111-marker matches, but 238 12-marker matches. This is due, in part, to the fact that many men have not upgraded to the higher-level tests. Some men will match on the 12-marker test but will have too many mismatches at higher-level testing. Generally, when both men are being compared at the same level, the higher-level tests ferret out matches that occur simply because they share a very old and distant haplogroup.

The “Genetic Distance” step number is NOT the number of generations difference, but the number of mutational steps separating the results at the level being viewed.

H Estes, the first match, tested at the 111-marker level, so 1-111 markers are being compared. My cousin and H Estes have a “1-step” difference at 111 markers. That means H Estes matches my cousin on 110 of the 111 markers in that panel.

The values of those markers can be viewed under the “Y-STR Results” under the “See More” tab, but the values themselves are not generally informative. You cannot see your matches’ values unless they have joined a group project. Some group projects are displayed publicly, and some are not.

If a tester has joined a DNA Group Project, such as the Estes Project, the values for consenting participants can be seen there, along with additional information such as the Earliest Known Ancestor (EKA).

In general, the fewer the mismatches, the closer the relationship. That said, STR (Short Tandem Repeat) markers are inherently unstable. Mutations and back-mutations can happen at any time, which sometimes makes the results misleading. Haplogroup-defining SNP mutations don’t suffer from that issue.

You can also see project members listed in Group Time Tree format as we discussed in the third FOCUS article, here.

More Hints on the Matches Page

Additional important genealogy hints on the Matches page include the “Paternal Country of Origin” and, of course, the “Earliest Known Ancestor.”

Always check the trees of your matches, even if the match has a different surname. Adoptions, both formal and informal, have been going on as long as there have been humans, and family trees can also hold location proximity information. Think, “right time, right place.”

In the second article, FOCUS: Step 1 – Seven Solutions for DNA Matches with Absent or Shrunken Trees, we discussed how to work around small or absent trees.

Be sure to inspect every match level. Some people view their 111-marker matches but ignore their 12-marker or other match levels.

In this case, there are 198 more 12-marker matches than 111-marker matches, so don’t neglect to review each one. Think of it this way – there are 198 hints you’re missing if you don’t.

Depending on where mutations randomly happened to occur, you may NOT match someone at the 12-marker level that you DO match at higher levels, so you can’t always assume that all of your 25-marker matches are shown at the 12-marker level or vice versa.

In the Estes lineage, we’ve been recruiting males and solving mysteries for 25 years now, but not every lineage has this many testers with surname matches. Then, of course, there’s mitochondrial DNA, where surnames won’t meaningfully match testers.

Mitochondrial DNA Matching

People working with mitochondrial DNA consider Y-DNA testers fortunate because their surname tends to remain the same across generations, at least in some parts of the world.

For the most part, mitochondrial DNA matching is the same as Y-DNA matches, except:

  • You seldom recognize a surname
  • If you do recognize a surname, it won’t be the tester’s surname that matches yours, but perhaps you’ll recognize the surname of their Earliest Known Ancestor
  • You have a Mitotree Haplogroup in addition to the mtDNA Haplogroup
  • You have an F number, which is your haplotype cluster number, in addition to your Mitotree Haplogroup

All people who take or upgrade to the mtFull level test will receive a new Mitotree haplogroup in addition to the older legacy haplogroup. Mitotree was released in 2025 and restructured the entire mitochondrial DNA tree of humankind.

People who only took the HVR1 (Hypervariable Region 1) or HVR1+HVR2 Plus level tests can’t receive the new haplogroup because not enough locations have been tested, so you’ll only see their legacy haplogroup when you’re viewing your lower-level matches. Don’t neglect your HVR1 and HVR2 matches, because the very hint you need may be waiting there.

Your Coding Region matches include the entire mitochondrial sequence – in other words – the mtFull test.

About Haplotype Clusters

As part of your Mitotree haplogroup, you also have a haplotype cluster number which begins with F. The number itself doesn’t matter. The message does.

The mitochondrial DNA matching system excludes several unstable markers because they may provide essentially false matches. However, they can sometimes be useful genealogically, so we have multiple matching criteria.

  • Rose’s example: The genetic distance matching excludes unstable markers such as 315.1, so it’s possible to have an “Exact Match” under Genetic Distance, but a different F number because not every location matches.
  • Anastasia’s example: It’s NOT possible to have a “1 step” Genetic Distance, but the same haplotype cluster F number. It is possible to have the same haplogroup.
  • Per’s example: An identical F number, or haplotype cluster, means you match exactly, INCLUDING any excluded or unstable markers, such as 315.1.

In other words, proceed with caution, and your mileage may vary.

Check marks in the blue boxes mean you have the same haplogroup and/or the same haplotype cluster as your match.

I wrote about haplotype clusters here and here.

Identifying Sophia

In this example, Ms. Traxler and Mr. Lyman are exact matches in the regular “Genetic Distance” matching, their haplogroup, and the new Mitotree haplotype clusters.

In the third example, Ms. Crosbie has a 1-step difference, which means, in this case, she is missing a haplogroup-defining mutation. We know this because her haplogroup is V216a instead of V216a2. And of course, she doesn’t match our tester exactly, so they don’t share an F number either.

The tester, a family member, was brick-walled at his great-grandmother, Sophia Smith, born in 1877, someplace, and died in 1950 in Richland County, Ohio. It seemed like she was dropped off by the stork in the middle of a field, because records about her didn’t seem to exist.

Even though the surnames are different, and Traxler doesn’t have a tree, the name Schmidt in the EKA field caught my eye. Smith is Schmidt in German, and I knew the tester had German heritage in other lines, but Sophia Smith was supposed to be English.

Sophia Smith was married to John Rittinger. That, plus their children’s names, was all I had, but it was eventually enough.

I clicked on the match’s EKA link, and it showed that Elizabeth Schmidt Hornung was born in 1888 and died in 1930.

At this point, I’m wondering whether Schmidt was a middle name or a birth surname.

Two days and a sleepless night later, I had discovered that Hornung was her married name, and Elizabeth Schmidt had married Karl Hornung. As these things tend to do, one thing led to another, and eventually, sorting through newspaper articles, death certificates, and a bunch of misinformation, misspelled names, dead ends, and wrong turns, I found information linking Elizabeth to her brother, Joseph, who connected to their sister, Sophia Schmidt. But was Sophia Schmidt the same person as Sophia Smith?

Finally, running on pure caffeine and determination, I found Elizabeth Hornung’s death announcement in the newspaper, where it gave the names of her siblings, including Mrs. John Rittinger. Now I needed to connect a few final dots to verify that her sister was, in fact, that same Mrs. John Rittinger (by several spellings).

I eventually connected even more dots and discovered the family was from Timisoara, Romania, even though the area where they lived changed borders more than once and fell within the multiple countries of the Austro-Hungarian Empire.

Then, I discovered their parents’ names, but the parents never immigrated, and we don’t know any more about them. Unfortunately, that area was terribly ravaged by WWII, which is what spurred immigration.

The point being that it’s incredibly important to follow every available clue, even if it seems rather pointless. You never know which tidbit is the right one, and if you skip them, you’ll never make that breakthrough.

Follow your exact haplotype cluster matches first, then your exact and one-step regular matches, then your haplogroup-only matches, and then your near-haplogroup matches.

What if the Y-DNA Match Surnames Aren’t the Same as Yours?

Let’s say you take a Y-DNA test and your surname is Estes. Furthermore, your father and grandfather carry the same surname.

So, you didn’t expect to see this on your match page.

First, breathe.

Second, you’re looking at 12-marker matches. It’s not at all uncommon for men within a core haplogroup, like R, to match at the 12-marker level even though they may not have shared a common paternal ancestor in thousands of years.

Panning for Gold

But wait, you’re saying, you just told me not to ignore 12-marker matches.

At 12 markers, you’ll need to focus on your own or similar surnames. It’s like panning for gold.

At 12 markers, my Estes cousin has a total of:

  • 35 Estes matches
  • 2 Easter matches
  • 1 Eastes match
  • 3 Eastridge matches

This means that he also has 197 non-similar surname matches.

The information you need may well be buried in the information provided by those 12-marker Estes or similar surname matches.

For example, if your surname is Eastridge or Easter, you might want to look at historical documents to compare your ancestors’ surnames. We now know that Easter happened sometime near the Civil War in North Carolina, probably because the final S in Estes was interpreted as an R. The circumstances surrounding Eastridge are less clear, but we know roughly when and where it occurred in North Carolina.

A group of researchers spent years trying to unravel the Eastridge mystery and have narrowed the event to a specific North Carolina county.

On the other hand, if an Easter or Eastridge male takes the Big Y-700 test, he will know immediately if he falls into this Estes grouping, and where, or if he belongs to a different genetic lineage.

A Genetic Detour

However, if your surname is Jones and you match a large number of Estes males at the highest testing levels, and you don’t match any or many other men by your surname, that might be a significant hint about your brick-walled ancestor.

The telltale sign may be that you can track your surname and DNA matching back a couple of generations, then nothing. I recommend working progressively upstream, testing male-line descendants of different sons in each generation, if possible.

In this example, John Jones is the progenitor of the Jones family. According to the genealogy, he had three sons, Elijah, Sidney and William.

In this hypothetical situation, Rodney Jones’ descendant tested and discovered that he matched a whole group of Estes men, many with his own haplogroup – R-ZS3700. A descendant of Nathaniel Jones, a second son of William Jones, tested and confirmed that he matches the descendant of Rodney.

So far, so good.

Next, a direct male-line descendant of Sidney Jones tested and sure enough, he’s a member of haplogroup J. Hmmm. We need another Jones male that descends from another son of John as a tiebreaker. Lucky for our tester, further investigation revealed that Sidney’s descendant matches a descendant of Elijah Jones, another son of John.

This tells us exactly where the genetic break in the Jones line occurred. Between John and William Jones. You may have heard this situation referred to as a “misattributed paternity,” or an NPE, “not parent expected,” but we really know what happened, or why, without additional research.

Caution – Don’t Jump!

A word of caution here. Never, ever jump to conclusions about “cheating wives.” While that’s one possibility, there are several other circumstances we need to consider and rule out first.

In many cases, a young widow remarried, and her baby took the stepfather’s surname. The “adoption” wasn’t remarkable. Adoptions in 1600s, 1700s, 1800s and into the 1900s were informal, not legal affairs. Everyone at the time knew about it, but over the generations it was forgotten until DNA testing shocked everyone.

In another case, a widow had two children more than 9 months after her husband died and both children took the deceased husband’s surname, which was then their mother’s surname.

When making these discoveries, we also need to keep in mind that not all sexual encounters were consensual.

Sometimes, the situation is complicated. I know of a case during the Civil War where a woman traded favors with a soldier of the opposing army for food for her children. Her husband returned home to a pregnant wife, but his wife and children had all lived, and he simply raised that child as his own. That family’s oral history was confirmed by DNA testing.

Now, in our example, given that our Jones tester carries haplogroup R-ZS3700, we know that he descends from Moses Estes, born in 1711, the progenitor of that haplogroup. We need to begin by working down the genealogical tree with Moses and look for an Estes male in the same location as William Jones’ mother about 10 months before his birth. Also consider factors like warfare and trader movement. Check the census for missing children, or a child that suddenly appears in a later census that should have been recorded with the family in an earlier census. Notice anomalies.

Look for the surname you match the most closely in that location and at that time. Right time, right place, and opportunity.

And of course, to complicate things further, don’t assume that the mother was the mother either. Sometimes both parents died and someone took the child to raise as their own. Review all of the evidence at hand with fresh eyes.

Matches Map

Another matching feature for both Y-DNA and mtDNA includes the Matches Map.

For Y-DNA, the Matches Map can be found under the “See More” tab.

For mitochondrial DNA, it’s found under “mtDNA Results and Tools.”

While the Matches page and Discover reports both provide the Country of Origin, the Matches Map provides a specific location where your match’s earliest known ancestor is found. Be sure to select the match level using the drop-down in the upper left-hand corner, or no results will display, and you’ll receive the message that there are no results available.

The Matches Map is extremely useful for quickly identifying common locations, especially when surnames don’t match.

The Matches Map utilizes the location entered for your EKA.

Add Your Earliest Known Ancestor and Locations

Please be sure to add your Earliest Known Ancestor and their location under the drop-down beside your name at the upper right-hand corner of your dashboard page. Click on the gear for “Account Settings,” then “Genealogy.”

You don’t need to know the longitude and latitude. Just click on “Update Location,” which takes you to the map where you can simply search for and select the location, which updates these fields.

An identical field for your matrilineal line is found below the paternal section. For purposes of clarification, this is NOT any woman on your “maternal” line, and NOT the “earliest known person” on your maternal side. The ancestor must be a female, and it is ONLY ever your mother’s mother’s mother’s direct matrilineal line – through all women – to the end of that line.

If you see a male EKA in your mitochondrial DNA match list, you know the tester was confused about what to enter here. Hopefully they have a tree that you can view to find the correct EKA.

In addition to your EKA, please add the list of your family surnames, your Family Tree, and a link to your profile at WikiTree while you’re there. You’ll see in just a minute why that information is so important and how it benefits your genealogy.

The Difficult Moore Line

Let’s look at a much more difficult scenario.

My James Moore line (c1720-c1798) is my decades-long brick wall. He first appears in Amelia County, VA, and then moved to Halifax County. His wife was Mary Rice. His life before that is a blank slate, despite my earlier efforts and those of several cousins. I wrote about him here and here.

My Moore cousin, who is deceased, so cannot upgrade his Y-DNA test from its original 12 markers, has only three matches at the 12-marker level. This is all I have to work with except for his autosomal Family Finder results.

Note that one of his matches tested at the 12-marker level, one at 37 markers, and one at 111 markers. Each man would have received a predicted haplogroup based on his STR marker test. Recently, if they had taken a Family Finder test, their predicted haplogroup would have been updated and overwritten by a confirmed haplogroup derived from Family Finder.

Not only are Family Finder haplogroups more specific and closer in time than predicted haplogroups from STR tests, but they are also SNP-confirmed, not predicted.

Keep in mind that not all autosomal DNA chips were programmed to read the same Y-DNA and mtDNA locations. At that time, they were never intended to be used for this purpose, which probably explains the two different haplogroups for the Moore men.

My Moore cousin’s original predicted haplogroup based on his STR test was J-M102. His Family Finder results updated his haplogroup to J-M241, while his matches are J-Z631.

Using Discover’s Compare feature, we find that:

  • J-M102 developed about 16,000 years ago
  • J-M241 developed about 9,500 years ago
  • J-Z631 developed about 2,950 years ago

While their haplogroups don’t match because they come from different sources, they are still in the same genetic lineage on the Y-DNA phylogenetic tree. In other words, they don’t preclude a common ancestor. Since they also match on their STR markers and share the same surname, we don’t need to be terribly concerned about false Y-DNA matches.

I’ve tried to break through this brick wall many times, but let’s try again using new information.

To begin with, there are many more genealogy resources available now than when my cousin and these other men tested. I had originally communicated with all three of his matches when they initially matched, and they provided me with what little they knew.

I still have that information entered into a tiny tree on my computer. I have not been able to get ahold of these men now in several years, so I’m VERY glad that I reached out when I did. Reach out and collaborate now. You never know when it’s too late.

Y-DNA Plus Family Finder Yields More Hints

Let’s move to my Moore cousin’s autosomal Family Finder matches and see if there’s any additional help buried there.

Searching his Family Finder match list for “Moore” produces 39 people with the Moore surname, and 256 people with the Moore surname either in their own name or their surname list. This is why entering your list of ancestral surnames is important.

I selected the 39 Moore surname matches, then focused on the males’ Y-DNA haplogroups. Our Moore cousin’s haplogroup is J-M241, and his Y-DNA matches’ haplogroups are all J-Z631.

Haplogroups derived from autosomal testing are very useful when viewing autosomal matches with Moore men. As you can see, these Moore men aren’t in the same major haplogroup as our line, so even though they share the same surname, it’s happenstance. Their haplogroup results preclude matches due to their Moore direct paternal line.

Autosomal transfer haplogroups do not update Y-DNA haplogroups and are not displayed to autosomal matches due to quality and consistency challenges.

Working with the rest of my Moore cousin’s autosomal matches, I did not find others who match with haplogroup J and the Moore surname.

If I had found another Moore male that fell someplace in the same branch of haplogroup J, I could use autosomal tools to view shared “in common” matches and triangulate segments to identify others who share that specific lineage. Autosomal matches’ trees plus the genealogy work I’m doing on the trees of the Y-DNA testers might lead to a breakthrough on the Moore line that is severely brick-walled in colonial Virginia.

This approach didn’t work this time, but new matches appear all the time, and autosomal matches may help.

However, we’re not done.

Advanced Matching

FamilyTreeDNA provides an Advanced Matches feature that allows you to select matching criteria across different tests to see whether anyone matches you on those combined criteria.

You’ll find “Advanced Matches” in the “Additional Tests and Tools” section.

You can select the tests to compare to see if people match you on ALL of the criteria you choose.

Yes, ALL is bold red because if you select any of the “Select All” features – that means everything. So, if you select “All Y-DNA” you must match at the 12, 25, 37, 67 and 111 marker levels – not just one of them. If someone doesn’t meet the matching criteria at any individual selected level, that person won’t show on the combined match list.

So, select one Y-DNA choice that both people have, plus Family Finder.

Then, CHECK “YES” under “Show only people I match in all selected tests.” Otherwise, you’ll see everyone you match on both tests, combined.

In this example, one of my cousins matches a Morrow male on both the 12-marker test and the Family Finder test. If I had NOT checked “yes,” I would have seen all of my cousin’s Y-DNA AND all of his Family Finder matches on this list.

Is Morrow the same paternal lineage as Moore? We don’t know. Matching on both tests DOES NOT mean your match is from the same line.

However, this possibility absolutely warrants additional investigation.

Big Y Matching

Big Y matches and tools are displayed separately from STR matches.

The only reason I look at the matches page is to see who has a tree, because the most useful information is provided on the Block Tree and in Discover.

Big Y Block Tree

The Block Tree is an alternate way to view tree relationships over time.

The block tree shows a top-down genetic view of the original Estes line out of Kent. The primary named haplogroup is R-BY482, shown at the top of the blue block labeled “Estes in Kent.” The haplogroup names, like BY483 shown in that same block, mean that all of the men within and beneath that block also have those SNP mutations. Someday, a man may come along and test who does NOT have all of those mutations, or has additional mutations, and may be a candidate to form a new haplogroup.

For genealogy, the point is to see who you’re genetically the closest to.

In this case, our Estes tester falls into the Moses descendant group with haplogroup R-ZS3700. Because other men have already tested and we’ve done that associated genealogy work, we know that this mutation occurred with the birth of Moses Estes, who was born in Virginia in 1711.

Another branch, the James Carroll Estes line, has been defined beneath Moses’ line. If you were to take a DNA test and find yourself in haplogroup R-BY154784, you would know that your ancestor was born to a son of James Carroll Estes who was born in 1860 – so not many generations back in time. You’ll notice a man with the surname of Wilbur in this branch. Sometime, and in some set of circumstances between about 1880 and the present generation, the surname became Wilbur, but the genetic line is absolutely Estes. I view this as the Wilburs having established a new genetic branch in their family line while also being Estes cousins.

Discover

For both Y-DNA and mitochondrial DNA, Discover holds a plethora of wonderful information. Lower-level haplogroups can use the free versions of Discover, but we’re going to focus on information available from the mtFull and Big Y tests when the tester clicks through to Discover from within their own account.

I wrote about Discover broadly here. All Discover reports are educational and help you understand your ancestors and their journey to you, but we are focusing only on the tools you would use to break through brick walls.

Click through on the Discover link in your account on your dashboard for either mitochondrial or Y-DNA.

You’ll arrive on the Haplogroup Story page, which provides a summary of the information available in other Discover Reports.

  1. First, read, don’t skim.
  2. Second, don’t skip the other reports because you read the summary.
  3. Third, check each report for various tabs, displays, and settings.
  4. Fourth, read all the reports.

I wrote a very detailed article about using mitochondrial DNA, Mitotree, and Discover, here.

The Match Time Tree

The Match Time Tree is one of my favorite reports.

Please note the various display options at the top of reports. Checking the “Share Mode” box obfuscates the names of your matches, which allows you to share with others without unintentionally compromising privacy.

I particularly like the Match Time Tree report because it lets you view several things in one place.

  • Your Big Y (or full sequence mitochondrial DNA) matches
  • Genetic lineages and the time when haplogroups were born
  • Globes representing the country where your match indicates that their EKA was born
  • Your matches’ EKAs and family trees, if they have provided them

Additional Bonuses:

  • Ancient Connections
  • WikiTree Connections and lineages

If you add both Ancient Connections and WikiTree Connections to your display criteria, you’ll see them on the Match Time Tree too. In this case, no Ancient Connections are found in this portion of the tree, but four matches have connected themselves to WikiTree as indicated by the rows of pearls.

This is particularly useful because EKAs only display the Earliest Known Ancestors, but you’re probably interested in the entire lineage of your match. Their entire WikiTree patrilineal lineage is displayed on the line, including their common ancestors and their linkage to each other.

In this case, the little blue circle “pearl” on the WikiTree line where I clicked is John R. Estes.

I can click on any pearl and see which ancestor that represents in that match’s tree. I think this is the best thing since sliced bread because, generally, I am looking for the missing ancestor between the tester and their common EKA with their matches. I certainly care about the EKA, but to break down brick walls, I need to know how I can connect from here to there.

Ancient Connections

Ancient Connections shows archaeological excavations from published academic papers and is an evergreen feature. This means that as new Ancient Connections are added, in order of how closely they are genetically related to the tester’s haplogroup, older Connections roll off the end.

You can select the option to view Ancient Connections on your Globetrekker™ video too.

Ancient Connections are anchored in the location where they were excavated by little trowels.

While you may think that Ancient Connections are simply interesting, they hold more information. On a different line, I found another clue about the “rumored” birth city of my ancestor, based on an Ancient Connection buried on the Roman Road just outside the city who could potentially have been his ancestor.

Some Ancient Connections are our haplo-cousins, because they belong to descendant haplogroups from our common ancestor, but sometimes their locations, cultures and artifacts can speak to the lives of our ancestors too.

I wrote in detail how to use Ancient Connections here and here. Don’t shortchange yourself by glossing over these.

Notable Connections

Notable Connections may or may not be useful genealogically. It all depends on who is included, and what the evidence reveals. Some Notable Connections are actually bonus Ancient Connections.

The Estes haplogroup R-ZS3700 connects to the Celtic Mystery Ancestor, but based on the Time Tree, the Celtic Mystery Ancestor cannot be the Ancestor of the Estes line. They do, however, share R-DF49 as their common ancestor.

Who doesn’t love a good mystery? Regardless of how we are related, I enjoyed studying the Mystery Ancestor’s cultural information and assembling it in context with the other Ancient Connections. I stood at Tara, Knowth and Newgrange long before Discover existed, but now I know it might have been where our haplo-cousin lived, and maybe where our common ancestor R-DF49 once stood too.

Notable Connections are intended to be fun facts, but sometimes there’s more.

Globetrekker™

Screenshot of Globetrekker™ video

Globetrekker™ is a video that maps the path your ancestors took across the globe. Note the several display options at the top, along with the legend. Globetrekker™ is really an amazing tool.

Haplogroup locations and connecting lines or paths are based on:

  • Locations of ancient burials which serve as anchors
  • Locations of the EKAs of various testers who carry that specific haplogroup
  • Least-cost travel, meaning given the choice between climbing over the Himalayas or taking the route through a valley beside a river – the valley was almost always the choice of people who survived to create the next generation.
  • Only extending into the Americas for the migration routes of indigenous peoples

You may notice what appears to be confusion or inconsistency in the most recent haplogroups. For example, we know that R-ZS3700 occurred in Moses Estes, born in 1711 in Virginia, son of Abraham Estes, the immigrant, who was born in Kent, England. However, that’s not what the map depicts.

The men who carry R-ZS3700 accurately show their EKA as Nicolas Ewstas born in 1495 in England.

Globetrekker™ can only work with the information it has at its disposal. Moses is not the testers’ EKA, but he is the progenitor of R-ZS3700. The way we know that R-ZS3700 occurred in Virginia in 1711 is because the tested male-line descendants of Moses all carry that SNP mutation, while tested male-line descendants of Moses’s siblings, Abraham’s other sons, do not.

Another potential reason that haplogroup placement might appear faulty is because multiple testers with that haplogroup show different locations.

Let’s say the EKA location provided by one man is Dover, Kent, England, across the Strait of Dover from France. A second man shows his EKA on the far western coast of Ireland in Galway, and a third man places his EKA in the Orkney Islands, off the Northern coast of Scotland.

The “average” of those three locations might be someplace around Dumfries in Scotland, even though none of the three men entered that location – and all three testers are equally unhappy.

Keep in mind that EKA information and locations are user-entered, and, as we know, genealogy can be incorrect and people are sometimes confused.

Another factor affecting placement is that when someone enters only a country name, maps default to the center of the country, which can pull the Globetrekker™ migration paths in one direction or another.

Globetrekker™, in combination with other tools, provides valuable evidence about your ancestor.

Globetrekker™ for mitochondrial DNA has not been released but is planned for the future.

Suggested Projects

Suggested Projects can also provide clues.

Projects are suggested for one of three reasons:

  • Other people with that surname have joined that project
  • The surname administrators have identified your surname as “of interest” to their project
  • Your haplogroup, haplogroup branches, or specific keywords

If you’re searching for your ancestor, hints about their origins or family associations may be found in the projects suggested.

Mitochondrial DNA Match Time Tree Haplotype Clusters

One important difference between the Y-DNA Match Time Tree and the mitochondrial DNA Match Time Tree is that the mitochondrial DNA version displays results within haplotype clusters.

On the Match Time Tree, your results are displayed with other members of your haplotype cluster. These are your closest matches.

That isn’t to say that some of your identifiable ancestors won’t be found in other haplotype clusters, or even neighboring haplogroups, but the place where you should start your analysis is with other people in your haplotype cluster.

I’ve written about haplotype clusters here and here.

Your Summary Checklist

Mitochondrial DNA and Y-DNA have the unique ability to look in a laser-straight line back in time. Unlike autosomal DNA, mtDNA and Y-DNA aren’t recombined, so parts of your ancestor’s DNA aren’t lost during recombination with the other parent’s DNA.

The tools on your personal page, plus Discover Reports, provide at least 25 different ways to analyze your results, several of which are critically important for genealogy and, specifically, breaking through brick walls.

  1. Y-DNA STR matching and Big Y DNA matching are different, so take advantage of both and review every level.
  2. Big Y-700 results include several features that neither STR matching nor mitochondrial DNA can offer.
  3. Mitochondrial DNA provides features not available for Y-DNA.
  4. Matching includes how close or distant the match is, their haplogroup, EKA, EKA’s country of origin, and family tree.
  5. The Matches Map provides the exact location provided for your matches’ EKAs, not just the country.
  6. Enter your patrilineal and matrilineal Earliest Known Ancestor (EKA), their ancestral location, and all of your family surnames.
  7. Be sure you’ve uploaded a tree. Also, connected yourself to your WikiTree profile.
  8. Be sure to check your matches’ trees and their WikiTree connection, if they have one, and build out as necessary to connect with your EKA and your other matches’ EKAs.
  9. Use Group Project Results to check groupings made by the volunteer administrators, EKAs, and possibly marker values.
  10. The Y-DNA Block Tree displays matches along with their mutations in a vertical phylogenetic tree format.
  11. Mitochondrial DNA matching also provides your legacy (pre-Mitotree) haplogroup, plus your Mitotree haplogroup, haplotype cluster and features like trees. Be sure to view all match levels.
  12. Haplotype clusters group mitochondrial DNA testers who match exactly, and include less-reliable markers that are excluded from general matching and haplogroup formation. Research to identify a common ancestor should begin with your haplotype cluster, but should not ignore people in different haplotype clusters.
  13. Investigate unfamiliar surnames through family histories, testing male-line descendants of different sons, and researching descendants of the identified genetic ancestor. Look for intersections and remember: right time, right place, opportunity.
  14. Advanced Matching allows you to combine two (or more) forms of DNA test to determine if someone matches you on both tests, such as either a Y-DNA or mtDNA test and the Family Finder autosomal test. Remember that they may match on both tests due to different ancestors.
  15. Y-DNA haplogroups found in Family Finder matches may identify additional family members in your lineage who have not taken a Y-DNA test (but might be willing to).
  16. Discover provides more than a dozen additional reports.
  17. The Match Time Tree plots your matches with their EKAs along a genetic timeline.
  18. The Match Time Tree also displays WikiTree Connections, which include each generation, not just the EKA.
  19. The Match Time Tree displays Ancient Connections and Notable Connections, which may prove useful.
  20. Ancient Connections provide insight into the movements of your ancestor, their culture and location at a specific point in time.
  21. Globetrekker™, an animated Y-DNA video, tracks your ancestor’s journey across the world to the locations where recent haplogroups are found, based on a variety of criteria and data points.
  22. Suggested Projects provides a list of projects that you may be interested in joining based on common interests. The suggestions alone may be especially important when surnames aren’t particularly helpful, and when you’re searching for your ancestor’s origins.
  23. Use Discover’s Compare feature to determine how different haplogroups relate to each other and whether they are in the same genetic lineage. This is particularly useful for autosomal matches with the same surname.
  24. Use shared matches, segment triangulation, and your matches’ trees to investigate possible connections identified through Family Finder surname and haplogroup searches.
  25. Contact matches, collaborate, and preserve the genealogy they provide.

Your ancestors are waiting for you to find them!

_____________________________________________________________

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’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

I receive a small commission when you click a vendor link in my articles and purchase that item. 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

FOCUS: Step 2 – Finding the Y-DNA and Mitochondrial DNA of Your Ancestors

This is the third article in our FOCUS series, providing step-by-step instructions for identifying brick-walled ancestors.

These two articles detail the initial steps:

By now, you will have selected the ancestor you want to focus on identifying, and you have tools in your toolkit for working with DNA matches who have no trees.

You may have ordered DNA tests from multiple vendors and are waiting on results, so while you wait, we’ll start with finding the Y-DNA and mitochondrial DNA of your ancestors and identifying DNA testing candidates.

While it may sound counterintuitive, we’re going to be working with all of the major vendors, including FamilyTreeDNA, who actually tests for Y-DNA and mitochondrial DNA, plus WikiTree, 23andMe, MyHeritage, Ancestry, GEDmatch and FamilySearch. They are all quite useful in different ways.

This Type of Searching Is Different

Normally, when we search for brick-walled ancestors, we are searching backward in time. In other words, we begin with the last person we know and work back from there, hoping to identify the previous generation.

If we don’t know Lucy’s birth surname and she was born about 1750, and married William Moore in the late 1770s, we begin with what we do know in that timeframe.

Searching for our ancestor’s Y-DNA or mitochondrial DNA, and testers who carry that DNA, is fundamentally different because we begin with that ancestor and work forward in time.

In other words, if we want to find Lucy’s mitochondrial DNA, we begin with her daughters and track forward in time to the present. Hopefully, someone has already tested, and we can locate that result, but if not, we need to find people who descend through a specific path that carry Lucy’s mitochondrial DNA.

If we were searching for the Y-DNA of William Moore, we would look for his direct paternal descendant males who would carry the Moore surname.

Chicken or Egg?

I’ve been debating whether I should show you:

  1. How to locate and identify the Y-DNA and mitochondrial DNA of your ancestors first, or
  2. How to use Y-DNA and mitochondrial DNA (mtDNA) to help break through your brick wall first

I decided to write the “how to locate” article first because I don’t want you to skim over and ignore the ‘how to use’ article, thinking it’s irrelevant to your research because you don’t carry the Y-DNA and/or mtDNA of your brick-walled ancestor.

There are lots of avenues to locate the Y-DNA or mitochondrial DNA of your ancestors, something you definitely want to do. You’ll soon see that Y-DNA and mtDNA information can also assist with autosomal DNA results.

These are all pieces of your ancestor’s puzzle, and you never know which one will be the one to topple that wall.

Plus, you don’t know what you don’t know about that ancestor.

Let’s jump right in!

Who Carries the Y-DNA and Mitochondrial DNA of Your Ancestor?

As a quick refresher, only men can test for Y-DNA because only men have a Y chromosome which is inherited from their father. It’s passed in a direct paternal line from father to son, never mixed with DNA from the mother. Because it’s never divided during recombination like autosomal DNA, it’s uniquely useful for connecting lineages both recently and back in time hundreds and thousands of years.

Both Y-DNA and mitochondrial DNA incur occasional mutations that function as genetic breadcrumbs, making them incredibly useful for reassembling those specific family lines where genealogy paper trails have broken or been interrupted.

Mitochondrial DNA is passed from mothers to their children of both sexes, but only daughters pass it on. This means that in the current generation, males and females can both test for the mtDNA of their direct, mother-to-mother, matrilineal line.

Anyone, including males, who descends from an ancestor through all females can test for that ancestor’s mitochondrial DNA.

If you’re lucky, you’ll carry the Y-DNA or mitochondrial DNA of the ancestor you are seeking. If not, you’ll need to do one of two things:

  1. Determine if someone has already tested for that ancestor
  2. If not, find candidates to test

Y-DNA is generally easier because you at least (hopefully) have a surname to work with that has been passed from father to son, along with their Y chromosome.

Mitochondrial DNA is more challenging since surnames change each generation, so I’ve included several mitochondrial examples. Don’t skip over them, because the same research techniques apply to Y-DNA too, especially difficult cases.

If you’re a male, I strongly recommend that you order:

If you’re a female, you can only order the mtFull test, but you may be able to ask your father or brother or a male relative (with the surname in the lineage you seek) to take the Big Y-700 to represent your father’s family line. In other words, if you’re looking for a male Estes, you can ask your 2C Estes male who descends in a direct paternal line of all Estes men from your common ancestor.

Complete Versus Partial Tests

Haplogroup-only results derived from autosomal tests are fine as far as they go – but they don’t go very far. Most are what I would call midrange, providing testers with a haplogroup from maybe 2000 years ago, and some are much more distant than that. That isn’t to say they can’t be useful in a limited capacity, but Y-DNA and mtDNA have so much more potential.

You need comprehensive Y-DNA and mtDNA test results that identify all your haplogroup-defining mutations and can be refined as more people test and match family-level mutations.

Haplogroups are important, but you also need to match with other testers. Additionally, you’ll want the most complete haplogroup possible, because it will help you genealogically by providing a complete breadcrumb trail with the ability to identify your most recent common ancestor (MRCA).

FamilyTreeDNA is the only vendor that offers these complete tests that include matching with other testers, plus additional genealogy tools.

The Big Y-700 test scans for mutations in the stable portion of the Y chromosome and is the only way to obtain that personal-level information. It’s those recent mutations that will help place you within a biological family – or eliminate you from other lines, which prevents barking up the wrong tree.

The benefit of taking the test yourself, or sponsoring a test for someone willing to share their results with you, is that you have ready access to information through FamilyTreeDNA’s tools such as:

  • Matches with other Y-DNA and mtDNA testers
  • Matches Map (ancestor locations)
  • Advanced Matching, which provides a filtered list of people who match you on BOTH your Y-DNA or mitochondrial DNA AND your Family Finder autosomal test
  • Haplotype clusters (for mtDNA)
  • Your mutations
  • Block Tree (for Y-DNA)
  • Customized Discover tools

Click any image to enlarge

  • Discover’s Advanced Tools like the Match Time Tree, shown above, which displays your matches with their earliest known ancestors (EKA) together on the Time Tree
  • Globetrekker™ (for Y-DNA with mtDNA coming soon)
  • Up to 30 Ancient Connections
  • Up to 20 Notable Connections

FamilyTreeDNA’s free Discover tool, here, provides public information for everyone about haplogroups, but if you haven’t taken the test, you won’t receive matching and customized information described above, which is essential to genealogy.

Upgrades for Partial Tests

You may have previously tested at a lower level at FamilyTreeDNA.

For mtDNA, the early mtPlus test examined a portion of the mitochondria and provided matching at lower levels, as do the 12-111 marker Y-DNA tests. Both provide a predicted high-level basic or midrange haplogroup based on the mutation information available in those limited tests.

If you took an earlier, partial test, you can sign on to your account to upgrade by clicking on the “Big Y,” even though it’s greyed out. Grey simply indicates that you don’t currently have that level of test.

Click on “Full” to upgrade to the mtFull test.

Test Features at Various Levels

Depending on the type of test you take, and at which vendor, you may have a fully refined or partial haplogroup.

Discover provides a substantial amount of information if you receive a partial haplogroup:

A partial haplogroup is better than no haplogroup, but it’s also like working with one hand tied behind your back. If at all possible, you need to work with a full haplogroup and matches.

Testers who click through to Discover from their own test, or a test they manage, can view additional features not available in the free version.

The table below shows the four different ways you can access and view your ancestor’s haplogroup. Based on the testing level and/or how they tested, the haplogroup level will vary.

Clearly, the best scenario is when you either take the Big Y-700 or mtFull test yourself, or you have access to the test results of someone who takes that test to represent your ancestor’s DNA. Primary access confers the greatest amount of information, but you can still glean information in other ways.

Feature Introductory Level Test at FamilyTreeDNA* Tester’s Big Y-700 or mtFull Test – Full Access Partial Haplogroup from Autosomal Test Your Ancestor’s Haplogroup but without Full Access
Matching Yes, at that lower level Best – at all levels No No
Matches Map Yes, at lower level Yes No No
Mutation Values Yes, STR markers at lower Y-DNA level Yes, STRs (Y-DNA) and SNPs Not directly but through Discover Not directly but through Discover
Haplotree & SNPs with surnames (Y-DNA only) Yes, at lower level Yes No No
Block Tree (Big Y test only) No Yes No No

 

Advanced Matching (multiple types of tests) Yes, at that level Yes No No
Ability to Join Group Projects Yes Yes Only test owner or manager can join Only test owner or manager can join
Discover Reports Yes, same information as the free version due to lower coverage Yes, when clicking through from your FamilyTreeDNA account Free version Free version
Haplogroup Story Yes, at lower haplogroup level Yes – best and highest level Yes, at lower haplogroup level Yes, at lower haplogroup level
Country Frequency Map and Table views Yes, at lower haplogroup level Yes, at most refined haplogroup level Yes, at lower haplogroup level Yes, at most refined haplogroup level
Notable Connections Same as free version About 20 for Y-DNA, 11 for mtDNA About 10 for Y-DNA, 3 for mtDNA About 10 for Y-DNA, 3 for mtDNA
Migration Map Yes, at lower level Yes, at advanced level Yes, at lower level Yes, at advanced level
Globetrekker (Y-DNA only, mtDNA coming soon) No Yes No No
Ancient Connections Same as free version About 30 About 10 for Y-DNA, 3 for mtDNA About 10 for Y-DNA, 3 for mtDNA
Time Tree Yes, at lower haplogroup level – generally 2,000 years or older Yes, at most refined haplogroup level, often within genealogical timeframe Yes, at lower haplogroup level – generally 2,000 years or older Yes, at most refined level
Match Time Tree No Yes – your matches & their EKA on the Time Tree including WikiTree Connections and Ancient DNA No No
Ancestral Path Yes, at lower haplogroup level Yes Yes, at lower haplogroup level Yes
Suggested Projects Yes Yes, at more refined level Yes, but must test with FamilyTreeDNA to join Yes, but must test with FamilyTreeDNA to join
Scientific Details, ages and variants Yes, at lower level Yes Yes, at lower level Yes
Compare Haplogroups Yes Yes Yes Yes

*Note that often your ancestor’s haplogroup as reported by the Family Finder (autosomal) test is more refined, meaning closer in time, than the Y-DNA haplogroups predicted by STR tests, but both are always substantially less specific than the Big Y-700 test. As of the publication date of this article, Family Finder does not yet report a mitochondrial DNA haplogroup, but that is planned for the future.

This chart only includes features you would specifically use to identify an ancestor or ancestral lineage. There are other reports provided with your test that will be of interest. Discover provides about 14 reports that include various options.

Now we can envision:

  • The benefits of finding our ancestors’ Y-DNA and mtDNA
  • The benefits of obtaining the most refined haplogroup possible
  • The benefits of being able to view the results directly

You may not be able to achieve all of these, but even a partial haplogroup is better than no haplogroup at all, and a fully refined haplogroup, even if you can’t see everything in another tester’s account, is better than a partial haplogroup.

So, let’s see how to find your ancestors’ haplogroups. I collect them all, not just for brick-walled ancestors, but because they tell a part of our story not available through any other means.

Finding Your Ancestor’s Mitochondrial and Y-DNA

If you are the DNA tester for your brick-wall ancestor, then you’re golden, but chances are that you’re not.

If you’re searching for Y-DNA, and you don’t carry that Y-DNA yourself, you’ll need a male relative who carries that Y chromosome to test.

Males carry the Y-DNA of their direct patrilineal ancestors, shown in the image below on the left side in blue, plus the mitochondrial DNA (mtDNA) of their mother, shown with yellow hearts at far right.

At the 4th generation level, we have 4 Y-DNA lineages to collect (light blue, dark green, medium green, and teal), and a total of 8 mtDNA lineages.

Let’s say you’re searching for your father’s mother’s mother as your brick-wall ancestor.

Your father (and his siblings) carry the mtDNA of his mother, shown above in fuchsia, as do her grandchildren through her daughters. That’s why your father has a fuchsia heart. If close family members test, chances are you can arrange to manage their test or view their results. (Be sure they take the autosomal Family Finder test too. You’ll need that later.

If you don’t manage their test for them, you’ll need to ask to see their results to view matches and work with trees.

I have a family project at FamilyTreeDNA that I manage. I ask people who have tested for a particular ancestor to join that project so I can easily view their results while they continue to manage their test, and can select how much they want me to see or do.

FamilyTreeDNA is currently working on a multi-kit management feature that will address the challenge of sharing results.

But I Don’t Know of Any Cousins…

Let’s say you don’t know of and can’t readily identify anyone who descends from your ancestor appropriately.

If the ancestor you seek is a male, mitochondrial DNA is probably not going to help you because men don’t pass their mitochondrial DNA on to their descendants. In order to obtain a male ancestor’s mitochondrial DNA, you’d need to be able to identify a sister or someone known to descend from his mother (or sisters) through all females to the current generation. Needless to say, if you know who his mother is, you probably already know who he is.

If your brick wall is a female ancestor, your first order of business is to find someone who descends from her through all females to the current generation, where the tester can be male or female.

Why is this so important?

Mitochondrial DNA isn’t admixed with the father’s DNA, so it’s not divided in each generation. This means that mitochondrial DNA is the only direct line-of-sight we have that bypasses both changing surnames and genetic recombination for females.

Who Has Tested for Your Ancestor?

If you’re NOT the tester for your brick-walled ancestor or aren’t the curator of the test, your first step is to see if someone else has already tested.

This can sometimes be challenging.

It’s impossible to obtain mitochondrial DNA for an unknown ancestor if there are no known daughters, and for Y-DNA if there are no known sons. You may need to review genealogical resources to make sure you’ve identified all of that ancestor’s children.

Barring those scenarios, there are a surprising number of resources available to find descendants.

WikiTree

The first place I check to see if someone has already tested for a particular ancestor is WikiTree.

WikiTree is the one place where you find the ancestor along with the people who have taken DNA tests who descend from that ancestor. It’s invaluable.

Normally, you have to work with matches to identify your common ancestor. WikiTree works the other way around. Your starting place is with the ancestor.

You can’t Google your mystery ancestor’s name because if you knew their name, they wouldn’t be a mystery ancestor – but you can Google their spouse or a child.

I’m using an example from my own line because my mitochondrial DNA results are connected to her.

I’m Googling:

Barbara Mehlheimer born 1822 died 1906 in Indiana at WikiTree

Google was slightly confused but the results got me to where I needed to go.

Barbara Mehlheimer married George Drechsel and her daughter was Barbara Drechsel who married Jacob Kirsch.

First, check Barbara’s WikiTree profile card to confirm you’ve found the correct person.

Next, click on the DNA tab beneath her profile information (or just scroll down). She has four DNA Connections.

You can see that one person, me, who carries Barbara’s mitochondrial DNA has connected their DNA to Barbara’s profile. I did this by entering my DNA information on my WikiTree profile, then WikiTree connects my DNA haplogroup information from mother to mother to mother to Barbara and propagates my DNA haplogroup to her, her matrilineal ancestors, and their female descendants. If you click on the haplogroup, it takes you directly to that haplogroup in Discover.

Three people have connected their autosomal results to Barbara. This information can be very important, and not just for mitochondrial DNA. It allows us to identify autosomal testers we may match at different testing companies who descend from Barbara.

In your research journal, make notes of these names, testing companies, and kit numbers. Remember that this doesn’t mean the company noted is the only place someone has taken an autosomal DNA test. I’ve tested at all of the major companies, but only GEDmatch and FamilyTreeDNA are listed here.

For Y-DNA and mitochondrial DNA, the haplogroup is shown, although when testers receive a new Y-DNA or Mitotree haplogroup, they seldom think to revise it in WikiTree. This means their current haplogroup may be more specific and improved since the WikiTree information was entered.

Some people may have tested at different levels too. In this case, Buster Estes, who is now deceased, was one of the earliest testers, long before the Big Y tests were available. He only took a 25-marker test, so his haplogroup was predicted as R-M269. Garmon, on the other hand, was able to upgrade his Y-DNA test to the Big Y-700, and his haplogroup is much more refined at R-ZS3700. Their haplogroups don’t match exactly due to the levels at which they tested, but they also don’t preclude the two testers from belonging to the same genetic line.

This screenshot of Discover’s Compare function illustrates how important the Big Y-700 test is when compared to the STR test’s predicted haplogroups. The man who developed the mutation that defines R-ZS3700 lived about 1750 CE, and the man who developed R-M269 lived about 4450 BCE, or 6,450 years ago. That’s a big difference.

Using a combination of multiple testers and genealogy, we’ve identified the man who developed R-ZS3700 and passed it on to his sons. Moses Estes was born in 1711 in Virginia and all of his descendant testers carry R-ZS3700.

Now that’s extremely useful information, because we know that any man with haplogroup R-ZS3700 descends from Moses Estes in a direct paternal line, and any man whose haplogroup is not R-ZS3700 or doesn’t include R-ZS3700 upstream of his haplogroup does not descend from Moses Estes in that way.

Please add your DNA tests, including haplogroups and your kit number, to your profile at WikiTree so that the haplogroup information can be populated appropriately to your ancestors.

Searching for a Test Candidate Using Autosomal Descendants

When you’re searching for a testing candidate at WikiTree, you can click through to the tester’s profile and view exactly how they descend from the ancestor shown.

Let’s say that no one has linked a mitochondrial DNA test to the ancestor you’re searching for, but several people have linked autosomal tests to that ancestor’s profile card.

Click on the tester’s name and then on the DNA Ancestors tab to see how they descend from that ancestor. If you’re lucky, you’ll find someone in the autosomal list who is a mitochondrial DNA testing candidate.

If you’re looking for a Y-DNA tester, begin by looking for a male with the same surname as that ancestor. If you’re looking for a mitochondrial DNA tester, you’ll need to view each tester’s ancestors.

Regardless of whether they are a mitochondrial or Y-DNA testing candidate, you’ll identify your most recent common ancestor (MRCA) for each person, information that will become essential for the autosomal tools that we’ll be discussing in future articles.

In your research journal, I suggest that you record all of their descent information now, including their names, where they tested, your MRCA, kit numbers and any other relevant notes.

If you’d like to ask them to take a specific test, or if they already have and you’d like to know more, you can message WikiTree users by clicking on their profile, and then on the little envelope beside the profile manager’s name.

Finding Your Ancestor’s DNA Descendants at WikiTree

Let’s say that no one in the DNA list of people who have already taken tests descends from your ancestor matrilineally. Don’t worry, there are still more options!

At the top of the WikiTree page for that ancestor, click the down arrow, then on DNA.

The default tab shows the DNA Ancestors of the profile you’re viewing. You’ll see Y-DNA for males, and both mitochondrial and X-chromosome ancestors for everyone.

You may notice that there’s an ancestor listed for your brick wall ancestor. That’s wonderful, but don’t jump for joy quite yet. Remember, WikiTree is a one-world tree, and you need to verify the underlying genealogy in every tree here, and at every vendor.

Always confirm using multiple sources, meaning resources other than trees. The great thing about WikiTree is that there are often several sources listed in each person’s profile, and other resources that can help immensely. I love WikiTree, but I’m always skeptical of information in any tree, and I prove everything to my own satisfaction. I wrote several articles about that topic in the Genealogy Proof Series, here.

To find testers, you’ll need to view your ancestor’s DNA Descendants.

Click on the DNA Descendants tab.

The Mitochondrial DNA Descendants view shows potential candidates for mtDNA testing. Remember, in the current generation, males and females can both test so long as they descend from that ancestor through all females.

In the case of Barbara Mehlheimer Drechsel and her descendants, there are several males who are immediately eliminated because they’ve been deceased for more than a century, and several daughters who didn’t have children.

Not every person’s line on WikiTree has been added or developed. You can see that three daughters’ lines that might hold candidates don’t list all their children, and I still need to research two additional people. That means I still have five candidate lines to extend that have potential mtDNA testers.

So, in summary, if Barbara was the ancestor I was seeking:

  • One person has already tested
  • Three daughters don’t have their families extended.
  • Two have daughters that I need to research.

For both Y-DNA and mitochondrial DNA, I like to have at least two people who descend from different children of the ancestor, and whose tests match at a level that does not preclude that lineage. This helps confirm both the genetic line and the genealogy of both testers.

With male ancestors, having more than one tester for each line through different siblings is essential.

Kit Numbers, Earliest Known Ancestors and Google

When DNA kit numbers are included at WikiTree, you’ll want to Google to see if that kit number is shown in a public Group Project at FamilyTreeDNA where you may find more information.

The exact search string to use to find a specific kit at FamilyTreeDNA within projects is:

“9993” site:familytreedna.com

Replace 9993 with the kit number you’re interested in. You can also add the word “projects”, without quotes, to the end of that string to omit forums and limit the search to within projects. This string both focuses and limits the search, filtering out most noise.

By clicking on “read more,” you’re taken directly to the Estes Family Surname Project Y-DNA page.

The green haplogroups are SNP-confirmed, unlike the red predicted haplogroups from the lower-level 12, 25, 37, 67 or 111-marker tests. The R-ZS3700 haplogroup was obtained from the Big Y-700 test, so it is the most granular and specific. If this is your line, you’ve just found your ancestor’s haplogroup. It’s also possible that, by testing, you could receive an even more specific haplogroup.

Please note that haplogroup R-M269 is the most common haplogroup in Europe, and isn’t specific enough to use for anything other than very basic information. It can rule out two people with different base haplogroups, like haplogroup I or J, for example, as descending from a common patrilineal ancestor.

Project administrators are all volunteers, and each administrator groups their Group Project members differently, so take a few minutes to review the project pages. You may find additional testers who have joined this project who descend from your ancestors or your ancestral line.

You may also find other lines with the same surname and a substantially different haplogroup, which tells you that there are multiple genetic lines with the same surname. I have one example of this in the same county, at the same time, found in men by the same exact name – think John Smith. So frustrating. Without DNA testing, we would NEVER have sorted through those two same-name but completely different lines.

However, finding people who match your ancestor’s DNA but don’t have your earliest known ancestor (EKA) may be just the clue you need to knock down that brick wall. How are your ancestor and that other person’s EKA connected, and in what timeframe? Do they share a surname? A location? Are there other clues?

It’s unlikely that you’ll be able to use a kit number to Google unless you find one at WikiTree, but you can still search using the oldest name in that line that you know.

nicholas ewstas site:familytreedna.com

Replace the kit number with your EKA, in this case, “Nicholas Ewstas” in the search string, either with or without quotes. This takes you to the same page and any other projects that someone may have joined using exactly that earliest known ancestor’s name. Keep in mind that you’re only looking at their oldest ancestor, not every ancestor between them and their EKA. Your brick wall may lie someplace in there, which is why you need to check matches and view their trees.

Since women’s surnames change in every generation, they generally won’t be found in specific ancestral surname projects like men. This makes Googling using the ancestor’s name even more important.

catherine lejeune site:familytreedna.com

We don’t know who Catherine LeJeune’s mother is, so finding that someone has entered Catherine as their EKA may be critically important.

This is especially important for female brick-walled ancestors, since using this Google string with their daughters’ names may reveal someone else’s EKA in that genetic line within a project.

After clicking through to the project page, be sure to enlarge the page to display the full project, and use your browser search since partial results with predicted haplogroups may not be grouped with full mitochondrial sequence results.

Multiple people who descend from Catherine LeJeune have tested. The first six only took the partial test years ago. The bottom two testers took the full sequence test and have a new Mitotree haplogroup – U6a7a1a. We know that Catherine was born about 1633, in France, and we can see that other people have also tested and list different EKAs. Next, it’s time to research the other ancestors shown, or check WikiTree to see if any of these testers are listed there so you can contact them.

Now that you have found your ancestor’s haplogroup, you can use the free version of Discover to learn more. I wrote about using mitochondrial DNA and Discover in the article Mitochondrial DNA A-Z: A Step-by-Step Guide to Matches, Mitotree, and mtDNA Discover.

Now, let’s move to the DNA testing companies to see how we can find our ancestors’ Y-DNA, mitochondrial DNA, or testers, at 23andMe, FamilyTreeDNA, Ancestry, and MyHeritage.

At 23andMe

23andMe is not a genealogy company. That said, if you can figure out how people are related to you, you might be able to obtain a partial haplogroup for an ancestor. 23andMe shows both Y-DNA and mitochondrial DNA haplogroups to autosomal matches, but there is no Y-DNA or mitochondrial DNA matching, or associated tools.

23andMe caps matches without a subscription at only 1,500, and they don’t support trees, so I struggle to find useful haplogroups without an associated surname.

Browsing or searching your 1,500 allowed matches (you can have around 5,000 with a subscription) for a particular surname may provide you with an abbreviated haplogroup for both male and female ancestors.

Despite my best efforts, while my maternal grandfather’s mother is not unknown, nor are her ancestors for several generations reaching back into Germany, I’ve been unable to find her mitochondrial haplogroup. Evaline Miller (1857-1939) was born and died in Kosciusko County, Indiana, where she married Hiram Bauke Ferverda, an immigrant from the Netherlands.

Ferverda is an unusual surname, so let’s use it for our example. Thankfully, I’m not dealing with something like Smith.

I entered Ferverda in the 23andMe search bar and it shows four results, two of which are in the 2C-3C range, and one that’s further distant.

I already have the Ferverda Y-DNA, so I don’t need that, but I do need the mitochondrial DNA of Eva Miller Ferverda, and I really don’t want to sift through Miller surnames.

I know who Mr. Ferverda is on my match list, and which ancestor we share. His mitochondrial DNA is not Eva Miller’s.

Fortunately, I know who Eva’s parents were, as shown above on my MyHeritage tree, so I can search for Ferverda, Miller, Lentz, Ruhle, Wolflin, and Heubach, several of which are unusual. Reaching back into Germany is difficult.

It’s likely I match all four of those people at 23andMe through a common lineage that descends from either Hiram Ferverda, Eva Miller, or both. Let’s see what I can put together.

Emily is estimated to be a 2C2R. She is younger than I am based on the birth year she provided in her profile which I am not showing for privacy reasons. Emily also stated that her maternal grandmother was born in Warsaw, Kosciusko County, Indiana, and provided family surnames that include Ferverda, Miller, Glant, Zimmermann, and others.

Kosciusko County is where Evaline Miller lived with Hiram Ferverda, and their daughter, Margaret, married Chester Glant. Margaret Ferverda Glant’s daughter, Joyce, was born in Kosciusko County and married a Zimmerman.

But now, I was stuck. That’s all I had in my desktop genealogy software.

I shifted to Ancestry, where I discovered a death certificate and other information that provided what I needed to close the gap.

This information confirmed Emily’s statement that her maternal grandmother was born in Warsaw, Kosciusko County, Indiana.

Therefore, drum roll…Emily carries Eva’s mitochondrial DNA haplogroup, which is T2b.

Let’s move on to the other two matches, both of whom carry haplogroup T2b.

Ian’s maternal grandmother’s birthplace is Leesburg, Kosciusko County, Indiana, and his surnames include both Ferverda and Robison.

Eva Miller Ferverda’s daughter, Chloe Ferverda, married Rolland Robison and had a daughter, Charlotte, whose daughter married a man with Ian’s surname. Their information allowed me to connect the dots appropriately. Ian’s mitochondrial haplogroup is also T2b, which confirms Eva Miller’s mtDNA haplogroup through a second child.

Shirley, the third match who carries haplogroup T2b, also shows the surnames of Ferverda and Robison, and tracks back matrilineally to Eva Miller.

In spite of the many challenges at 23andMe, and thanks to the rare surname of Ferverda, I’ve identified Eva Miller’s partial haplogroup, but not her full haplogroup. A partial haplogroup is much better than nothing and gives me something to work with.

I checked at Ancestry, MyHeritage and FamilyTreeDNA to see if any of those three people have tested there and have trees. Indeed, Ian tested at FamilyTreeDNA and I had corresponded with him and made a note that he is a matrilineal descendant of Eva Miller Ferverda, but he has not taken a mitochondrial DNA test there.

We know that if Emily, Ian, Shirley, or another appropriately descended person were to take a full-sequence mitochondrial DNA test, we would learn a LOT more about Eva’s mitochondrial DNA. If I can’t locate someone who has already tested, I’ll reach out to these people at 23andMe and offer a scholarship for a full-sequence mtDNA test.

It’s ironic that at the most restricted and least likely testing company, I found three people descended from Eva Miller. Hope springs eternal.

Unfortunately, T2b was formed about 8450 years ago and is a very broad haplogroup made up of many subclades, but at least I have something now – and this partial haplogroup may be just the seed I need to lead to more.

Now, let’s move to FamilyTreeDNA and hope that someone there has already taken the mtFull test.

At FamilyTreeDNA

There are multiple ways to find the Y-DNA or mitochondrial DNA of your ancestors at FamilyTreeDNA.

Project Search

You can search for surname projects along with other types of projects.

On FamilyTreeDNA’s main page, without signing in, scroll all the way to the very bottom footer where you will see the Group Projects link.

If you’re searching for a surname, enter that surname in the search box.

The next screen shows projects that people with the Estes surname, including females, have joined. This includes all types of projects and does NOT mean that these projects are relevant to your line, but it does include two surname projects you may find useful.

Scrolling down shows you how many people with the surname of Estes have tested. Keep in mind that some will be females, some use married names, and sometimes people use an alias, so they aren’t included in this count.

Surname projects for females aren’t terribly helpful since the surname typically changes in each generation, at least in Western cultures.

You can also search for keywords, such as Acadian. If you know that ancestral line is Acadian, you may find clues there, including descendants of your brick-wall ancestor.

Group Project Time Tree

Many Group Projects at FamilyTreeDNA have enabled the Y-DNA Group Time Tree feature. When visiting the project, if the administrator has the Group Time Tree enabled, click on that link under the DNA results tab.

The Group Time Tree is a genetic tree of Y-DNA testers within that project based on the groups created by the project administrator.

The groups constructed by the administrator are shown at left, the Time Tree in the middle, and the testers with their EKAs and country of origin flags at right. I’ve added the red text to reflect the Estes genealogical lineage.

Based on the timeline at the top, you can see how closely these Y-DNA testers are related in time. Each haplogroup shown represents a different branching genetic lineage – breadcrumbs at work. If you are a genetic Estes male who descends from the Estes family that originated in Kent, England, and you take the Big Y-700 test, you’ll be a member of R-BY482 or its descendant haplogroups.

Keep in mind that not all testers join group projects, so it’s likely that there will be matches on your match list that aren’t here. Furthermore, only Big Y testers appear on any Time Tree.

The Group Time Tree is public, but when you sign in to your account and click on the Match Time Tree from your account, you’ll be able to view more, including testers’ trees and WikiTree connections if your matches have connected themselves to WikiTree.

Click to enlarge

I’ve converted the Estes genetic tree into a genealogical tree in a spreadsheet based on the trees of DNA matches. I’ve also included STR testers, because they are good candidates to upgrade to Big Y tests, and they are shown in the Estes Group Project. They can’t be included in the Time Trees because they don’t have the SNPs discovered with the Big Y tests. Please note that not all testers were included in this spreadsheet.

You can follow the paths of the various haplogroups. All of the red-background, black-outlined cells are Big Y-500 or Big Y-700 testers. The Big Y-500 was obsoleted several years ago in favor of the much more informative Big Y-700 test, which reveals additional haplogroups because it tests more of the Y chromosome. I’m still hoping that people will upgrade, although some testers are deceased and can’t.

The Big Y-500 tests with red stars are candidates to be upgraded to the Big Y-700 to potentially receive a more specific haplogroup. The balance of the tests in red cells are Big Y-700 tests, which identify several additional Estes haplogroup paths.

Let’s look at an example.

Beginning at the top, we know that R-BY482 is present in Nicholas Ewstas, born in 1496 in Kent, England, because all of his descendant testers carry that haplogroup too. Additionally, three generations later, in Silvester’s generation, he developed the additional mutation named R-BY490. We know it developed in Silvester’s generation for two reasons:

  • The descendants of Silvester’s brother, Robert, born in 1603, do NOT carry R-BY490. Robert’s son Matthew’s descendants only carry R-BY482.
  • The descendants of both of Silvester’s sons, Richard (pink column) and Abraham (the entire green row), all carry R-BY490.

All of the descendants of Silvester’s son, Abraham, born about 1647, the Virginia settler, who have taken the Big Y test carry R-BY490. Additionally, descendants of several of Abraham’s sons, color-coded columns beneath the green row, have developed additional haplogroups. Several more testers would likely have new haplogroups if they took the Big Y-700 test. A new haplogroup requires at least two men with the same unique mutation (breadcrumb), in addition to R-BY490 (in this case), to identify a specific lineage and assign it a new haplogroup name.

Abraham’s son, Moses Estes, born in 1711, is a good example. We know that Moses developed the mutation R-ZS3700 because four of his descendants have taken the Big Y-700 test and have that mutation that is not found in Moses’s brothers’ lines. All four Moses descendants carry R-ZS3700, and two, in the James Carroll Estes line, have developed an additional mutation, haplogroup R-BY154784.

Until Big Y testing became available, descendants of the R-BY154784 lineage didn’t know where they fit in the Estes tree, because the connecting genealogical records between Missouri, where their ancestors are found, and Virginia, where they came from, were missing.

Therefore, if you don’t carry the Estes Y-DNA, but you can find your ancestral line in projects, you can potentially do two things:

  1. Identify the specific lineage to which you belong, especially if you have access to your relative’s test results, including matches and trees.
  2. Without matches, you may still be able to identify at least some haplogroup levels, such as R-BY482 or R-BY490, which opens the door to:
    • Using autosomal results to find matches with Estes-specific haplogroups
    • Using Discover to utilize the dozen+ public reports available for everyone
    • Asking people to upgrade

While I’ve been using the Estes DNA results because it’s a project I administer and the one with which I’m the most familiar, this same approach works for mitochondrial DNA as well, especially if you can identify your ancestor’s DNA in a project.

Finding Projects in Discover

The public version of Discover provides surname and project searches as well, but works a little differently.

Select Group Project and enter the term you wish to search for.

Clicking on the project takes you directly to that project’s Group Time Tree where you can identify your ancestral line.

People who have tested at FamilyTreeDNA can join projects. Many projects accept autosomal testers who descend from that family line.

To join projects, sign in, then from your home page, click on “Group Projects” in the header, and make your selection.

Search for Surnames in Family Finder Autosomal Matches

Now that you’ve identified your ancestor’s haplogroup, you can use that information to find, rule in, or rule out various people in your Family Finder match list as your ancestors’ haplogroup carriers.

FamilyTreeDNA displays the haplogroups of your autosomal matches who have taken the:

The Family Finder test doesn’t test either the Y chromosome or mitochondria fully, but it target-tests a selected number of non-autosomal haplogroup-defining locations. The haplogroups that Family Finder identifies are typically midrange, meaning they are from roughly 2,000 to 5,000 years old. Furthermore, different tests on different chips at different times didn’t always test the same locations. This relatively new Family Finder haplogroup feature is free.

Uploaded DNA tests from other vendors may or may not receive a haplogroup, but regardless, it will NOT be displayed to their matches. Not all other vendors test or include Y-DNA or mtDNA SNP locations in their upload files, and your mileage may vary widely.

My cousin David has taken the mtFull test, so his mitochondrial haplogroup is the most refined possible, but his Y-DNA haplogroup of R-L151 was derived from his Family Finder test. Haplogroup R-L151 is about 5,000 years old. If I needed his haplogroup, it’s useful to rule out other major haplogroup branches that might be found in other men by the same surname. Plus, I can learn quite a bit from Discover.

Haplogroups are displayed in your Family Finder match list for everyone who has taken a Y-DNA or mtDNA test, but currently, only Y-DNA haplogroups are provided for Family Finder results. Midrange mtDNA haplogroups are planned for sometime in the future.

There are several methods to search for either a specific surname or haplogroup within Family Finder matches.

Let’s use my Ferverda/Miller/Lentz haplogroup T2b revealed at 23andMe. That haplogroup would almost assuredly be broken down further with full-sequence testing, and it might have been renamed as a different subgroup of haplogroup T in the new Mitotree.

Let’s begin with searching for haplogroup T2b.

The search bar allows users to select Name, Ancestral Surname, mtDNA Haplogroup or Y-DNA Haplogroup.

You’ll notice that there are a total of 59 results that include T2b as a part of the haplogroup. The mitochondrial lineage I’m seeking is my mother’s paternal grandmother, so the matches should be on my mother’s side, although there is no guarantee I don’t match someone autosomally on my father’s side too.

I checked the trees of all 59 people in the T2b category, and unfortunately, none descended from the line I need.

If you change search terms or categories, be sure to clear your filters.

Under the Filter option, you can filter for several options in addition to searching.

For our next example, I’ve selected both the Big Y-500 and Big Y-700 tests, and searched for Ferverda.

I already have the Ferverda Big Y-700 haplogroup, but if I didn’t, I would now!

Don’t forget that you can sort by any number of fields, and you can download your entire match list into a csv file. I find that easier because I can search, sort and filter at will.

Don’t forget to check back from time to time as more matches are added.

Utilizing Haplogroup Projects

Under the Group Projects header, or by Googling for a haplogroup T2 (or T, or T2b, etc.) at FamilyTreeDNA, you can view the haplogroup T2 project, and filter for haplogroup T2b or any subclade.

Be sure to expand the project’s page size to display the entire project. It defaults to displaying 25 rows at a time, but you can see the number of pages at the bottom of the page. I expanded the page size to 5000 so that I can use my browser search for known surnames in the mitochondrial line.

By using my browser search and searching for each known surname by generation, I searched for Ferverda, Miller, Lentz, Ruhle, Wolflin and Heubach.

I was VERY excited for a minute when I found a Lydia Lentz listed as a tester’s EKA.

Because the female’s surname changes in every generation, there’s only one family in this lineage that Lydia Lentz could have been a member of to represent the mitochondrial DNA of Eva Miller whose mother was Margaret Elizabeth Lentz.

So, the question is whether or not Lydia Lentz is the sister of Margaret Elizabeth Lentz.

Shifting to my desktop software, it’s easy to see that Jacob Lentz and Johanna Frederica Ruhle had four Lentz daughters who lived to marry and have children. None of those daughters were named Lydia, so the Lydia Lentz EKA in the haplogroup T2 project is not representative of Eva Miller’s mother and grandmother.

Margaret Elizabeth Lentz is Eva Miller’s mother, and I had already searched within the project for Miller. I added Yost, Gallagher, and Overlease to the browser search in the haplogroup T2 project with the hope that someone might have listed a woman with one of those surnames as their EKA, but no such luck.

Not everyone joins projects, or provides their earliest known ancestors, but I didn’t find the surnames of any of the females in my known line here.

Let’s see if Ancestry can help.

At Ancestry

Ancestry doesn’t do Y-DNA or mitochondrial DNA testing, so you won’t find your ancestors’ Y-DNA or mtDNA at Ancestry, but their trees can help you find testers.

Let’s shift to Louisa Drechsel, one of the daughters in the Mehlheimer/Drechsel line we were working with earlier that needed more research.

I looked at the hints for Emma Louisa Drechsel, who was always called Louise or Aunt Lou in my family, and discovered another Ancestry member with Emma in their tree.

I clicked through to the tree to discover that the tree’s home person does not descend from Barbara matrilineally, which means they are not a candidate for Barbara’s mitochondrial DNA.

I then clicked on the tree owner’s name to see whether they happen to be an autosomal DNA match to me. They are not. Without messaging them, there’s no way to know whether they have taken a DNA test, and there’s really no point since they are not a mitochondrial DNA candidate.

While I’m at Ancestry, I’m going to check ThruLines to see if anyone who is an autosomal DNA match to me also descends matrilineally from Barbara. There are no autosomal matches shown who have our common ancestor in their tree, and who are mitochondrial candidates.

Remember, a male between the ancestor and the testing candidate always blocks the mitochondrial DNA path.

These people are all autosomal DNA matches.

There may be descendants who either aren’t DNA matches or who haven’t tested who might be mitochondrial candidates. They can be located by checking Ancestry’s trees for our common ancestors and determining how the tree owner relates to that ancestor, if they do.

Compare Trees is New

Ancestry recently introduced “Compare trees”, a new beta feature. It may not be fully rolled out to everyone yet, and because it’s in beta, the feature may change.

To access this feature, go to your tree, not their profile card.

I clicked on Barbara Mehlheimer’s link in my tree, which displays this little mini-profile. Then click on “Compare trees” at the bottom.

Ancestry displays your tree, at right, and the other tree, at left. You can select another tree to compare at top right.

Ancestry’s comparison only shows a total of three generations – the selected person, their parents, and their children.

The person I actually want to follow is Louisa, but if you click on Louisa’s card here, it simply compares the two Louisas – it doesn’t shift down a generation.

This means that to follow more recent generations, you have to go back to your tree, select someone further down in the tree and repeat the process.

This process is cumbersome, but doable thanks to the new Compare Tree function. I’ll come back to this after checking the rest of the “easier to harvest” fruit from other resources. Remember to make notes in your research journal so you don’t forget where you left off – although trees are always changing.

MyHeritage has one of my favorite tools.

At MyHeritage

Recently, MyHeritage has begun providing midrange Y-DNA haplogroups for some of their DNA testers. If you’re one of the lucky testers, you can use the free Discover tool to learn about your haplogroup, but a haplogroup alone won’t help you much with genealogy. You need matching and advanced tools for that.

Unfortunately, you can’t see the haplogroups of your matches, so you can’t search or filter using that criterion. You can, however, ask any men with the surname you’re seeking if their haplogroup is displayed.

Cousin Finder

MyHeritage has an ingenious tool called Cousin Finder that I wrote about here. Cousin Finder helps you find cousins who share common ancestors with you, regardless of whether or not you are a DNA match.

MyHeritage found 531 people in their database that share ancestors according to both their and my trees.

This list of matches doesn’t page; it scrolls, so I made a spreadsheet of the people who are relevant to my search for my brick-walled ancestor. Scrolling becomes difficult and very slow as you proceed down the list. I didn’t want to have to do this twice.

You can improve performance by using the relationship side filter. Because your ancestors match, MyHeritage knows on which “side” of your tree your common ancestor is found.

At this point, I’m interested primarily in identifying Y-DNA or mitochondrial DNA candidates for a specific ancestor.

Using the Drechsel/Mehlheimer line as our example, I’ll search on my mother’s mother’s side.

We already met Patty at WikiTree, but let’s pretend we don’t know Patty. I can click on “View her tree” to see Patty’s whole tree, or I can click on “View Relationship,” which shows how we are both related to our common ancestor.

As we know, for mitochondrial DNA, any male in the line between the ancestor and the testing candidate blocks the mitochondrial DNA path. Patty inherited her mother’s mtDNA, not her father’s.

I didn’t forget about Eva Miller Ferverda either.

I searched for cousins who descended from my mother’s father’s side to find mtDNA candidates for Eva Miller and didn’t find any. But I did find an entirely unexpected bonus.

My mother’s father’s line shows all the connections on that side. While clicking through each one, I quite serendipitously discovered a mitochondrial DNA candidate for Eva Miller’s husband’s great-grandmother, Anna Elizabeth Jonker, AND, separately, a potential Camstra Y-DNA tester too. Oh, happy day!

It was only later, while working on my genealogy for Frederica Ruhle and hoping to discover where she actually lived in Pennsylvania, that I discovered that MyHeritage has put a Cousin Finder link in each ancestor’s profile.

Who doesn’t love a pleasant surprise?!

You no longer need to sift through all of your cousins on a particular side, but remember, had I not done that, I wouldn’t have found either the mitochondrial descendant of Anna Elizabeth Jonker nor the Camstra Y-DNA candidate.

At FamilySearch

FamilySearch is more challenging and is best for fleshing out trees where not much research has been done. Remember that FamilySearch has access to records that are not available at either Ancestry or MyHeritage.

FamilySearch is a one-world tree. Like all trees, it’s subject to errors, so caution is always advised.

At FamilySearch, from your profile card in the tree, locate the ancestor whose Y-DNA or mtDNA you seek.

Then click on that person. Their profile card will pop up. Click on “Tree,” then, at the top right, select Portrait.

Now you can expand their children downward. Note that the little “two people” in the top left corner of the profile card means there are multiple spouses. The only way to view all of the children is to click on that person’s placard, then select the alternate spouse.

Living people have no placeholders on this tree.

You can contact contributors who provided information on a profile in the tree.

Click on the source provider’s name to see if they are related, and click on the little tree icon to see how.

However, once a year, there’s a great way to contact interested descendants.

Relatives at RootsTech

RootsTech is the largest genealogy conference in the world, and it’s sponsored by FamilySearch.

About six weeks before RootsTech takes place each year, and for about a month after, you can participate in Relatives at RootsTech.

During that time, you can select an ancestor and see which other people who have signed up for RootsTech also descend from that ancestor. I wrote about how to do that in the article, Relatives at RootsTech Reveals Cousins and Provides DNA Candidates. I almost always find someone who descends from an ancestor whose Y-DNA or mtDNA I need for my tree.

It’s a wonderful opportunity to meet new cousins and collaborate.

At GEDmatch

GEDmatch is an autosomal DNA upload site that offers a variety of matching and display options. While they don’t attempt to calculate a haplogroup, uploaders can enter their mtDNA and Y-DNA haplogroups, if known.

GEDmatch isn’t normally a resource we think of for either Y-DNA or mtDNA, but it can be useful under some circumstances.

In the One-To-Many limited free version and the Tier 1 subscription model, you can view haplogroups if someone has entered their haplogroup name, but you can’t filter without the Tier 1 version.

I filtered for haplogroup T2b and found one person in the match list with haplogroup T2b4. I then viewed the GEDCOM that this person has also uploaded, but they do not descend from Eva Miller Ferverda’s line.

GEDmatch isn’t built for haplogroups, but sometimes, if you have a known haplogroup that isn’t terribly common, you can catch a lucky break there.

Where AM I?

OK, so where am I in all of this?

I feel like I’ve searched the corners of the earth!

I’ve primarily used two examples.

  • My own mtDNA line which is the Drechsel/Mehlheimer line that I chose because it’s a great example that I knew well.

If I had actually been searching for a testing candidate, we would easily have eliminated several possibilities. Five female lines remained as possibilities that need additional research, plus my own test if someone were actually searching.

  • Then there was Eva Miller Ferverda (1857-1939), whose partial haplogroup, T2b, was discovered at 23andMe in three matches. I was able to reconstruct their trees, confirming that this was her line, but I was unable to find any testing candidates elsewhere.

Each of the DNA testing and genealogy vendors provides a way to communicate with other users of their platform.

  • At both 23andMe and MyHeritage, you can message through their platform.
  • At FamilyTreeDNA and GEDmatch, you can email your matches.
  • At WikiTree, you send an email through their platform to the profile card manager.
  • At FamilySearch, you cannot see placeholder cards for living people, so you need to check to see if people making changes to that ancestor’s profile are related. Then check their children closest to the present day for the same information. You can message through the FamilySearch platform.
  • During Relatives at RootsTech, you can message your cousins through their platform. The great thing about these folks is that you know they are interested and engaged, because they’ve just signed up for RootsTech.

Communicating With Testing Candidates

I’m fortunate that there are three mitochondrial descendants of Eva Miller Ferverda at 23andMe, one of whom is also at FamilyTreeDNA. I will message or email all three of them individually with a short, customized message that contains:

  • How I am related to our common ancestor.
  • A question about whether they have taken the mtFull test, or any test, at FamilyTreeDNA. If they have taken any test there, it’s easy to upgrade.
  • A sentence about how FamilyTreeDNA was the original genetic genealogy founder of this industry and the only company to offer the full mtDNA and Y-DNA tests.
  • Why they can benefit from taking the mtFull test and how it can help us learn more about our common ancestor.
  • An offer for a full-sequence mitochondrial DNA testing scholarship if they have not already taken that test.
  • I ask if they are interested and provide my email in case they have questions or want to discuss further.

Depending on how much space I have for the message, there are two articles I often provide links to in case they are unfamiliar with either Y-DNA or mtDNA testing.

  1. 4 Kinds of DNA for Genetic Genealogy is a very basic article for people who might be unaware that there is any type of DNA testing other than autosomal. This is often the case with Ancestry.
  2. The article Mitochondrial DNA A-Z: A Step-by-Step Guide to Matches, Mitotree, and mtDNA Discover is an in-depth article about using mtDNA. This is a wonderfully educational how-to article, but I always hesitate before sending this one because I don’t want their eyes to glaze over.

Scholarships

I gladly and eagerly offer scholarships for both Y-DNA and mtDNA testers from lines I need to represent my ancestors.

I equate scholarships to finding a rare out-of-print book about that exact family line, with only one or two copies still in existence, and only one accessible in a rare book shop in Podunk, Idaho. I would book a flight tomorrow at 5 AM to go and pick it up in person even if I had to eat beans and hot dogs for the next six months to pay for it. If you know me, you know I’m not kidding! I’ve gone on many wonderful road trips to meet with and collect DNA samples from cousins.

A Y-DNA or mtDNA test doesn’t cost nearly as much as that excursion and is even more reliable, because we know the DNA results are accurate – assuming the tester’s genealogy is accurate, which you should verify, and no undocumented adoptions or broken lineages have occurred.

Good luck on your treasure hunt!

____________________________________________________________

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’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

I receive a small commission when you click a vendor link in my articles and purchase that item. 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

Sixteen Unique Trees at FamilyTreeDNA: How and When to Use Each

I love all the various trees at FamilyTreeDNA – and I’m not referring just to traditional genealogy trees with people, names, and dates. I’m talking about phylogenetic or haplogroup trees – the ones you use to understand your Y-DNA and mitochondrial DNA haplogroups, origins – and more. These trees tell you ABOUT your ancestors, those people in the more traditional genealogy tree, and the combination of both is powerful.

This article introduces the various trees available at FamilyTreeDNA, when and where you’ll find them, and what they can do for you.

Haplogroup Trees

Phylogenetic, or haplogroup trees, provide a genetic path from you, or the tester, today, back in time to Y-Line Adam, or Mitochondrial Eve – the first two humans who lived AND have descendants today.

Let’s start by explaining about Y-DNA and mitochondrial DNA (mtDNA), their inheritance path, and what they mean to you.

Y-DNA

Only men have a Y-chromosome, so only biological males can test their Y-DNA.

Y-Line Adam, Y-DNA haplogroup A-PR2921, lived about 232,000 BCE, or 234,000 years ago.

Is it possible that one day someone will test whose results push that date back somewhat? Yes, of course, as we are always learning, and many testers split branches.

Today, all 711,000+ modern descendants who have tested carry the mutation named A-PR2921 as their oldest SNP (single nucleotide polymorphism), or haplogroup-defining mutation in their Y-DNA. That’s because we all descend from that one man.

If you’re a male, Y-DNA testing tells you about your direct paternal line by matching with other men who have also taken a Y-DNA test, and by revealing valuable information from before the adoption of surnames. There’s no other way to reach that far back in time.

If you’re a female, you can recruit males in your family to test.

The Big Y-700 test provides the deepest-reaching and most refined Y-DNA test available, which is essential for both genealogy and tree-building.

Mitochondrial DNA

All people have mitochondrial DNA, inherited from their mother directly through her matrilineal line – meaning her mother, her mother, her mother, and so forth – directly up your tree through all mothers.

Everyone inherits their mitochondrial DNA (mtDNA) from their mother, but only females pass it on. Both males and females in the current generation, meaning you, can (and should) test their mitochondrial DNA.

Mitochondrial Eve, mitochondrial DNA haplogroup L, lived about 141,000 BCE, or about 143,000 years ago. All 315,000 testers descend from this one woman.

Like with Y-Line Adam, one day the results of future testers may push this date further back in time. A full sequence mitochondrial DNA test, mtFull, is necessary to test all 16,569 mitochondrial locations.

Test Types

FamilyTreeDNA has been in business for more than 25 years. Technology has advanced dramatically during that time. While they continue to offer new tests and products, they strive to maintain value for their original testers.

Even though some early testers may have joined their ancestors, matching with their test results is still beneficial to us.

Present-day DNA testers can still derive value by matching the earlier, lower-level, lower-resolution tests. Not as much value as if the original tester had taken a higher-level test, but those tests may not have been available at that time.

Matches, surnames, genealogy, locations, and haplogroups provide us with valuable information. The more people who test, the larger the pool becomes, and the better our chances of discovering something that refines our understanding of our ancestors – and identifies who they are.

Before we look at the trees available, let’s take a look at where haplogroups come from. Different level tests assign different levels of haplogroups, based on how much is tested.

Let’s answer two common questions:

  1. Where can you find your haplogroup, and what does it mean?
  2. How can haplogroups be different for people who descend from the same ancestor?

Where Do Haplogroups Come From?

Since the beginning, FamilyTreeDNA has always provided their customers with haplogroup information. Haplogroups are very genealogically useful today, but initially, 25 years ago, they were only able to provide essentially continental-level origin information for your particular line. That too was useful, and helped to identify and eliminate common lineages – just not as useful as today.

Science and testing have both come a long way. Present-day testers still match with people who only tested at a lower level. You never know what you might find at that level – a match to someone who has not taken the current tests, but is still very relevant because they share your ancestor. In fact, they may be the only tester who does.

For Y-DNA testers, you’ll notice several match categories that reflect different testing levels – along with the number of matches at each level. At one time, you could purchase each one of these tests individually, then later upgrade to higher-level tests. Today, only the 37 and 111 marker tests, and the Big Y-700, which scans the entire gold-standard region of the Y chromosome, are available. Higher level tests include the lower-level tests.

Click any image to enlarge

Different types of tests provide either a predicted or a confirmed haplogroup which shows on your match list.

Without getting all sciency on you – the 12-111 marker tests test targeted STRs, or short tandem repeats, which can’t be used for haplogroup assignment and confirmation. They can and are used to compare to other testers for matching because the number of repeats, or stutters, are inherited on the Y chromosome. The Big Y test scans the Y chromosome for SNPs, single nucleotide polymorphisms, which are stable mutations that define haplogroups. I wrote about this in the article, STRs vs SNPs, Multiple DNA Personalities.

Some haplogroups are much further down the tree, or more current, than others. Your most current haplogroup, only available with the Big Y-700 test, is the best because it brings you the closest to current in time, often placing you within family branches. The Big Y-700 scans about 23 million locations on the Y chromosome, revealing both known and unknown mutations, not just a few markers, making it the most refined and relevant test genealogically.

Each higher-level test includes the lower-level tests. You can see what tests your matches have taken by looking beneath their names on your match list. In this case, these Estes men who match my cousin have taken the Family Finder (or uploaded an autosomal transfer), and taken the mtFull test. One match initially took the Big Y-500 but has since upgraded to the Big Y-700, and the other originally tested at the 111 marker level, and has since upgraded as well.

The Big Y-700 includes all lower-level tests, such as the Big Y-500 (now obsolete), the 111, 67, 37, 25, and 12 marker STR tests. You still match with people who only tested at those levels, plus everyone else who ordered a more refined test.

The haplogroup you receive is more or less refined, based on the test level you take.

Y-DNA Test Type Haplogroup Provided Relevance Upgradable
Y-DNA STR 12-111 marker tests (only 37 and 111 are available today – the rest are obsolete) Predicted based on STRs – very reliable at the level predicted Predicted (not confirmed) haplogroup that was generally formed a couple thousand years ago, or earlier Yes, if enough quality DNA remains. Only 37, 111, and the Big Y-700 tests are available today. Recommend the upgrade to Big Y-700.
Individual SNP test (now obsolete) Confirms a predicted haplogroup or tests a single SNP to confirm a closer haplogroup Relevant at the level tested – either positive or negative result was reported Individual SNP tests have now been replaced by Big Y-700, which covers all individual SNPs that were available to test, plus much more.
Big Y-500 test (now obsolete) Confirmed haplogroup within range of that test’s ability, replaced by much more granular Big Y-700 Big Y-700 is more refined and moves the tester towards more current haplogroups, so more genealogically significant Yes, upgrade to Big Y-700 if enough DNA remains, or tester can re-swab
Big Y-700 – scans the entire gold-standard region of the Y chromosome – approximately 23 million base pairs Top-of-the-line SNP-confirmed test, most granular and refined. Scans for known and previously unknown mutations. Extremely accurate. Generally advances the tester into a genealogical timeframe, and often divides testers into multiple lineages descended from a known common ancestor No more advanced test is available.
Family Finder autosomal test or transfer Confirmed to mid-range level if possible. Not all transfer files have Y-DNA or mtDNA SNPs so you get what you get. Useful in autosomal matching for locating people you may be related to you with that surname. Ask the match if they are willing to take a Y-DNA test, if relevant, or sponsor a testing scholarship for them.

Family Finder haplogroups are relatively new at FamilyTreeDNA. Each chip level that FamilyTreeDNA has used for testing over the years, and the chips that other vendors have used, contain different SNPs (or none at all on the Ancestry test) that can be measured for some level of haplogroup. Other vendors generally don’t quality-control for either Y-DNA or mtDNA SNPs because they don’t use them. This is a “you get what you get” freebie.

That said, most Family Finder haplogroups are closer in time, or “better” than the predicted R-M269, the most common haplogroup in Europe, often reported with STR testing.

Not everyone with a transfer kit receives a haplogroup. Due to quality and reliability issues, you cannot see haplogroups on your autosomal match list for those who only have a haplogroup through an autosomal transfer.

Using our male Estes testers as an example, we find the following haplogroup results at the various testing levels:

Haplogroup Haplogroup Formation Date Ancestor or Haplogroup Formation Location Haplogroup Source
R-M269 4450 BCE (6450 years ago) Between Ukraine and Kazakhstan, north of the Black and Caspian Seas Predicted from 12-111 STR marker tests
R-BY487 700 CE (1300 years ago) UK, Scotland/England Family Finder DNA SNP Confirmed
R-BY482 1550 CE Robert Eastye b 1555 Ringwould, Kent, England Big Y-700
R-BY490 1700 CE Silvester Eastye b 1596 Kent, England Big Y-700
R-ZS3700 1750 CE Moses Estes 1711 VA Big Y-700
R-BY154784 1850 CE Joseph Estes b c 1790 VA or TN Big Y-700

All of these are valid and accurate haplogroups – some are just closer in time and much more useful than others. All of these men have R-M269, because it is a parent haplogroup of all of those downstream haplogroups. The Big-Y tested men beginning with R-BY482 don’t share the haplogroups below them, because they don’t have those mutations that are downstream on the tree. However, the men at the bottom with R-BY154784 have all of the SNPs above them.

Note that all haplogroup formation dates are ranges. I’m showing the midpoint here.

When upgrading, if the original tester is deceased, select the highest-level test available, as there may not be enough DNA to run more than one test. When I offer scholarships now, I always just offer the Big Y-700 test to avoid future issues.

If the tester you need is no longer available, consider the possibility that other people, family members perhaps, might be available to test to represent this same line.

Next, let’s look at mitochondrial test levels and haplogroups.

Mitochondrial DNA Test Type Haplogroup Provided Relevance Upgradable
HVR1 & HVR2 tests (no longer available) Predicted based on around 1000 markers – very reliable at the level predicted Predicted haplogroup, not confirmed, generally formed a couple thousand years ago or earlier Yes, if enough quality DNA remains. Only the mtFull test is available today.
mtFull, full sequence test Tests all 16,569 SNP locations in the entire mitochondria. Most granular and refined. Extremely accurate. Often brings tester into genealogical timeframe, especially with the new Mitotree. Divides testers into multiple haplotype lineages, sometimes descended from known common ancestor. No upgrade needed to receive new Mitotree and mtDNA Discover benefits.
Family Finder autosomal test or transfer Coming soon. Will be the same criteria and caveats as Y-DNA SNPs. May be able to find a similar or upstream haplogroup that might point to a common ancestor. Ask autosomal match if they are willing to take a mtFull test, if relevant, or sponsor a scholarship for them.

Ok, now that we understand more about haplogroups, how they are determined, and where yours came from, let’s look at all of the trees at FamilyTreeDNA.

Trees Within Your Y-DNA and Mitochondrial DNA Account

Let’s start with trees found within your personal account, so sign in.

Each tree has a different purpose and unique benefits.

Tree #1 – Your Matches Genealogy Trees

Each of your matches may have provided links to genealogical trees. They may show trees in multiple places too; at MyHeritage, an archived tree at FamilyTreeDNA, and a WikiTree link. I makes notes about their trees in the comments field, and I also keep a spreadsheet to look for commonalities.

Tree #2 – Haplogroups and SNPs for Y-DNA Testers

Next, for Y-DNA testers, click on the Y-DNA Results and Tools.

You’ll see the Haplotree & SNPs tile on the dashboard.

The Haplotree and SNPs link takes you to a phylogenetic tree that defaults to your haplogroup, where you can view:

  • Variants – SNP mutations that define your haplogroup
  • Surnames with this haplogroup – so long as there are multiple public testers
  • Countries – self-reported for earliest known ancestors (EKA)
  • Recommended Projects – haplogroup projects only – others such as surname projects are found in Discover under Suggested Projects

Tree #3 – The Block Tree for Big Y Testers

People who have taken the Big Y-700 test have a separate section that includes tools for the Big-Y test that aren’t relevant for the 12-111 STR marker tests.

Big Y testers will see the Block Tree tile on their dashboard.

The block tree is an alternative way of displaying matches on a phylogenetic tree. While the Discover Time Tree is viewed left to right, this tree is displayed top to bottom, with each mutation being represented by one grey bar on the scale at left. Each mutation corresponds to approximately 100 years, which is a rough average for the frequency of Y-chromosomal mutations.

People with 30 mutations or fewer are shown as matches, with the goal of reaching back about 1500 years.

Each large block shows the mutation for which the haplogroup is named, such as R-BY482, at the top. The mutations, known as variants, shown below that haplogroup name, are found in the results of each person in that haplogroup, but in the future, people without those mutations, or with additional mutations, will form a new branching haplogroup.

The green “Private Variants” at the bottom of the branches display the average number of mutations of people within that group awaiting another tester to have the same mutations, so a new branch can be formed. I view Private Mutations as “haplogroups in waiting.”

Discover

In addition to the haplogroup trees shown in your account at FamilyTreeDNA, there are several additional trees in Discover for both Y-DNA and mitochondrial DNA. Discover, updated weekly, is a suite of tools for both Y-DNA and mitochondrial DNA that, cumulatively, provides a book about your haplogroup results.

Discover comes in two flavors:

  • The publicly available free version with limited functionality
  • Your private version with expanded functionality available from within your account

You can access Discover, here if you’d like to follow along.

Discover is a publicly available free tool introduced in the fall of 2023 that provides more than a dozen reports, enabling a deeper understanding of all haplogroups.

Just select Y-DNA or mtDNA and enter your haplogroup of choice.

Think of these menu choices, in the sidebar, as chapters in your personal book. Every chapter has something interesting to tell you. Please read them – don’t just scan.

In addition to the free version, if you have taken a Big-Y or mitochondrial DNA full sequence test at FamilyTreeDNA, you’ll have additional information available.

For mitochondrial DNA results, just click on the pink Discover tile.

For Y-DNA results, click on the blue Discover tile.

Within Discover, you’ll find three distinct trees.

Trees #4 and #5 – Y-DNA and Mitochondrial DNA Time Trees

The Time Tree shows your Y-DNA or mitochondrial DNA haplogroup displayed on a timeline, along with:

  • A self-reported ancestral country indicator for every person’s DNA in that haplogroup
  • Haplotype groupings indicating exact matches between everyone in that haplotype.

A haplotype is a grouping of people whose DNA matches exactly, including unstable or hypervariable locations too unreliable to use for haplogroup formation. However, those mutations may be relevant for genealogical matching.

I wrote about haplogroups and haplotypes here and here.

Tree #6 and #7 – Y-DNA and Mitochondrial DNA Class Tree View

The Classic Tree is available for both Y-DNA and mitochondrial DNA.

On the Classic Mitotree View, you can display and filter the tree, including haplotypes, in seven ways, as shown in the dropdown “Display Options.”

Tree #8 and #9 – Y-DNA and Mitochondrial DNA Tree Branch Comparison

Have you ever seen two haplogroups and wondered how closely they are related? Compare provides that answer.

Here, I’m comparing my haplogroup to that of a family member. Everyone is related, but how long ago are we related on our matrilineal lines?

Haplogroup J1c2f compared with haplogroup V216a shows that our common ancestor lived a VERY long time ago – about 55,000 years in the past, someplace in the fertile crescent.

For either Y-DNA or mitochondrial DNA, you can compare two haplogroups. This provides specific information about those two branches of the tree, and where they intersect. To view more about the common ancestor, just pop R+10398 into Discover and learn more about when and where that ancestor lived.

Trees #10 and #11 – Match Time Trees

Match Time Trees are one of the most useful Discover features.

In addition to the Time Trees and Classic Trees provided for everyone in Discover, test takers will also have a Match Time Tree that shows all of your matches, organized genetically.

For mtFull testers, your matches are organized by haplotype cluster. People in your haplotype cluster are your exact matches.

I have over 100 full sequence matches, so I’m only showing the first few in this screenshot. In addition to the match’s name, their EKA (earliest known ancestor) is shown, if provided.

On the Y-DNA Match Time Tree, links are provided to genealogical trees of the tester, which could be an archived FamilyTreeDNA tree, a MyHeritage tree, WikiTree, or some combination.

You can actually see your matches’ WikiTree tree on your Match Time Tree by enabling another feature.

Trees #12 and #13 – WikiTree Tree Integration

While you’re still on the Match Time Tree page for either Y-DNA or mitochondrial DNA, click on Display Options, above the Time Tree, and enable WikiTree Connections. Unfortunately, the default for this great feature is “off.”

I’ve enabled “Share Mode” at the top to obfuscate the names of the testers, and I’ve adjusted the vertical spacing so you can see more in my examples. You’ll notice the grey lines with dots inside circles. I think of these as beads or maybe knots on a rope, but they actually represent a line of ancestors.

Each tester with one of those grey dot bars has connected themselves to their ancestors at WikiTree, a public one-world tree. Living people are not shown, hence the dash marks to the immediate left of the tester’s name.

By mousing over any of the dots, aka ancestors, you can view information about this ancestor of this Estes tester at WikiTree. Ancestors appear in genealogical order in their relevant place on the Time Tree. How cool is that!!!

WikiTree, like any tree, public or private, can have errors. Always verify any tree using original source documents.

As far as I’m concerned, the Match Time Tree is one of the very best features of both Y-DNA and mitochondrial DNA testing and matching. There are so many options to select from, so take some time to look around.

Your Personal Version of Discover is Best

Y-DNA Discover and mtDNA Discover can both be useful for any level of haplogroup, but the best results are obtained when clicking through from the tester’s FamilyTreeDNA account. Big Y and full sequence mitochondrial DNA customers receive additional information, not available in the free, public version of Discover, including

  • The Match Time Tree
    • Including WikiTree integration
  • Globetrekker™ (Y-DNA, mtDNA coming eventually)
  • Up to 30 Ancient Connections, as compared to 3 in the free version
  • Up to 30 Notable Connections, as compared to 3 in the free version

 

Tree #14 – Group Time Trees

I absolutely love Group Time Trees. They are similar to Match Time Trees, but unlike Match Time Trees, are publicly viewable for Group Projects if the volunteer project administrators have enabled this feature for the project.

There are two ways to access Group Time Trees – through publicly accessible Discover or directly through any project.

In Discover, select Group Project in the dropdown.

Then type the name of the surname project you’re seeking. You’ll be presented with a menu if the surname you’ve entered is found in multiple projects, or administrators have listed it as “of interest” in their project.

I clicked on the Estes project.

Viewing the Estes DNA Project, under DNA Results, you can see the various options.

Selecting Y-DNA Results Overview displays the project results by administrator-defined group. The teal groups all descend through Abraham Estes through various sons.

However, by clicking the Group Time Tree instead, you can view all these testers and their results in a Match Time Tree format, arranged genetically.

Clicking on the Group Time Tree link takes you to the Group Time Tree for this project. A menu is displayed at left, based on how the administrator has grouped the project.

I’ve selected several groups that I know descend from the original Estes ancestor from Kent, England. Testers who have joined the Estes project and granted permission for their results to be displayed publicly are automatically grouped genetically, at right, with their surname and EKA (earliest known ancestor), assuming they have entered that information.

Earliest Known Ancestors (EKA)

You’ve probably noticed that earliest known ancestors, along with their locations, are used in many places.

Please enter both your direct paternal (father, father, to father’s line) and direct matrilineal (mother, mother, to mother’s line) earliest known ancestors, along with their locations. I wrote about how to do that in “Earliest Known Ancestors” at FamilyTreeDNA in 3 Easy Steps, here.

Trees #15 and #16 – Public Trees

In addition to trees within testers’ accounts, Discover trees, Group Time Trees, and WikiTree tree integration, FamilyTreeDNA provides two additional public trees.

FamilyTreeDNA made the Y-DNA and mitochondrial DNA haplogroup trees freely available years ago, at the bottom of their main company public page – without signing in.

These trees are still actively maintained today and are free for everyone to use.

To find these trees, scroll all the way to the very bottom of the page, in the footer, to the Community section. Yes, I know, it’s a bit like a scavenger hunt!

You can select to view either the Y-DNA or mtDNA tree. I love this tree, because it shows how many SNP-confirmed people have been tested. That number does not include the thousands of academic and public samples that may be utilized to help define haplogroups, and that you’ll sometimes see in your Ancient and Notable Connections.

So, if you receive a new haplogroup, but you don’t see a new match on your list or on the Block Tree, it’s probably because you match a high-quality academic sample.

The trees display from the root, meaning the oldest haplogroup is shown at the top. In the Y-DNA tree, above, haplogroup A-PR2921 is “Y-Adam”.

You can select any haplogroup on the bar across the top, search by country, or select a specific branch name to view.

The tree itself is viewable by country, as shown above, or by variant, meaning the haplogroup-defining mutations, shown below.

Additionally, for the Y-DNA tree, you can choose to display by surname, so long as there are two or more testers with that identically spelled surname who share this haplogroup and who have given permission for public display.

Please note that these people are all SNP-tested and confirmed at the level reported, but they are NOT all Big-Y testers.

This feature alone can be genealogy-changing because they may be surnames associated with your ancestors in records, or they may just be neighbors. Or maybe you thought they were “just neighbors,” but they are actually related.

At one time, customers could order an individual SNP test for R-M269 to confirm their predicted haplogroup. That test is no longer available, but anyone who took that test to confirm R-M269 and never tested or received results (like Family Finder) at a more granular level will be reported at R-M269. Note that 687 is the number of distinct surnames shown, not the total number of testers.

The three “hamburger dots” on the right side provide options for a user-reported Country Report based on the location of their earliest known ancestor, and a Surname Report. The surname report for R-M269 shows a total of 2448 testers who share those 687 surnames.

It’s a Whole Forest

Who knew there were 16 unique trees available at FamilyTreeDNA!

Each tree has a unique purpose and provides information not available elsewhere.

Take a look and see what kind of information is waiting for you – and don’t forget to check back often.

_____________________________________________________________

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’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

I receive a small commission when you click a vendor link in my articles and purchase that item. 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

RootsTech 2026 – The Wind Beneath Our Wings

I started writing this article on Sunday evening, the day after RootsTech ended, and I’m basking in the afterglow. Also, my back and feet may never forgive me.

As a tongue-in-cheek comment, I think someone coined the word “exhausterwhelmulated” and defined it as being exhausted, overwhelmed, and overstimulated all at once. Yep, that’s me.

However, I need to add another couple of words to this – gratitude and joy.

Gratitude and Joy

I’m going to try to express this without sounding too sappy.

Do you recall the joy you used to feel when you spotted a relative you loved dearly but didn’t get to see often? Think of the unbridled joy as you piled out of your parents’ car and spotted your grandmother coming out of the door because she saw the car pull up. You ran as fast as your little legs could carry you directly into her arms, and got hugged so tightly it nearly squeezed the breath out of you.

I don’t know what the word for that would be, but it’s similar to how RootsTech feels.

Let me explain. Continue reading →

2025 Genetic Genealogy Retrospective: Wow – What a Year!

2025 has been quite a year in genetic genealogy. Genetic genealogy, per se, really isn’t a separate “thing” anymore. DNA testing is now an integral part of genealogy, with the potential to answer questions that nothing else can!

The 76 articles I wrote in 2025 fall into multiple categories and focus on different topics based on what was happening in the industry.

From my perspective, here are the most notable announcements and trends in genetic genealogy, and genealogy more broadly.

#1 for 2025 – Mitochondrial DNA: The Million Mito Project Released the New Mitotree, Updates, and mtDNA Discover

The biggest genealogy news items this year, both industry-wide and genealogy-changing are definitely the release of the new Mitotree, plus two tree updates. But that’s not all.

In addition, full sequence mitochondrial DNA testers received new Mitotree haplogroups, if appropriate, and everyone received a haplotype – a new feature. Along with Mitotree, FamilyTreeDNA introduced mtDNA Discover which provides 13 individual reports based on your haplogroup and matches.

It’s no wonder that mitochondrial DNA articles led the pack with the most views based on the eleven articles about that topic. If you haven’t yet tested your mitochondrial DNA at FamilyTreeDNA, there’s no better time! You never know what you’re going to discover and the more testers, the more matches for everyone.

You don’t know what you don’t know, and you’ll never know if you don’t test. Remember, mitochondrial DNA is for both males and females and tests your mother’s direct matrilineal line (mother to mother to mother, etc.) – reaching beyond known surnames.  Click here to order or upgrade.

#2 – MyHeritage Low Pass Whole Genome Sequence Test Charges into the Future

Another big hitter is the new MyHeritage low-pass whole genome test (WGS) test. It’s new and innovative, but we haven’t seen comparative results yet.

My results from the new low-pass whole genome test just came back, and I haven’t had the opportunity to review them yet, as compared to the earlier tests. That said, I do have roughly the same number of matches, but I need to determine if they are the same matches, and how well they track. I’ll be working on that review soon.

The new whole genome test may be more about future proofing and preparedness than additional current benefit – but we will see. I definately wanted to take the whole genome test so I can receive and benefit from whatever new is coming down the pike.

MyHeritage allows you to maintain multiple DNA tests on your account, so the new whole genome won’t “replace” your older or uploaded test. That way, you can easily compare the results of the whole genome against any DNA test that you curently have at MyHeritage.

Click here to order the new test.

#3 – 23andMe Experiences Problems

On a less positive note, but still quite newsworthy is the bankruptcy of 23andMe and subsequent repurchase of 23andMe by the original founder after setting up a new nonprofit. I have real mixed feelings about this topic. However, 23andMe was really never about genealogy, and now, matching segment information is no longer available. Those searching for unknown parents or family may want to test there if they are unsuccessful elsewhere.

Best Genealogy Tool

The FamilySearch full text search continues to have a HUGE impact for genealogists. This tool is not one-and-done, but provides increasing amounts of rich information as more records are added to the “fully scanned” collection. If you haven’t tried it, please do. It’s a game-changer and continues to improve.

A Cautionary Word About AI – Artificial Intelligence

AI is such a hot topic right now that I feel it needs to be included.

The FamilySearch full text search uses a form of AI. However, you’ll quickly notice that it can’t read everything, gets words and names wrong, and if you actually need to fully depend on it for accuracy, you cannot. (That said, it’s still an amazing tool, and I’m not picking on FamilySearch.)

Aside from FamilySearch, AI in its current form is both wonderful and terrible. I’ll be writing about AI in the new year, but for now, don’t ever rely on AI for anything that you can’t verity. It’s your assistant, not an expert, no matter how insistent it is. Never trust and always verify.

This is ESPECIALLY TRUE WHEN RELATED TO GENETICS and genetic related topics. I can’t even begin to tell you how very wrong it has been, and how much people fall in love with inaccurate results. No, just no – at least for now.

You need to know your AI tool, your skill set, your understanding of AI broadly, the tool’s limitations, and yours, and that’s all before verifying the actual AI results. If you want to educate yourself, and everyone should, treat yourself to anything, anyplace by either Mark Thompson or Steve Little, the dynamic AI duo. They offer YouTube videos and classes in a wide variety of places – but keep in mind that AI tools and technology literally change every few weeks.

AI is, indeed, a specialty all unto itself, much like genetic genealogy. And right now, it’s not soup yet, but it is cooking.

Tried and True Genetic Genealogy Staples – DNAPrint and Genetic Affairs

I haven’t written about either one this year, but I use both DNAPainter and Genetic Affairs regularly.

I consistently paint segments from matches at both MyHeritage, FamilyTreeDNA, and GEDmatch that are newly identified to an ancestor or ancestral couple at DNAPainter.

Unfortunately, neither Ancestry nor 23andMe provide matching cM location information for your matches (chromosome browser), but you may find some people who have tested at those companies at both FamilyTreeDNA and GEDmatch if they have uploaded to either of those vendors. Both vendors provide segment information and a Chromosome Browser, enabling you to paint that information to DNAPainter when you can identify your common ancestor.

MyHeritage also provides a Chromosome Browser, but unfortunately, no longer accepts uploads from any other vendor. You can paint segments from MyHeritage, but no longer upload DNA files to MyHeritage.

Thanks to DNAPainter, I have 90% of my segments identified to specific ancestors – which is actually rather remarkable given that my mother’s grandfather was a Dutch immigrant, and her great-grandparents on her other side were German immigrants, meaning we don’t have many matches on either of those lines.

Genetic Affairs continues to develop new, advanced clustering tools, one of which I’ll be reviewing soon.

Major Vendor Releases

Aside from what’s listed above, most of the major vendors released new features.

MyHeritage released a VERY COOL new tool called Cousin Finder that finds your relatives in the MyHeritage database, whether they match you on a DNA test, or not. They may not have even taken a DNA test. Cousin Finder identifies your common ancestor and shows your relationships. It’s a wonderful way to initiate communications, discuss your common ancestors, and ask about DNA testing.

Of my 378 Cousin Finder matches, only 23 (about 6%) are on my DNA match list, so that leaves 355 people to message, several of whom represent Y-DNA and mtDNA lines I don’t have. You can bet I’ll be offering testing scholarships.

Additionally, MyHeritage released a new ethnicity version.

FamilyTreeDNA, in addition to the new Mitotree, Discover, and associated features, released a new match matrix so you can see if and how selected matches are related to each other in a grid format. In other words, you can create your own cluster.

A new built-in “Share” feature blurs private information to make sharing easier both on the website and in Discover.

Discover improvements include thousands of new Y-DNA and mtDNA tree branches, plus thousands of new Ancient DNA samples. Discover is evergreen, so once you’ve taken that Big Y-700 test or the mitochondrial DNA test, your learning never stops as more content is added.

Tree integration with WikiTree is super-easy and means you don’t have to choose between trees. You can choose to retain your archived tree at FamilyTreeDNA, or move your tree to MyHeritage, PLUS link yourself to your family at WikiTree.

Ancestry released match clustering and a new beta pedigree view of ThruLines, but that’s back in the shop for more work. I’d expect to see it rereleased in 2026.

Conferences

RootsTech is the granddaddy of genealogy conferences, and it’s always fun to attend and write about the experience. Many vendors release new tools or products during the conference.

The ECGGC (East Coast Genetic Genealogy Conference), held in the fall, is the only conference that focuses entirely on genetic genealogy, new tools, how to use existing tools, and more. The 2025 conference was virtual and provided a great deal of focused content. Attendees particularly appreciate the deep dive in a particular topic presented in DNA Academy.

I’ll be at RootsTech in 2026, will write about that soon, and hope to see you there.

Concepts, Techniques and Plain Old Genealogy

In the past, my Concepts series and genealogy “how to” articles have been very popular, so, in 2025, I penned a half-dozen articles focusing on frequently asked questions about relationships and DNA.

For example, how does one go about finding DNA testing candidates? The number of options may surprise you and includes both Cousin Finder and Relatives at RootsTech.

By testing ONE PERSON for either Y-DNA or mitochondrial DNA that represents an ancestor, you actually receive information about that entire lineage of ancestors. So, on my Estes line, by locating an Estes male from my line to test, I received relevant information for every Estes male in my line, back to and beyond the progenitor.

Eventually, we hit a brick wall in every line, and those tools are the perfect way to break through those brick walls.

Other articles discuss things like how to use Discover’s Ancient Connections, and the difference between half and full relationships, both in your tree and genetically. Plus, what does a cousin “once removed” mean anyway? And why do I care?

Another question I receive is how far back, based on the shared amount of DNA, should I look in my matches’ trees for our common ancestor? In other words, how many generations back should I click? That article was fun and produced some unexpected results.

Memorial Articles

Because we are part of a community, I write memorial articles when one of our friends passes on. This year, sadly, Schelly Talalay Dardashti, well-known Jewish genealogist, and another very close friend joined the ancestors, so I’ve recognized the best in both of their lives which constitutes their legacy.

Be the Storyteller

Last, but not least, I wrote about my ancestors in the “52 Ancestors” series, which launched several years ago with Amy Johnson Crow’s challenge to write about one ancestor per week. She hosts this every year, and you can join (free) now.

I’m now on ancestor #467, so yes, it’s addictive, but it’s also AMAZING how many wonderful cousins I’ve met who have information that I did not. Not only that, but after publishing about an ancestor, I’ve discovered that I’m related to people I’ve known for years. We were SOOOooo excited!

I’ve been writing about the lives of my ancestors for several years now, and the articles include attempts to identify Y-DNA and mtDNA testers for each ancestor, where appropriate. There’s so much to learn that can’t be revealed any other way.

Plus, people seem to like the “mystery” and “short story” aspect, and I salt each story with the history of the region and relevant historical events of the timeframe. You might find your ancestors here too, or other helpful information.

Find a way to share about your ancestors!

Do You Have Suggestions for 2026 Topics?

Do you have suggestions or requests for article topics in 2026? If so, please comment on this article and let me know.

Check Out the 2025 List

Here’s the list of the 2025 articles. Did you miss something fun? Enjoy!

  Title Category Date Link
1 Welcome to 2025 – Opportunities and New Genetic Genealogy Articles Welcome, general 1-2-2025 https://dna-explained.com/2025/01/02/welcome-to-2025-opportunities-and-new-genetic-genealogy-articles/
2 Anne Doucet (1713-1791), Oceans, Rivers, and Perseverance – 52 Ancestors #438 52 Ancestors 1-4-2025 https://dna-explained.com/2025/01/04/anne-doucet-1713-1791-oceans-rivers-and-perseverance-52-ancestors-438/
3 Register for RootsTech 2025 Now RootsTech 1-16-2025 https://dna-explained.com/2025/01/16/register-for-rootstech-2025-now/
4 What IS the McNeil Family History, by George Franklin McNeil – 52 Ancestors #439 52 Ancestors 1-19-2025 https://dna-explained.com/2025/01/20/what-is-the-mcneil-family-history-by-george-franklin-mcneil-52-ancestors-439/
5 Jean Garceau dit Tranchemontagne (c1785-1711), Soldier from Saint Marseault – 52 Ancestors #440 52 Ancestors 1-29-2025 https://dna-explained.com/2025/01/29/jean-garceau-dit-tranchemontagne-c1785-1711-soldier-from-saint-marseault-52-ancestors-440/
6 Memories Resurface When the Old Family Home Gets a Facelift Genealogy 2-3-2025 https://dna-explained.com/2025/02/03/memories-resurface-when-the-old-family-home-gets-a-facelift/
7 MyHeritage Introduces Ethnicity v2.5 MyHeritage 2-6-2025 https://dna-explained.com/2025/02/06/myheritage-introduces-ethnicity-v2-5/
8 Relatives at RootsTech Reveals Cousins and Provides DNA Candidates RootsTech, techniques 2-8-2025 https://dna-explained.com/2025/02/08/relatives-at-rootstech-reveals-cousins-and-provides-dna-candidates/
9 FamilyTreeDNA’s New Matrix Shows How Your Matches Are Related to Each Other FamilyTreeDNA 2-12-2025 https://dna-explained.com/2025/02/12/familytreednas-new-matrix-shows-how-your-matches-are-related-to-each-other/
10 René Doucet (c1680-c1731), Lifetime of Incessant Upheaval – 52 Ancestors #441 52 Ancestors 2-15-2024 https://dna-explained.com/2025/02/16/rene-doucet-c1680-c1731-lifetime-of-incessant-upheaval-52-ancestors-441/
11 Lineages Versus Ancestors – How to Find and Leverage Yours Techniques 2-23-2025 https://dna-explained.com/2025/02/23/lineages-versus-ancestors-how-to-find-and-leverage-yours/
12 Mitotree is Born Mitochondrial DNA 2-25-2025 https://dna-explained.com/2025/02/25/mitotree-is-born/
13 RootsTech 2025 – The Year of Discover and the New Mitotree RootsTech, Mitochondrial DNA 3-14-2025 https://dna-explained.com/2025/03/15/rootstech-2025-the-year-of-discover-and-the-new-mitotree/
14 Pierre Doucet (c1621-1713), Walking History Book Lived to Nearly 100 – 52 Ancestors #442 3-16-2025 https://dna-explained.com/2025/03/16/pierre-doucet-c1621-1713-walking-history-book-lived-to-nearly-!100-52-ancestors-442/
15 Welcome to the New FamilyTreeDNA mtDNA Group Mitochondrial DNA 3-17-2025 https://dna-explained.com/2025/03/17/welcome-to-the-new-familytreedna-mtdna-group/
16 23andMe Files for Bankruptcy – What You Need to Know! 23andMe 3-24-2025 https://dna-explained.com/2025/03/25/23andme-files-for-bankruptcy-what-you-need-to-know/
17 New “Share” Features at FamilyTreeDNA Blur Match Information and Make Sharing Easy FamilyTreeDNA 4-1-2025 https://dna-explained.com/2025/04/01/new-share-features-at-familytreedna-blur-match-information-and-make-sharing-easy/
18 The Chauvet Cave: Trip Back in Time with Prehistoric European Humans – Are We Related? History, DNA 4-6-2025 https://dna-explained.com/2025/04/06/the-chauvet-cave-trip-back-in-time-with-prehistoric-european-humans-are-we-related/
19 DNA for Native American Genealogy Webinar & Companion Book Native American 4-8-2025 https://dna-explained.com/2025/04/08/dna-for-native-american-genealogy-webinar-companion-book/
20 Marie Levron (c1686-1727), Tragedy from Cradle to Grave – 52 Ancestors #443 52 Ancestors 4-14-2025 https://dna-explained.com/2025/04/14/marie-levron-c1686-1727-tragedy-from-cradle-to-grave-52-ancestors-443/
21 Mitochondrial DNA: What is a Haplotype Cluster and How Do I Find and Use Mine Mitochondrial DNA 4-14-2025 https://dna-explained.com/2025/04/14/mitochondrial-dna-what-is-a-haplotype-cluster-and-how-do-i-find-and-use-mine/
22 New Mitotree Haplogroups and How to Utilize Them for Genealogy Mitochondrial DNA 4-23-2025 https://dna-explained.com/2025/04/23/new-mitotree-haplogroups-and-how-to-utilize-them-for-genealogy/
23 Sir Francois Levron dit Nantois(c1651-1714), and Acadia’s Pirate – 52 Ancestors #444 52 Ancestors 4-26-2025 https://dna-explained.com/2025/04/27/sir-francois-levron-dit-nantois-c1651-1714-and-acadias-pirate-52-ancestors-444/
24 Catherine Savoie (c1661-c1722/25), Whispered Threads Weave a Tapestry of Life – 52 Ancestors #445 52 Ancestors 5-4-2025 https://dna-explained.com/2025/05/04/catherine-savoie-c1661-c1722-5-whispered-threads-weave-a-tapestry-of-life-52-ancestors-445/
25 Discover’s Ancient Connections – How Are You Related? Discover, Ancient DNA 5-8-2025 https://dna-explained.com/2025/05/08/discovers-ancient-connections-how-are-you-related/
26 Mother’s Day and Legacies 52 Ancestors, Genealogy 5-10-2025 https://dna-explained.com/2025/05/11/mothers-day-and-legacies/
27 The Mystery of the Blue Fugates and Smiths: A Study in Blue Genes and Pedigree Collapse Genetics, Genealogy 5-18-1015 https://dna-explained.com/2025/05/19/the-mystery-of-the-blue-fugates-and-smiths-a-study-in-blue-genes-and-pedigree-collapse/
28 Regeneron Wins Bid for Bankrupt 23andMe – Wedding Planned 23andMe 5-19-2023 https://dna-explained.com/2025/05/19/regeneron-wins-bid-for-bankrupt-23andme-wedding-planned/
29 Francois Savoie’s Homestead Rediscovered – 52 Ancestors #446 52 Ancestors 5-24-2025 https://dna-explained.com/2025/05/24/francois-savoies-homestead-rediscovered-52-ancestors-446/
30 Memorial Day – Some Gave All Memorial 5-25-2025 https://dna-explained.com/2025/05/25/memorial-day-some-gave-all/
31 Mitotree Webinar – What It Is, How We Did It, and What Mitotree Means to You Mitochondrial DNA 6-4-2025 https://dna-explained.com/2025/06/04/mitotree-webinar-what-it-is-how-we-did-it-and-what-mitotree-means-to-you/
32 Catherine LeJeune (c1633-1671/1686), Meet Your Grandchildren – 52 Ancestors #447 52 Ancestors 6-7-2025 https://dna-explained.com/2025/06/07/catherine-lejeune-c1633-1671-1686-meet-your-grandchildren-52-ancestors-447/
33 Mitotree Q&A for Everyone Mitochondrial DNA 6-11-2025 https://dna-explained.com/2025/06/11/mitotree-qa-for-everyone/
34 Father’s Day: Bravery and Love 52 Ancestors, Genealogy 6-14-2025 https://dna-explained.com/2025/06/14/fathers-day-bravery-and-love/
35 Francoise Bourgeois (c1659-1693/1697), High Drama in Beaubassin and Terror at Port Royal – 52 Ancestors #448 52 Ancestors 6-16-2025 https://dna-explained.com/2025/06/16/francoise-bourgeois-c1659-1693-97-high-drama-in-beaubassin-and-terror-at-port-royal-52-ancestors-448/
36 Requesting Suggestions for RootsTech 2026 Topics RootsTech 6-18-2025 https://dna-explained.com/2025/06/18/requesting-suggestions-for-rootstech-2026-topics/
37 FamilyTreeDNA and WikiTree Collaboration – In Two Easy Steps!! FamilyTreeDNA, WikiTree 6-25-2025 https://dna-explained.com/2025/06/25/familytreedna-and-wikitree-collaboration-in-two-easy-steps/
38 Jacques Bourgeois (c1620-c1700), Surgeon of Port Royal – 52 Ancestors #449 52 Ancestors 7-1-2025 https://dna-explained.com/2025/07/01/jacques-bourgeois-c1620-c1700-surgeon-of-port-royal-52-ancestors-449/
39 TTAM, a Nonprofit Formed by 23andMe’s Founder Now Plans to Buy 23andMe 23andMe 7-1-2025 https://dna-explained.com/2025/07/01/ttam-a-nonprofit-formed-by-23andmes-founder-now-plans-to-buy-23andme/
40 Jacques Bourgeois: Complex Acadian, Founder of Beaubassin – 52 Ancestors #450 52 Ancestors 7-6-2025 https://dna-explained.com/2025/07/06/jacques-bourgeois-complex-acadian-founder-of-beaubassin-52-ancestors-450/
41 How to Use Ancestry’s New Match Clusters and What They Mean Ancestry 7-10-2025 https://dna-explained.com/2025/07/10/how-to-use-ancestrys-new-match-clusters-and-what-they-mean/
42 Walk with Your Ancestors: Peace, Light and Healing in an Abandoned Medieval Village History 7-21-2025 https://dna-explained.com/2025/07/21/walk-with-your-ancestors-peace-light-and-healing-in-an-abandoned-medieval-village/
43 Jeanne Trahan (c1629-c1699), Life in Chinon, La Heve, Port Royal, and Beaubassin – 52 Ancestors #451 52 Ancestors 8-2-2025 https://dna-explained.com/2025/07/28/jeanne-trahan-c1629-c1699-life-in-chinon-la-heve-port-royal-and-beaubassin-52-ancestors-451/
44 Wherefore Art Thou, Oh Ancestor – New Generation Tree Chart Suggests Where to Look in Your Matches’ Trees Techniques, Genetics, Genealogy 8-2-2025 https://dna-explained.com/2025/08/02/wherefore-art-thou-oh-ancestor-new-generation-tree-chart-suggests-where-to-look-in-your-matches-trees/
45 Guillaume Trahan (c1601-1625), More Than Meets the Eye – 52 Ancestors #452 52 Ancestors 8-13-2025 https://dna-explained.com/2025/08/13/guillaume-trahan-c1601-c1684-more-than-meets-the-eye-52-ancestor-452/ 
46 The East Coast Genetic Genealogy Conference – ECGGC – Register Now for the Best of the Best ECGGC Conference 8-14-2025 https://dna-explained.com/2025/08/14/the-east-coast-genetic-genealogy-conference-ecggc-register-now-for-the-best-of-the-best/
47 Schelly Talalay Dardashti – May Her Memory Be a Blessing Memorial 8-17-2025 https://dna-explained.com/2025/08/17/schelly-talalay-dardashti-may-her-memory-be-a-blessing/
48 Francoise Corbineau (c1609-c1665), Bride in Chinon, Founder of Acadia – 52 Ancestors #453 52 Ancestors 8-25-2025 https://dna-explained.com/2025/08/23/francoise-corbineau-c1609-c1665-bride-in-chinon-founder-of-acadia-52-ancestors-453/
49 Nicolas Trahan (c1570->1632), Life in the Heart of French Wine Country – 52 Ancestors #454 52 Ancestors 8-31-2015 https://dna-explained.com/2025/08/31/nicolas-trahan-c1570-1632-life-in-the-heart-of-french-wine-country-52-ancestors-454/
50 Mitochondrial DNA A-Z: A Step-by-Step Guide to Matches, Mitotree, and mtDNA Discover Mitochondrial DNA, Discover, Genealogy, Techniques 10-2-2025 https://dna-explained.com/2025/09/02/mitochondrial-dna-a-z-a-step-by-step-guide-to-matches-mitotree-and-mtdna-discover/
51 Renée Desloges (c1570-1627/1632), Fragments of Life in Montreuil-Bellay – 52 Ancestors #454 (this is actually 455) 52 Ancestors 9-6-2025 https://dna-explained.com/2025/09/06/renee-desloges-c1570-1627-1632-fragments-of-life-in-montreuil-bellay-52-ancestors-454/
52 Best Mitochondrial DNA Presentation EVER – You’re Invited to DNA Academy!! Mitochondrial DNA 9-9-2025 https://dna-explained.com/2025/09/09/best-mitochondrial-dna-presentation-ever-youre-invited-to-dna-academy/
53 Unfillable Shoes Memorial – Douglas Rhodenbaugh 9-14-2025 https://dna-explained.com/2025/09/14/unfillable-shoes/
54 Concepts: What Does a Cousin “Once Removed” Mean? Concepts, Genealogy 9-24-2025 https://dna-explained.com/2025/09/24/concepts-what-does-a-cousin-once-removed-mean/
55 Daniel Vannoy (1752-after 1820), “Lived in the Boundary of the Cherokee Indians” – Say What??? 52 Ancestors 9-29-2025 https://dna-explained.com/2025/09/29/daniel-vannoy-1752-after-1820-lived-in-the-boundary-of-the-cherokee-indians-say-what/
56 Daniel Vannoy and the Strange Case of the Two Sarahs – 52 Ancestors #457 52 Ancestors 10-5-2025 https://dna-explained.com/2025/10/06/daniel-vannoy-and-the-strange-case-of-the-two-sarahs-52-ancestors-457/
57 Cousin Finder – MyHeritage’s Innovative New Tool Finds Your Relatives MyHeritage 10-9-2025 https://dna-explained.com/2025/10/09/cousin-finder-myheritages-innovative-new-tool-finds-your-relatives/
58 Sarah Hickerson Vannoy (c1761 – after 1826), Threw More than Shade – 52 Ancestors #458 52 Ancestors https://dna-explained.com/2025/10/13/sarah-hickerson-vannoy-c1761-after-1826-threw-more-than-shade-52-ancestors-458/
59 MyHeritage Introduces a Low-Pass Whole Genome Autosomal DNA Test & Why It Matters MyHeritage 10-14-2025 https://dna-explained.com/2025/10/14/myheritage-introduces-a-low-pass-whole-genome-autosomal-dna-test-why-it-matters/
60 Henriette Pelletret (c1640 – before 1694), Life Death in the Shadow of the Fort – 52 Ancestors #459 52 Ancestors 10-21-2025 https://dna-explained.com/2025/10/21/henriette-pelletret-c1640-before-1694-life-and-death-in-the-shadow-of-the-fort-52-ancestor-459/
61 Cheat Sheet: Mitochondrial Matches, Haplotype Clusters, and Haplogroups Mitochondrial DNA 10-22-2025 https://dna-explained.com/2025/10/22/cheat-sheet-mitochondrial-matches-haplotype-clusters-and-haplogroups/
62 Simon Pelletret (1610-1642/1645): A Walk Through Port Royal – 52 Ancestors #460 52 Ancestors 10-27-2025 https://dna-explained.com/2025/10/27/simon-pelletret-c1610-1642-1645-a-walk-through-port-royal-52-ancestors-460/
63 Perrine Bourg (c1626-1693/1698): Phoenix Rising from the Ashes – 52 Ancestors #461 52 Ancestors 11-2-2025 https://dna-explained.com/2025/11/02/perrine-bourg-c1626-1693-1698-phoenix-rising-from-the-ashes-52-ancestors-461/
64 Concepts: What is a Half Relationships, Life Half First Cousins, Anyway? Concepts, Genealogy 11-4-2025 https://dna-explained.com/2025/11/04/concepts-what-is-a-half-relationship-like-half-first-cousins-anyway/
65 Marie Broussard (1686-after 1752), Life Across the River from Port Royal – 52 Ancestors #462 52 Ancestors 11-10-2025 https://dna-explained.com/2025/11/10/marie-broussard-1686-after-1752-life-across-the-river-from-port-royal-52-ancestors-462/
66 Francois Broussard (1653-1716), Intractable Acadian – 52 Ancestors #463 52 Ancestors 11-22-2025 https://dna-explained.com/2025/11/22/francois-broussard-1653-1716-intractable-acadian-52-ancestors-463/
67 Mitotree Sprouts 12,773 New Branches and Includes Ancient DNA Mitochondrial DNA 11-24-2025 https://dna-explained.com/2025/11/24/mitotree-sprouts-12773-new-branches-and-includes-ancient-dna/
68 Catherine Richard (c1663 – after 1714), Mother of Beausoleil, Acadian Freedom Fighters – 52 Ancestors #464 52 Ancestors 11-29-2025 https://dna-explained.com/2025/11/29/catherine-richard-c1663-after-1714-mother-of-beausoleil-acadian-freedom-fighters-52-ancestors-464/
69 Ancestry’s ThruLines Has a New Pedigree View Ancestry 12-2-2025 https://dna-explained.com/2025/12/03/ancestrys-thrulines-has-a-new-pedigree-view/
70 Ancestry Reverts ThruLines to the Original View Ancestry 12-6-2025 https://dna-explained.com/2025/12/06/ancestry-reverts-thrulines-to-the-original-view/
71 Michel Richard (c1630-1686/1689), Carefree Acadian – 52 Ancestors #465 52 Ancestors 12-7-2025 https://dna-explained.com/2025/12/08/michel-richard-dit-sansoucy-c1630-1686-1689-carefree-acadian-52-ancestors-465/ 
72 Mitochondrial DNA: How Do I Know if I’m a Candidate to Receive a New Haplogroup? Mitochondrial DNA 12-9-2025 https://dna-explained.com/2025/12/09/mitochondrial-dna-how-do-i-know-if-im-a-candidate-to-receive-a-new-haplogroup/
73 Heavens Ablaze: the 1833 Leonid Meteor Storm and Your Ancestors History, Genealogy 12-15-2025 https://dna-explained.com/2025/12/15/heavens-ablaze-the-1833-leonid-meteor-storm-and-your-ancestors/
74 Madelaine Blanchard (c1643 – 1678/1683), Gone Too Soon – 52 Ancestors #466 52 Ancestors 12-20-2025 https://dna-explained.com/2025/12/20/madelaine-blanchard-c1643-1678-1683-gone-too-soon-52-ancestors-466/
75 Soar Inspiration 12-24-2025 https://dna-explained.com/2025/12/24/soar/

_____________________________________________________________

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’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

I receive a small commission when you click a vendor link in my articles and purchase that item. 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

The Big Y-700 Test Marries Science to Genealogy

Recently, one of my long-time friends and project co-administrators asked me a simple question.

  • What do the FamilyTreeDNA Big Y-700 test and the Time Tree tell us when we have genealogy trees provided by testers?
  • What does the Discover Time Tree tell us that’s different, and how do we reconcile the Time Tree and genealogy?

Those are great questions.

Sometimes, I get so buried in the details of genetic genealogy that I neglect the obvious, so I’m writing this article for my co-admin and anyone else with the same questions.

Time Tree Versus Genealogy Question

Of course, as a genealogist, my first answer would be that we always need to be cautious about user-provided trees. Even when the genealogy is accurate, that’s no guarantee there wasn’t a biological disruption that caused the genetic line not to be the same as the surname line.

Almost every lineage has examples of people whose genealogy was “off” or misattributed paternity occurred someplace upstream, meaning that someone carries the surname but does not descend from that biological lineage.

However, relative to DNA projects, the Big Y-700 tests provide one very important feature that STR testing does not and cannot do.

The Big Y-700 test creates a genetic tree, in conjunction with other testers, which provides scientifically calculated dates when branches of the genetic tree were formed.

The genetic tree should align, at least closely, with testers’ genealogical trees.

In other words, if their genealogy is accurate, testers “should” fit in (or at least near) the appropriate places on the branches of the genetic tree.

Furthermore, for people trying to sort out their actual branch in the tree, the Big Y-700 test is MUCH MORE reliable than the earlier STR (short tandem repeat) tests that are prone to random and back mutations. At one time, STR tests were all that was available, but now,  SNPs have been added to our arsenal. SNPs (single nucleotide polymorphisms) are extremely stable and reliable mutations.

I’m getting ready to record a new Y-DNA webinar, and I’m giving you a sneak peek of a couple of my slides here. I’ll publish an announcement when the webinar is available.

STRs Versus SNPs

Historic Y-DNA testing tested only a limited number of STR locations. That test reported the number of repeats at a specific genetic location on the Y chromosome. Today, the 37, 67, and 111 marker STR tests are still available to purchase.

What are the major differences between the two types of tests, and why would someone purchase one over the other?

If you purchase one of the STR tests, you purchase testing at a specific number of locations, such as 37, 67, and 111. The Big Y-700 test includes at least 700 STR locations, but the specificity of the Big Y-700 SNP testing replaces most of the STR test results in terms of lineage definition.

SNP mutations, when discovered in more than one man in a particular haplogroup lineage, are then named as haplogroups. That mutation is then found in each directly descended male in that line.

STR – 37, 67, 111 Big Y-700 (STRs & SNPs)
Tests A limited number of repeat STR markers – Big Y guarantees 700+ NGS scan targets ~ 25 million locations
Focus Comparatively short genealogy timeframe All-inclusive – recent genealogy plus older to ancient
Includes Can upgrade to Big Y-700 Includes STR tests, separate matching, Globetrekker, Discover, and more
Tree Genealogy, customer provided Genetic Tree – Group Time Tree coordinates with genealogy if provided
Tools STR tools STR tools plus SNP tools & robust Discover
Haplogroup Estimated based on STR values Confirmed to the most granular level possible – evergreen
Useful When Exclusion testing, less costly, entry-level Discover provides lineage, ancient DNA, TMRCA, and more
Matching STRs only STR plus Big Y – both can be useful
Trees Customer provided genealogy Time Tree, Group Time Tree, Block Tree, Classic Tree + 1 more soon

Put simply, the STR tests are now entry-level. Once you see what the Big Y-700 provides, you’ll absolutely want to upgrade to that test. Most of the time, if I know I’m testing someone from the correct line, I just purchase the Big Y-700 out the gate. If I’m not sure I’m testing the correct lineage, I’ll purchase the STR test first to make sure they match the correct lineage before upgrading to the Big Y-700.

Discover

The Discover tool was introduced to provide additional information to Big Y testers and others seeking haplogroup information. STR results can only predict a relatively high-level haplogroup, usually a few thousand years ago, while the Big Y-700 provides testers with an extremely granular haplogroup – usually decades to a few hundred years ago. Often, living men that span 2 or 3 descendant generations (grandfather, father, sons) discover that they have their own haplogroup branch on the tree of mankind!

However, if no one else from your line has tested in hundreds of years, Discover can only work with available information.

Let’s take a quick look at the Estes Group Time Tree.

Estes Project Group Time Trees

Group projects have Group Time Trees. You can view the Estes surname project, here. You can find a project for any surname by either googling “<surname> DNA Project” or scrolling to the VERY bottom of the FamilyTreeDNA main page.

If you’re signed into FamilyTreeDNA, you can also find projects in the top banner.

Once you’re on the project page, you’ll see an option for DNA Results (assuming the administrators have not made the project entirely private.)

Click on the DNA Results link and select Y-DNA.

Next, you’ll see “Group Time Tree.”

Group Time Tree Display

What appears next depends on how the project administrators have grouped the project participants.

I’ve grouped the Estes project by genealogical line, with the exception of a couple of people who carry the Estes surname but have experienced an adoption or other unknown parental event in their Estes lineage.

In some cases, there are simply two same-name lineages that were never from the same biological line. Unfortunately, occasionally they settle in the same place, making the genealogy difficult. Even worse, until Y-DNA testing came along, there was often no way to know they were two different families.

This situation is actually where the Big Y-700 test shines.

 

The Group Time Tree shows the genetic tree scientifically constructed from the SNP results of the Big Y-test results of the testers, at left. At right you’ll see the surnames of the testers along with their Earliest Known Ancestor (EKA) if they have entered that information.

Initially, you don’t even realize you’re actually looking at two types of information merged together. This display allows testers to see the genetic branching tree structure, at left, which is reflective of their actual genealogy, at right.

You can see that the birth year of Sylvester Estes, entered by a tester with haplogroup R-BY482, is 1622. Please note, there’s a typo. Sylvester was born in 1522, NOT 1622. This is a perfect example of what I meant by tree information sometimes being inaccurate and it’s very important when trying to correlate the genetic tree and the user-provided genealogy.

We discovered that R-BY482 (red profile above, at left) is an Estes “signature” haplogroup for the Estes line originating in Deal, England, with three other haplogroups that formed in descendant generations. We know this because every descendant from this line has this mutation.

R-BY490 was formed between Sylvester’s son Robert Estes, born about 1555, and his son, born about 1600, also named Sylvester. We know this because all of the descendants of Sylvester (born circa 1600) carry this mutation, but Robert’s son, Robert, born in 1603, does not.

The genealogy portion of the Group Time Tree, above, doesn’t reveal that information because testers either don’t know their genealogy that far back or perhaps listed an earlier known ancestor, such as Nicholas, born in 1495.

Click to enlarge

I created a spreadsheet tracking the Big Y-700 testers of the descendants of Nicholas Estes, along with their descendant haplogroups.

We know that Robert, born in 1555, carries R-BY490 because both of his sons, Abraham and Richard, inherited that mutation, seen with green arrows.

However, this calls into question the associated genealogy because if Robert, born in 1603, descended from Robert, born in 1555, he too would have the mutation R-BY490 since Robert’s other two sons do. Note that the user-provided birth year typo of 1622 which should be 1522 is a century off – enough to be within the genetic band haplogroup birth band – but impossible for the genealogy table.

There is one other possibility: kit 166011, the descendant of Robert born in 1603, could have taken the earlier Big Y-500 test and never upgraded to the more powerful Big Y-700. That’s too much detail for this article, but the discrepancy between the genetic tree and the genealogy tree alerts us that additional research is warranted. The genealogy submitted for tester 166011 confirms that, indeed, 1622 is a typo.

There are no other descendants of known sons of Nicholas or Sylvester born in 1522 to test, but perhaps another will surface one day.

You can see that the more testers in any particular line, the more granularity we can achieve.

The Genetic Tree

How close is the genetic tree to the genealogical tree that has been confirmed?

We know that Sylvester was born in 1522, and his father Nicholas in about 1496. The scientifically calculated creation date of R-BY482 is 1493, just 3 years before the birth of Nicholas. Based on this, there’s a good chance that this mutation occurred between Nicholas’s unknown father and him, or perhaps between Nicholas and Sylvester.

You can view the scientific details of any haplogroup in Discover.

Discover’s BY-482 scientific details page shows its creation date range.

Marriage

You can see that the scientifically created tree and the genealogy information are both important.

In fact, the combination of both allowed us to identify the correct branch of a Wilbur man who matches Estes men but doesn’t know where he fits in the tree.

His haplogroup placed him definitively on the more recent R-BY154784 branch, and his autosomal results then confirmed his specific path of descent because he matches descendants of three generations of Estes men’s wives, showing that his branch descends from Joseph Estes and his wife Ritty Lee, through son Chism, on down to our tester. In this case, autosomal DNA results provided a boost-assist to the genealogy, which helped identify the generation that the Y-DNA haplogroup R-BY154784 actually formed.

This also informs us that Joseph Estes, born in 1780, carried haplogroup R-BY154784 because both of his sons have it. If Joseph hadn’t had that mutation, then both of his sons couldn’t have inherited it.

Therefore, the mutation that formed haplogroup R-BY154784 had to occur between Moses, born in 1711, and John, born in 1732. We know that because Moses’s other son’s descendants do not have that haplogroup.

The more descendants of any ancestor that test, the more specific and accurate the descendant haplogroup formation dates will be.

The marriage of genetic trees and genealogy is powerful indeed.

More Information

For those seeking more information, 70 pages of my new book, The Complete Guide to FamilyTreeDNA – Y-DNA, Mitochondrial, Autosomal and X-DNA is devoted to Y-DNA results.

_____________________________________________________________

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

Great News – Both e-Pub and Print Version of “The Complete Guide to FamilyTreeDNA” Now Available Worldwide  

  • Anyone, anyplace, can order the full-color, searchable, e-pub version of The Complete Guide to FamilyTreeDNA – Y-DNA, Mitochondrial, Autosomal and X-DNA from the publisher, Genealogical.com, here.
  • Customers within the US can order the black and white print book from the publisher, here.
  • Customers outside the US can order the print book from their country’s Amazon website. The publisher does not ship print books outside the US due to customs, shipping costs, and associated delays. They arranged to have the book printed by an international printer so that it can be shipped directly to Amazon for order fulfillment without international customers incurring additional expenses and delays. If you ordered the book previously from Amazon and a long delivery time was projected, that should be resolved now and your book should be arriving soon.

Comprehensive

This book is truly comprehensive and includes:

  • 247 pages
  • More than 267 images
  • 288 footnotes
  • 12 charts
  • 68 tips
  • Plus, an 18-page glossary

To view the table of contents, click here. To order, click here.

Thank you, everyone, for your patience and your support.

_____________________________________________________________

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