Six Ways to Figure Out How We’re Related

In my latest Webinar, Six Ways to Figure Out How We’re Related, I discuss the various tools from Ancestry, FamilyTreeDNA, MyHeritage, and 23andMe – plus clusters from Genetic Affairs and the amazing DNAPainter.

This webinar lives in the Legacy Family Tree Webinar library, but as part of the “webtember” lineup, you can view it for free through the end of September.

It’s always exciting to discover a new match at one of the DNA testing companies, which, of course, begs the question of how you’re related.

So, what are the six ways to figure out how you’re related, and how do you use them?

Come along for a step-by-step guide!

Shared Matches

We begin with how each vendor handles shared matches, what that feature is called, where to find the information, and how to interpret what they are telling you.

23andMe goes a step further and creates a genetic tree, of sorts, although that functionality has changed since their breach last October.

Bucketing and Sides

Two vendors go a step further and provide unique tools to divide your matches maternally and paternally.

FamilyTreeDNA buckets your matches maternally and paternally (or both) based on matches you link to their profile cards in your tree. FamilyTreeDNA then uses your linked matches to triangulate with other matches and assign your matches accordingly, providing a maternal and paternal match list. Bucketing, also known as Family Matching, is one of my favorite tools.

Note that linking matches at FamilyTreeDNA requires that you have transferred your tree to MyHeritage. I wrote about that and provided instructions here and here, and produced a complimentary webinar, too.

Ancestry also divides your matches by parent, but they use a different technique based on their Sideview technology and either ethnicity or shared matches.

Surnames and Locations

Surnames and locations, either separately or together, provide HUGE hints!

MyHeritage provides a nice summary for each of your matches that includes ancestral surnames, a map of locations in common, and “Smart Matches” which shows you people in common in both of your trees. There are several ways to use these tools.

FamilyTreeDNA also provides a list of surnames. You can view either the surnames in common with a match, or all of their ancestral surnames, with locations if provided. The tester enters these surnames, and we review how to complete that step.

Ancestry also provides shared surnames, with clickable links to the number of people in your matches tree with that surname, plus common locations.

X-DNA

X-DNA is probably the most underutilized DNA matching tool. While each of the vendors actually test the X chromosome, only one, FamilyTreeDNA, provides X-matching. You can obtain X-matching results by uploading your DNA file to FamilyTreeDNA. I’ve provided upload/download instructions for all companies, here.

X-DNA has a very unique inheritance pattern because males only inherit an X chromosome from their mother which limits the number of potential common ancestors for any two testers. In other words, X-DNA matching does half your work for you!

Clustering Technology – AutoClusters, the Matrix and DNAPainter

In the past few years, match clustering has become a very useful tool. Clustering shows which of your matches match you and each other.

Genetic Affairs offers several flavors of these clusters, and both MyHeritage and GEDmatch have incorporated Genetic Affairs clusters into their product offerings.

If you haven’t used AutoClusters yet, by all means, try them out.

FamilyTreeDNA offers the Matrix, a slightly different version of clustering. You can select 10 people from your match list to see if they also match each other. Shared matches don’t automatically mean triangulation between you and those two people, or even that all three people descend from the same line. However, if the people are bucketed to your same side (parent) and they share common segments with you in the chromosome browser, they triangulate.

You’ll want to paint those matches to DNAPainter to determine which ancestor you share, especially if they haven’t provided a tree.

DNAPainter provides your chromosomes as the “canvas” upon which to paint your matches in order to correlate segments with ancestors and identify common ancestral lines with mystery matches.

Three vendors, FamilyTreeDNA, MyHeritage, and GEDmatch provide segment information with matches for you to paint. I illustrate how I walk segments back in time, identifying our most distant common ancestor possible.

Theories of Family Relativity and ThruLines

Both MyHeritage and Ancestry provide a combination of DNA matching and tree triangulation, where they search the trees of your DNA matches to find common ancestors with you – although their implementation is different.

MyHeritage’s Theories of Family Relativity provides varying theories about common ancestors for you and a specific match using both trees and historical documents. You can review the various pathways and confirm or reject theories. I love this tool.

Ancestry’s Thrulines functions a bit differently, showing you all of your matches that descend from a common ancestor in all your matches’ trees. Sometimes, the trees are incorrect, but Theories of Family Relativity and ThruLines should still be used as hints.

I showed how ThruLines helped me discover what happened to one of my ancestor’s grandchildren who was lost to the family at his mother’s death – and to all of us since. Not anymore.

Bonus – Y-DNA and Mitochondrial DNA at FamilyTreeDNA

Only FamilyTreeDNA offers both Y-DNA and Mitochondrial DNA testing and matching. All of the tools above pertain to autosomal DNA testing, which is named Family Finder at FamilyTreeDNA. Illustrated by the green arrow below, autosomal DNA testing measures and compares the DNA you inherited from each ancestral line, but that’s not the only game in town.

Y-DNA, in blue, for males, tracks the direct paternal line, which is the surname line in Western cultures. Mitochondrial DNA, in red, is passed from mothers to all of their children. Therefore, everyone can test, revealing matches and information about their mother’s direct matrilineal lineage.

Y-DNA testing includes the amazing Discover tool with a baker’s dozen different reports, including ancient DNA. Mitochondrial DNA will soon have its own MitoDiscover after the rollout of the new Mitotree.

Both tests include “Matches Maps” to help you determine how you are related to your matches, as well as where your ancestors came from before the advent of surnames.

The Advanced Matching feature allows you to select multiple tests to see if your matches match you on combined types of tests.

Tune In

Now that you know what we cover in the webinar, please tune in to see how to use these awesome tools. Be sure to fish in all four “ponds” plus GEDmatch, where you may find people who didn’t test at a company that provides a chromosome browser or matching segment information.

Tools provided by the DNA testing vendors facilitate multiple ways to determine how we match and which ancestor(s) we have in common.

You can watch the webinar, here.

Additionally, subscribers to Legacy Family Tree Webinars have access to the 25-page syllabus with even more information!

A Legacy Family Tree Webinar subscription normally costs $49.95 per year, but through the end of September, there’s a coupon code good for 20% off. Just click here, then enter webtember24 at the checkout.

Enjoy!

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

FamilyTreeDNA Summer Sale Ends Soon

Rarely does FamilyTreeDNA put all of their products on sale at the same time, but this Summer Sale is a notable exception.

Not only are all new tests on sale, but so are upgrades, including mitochondrial and Y-DNA STR to Big Y-700 upgrades. So, if you’ve tested at the Y-DNA 37, 67, or 111 marker level, this is the perfect opportunity to discover more.

Plus, there are GREAT prices on bundles of multiple tests. If you aren’t sure which tests are beneficial for what, the article, 4 Kinds of DNA for Genetic Genealogy will help you sort things out.

If you’ve been considering a test or an upgrade for yourself or another family member, now’s a great time. I asked permission to upgrade a cousin’s Y-DNA just this morning, and he gladly agreed. I added a Family Finder test, too, because knowing who else in our study group he matches will help determine how closely people are related.

This sale ends in 5 days, August 31st at 1:59 am CDT, so don’t miss this opportunity.

Just the Facts, Please

Here’s the non-marketing “just the facts” list of regular and sale prices for comparison.

Are you seeing someone over the upcoming holiday weekend that would be a good testing candidate? What brick walls might be broken down?

Single Products
Product Regular Price Sale Price
Family Finder $79 $49
Autosomal Transfer Unlock  $19 $10
Mitochondrial mtFull Sequence  $159 $129
Y-37 $119 $99
Y-111 $249 $209
Big Y-700 $449 $399
Bundles
Bundle Regular Price Sale Price
Family Finder + mtFull Sequence  $238 $169
Family Finder + Y-37 $198 $139
Family Finder + Y-111 $328 $249
Family Finder + Big Y-700 $528 $439
mtFull Sequence + Y-37 $278 $219
mtFull Sequence + Y-111 $408 $329
mtFull Sequence + Big Y-700 $608 $499
Family Finder + mtFull Sequence + Y-37 $357 $259
Family Finder + mtFull Sequence + Y-111 $487 $369
Family Finder + mtFull Sequence + Big Y-700 $687 $507
Upgrades
Upgrade Regular Price Sale Price
Y-12 to Y-37 $79 $59
Y-12 to Y-67 $149 $139
Y-12 to Y-111 $199 $159
Y-12 to Big Y-700 $399 $339
Y-25 to Y-37 $49 $39
Y-25 to Y-67 $119 $109
Y-25 to Y-111 $189 $139
Y-25 to Big Y-700 $389 $339
Y-37 to Y-67 $89 $69
Y-37 to Y-111 $139 $119
Y-37 to Big Y-700 $339 $299
Y-67 to Y-111 $89 $79
Y-67 to Big Y-700 $279 $229
Y-111 to Big Y-700 $239 $189
Big Y-500 to Big Y-700 $209 $189
Mitochondrial mtDNA to mtFull Sequence $119 $79
Mitochondrial mtDNA+ to mtFull Sequence $119 $79

_____________________________________________________________

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Y-DNA Highways of History: Fleshing Out Your Ancestors Using Discover Case Studies – Webinar Free for 7 Days!!

I’m so very pleased to announce with Legacy Family Tree Webinars, that we are offering a special midsummer surprise webinar – and it’s FREE through August 1st, here.

Thank you, Legacy Family Tree Webinars, for making this webinar free!

We are using FamilyTreeDNA’s free Discover tool to reveal our ancestors’ past and their path through history.

This webinar features fun ”how-to” case studies. Who doesn’t love a good story – especially ones that you can put to use in your own genealogy right away?

We begin with an overview.

  • What are reasonable testing goals for Y-DNA?
  • Why do we want to take Y-DNA tests anyway?
  • What can we discover when we test, and when we encourage our cousins to test?
  • Where and how do we find those cousins?

If you ladies are thinking, I WISH I had a Y chromosome to test, cheer up, because one of the topics I cover is how to find relevant family members, even distant members, who can test for your male ancestral lines.

History Revealed

Genealogists always want every piece of available information. Y-DNA testing does just that and reaches beyond the barrier of surnames. In fact, it reaches beyond the possibility of genealogical research with only one test.

There’s so much to learn.

Who were my ancestors, and where did they come from? How are they related to other people, including ancient burials and notable people who lived more recently?

I’m sharing several case studies from my own genealogy. Come join me on my journey.

  • I discovered that my ancestor is related to a burial along the old Roman Road in France. He lived there before the Romans arrived. What does that mean to me today, and how can I find out?
  • I’ll also share with you how I solved an adoption case within a generation with JUST Y-DNA, and then how I used autosomal DNA matches to augment and refine that information.
  • In another case, we learned something VERY interesting and quite unexpected, revealing either a secret or information that was never passed to contemporary family researchers. Y-DNA testing is the only way this would EVER have been revealed.
  • Another ancestor appears to have been a retired Roman soldier in England. How did I figure this out? I’ll show you.
  • My Jewish friend famously said “My ancestors are in my soul. I can’t get them out of my mind.” Can you relate? The Big Y-700 test proved that his ancestors settled in Spain and exactly when they migrated to Eastern Europe using a very unconventional approach that you can utilize too.
  • Another tester discovered that he and a famous lineage match. You’ll probably recognize this historical person and you might even be related yourself. Their ancestors are found in the baptismal records of the same church in England, but their common ancestor reaches back to the people buried beneath the Saxon tombstones outside.

How did we discover all of this???

Big Y-700 testing at FamilyTreeDNA, combined with the Discover tool, sprinkled from time to time with some old-fashioned genealogy.

Once you engage in Y-DNA testing, you’ll have fascinating success stories of your own to share too.

Collect the Full Set

There’s so much to be learned about our ancestors.

I “collect” Y-DNA haplogroups from testers in each of my ancestral lines to reveal their history that has been obscured by time – and to assure my recent genealogy is accurate.

Every one of these haplogroups on my family tree, such as R-ZS3700, looks like just letters and numbers, but they aren’t. They are the keys that easily unlock that ancestor’s paternal family story, previously hidden behind history’s misty curtains. Now, they’ve been revealed! You can do exactly the same thing!

All you need to do is enter your Y-DNA haplogroup into Discover or just click through directly from your results page at FamilyTreeDNA.

Which ancestors are waiting for you?

Please enjoy this webinar. Don’t forget it’s only free for a week, so check it out now.

There’s More

Take a look at the other webinars I’ve recorded for Legacy Family Tree Webinars. (Hint – there are more coming very soon!!)

You can always access this and any of more than 2200 webinars in the library by subscribing to Legacy Family Tree Webinars, 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 e-mail whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

The Big Y-700 Test Marries Science to Genealogy

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

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

Those are great questions.

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

Time Tree Versus Genealogy Question

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

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

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

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

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

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

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

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

STRs Versus SNPs

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

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

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

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

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

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

Discover

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

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

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

Estes Project Group Time Trees

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

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

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

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

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

Group Time Tree Display

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

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

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

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

 

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

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

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

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

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

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

Click to enlarge

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

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

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

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

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

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

The Genetic Tree

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

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

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

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

Marriage

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

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

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

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

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

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

The marriage of genetic trees and genealogy is powerful indeed.

More Information

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

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

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

Comprehensive

This book is truly comprehensive and includes:

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

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

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

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

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

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

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

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

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

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

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

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Why Don’t Our Y-DNA Haplogroups Match?

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

How Haplogroups Work

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

Image courtesy FamilyTreeDNA

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

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

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

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

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

What is Your Goal?

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

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

We will cover all of these scenarios.

Where Did You Both Test?

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

These factors all make a difference.

Which Test Did You Take?

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

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

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

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

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

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

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

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

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

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

What Do You Mean by Match?

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

Not all haplogroups are created equal.

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

STR to STR or Autosomal to Autosomal Haplogroup Match

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

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

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

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

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

Using Discover to Compare Haplogroups

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

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

Click search to view information about that haplogroup.

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

Add the second haplogroup.

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

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

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

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

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

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

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

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

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

How cool is this??!!

Big Y-700 to Autosomal or STR Haplogroup Comparison

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

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

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

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

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

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

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

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

Let’s compare these results using Discover.

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

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

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

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

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

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

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

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

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

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

Big Y to Big Y Comparison

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

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

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

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

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

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

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

Haplogroup Assignments

Haplogroup assignments range from good to better to best.

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

Where Are You?

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

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

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

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

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

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

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

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

The Big Y-700 haplogroup is:

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

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

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

You Don’t Know What You Don’t Know

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

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

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

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

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

______________________________________________________________

Sign Up Now – It’s Free!

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

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

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

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

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

Bennett Greenspan

“And yes, I brake for cemeteries.”

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

12-Marker Matches

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

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

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

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

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

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

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

What Happened in Spain?

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

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

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

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

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

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

How does this actually apply to Bennett’s results?

Bennett’s Spanish Matches

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

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

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

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

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

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

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

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

DNA Plus History

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

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

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

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

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

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

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

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

Contacting Matches

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

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

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

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

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

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

Upgrade Request

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

Bennett’s email:

Hello <name>,

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

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

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

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

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

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

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

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

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

Best,

Bennett Greenspan

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

What’s Next?

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

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

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

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

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

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