Y-DNA Results at 20 Years: Answers, Lessons, Methods, and Workarounds

Our goal as genealogists is always to learn what we don’t know and reveal anything we should know.

I’m going to share the evolution of four tests, purchased exactly twenty years ago. I haven’t cherry-picked these, so you’re getting the raw story. Successes, challenges and regrets, plus a few hacks to help you out when you’ve hit a roadblock.

I’m also sharing how I work around some issues – like tests that haven’t been (and can’t be) upgraded to Big Y tests.

DNA testing has come a long way from an infant science two decades ago, when we were tentatively establishing a new industry – one that today has evolved into a staple for serious genealogists.

On New Year’s Eve, 2005, exactly 20 years ago, I was doing the same thing I was doing at midnight in 2025 – genealogy.

That was long before the days of social media and chat groups, so some of us geeky types were discussing our genealogy research on the now-obsoleted RootsWeb e-mail list.

I Was Planning for 2006 Travel

I realized that I was going to be traveling during 2006 and would be asking several men to take a Y-DNA test, so I should purchase several kits while they were still on sale.

Then I got a bit giddy when I realized that I could actually celebrate the New Year by making those purchases right at midnight.

And I did too – I hit it right on the dot.

I mean, for a genealogist, what better way to celebrate? Right?

What I didn’t know is that, quite by accident, I managed to score kit 50,000. That seemed like such a milestone!

And now, I can’t believe it’s been 20 years. How is that even possible?

After I went to bed in the wee hours of January 1, 2026, I decided I needed to check in on the kits I purchased on that fateful New Year’s Eve, 2005, and see how they are doing. What were my goals, aspirations and expectations? Did we accomplish them then? Have we now?

What has happened in the past twenty years?

Let’s take a look, beginning with kit 50,000.

Kit 50,000 – Mr. Miller

Mr. Miller is my mother’s second cousin, so the perfect person to represent our Miller line.

Goals and Questions:

  • Do we descend from Johann Michael Miller born in 1692 in Germany? At that time, we did not know his birth location, and only knew that the line was German. Later research would add two additional generations and place his grandfather, Heinsman Mueller in Schwarzenmatt, Switzerland before 1655.
  • Does the Elder Jacob Miller (born about 1710 in Germany), a Brethren minister, match the Johann Michael Miller line? They were both Brethren, clearly knew each other, and were found in some of the same locations. The answer is conclusively no; the lineages are not the same based on both STR and Big Y-700 tests.

2005 – 12-marker test – $99

  • Initial 2006 haplogroup – R-M269 – about 6,500 years old
  • 2025 haplogroup – R-BY56132 – about 350 years old, obtained via DNA match to another Miller tester

That a HUGE difference!

2006 matches – no Y-DNA matches.

Remember, this was early, with less than 50,000 results in the database, compared to just under 700,000 SNP-confirmed testers today, not to mention probably double many more STR-only testers.

Haplogroups for STR testers are predicted based on marker values and are not SNP tested or confirmed. The Big Y tests, SNP tests and SNP packs which are no longer available, and haplogroups assigned through Family Finder are SNP confirmed.

2025 matches – 2 (yes two) 12-marker matches, both Millers. At 25 markers, he has 7 matches, all Millers.

I created the Miller-Brethren Project in September 2006 for any Miller line that was of the Brethren faith, hoping to differentiate between families with the same names in the same place.

2009 – upgraded to 67 markers – $148

In 2009, I upgraded Mr. Miller to 67 markers and recruited two other Miller males from our believed line. They all matched at 25 markers and above, confirming the lineage to our ancestor, Johann Michael Miller/Mueller. Whew! That one was close, because there was a great deal of consternation and confusion about these lineages.

2011 – added Family Finder – $289

Mr. Miller’s haplogroup today, confirmed by Family Finder, is still same as his predicted R-M269 from his STR results. Unfortunately, the kit has never been upgraded to the Big Y test, and I desperately want our personal lineage haplogroup. However, all is not lost because he matches several males from the same lineage who have been assigned to haplogroup R-BY56132 through the Big Y-700 test.

Every haplogroup is publicly viewable in Discover, but testers can see additional information and features when they click through to Discover from their own account – including the Match Time Tree, Globetrekker, and more Ancient and Notable DNA Connections.

Discover provides an informative Haplogroup Story, an overview before viewing the dozen reports available in the left sidebar about that haplogroup’s history and lineage. You can take a look, here.

From Discover, we learn that the Miller haplogroup was born (or branches off from) its parent haplogroup about the year 1650 CE, so when the Millers were still living in either Switzerland or Germany. If we match males from either of those locations, they would probably match us upstream at R-BY115568. Their genealogy would certainly help our genealogy!

Ancient Connections, which are ancient DNA matches, extend beyond surnames, revealing connections to both the Yamnaya and Moros cultures and shared ancestry with Bronze Age Balkan burials.

Viewing the Ancient Connections tab, we learn that remains related to or upstream of our haplogroup were excavated in Albania, Germany, Hungary, Bulgaria, the North Banat and Mokrin in Serbia, and Macedonia. The closest genetic connections are shown first.

New Goal: Would love to test and match with Mueller men from Steindwenden, Germany, Schwarzenmatt, Switzerland, or anyplace near either location.

Kit 49,999 – Mr. Estes

Goals and Questions:

  • Do we connect with the Abraham Estes (c1647-1720) lineage?
  • Was there more than one early colonial Estes line?
  • If so, were they related?
  • Did our line come from Kent, England?

2005 – 25-marker test – $150

2006 matches –  54 12-marker matches

2025 matches – 326 12-marker matches

2006 matches – 4 25-marker matches – one to a known cousin, two more to other Estes males

2025 matches – 30 25-marker matches, including several Estes men

Crucial – this tester matched an Eastes male who lived in Kent and whose ancestors never left. This confirmed our oral history and early research suggesting that Abraham Estes’s origins were in Kent.

  • Original 2006 haplogroup – R-M269 – about 6.500 years old
  • Current Haplogroup – R-L151 – about 5,000 years old, SNP confirmed from the Family Finder test
  • Match Haplogroup – R-ZS3700 – about 250 years old obtained from STR match to multiple Big Y testers who shares same ancestor

In 2012, we added the Family Finder test for $199, which answered questions about whether multiple half-siblings were actually descended from a close relative of the tester. Family Finder also allowed people descended from this line, but who don’t carry the Estes Y-DNA to confirm their relationship to the Estes family.

This tester has not upgraded to the Big Y-700, but does match at the STR level with those who have taken that test.

Today, the Eastes male from Kent who subsequently upgraded to the Big Y-700 forms the base of the Estes family genetic tree, and others in the American lines form descendant branches based on the Big Y-700 test!

This includes some men whose genealogy we can’t yet connect vis the paper trail, such as kit 491887, shown in lavender below, but we know where he connects genetically. We were able to place him due to his Big Y-700 test results.

Thanks to the man from Kent whose results appear in the pink column, we know that both the Massachusetts and the Virginia immigrants descend from the Estes line in Kent, based on haplogroup R-BY490.

The Massachusetts line carries only R-BY482, so R-BY490 occurred in the generation between Robert b 1555 and Sylvester b 1600. Because the descendant of Sylvester’s brother Robert, born in 1603, does NOT carry the BY490 SNP, so we know exactly where and when it was introduced.

In Abraham’s lineage, two additional branches have been discovered. R-ZS3700, and within that haplogroup, R-BY154784.

All of this structure was built beginning with kit 9,993, followed by 49,999 (for my line), which is not shown in the chart above because there is no Big Y test, but whose STRs do match with kit 9,993, our very first Estes male to test.

Discover shows that R-ZS3700, the defining haplogroup of the Moses Estes lineage, kit 9,993, was born about 1750, which is within the genetic range of about 1600 to about 1820. Moses Estes, the man in whom this SNP originated, was actually born in 1711. The genetic tree closely matches the genealogy tree.

Ancient Connections reveals that we share distant ancestors from about 4400 years ago with Iron Age burials in Scotland, Cambridgeshire, Denmark, Dorset, Cornwall, Bedfordshire, Oxfordshire, Yorkshire, and Iceland. In other words, the Estes lineage has been in England for a very, very long time.

One of the upstream parent haplogroups, R-S252, dating from about 4500 years ago, was found in an Anglo-Saxon burial at Cliff’s End Farm, a mortuary and ritual Bronze Age site in Kent, England.

Cliffsend is only about 10 miles from Deal, where many Estes family records are found, and about 5 miles from Sandwich where Abraham Estes, the immigrant, was a weaver, next to the village of Worth, where he was married in 1672.

Kit 49,998 – Mr. Moore

Goals and Questions:

  • I was desperate to test a male from my Moore family in Halifax County, VA, and was very fortunate to locate Mr. Moore when I visited in person. I had to work on his genealogy, but once I was able to connect him, he was excited to test.
  • Could we connect our line with other Virginia lines, or eliminate them from consideration?

2005 -12 marker test – $99

2006 matches – 37 12-marker matches, two of whom were Moore men. One was a man I believed to be from my James Moore and William Moore line, and one we suspected, but really didn’t know. Many records from that time period are missing, and people were moving to the next frontier, with no connection to where they came from.

Mr. Moore’s matches, combined with his genealogy, confirmed what we thought we knew, but we still needed more.

  • Original 2006 haplogroup – J-M172 – about 28,000 years old
  • Current Haplogroup – J-M241 – about 8,600 years old, obtained from Family Finder
  • Match Haplogroup – J-Z631 – about 2,950 years old, obtained from matches to other Moore men who took the Family Finder test
  • Big Y Match Haplogroup – J-BY136349 – about 1,300 years old, obtained from a 111-marker Moore match to a non-Moore man who has taken a Big Y test

In 2012, we added Family Finder for $199, which provided invaluable matches to known Moore lineage family members, including Mr. Estes, kit 49,999. That makes perfect sense, since they are 4C1R.

2025 matches – 276 12-marker matches, of which five are Moore men, none of whom have taken the Big Y-DNA test.

One Moore match, who has not responded to emails, shows his paternal Moore ancestor as having been born in Scotland.

Three of Mr. Moore’s matches whose haplogroups were determined by Family Finder are J-Z631, which is closer to the present time than Mr. Moore’s haplogroup.

Why might that be?

Different autosomal DNA testing chips were used by different vendors at different times. Mr. Moore and the three other Moore men all took a Family Finder test at FamilyTreeDNA, but at different times when different chips were in use. That’s probably why the haplogroup assignment is different. The other reason could be that one of the SNP locations was missed in the autosomal DNA test. The haplogroup designation from the Family Finder test is a recent freebie, so was never actually intended to be a feature.

That’s all fine and dandy, but I STILL need a Moore Big Y tester to reveal more information about my line.

Workarounds for No Big Y Testers

Without a Big Y-700 Moore tester, is there something else we can try to obtain at least a somewhat more refined haplogroup?

Perhaps.

Without at least one Big Y-700 test, the next two things can do are:

  • Hope that someone has included at least some genealogy for you to follow.
  • One of the 111 marker matches will help by sharing if they have any Moore matches at that level. Remember, this kit, 49,998, only has 12 marker matches.

In this case, there is one match with a tree, but I hit the same genealogical brick wall that they did.

They, and now I am stuck with John Moore, born between 1851 and 1860, possibly in Sullivan County, TN. He was married to Mary, Polly, Mollie (take your pick based on the census and death certificates) Whitaker, who died between 1900 and 1910. John Moore died on September 25, 1936, in Sullivan County, TN, with several children and a brother named Bob Moore who lived in nearby Bristol listed in a brief obituary. I’m doing the “quick and dirty” tree thing, here, hoping to perhaps track his Moore back further than I have my own so we can connect – but so far – no cigar. I’m not finished yet, but this one is challenging. I’m always hopeful that I’ll find some hint about where James Moore (c1718-c1798) came from before Prince Edward and Amelia County, VA.

Eliminating Other Moore Lines

I certainly don’t have as much information as I want about my own Moore line, but I do have something. How can I use this to eliminate other potential Moore lines?

Checking the Moore Surname Project, I use the browser search and located the group of my James Moore testers.

These six men are candidates for Big Y upgrades.

I can also use the browser search to locate other groups of Moore men that have tested and I know we’re not related to.

For example, here’s another group of Moore men that we aren’t related but – but here’s the catch. This is the “other” James Moore that appears in Halifax County, and whose land is located right across the road from my James Moore. I kid you not. I could have SWORN these two Moore lines were the same, but they are not. This line track back to Thomas Moore born in 1720 and who married Mary Farrar. Using genealogy and projects, combined with what we do know, we can eliminate many possibilties.

Ok, let’s set genealogy aside for a minute.

Working With Alternative Haplogroups

What else can we do if we cannot upgrade either our tester or convince other Moore men to upgrade to the Big Y-700?

If a tester has higher level STR matches, meaning 67 or 111, and they match anyone with a Big Y-700 test, they will likely be in the same area of the genetic tree, but probably not the same branch, and possibly not within hundreds to the low thousands of years. This approach is an extremely poor substitute for the Big Y test and should never be used unless there is absolutely no other alternative. Think of it as sitting proxy at home, watching the Jumbotron on your TV, versus sitting behind home plate in the ballpark. It will do if you have no other choice.

That said, let’s see what we have. Our Moore Family Finder SNP is J-Z631, which is about 2,950 years old.

Our J-Z631 haplogroup story shows that the majority are found in Germany, followed by England, and the Ancient Connections are associated with the Roman era in the Balkans and Sicily. Burials from that era were found in Rome, Montenegro, Hungary, Poland, Serbia, Croatia, and Trapani, Italy.

Next, let’s look at one of the Moore men’s 111 matches, who has been assigned the Big Y-700 haplogroup of J-BY136349.

This is quite interesting, because this haplogroup has few testers, but the Ancient Connections are found in some of the same locations.

Next question – how are these two haplogroups related? Let’s see, using Discover’s Compare feature.

Wow, I didn’t expect to discover that J-BY136349 (111 marker match to a non-Moore man) is a descendant of J-Z631 (Moore haplogroup from Family Finder) and is about 2,200 years closer to the present time. Our Moore men, if we can ever find a Big Y-700 tester, will likely be someplace near J-BY136349.

Goals:

  • To upgrade at least one of Mr. Moore’s matches to the Big Y-700, and for some new Moore male to match so we can figure out which Virginia line, and which European line our Moore family descends from.
  • To break through the John Moore brick wall in Sullivan County, TN to see if we can track that lineage further back in time – informing us of our Moore line.

Kit 49,994 – Mr. Speaks

Goals and Questions:

  • To find and test any Speak/Speaks tester for our line.
  • Were the two Thomas Speaks in Maryland in the 1700s related?
  • Were various Speaks lines, by various spellings, throughout the country, related?
  • Where did we “come from?”

Twenty years ago, we had no Speaks males to test until Joyce, one of our long-time genealogy experts, located one man. She visited him and explained why his DNA was important. I provided a scholarship, and the rest, as they say, is history.

Not long after, another Speaks man tested, but did not match our original tester. Everyone was shocked. No one expected that result, and it only confused matters even more.

We needed tie-breakers, meaning other men from both of the known sons of immigrant, Thomas Speake (1633-1681).

At this point, we had far more questions than answers.

The Speaks Family Association had a whole list of questions, in part due to a lack of early records in Maryland, combined with burned southern states in later generations. That list was growing, not shrinking.

How many Speaks lines were there anyway? Had we stumbled across a descendants from the “other” Thomas Speaks in Maryland? I can’t answer that question now, and the answer is no, we had not accidentally found the other Thomas. That Thomas’s will and estate shows he had no sons other than a son Thomas who is not our Thomas, based on the fact that he died before his father. That also means there are no males from his line to test. You can read more, here, if you’re interested.

Did men with the surname Speak, Speaks and similar spellings all descend from the same Maryland line? Apparently not, or maybe not, based on those early results.

Could we determine through which men various testers descend?

At that time, we didn’t even dream that we’d be able to obtain Y-DNA from various men in the Lancashire villages where we thought our line might have originated. That was still years in the future. Our big breakthrough came after a Speaks man from New Zealand tested, and knew the name of the Lancashire village, Gisburn, where his grandfather was born. Working with local historical societies in England, we made that trip happen in 2014 and learned even more about differing Speaks lines.

In other words, in 2005, we were starting from scratch with pockets of men in various locations across the US who shared the same or similar surnames.

2005 – 25-marker – $150

  • Initial haplogroup – I-M170 – about 28,000 years old
  • Current 2025 haplogroup – I-FTA13986 – about 250 years old, obtained from a Big Y test

2014 – 111-marker upgrade – $184

2024 – Family Finder and the Big Y

2006 matches – Mr. Speaks had no 12 or 25-marker matches, which was discouraging. In fact, Mr. Speaks wouldn’t have any matches until the Family Association began actively recruiting testers a few years later. As it turns out, the Speaks family line has a rather unique DNA signature.

Today, Mr. Speak has 61 12-marker matches, and 54 25-marker matches, but it’s his Big Y results that confirm his placement in the tree as a descendant of John Speake the Innkeeper, son of Thomas Speake the immigrant.

Initially, we did the best we could, placing people in the tree based on STR results, but STRs did not provide the granularity we needed to define lines conclusively. STR mutations tend to back-mutate and aren’t always reliable.

Fast forward to January 2026.

The Speaks DNA project now has 48 Y-DNA testers, of which 32 fall into the Lancashire Speaks line we were seeking.

The Speak Family Association funded several Big Y-700 tests and upgrades for critical men in known lines.

Additionally, we’ve finally placed the elusive Aaron Lucky Speaks line, found in North Carolina, without any connecting documents back to Maryland. DNA connected him!

We’ve also eliminated several lines that were possibly connected to the Lancashire/Maryland line, thanks to DNA testing.

The Speak Family DNA Project Time Tree shows the Big Y testers with their self-identified earliest known ancestors (EKA) placed on branches of the genetic Time Tree.

Shifting to Discover, we see that Lancashire SNP, I-BY14004, which defines our Speak line, is associated with Medieval Britain, the early Slavs, and a historical Romanian culture.

Checking Ancient Connections, our ancestors are associated with burials from Yorkshire, Croatia, Romania, Denmark, Italy, the Czech Republic, France, Germany, and more, dating from about 4500 years ago.

Today, if a Speak/Speaks male takes a Big Y-700 test, we can assign his location in the tree very closely, and can tell him definitively which lines he does not descend from.

The Speaks project also welcomes all Speaks descendants, from any line, who have taken or uploaded autosomal DNA tests.

Regrets

Yes, I have regrets – learned in the school of hard knocks.

  1. My largest regret is that I didn’t test all of “my” kits at the highest level possible initially.
  2. My second regret is that I didn’t reach out to matches much earlier (when they still might answer) to inquire about genealogy and offer scholarships for upgrades. My testers need someone from that same line to match at the Big Y level. In some cases, I need that person to upgrade because my tester cannot. The longer you wait, the less likely you’ll receive a response.

Many tests, especially early tests, cannot be upgraded for various reasons:

  • Deceased tester
  • Lost the ability to contact the tester – obsolete or bounced email
  • Tester does not want to upgrade or does not reply to emails
  • Last vial available was already used and tester cannot provide another
  • Last vial was tested and failed

Solutions

  • Buy the most advanced test immediately. I literally have a kit available at all times.
  • Upgrade to the newest relevant tests as soon as they are introduced. In this case, that would be the Big Y-700 today and the Family Finder when it was introduced.
  • If the tester is deceased and you can contact the family, after offering condolences, ask for brothers, sons, or nephews who would be willing to retest.
  • Offer DNA testing scholarships either personally, through family associations, or through surname projects.
  • Request extra vials be sent to the tester so they can be returned and stored for future use.

There’s one more thing you need to do too.

Permissions

Testers can grant various forms of permission to other people, which allows their tests to be upgraded later. One man even sent me an affidavit stating I could do so after he died. Today, that’s not necessary because FamilyTreeDNA provides a Beneficiary service.

Permissions can be granted under the tester’s Account Settings.

  • Ask the tester to designate a Beneficiary which can be a Group Project Administrator. That means any person who is a group project administrator of a project the tester belongs to, after they are deceased.
  • Ask the tester to assign a Kit Manager who literally manages their kit on their behalf.

Under Project Preferences, project members can grant Advanced Access to individual project administrators by name. Advanced Access provides the ability for that specific administrator to act on behalf of the tester, including ordering upgrades and additional tests, so long as the administrator pays for them, which they often do with project funds.

Looking Back

I have absolutely no regrets about purchasing any of the tests I’ve bought over the years.

I look at it this way – if someone told me that a book about my ancestral line was in a library, and it held the undisputed truth about that one line – I’d spend far more than what I’ve spent on any one DNA test to obtain it. There’s simply no other way to conclusively unravel direct paternal vines, both within a genealogical timeframe, and before.

I want to know everything. Not just since the advent of surnames, but where my ancestors came from before that, and before that, and before that. I want to read about the culture and history of the land where my ancestors lived. What did they survive to travel to the next frontier? And where was that next frontier, and when?

Their own Y-DNA, passed down to their direct male descendants holds those secrets, just waiting to be revealed.

What’s Next?

  • Check your own and any Y-DNA tests that you sponsor or manage to see how they’re doing and what’s new.
  • Check surname projects at FamilyTreeDNA, here, to see if your ancestral surnames are represented any other information, similar to my Moore line.
  • Check your ancestor at WikiTree to see if anyone has entered a haplogroup for that ancestor, which tells you that someone has tested. The haplogroup may not be current, but it gives you a connection and someplace to start.
  • Check your autosomal matches at FamilyTreeDNA and any other vendor to see if you match surnames of interest. If the match is male, reach out and see if they descend from your line, and if they haven’t taken a Y-DNA test, would they be willing. If your match is female, reach out to see if it’s your line, and if so, if they know of males who have tested or would be willing.
  • If you’re a male and have not yet tested your Y-DNA, by all means, order that test now, by clicking here! Then make sure to join your surname project!

Is there something new and wonderful waiting for you?

_____________________________________________________________

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

Mitotree Q&A for Everyone

I recently presented Mitotree Webinar – What It Is, How We Did It, and What Mitotree Means to You at Legacy Family Tree Webinars. It’s still free to view through June 13th, and after that, it’s available in the webinar library with a subscription. The 31-page syllabus is also a subscription feature.

Thank you to all 1000+ of you who attended and everyone else who has since watched the webinar – or will now.

We had a limited amount of time for Q&A at the end, so Geoff, our host, was kind enough to send me the list of questions from the Chat, and I’m doing the Q&A here. But keep in mind, please, that I’m assuming when I answer that you’ve watched the webinar or are familiar with how the new Mitotree and tools work.

That said, I think this Q&A can help everyone who is interested in mitochondrial DNA. Your genealogy gift from your mother and her female lineage.

Just a quick reminder that the mitochondrial DNA test tracks your direct matrilineal line only, meaning your mother’s mother’s mother’s line on up your tree until you run out of mothers. Of course, our goal is always to break through that brick wall.

This is a wonderful opportunity, because, unlike autosomal DNA, mitochondrial DNA is not admixed with the DNA of the other parent, so it’s a straight line look back directly up your mother’s female line.

Aha Moment!

Geoff said at the end that he had an aha moment during the webinar. Both males and females have mitochondrial DNA inherited from their mother, so we think of testing our own – but forget to obtain the mitochondrial DNA of our father. Testing your father’s mitochondrial DNA means obtaining your paternal grandmother’s mitochondrial DNA, so test your father to learn about his mother’s maternal line.

And it’s Father’s Day shortly.

Q&A

I’ve combined and summarized similar questions to make this short and sweet. Well, as short and sweet as I can make anything!

  • Can I benefit from Discover even if I don’t have a full sequence test?

You can benefit from the free FamilyTreeDNA Discover tool with any haplogroup, even a partial haplogroup. Be sure to click the down arrow and select mtDNA before entering the haplogroup if you’re using the public version.

However, to gain the most advantage from your test results and Discover, and to receive your closest matches, you need the full sequence test, called the mtFull, which you can purchase here. If you took one of the lower-level “Plus” tests, years ago, click here to sign in and upgrade or check your account to see if you have the full sequence test.

  • What benefits do I receive if I click through to Discover from my account versus using the public version of Discover?

Click any image to enlarge

If you click through to Discover directly from your FamilyTreeDNA account, you will receive features and additional information that are not available in the free, public version of Discover.

You’ll receive additional Notable Connections and up to 30 Ancient Connections based on how many are available and relevant for you.

You’ll also be able to view the Match Time tree, showing your matches, their earliest known ancestors, and where they fit in your haplogroup and haplotype cluster. In this example, two EKAs hinted at a common lineage, which turned out to be accurate after I did some digging.

I think the Match Time Tree is indispensable – the best thing since sliced bread!

The Scientific Details report is also customized for you with your Haplotype Cluster and your private variants.

  • Will a child and their mother always have the same haplogroup?

Yes, but if one of them has a mutation that the other doesn’t, or a heteroplasmy, they may be in a different haplotype cluster.

Also, they both need to have taken the full sequence test. Otherwise, the one who did not take the full sequence test will only have a partial haplogroup until they upgrade.

We will talk more about edge cases in Q&A on down the list.

Great question. Sign in to your account.

In the Maternal Line Ancestry section, which is mitochondrial DNA, check to see if both the Plus and Full boxes are pink. If so, you have taken both and you’ll have a new Mitotree haplogroup and haplotype cluster.

If the “Full” box is grey, you can either click there or at the top where it says “Add Ons and Upgrades” to upgrade to the full sequence test.

  • Why is it called the Million Mito Project? What were you counting?

When we first launched the project, we hoped for a million full sequence samples to build the initial tree. After removing duplicates, such as parent/child, partial sequence samples such as HVR1/2, unreliable samples from PhyloTree, and including FamilyTreeDNA  testers and academic samples, we had between one-third and half a million samples when we launched. The Mitotree and Discover are growing with new testers and groups of samples from archaeological studies, academic samples, and other publicly available resources, following quality analysis, of course.

  • Is there a way to confirm that I submitted an mtDNA to the Mito Tree project? I think I submitted my mom’s when you first started, but my husband recently tested, and I don’t remember if we opted him in at that time.

The science team at FamilyTreeDNA  is using all of the full sequence tests in the construction of the Mitotree, so you don’t need to do anything special.

  • Do or can haplotype F numbers (haplotype clusters) ever become haplogroups?

The answer is maybe. (I know – I’m sorry!)

If you have private variants in addition to your haplotype cluster, then yes, those are haplogroup seeds.

This is my result and I have no additional private variants left to use.

If you don’t have any private variants, or mutations, left over, then no, you won’t receive a new haplogroup for this reason. However, if for some reason the haplogroup splits upstream, you might receive a new haplogroup in the future due to that split.

In addition to the webinar, I wrote about haplotype clusters in the article, Mitochondrial DNA: What is a Haplotype Cluster and How Do I Find and Use Mine?

  • How can mitochondrial DNA and the Mitotree be useful for breaking down genealogy in various parts of the world?

There are two aspects to mitochondrial DNA testing.

The first is to connect genealogically, if possible. To do that, you’ll be paying attention to your matches EKAs (earliest known ancestors), their trees, and their locations. You may well need to do some genealogy digging and build out some trees for others.

The second aspect is to learn more about that lineage before you can connect genealogically. Where did they come from? Do they share a haplogroup with any Ancient Connections, and what cultures do they share? Where did they come from most recently in the world, and where do the breadcrumbs back in time lead?

I wrote about this in the article, New Mitotree Haplogroups and How to Utilize Them for Genealogy.

Sometimes, DNA testing of any type is simply a waiting game until the right person tests and matches you. That’s one reason it bothers me so much to see people “not recommend” mitochondrial DNA testing. We all need more testers so we can have more matches.

  • When will Globetrekker for mtDNA be available?

I don’t know and neither does the team. The Mitotree is still being refined. For example, we are adding thousands of samples to the tree right now from multiple locations around the world. I probably wouldn’t expect Globetrekker until the tree is officially out of Beta, and no, I don’t know when that will happen either. It’s difficult to know when you’re going to be “finished” with something that has never been done before.

While it’s not Globetrekker, you do have the Matches Map to work with, and the Migration Map in Discover, which also shows the locations of your Ancient Connections.

  • During the webinar, Roberta mentioned that her ancestor is German, but she discovered her ancestors were Scandinavian. Can you expand about the “event” that explained this unexpected discovery.

In my case, the church records for the tiny village where my ancestor lived in Germany begin right after the 30 Years’ War, which was incredibly destructive. Looking at Swedish troop movements in Germany, the army of Gustavus Adolphus of Sweden marched through the region with more than 18,000 soldiers. Women accompanied the baggage trains, providing essential, supportive roles and services to the soldiers and military campaign. I’ll never know positively, of course, but given that the majority of my full sequence matches are in Scandinavia, mostly Sweden, and not in Germany, it’s a reasonable hypothesis.

People often receive surprises in their results, and the history of the region plays a big role in the stories of our ancestors.

You don’t know what you don’t know, until you test and follow the paths ahd hints revealed.

  • Why do I have fewer matches in the HVR2 region than the HVR1 region?

Think of the mitochondria as a clock face.

The older (now obsolete) HVR1 test tested about 1000 locations, from about 11-noon and the HVR2/3 region tested another 1000 locations, from about noon-1 PM. The full sequence test tests the full 16,569 locations of the entire mitochondria.

Each level has its own match threshold. So, if you have one mutation at either the HVR1 or HVR2/3 level, combined, you are not considered a match. For example, you can match 10 people at the HVR1 level, and have a mutation in the HVR2 level that 4 people don’t share, so you’ll only match 6 people at the HVR2 level.

If you have one mutation in the HVR1 region, you won’t match anyone in either the HVR1 or HVR1/HVR2 regions.

At the full sequence level, you can have three mutation differences (GD 3) and still be considered a match.

So, the short answer is that you probably have a mutation that some of your matches at the HVR2 level don’t have.

In addition to matches on your Matches page, you will (probably) have haplogroup matches that aren’t on your match list, so check Discover for those.

  • I have HVR1/HVR2 matches, but none at the full sequence level. Why?

It’s possible that none of your matches have tested at that level.

You have no mutations in the HVR1/2 region, or you would not be a match. If your HVR1/2 matches have tested at the full sequence level, then you have more than 3 mutations difference in the coding region.

  • Why do I match people at the full sequence level but not HVR1/2?

The match threshold at the HVR1/2 level is 1, so if you have one mismatch, you’re not listed as a match. However, at the full sequence level, the GD (genetic distance) is 3 mismatches. This tells me you have a mismatch in the HVR1 region, which also precludes HVR2 matching, but less than 4 mutations total. Click on the little “i” button above each match level on the matches page.

  • Why don’t all of my matches show on the Match Time Tree?

Only full sequence matches can show on the Match Time Tree, because they are the only testers who can receive a full haplogroup.

  • How does a heteroplasmy interfere with mtDNA research?

Heteroplasmies, where someone carries two different nucleotides at the same location in different mitochondrial in their body, are both extremely fascinating and equally as frustrating.

Heteroplasmies can interfere with your matching because you might have a T nucleotide in a specific location, which matches the reference model, so no mutation – like 16362T. Your mother might have a C in that location, so T16362C, which is a mutation from T to C. Your aunt or sister might have both a T and a C, which means she is shown with letter Y, so 16362Y, which means she has more than 20% of both. All three of you probably have some of each, but it’s not “counted” as a heteroplasmy unless it’s over 20%.

The challenge is how to match these people with these different values accurately, and how heteroplasmies should “count” for matching.

I wrote about this in the article What is a Heteroplasmy and Why Do I Care?

Bottom line is this – if you are “by yourself” and have no matches, or you don’t match known relatives exactly, suspect a heteroplasmy. If you ask yourself, “What the heck is going on?” – rule out a heteroplasmy. Check out my article and this heteroplasmy article in the FamilyTreeDNA help center.

  • Someone asked about the X chromosome and may have been confusing it with mitochondrial DNA. The X chromosome is not the same as mitochondrial DNA.

The confusion stems from the fact that both are associated with inheritance from the maternal line. Everyone inherits their mitochondrial DNA from their mother. Men inherit their X chromosome ONLY from their mother, because their father gives them a Y chromosome, which makes them a male. Females inherit an X chromosome from both parents. And yes, there are medical exceptions, but those are unusual.

I wrote about this in the article, X Matching and Mitochondrial DNA is Not the Same Thing.

  • How do you determine the location of the last mutation? A tester and their aunt are from one country, and another man in the same haplogroup is from another country, but he has tested only the HVR1/HVR2 level.

There are really two answers here.

First, you can’t really compare your full sequence new Mitotree haplogroup with a partial haplogroup based on only the HVR1/2 test. Chances are very good that if he upgraded to a full sequence test, he would receive a more complete haplogroup, and one that might be near the tester’s haplogroup, but perhaps not the same.

For example, my full sequence haplogroup is J1c2f. I have matches with people who only tested at the HVR1/HVR2 level, but they can only be predicted to haplogroup J, with no subgroup, because they are missing about 14,000 locations that are included in the full sequence test.

Using the Discover Compare feature, comparing haplogroup J to J1c2f clearly shows that the mutations that define haplogroup J1c2f happened long after the mutation(s) that define haplogroup J.

You can use other Discover tools such as the Match Time Tree (if you click through from your account), the Time Tree, the Ancestral Path and the Classic Tree to see when the various haplogroups were born.

  • My mother took the full sequence test in 2016, so should I look for an upgrade now? She is deceased so can’t retest.

First, I’m sorry for your loss, but so glad you have her DNA tests.

The good news is that you ordered the full sequence right away, so you don’t need to worry about an upgrade failing later. In this case, there is no upgrade because the full sequence tests all 16,569 locations.

Additionally, had you needed an upgrade, or wanted to do a Family Finder test, for example, FamilyTreeDNA stores the DNA vials for future testing, so you could potentially run additional tests.

And lastly, since we’re talking mitochondrial DNA, which you inherit from your mother with no admixture from your father, your mtDNA should match hers exactly, so you could test in proxy for her, had she not already tested.

  • Has anything changed in Native American haplogroups?

Absolutely. About 75% of testers received a new haplogroup and that includes people with Native American matrilineal ancestors.

For example, my Native ancestor was haplogroup A2f1a, formed about 50 CE and is now A2f1a4-12092, formed about 1600 CE, so has moved 2 branches down the tree and about 1500 years closer. My ancestor was born about 1683. Her descendant has 58 full sequence matches, 22 in the same haplogroup, and 16 people in their haplotype cluster.

I’m so excited about this, because it helps provide clarity about her ancestors and where they were before she entered my genealogy by marrying a French settler.

  • Are mtDNA mutations the same or similar to autosomal SNPs?

A SNP is a single nucleotide polymorphism, which means a single variation in a specific location. So yes, a mutation is a change in a nucleotide at a genetic location in Y-DNA, autosomal DNA, or mitochondrial DNA.

  • Can we filter or sort our matches by haplotype on our match page?

Not yet. Generally, your closest matches appear at or near the top of your match list. Of course, you can use the Discover Match Time Tree and you can download your matches in a CSV file. (Instructions are further down in Q&A.)

  • Is there a way to make it more obvious that the EKA should be in their matrilineal line? There are so many men as EKAs!

So frustrating. The verbiage has been changed and maybe needs to be revised again, but of course, that doesn’t help with the people who have already entered males. We know males aren’t the source of mitochondrial DNA.

When I see males listed as an EKA, I send the match a pleasant note. I’m not sure they make the connection between what they entered and what is being displayed to their matches. If they have included or linked to a tree, I tell them who, in their tree, is their mtDNA EKA.

I’ve written about how to correctly add an Earliest Known Ancestor. I’ll update that article and publish again so that you can forward those instructions to people with no EKA, or male EKAs.

  • I love learning about my ancient connections. I have a new match due to the updates, who is from a neighboring area to my great-great-great-grandmother.

I love, love, LOVE Ancient Connections. They tell me who my ancestors were before I have any prayer of identifying them individually. Then I can read up on the culture from which they sprang.

I’ve also had two situations where Ancient Connections have been exceptionally useful.

One is an exact haplogroup match to my ancestor, and the burial was in a necropolis along the Roman road about 3-4 km outside the medieval “city” where my ancestor lived.

In a second case, there were two villages in different parts of the same country, hundreds of miles apart, and one burial from about 200 years before my ancestor lived was found about 10 km from one of those villages. While this isn’t conclusive, it’s certainly evidence.

  • What does the dashed line on the Time Tree mean?

Dashed lines on the time tree can mean two things.

The red dashed line, red arrow above, is the haplogroup formation date range and correlates to the dates at the top of Time Tree, not show in this screen shot. You can also read about those dates and how they are calculated on the Scientific Details tab in Discover.

The brown dashed lines, green arrow above, connect an ancient sample to its haplogroup, but the sample date is earlier than the estimated haplogroup.

At first this doesn’t make sense, until you realize that ancient samples are sometimes carbon dated, sometimes dated by proximity to something else, and sometimes dated based on the dates of the cemetery or cultural dig location.

Archaeological samples can also be contaminated, or have poor or low coverage. In other words, at this point in time, the samples are listed, but would need to be individually reviewed before shifting the haplogroup formation date. Haplogroup formation dates are based on present day testers.

  • A cousin and I have been mtDNA tested. What might be gained by testing our other six female cousins/10 or so male cousins?

Probably not much, so here’s how I would approach this.

I would test one cousin who descends from another daughter of the EKA, if possible. This helps to sift out if a haplogroup-defining mutation has occurred.

If you or that cousin has private variants left over after their haplotype cluster is formed,  testing a second person from that line may well results in a new haplogroup formation for that branch.

I absolutely would ask every single one of those cousins to take an autosomal test, however, because you never know what tools the future will bring, and we want to leverage every single segment of DNA that our ancestors carried. Testing cousins in the only way to find those.

  • In the Mitotree, I am grouped in a haplogroup that, according to the Mitotree Match Time Tree, branched off only about 200 years ago and has four mtDNA testers in it, including me. In fact, my earliest known maternal line ancestor I found using pen-and-paper genealogy was indeed born around 230 years ago and is also the known maternal ancestor for one of these three testers – confirming the Mitotree grouping is correct. But the other two matches in this haplogroup are completely unknown to me. Unfortunately, they do not have a tree online, and they did not respond to several messages. Is there any way to find out more about them using the new Mitotree tools?

First of all, this is great news. Having said that, I share your frustration. However, you’re a genealogist. Think of yourself as a sleuth.

I’d start by emailing them, but in this case, you already have. Tell them what you know from your line and ask if their line is from the same area? End with a question for them to answer. Share tidbits from Discover – like Ancient Connections maybe. Something to peak their interest.

Next, put on your sleiuh hat. I’d google their name and email address, and check Facebook and other social media sites. I’d check to see if they match me, or any cousins who have tested, on an autosomal test. If they do match autosomally, use shared matching and the matrix tool. If they are an autosomal match, I’d also check other testing sites to see if they have a tree there.

  • One webinar attendee is haplogroup H1bb7a+151 and is frustrated because they only have eight matches and don’t understand how to leverage this.

Of course, without knowing more, I can’t speak to what they have and have not done, and I certainly understand their frustration. However, in mitochondrial and Y-DNA, you really don’t want thousands of matches. It’s not autosomal. You want close, good matches, and that’s what the Mitotree plus haplotype clusters provide.

Your personal goals also make a lot of difference.

For me, I wanted to verify what I think I know – and received a surprise. I also want to go further back if possible. Then, I want to know the culture my ancestors came from.

First, step through every single one of Discover’s 13 tools and READ EVERY PAGE – not skim. These are chapters in your free book about your ancestor.

Their haplogroup was formed about 1200, so all of those matches will be since that time. The Ancient Connections tell me it’s probably British, maybe Irish – but they will see more from their account than I can see on the public version of Discover.

The Time Tree shows me one haplotype cluster, which is where the tester’s closest matches will probably be, barring a mutation or heteroplasmy.

Looking at the matches, e-mail people, look for common locations in their trees, and see if any of them are also autosomal matches using the Advanced Matching tool.

Looking at the 10 success story examples I used, one man was able to connect 19 of his matches into three groups by doing their genealogy for them. This doesn’t work for everyone, but it will never work if we don’t make the attempt.

  • An attendee would like to search on the Earliest Known Ancestor’s (EKA’s) name field.

I would like that too. You can search on surnames, but that’s often not terribly useful for mitochondrial DNA. The Match Time Tree shows the EKA for all full sequence testers.

In the upper right hand corner of your Matches page, there’s an “Export CSV” file link. Click there to download in a spreadsheet format. The EKA is a column in that file, along with both the new Mitotree haplogroup and haplotype F number, and it’s very easy to do a sort or text search from there.

  • Several questions about why people have so many more autosomal matches than either Y-DNA or mitochondrial.

There are several considerations.

First, autosomal testing became very popular, often based on ethnicity. There are many times more autosomal testers than there are either Y or mitochondrial.

Second, if you look back just six generations, you have 64 lineages. Y-DNA and mtDNA tests one line each and you don’t have to figure out which line. It also reaches back much further in time because it’s not admixed, so nothing washes out or rolls off in each generation like with autosomal.

Third, the Y-DNA and mitochondrial DNA tests are very specific and granular.

More is not necessarily better. You’re looking for refinement – and mitochondrial is just one line. No confusion. Think how happy you’d be if your autosomal matches weren’t all jumbled together and could be placed into 64 neat little baskets. Think how much time we spend sorting them out by shared matches and other criteria. Both Y-DNA and mitochondrial is already sorted out.

I’ve broken through several brick walls with unrecombined Y-DNA and mitochondrial DNA that could never be touched with autosomal – especially older lines where autosomal DNA is either gone or negligible.

  • You mentioned a Facebook group where I can ask questions about mitochondrial DNA?

The mitochondrial DNA Facebook group is the FamilyTreeDNA mtDNA Group, here.

  • To the webinar attendee who came to see me more than 20 years ago at Farmington Hills, Michigan, at one of my first, if not the first, genetic genealogy presentation – thank you!

Thank you for attending then when I really had no idea if ANYONE would come to hear about this new DNA “thing” for genealogy. I remember how nervous I was. And thank you for sticking around, continuing to research, and saying hello now!

Closing Comment

Mitochondrial DNA testing is different than autosomal, of course. It’s often the key to those females’ lines with seemingly insurmountable brick walls.

I attempt to collect the mitochondrial DNA of every ancestor. I trace “up the tree” to find people to test who descend from those ancestors through all women to the current generation, which can be males.

To find testers, I shop:

  • Autosomal matches at FamilyTreeDNA
  • Projects at FamilyTreeDNA
  • WikiTree
  • FamilySearch
  • Ancestry DNA matches
  • Ancestry Thrulines
  • Ancestry trees
  • MyHeritage DNA matches, where ther are a lot more European testers
  • MyHeritage Theories of Family Relativity
  • MyHeritage Cousin Finder
  • Relatives at RootsTech during the month before and after RootsTech when it’s available
  • Facebook Genealogy and family groups that appear relevant

When I find an appropriately descended person, I ask if they have already taken either the Y-DNA or mitochondrial DNA test, whichever one I’m searching for at that moment. If yes, hurray and I ask if they will share at least their haplogroup. If they haven’t tested, I tell them I’m offering a testing scholarship.

I will gladly explain the results if they will share them with me. Collaboration is key and a rising tide lifts all ships.

My mantra in all of this is, “You don’t know what you don’t know, and if you don’t test, you’ll never know.” I’ve missed testing opportunities that I desperately wish I hadn’t, so test your DNA and find testers to represent your ancestors.

I hope you enjoyed the webinar. It’s not too late to watch.

_____________________________________________________________

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Mitotree is Born

Mitotree is born and I can hardly contain my excitement.

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

Left to right, the Million Mito science team is:

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

The Million Mito Project Inception

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

Drum Roll – The Mitotree

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

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

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

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

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

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

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

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

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

The beta Mitotree includes:

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

More is on the way.

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

Today’s Releases

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

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

New Haplogroups

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

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

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

New mtDNA Matches Page

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

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

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

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

mtDNA Discover

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

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

Customization that occurs exclusively for FamilyTreeDNA mtFull sequence customers includes:

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

mtDNA Discover is similar to Y-DNA Discover.

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

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

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

Match Time Tree

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

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

Haplotype Clusters

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

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

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

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

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

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

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

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

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

More to Come

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

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

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

Resources

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

_____________________________________________________________

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

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

Complete Guide to FamilyTreeDNA Released in Hardcopy

Just what many of you have been waiting for! The hardcopy print version of the Complete Guide to FamilyTreeDNA has just been released.

As shown in the table of contents below, The Complete Guide to FamilyTreeDNA contains lots of logically organized information! It includes basic education about genetic genealogy and how it works, instructions on using the FamilyTreeDNA tests and tools, plus an extensive glossary.

Enjoy!

_____________________________________________________________

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

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

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

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

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

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

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

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

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

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Why Don’t Our Y-DNA Haplogroups Match?

I’ve been asked this question several times recently, and the answer is resoundingly, “it depends.” There are several reasons why Y-DNA haplogroups might not match and most of them aren’t “bad.”

How Haplogroups Work

Haplogroups are the 79,000+ branches of the Y-DNA phylogenetic tree which you can view here, along with countries where those haplogroups are found. You can think of haplogroups as genetic clans of either closely or distantly related men. Major haplogroup branches have unique letters assigned. Downstream or younger haplogroups are designated by a letter-number sequence that is always preceded by the main haplogroup letter.

Image courtesy FamilyTreeDNA

Major haplogroups were formed tens of thousands of years ago, with more recent haplogroups added as they’ve been discovered. Haplogroups are discovered and added every day thanks to the Big Y-700 test. You can read more about that process, here.

As you look at the pie chart above, you’ll notice that haplogroup R represents about half the men who have tested and has several major subbranches. Every haplogroup R man belongs to all of the branches above his own that lead back to the root of haplogroup R.

Using haplogroup R, which is R-M207, its identifying SNP, as an example, it immediately splits into two branches: R-M173, which has 37,000+ more branches, and R-M479, which has 313 branches. My Estes men fall into a haplogroup several steps beneath R-M173, but they are still members of haplogroups R-M173 and R-M207, even though their descendant haplogroup is R-BY490, which was formed by a mutation that occurred 20,000 years later.

Haplogroup R-M173, then, in turn, leads back to Y-Adam, the first man to have lived and has descendants today.

As we approach the question of why haplogroups of two men might differ, we will review tools to use and how to interpret your findings to reach the appropriate answer for your situation.

What is Your Goal?

You may be looking for a very specific answer, or this may be a more general question.

  • If you’re evaluating closely related men who have different haplogroup assignments, not matching can be very disconcerting. Breathe. There are several perfectly legitimate reasons why they may not match, and we have easy, free analysis tools.
  • If you’re looking at your Y-DNA match list at FamilyTreeDNA, you may or may not match other men closely, but you do “match” at some level if they are on your match list. You may see several different haplogroups in your match list. How closely you match those men is a different question.
  • If you’re looking at autosomal results at FamilyTreeDNA, you may see haplogroups listed for males. You may or may not “match” the haplogroup of men with the same surname. What does this mean, and why don’t you match? Your autosomal match may have nothing to do with your paternal line, or it may be because of your paternal line.

We will cover all of these scenarios.

Where Did You Both Test?

  • Are you comparing apples and apples?
  • Did you both test at the same company?
  • Did you both take the same type or level of test?

These factors all make a difference.

Which Test Did You Take?

There are four types of tests that will provide males with some level of Y-DNA haplogroup.

Autosomal Tests – Some companies include a few Y-DNA location probes in their autosomal test, meaning that they test a few haplogroup-specific Y-DNA locations. LivingDNA, 23andMe, and FamilyTreeDNA’s Family Finder test provide a mid-level Y-DNA haplogroup to customers. The haplogroup that can be determined from these tests depends on a variety of factors, including the vendor, the probes they selected for their chip, the test version, and if that location is successfully read in the test.

Note that FamilyTreeDNA supports autosomal uploads from MyHeritage and Ancestry who do not provide Y-DNA haplogroups to customers, but who do test some Y-DNA locations. Therefore you can upload your autosomal test from those companies to FamilyTreeDNA for free and receive at least a cursory Y-DNA haplogroup.

FamilyTreeDNA is currently processing all of its Family Finder tests, followed by tests uploaded from other vendors, to provide all genetic male testers with a Y-DNA haplogroup at some level. Different vendors and test versions test different Y-DNA SNPs, so your mileage may vary. Y-DNA haplogroups are a free benefit at FamilyTreeDNA.

STR Tests – At FamilyTreeDNA, you can purchase both Y-37 and Y-111 STR (short tandem repeat) Y-DNA tests that provide matching at the number of locations you purchased, plus a predicted haplogroup based on those results. These haplogroup predictions are accurate but are often relatively far back in time.

If you match someone on STR tests, your match may be very recent or before the advent of surnames. For a more specific haplogroup, you need to purchase the Big Y-700 test, which provides at least 700 STR match locations but, more importantly, sequences the entire gold-standard region of the Y-chromosome for the most precise haplogroup and matching possible.

  • When viewing matches of two men who ONLY took STR tests, STR marker matches are more important for genealogy than haplogroups because the haplogroups were formed thousands of years ago.
  • When viewing matches on the Big Y-700 test, haplogroup matching is much more specific and reliable than STR matches because the mutations (SNPs – single nucleotide polymorphisms) that form haplogroups are much more stable than STRs which mutate unpredictably, including back mutations.

SNP Confirmation Tests – Historically, FamilyTreeDNA customers could purchase individual SNPs to confirm a haplogroup, or SNP packs or bundles to do the same for a group of SNPs. With the advent of both the Family Finder haplogroup assignments, and the Big Y-700, these individual tests are no longer necessary or advantageous and are being discontinued.

Big Y-700 Test – At FamilyTreeDNA, the Big Y-700 test provides the most granular and specific haplogroup possible, most often well within a genealogical timeframe. You may be able to tell, based on previously undiscovered mutations, that two people are brothers or father and son, or, depending on who else has tested and when mutations formed, testers may match further back in time. Here’s an example of using the results from multiple testers in the Estes DNA Surname Project.

You can also match men who took the Big Y-500 test which is less specific than the Big Y-700. In the now-obsolete Big Y-500 test, a smaller portion of the Y chromosome was sequenced and testers only received about 500 STR locations. The Big Y-700 test has been enriched to provide a wider range of more specific information. Men who originally took the Big Y-500, then upgraded to the Big Y-700, will very probably have a new haplogroup assignment based on the expanded coverage and increased resolution of the Big Y-700 test. The Big Y-700 ferrets out lineages that the Big Y-500 simply could not, and continues to provide additional value as more men test, which facilitates the formation of new haplogroups.

What Do You Mean by Match?

Matching doesn’t mean you have to have the exact same haplogroup. A perfectly valid match can have a different haplogroup because one haplogroup is more specific or refined than the other. Matching exactly as a result of a predicted STR haplogroup is much less useful than matching closely on a much more recent Big Y-700 haplogroup.

Not all haplogroups are created equal.

I know this is a bit confusing, so let’s look at real-life examples to clarify.

STR to STR or Autosomal to Autosomal Haplogroup Match

Two males might match exactly on a mid-range Family Finder autosomal haplogroup or on a STR-predicted haplogroup like R-M269, which is about 6350 years old.

This haplogroup “match,” even though it might be exact, does not confirm a close match and really only serves to eliminate some other haplogroups and confirm that a closer match is possible. For example, R-M269 men don’t match someone in haplogroup J or E. You may or may not share a surname. You may or may not still “match” if you both upgrade to the Big Y-700.

In this case, a father/son pair would match exactly, as would two men with different surnames whose common ancestor lived 6000 years ago.

Note that if you’re comparing autosomal-derived haplogroups across different vendor platforms, or even different DNA testing chip versions on the same platform, you may see two different haplogroups. Different vendors test different locations. Please note that second cousins and closer will always match on autosomal DNA, but relationships further back than that may not. Y-DNA very reliably reaches far beyond the capabilities of autosomal DNA due to the fact that it is never mixed with the DNA of the other parent – so it never divides or is watered down in time. When comparing two autosomally-generated haplogroups of men who are supposed to be closely related, always check their autosomal match results too.

Use the free Discover Tool to find various categories of information about any haplogroup, including its age. Take a look at R-M269 here.

Using Discover to Compare Haplogroups

You can always use the Discover tool to compare two haplogroups.

Go to Discover (or click through if you’re signed on to your FamilyTreeDNA Y-DNA page), then enter the first haplogroup you’d like to compare.

Click search to view information about that haplogroup.

On the menu bar, at left, click on Compare.

Add the second haplogroup.

I’m selecting E-M35, a completely different branch of the phylogenetic tree.

R-M269 was formed about 6350 years ago, while E-M35 was formed about 25,000 years ago. Their common ancestor was formed about 65,000 years ago. Clearly, these two paternal lineages are not related in anything close to a genealogical timeframe.

These two men would never match on an STR test, but could easily match on an autosomal test on any line OTHER than their direct paternal line.

Now let’s compare two haplogroups that are more closely related.

Haplogroup R-M222 is very common in Ireland, so let’s see how closely related it is to R-M269 which is very common in western Europe.

We see that R-M222 descends from R-M269, so there is no “other haplogroup” involved.

R-M222 was formed about 2100 years ago, around 4250 years after R-M269 was formed.

There are 17 steps between R-M222 and R-M269.

The bottom block shows the lineage from R-M269 back to Y-Adam.

How cool is this??!!

Big Y-700 to Autosomal or STR Haplogroup Comparison

Joe took the Big Y-700 test and discovered that he’s haplogroup R-BY177080.

Joe noticed that his son, who had initially taken an STR test, had been assigned haplogroup R-M269. Then, his son took a Family Finder test and his haplogroup changed to R-FGC8601.

Joe was confused about why he and his son’s haplogroups didn’t match.

First, let’s check Family Finder to confirm the parent/child relationship. Joe’s son is clearly his son.

So why doesn’t Joe’s son’s haplogroup match Joe’s haplogroup? And why did Joe’s son’s haplogroup change?

Joe’s son had not taken a Big Y-700 DNA test, so Joe’s son’s R-M269 haplogroup was initially predicted from his STR test.

Joe’s son’s updated haplogroup, R-FGC8601 was generated by the Family Finder test. Think of this as a bonus. If you’re a male and haven’t yet, you’ll soon receive an email telling you that you’ve received a Family Finder Y-DNA haplogroup. It’s your lucky day!

Family Finder haplogroups always replace STR predicted haplogroups since they are always more specific than predicted STR haplogroups. Big Y-700 haplogroups always replace STR-generated haplogroup predictions and Family Finder haplogroups because they are the most specific.

Let’s compare these results using Discover.

Joe’s son’s original predicted haplogroup was R-M269.

Discover Compare shows us that Joe’s Big Y-700 Haplogroup, R-BY177080, is a descendant of R-M269.

So, they actually do “match,” just several branches further up the tree

Joe’s son’s more precise Family Finder haplogroup was assigned as R-FGC8601.

Discover Compare shows us that Joe’s Big Y-700 haplogroup also descends from R-FGC8601.

You can see that the haplogroup generated by Family Finder is more precise by about 4700 years and improves that comparison.

R-M269 was formed about 6350 years ago, but R-FGC8601 was formed about 1700 years ago.

Joe’s Big Y-700 haplogroup, R-BY177080 was formed about the year 1900, improving the family haplogroup by another 1600 years or so.

Joe’s son’s Family Finder haplogroup moved down the haplotree 21 branches and 4650 years, for free! If Joe’s son were to upgrade to the Big Y-700, they might very well be assigned a new haplogroup that, for the time being, only they share.

Of course, Family Finder doesn’t provide Y-DNA matching so you still need the Y-DNA tests for that important aspect of genealogy.

Big Y to Big Y Comparison

In our next example, a group of men, including a father and son or other very close relative may take the Big Y-700 test and have different haplogroups. If you’re saying, “Whoa Nelly,” hear me out.

George took a Big Y-700 test and discovered that he is haplogroup R-FGC43597. His son and grandsons tested, and they are haplogroup R-FTC50269. What happened? Shouldn’t they all match George?

On George’s Big Y-700 block tree, you can see that a mutation, R-FTC50269, occurred between George and his son. George doesn’t have it, but his son does.

A haplogroup isn’t “named” until there are two men with the same mutation in the same lineage. Therefore, when George’s son initially tested, he would have been assigned to the same haplogroup as George, R-FGC43697, but with one extra variant, or mutation.

Of course, that extra mutation was passed from George’s son to both of his grandsons, so when the first grandson tested, the new haplogroup, R-FTC50269 was assigned as a result of that mutation. Now, George has one haplogroup and his son and grandsons have a different haplogroup, one branch downstream.

Using Discover to check the haplogroup ages and path, we find that indeed, these haplogroups are only one step apart.

Checking Family Finder results can always verify that the match is close or as close as you expected.

Haplogroup Assignments

Haplogroup assignments range from good to better to best.

Good Better Best
STR predicted Yes – but further back in time
SNP Packs (now obsolete) Between good and better
Family Finder autosomal Yes – generally midrange between STR predicted and the Big Y-700
Big Y-500 (need to upgrade) Usually between better and best
Big Y-700 The best – usually within a genealogically relevant timeframe unless your DNA is rare

Where Are You?

Older haplogroups, such as the STR-predicted haplogroups are useful for:

  • Eliminating some potential matches
  • Identifying where that haplogroup originated at that specific point in time. In other words, where your ancestor lived when that haplogroup was born.

If your Y-DNA matches another Y-DNA tester at FamilyTreeDNA, your haplogroups will fall someplace on the same haplogroup branch, although they may be thousands of years apart. STR-predicted haplogroups are “older,” meaning they range in age from about 6500 years to tens of thousands of years ago. They can tell you where the haplogroup originated at that time.

Autosomal haplogroups will be newer, or more recent, than STR-predicted haplogroups, but still (sometimes significantly) older than the Big Y-700 haplogroups..

FamilyTreeDNA provides Y-DNA haplogroups for free for every biological male who either takes the FamilyTreeDNA Family Finder test or uploads an autosomal result from either Ancestry or MyHeritage. Soon, 23andMe uploads will be resumed as well. This means that you will be able to view other men with a similar surname in your Family Finder results and:

  • Rule them out as a paternal line match.
  • Check your STR matches if they have taken a Y-DNA test
  • Check your Big Y-700 test for matches if both men have taken a Big Y test.
  • Encourage your matches to take a Big Y-700 test so you can see how closely you match on your paternal line.
  • Use the Discover Compare and other tools to reveal more information.

Family Finder haplogroups are relatively new, so currently, all new Family Finder testers are receiving haplogroups. Older Family Finder tests are being processed and will be followed by autosomal tests uploaded from other vendors. Haplogroups from autosomal tests are confirmed and will be newer, or more recent, than STR-predicted haplogroups.

The only test that can bring your haplogroup to current, meaning the most refined, recent, personal haplogroup, is the Big Y-700 test. Without taking the Big Y-700 test, you’ll forever be stuck with an older, less informative haplogroup branch. The Big Y-700 allows us to reliably sort families into lineages based on branching mutations.

The Big Y-700 haplogroup is:

  • The most detailed and granular possible.
  • Determined by sequencing the Y chromosome.
  • A test of discovery that continues to provide additional value as more men test and new haplogroups are formed.

Big Y-700 haplogroups generally fall into a genealogically useful timeframe and can be very recent.

The Discover tool and Time Tree provide a wealth of information about your ancestors, including locations, migration paths, ancient DNA, and more.

You Don’t Know What You Don’t Know

Now that you understand how to compare and interpret haplogroup matches, what additional information can you learn?

I always encourage Y-DNA matches to upgrade to the Big Y-700. Why? You don’t know what you don’t know. The article, Bennett Greenspan: Meet My Extended Family & Discover Extraordinary Deep Heritage illustrates the benefits of the Big Y-700 for all matches. Upgrading 12-marker matches is exactly how he made his big breakthrough.

The Big Y-700 test answers many questions beyond simply matching by using Discover and the Group Time Tree.

  • Where were your ancestors?
  • Who do you match, and who were their ancestors?
  • Genetically and genealogically, how do your surname matches fit together?
  • Where were your matches’ ancestors, and when?
  • Which ancient DNA results do you match, and where were they located?
  • What is the history of locations where your ancestors were found along their journey?
  • How closely or distantly are you related to other Big Y-700 matches?
  • Can your matches’ information break down your paternal line brick wall, or at least move it back a few generations?

Where are your Y-DNA results along the spectrum of useful haplogroup information? Do you or your matches need to upgrade? Click here to upgrade or order a Big Y-700 test.

______________________________________________________________

Sign Up Now – It’s Free!

If you appreciate this article, subscribe to DNAeXplain for free, to automatically receive new articles by e-mail each week.

Here’s the link. Look for the black “follow” button on the right side of your computer screen below the black title bar, enter your e-mail address, and you’re good to go!

In case you were wondering, I never have nor ever will share or use your e-mail outside of the intended purpose.

_____________________________________________________________

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 Book

Genealogy Books

Genealogy Research

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

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

Bennett Greenspan

“And yes, I brake for cemeteries.”

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

12-Marker Matches

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

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

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

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

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

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

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

What Happened in Spain?

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

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

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

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

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

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

How does this actually apply to Bennett’s results?

Bennett’s Spanish Matches

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

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

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

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

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

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

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

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

DNA Plus History

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

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

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

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

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

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

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

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

Contacting Matches

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

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

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

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

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

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

Upgrade Request

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

Bennett’s email:

Hello <name>,

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

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

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

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

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

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

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

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

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

Best,

Bennett Greenspan

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

What’s Next?

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

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

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

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

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research