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

In the first three articles of this series, we:

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

I suggest reading these articles in order.

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

Multiple Levels of Information

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

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

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

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

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

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

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

Matches are the Backbone of DNA Testing

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

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

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

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

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

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

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

Y-DNA Testing and Matching Levels

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

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

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

12-111 STR Panel Matches

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

Click any image to enlarge

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

Not everyone has tested at that level.

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

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

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

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

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

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

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

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

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

More Hints on the Matches Page

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

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

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

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

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

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

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

Mitochondrial DNA Matching

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

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

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

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

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

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

About Haplotype Clusters

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

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

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

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

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

I wrote about haplotype clusters here and here.

Identifying Sophia

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

First, breathe.

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

Panning for Gold

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

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

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

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

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

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

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

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

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

A Genetic Detour

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

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

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

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

So far, so good.

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

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

Caution – Don’t Jump!

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

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

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

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

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

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

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

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

Matches Map

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

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

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

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

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

The Matches Map utilizes the location entered for your EKA.

Add Your Earliest Known Ancestor and Locations

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

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

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

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

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

The Difficult Moore Line

Let’s look at a much more difficult scenario.

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

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

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

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

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

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

Using Discover’s Compare feature, we find that:

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

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

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

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

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

Y-DNA Plus Family Finder Yields More Hints

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

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

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

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

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

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

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

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

However, we’re not done.

Advanced Matching

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

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

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

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

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

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

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

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

However, this possibility absolutely warrants additional investigation.

Big Y Matching

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

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

Big Y Block Tree

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

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

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

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

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

Discover

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

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

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

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

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

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

The Match Time Tree

The Match Time Tree is one of my favorite reports.

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

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

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

Additional Bonuses:

  • Ancient Connections
  • WikiTree Connections and lineages

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

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

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

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

Ancient Connections

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

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

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

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

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

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

Notable Connections

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

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

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

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

Globetrekker™

Screenshot of Globetrekker™ video

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

Haplogroup locations and connecting lines or paths are based on:

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

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

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

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

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

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

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

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

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

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

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

Suggested Projects

Suggested Projects can also provide clues.

Projects are suggested for one of three reasons:

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

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

Mitochondrial DNA Match Time Tree Haplotype Clusters

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

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

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

I’ve written about haplotype clusters here and here.

Your Summary Checklist

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

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

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

Your ancestors are waiting for you to find them!

_____________________________________________________________

Share the Love!

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

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

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

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

These two articles detail the initial steps:

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

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

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

This Type of Searching Is Different

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

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

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

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

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

Chicken or Egg?

I’ve been debating whether I should show you:

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

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

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

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

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

Let’s jump right in!

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

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

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

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

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

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

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

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

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

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

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

Complete Versus Partial Tests

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

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

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

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

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

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

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

Click any image to enlarge

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

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

Upgrades for Partial Tests

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

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

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

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

Test Features at Various Levels

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

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

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

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

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

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

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

 

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

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

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

Now we can envision:

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

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

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

Finding Your Ancestor’s Mitochondrial and Y-DNA

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

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

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

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

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

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

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

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

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

But I Don’t Know of Any Cousins…

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

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

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

Why is this so important?

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

Who Has Tested for Your Ancestor?

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

This can sometimes be challenging.

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

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

WikiTree

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

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

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

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

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

I’m Googling:

Barbara Mehlheimer born 1822 died 1906 in Indiana at WikiTree

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

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

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

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

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

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

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

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

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

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

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

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

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

Searching for a Test Candidate Using Autosomal Descendants

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

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

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

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

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

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

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

Finding Your Ancestor’s DNA Descendants at WikiTree

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

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

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

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

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

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

Click on the DNA Descendants tab.

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

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

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

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

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

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

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

Kit Numbers, Earliest Known Ancestors and Google

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

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

“9993” site:familytreedna.com

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

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

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

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

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

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

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

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

nicholas ewstas site:familytreedna.com

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

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

catherine lejeune site:familytreedna.com

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

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

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

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

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

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

At 23andMe

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

At FamilyTreeDNA

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

Project Search

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

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

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

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

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

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

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

Group Project Time Tree

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

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

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

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

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

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

Click to enlarge

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

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

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

Let’s look at an example.

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

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

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

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

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

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

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

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

Finding Projects in Discover

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

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

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

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

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

Search for Surnames in Family Finder Autosomal Matches

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

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

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

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

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

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

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

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

Let’s begin with searching for haplogroup T2b.

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

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

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

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

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

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

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

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

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

Utilizing Haplogroup Projects

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

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

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

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

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

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

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

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

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

Let’s see if Ancestry can help.

At Ancestry

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

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

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

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

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

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

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

These people are all autosomal DNA matches.

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

Compare Trees is New

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

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

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

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

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

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

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

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

MyHeritage has one of my favorite tools.

At MyHeritage

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

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

Cousin Finder

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

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

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

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

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

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

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

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

I didn’t forget about Eva Miller Ferverda either.

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

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

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

Who doesn’t love a pleasant surprise?!

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

At FamilySearch

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

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

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

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

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

Living people have no placeholders on this tree.

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

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

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

Relatives at RootsTech

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

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

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

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

At GEDmatch

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

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

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

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

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

Where AM I?

OK, so where am I in all of this?

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

I’ve primarily used two examples.

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

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

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

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

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

Communicating With Testing Candidates

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

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

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

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

Scholarships

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

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

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

Good luck on your treasure hunt!

____________________________________________________________

Share the Love!

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

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Ancient Connections: Where Archaeology Meets Your Ancestors

Ancient Connections, a report found on FamilyTreeDNA’s Discover platform for both Y-DNA and mitochondrial DNA (mtDNA), can be used in multiple ways to enhance your genealogy and unlock secrets.

It’s exciting to examine ancient burials linked to our ancestors and understand how we connect to them. Ancient Connections offer a wealth of information, providing clues that can help unravel long-standing mysteries.

Today, there are more than 12,960 Y-DNA Ancient Connections in Discover, along with more than 25,310 mitochondrial Ancient Connections, and that number increases weekly.

Why the disparity, you ask? Remember, everyone has mitochondrial DNA, but only males have Y-DNA.

In addition to matches, your DNA results hold something even more powerful – evidence of where your ancestors and their cousins lived in the distant past, when they lived, and the cultural context surrounding them. These essential insights are unavailable through any other means. Ancient Connections help us answer the age-old question, “Where did I come from?”

Could These People Be My Ancestors?

I’ll show you how to answer another question, too. Which of these Ancient Connections could potentially be your ancestors, and which ones are your “haplo-cousins”?

Regardless, they all help us understand our ancestors’ past, and that of their descendants.

Discover is for Everyone

FamilyTreeDNA provides a free version of Discover that everyone can use. There’s also an enriched version with additional information for their customers who have purchased Y-DNA and mitochondrial DNA tests.

Discover has something to offer for everyone.

Mitochondrial DNA is passed from mothers to all of their children of both sexes – unmixed with the DNA of the father.

Everyone has their mother’s mitochondrial DNA, which is passed intact, except for an occasional mutation, directly down through generations of mothers. It’s not admixed like autosomal DNA, so we don’t lose some portion in each generation. This is exactly why we can track mitochondrial DNA infinitely far back in time and why it’s so crucial for understanding the origins of your mother’s specific line.

Y-DNA is passed from fathers only to their sons, which is what makes males male. Like mitochondrial DNA, Y-DNA is not admixed with any DNA from the mother, so we get a laser line-of-sight view of the direct patrilineal line back in time. The Y-DNA direct paternal line is the male’s surname line in cultures where males carry their father’s surname.

If you’ve tested at or upgraded to either the Big Y-700 level or the mtFull, full mitochondrial sequence test, you will receive the most granular haplogroup possible, meaning the closest in time and most informative. You’ll also match with other testers who have taken the less-refined lower-level tests.

The most informative and precise results occur when both people have taken the premium tests. As more people test and science advances, you may receive a new haplogroup from time to time when you and another tester share a rare mutation – so these tests are evergreen.

Both Y-DNA and mitochondrial DNA testers at any level have access to Discover on their dashboard for those products, although the results of lower-level tests provide less information.

The Free Version of Discover Compared to the Premium Version for Testers

Here’s a comparison of lower-level Y-DNA tests and the Big Y-700.

Click any image to enlarge

Y-DNA testers who have only taken the 12-111 STR panel tests receive a predicted haplogroup, and when clicking through to Discover, receive up to 10 Ancient Connections.

For example, If your Y-DNA haplogroup is predicted as R-M269, the most common male lineage in Europe that arose some 6450 years ago, your Ancient Connections begin with the closest genetic match to R-M269. Viewing Ancient Connections that are 6500 years ago will certainly be interesting, so please do look, but probably not terribly useful for genealogy.

However, if that same person were to upgrade to the Big Y-700, they would receive a much more recent haplogroup, and along with it, up to 30 Ancient Connections within their major haplogroup lineage, R in this case, plus the oldest sample in the database. For some haplogroups, there may not yet be 30 Ancient Connections, although new ancient samples are added weekly for both Y-DNA and mitochondrial DNA.

All Ancient Connections begin with the matches who are genetically closest to the haplogroup requested.

The same scenario holds true for mitochondrial DNA testers who previously tested at the HVR1/HVR2 level, but not at the full sequence level, which is the only test available today.

This article focuses on testers at the higher levels, meaning the Big Y-700 and the mtFull tests, and how to utilize their 30 closest Ancient Connections. We’ll walk through step-by-step examples using both.

However, before we begin evaluating our Ancient Connections, we need to cover two fundamental concepts.

BCE, CE and Converting to “Years Ago”

It’s helpful to understand date structures and how they are used.

It’s easy to get confused when seeing the dates of CE, current era, and BCE, before current era, which means we misinterpret the information.

For example, the year 100 CE is the year 100 that occurred roughly 1900 years ago. We round 2026 to 2000 for these types of calculations. The year 100 BCE, before current era, occurred approximately 2100 years ago. I often prefer to work in “years ago”, because it equalizes the numbers, meaning you’re less likely to get confused about how long ago someone lived or something happened.

To do the calculations from BCE dates to “years ago,” add 2000, so 2250 BCE equals 4250 years ago.

For CE dates, subtract from 2000. The date 500 CE occurred 1500 years ago.

This can be especially confusing when you’re dealing with the same number on either side of the current era, which began in the year 1. There is no year zero. For example, we need to be vigilant not to confuse 500 BCE, which was 2500 years ago, and 500 CE, which was 1500 years ago.

Now, on to our second concept.

Haplogroup Age and Burial Age Are Not the Same

When viewing Ancient Connections, the genetic age of the haplogroup, meaning when it was formed, and age of the burial are two different things.

Haplogroup R-ZP18 is about 4250 years old, and this Late Iron Age, pre-Roman burial which is also R-ZP18, occurred about between 2337 and 2043 years ago.

Haplogroup ages and the date they emerged, which show on the Timeline, sometimes mature and are refined with additional testers and branching.

Burials are dated using various techniques, and sometimes the ages provided in the academic papers are earlier than the genetic age of the haplogroup, shown on the Timeline at the bottom of the Connections page.

Discover makes no attempt to “fix” this situation, because it’s unclear which age should be changed. It’s not unusual to be unable to fully analyze ancient remains. For example, let’s say a sample is determined to have the SNP for R-ZP18, but simultaneously lacks downstream SNPs and some upstream SNPs, and the burial was dated from surrounding soil or artifacts. In that case, it would be impossible to know what is precisely “accurate”, but the sample is accurate enough to be included in Ancient Connections. This is also why some samples aren’t included in Globetrekker™ calculations. Some low-quality samples are excluded entirely.

Every ancient sample is individually analyzed by R&D team members before being included in the phylogenetic tree and Ancient Connections. Sometimes, the scientists at FamilyTreeDNA can assign a more specific haplogroup than was available to the paper authors at the time of publication because the tree has since branched.

As you receive new Ancient Connections, your older ones, except your final or oldest connection, will roll off of your list.

That’s one reason I devised a process for analyzing and recording my Ancient Connections, and for determining which ones might be actual ancestors – or at least aren’t precluded from it.

First Peek at Ancient Connections

Sign in to your FamilyTreeDNA account and click on the Discover link on the dashboard for the type of test you wish to view.

In the Y-DNA example, I’m using my male Estes cousins. As a female, I can’t test for the Estes Y chromosome, so I recruited others to represent my line. You can see the results in the Estes DNA project.

After signing in, click on Discover, then on Ancient Connections.

Y-DNA Ancient Connections 

It’s a bonanza!

Your Ancient Connections are displayed at the top of the page, ordered from genetically closest to most distant. These are archaeological samples whose data has been extracted from academic papers and analyzed before being include in Discover.

You’ll see a description of the first sample, or any sample you click on. The Timeline for that sample, along with your haplogroup and your common ancestor’s haplogroup, is displayed at the bottom of the page.

The first, meaning closest, Ancient Connection is highlighted, so let’s take a look.

  • “You” are shown in the dark purple frame (with purple arrows) at right, with your haplogroup, in this case R-ZS3700, which is placed on the Timeline at the bottom of the page in the appropriate location.
  • The Ancient Connection named “North Berwick 16499”, whose name was taken from the academic paper in which it was found, is shown in a red frame and placed on the timeline based on information provided in the paper.

“North Berwick” has been assigned to haplogroup R-ZP18, either in the paper, or by the FamilyTreeDNA R&D team if a more refined haplogroup can be determined, and is this tester’s closest Ancient Connection based on its position on the list.

Note that you may have other Ancient Connections who are genetically equivalent in age, meaning they too would be R-ZP18. In our case, only one sample is assigned to that haplogroup.

  • Your Shared Ancestor, in the green frame, is the first man who carried R-ZP18, which emerged about 2250 BCE, or 4250 years ago.

Notice that I said, “the first man.” That man’s sons, grandsons and so forth were also haplogroup R-ZP18. Some went on to develop new downstream haplogroups, but apparently, North Berwick, by the time he lived, had not. Either that, or a downstream haplogroup cannot yet be determined due to a lack of other testers in that lineage.

Men with downstream SNPs (mutations), meaning downstream haplogroups, also descended from R-ZP18. Those SNP mutations become downstream haplogroups when two or more men who carry the same SNP mutation match each other. For example, our Estes ancestor who carries haplogroup R-ZS3700 descends from R-ZP18 through a distinct series of downstream SNPs (mutations). While we carry R-ZP18 in our lineage, it’s not our most refined haplogroup.

However, for North Berwick, haplogroup R-ZP18 is his most refined haplogroup.

Because of this, we know for sure that North Berwick and the Estes men both descend from the original R-ZP18 man who lived about 4250 years ago, but we can’t tell when they shared a common ancestor between 4250 years ago and 3750 years ago when the next downstream haplogroup R-BY342, was formed in the Estes lineage.

Because North Berwick does not belong to a different downstream haplogroup, it’s genetically possible that the Estes men could descend from him during that 500-year timeframe. There’s nothing to exclude that possibility based on his haplogroup alone, but looking at when North Berwick lived is another matter.

North Berwick lived between 2337 and 2043 years ago, which is 1400 years LATER than when the first downstream haplogroup, R-BY342 was formed, about 3750 year ago, in the Estes lineage. This precludes North Berwick from being our direct ancestor. Instead, he’s our “haplocousin.” We share a common upstream ancestor.

What we absolutely CAN confirm, though, is that between 500 and 1300 years earlier than North Berwick lived, between when haplogroups R-BY342 and R-ZP18 were formed, both North Berwick and our Estes ancestor descended from the same man.

This kind of information is like waving a red flag in a genealogist’s face. We immediately need to know more.

This is just the beginning, and we have so many questions!

Revealing More Information

Did our common ancestor live in or near North Berwick, or someplace else? What do we know about the history of North Berwick?

What can we discern about North Berwick?

  • When did this man live, and where?
  • What do we know about him?
  • Who was he?
  • Did he live close to where my earliest known ancestor in this line is found?
  • What can I tell about his culture?
  • Were there grave goods that provide at least a peek into his life?

So many questions!

Discover tells us that he lived between 337 and 43 BCE, so between 2337 and 2043 years ago, during the Late Iron Age, and is associated with the Iron Age Britain cultural group.

The Ancient Connections “Reference” provides information about the paper where the North Berwick sample was found. No links are provided because sometimes the paper is behind a paywall, and you can’t access it without paying, and sometimes it’s a preprint and will appear later elsewhere. Sometimes one paper actually uses data from an earlier paper, and it gets complicated.

The first thing I do is Google the paper – Patterson et al. 2022. Google provides two links – one that’s free, and one that isn’t. Many times, the sample data is found in the supplementary material, which may also be behind a paywall, even if the paper isn’t.

I know you’re going to think it’s a pain, but I strongly encourage you to read every paper, though sometimes they can be challenging to understand, so read them when you’re fresh, not tired, and can concentrate. If nothing else, at least read the abstract. There’s so much great information buried in academic papers, including nice maps and discussions of the burial site. You can also learn more sometimes by Googling the burial site itself.

Let me give you an example from this paper’s abstract. I’ve added the brackets [ ] for clarity, from the body of the paper:

Between 1000 and 875 BC[E], EEF [Early European Farmer] ancestry increased in southern Britain [England and Wales] but not northern Britain [Scotland] due to incorporation of migrants who arrived at this time and over previous centuries, and who were genetically most similar to ancient individuals from France. These migrants contributed about half the ancestry of people of England and Wales from the Iron Age, thereby creating a plausible vector for the spread of early Celtic languages into Britain.

How does this information align with our North Berwick man? He lived between 2337 and 2043 years ago, and the EEF ancestry increased in southern Britain between 3000 and 2875 years ago. The authors do add “over previous centuries” which probably accounts for the 500-year gap and gets closer to when R-ZP18 lived. North Berwick is found in Scotland, not England or Wales, so not part of the group of people most closely aligned with the ancient French migrants from this timeframe. Maps in the paper confirm this as well.

Googling the paper and sample name provided additional sourced information. This paper incorporates samples from earlier papers and performed a different type of analysis.

Ironically, I wrote about this in detail in 2022, here, before Discover was introduced, so I had absolutely no idea that North Berwick 16499, discovered on Law Road in North Berwick, was related to my ancestors, and therefore, to me.

In that article, I researched and mapped the samples. North Berwick 16499 is located on the coast, along the harbour, not far from Edinburgh.

The burial was excavated in the cemetery of the original St. Andrew’s Church in North Berwick, originally built in the 1100s, but now in ruins.

This paper’s supplementary material explains that:

Excavation of a substantial square cist at Law Road, North Berwick, uncovered the remains of four inhumations of Late Iron Age date (Richardson et al. 2005). Two adult males 3603 (Skeletons C46 and C51) and a female around 16–18 years of age at death (Skeleton C50) appeared to have been displaced for the burial of an adult female (Skeleton C47), wearing an iron brooch. One of the males (C46) had been buried with a bone-handled iron knife.

What I wouldn’t give to see that iron brooch and bone-handled knife.

C51 is North Berwick 16499, “our” skeleton. A cist grave is a small, stone-lined burial box, and this one was preserved beneath medieval deposits.

That reference gave the even more precise location of Law Road and St. Andrews Street and informs us that the remains are held by National Museums Scotland. Checking their collections confirms that they hold these items, plus the bones. However, there are no photos shown. Contacting them for images might yield results.

What the paper did not say is that little was known prior to these excavations about early North Berwick.

By Stefan Schäfer, Lich – Own work, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=19450589

North Berwick was known to exist as a ferry landing from the 7th century, but an archaeological survey of Berwick Law, a hill that overlooks the town, revealed much earlier information:

The earliest features on North Berwick Law comprise a pair of newly discovered cup-marked rocks and the scanty remains of a prehistoric hilltop fort discovered by RCAHMS (1957, xv), whose outworks appear to be more limited than suggested by previous authorities (Feachem 1963, 119; OS 1975). The lower SW flank of the Law is dotted with the remains of a prehistoric settlement comprising at least 12 hut circles or house platforms and fragments of an associated field system of small cairns and banks.

Unfortunately, the perimeters of Berwick Law have been settled and farmed since, and the hilltop has served recently in the same capacity as it probably served initially – as a lookout across the firth. The residents would have been watching from this highest point for invaders arriving by sea.

It’s about half a mile from the foot of the hill to the burial cist.

The survey also mentioned that they found “stray bronze age finds” that had likely been disrupted by subsequent settlement. The bronze age in Northern Scotland began about 4200 years ago, about the time that R-ZP18 lived, until about 2800 years ago. Whoever North Berwick 16499 was, the man who was buried here some 2400 years ago, he was probably associated with this hilltop fort, perhaps farming at the base, probably living in one of those huts or nearby. His body wouldn’t have been taken far for burial.

We are left to wonder how long his family had lived here, and how they had arrived. Was his cist burial a sign of status? Was he sent to commend the fort, or had his family settled here centuries earlier? Did our ancestor descend from this location, too?

After our analysis, we know that our ancestor did not descend from North Berwick 16499 himself, but North Berwick definitely descended from our ancestor.

If you’re thinking this is a rabbit hole, it definitely is – but what a rabbit hole! There is so much to be gleaned from these Connections.

The Evaluation Process

I needed a process to keep track of these Ancient Connections, my findings, and how they relate to my Estes ancestors. Who begat, or might have begat whom, and where?

I created a spreadsheet as I read and analyzed each Ancient Connection relative to my ancestral line. I include what I know about it, and what I THINK I know about it. Those can be two vastly different things. I follow this same process for every ancestral line where I can find a representative Y-DNA or mitochondrial DNA tester.

For example, there’s a persistent rumor that the Estes family line descends from the d’Este family of Italy. That rumor was spun up long before we had genetic proof that our line was found in Kent, England, in records dating back to about 1495. Fortunately, church records, for the most part, and some civil records still exist.

The first known record is the will of our Nycholas Ewstas written on January 1, 1533/1534 in Deal, Kent, England. We confirmed that this is our Estes line by testing the Y-DNA of his descendant who still lives a few miles up the road, compared with the descendants of Abraham Estes (1647-1720), the man who immigrated to Virginia in 1673. We believed that Abraham Estes, who married in 1672, then immigrated 14 months later, was one and the same person.

Based on the details of the d’Este rumor, the Estes line was supposed to descend from one Francesco d’Este (Esteuse), an illegitimate royal son, exiled to France about 1471 after the death of his father, Azzo VI of Este, by a jealous half-brother, complete with a royal allowance. There are mentions of him in the Dutch and French courts, then nothing. Silence.

Apparently, various Estes lines in England liked the idea that he crossed the English Channel and settled in the fishing village of Deal, with his descendants carrying the surname Estes, a derivative of d’Este. King James apparently believed there was a connection and made that suggestion himself in one instance, although it’s unclear if that Estes man was from our Estes line.

It’s difficult to prove a negative, so we need to rely on the evidence we do have, much of which has been discovered and accumulated in more recent years, since the genesis of that rumor which was widely believed.

To begin with, it makes no sense that between 1471 and 1495, the family suddenly went from being a wealthy exiled royal circulating at court in France and the Netherlands, to peasant fishermen on the coast across the channel.

There is a legitimate royal lineage that does descend from the d’Este family in Italy, but until and unless someone who is a descendant of the direct male line of the House of Hanover, which reaches back to the Azzo line of Ferrara, takes the Y-DNA test, there’s no proof positive. Either their Y-DNA would match the Estes line, or not. I’d wager that it does not, but I’d love to find out for sure.

I’m hopeful that some nugget in Ancient Connections might add weight to either side of the argument.

Creating a Spreadsheet

First, I’ll show you the Ancient Connections spreadsheet built for the Estes line, then I’ll demonstrate how to build it.

Here’s the finished spreadsheet. Every haplogroup’s spreadsheet will be different.

I placed the four confirmed Estes haplogroups at the bottom because that’s the base from which the Ancient Connections are built, beginning with the closest Connection first.

“My” haplogroup, meaning for my ancestor’s Estes male line, is R-ZS3700, but there’s one additional downstream haplogroup, which I’ve included for completeness.

Let me alert you now that you WILL receive new Ancient Connections, which means that for every new Connection you receive, one more distant Connection rolls off the end because it’s outside of your 30 genetically closest Connections threshold. I’ve received new Ancient Connections in the past three months, between the time I originally began gathering this information and when I published this article.

The underlying message, in addition to maintaining your spreadsheet, is to set a calendar alert to check your Ancient Connections regularly. One rolled off that was more distant genetically, but was located only 10 miles away from where my Estes ancestors originated in Deal, England.

We’ll build the spreadsheet so you can easily expand it as new Connections are added.

Also, note that you may receive multiple matches from the same archaeological excavation site, which, of course, is highly suggestive of a family. If the multiple burials are in the same exact location and from roughly the same timeframe, I only record them on the spreadsheet once to reduce clutter, but I add a note that there are multiples.

The Build Process

Referencing the image above, haplogroups in the column directly above the originating haplogroup, R-BY154784, then R-ZS3700, colored apricot, are parent haplogroups – meaning that these haplogroups descend from the haplogroups above them. Look at R-ZP18, North Berwick, above R-BY482 as an example. This means two things.

  1. It’s possible that my ancestors could descend from these individuals in this column. However, all things considered, it’s more likely that they are a “cousin” of my ancestor who lived at that time and carried that haplogroup before a new mutation happened and branched into a new downstream haplogroup. That’s exactly what we proved about North Berwick based on when he lived and our downstream haplogroup formation date.
  2. Every man who shares that haplogroup, R-ZP18, absolutely DOES descend from the original man who carried that haplogroup-defining mutation that arose about 2250 BCE or about 4250 years ago. That one man in whom R-ZP18 occurred is noted above North Berwick, in red, indicating that both North Berwick and the Estes men descend from the man whose name is now R-ZP18.

On my spreadsheet, I’ve colored the cells of the haplogroups that I do descend from, and the burials I might descend from, apricot. The common haplogroups that burials and contemporary testers downstream descend from are in bold red text (R-ZP18 and R-DF49).

Burials who carry a different branching haplogroup, meaning they aren’t R-ZP18, but branch FROM from R-ZP18, are shown with their branches in blue. My ancestors cannot descend from blue haplogroups because we are on different branches of R-ZP18. Our branch is apricot.

Let’s add the next Ancient Connection.

Here’s the Time Tree Timeline of the second Ancient Connection, named Mount Pleasant 746, found at All Saints, Cambridgeshire, England, who lived between 940 and 1365 CE.

This shows two things.

  • My R-ZS3700 ancestor cannot descend from the Mount Pleasant burial, since R-ZS3700 doesn’t carry the mutation for R-BY173525, found in the Mount Pleasant burial.
  • However, since R-BY173525 branched from R-ZP18, we DO SHARE a common ancestor who lived about 4250 years ago. This means that between 4250 years ago and 940-1385 CE, the man found in Cambridgeshire, and my ancestor found in Kent around 1495 CE, both migrated in different directions from where their common ancestor, R-ZP18, lived, wherever that was.

The next closest Ancient Connection is Vor Frue Kirkegård 336, buried in the yard of a former monastic church in Vor Frue Kirkegård, Aalborg, Denmark, which dates from the 12th century. This man lived between 1536 and 1806 CE.

Again, my Estes ancestor who carries R-ZS3700 can’t descend directly from this man. Three things preclude Vor Frue Kirkegård 336 from being our ancestor:

  • The fact that Vor Frue Kirkegard 336 carries R-BY203953, but the Estes line does not.
  • Vor Frue Kirkegard 336 does not carry, R-BY342, the next downstream SNP for the Estes line.
  • Vor Frue Kirkegard 336 lived between 1536 and 1806 CE, which is contemporary with or after the earliest documented Estes ancestor was living in Kent, England circa 1495.

In this case, the locations are not in close proximity, over 500 miles apart by a combination of land and water. This distance would be less compelling as an elimination factor if the men were further separated by time.

In this case, any one of the first three pieces of evidence, alone, would preclude Vor Frue Kirkegard from being our ancestor.

Once again, R-ZS3700 shares the common ancestor of R-ZP18 with Vor Frue Kirkegård 336, along with Mount Pleasant 746 and North Berwick 16499. All of those men shared one common ancestor 4250 years ago.

Now, we have the bottom portion of our tree built out – meaning everyone who either carries haplogroup R-ZP18 as their primary haplogroup, or descends from that man.

Moving up the tree in the apricot column, you’ll notice that I’ve left spaces that leave room for the branching haplogroups in blue on the right. You won’t know how many spaces you need or the configuration until you start building the tree in your spreadsheet.

I listed both “5 haplogroups” and “3 haplogroups,” in the apricot column. You can spell those haplogroups out if you wish, but for my Ancient Connections, they didn’t matter. They may matter in the future, though, if you have an Ancient Connection who descends from or branches from one of them.

If you need an easy way to determine your ancestral lineage, the Ancestral Path is just the thing for you and will help build your spreadsheet.

Your Ancestral Path

It’s easy to view which haplogroups are in your direct ancestral line. Just click on the “Ancestral Path” link in Discover’s sidebar.

Your haplogroup is shown at the top, with the parent haplogroups in order beneath. I’ve boxed the “5 haplogroups” between R-BY482 and R-ZP18 here, and then the “3 haplogroups” between R-ZP18 and R-DF49, which is where we find the next closest Ancient Connections.

One bonus of the Ancestral Path display is that you can see how many Ancient Connections are in the database for each haplogroup, at far right.

As I continue to build out my spreadsheet, the next four burials are all R-DF49, a haplogroup that was formed about 4400 years ago. Three of those burials are in England, and the fourth is in the Orkney Islands. They are all apricot, meaning:

  • They don’t carry any downstream haplogroups
  • They all descend from R-DF49
  • Based on haplogroups alone, nothing precludes the Estes line from descending from any of those men

Evaluating each Ancient Connection in the same way we did for North Berwick, when they lived, as compared to our Estes men, and where, may eliminate some of these burials as possible direct ancestors.

The balance of the Ancient Connections descend from R-DF49 through different branches and are colored blue, removing them as possible ancestors of R-ZS3700.

Regardless, we all share an ancestor, R-DF49, about 4400 years ago, just shortly before R-ZP18 lived some 4250 years ago. It would make sense that R-DF49 and R-ZP18 lived in relatively close proximity, given that they only lived about 200 years apart.

What else can we learn about these Ancient Connections?

Migration Map

To view all of your Ancient Connections on a map, just click on “Migration Map” in Discover’s sidebar.

The haplogroup whose path you are viewing, in this case, R-DF13, is the red dot on the bar at the top and is shown on the map with a red circle, but is mostly obscured here by the blue and red circles with numbers in the British Isles.

That haplogroup’s migration map, and your Ancient Connections, are displayed together. Individual burials not in close proximity to others are shown with individual trowels, and multiple burials are shown with blue and red circles, with the number indicating how many burials are found at that location.

Expanding the map shows more detail. I placed a red star to indicate the Estes lineage in Deal, at the bottom right.

Many of the blue and red circles have expanded, too.

By clicking on the blue circle, you can see which samples are found there. In this case, these 7 matching samples were all found in the same archaeological dig.

By clicking on any sample, you’ll see additional information.

One of my original questions was whether or not there was any indication whatsoever, even a smidgen of possibility that the d’Este rumor might be true. Some Estes researchers are not convinced by other arguments.

Given that our closest Ancient Connection lived about 2000 years ago in the British Isles, as do most, but not all, of the other Ancient Connections, it’s exceptionally unlikely that the progenitor of the Estes lineage was living in Italy in the 1400s, just a generation before our Estes ancestors are found in the records in Deal, and some 2000 years after the parent haplogroups of R-ZS3700 were already well-established in the British Isles.

There’s another place to check for additional information.

Notable Connections

Sometimes Notable Connections includes people who are either “ancient” themselves, and whose haplogroups have been identified through their descendants, or are from burials, or a combination of both. The difference is that their identity is not entirely a mystery.

When evaluating Notable Connections for genealogy, focus on:

  • Their haplogroup
  • Your shared haplogroup
  • When and where they lived
  • Any precluding factors like we found when analyzing North Berwick

Notable Connections are all interesting, but only a few may be relevant to your genealogy or your ancestors’ journey to where you first found them.

Speaking of their journey, Globetrekker™ shows you the most likely path of your ancestor’s haplogroup over time.

Globetrekker™

Globetrekker™ is currently only available for Y-DNA, and only for those who have taken the Big Y test.

Clicking on Globetrekker™ through my cousin’s account shows the path of his haplogroup, through Europe, in this case, into England and, if I enable them, includes relevant Ancient Connections. One Ancient Connection, Mount Pleasant 746, at Cambridgeshire, is found on the estimated genetic haplogroup path.

We’ve already determined that the Estes line cannot descend from Mount Pleasant 746, but the locations of the descendants of our common ancestor, R-ZP18 can still provide substantial clues about where our common ancestor might have lived, and his culture.

I’ve also enabled Globetrekker™’s “Sibling Lines” which indicate haplogroup siblings with the thinner lines. These display options are easy to toggle on and off.

Note that this is an estimated genetic path. In other words, it’s not exact. Especially, paths of the newer haplogroups can and will change over time as more testers test, and earliest known ancestors (EKAs) are added. I wrote about how to add EKAs in the article, “Earliest Known Ancestors” at FamilyTreeDNA in 3 Easy Steps. Please add yours, along with their location.

Sometimes the most refined haplogroup did not emerge in England, R-ZS3700 in this case, but in America. However, since the descendants have noted their EKA correctly as originating in England, that’s where the most refined haplogroup is also shown.

Furthermore, other than for Native Americans who are indigenous to the Americas, Globetrekker™ and the Migration Map both stop at the originating land mass for both Y-DNA and mitochondrial DNA.

You can read more about Globetrekker™, here.

What About the d’Este Family Story?

Now, about that d’Este family story.

Globetrekker™ utilizes the “least cost” migration methodology, which means the easiest, least risky, route of passage from place to place for our ancestors. The Strait of Dover is the closest link to the European mainland, and was shallower at that time as well.

There’s absolutely no genetic evidence that points to Italy or anyplace south for the Estes ancestral line. In fact, haplogroup R-S552 emerged about 4650 years ago, and appeared about the time that this lineage crossed from continental Europe into what is today England. There’s no evidence that this line back-migrated to the continent, to then remigrate back to the British Isles after 1471.

Ancient Connections show us that there’s evidence of the Estes ancestral haplogroups in many locations across the British Isles, long before Frencesco d’Este was being exiled from Italy. Multiple Estes family members appear in the earliest records in the Deal area, so it’s certain that they were well established and probably fishing on those same shores hundreds, if not thousands, of years earlier, based on Ancient Connections these various migration maps.

These provide one more very large nail in the coffin of that much-loved but extremely unlikely family story.

The final piece of evidence would be if a proven male descendant of the d’Este line tested and did or didn’t match. I’m not holding my breath.

Mitochondrial DNA

The methodology for building your Ancient Connections spreadsheet is exactly the same for mitochondrial DNA, with one exception.

You immediately know that you cannot descend from any male burial, because men don’t pass their mitochondrial DNA on to their children of either sex. You could, however, potentially be descended from his mother, or sister, or cousin, etc. Otherwise, the guidelines are the same.

Sometimes, Ancient Connections can resolve long-standing conflicts.

The Conflict Surrounding Radegonde Lambert

For a very long time, it was believed that Radegonde Lambert, an early Acadian woman born around 1621, was Native American because there were no known people, other than her, with that surname in Acadia. Based on the birth years of her children, she married Jean Blanchard, a French man, around 1642.

It doesn’t help any that French soldiers arrived in 1632, family settlement began about 1636, but there are virtually no records until the 1671 census, nearly 40 years later. Lots of people perished during that 40 year window.

Radegonde could have married before her arrival in Acadia, and Lambert may not be spelled accurately. We are fortunate that French women are referenced by their birth surnames, not their married surnames, so she is listed as Radegonde Lambert, the wife of Jean Blanchard on the 1671, 1678 and 1686 censuses.

Based on the conflict swirling around her presumed Native American ancestry, plus early mitochondrial DNA HVR1/HVR2 results that pointed to haplogroup “X”, which has both Native American and European branches, Radegonde began to be reported as “DNA confirmed Native”. However, that was incorrect, and she was NOT DNA confirmed as Native. Haplogroup X2a and subclades are Native American, while other haplogroup X AND X2 subclades are European, as can be viewed in the Acadian AmerIndian DNA Project.

By the time full mitochondrial sequence testing became available, that incorrect “confirmation” was firmly entrenched in family trees and among researchers, leading me to pen the article, Haplogroup X2b4 is European, Not Native American.

While ho-hum with a yawn today, it was radical at the time and greeted with quite the kerfluffle. After all, Radegonde was proven Native and HOW DARE ME! 😊

Prior to Mitotree, Radegonde’s haplogroup was X2b4, but now it’s been extended to X2b4t2, which arose about the year 500, or around 1500 years ago.

X2b4 and subclades are quite rare, with only 353 descendants today, including subclades.

X2b4t2 only has 65 members.

Clicking on the “Other Countries” link takes you to the Country Frequency report.

Click on “Table View.”

Note that the 36 “Other Countries” includes people who have listed “Unknown Origin,” who are counted individually. People listing United States often mean they are brick walled here. Some people interpret this as Native American, but there is a separate United States Native American category. Not everyone selects the correct category.

These locations are user-reported in the Earliest Known Ancestor (EKA) information, which is critical for Discover reports. I wrote about how to complete that information in 3 easy steps, here. Please add yours, including location!

One person has reported that Radegonde Lambert is “United States Native American.” She’s not Native, and she never lived in the United States either. During her lifetime, Acadians lived in Nova Scotia, where three censuses accurately reflect her residence.  Perhaps that incorrect information was entered by someone years ago, and never changed. Most people don’t think to update their EKA information.

Unfortunately, when misinformation is provided, or not corrected after we learn more, new testers view that as nuggets of evidence, and the misinformation cycle continues.

One of the benefits of Ancient Connections is that they are NOT based on trees, historical records, or genealogy of any sort. Ancient Connections are based on archaeological digs, and the location of the excavation is not subject to question.

So, let’s take a quick look at Radegonde Lambert’s Ancient Connections and see what we find.

A Quick Sneak Preview

Because I’m interested primarily in a quick view of locations, I’m skipping right to the Migration Map where all of the Ancient Connections are shown.

Radegonde’s Ancient Connections are scattered all over Europe, but there’s absolutely nothing in the Americas.

Given that Native burial excavations are culturally frowned upon in many locations, we might not see any in the US, but we also wouldn’t see any recent burials in Europe, given that the Native people have been in the Americas for well over 10,000 years.

Generally, even when Ancient Connections are missing in the US, we still find some contemporary testers with proven genealogy who carry that haplogroup, and at least a few ancient burials in Canada, Mexico, Central and South America.

The first seven Ancient Connection matches carry haplogroup X2b4, and the rest are European subgroups of X2b4. There are no closer matches as of today, but that doesn’t mean there won’t be eventually.

X2b4 emerged sometime before 5200 years ago, clearly someplace in Europe, possibly central Europe.

Radegonde’s X2b4 match locations are:

  • Malá Ohrada site in Prague – the individual lived 5800-5400 years ago
  • Hetty Peglers Tump, Gloucestershire, England – lived 5639-5383 years ago
  • Sorsum, Hildesheim, Lower Saxony, Germany – lived 5350-5100 years ago
  • Passage Tomb, Carrowkeel, Cairn K, Sligo, Ireland – lived 5100-4600 years ago
  • Kolín I-7b, Bohemia, Czech Republic – lived 4835-4485 years ago
  • De Tuithoorn, Oostwoud, Netherlands – lived 4579-4421 years ago

It’s unquestionable that X2b4 was found across Europe, not in the Americas, 5000 years ago.

This image is NOT from Radegonde Lambert’s Ancient Connections. I’ve included it to illustrate a Native American branch of haplogroup X2.

The descendants of Native American haplogroup X2a, shown above, match Kennewick Man, who is also X2a, as their closest Ancient Connection. He lived between 9250 and 8390 years ago along the river in present-day Kennewick, Washington. Their second-closest Ancient Connection is with an X2a1 burial found in Windsor, Ontario, who lived between 1223 and 1384 CE.

Neither of these unquestionably Native burials are found in the Ancient Connections of Radegonde Lambert’s descendants.

It’s worth noting here that when evaluating rare haplogroups, their Ancient Connections may reach far back in time. For example, if a Native American haplogroup only has a few Ancient Connections within the Americas, the rest of their Ancient Connections, if any, will be found on another continent. Failing to read the results thoroughly and thoughtfully could lead to an inappropriate and incorrect conclusion.

For example, haplogroup X is found in Eurasia prior to the migrated of people across Beringia, the now-submerged landmass connecting Asia with Alaska, to become the indigenous people of the Americas. Therefore, if there are less than 30 closer X2a Ancient Connections, one would expect to find Ancient Connections reflecting that continental Asian, or even Eurasian, heritage far back in time.

Notable Connections

One final tip for both Y-DNA and mitochondrial DNA is to check Notable Connections and selectively add them to your spreadsheet, if appropriate. Sometimes you’ll find people there that are both Notable and Ancient.

Not that we need more evidence about whether Radegonde Lambert’s matrilineal ancestors were Native or European, but Notable Connections provides us with one more corroborating piece of evidence.

Cangrande della Scala was an Italian nobleman who lived around 1300. He and Radegonde share a haplogroup X2b1″79 ancestor in Europe around 9000 years ago, which was after the Native people had crossed Siberia and Beringia to begin settling Canada and the Americas.

If there was any question left about Radegonde Lambert’s origins, Ancient Connections resolved it, with a backup volley from Notable Connections.

Radegonde Lambert was my ancestor, so I’m going to build her Ancient Connections spreadsheet and savor every discovery, but if I were simply seeking confirmation of or the answer to the question of whether Radegonde Lambert was Native American or European, I need look no further.

Mitochondrial DNA Case Study

In the article, Mitochondrial DNA A-Z: A Step-by-Step Guide to Matches, Mitotree and mtDNA Discover, I wrote in detail about utilizing mitochondrial DNA to break through genealogy brick walls.

My goal was to detremine if Catherine LeJeune, Edmee LeJeune and Jeanne LeJeune dit Briard were sisters or at least matrilineal relatives. Fortunately, we had several testers.

As it turned out, Catherine and Edmee were European sisters, but Jeanne did not share a matrilineal ancestor with Catherine and Edmee. Jeanne was Native American.

Next, we wanted to discover as much information about the LeJeune sisters as possible.

I created an Ancient Connections spreadsheet for the LeJeune sisters and included those results in my analysis, so please take a look. Their Ancient Connections were unexpected and simply astounding.

You literally never know who is waiting for you, nor the message they hold, just waiting to be delivered.

Ancient Connections are clues from your ancestors.

_____________________________________________________________

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

Discover’s Ancient Connections – How Are You Related?

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

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

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

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

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

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

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

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

Ok, are you ready for some fun???

Let’s find out how to leverage these tools.

Ancient Connections

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

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

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

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

Radegonde Lambert

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

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

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

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

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

Sign on and Identify Your Haplogroup

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

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

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

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

Click Through to Discover

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

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

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

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

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

The Classic Tree

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

Click on any image to enlarge

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

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

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

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

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

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

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

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

In descending order, for Radegonde, we have haplogroups:

  • X2b4
  • X2b4d’g
  • X2b4g

Your Match Page

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

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

I wrote about haplotype clusters, here.

Click on any image to enlarge

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

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

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

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

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

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

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

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

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

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

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

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

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

Radegonde’s Discover Haplogroup

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

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

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

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

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

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

Parent Haplogroups

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

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

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

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

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

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

Ancient Connections

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Ancient Connections Analysis Chart

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

Legend:

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

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

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

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

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

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

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

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

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

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

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

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

According to Discover, Haplogroup X2b4:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The Migration Map

The Migration map in Discover provides two different features.

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

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

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

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

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

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

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

Radegonde Lambert and Kennewick Man

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

Let’s work through our evaluation process using Discover.

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

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

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

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

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

One went east and one went west.

X2a became Native American and X2b became European.

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

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

Let’s Compare

Discover has a compare feature.

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

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

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

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

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

More Ancient Connections

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

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

Zlatý kůň Woman

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

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

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

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

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

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

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

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

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

Ancient Connections for Genealogy

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

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

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

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

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

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

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

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

What is waiting for you?

_____________________________________________________________

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

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

RootsTech 2024 – MyHeritage is ON FIRE with 13 Announcements

I’ve got to tell you, MyHeritage has outdone themselves.

I had a hard time just keeping track of their announcements, which totaled 13 – a baker’s dozen.

You can watch the MyHeritage RootsTech keynote by Aaron Godfrey, here.

However, there are a few things not in the video, so let’s take a look at a quick summary of what’s new.

DNA Uploads with Free Advanced Tools Forever Extended Until March 10th

MyHeritage just extended their DNA upload that includes ALL ADVANCED TOOLS FOR FREE, forever, to March 10th so click here now to upload every kit you manage. This is a great deal. Hint – new ethnicity results are coming soon and you’ll be saving $29 on each kit you upload.

20+ Billion Records

MyHeritage has just passed the 20 billion record mark and is continuing to add. That’s billion, with a B. These records are available to customers with a MyHeritage subscription. If you don’t have a subscription, you can try a MyHeritage Subscription with a Free Trial, here.,

Additionally, right now, subscriptions are 50% off, but I don’t know how long that price lasts.

I love my MyHeritage subscription, and if you try it and don’t like yours, you can cancel and be charged nothing during the 14-day trial period.

I particularly like that the local newspaper where my grandparents lived is available on MyHeritage, and no place else. In addition, MyHeritage has integrated with FamilySearch, which is digitizing and indexing records like wildfire. That collaboration has provided me with information from European sources, including archives.

MyHeritage Wiki

MyHeritage has been working on their new Wiki, a community encyclopedia for genealogy and DNA, for almost a year now, although it was only recently released.

Photo courtesy of MyHeritage

I’ve been honored to write several articles for the newly announced MyHeritage Wiki, including the definition of DNA itself:

Take a look at the new Wiki, here.

You can filter in a number of ways, and you can even sign up to be a contributor.

Check out their blog article, here.

AI Record Finder

The AI Record Finder is the world’s first AI chat-based search engine for historical records.

I should probably tell you that, at this point in time, I do use AI, such as ChatGPT, very cautiously, and I’m inherently suspicious because AI tools sometimes hallucinate. It’s a new technology with lots of glitches and unknowns, so let’s see how MyHeritage is using this tool. It should be much more reliable since it’s in a controlled environment. I need to be convinced. 😊

The AI Record Finder is under the Research Menu. Just type your question about your ancestor.

I’m cheating and giving MyHeritage a tough one. I typed, “Please tell me about Solomon Ferwerda, who died in 1768 in Groningen, the Netherlands.”

MyHeritage returned three possibilities in their database, including their affiliated databases. One is a MyHeritage tree and two are records from FamilySearch.

Don’t limit yourself at this point.

I happen to know “my” Solomon is the first person, but I played around a bit before selecting the “right” Solomon. Why? Because there’s a lot that I don’t know about his life. It’s possible that the second and third records are ALSO the right person, so be sure to review everything.

Clicking on the middle or right record for Solomon shows that, indeed, this record from FamilySearch comes from the Dutch Archival Indexes, so it’s not “just someone’s tree.”

We do know the Ferwerda family is from Leeuwarden, but we don’t know when Solomon was born, nor if he was married twice. I only have the name of his second wife and one child, Jan, who was born the year he died.

The two FamilySearch Dutch archive records are from Leeuwarden, so maybe, just maybe, I’ve discovered something new about Solomon. How exciting!

I need to click through and check this out further.

I didn’t expect to like this tool, but so far, I really do. But wait – there’s more.

AI Ancestor Bio

You can click to have MyHeritage generate an AI bio of an ancestor for you.

The bio takes a few minutes to generate and will be available for download in the chat and will also be emailed to you. You can easily share with others. Getting other people interested in genealogy often encourages them to take a DNA test. DNA tests are still on sale for $39, here.

Solomon Ferwerda’s AI bio was completed quickly and arrived in pdf format. We know so little about him, I knew it would be short. I must say, I really enjoyed the “Historical Context” section that discussed the surrounding events that would have affected his life. That’s incredibly important and would have or could have influenced the decisions he made. Maybe the warfare and political unrest caused him to move from Leeuwarden to Groningen for some reason, where he died the year his son was born.

Here’s Solomon’s bio.

Here’s a link to the RootsTech lecture about the MyHeritage AI tools by Ran Snir, the VP of Product.

MyHeritage blog links for AI Record finder are here and here.

You can watch Telling Your Family’s Story with MyHeritage’s AI Features by Janna Helshtein at Legacy Family Tree Webinars, here.

I can’t wait to play with the MyHeritage AI tools more.

Updated Ethnicity Coming Soon

This is going to make a lot of people happy!

MyHeritage is in the process of updating their ethnicity results, increasing their regions from 42 to 80, with significantly optimized granularity in Europe. I initially misunderstood and thought the new results were available now, but they won’t arrive until summer.

I understand from talking to a Jewish friend involved in MyHeritage’s R&D effort that their own results are substantially improved and that they have now been placed in Armenia where their ancestors are from. They are no longer generically “Jewish.”

New Profile Pages with Hints

Daniel Horowitz said that everyone calls Smart Matches and Record Matches hints, so now MyHeritage has updated profile pages and is adding them to the profile page and officially calling them Hints.

You can still find Smart Matches and Record Matches listed separately under Discoveries, but on everyone’s profile, they are called Hints.

On Solomon’s profile page, scroll down to view his journey based on the information you’ve entered or accepted into your tree.

I did not yet add Leeuwarden, because I’m yet positive those records in Leewarden are his, but if I had, Leeuwarden would also be shown on his journey map. I’ll be incorporating these into my 52 Ancestors stories. I love maps! Maybe I can find old maps to include too,

You can read more about the new profiles and hints, here.

Tree Collaboration with FamilyTreeDNA

Aaron Godfrey announced tree collaboration with FamilyTreeDNA who pre-announced this at their conference in November.

I don’t have specific details about how it works, as this won’t happen for a few months yet, but FamilyTreeDNA customers will port their trees to MyHeritage which allows them to take advantage of MyHeritage’s record collections and such. Existing MyHeritage customers will simply connect their FamilyTreeDNA test to their MyHeritage tree.

FamilyTreeDNA has never been a “tree” company, so this means that users will have one less tree to maintain independently, and they can augment their research with records from MyHeritage.

I talked to Katy Rowe-Schurwanz, the Product Manager at FamilyTreeDNA to confirm that this is NOT a DNA transfer. FamilyTreeDNA matches still occur in the FamilyTreeDNA database, just like always, and MyHeritage matches still occur in the MyHeritage database. If you want matching in both databases, you still have to upload to or test at both. Only the trees are integrated, meaning when you click on a tree at  FamilyTreeDNA, you’ll see the tree displayed on MyHeritage.

The great news is that FamilyTreeDNA features such as Family Matching (bucketing) where you link your DNA matches at FamilyTreeDNA to their profile cards so that maternal/paternal bucketing occurs will still work the same way. The only difference will be that your tree will actually reside at MyHeritage and not at FamilyTreeDNA.

You’ll be able to enjoy the best of both worlds.

We will know more in a few months, and I’ll provide more details when I have them.

Invite Another MyHeritage User to View Your DNA Results

Aaron Godfrey said in the keynote that 2FA (two-factor authentication) at MyHeritage will become mandatory later this month, and with it, MyHeritage is adding the feature of being able to invite another MyHeritage user to view your DNA results. This allows people to collaborate more easily, especially if a different person is managing someone else’s DNA test.

Reimagine Multi-Photo Scanner App

This photo-scanning innovation is for your phone and allows you to scan photos and entire photo album pages – automatically separating and improving the photos. Then, of course, you just tag them to the proper person in your tree like any other photo.

Oh, and did I mention that Reimagine is free? I expected to have to pay when I downloaded the app, but I didn’t, probably because I have a full subscription.

Based on this article, Reimagine is not meant for other types of images, like pages of text or albums of clipped newspaper articles. But guess what? I downloaded the app, and it works just fine for those items! Hallelujah. How I wish I had this last week at the FamilySearch Library when I was finding pages in books I wanted to associate with a specific ancestor.

If you have album pages of photos to scan, this is golden and integrates with the profiles of people into your MyHeritage tree.

I really, really like the idea of having the ability to scan in the palm of my hand. That way if someone has a photo, you don’t have to try to take a photo of it. Gone are the days of literally dragging a laptop and scanner around with me when I’m traveling – just in case. Yes, I actually did and now I don’t have to anymore.

I cringe to think how many opportunities were lost to me before the days of laptops – but not now.

Thank you – THANK YOU, MyHeritage. What a great gift!

You can find the QR code to download the app, here.

OldNews is New News

MyHeritage has introduced a new website for old newspapers called OldNews which you can find here.

This addition doubles the number of newspapers previously available on MyHeritage.

Users can also subscribe separately to Old News for about $99/year.

MyHeritage customers use their normal credentials to sign in to either site, but accessing newspapers not previously integrated into MyHeritage will require an OldNews subscription too.

I had to try it. I entered my mother’s name.

Look, my Mom had a tonsillectomy. I never knew that. It was just a couple of months after she graduated from high school.

I didn’t know Mom spent the summer in Philadelphia, either. She was 19 at that time, and I had heard rumblings that she studied with a “prima ballerina” at the School of American Ballet. Guess where that is? Yep, Philly.

My Mom was a professional tap and ballet dancer before she became my Mom.

Understanding that Mom spent the summer of 1942 on the east coast sheds new light on this and a few other photos in Mom’s photo album, which I can now scan.

Ok, I can’t help myself. I have to enhance this photo at MyHeritage.

Much better. Another tiny piece of Mom’s life brought into focus.

I wonder what else is in OldNews that I don’t know about. Hmmmm…

You can read about OldNews here.

New All-Inclusive Omni Subscription

MyHeritage is launching a new Omni all-inclusive subscription plan that includes most of the MyHeritage products and tools, except for Filae, unless I’m missing something. Omni reportedly costs less than half the price if you were to subscribe to all of these individually. I’ve asked for a comparison chart which I don’t have yet, but I’m told will be coming soon.

Here’s what’s included:

Additionally, I asked MyHeritage about whether or not the advanced DNA tools are included with Omni, and they are. So, add advanced DNA tools to that list.

The following information about the Omni Plan is a screenshot from the MyHeritage blog article, here.

I have not been able to determine the price of an Omni subscription. At RootsTech, you were interested in the Omni plan, you submitted a Google form and a day or so later, you received this email.

I suspect MyHeritage needs to talk to you because how much it costs initially depends on your existing subscriptions, and how much time is left on those.

I reached out to MyHeritage and asked when Omni will be available to purchase, and the answer is “soon.” You can’t sign up just yet.

I have never subscribed to Legacy Family Tree Webinars, even though I’m a webinar presenter and have several webinars available there. My gift to myself is going to be Omni when it’s available because I want Legacy Family Tree Webinars, and I’d love a subscription to OldNews. I already have a full subscription to MyHeritage, and I’d probably use Geni more than I do as a casual user if I had the Omni subscription.

Artifact Testing – Maybe

Unfortunately, I was not able to attend CEO Gilad Japhet’s RootsTech session because his session and mine were at exactly the same time.

However, I asked Aaron Godfrey after Gilad’s session what I had missed that was not in Aaron’s keynote, other than Gilad’s wonderful stories.

Aaron and others told me that Gilad stated that he was personally submitting personal artifacts, such as stamps, to a third-party lab once again, to test the waters to see if DNA can now be extracted from artifacts successfully.

MyHeritage tried this a few years ago, ultimately unsuccessfully. Perhaps this time will be different, but I would not hold my breath, truthfully. Degraded DNA has quality issues, not to mention that the DNA extracted might not be the DNA of the person expected.

I would personally love this, but I am also skeptical at this point. Kudos to Gilad for trying again with his own personal items.

MyHeritage Online RootsTech Booth

MyHeritage has provided several educational videos in their online RootsTech booth, at this link. Be sure to take advantage of this free resource.

Whew, I’m finally done! I told you that MyHeritage had been very, very busy, and I wasn’t kidding. I hope I didn’t miss anything.

_____________________________________________________________

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

FamilyTreeDNA 2023 Update – Past, Present and Future

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

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

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

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

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

Past, Present, and Future with Katy Rowe-Schurwanz

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

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

Recent Milestones

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

Acquisition and Wellness Bundles

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

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

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

New TIP (Time Prediction) STR Report

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

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

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

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

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

MyOrigins3

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

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

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

Additional Releases

Additional products and features released since the last conference include:

Discover

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

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

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

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

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

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

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

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

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

Earliest Known Ancestor (EKA) Improvement

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

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

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

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

Recommended Projects on Haplogroups & SNPs Page

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

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

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

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

Abandoned Projects

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

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

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

New Kit Manager Feature

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

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

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

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

Beneficiary Page

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

What is FamilyTreeDNA working on now?

Currently in the Works

Katy moved on to what’s currently underway.

Privacy and Security

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

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

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

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

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

Why is this necessary?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

New Permissions

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

  • Download data
  • Purchase tests

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

Family Finder Haplogroups

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

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

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

Please read this article for more information.

New Discover Tools and Updates

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

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

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

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

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

Big Y FaceBook Group

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

FamilyTreeDNA Blog

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

Multi-Language Support

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

Paypal, Payments, and Gift Cards

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

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

Million Mito Project & Mitotree

Work on the Million Mito Project is ongoing.

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

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

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

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

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

This is SOOO exciting!!!

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

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

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

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

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

The Future

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

Privacy Laws

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

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

New Kits Opted Out of IGG

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

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

Biobanking Separate Consent

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

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

MyHeritage Tree Integration

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

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

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

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

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

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

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

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

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

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

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

Big Y Infrastructure

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

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

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

Wishlist

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

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

Which items do you want to see most?

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

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

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

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

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

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

Suggestions Welcomed

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

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

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

Lab Update

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

A lab update has become a tradition over the years.

Linda Jones, Lab Manager, provided a lab update.

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

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

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

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

Q&A and Thank You

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

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

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Y-DNA Haplogroup O – When and How Did It Get to the Americas?

Y-DNA Haplogroup O has been found in male testers descended from a Native American ancestor, or in Native American tribes in the Americas – but sometimes things are more complex than they seem. The story of when and how haplogroup O arrived in the Americas is fascinating – and not at all what you might think.

Introduction

The concept of Native American heritage and indigenous people can be confusing. For example, European Y-DNA haplogroup R is found among some Native American men. Those men may be tribal members based on their mother’s line, or their haplogroup R European Y-DNA may have been introduced either through adoption practices or traders after the arrival of Europeans.

There is unquestionable genetic evidence that the origin of Haplogroup R in the Americas was through colonization, with no evidence of pre-contact indigenous origins.

Y-DNA testing and matching, specifically the Big Y-700 test, with its ability to date the formation of haplogroups very granularly, has successfully identified the genesis of Y-DNA haplogroups and their movement through time.

We’ve spent years trying to unravel several instances of Native American Y-DNA Haplogroup O and their origins. Native American, in this context, means that men with haplogroup O are confirmed to be Native American at some point in documented records. This could include early records, such as court or probate records, or present-day members of tribes. There is no question that these men are recognized as Native American in post-contact records or are tribal members, or their descendants.

What has not been clear is how and when haplogroup O entered the Native American population of these various lineages, groups, or tribes. In other words, are they indigenous? Were they here from the earliest times, before the arrival of colonists, similar to Y-DNA haplogroups C and Q?

This topic has been of great interest for several years, and we have been waiting for additional information to elucidate the matter, which could manifest in several ways:

  1. Ancient pre-contact DNA samples of haplogroup O in the Americas, but none have been found.
  2. Current haplogroup O testers in Native American peoples across the North and South American continents, forming a connecting trail genetically, geographically, and linearly through time. This has not occurred.
  3. Big-Y DNA matches within the Americas between Haplogroup O Native American lines unrelated in a genealogical timeframe whose haplogroup formation pre-dates European contact. This has not occurred.
  4. Big-Y DNA matches between Haplogroup O men whose haplogroups were formed in the Americas after the Beringian migration and expansion that scientists agree occurred at least 12-16K years ago, and possibly began earlier. Earlier human lineages, if they existed, may not have survived. A later Inuit and Na-Dené speaker circumpolar migration occurred 4-7K years ago. This has not occurred.
  5. Big-Y DNA matches with men whose most recent common ancestor haplogroup formation dates connect them with continental populations in other locations, outside of North and South America. This would preclude their presence in the Americas after the migrations that populated the Americas. This has occurred.

The Beringian migration took place across a now-submerged land bridge connecting the Chutkin Peninsula in Russia across the Bering Strait with the Seward Peninsula in Alaska.

By Erika Tamm et al – Tamm E, Kivisild T, Reidla M, Metspalu M, Smith DG, et al. (2007) Beringian Standstill and Spread of Native American Founders. PLoS ONE 2(9): e829. doi:10.1371/journal.pone.0000829. Also available from PubMed Central., CC BY 2.5, https://commons.wikimedia.org/w/index.php?curid=16975303

Haplogroup O is clearly Native American in some instances, meaning that it occurs in men who are members of or descend from specific Native American tribes or peoples. One man, James Revels, is confirmed in court records as early as 1656. However, ancestors of James Revels fall into category #5, as their upstream parental haplogroup is found in the Pacific islands outside the Americas after the migration period.

Based on available evidence, the introduction of haplogroup O appears to be post-contact. Therefore, haplogroup O is not indigenous to the Americans in the same sense as haplogroups Q and C that are found widespread throughout the Americas in current testers who are tribal members, descendants of tribal members, and pre-contact ancient DNA as mapped in the book, DNA for Native American Genealogy.

Ancient DNA

Haplogroup C is found in both North and South America today, as are these ancient DNA locations.

Haplogroup Q is more prevalent than Haplogroup C, and ancient DNA remains are found throughout North and South America before colonization.

No ancient DNA for Haplogroup O has been discovered in the Americas. We do find contemporary haplogroup O testers in regional clusters, which we will analyze individually.

Let’s take a look at what we have learned recently.

Wesley Revels’ Lineage

Wesley Revels was the initial Y-DNA tester whose results identified Haplogroup O as Native American, proven by a court record. That documentation was critical, and we are very grateful to Wesley for sharing both his information and results.

Wesley’s ancestor, James Revels, was Native American, born about 1656 and bound to European planter, Edward Revell. James was proven in court to be an Accomack “Indian boy” from “Matomkin,” age 11 in 1667. James was bound, not enslaved, until age 24, at which time he was to be freed and receive corn and clothes.

James had died by 1681 when he was named several times in the Accomack County records as both “James, an Indian” and “James Revell, Indian,” in reference to his estate. James lived near Edward Revell, his greatest creditor and, therefore, administrator of his estate, and interacted with other Indian people near Great Matompkin Neck. Marie Rundquist did an excellent job of documenting that here. Additional information about the Revels family and Matomkin region can be found here.

The location where Edward Revell lived, Manokin Hundred, was on the water directly adjacent the Great Matomkin (now Folly Creek) and Little Matomkin Creeks, inside the Metomkin Inlet. The very early date tells us that James Revels’s paternal ancestor was in the colonies by 1656 and probably born about 1636, or perhaps earlier.

Lewis and Revels men are later associated with the Lumbee Tribe, now found in Robeson and neighboring counties in North Carolina. The Lewis line descends from the Revels lineage, as documented by Marie and Wesley. Other men from this line have tested and match on lower-level STR markers, but have not taken the much more granular and informative Big-Y test.

Until recently, the men who matched Wesley Revels closely on the Big-Y test were connected with the Revels line and/or the Lumbee.

Wesley has a 37-marker STR match to a man with a different surname who had not tested beyond that level, in addition to several 12-marker STR matches to men from various locations. Men who provided known ancestral or current locations include one from Bahrain, two from the Philippines, and three from China. Those men have not taken the Big-Y, and their haplogroups are all predicted from STR results to O-M175 which was formed in Asia about 31,000 years ago.

12-marker matches can reach thousands of years back in time. Unless the matches share ancestors and match at higher levels, 12-marker matches are only useful for geographic history, if that. The Big Y-700 test refines haplogroup results and ages from 10s of thousands of years to (generally) within a genealogically relevant timeframe, often within a couple hundred years.

One of Wesley’s STR matches, Mr. Luo, has taken a Big Y-700 test. Mr. Luo descends directly from Indonesia in the current generation and is haplogroup O-CTS716, originating about 244 BCE, or 2244-ish years ago. Mr. Luo does not match Wesley on the Big-Y test, meaning that Wesley and Mr. Luo have 30 or more SNP differences in their Big-Y results, which equates to about 1,500 years. The common ancestor of Wesley Revels and Mr. Luo existed more than 1,500 years ago in Indonesia. It’s evident that Mr. Luo is not Native American, but his location is relevant in a broader analysis.

There is no question that Wesley’s ancestor, James Revels, was Native American based on the court evidence. There is also no question that the Revels’ paternal lineage was not in the Americas with the Native American migration group 12-16K years ago.

The remaining question is how and when James Revels’ haplogroup O ancestor came to be found on the Atlantic seaboard in the early/mid 1600s, only a few years after the founding of Jamestown.

The results of other Haplogroup O men may help answer this question.

Mr. Lynn

Another haplogroup O man, Mr. Lynn, matches Wesley on STR markers, but not on the Big-Y test.

Mr. Lynn identified his Y-DNA line as Native American, although he did not post detailed genealogy. More specifically, we don’t know if Mr. Lynn identified that he was Native on his paternal line because he matches Wesley, or if the Native history information was passed down within his family, or from genealogical research. Mr. Lynn could also have meant generally that he was Native, or that he was Native “on Dad’s side,” not specifically his direct patrilineal Y-line.

Based on Mr. Lynn’s stated Earliest Known Ancestor (EKA) and additional genealogical research performed, his ancestor was John Wesley Lynn (born approximately 1861, died 1945), whose father was Victor Lynn. John’s death certificate, census, and his family photos on Ancestry indicate that he was African American. According to his death certificate, his father, Victor Lynn, was born in Chatham Co., NC, just west of Durham.

Family members are found in Baldwin Township, shown above.

I did not locate the family in either the 1860 or 1870 census. In 1860, the only Lynn/Linn family in Chatham County was 50-year-old Mary Linn and 17-year-old Jane, living with her, presumably a daughter. Both are listed as “mulatto” (historical term) with the occupation of “domestic.” They may or may not be related to John Wesley Lynn.

In 1870, the only Linn/Lynn in Chatham County is John, black, age 12 or 13 (so born in 1857 or 1858), farm labor, living with a white family. This is probably not John Wesley Lynn given that he is found with his mother in 1880 and the ages don’t match.

In 1880. I find Mary Lynn in Chatham County, age 48, single, black, with daughter Eliza Anne, 20, mulatto, sons John Wesley, 14 so born about 1866, and Charles 12, both black. Additionally, she is living with her nieces and nephews, Cephus, black, 12, Lizzie, 7, mulatto, Malcom, 4, mulatto, William H, 3, mulatto (I think, written over,) and John age 4, mulatto. The children aged 12 and above are farm labor.

In 1880, I also find Jack Lynn, age 28, black, married with 3 children, living beside William Lynn, 25, also married, but with no children.

Trying to find the family in 1870 by using first name searches only, I find no black Mary in 1870 or a mulatto Mary with a child named Jack or any person named Cephus by any surname. I don’t find Jack or any Lynn/Linn family in Chatham County.

The 1890 census does not exist.

In the 1900 census, I find Wesley Lynn in Chatham County, born in January of 1863, age 37, single, a boarder working on the farm of John Harris who lives beside Jack Lynn, age 43, born in April of 1857. Both Lynn men are black. I would assume some connection, given their ages, possibly or probably brothers.

In 1940, John Wesley Lynn, age 74, negro (historical term), is living beside Victor Lynn, age 37, most likely his son.

I could not find Victor Lynn, John Wesley Lynn’s father in any census, so he was likely deceased before 1880 but after 1867, given that Mary’s son Charles Lynn was born in 1868, assuming Mary’s children had the same father. The fact that Mary was listed as single, not married nor widowed suggests enslavement, given that enslaved people were prohibited from legally marrying.

About the only other assumption we can make about Victor Sr. is that he was probably born about 1832 or earlier, probably in Chatham County, NC based on John Wesley’s death certificate, and he was likely enslaved.

Subclades of Haplogroup O

Both the Revels and Lynn men are subclades of haplogroup O and both claim Native heritage – Wesley based on the Revels genealogy and court documents, and Mr. Lynn based on the Native category he selected to represent his earliest known paternal ancestor at FamilyTreeDNA.

Both men have joined various projects, including the American Indian Project, which provides Marie and me, along with our other project co-administrators, the ability to work with and view both of their results at the level they have selected.

How Closely Related Are These Haplogroup O Men?

How closely related are these two men?

By Viajes_de_colon.svg: Phirosiberiaderivative work: Phirosiberia (talk) – Viajes_de_colon.svg, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=8849049

  • Do the haplogroups of the Revels men and Mr. Lynn converge in a common ancestor in a timeframe BEFORE colonialization, meaning before Columbus “discovered” the Caribbean islands when colonization and the slave trade both began?
  • Do the haplogroups converge on North or South American soil or elsewhere?
  • Is there anything in the haplogroup and Time Tree information that precludes haplogroup O from being Native prior to the era of colonization?
  • Is there anything that confirms that a haplogroup O male or males were among the groups of indigenous people that settled the Americas sometime between 12 and 26 thousand years ago? Or even a later panArctic or circumpolar migration wave?

Haplogroup O is well known in East Asia, Indonesia, and the South Pacific.

Another potential source of haplogroup O is via Madagascar and the slave trade.

The Malagasy Roots Project has several haplogroup O individuals, including the Lynn and Revels men, who may have joined to see if they have matches. We don’t know why the various haplogroup O men in the project joined. Other haplogroup O men in the project may or may not have proven Malagasay heritage.

Information provided by the project administrators is as follows:

The people of Madagascar have a fascinating history embedded in their DNA. 17 known slave ships came from Madagascar to North America during the Transatlantic Slave Trade. As a result, we find Malagasy DNA in the African American descendants of enslaved people, often of Southeast Asian origin. One of the goals of this project is to discover the Malagasy roots of African Americans and connect them with their cousins from Madagascar. Please join us in this fascinating endeavor. mtDNA Haplogroups of interest include: B4a1a1b – the “Malagasy Motif”, M23, M7c3c, F3b1, R9 and others Y-DNA Haplogroups include: O1a2 – M50, O2a1 – M95/M88, O3a2c – P164 and others

Resources:

http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2987306/  http://www.ncbi.nlm.nih.gov/pmc/articles/PMC1199379/  http://mbe.oxfordjournals.org/cgi/pmidlookup?view=long&pmid=19535740  http://www.biomedcentral.com/1471-2156/15/77  http://www.biomedcentral.com/1471-2164/10/605

The Malagasy group only has one other man who is haplogroup O and took the Big-Y test, producing haplogroup O-FTC77008. Of course, we don’t know if he has confirmed Madagascar ancestry, and his haplogroup is quite distant from both Revels and Lynn in terms of when his haplogroup was formed.

Viewing the Malagasy Project’s Group Time Tree, above, the common ancestor between those three men lived about 28K BCE, or 30,000 years ago.

Haplogroup O Project Group Time Tree

The Haplogroup O Project Time Tree provides a better representation of haplogroup O in general given that it has a much wider range of samples.

On this tree, I’ve labeled the haplogroup formation dates, along with the Revels/Lewis line which descends from O-FT45548. This haplogroup includes one additional group member whose surname is locked, as he hasn’t given publication permission. The haplogroup formation date of 1766 occurs approximately 85 years after James Revel’s birth, so is attributable to some, but not all of his descendants. At least one descendant falls into the older Haplogroup O-BY60500.

The common ancestor of all three, meaning Revels, Lewis, and the man whose name is locked and does not know his genealogy, is haplogroup O-BY60500, born about 1741.

Their ancestral haplogroup before that, O-FT11768, is much older.

Two Filipino results are shown on and descending from the parent branch of O-FT11768, formed about 3183 BCE, or about 5183 years ago. This tells us that the ancestors of all these men were in the same place, most likely the Philippines, at that time.

3183 BCE (5180 years ago) is well after the Native American migration into the Americas.

Discover Time Tree

Obviously, not every tester joins a project, so now I’m switching to the Discover Time Tree which includes all Y-DNA haplogroup branches. Their common haplogroup, O-FT11768, has many branches, not all of which are shown below. I’m summarized unseen branch locations at bottom left.

Expanding the Time Tree further to view all of the descendant haplogroups of O-FT11768, we see that this was a major branch with many South Pacific results, including the branch of O-FT22410, bracketed in red, which has three members.

One is Mr. Lynn whose feather indicates Native American as his EKA country selection, one is a man whose ancestor is from Singapore, and one is an unknown individual who did not enter his ancestor’s country of origin.

Geography

Wesley’s STR match list, which can reflect matches further back in time than the Big-Y test, includes islands near Singapore. This geography aligns with what is known about haplogroup O.

The distance between this Asian region and continental America, 9000+ miles distant by air, is remarkable and clearly only navigable at that time by ship, meaning ships with experienced crew, able to navigate long distances with supplies and water.

We know that in 760 CE, about 1240 years ago, Mr. Lynn’s haplogroup O-F24410 was formed someplace in the South Pacific – probably in Malaysia or a nearby island. This region, including the Philippines, is home to many haplogroup O men. The majority of haplogroup O is found in Asia, the South Pacific, and Diaspora regions.

We know that Hawaii was populated by Polynesian people about 1600 years ago, prior to the age of colonization. Hawaii is almost 7000 miles from Singapore.

Here’s the challenge. How did these haplogroup O men get from the South Pacific to Virginia? Mr. Lynn and the Singapore tester share a common ancestor about 1240 years ago, or 760 CE.

There is no known or theorized Native American settlement wave across Beringia as late as 760 CE. We know that the parent haplogroup was someplace near Singapore in approximately 760 CE.

Two Filipino men and the Revels’ ancestors were in the same location in the Pacific Islands 5180 years ago. How did they arrive on the Eastern Shore in Virginia, found in the Native population, either in or before 1656 when James Revels was born?

What happened in the 3500 years between those dates that might explain how James Revel’s ancestor made that journey?

Academic Papers

In recent years, there has been discussion of possible shoreline migration routes along the Russian coast, Island hopping along Alaska, Canada, and what is now the US, known as the Kelp Highway or Coastal Migration Route – but that has yet to be proven.

Even if that is the case, and it’s certainly a possibility, how did this particular group of men get from the Pacific across the continent to the Atlantic shore in such a short time, leaving no telltale signs along the way? The Coastal Migration Theory hypothesis states that this migration occurred from 12-16 thousand years ago, and then expanded inland over the next 3-5K years. They could not have expanded eastward until the glaciers receded. Regardless, the parent haplogroup and associated ancestors are still found in the Philippines and South Pacific 5000 years ago – after that migration and expansion had already occurred.

The conclusion of the paper is that there is no strong evidence for a Pacific shoreline migration. Regardless, that’s still thousands of years before the time range we’re observing.

We know that the Lynn ancestor was with men from Indonesia in 760 CE, and the Revels ancestor was with men from the Pacific Islands, probably the Philippines, 5180 years ago. They couldn’t have been in two places at the same time, so the ancestors of Revels and Lynn were not in the Americas then.

A 2020 paper shows that remains from Easter Island (Rapa Nui) show Native American DNA, and suggests that initial contact occurred between the two cultures about 1200 CE, or about 800 years ago, but there is not yet any pre-contact or post-contact ancient Y-DNA found in the Americas that shows Polynesian DNA. Furthermore, the hypothesis is that the DNA found on Easter Island came from the Americas, not vice versa. The jury is still out, but this does show that trans-Pacific contact between the two cultures was taking place 800 years ago, at least two hundred years pre-European contact.

Australasian migration to South America is also suggested by one set of remains found in Brazil dating from more than 9000 years ago, but there have been no other remains found indicating this heritage, either in Brazil, or elsewhere in the Americas.

Based on the Time Tree dates of the Haplogroup O testers in our samples, we know they were in the Islands of Southeast Asia after this time period. Additionally, there are no Australia/New Zealand matches.

The Spanish

The Spanish established an early trade route between Manila and Acapulco beginning in 1565. Consequently, east Asian men left their genetic signature in Mexico, as described in this paper.

Historians estimate that 40-129K immigrants arrived from Manilla to colonial Mexico between 1565 and 1815, with most being enslaved upon arrival. Approximately one-third of the population in Manilla was already enslaved. Unfortunately, this paper focused only on autosomal genome-wide results and did not include either Y-DNA, nor mitochondrial. However, the paper quantifies the high degree of trade, and indicates that the Philippines and other Asian population haplotypes are still prevalent in the Mexican population.

In 2016, Dr. Miguel Vilar, the lead scientist with the National Geographic Genographic project lectured in Guam about the surprising Native American DNA found in the Guam population and nearby islands. He kindly provided this link to an article about the event.

Guam was colonized by Spain. In the image from the Boxer Codex, above, the local Chamorro people greet the Manila Galleon in the Ladrones Islands, as the Marianas were called by the Spanish, about 1590.

Native Hawaiians descend from Polynesian ancestors who arrived in the islands about 400 CE, or about 1600 years ago. Captain Cook, began the age of European contact in Hawaii in 1778.

Five Possibilities

There are five possible origins of haplogroup O in the Americas.

  • Traditional migration across Beringia with the known migrations, estimated to have occurred about 12-16K years ago.
  • A Kelp Highway Coastal Migration which may have occurred about 12-16K years ago and dispersed over the next 3-5K years.
  • Circumpolar migration – specifically Inuit and Na-Dene speakers, about 4-6K years ago.
  • Post-contact incorporation from the Pacific Islands resulting from shipping trade on colonial era ships sometime after 1565.
  • Post-contact incorporation from Madagascar resulting from the importation of humans who may or may not have been enslaved upon arrival.

Do we have any additional evidence?

Other Haplogroup O DNA

From my book, DNA for Native American Genealogy:

Testers in haplogroup O-BY60500 and subclade O-FT45548 have proven Native American heritage.

We have multiple confirmed men from a common ancestor who is proven to be an enslaved Accomack “Indian boy,” James Revell, born in 1656, “belonging to the Motomkin” village, according to the Accomack County, Virginia court records. These men tested as members of haplogroup O-F3288 initially, after taking the Big Y-500 test. However, upgrading to the Big Y-700 produced more granular results and branches reflecting mutations that occurred since their progenitor was born in 1656.

Unfortunately, other than known descendants, these men have few close Y-DNA or Big Y-700 matches.

Without additional men testing from different unrelated lines, or ancient haplogroup O being discovered, we cannot confirm that this haplogroup O male’s ancestor was not introduced into the Matomkin Tribe in some way post-contact. Today, one descendant from this line is a member of the Lumbee Tribe.

However, that isn’t the end of the haplogroup O story.

The Genographic Project data shows one Haplogroup O Tlingit tribal member from Taku, Alaska, along with several testers from Mexico that indicate their paternal line is indigenous. Some people from Texas identify their paternal line as Hispanic.

Another individual indicates they were born on the Fountain Indian Reserve, in British Columbia and speaks the St’at’imcets language, an interior branch of Coastal Salish.

Haplogroup O has been identified as Native American in other locations as well.

Much of the information about Haplogroup O testers was courtesy of the Genographic Project, meaning we can’t contact those people to request upgraded tests, and we can’t obtain additional information in addition to what they provided when they tested. As an affiliate researcher, I’m very grateful to the National Geographic Society’s Genographic project for providing collaborative data.

When the book was published, the Discover Time Tree had not yet been released. We have additional information available today, including the dates of haplogroup formation.

FamilyTreeDNA Haplotree and Discover

The FamilyTreeDNA Haplotree (not to be confused with the Discover Time Tree) shows 10 people at the O-M175 level in Mexico, 10 people in the US report Native American heritage, 2 in Jamaica, and one each in Peru, Panama, and Cuba. There’s also one tester from Madagascar.

Altogether, this gives us about 35 haplogroup O males in the Americas, several with Native heritage.

Please note that I’ve omitted Hawaii in this analysis and included only North and South America. The one individual selecting Native Hawaiian (Kanaka Maoli) is in haplogroup O-M133.

Let’s look at our three distinct clusters.

Cluster 1 – Pacific Northwest – Alaska and Canada

We have a cluster of three individuals along the Pacific Coast in Alaska and Canada who have self-identified as Native, provided a tribal affiliation, and, in some cases, the spoken language.

How might haplogroup O have arrived in or near Vancouver, Washington? We know that James Cook “discovered” Hawaii in 1778, naming it the Sandwich Islands. By 1787, a female Hawaiian died en route to the Pacific Northwest, and the following year, a male arrived. Hawaii had become a provisioning stop, and the Spanish took Hawaiians onto ships as replacement workers.

Hawaiian seamen, whalers, and laborers began intermarrying with the Native people along the West Coast as early as 1811. Their presence expanded from Oregon to Alaska. Migration and intermarriage along the Pacific coast began slowly, but turned into a steady stream 30 years later when we have confirmed recruitment and migration of Hawaiian people

In 1839, John Sutter recruited a small group of 10 Hawaiians to travel with him to the then-Mexican colony of Alta, California.

By the mid-1800s, hundreds of Hawaiians lived in Canada and California. In 1847, it was reported that 10% of San Francisco’s residents were Hawaiian. Some of those people integrated with the Native American people, particularly the Miwok and Maidu. The village of Verona, California was tri-lingual: Hawaiian, a Native language, and English, and is today the Sacramento-Verona Tribe.

This article provides a history of the British Company who administered Fort Vancouver, near Vancouver, Washington, that included French-Canadians, Native Americans and Hawaiians. In 1845, 119 Hawaiians were employed at the fort. One of the 119, Opunuia, had signed on as an “engagé,” meaning some type of hired hand or employee, with the Hudson Bay Company for three years, after which he would be free to return home to Honolulu or establish himself in the Oregon Country. He married a woman from the Cascade Tribe.

The descendants of the Hawaiian men and Native women were considered tribal members. In most tribes, children took the tribal status and affiliation of the mother.

The Taku and Sitka, Alaska men on the map are Tlingit, and the man from British Columbia is from the Fountain Indian Reserve.

Hawaiian recruitment is the most likely scenario by which haplogroup O arrived in the tribes of the Pacific Northwest. In that sense, haplogroup O is indeed Native American but not indigenous to that region. The origins of haplogorup O in the Pacific Northwest are likely found in Hawaii, where it is indigenous, and before that, Polynesia – not due to a Beringian crossing.

Cluster 2 – Mexico

We find a particularly interesting small cluster of 4 haplogroup O individuals in interior Mexico.

In the 1500s, Spain established a trade route between Mexico and Manilla in the Philippines.

In 1564, four ships left Mexico to cross the Pacific to claim Guam and the Philippines for King Philip II of Spain. The spice trade, back and forth between Mexico and the Philippines began the following year and continued for the next 250.

Landings occurred along the California coast and the western Mexican coastline. The majority of the galleon crews were Malaysian and Filipino who were paid less than the Spanish sailors. Slaves, including people from the Marianas were part of the lucrative cargo.

One individual in Texas reports haplogroup O and indicates their paternal ancestors were Hispanic/Native from Mexico. A haplogroup O cluster claiming Native heritage is found near Zacatecas, Fresnillo and San Luis Potosi in central Mexico. Additionally, mitochondrial haplogroup F, also Asian, is found there as well. Acapulco is the lime green pin.

An additional haplogroup O tester with Native heritage is found in Lima, Peru.

Haplogroup O men are found in Panama, Jamaica and Cuba, but do not indicate the heritage of their paternal ancestral line. None of these men have taken Big-Y tests, and some may well have arrived on the slave ships from Madagascar, especially in the Caribbean. This source attributes some enslaved people in Jamaica to Hawaiian voyages.

I strongly suspect that the Mexican/Peru grouping in close proximity to the Pacific coastline is the result of the Manilla-Mexico 250-year trade route. The Spanish also plied those waters regularly. Big Y testing of those men would help flesh-out their stories – when and how haplogroup O arrived in the local population.

Cluster 3 – East Coast

At first glance, the East Coast grouping of men with a genetic affinity to the people of the Philippines and Indonesia seems more difficult to explain, but perhaps not.

On the East Coast, we have confirmed reports of whalers near Nantucket as early as 1765 utilizing crewmen from Hawaii, known then as the Sandwich Islands, Tahiti, and the Cape Verde Islands off of Africa. A thorough review of early literature might well reveal additional information about early connections with the Sandwich Islands, and in particular, sailors, crew, or enslaved people.

The Spanish and French were the first to colonize the Philippines by the late 1500s. They had discovered the Solomon Islands, Melanesia, and other Polynesian Islands, and by the early 1600s, the Dutch were involved as well.

The Encyclopedia Britanica further reports that Vasco Balboa first sailed into the Pacific in 1513 and seven years later, Ferdinand Magellan rounded the tip of South America. The Spanish followed, establishing a galley trade between Manila, in the Philippines and Acapulco in western Mexico.

While I found nothing specific stating that the earliest voyages brought men from the Philippines and Oceania back to their European home ports with them, we know that early European captains on exploratory voyages took Native people from the east coast of the Americas on their return journey, so there’s nothing to preclude them from doing the same from the Pacific. The early explorers stayed for months among the Oceanic Native peoples. If they were short on sailors for their return voyage, Polynesian men filled the void.

We know that the Spanish took slaves as part of their trade. We know that the ships in the Pacific took sailors from the islands. If the men themselves didn’t stay in the locations they visited, it’s certainly within the realm of possibility that they fathered children with local, Native women. Furthermore, given that the slave trade was lucrative, it’s also possible that some Pacific Island slaves were taken not as crew but with the intention of being sold into bondage. Other men may have escaped the ships and hidden among the Native Tribes along the eastern seaboard.

Fishing in Newfoundland and exploration in what would become the US was occurring by 1500, so it’s certainly possible that some of the indigenous people from Indonesia and the Philippines were either stranded, sold to enslavers, escaped, or chose to join the Native people along the coastline in North America. Ships had to stop to resupply rations and take on fresh water.

We know that by the mid-1600s, James Revels, whose father carried haplogroup O, had been born on the Atlantic coast of Virginia or Maryland, probably on the Delmarva Peninsula, short for Delaware, Maryland, Virginia, where the Accomac people lived.

There are other instances of haplogroup O found along the east coast.

On the eastern portion of the haplogroup O map from the book, DNA for Native American Genealogy, we find the following locations:

  • Hillburn, NY – man identified as “Native American Black.”
  • Chichester County, PA – Genographic tester identified the location of his earliest known ancestor – included here because O is not typically found in the states.
  • Accomack County, VA – Delmarva peninsula – James Revels lineage
  • Robeson County, NC – Lewis and Revels surname associated with the Lumbee
  • Chatham County, NC – Lynn ancestor’s earliest known location
  • Greene County, NC – enslaved Blount ancestor’s EKA in 1849

The genesis of Mr. Blount’s enslaved ancestor is unclear. Fortunately, he took a Big Y-700 test.

Mr. Blount’s only Big-Y match is to a man from the United Arab Emirates (UAE), but the haplogroup history includes Thailand, which is the likely source of both his and his UAE matches’ ancestors at some point in time. Their common ancestor was in Thailand in 336 CE, almost 1700 years ago.

All surrounding branches of haplogroup O on the Time Tree have Asian testers, except for the one UAE gentleman.

The Blount Haplogroup O-FTC77008 does not connect with the common ancestral haplogroup of Lynn and Revels, so these lineages are only related someplace in Oceana prior to O-F265, or more about  30,000 years ago. Their only commonality other than their Asian origins is that they arrived on the East Coast of the Americas.

We know that the Spanish were exploring the Atlantic coastline in the 1500s and were attempting to establish colonies. In 1566, a Spanish expedition reached the Delmarva Peninsula. This spit of land was contested and changed hands several times, belonging variously to the Spanish, Dutch, and British by 1664.

Furthermore, we also know that the ships were utilizing slave labor. One of the Spanish ships wrecked in the waters off North Carolina near Hatteras or Roanoke Island before the Lost Colony was abandoned on Roanoke Island in 1587. The Croatan Indians reported that in memorable history, several men, some of whom were reported to be slaves, had survived the wreck and “disappeared” into the hinterlands – clearly running for their lives.

These men, if they survived, would have been incorporated into the Native population as there were no other settlements at the time. Variations of this scenario may have played out many times.

James Revels’ ancestor could have arrived on any ship, beginning with exploration and colonization in the early 1500s through the mid-1650s.

By the time the chief bound the Indian boy who was given the English name James to Edward Revell, James’s Oceanic paternal ancestor could have been 4, 5 or 6 generations in the past – or could have been his father.

The Accomack was a small tribe, loosely affiliated with the Powhatan Confederacy along the Eastern Shore. By 1700, their population had declined by approximately 90% due to disease. A subgroup, the Gingaskins, intermarried with African Americans living nearby. After Nat Turner’s slave rebellion of 1831, they were expelled from their homelands.

The swamps near Lumberton in Robeson County, NC, became a safe haven for many mixed-race Native, African, and European people. The swamps protected them, and they existed, more or less undisturbed, for decades. Revels and Lewis descendants are both found there.

Many Native Americans were permanently enslaved alongside African people – and within a generation or so, their descendants knew they were Native and African, but lost track of which ancestors descended from which groups. Life was extremely difficult back then. Generations were short, and enslaved people were moved from place to place and sold indiscriminately, severing their family ties entirely, including heritage stories.

Returning to the Discover Time Tree Maps

Wesley Revels has STR matches with several men from Indonesia, China, and the Philippines. It would be very helpful if those men would upgrade to the Big Y-700 so that we can more fully complete the haplogroup O branches of the Time Tree.

The common Revels/Lewis ancestor, accompanied by two descendant men on different genetic branches from the Philippines, was born about 5180 years ago. There is no evidence to suggest Haplogroup O-FT11768 was born anyplace other than in the Philippines.

How did the descendant haplogroups of O-FT45548 (Revels, Lewis, and an unnamed man) and O-F22410 (Lynn) arrive in Virginia or anyplace along the Atlantic seaboard?

Hawaii wasn’t settled until about 1600 years ago. We know Hawaiians integrated with the Pacific Coast Native tribes in the 1800s, but James Revels was in Virginia in 1656..

We know that the Spanish established a mid-1500s trade route between Manila and Acapulco, leaving their genetic signature in western Mexico.

None of these events fit the narrative for the Revels or the Lynn paternal ancestor.

Furthermore, the Revels and Lynn lines do not connect on North American soil, as both descend from the same parent haplogroup, O-FT11768, 5180 years ago in the Philippines. This location and history suggest a connection with the Spanish galleon trade era. The haplogroup formation clearly predates that trade, which means those men were still in the Philippines, not already living on the American continents. Therefore, the descendants of the haplogroup O-FT11768 arrived in Virginia and North Carolina sometime after that haplogroup formation 5100 years ago.

The Lynn ancestor connects with a man from Singapore in 760 CE, or just 1240 years ago. A descendant of haplogroup O-F22410 arrived in North Carolina sometime later.

It does not appear, at least not on the surface, that there is a connection through Madagascar, although we can’t rule that out without additional testers. If the connection is through Madagascar, then their ancestors were likely transported from Indonesia to Madagascar, then as enslaved people from Madagascar to the Atlantic colonies to be sold. However, James Revels was not enslaved. He was clearly Native and bound to a European plantation owner, who did, in fact, free him as agreed and subsequently loaned him money.

Based on the dates involved, and when we know they were in Oceania, an arrival along the west coast, followed by a quick migration across the country to a peninsula of land in the Atlantic, is probably the least likely scenario. There is also no historical or ancient haplogroup O DNA found anyplace between the west and east coasts, nor in the Inuit or Na-Dene speakers. The Navajo, who speak the Na-Dené language, migrated to the Southwest US around 1400 CE, but haplogroup O has not been found among Na-Dené speakers.

It’s a long way from Singapore and the Philippines to Madagascar, so while the coastal migration scenario is not impossible, it’s also not probable, especially given what we know about the Spanish Pacific trade that existed profitably for 250 years.

However, one haplogroup O subgroup arrived in the UAE by some methodology after 336 CE.

It’s entirely possible, indeed probable, that haplogroup O arrived in the Americas for various reasons, on different paths, in different timeframes.

Haplogroup O was found in people in the Americas after colonization had begun. There has been no ancient Haplogroup O DNA discovered, and there’s evidence indicating that these instances of haplogroup O could not have arrived in any of the known Beringia migrations nor the theorized Coastal or Kelp migration. We know the East Coast Cluster is not a result of the West Coast 19th-century migration because James Revels was in court one hundred and fifty years before the Hawaiians were living among the Native people along the Pacific coastline.

There’s nothing to indicate that the Mexican group that likely arrived beginning in the mid-1500s for the next 250 years as a result of the Indonesian trade route migrated to the east coast, or vice versa. That’s also highly unlikely.

The most likely scenario is that Mr. Lynn’s, Mr. Blount’s, and James Revels’ ancestors were brought on trade ships, either as sailors or enslaved men. They may not have stayed, simply visited. They may each have arrived in a completely different scenario, meaning Mr. Blount’s ancestors could have been enslaved arrivals from Madagascar, Mr. Lynn’s from Indonesia, and Mr. Revel’s as a crew member on a Spanish ship. We simply don’t know.

James Revels’ descendants were Native through his mother’s tribe, as confirmed in the 1667 court records. However, the Revels and Lynn lineages weren’t Native as a result of their paternal haplogroup O ancestors crossing Beringia into the Americas with Native American haplogroups Q and C. Instead, the Lynn and Revels migration story is quite different. Their ancestors arrived by ship. The journey was long, perilous, and far more unique than we could have imagined, taking them halfway around the world by water.

Timeline

There’s a lot of information to digest, so I’ve compiled a timeline incorporating both genetic and historical information for easy reference.

  • 30,000 years ago (28,000 BCE) – haplogroup O-F265, common Asian ancestor  of Mr. Blount, the Revels/Lewis group, Mr. Lynn, and an unknown Big-Y tester in the Malagasy group project
  • 12,000-16,000 years ago – Indigenous Americans arrived across now-submerged Beringia
  • 12,000-16,000 years ago – possible Coastal Migration route may have facilitated a secondary source of indigenous arrival along the Pacific coastline of the Americas
  • 4000-7000 years ago – circumpolar migration arrival of Inuit and Na-Dené speakers found in the Arctic polar region and the Navajo in the Southwest who migrated from Alaska/Canada about 1400 CE
  • 5180 years ago (3180 BCE) – haplogroup O-FT11768, the common ancestor of Mr. Lynn and the Revels/Lewis group with many subgroups in the Philippines, Hawaii, Singapore, Brunei, China, Sumatra, and Thailand
  • 2244 years ago (244 BCE) – haplogroup O-CTS716, the common ancestor of Wesley Revels and Mr. Luo from Indonesia
  • The year 336 CE, 1684 years ago – haplogroup O-FTC77008, the common ancestor of Mr. Blount, UAE tester and a man from Thailand
  • 400 CE, 1600 years ago  –  Hawaii populated by Polynesian people
  • 760 CE, 1240 years ago – haplogroup O-F22410, common ancestor of Mr. Lynn with a Singapore man
  • 1492 CE, 528 years ago – Columbus begins his voyages to the “New World,” arriving in the Caribbean
  • By 1504 CE – European fishing began off of Newfoundland
  • 1565 – Spain claimed Guam and the Philippines
  • 1565 – Spanish trade between Manilla and Acapulco begins and continues for 250 years, until 1815, using crews of men from Guam, the Philippines, and enslaved people from the Marianas.
  • 1565 – St. Augustine (Florida) was founded by the Spanish as a base for trade and conquest along the eastern seaboard
  • 1566 – A Spanish expedition reached the Delmarva peninsula intending to establish a colony, but bad weather thwarted that attempt.
  • 1585-1587 – voyages of discovery by the English and the Lost Colony on Roanoke Island, North Carolina
  • 1603 – English first explored the Delmarva Peninsula, home to the Accomac people, now Accomack County, VA, where James Revels’s court record was found in 1667
  • 1607 – Jamestown, Virginia, founded by the English
  • 1608 – Colonists first arrived on the Delmarva Peninsula and allied with Debedeavon, whom they called the “laughing King” of the Accomac people. At that time, the Accomac had 80 warriors. Debedeavon was a close friend to the colonists and saved them from a massacre in 1622. He died in 1657.
  • 1620 – The Mayflower arrived near present-day Provincetown, Massachusetts
  • 1631-1638 – Dutch West India Company established a colony on the Delmarva Peninsula, but after conflicts, it was destroyed by Native Americans in 1638. The Swede’s colony followed, and the region was under Dutch and Swedish control until it shifted to British control in 1664
  • 1656 – Birth of James Revels, confirmed in a 1667 court record stating that he was an Accomack “Indian boy” from “Matomkin,” judged to be age 11, bound to Edward Revell. This location is on the Delmarva Peninsula.
  • 1741 CE –  Haplogroup O-BY60500 formation date that includes all of the Revels and Lewis testers who descend from James Revels born in 1656
  • 1765 – Whalers near Nantucket using crewmen from Hawaii (Sandwich Islands), Tahiti, and the Cape Verde Islands off of Africa
  • 1766 CE – Formation date for haplogroup O-FT45548, child haplogroup of O-BY60500, for some of the Lewis and Revels men who all descend from James Revels born in 1656
  • 1778 – Captain Cook makes contact with Hawaiian people
  • 1787 – The first male arrived in the Pacific Northwest from Hawaii
  • 1811 – Hawaiian seamen begin intermarrying with Native American females along the Pacific shore, eventually expanding their presence from Oregon to Alaska
  • 1839 – John Suter recruits Hawaiian men to travel with him to California
  • 1845 – Hawaiians employed by Fort Vancouver, with some marrying Native American women

Conclusions

It’s without question that James Revels was Native American very early in the settlement of the Delmarva Peninsula, now Accomack County, Virginia, but his common ancestor with Filipino men 5100 years ago precludes his direct paternal ancestor’s presence in the Americas at that time. In other words, his Revel male ancestor did not arrive in the Beringian indigenous migration 12,000-16,000 years ago. His ancestor likely arrived post-contact, based on a combination of both historical and genetic evidence.

Haplogroup O is not found in the Arctic Inuit nor the Na-Dene speakers, precluding a connection with either group, and has never been found in ancient DNA in the Americas.

Haplogroup O in the Revels lineage is most likely connected with the Spanish galleon trade with the Philippines and the early Spanish attempts to colonize the Americas.

The source of Haplogroup O in the Pacific Northwest group is likely found in the recruitment of Hawaiian men in the early/mid-1800s.

The Mexican Haplogroup O group likely originated with the Manilla/Mexico Spanish galleon trade.

The source of the Blount Haplogroup O remains uncertain, other than to say it originated in Thailand thousands of years ago and is also found in the UAE. The common Blount, UAE, and Thailand ancestor’s haplogroup dates to 336 CE, so they were all likely in or near Thailand at that date, about 1687 years ago.

What’s Next?

Science continuously evolves, revealing new details as we learn more, often clarifying or shifting our knowledge. Before the Discover tool provided haplogroup ages based on tests from men around the world, we didn’t have the necessary haplogroup origin and age data to understand the genesis of haplogroup O in the Americas. Now, we do, but there is invariably more to learn.

New evidence is always welcome and builds our knowledge base. Haplogroup O ancient DNA findings would be especially relevant and could further refine what we know, depending on the location, dates of the remains, who they match, and historical context.

Additional Big Y-700 tests of haplogroup O men, especially those with known genealogy or ancestor location, including Madagascar, would be very beneficial and allow the haplogroup formation dates to be further refined.

If you are a male with haplogroup O, please consider upgrading to the Big Y-700 test, here.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Haplogroups: DNA SNPs Are Breadcrumbs – Follow Their Path

Recently a reader asked some great questions.

If Y-DNA is unchanged, then why isn’t the Y-DNA of every man the same today? And if it’s not the same, then how do we know that all men descend from Y-Adam? Are the scientists just guessing?

The scientists aren’t guessing, and the recent scientific innovations behind how this works is pretty amazing, so let’s unravel these questions one at a time.

The first thing we need to understand is how Y-DNA is inherited differently from autosomal DNA, and how it mutates.

First, a reminder that:

  • Y-DNA tests the Y chromosome passed from father to son in every generation, unmixed with any DNA of the mother. This article focuses on Y-DNA.
  • Mitochondrial DNA tests the mitochondria passed from mothers to all of their children, but is only passed on by the females, unmixed with the DNA of the father. This article also pertains to mitochondrial SNPS, but we will cover that more specifically later in another article.
  • Autosomal DNA is passed from both parents to their children. Each child inherits half of each parent’s autosomal DNA.

Let’s look at how this works.

Autosomal vs Y-DNA Inheritance

Click on image to enlarge

Autosomal DNA, shown here with the green (male) and pink (female) images, divides in each generation as it’s passed from the parent to their child. Each child inherits half of each parent’s autosomal DNA, meaning chromosomes 1-22. For this discussion, each descendant shown above is a male and has a Y chromosome.

This means that in the first generation, which would be the great-grandfather, about 700,000 locations of his green autosomal DNA are tested for genealogy purposes.

His female partner (pink) also has about 700,000 locations. During recombination, they each contribute about 350,000 SNPs (Single Nucleotide Polymorphisms) of autosomal DNA to their child. Their offspring then has a total of 700,000 SNPs, 350,000 green and 350,000 pink contributed by each parent.

This process is repeated for each child, whether male or female (with the exception of the X chromosome, which is beyond the scope of this article), but each child does not receive exactly the same half of their parents’ autosomal DNA. Recombination is random.

In the four generations shown above, the green autosomal DNA of generation one, the great-grandfather, has been divided and recombined three times. The original 700,000 locations of great-grandfather’s green DNA has now been whittled down to about 87,500 locations of his green DNA.

Y-DNA in the Same Generation

Looking now at the blue Y-DNA at left, the Y-DNA remains the same in each generation with the exception of one mutation approximately every two or three generations.

As you can see in the chart, in the exact same number of generations, the Y-DNA of each male, which he inherited from his father:

  • Never recombines with any DNA from the mother
  • Never divides and gets smaller in subsequent generations
  • Remains essentially unchanged in each generation

The key word here is “essentially.”

Y-DNA

The Y chromosome consists of about 59 million locations or SNPs of DNA. STR tests, Short Tandem Repeats, which are essentially insertions and deletions, test limited numbers of carefully curated markers selected for the fact that they mutate in a genealogically relevant timeframe. These markers are combined in panels of either 67 or 111 marker tests available for purchase at FamilyTreeDNA today, or historically 12, 25, 37, 67, and 111 marker panels. The STR test was the original Y-DNA test for genealogy and is still used as an introductory test or to see if a male matches a specific line, or not.

From the STR tests, in addition to matching, FamilyTreeDNA can reliably predict a relatively high-level haplogroup, or genetic clan, based on the frequency of the combinations of those marker values in specific STR locations.

SNPs are much more reliable than STRs, which tend to be comparatively unstable, mutating at an unreliable rate, and back mutating, which can be very disconcerting for genealogy. We need reliable consistency to be able to assign a male tester to a specific lineage with confidence. We can, however, find genealogically relevant matches that may be quite important, so I never disregard STR tests or testers. STR tests aren’t relevant for deeper history, nor can they reliably discern a specific lineage within a surname. SNP tests can and do.

The Big Y-700 SNP test gives us that and more, along with the earlier Big Y-500 test which scanned about 30 million locations. The Big Y-700 is a significant improvement; men can upgrade from the Big Y-500 or STR tests.

The Big Y-700 test scans about 50 million Y-DNA locations, known as the gold standard region, for all mutations. It reports 700 or more STR markers for matching, but more importantly, it scans for all SNP mutations in those 50 million locations.

All mutations are confirmed by at least five positive repeat scans and are then assigned a haplogroup name if found in two or more men.

Y-DNA Testing

If Y-DNA remained exactly the same, then the Y-DNA of men today would be entirely indistinguishable from each other – essentially all matching humankind’s first common ancestor. With no changes, Y-DNA would not be useful for genealogy. We need inherited mutations to be able to compare men and determine their level of relatedness to each other.

Fortunately, Y-DNA SNPs do mutate. Y-DNA is never divided or combined, so it stays essentially the same except for occasional mutations which are inherited by the following generations.

Using SNP markers scanned in the Big Y test, one new mutation happens on the average of every two or three generations. Of course, that means that sometimes there are no mutations for a few generations, and sometimes there are two mutations between father and son.

What this does, though, very effectively, is provide a trail of SNP mutations – breadcrumbs essentially – that we can use for matching, AND for tracking our mutations, which equate to ancestors, back in time.

Estes Male Breadcrumb Trail

I’ve tested several Estes men of known lineage, so I’m going to use this line as an example of how mutations act as breadcrumbs, allowing us to track our ancestors back in time and across the globe.

Multiple cousins in my Estes line have taken the Big Y-700 test.

My closest male cousin matches two other men on a unique mutation. That SNP has been named haplogroup R-ZS3700.

We know, based on our genealogy, that this mutation occurred in Virginia and is found in the sons of Moses Estes born in 1711.

How do we know that?

We know that because three of Moses’s descendants have tested and all three of those men have the same mutation, R-ZS3700, and none of the sons of Moses’s brothers have that mutation.

I’ve created a chart to illustrate the Estes pedigree chart, and the haplogroups assigned to those men. So, it’s a DNA pedigree chart too. This is exactly what the Big-Y DNA test does for us.

In the red-bordered block of testers, you can see the three men that all have R-ZS3700 (in red), and all are sons of Moses born in 1711. I have not typed the names of all the men in each generation because, for purposes of this illustration, names aren’t important. However, the concept and the fact that we have been able to connect them genealogically, either before or because of Y-DNA testing, is crucial.

Directly above Moses born in 1711, you can see his father Abraham born in 1647, along with Moses’ brothers at right and left; John, Richard, Sylvester, and Elisha whose descendants have taken the Big Y-700 test. Moses’s brothers’ descendants all have haplogroup R-BY490 (in blue), but NOT R-ZS3700. That tells us that the mutation responsible for R-ZS3700 happened between Abraham born in 1647, and Moses born in 1711. Otherwise, Moses’s brothers would have the mutation if his father had the mutation.

Moses’s descendants also have R-BY490, but it’s NOT the last SNP or haplogroup in their lineage. For Moses’s descendants, R-ZS3700 occurred after R-BY490.

You can see haplogroup R-BY490 boxed in blue.

We know that Moses and his father, Abraham, both have haplogroup R-BY490 because all of Abraham’s sons have this haplogroup. Additionally, we know that Abraham’s father, Silvester also had haplogroup R-BY490.

How do we know that?

Abraham’s brother, Richard’s descendant, tested and he has haplogroup R-BY490.

However, Silvester’s father, Robert born in 1555 did NOT have R-BY490, so it formed between him and his son, Silvester.

How do we know that?

Robert’s other son, Robert born in 1603 has a descendant who tested and has haplogroup R-BY482, but does NOT have R-BY490 or R-ZS3700.

All of the other Eates testers also have R-BY482, blocked in green, in addition to R-BY490, so we know that the mutation of R-BY490 developed between Robert born in 1555 and his son, Silvester born in 1600, because his other son’s descendant does not have it.

Looking at only the descent of the haplogroups, in order, we have

  • R-BY482 (green) found in Robert born in 1555 and all of his descendants.
  • R-BY490 (blue) found in Silvester born in 1600 and all of his descendants, but not his brother
  • R-ZS3700 (red) found in Moses born in 1711 and all of his descendants, but not his brothers

If we had Estes men who descend from the two additional documented generations upstream of Robert born in 1555, we might discover when R-BY482 occurred, but to date, we don’t have any additional testers from those lines.

Now that we understand the genesis of these three haplogroups in the Estes lineage, what else can we discover through our haplogroup breadcrumbs?

The Discover Reports

By entering the haplogroup in the Discover tool, either on the public page, here, or clicking on Discover on your personal page at FamilyTreeDNA if you’ve taken the Big-Y test, you will see several reports for your haplogroup.

I strongly suggest reviewing each category, because they cumulatively act as chapters to the book of your haplogroup story, but we’re going to skip directly to the breadcrumbs, which is called the Ancestral Path.

The Ancestral Path begins with your haplogroup in Line 1 then lists the first upstream or parent haplogroup in Line 2. In this case, the haplogroup I entered is R-ZS3700.

You can see the estimated age of the haplogroup, meaning when it formed, at about 1700 CE. Moses Estes who was born in 1711 is the first Estes man to carry haplogroup R-ZS3700, so that’s extremely close.

Line 2, R-BY490 occurred or was born about 1650, and we know that it actually occurred between Robert and Silvester born in 1600, so that’s close too.

Scanning down to Line 3, R-BY482 is estimated to have occurred about 1500 CE, and we know for sure it had occurred by 1555 when Robert was born.

We see the parent haplogroup of R-BY487 on Line 4, dating from about 750 CE. Of course, if more men test, it’s possible that more haplogroups will emerge between BY482 and BY487, forming a new branch. Given the time involved, those men wouldn’t be expected to carry the Estes surname, as surnames hadn’t yet been adopted in that timeframe.

Moving down to Line 9, we see R-ZP18 from 2250 BCE, or about 4250 years ago. Looking at the right column, there’s one ancient sample with that haplogroup. The location of ancient samples anchors haplogroups definitively in a particular location at a specific time.

Haplogroup by haplogroup, step by step, we can follow the breadcrumbs back in time to Y-Adam, the first homo sapiens male known to have descendants today, meaning he’s the MRCA, or most recent common ancestor for all men.

Neanderthals and Denisovans follow, but their Y-DNA is only available through ancient samples. They have no known direct male survivors, but someday, maybe someone will test and their Y-DNA will be found to descend from Neanderthals or Denisovans.

Now that we know when those haplogroups occurred, how did our ancestors get from Africa 232,000 years ago to Kent, England, in the 1400s? What path did they take?

The new Globetrekker tool answers that question.

The Breadcrumb Trail

In Globetrekker, each haplogroup’s location is placed by a combination of testers’ results, their identified earliest known ancestor (EKA) country and location, combined with ancient samples, climatic factors like glaciers and sea levels, and geographic features. You can read about Globetrekker here and here.

To view the Globetrekker tool, you must sign it to an account that has taken the Big Y test. It’s a tool exclusively provided for Big-Y testers.

You can click at the bottom of your Globetrekker map to play the animated video.

Beginning in Africa, our ancestors began their journey with Y-Adam, then migrated through the Near East, South Asia, East Asia, then west through central Asia into Europe. The Estes ancestors crossed the English Channel and migrated around what is now England before settling in Deal, on the east coast.

Clicking on any haplogroup provides a description of that haplogroup and how it was placed in that location.

Enabling the option for ancient DNA shows those locations as well, near the haplogroups they represent when the animation is playing.

Clicking on the shovel icon explains about that particular ancient DNA sample, what is known, and how it relates to the haplogroup it’s connected to by a dotted line on the map.

Pretty cool, huh!!

End to End

As you can see from this example, Big Y results are an end-to-end tool.

We can use the Big Y-700 haplogroups very successfully for recent genealogy – assigning testers to specific lines in a genealogy timeframe. Some haplogroups are so specific that, without additional information, we can place a man in his exact generation, or within a generation or two.

Not shown in my Estes pedigree chart is an adoptee with a different surname, of course. We know that he descends from Moses’s line because he carries haplogroup R-ZS3700, but we are still working on the more recent generations using autosomal DNA to connect him accurately.  If more of Moses’s descendants tested, we could probably place him very specifically. Without the Big Y-700 test, he wouldn’t know his biological surname or that he descends from Moses. That’s a HUGE breakthrough for him.

There’s more about the Estes line to learn, however.

If our Estes cousins tested their brothers, uncles or other Estes males in their line, they would likely receive a more refined haplogroup that’s relevant only to that line.

Using Big-Y test results, we can place men within a couple of generations and identify a common ancestor, even when all men within a haplogroup don’t know their genealogical lineage. Using those same test results, we can follow the breadcrumbs all 50 steps back in time more than 230,000 years to Y-Adam.

End to end, the Big-Y test coupled with breadcrumbs in Discover, Globetrekker, and other amazing tools is absolutely the most informative and powerful test available to male testers for their paternal line genealogy.

These amazing innovations tracking more than 50,000 haplogroups across the globe answer the original questions about how we know.

The more people who take or upgrade to the Big Y-700 test, the more haplogroup branches will be added, and the more refined the breadcrumbs, ages, and maps will become. In other words, there’s still more to learn.

Test if you haven’t, and check back often for new matches and breadcrumbs, aka updates.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

 

Genealogy Books

  • com – Lots of wonderful genealogy research books
  • American Ancestors – Wonderful selection of genealogy books

Genealogy Research