Tag Archives: Science

Lineages Versus Ancestors – How to Find and Leverage Yours

Posted on by
4

Today, we’ll explore how a single direct test can uncover insights into an entire ancestral lineage, shifting our focus from individual ancestors to the broader concept of lineages.

When we work with either Y-DNA or mitochondrial DNA, we’re using a type of DNA that is specific to one ancestral line – or lineage. However, it’s not limited to just one ancestor. In fact, it applies to many.

Autosomal DNA, on the other hand, can be and is inherited from multiple ancestral lines. Of course, autosomal DNA is a bit like a jigsaw puzzle because YOU have to figure out WHICH line is the source of your match to someone.

You don’t have to do that with Y-DNA and mitochondrial DNA, plus, there’s a LOT more information available about both of those types of DNA.

Inheritance – How Parts of Your Ancestors Descend to You

I’ve put together a chart to explain the difference in the amount of autosomal DNA that you inherit from your ancestors versus the amount of either Y-DNA or mitochondrial DNA (mtDNA) that you inherit from specific lineages of ancestors.

Generation Autosomal Ancestors % DNA # Ancestors Y (males) & mtDNA Ancestors – %
7 GGGG-grandparents 1.5625 64 1 – 100%
6 GGG-grandparents 3.125 32 1 – 100%
5 GG-grandparents 6.25 16 1 – 100%
4 Great-grandparents 12.5 8 1 – 100%
3 Grandparents 25 4 1 – 100%
2 Parents 50 2 1 – 100%
1 You 100 1 – 100%

If you look at the amount of autosomal DNA inherited from each ancestor back seven generations, with you as the first generation, you’ll see that, on average, each of your GGGG-grandparents contributes 1.5625% of their DNA to you. In some cases, you might receive none at all, and in other cases, you might receive more – thanks to the uncertainty of recombination in each generation which I explained, here.

That’s not the case, though, for either Y-DNA (for males) or mitochondrial DNA for everyone. You always inherit 100% of the mitochondrial DNA carried by the entire lineage of your direct maternal line ancestors. Males always inherit 100% of the Y chromosome of their direct paternal line ancestors. Neither type of DNA is divided, recombined, or washed out over the generations. With the exception of an occasional mutation, the Y-DNA or mitochondrial DNA that your most distant ancestor in that line inherited is exactly what you receive.

Everyone can test their mitochondrial DNA, and males can take the Y-DNA test. Women give their mitochondrial DNA to both sexes of their children, but only females pass it on.

While you can only test for your own direct lines, you can test other people for their lineages which are also your ancestors.

Test Family Members

By testing family members who descend appropriately, you can obtain that same information for any ancestor.

For example, your father can test his mitochondrial DNA to receive the mitochondrial DNA information for his mother’s direct matrilineal line, or lineage. If you’re a female, having your father test both his Y-DNA and mitochondrial DNA provides you with valuable information about two ancestral lines that you can’t obtain from your own DNA.

Your mother’s brothers (or paternal uncles) can test their Y-DNA for your mother’s father’s line, and so forth.

Y-DNA is always the direct patrilineal line for males, and mitochondrial DNA is always the direct matrilineal line for everyone, so males can provide the DNA for both types of DNA for their ancestors. Men carry both types of DNA, the Y-DNA of their father and the mitochondrial DNA of their mother.

Lineages

The great news is that once you obtain that information by locating an appropriate tester, it’s conclusive in the sense that you typically don’t need to find someone else in that line to test – especially if they match someone else who descends from an ancestor in that same line. I say typically because, especially with Y-DNA, you may well want to test multiple men in different generations to track mutations that identify twigs and even leaves on their haplotree branch.

Essentially, both Y-DNA and mitochondrial DNA represent entire lineages, not just individual ancestors.

Once you obtain that information, you can:

  • Identify ancestors further back in time
  • Confirm lineages
  • Disprove lineages
  • Learn when your common ancestors with other testers lived
  • Learn where your ancestors and their ancestors lived
  • Discover which ancient and notable people you’re related to
  • Utilize match maps
  • And more

Click on any image to enlarge

There’s an entire world of information just waiting to be revealed – beyond matching for both Y-DNA and mitochondrial DNA and the half dozen great tools provided on your dashboard at FamilyTreeDNA.

The free Discover tool (currently for Y-DNA but very soon for mitochondrial too) provides a dozen extra reports. Between your dashboard reports and the Discover reports, there are about 20 chapters to your lineage story waiting for you.

There’s even a customized Discover experience for Big Y-DNA testers and full sequence mitochondrial DNA testers.

If you take the Big Y-700 test or the full sequence mitochondrial DNA test, your Discover experience includes:

  • Globetrekker
  • More Ancient Connections
  • More Notable Connections
  • The Match Time Tree
  • If you join projects, the Project Time Tree

For my Estes research, the Match Time Tree and Project Time Trees have been critically important.

Time Trees provide a genetic structure for how you and your matches are related over time. In the Match Time Tree above, you can see how my cousin is related to his matches, and when important branching of the tree that defines lineages occurred. The earliest known ancestors (EKA), provided by testers, are shown as well. This branching information correlated within 25 years of the births of the ancestors whose DNA split those branches.

For example, the mutation, R-ZS3700 was formed when Moses Estes was born in 1711 and was then passed to his descendants. If you test as a member of haplogroup R-ZS3700, we know you descend from Moses Estes. Some of his descendants have downstream haplogroups too, such as R-BY154184.

The Group Time Tree shows the same type of things but for members within Group Projects.

It’s truly exciting what lineage tests can reveal and how they can demolish brick walls.

Finding Testers

After you’ve exhausted your supply of close family members, then known aunts, uncles and cousins, how do you find testers to represent your lineages?

Most of us don’t know our third or fourth cousins, but they may carry that golden DNA that represents that entire lineage.

I’ve written about using both Relatives at RootsTech and WikiTree to find people who descend appropriately from the line you seek, but you’ll be most productive if you get organized first.

Let’s begin with organizing your lineages. Since this type of DNA is passed through that entire line of ancestors, you want to have those ancestors gathered together so it’s easy to find someone who has descended from any of those ancestors in that lineage appropriately.

For Y-DNA, that means each direct male line, and for mitochondrial DNA, that means every matrilineal line.

Lineage Spreadsheet

In my Ancestor Birthday Spreadsheet, where I track pertinent information about each of my ancestors individually, one row per ancestor, I created a lineage sheet for mitochondrial DNA and another one for Y-DNA. If you don’t want to create a spreadsheet, you can always make a chart or list.

It’s easier to recognize Y-DNA testing candidates because the surname (generally or often) doesn’t change.

Surnames generally do change in each generation in mitochondrial lineages.

Everyone can test their own mitochondrial DNA, so let me start with the tester (me) as an example. If I test my mitochondrial DNA, the results automatically apply to my ancestors in my direct matrilineal line – or lineage.

So, one test represents a dozen of my direct-line maternal ancestors. Your test represents however many ancestors you have on your direct matrilineal lineage.

Beginning with my mother, I’ve been able to track my matrilineal line beyond the six generations shown in my desktop genealogy software.

For purposes of clarity, while only six generations are displayed here, the entire lineage continues with Anna Elisabetha Mehlheimer on the next page. That line includes each female, mother-to-mother, as far back as I can go, consisting of all 12 generations.

I’ve entered all of those ancestors into their generational position in the first row on the Lineage Spreadsheet that begins with me.

Click any image to enlarge

The entire spreadsheet looks like these first few rows. I don’t expect you to read the small print. I just want you to get the idea so that you can follow the process.

The entire mitochondrial lineage of each “first of line” ancestor is shown in the “Upstream” generation columns at right. In other words, the person closest to current in the lineage is listed by last and first name (me), and all of their mitochondrial lineage ancestors are shown to their right.

My mother, Barbara Jean Ferverda is shown in the column “Upstream 1”, because she is one generation upstream from me, or the ancestor listed at far left. “Upstream 2” is her mother, Edith Barbara Lore, and so forth.

The haplogroup, once discovered, applies to ALL of those people – the entire lineage. Those ancestors don’t need to be shown on the spreadsheet again because you’ve checked them off the list when you find someone to represent all of them. Of course, in this case, that person is me.

My mitochondrial DNA represents 12 known generations, and countless unknown ones, some of which may yet be discovered. But there are other lineages that I need to discover that I can’t personally test for.

Identifying Lineages That You Need

I created this fan chart in my genealogy software and placed a red star for each pink mitochondrial DNA line that I need – beginning with the “first of line” ancestor. For example, Ollie Bolton is my “first of line” ancestor whose mitochondrial DNA represents all of her direct-line matrilineal ancestors.

Of course, each generation back in time provides more ancestors whose DNA we need – including each male who carries the mitochondrial DNA of his mother.

By the way, if I only have a partial haplogroup from either an autosomal test that provides base haplogroups, or a predicted haplogroup from an older HVR1 or HVR1/2 test, I leave them in the “need” category. In other words, I’m still seeking a full-sequence tester.

I started with each female in my tree and created their lineage backward in my spreadsheet.

More Distant Ancestors in Your Tree

My genealogy software shows a maximum of 6 generations on one page.

When I reached the point in my tree where I needed to go to the “next page,” other lineages began there. I began losing my place, so I color-coded the lineages in my spreadsheet so I could identify them at a glance. Additionally, the red-colored text indicates that the line begins with a female, and the black text means that the line “bookmark” begins with that man’s mother. Remember, every man had a mother whose mitochondrial DNA we need as part of that family’s story.

The “bookmark” ancestor is the person where I was when I advanced to the next “page” in my genealogy software, so I don’t lose my place.

You can see that Johanna Fredericka Ruhle is the bookmark ancestor for Maria Margaretha Krafft. Johanna Ruhle’s direct line is listed in the Upstream columns for her, and Maria Margaretha Krafft’s direct line is listed in the upstream columns for her. Please note that Maria Margaretha Krafft is NOT in the direct matrilineal line for Johanna Ruhle, but a different lineage that I need.

In my desktop genealogy software, Johanna Fredericka Ruhle is the last person in her line on page one. She’s the bookmark that leads to the next page, so I need to begin with her on page 2.

Now Johanna is the first person on the next page, with her pedigree chart showing. You can see that Johanna’s OWN mitochondrial lineage continues through Margaretha Kurtz (red arrow), but this page also includes 11 NEW mitochondrial lineages that begin with a female in each line.

Maria Margaretha Krafft’s lineage is labeled as #11 here.

If your bookmark or “page turn” individual is a male, then he goes in your bookmark field so you can figure out how to get that lineage in the first place. Bookmarks are kind of like breadcrumbs.

You don’t need to worry about “page 2” and more distant if you are just beginning.

However, this process will encourage you to check each end-of-line individual. As you search, you’ll know that when you find descendants of any one of these people, their mitochondrial DNA test will represent all of the ancestors in that entire lineage.

Find One, Get the Entire Dozen! BOG12

BOGO might be an American saying, and it means Buy One Get One, so essentially two for the price of one. In my case, it was buy one test, get information for 12 ancestors, or BOG12.

So, find one tester/haplogroup and get that information for the entire lineage! In my case, I got 12 for the price of one.

In Johanna Fredericka Ruhle’s case, she is the grandmother of Evaline Miller, my mother’s grandmother. Evaline Miller’s line includes 8 generations, so when I found someone who carried Evaline’s mitochondrial DNA, it applied to all 8 generations of her direct matrilineal ancestors – BOG8. The great news is that it doesn’t have to come from a descendant of Evaline herself, it can come from a direct female descendant of, say, Margaret Elisabeth Lentz, or her mother, Johanna Fredericka Ruhle – or more distant in the tree.

More distant ancestors may have more descendants that carry their Y-DNA or mitochondrial DNA.

You can see that in my desktop software (and only there,) I’ve added Evaline’s mitochondrial haplogroup as a middle name. I don’t ever do this in a public tree because it confuses the search algorithm. Besides that, haplogroup names evolve and change over time as the phylogenetic trees become more specific.

Follow That Line

For purposes of this exercise, let’s use one of my lineages to see if I can find someone who descends appropriately from either that ancestor, through all females to the current generation, or from any of her matrilineal ancestors upstream.

Let’s use Curtis Benjamin Lore’s mother as an example. His mother was Rachel Levina Hill, so that lineage begins with her since only females pass mitochondrial DNA to their offspring.

I’m going to search for someone who carries the mitochondrial DNA of Rachel.

Rachel is the fourth generation back from me, and according to my lineage spreadsheet, there are a total of 11 generations from me to the last person in her direct mitochondrial lineage.

  • Rachel Levina Hill – (born 1815 Addison Co., VT, died after 1870 Warren Co., PA, married Antoine “Anthony” Lore)
  • Abigail “Nabby” Hall – (born 1792 Mansfield City, Tolland Co., CT, died 1874 Waukegan, Lake Co., IL, married Joseph Hill)
  • Dorcas Richardson – (born 1769 Willington, Tolland Co., CT, died c 1840 Addison Co., VT, married Gershom Hall)
  • Dorcas Eldredge – (born 1739 Mansfield City, Tolland Co., CT, died 1772 Willington, Tolland Co., CT, married James Richardson)
  • Abigail Smith – (born 1718 Massachusetts, died 1793 Willington, Tolland Co., CT, married Jesse Eldredge)
  • Abigail Freeman – (born 1693 Eastham, Barnstable Co., MA, died 1737 Wellfleet, Barnstable Co., MA, married Samuel Smith)
  • Mary Howland – (born 1665 Dartmouth, RI, died 1743 Eastham, Barnstable Co., MA, married Nathaniel Freeman)
  • Abigail (surname unknown) – (born about 1635, married October 1656 to Zoeth Howland)

In order to obtain Rachel Levina Hill’s mitochondrial DNA, I need to find someone who descends from either her or her matrilineal lineage ancestors through all females to the current generation, which can be male. Women give their mitochondrial DNA to both sexes of their children, but only females pass it on.

In order to be “safe,” meaning less likelihood of a genealogical error, I prefer to find two descendants through different children who match each other. However, to begin, I’m always happy to locate any one descendant. They may match someone from this line who has already tested.

This is a good place to insert a cautionary note about the accuracy of other people’s genealogy. Always verify as best you can that the person you’re relying on for a critical test actually descends appropriately from the ancestor whose DNA you seek.

Autosomal Match List

When searching for testers, I always check my own autosomal match list first to be sure someone with that surname or who descends from that ancestor isn’t already lurking there. That includes both ThruLines at Ancestry and Theories of Family Relativity at MyHeritage.

It’s not always easy to tell because, at most vendors, you can’t search for (mitochondrial or other) matches by ancestor.

However, I enter the various surnames, beginning with the closest first, to see if maybe the right person is already there. The further back in time, the less likely you’ll have an autosomal match from any ancestor.

After you view one of your matches’ trees and determine that they are NOT an appropriate tester for what you seek, be sure to make a note on that match so you don’t check over and over again. You can make notes at every vendor on your matches.

FamilyTreeDNA Projects

If you’re searching for a particular surname, especially a Y-DNA lineage, checking the surname Group Projects at FamilyTreeDNA is always a wonderful first step to see if someone has already tested.

You can check group projects for surnames here.

Unfortunately, due to generational surname changes, surname projects often aren’t relevant to mitochondrial DNA lineages, although there are some lineage projects. If your ancestor is connected to a particular group of people, like the Acadians, for example, you can search or browse that group. The Acadian project and some others have both mitochondrial DNA and Y-DNA pages.

The Group Project search results will show any project where the administrators have entered that surname as potentially of interest to that specific project, so always check that resource.

WikiTree

Next, I go to WikiTree. If someone enters their mitochondrial DNA information, WikiTree propagates it through the tree to the appropriate descendants and ancestors. I love this feature.

Let’s see what we find for Rachel Levina Hill.

Look here!!!

Tim Prince has entered his mitochondrial DNA haplogroup, which was automatically associated with Rachel. It’s my lucky day. She is haplogroup H2a2a1e.

I can click through to Tim and view his tree.

Sure enough, Tim’s ancestor is Bathshua Smith, the sister to my Abigail Smith, four generations upstream from Rachel Levina Hill.

How cool is this?!!!

If no one is listed for Rachel’s mitochondrial DNA, I can click on the Descendants link on any ancestor, then click on DNA Descendants.

Next, click on which type of DNA you’re looking for.

At this point, I’d suggest contacting the profile owner or checking your autosomal matches for people with these surnames—in this case, Wickwire or Chain. You can also view the entire descendants list, which I’ve truncated here for brevity.

Relatives at RootsTech

While you can check WikiTree anytime, you can only access Relatives at RootsTech for a short time, typically about a month before and after RootsTech  – which means right now. Signing up for free virtual attendance works just fine as your key to accessing Relatives at RootsTech.

I wrote about Relatives at RootsTech here. Once you’re set up, you can access your list of cousins attending RootsTech by:

  • Location
  • Ancestor
  • Family Line

By selecting “Ancestor,” I can see who is attending that descends from Rachel Hill, according to the FamilySearch tree. Scanning further down the list, I see her mother, Abigail “Nabby” Hall. Two people descend from Rachel, while 3 descend from Abigail.

By clicking on “Relationship,” you can see how you and that person are related. In this case, what I’m really interested in is how they descend from Rachel Lavina Hill.

Rachel contributed her mitochondrial DNA to her son, William, but he didn’t pass it on, so that mitochondrial DNA line stops right there. If it hadn’t stopped there, it would have stopped a few generations later with another male – Gladys’s son.

Any male in the line is a blocker for mitochondrial DNA, unless it’s a current generation tester who descends from all females.

Sometimes, when the line is interrupted by a male in the last couple of generations, it’s worth reaching out to that cousin to see if they know of anyone who descends appropriately. Ask if the last female in the line has daughters or sons who are still living and might be willing to test – or if their daughters had children and so forth.

Each Relatives at RootsTech selection shows a maximum of 300 people, but you can choose the applicable grandparent’s family line to see 300 people in that line. You’ll need to click through each person to see how they descend, but that’s fine because you have 300 opportunities for success!!

Check back, too, because more people register up to and even during RootsTech.

Create Those Lineage Spreadsheets

Now, we’re back to why creating those lineage spreadsheets is essential. I don’t know about you, but I can’t remember exactly how family members descend from each other beyond 3 or 4 generations.

I actually need a tester from my paternal grandmother’s line, so I’m focusing on that line for this next example.

When I look at the list of who is related to me through my paternal grandmother’s line, I want that spreadsheet readily available, so I know precisely which lineages I need to find cousins to test for both Y-DNA and mitochondrial DNA.

I have a partial haplogroup for Ollie Bolton based on a very old HVR1 test. There is no DNA left to upgrade, and the tester is deceased, so I need to find someone else.

I’ve made a list of all of the women in that lineage. Unfortunately, it’s pretty short.

  1. Ollie Florence Bolton – (1874 born Hancock Co., TN, died 1955 in Chicago, married William George Estes)
  2. Margaret N. Claxton or Clarkson – (1851-1920 Hancock Co., TN, married Joseph Bolton)
  3. Elizabeth “Bettie Ann” Speaks – (1832 Lee County Va, died 1907 Hancock Co., TN, married Samuel Claxton/Clarkson)
  4. Ann McKee – (1804/5 Washington Co., VA, died 1840/1850 Lee Co., VA, married Charles Speak)
  5. Elizabeth (surname unknown) – (born about 1768, died 1839 Washington Co., VA, married Andrew McKee)

I’m brick-walled, so if I can obtain Ollie’s mitochondrial DNA, through matching, I may be able to identify Elizabeth, Ollie’s great-great-grandmother. This line is one of my most frustrating, and mitochondrial DNA testing and matching hold a lot of promise for giving Elizabeth a surname and parents.

I’ve already checked my matches and WikiTree, so I’m going to see if any of the “Family Line” Relatives at RootsTech descend through all females.

I have 300 opportunities to find a tester.

As more people sign up, the most distant cousins will roll off the list, so start at the bottom.

Cross your fingers for me!

DNA Testing Scholarships

If I find someone, the first thing I’ll ask is if they have taken any kind of DNA test. If so, where? Then, I’ll ask if they have taken a mitochondrial DNA test at FamilyTreeDNA and explain why that’s important and what it can potentially do for us.

If yes, I’m golden because the next question will be about their haplogroup, and I’ll invite them to join a project that I manage so I can view the results.

If the answer is no, but they’ve tested their autosomal DNA elsewhere, I’ll invite them to upload for free and join the project. You can also establish a private family project for this purpose, if you wish.

I tell them I have a DNA testing scholarship for someone who carries that DNA lineage. I explain that with the scholarship, the test is entirely free, including postage, and that they’re in complete control of their kit and results. All I ask is some level of access.

I always explain the results when they arrive. I’ve never had anyone object to this arrangement, and often we research collaboratively. I’ve met wonderful cousins this way.

Get Started!

Whose Y-DNA or mitochondrial DNA do you need to find?

Make your lineage spreadsheet or chart, and take this opportunity to find a testing candidate and learn more about your ancestors! Not just one at a time, but entire lineages.

They are waiting for you!

_____________________________________________________________

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

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

Posted on by
5

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

Comprehensive

This book is truly comprehensive and includes:

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

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

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

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Complete Guide to FamilyTreeDNA Released in Hardcopy

Posted on by
23

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

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

Enjoy!

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

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

Posted on by
36

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?

Posted on by
12

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

Rootstech 2024: Friends, Discover Tools, Highways of History and the Storm

Posted on by
5

I didn’t want to open the curtains Saturday morning, given the blizzard warnings that were worsening all day Friday.

I finally screwed up my courage and peeked out.

Indeed, those skies look dark, grey, and foreboding.

Decision Time

I had a decision to make.

I originally planned to stay in Salt Lake City until Sunday, but I had already changed my flight to late Saturday afternoon following my session. I also changed my hotel reservation accordingly.

However, if I packed and checked out, got to the airport, and my flight was canceled, I was likely going to be stranded, potentially at the airport for at least two days. There aren’t any hotels in the Salt Lake City airport, but there are a few nearby. However, probably not enough rooms to accommodate an airport full of stranded people.

Would Uber even be available?

Could I get back into Salt Lake City to check back into the Marriott or any other hotel? Would they have space?

I was at the go-no-go decision point.

It was probably a 50-50 roll of the dice.

I packed and checked out.

It wasn’t snowing yet, but no one doubted that it would. The only questions were when the snow would begin, whether it would begin as rain and freeze into ice before the snow started falling, and how much snow would there be.

Maybe more important to the people at RootsTech – what about flights?

All day, you could see people obsessively checking their flight information on their phones.

I had two speaking engagements scheduled for the day: a morning Y-DNA “Ask Me Anything” panel and my afternoon session, “Highways of History – Flesh out Your Ancestors Using Discover Case Studies.”

The afternoon session was scheduled to end just half an hour before RootsTech closed for the year, so there really was no getting out early.

In for a penny, in for a pound.

Friends in the Expo Hall

I was still trying to visit every booth on the show floor.

I’ll just admit right now that I failed miserably. Not only was I bone tired by this time, but I kept running into people I knew. I realized that this was my last opportunity to see them this year, so I never made it past the halfway point in the Expo Hall.

I did notice that the crowds were very thin. Saturday was Family Day, but apparently, not many people wanted to risk venturing out. Even the locals were concerned which is never a good sign.

The Heritage Theater had a full schedule of events, but there were very few people in the audience through no fault of the speakers or RootsTech.

For those hearty souls who did attend, they received up-close and personal sessions and information from the presenters.

It was nice to see the folks from Family Tree Magazine again. I’ve written for them off and on for years, but had never met the staff in person before.

Be sure to check out their Best Genetic Genealogy Websites and also their Genealogy Books Guide, listed by subject.

When you get there, check out their other “best of” categories and other topics.

Walking on down the aisle, I stopped to talk to the “One Kind Act a Day” people,

Being the skeptic that I am, I kept trying to find the hook, but I couldn’t. It’s a nonprofit that seems to do exactly what it says.

This is absolutely something I can sign up for, so I did and took the pledge.

Doing one kind act a day is easy, so let’s do two!

You can follow them on Facebook, too.

Reclaim the Records is another nonprofit that has successfully advocated and reclaimed more than 60 million records to date that were behind lock and key.

Take a look at their successes and their to-do list.

They style themselves as intellectual freedom fighters. Did you know so many records were still entirely unavailable?

Hey, isn’t that Myko Cleland sitting at the Reclaim booth, on the left? He’s the Director of Content in Europe for MyHeritage, nicknamed the DapperHistorian, and you just never know where you’re going to find him!

How cool is this? Wear What You Love uses sublimation dying to permanently print/infuse your photos on t-shirts or other materials.

This also works on fabric that can be used in quilts but more reliably on polyester fabrics, not cotton.

Hmmm, I have some ideas.

Y-DNA Ask Me Anything at FamilyTreeDNA

The Y-DNA “Ask Me Anything” session began at 10:30. I don’t think attendees realized that FamilyTreeDNA brought the R&D brain trust and you could literally ask them anything. What an opportunity!

Left to right, Michael Sager, FamilyTreeDNA’s well-known Y-DNA phylogeneticist, Dr. Paul Maier, seated, population geneticist, and Goran Runfeldt, standing at right, Head of R&D.

The team reviewed how to use Discover and what can be revealed.

Janine Cloud, Manager of Group Projects, is beside me in the black shirt, seated at far right. Group Projects are important tools for Y-DNA testing and testers.

In addition to the Discover Time Tree, shown on the screen above, a Group Time Tree shows Big Y project members as grouped by the volunteer administrators, along with their earliest known ancestors (EKA.)

Here’s an example from the Estes surname project that I administer. My grouping of participants is shown at left, the Time Tree in the center, and the locations with earliest known ancestors at right. Results are displayed in the order that they are phylogenetically related, helping genealogists immensely.

Here, the team is explaining the Block Tree which displays matches in a different format.

Men displayed together on the same Block Tree branch are more closely related to each other than to men displayed in other branches.

Michael Sager observes while Paul Maier demonstrates Globetrekker, an innovative interactive map that shows the path that one’s male ancestors took on their journey from Africa to where they are most recently found.

One of the attendees had a question and looks on as the team explains their results using Globetrekker.

We tried to get a team photo after the presentation and managed to corral some of the team. You’ve met several already, but Bennett Greenspan, Founder and President Emeritus of FamilyTreeDNA, is to my right as you look at the photo, with Sherman McRae standing between Bennett and Paul.

I particularly like this “generations” photo.

In the rear, Katherine Borges stands with Bennett Greenspan. Bennett obviously founded the company, and Katherine was one of the early administrators. Dr. Lior Rauchberger, CEO of myDNA, which includes FamilyTreeDNA, is seated at left, along with Alex Zawisza, CFO, at right. MyDNA purchased Gene by Gene, which includes FamilyTreeDNA, just over three years ago, and the team has continued to work together for the benefit of FamilyTreeDNA customers.

Lior traveled from Australia to attend RootsTech. He could be seen checking people out at the booth, so he had the opportunity to talk with customers. He said he heard the words “brick wall” more in those three days than ever before, as in, “Thanks to FamilyTreeDNA, I broke down my brick wall.”

We all owe Lior a huge debt of gratitude for his continued commitment to FamilyTreeDNA research, and in particular, the Big Y-700 tools, such as Discover, along with the Million Mito Project which will be released with a similar tool, MitoDiscover.

Thanks Lior!

I turned around to see Stephanie Gilbert, who gave the keynote at the FamilyTreeDNA conference.

Stephanie is an incredibly engaging speaker, and I’m going to recommend her to RootsTech for next year.

It was wonderful to see Schelly Talalay Dardashti, at left. She has worked for MyHeritage since 2006 and administers the Tracing the Tribe – Jewish Genealogy Facebook group, which has more than 73,000 members. Schelly is a wonderful ambassador, always helpful and incredibly knowledgeable.

Between us is Dana Stewart Leeds, creator of the Leeds Method, a technique that launched the autocluster craze by manually grouping matches. I wrote about the Leeds Method, here, in 2018. When you see AutoClusters at Genetic Affairs or the Collins-Leeds method at DNAGedcom, think of and thank Dana. They automated her process, with her permission, of course, creating some of the most useful tools available to genealogists. You can follow Dana here.

I swear, it was brainiac day at RootsTech!

Mags Gaulden, one of the founders of mitoYDNA and who writes at Grandma’s Genes, was working in the FamilyTreeDNA booth and was quite busy – so busy that I almost didn’t manage a picture with her. We never did get to have a meal together. We will have to do better in October when we are both scheduled to be at the East Coast Genetic Genealogy Conference in person. Oops, did I say that out loud???

Save the dates!

GEDmatch – New AutoCluster Endogamy Tool

I’ve emailed back and forth with Tom Osypian with GEDmatch many times now, but I’ve never met him in person, even though we’ve been in the same place before.

This time, I was determined. Although Tom was busy several times when I stopped by the booth, there were fewer people on Saturday, so I stood a fighting chance.

Tom explained that GEDmatch has a new AutoCluster tool developed by Evert-Jan Blom at Genetic Affairs and Jarret Ross from GeneaVlogger that helps with unraveling endogamy. I told him that I already knew because we used my Mom’s autosomal results during testing. Mom is partly endogamous through her grandfather’s Acadian line.

The Acadian cluster in the upper left quadrant looks like an orange blob with no differentiation, where everyone is related to everyone else – because that’s truly how Acadian descendants are connected. As my Acadian cousin once said, “If you’re related to one Acadian, you’re related to all Acadians,” and it’s true.

Evert-Jan needed to optimize clusters for a partially endogamous person without negatively affecting their non-endogamous clusters.

He did a great job separating my Mom’s big orange blob endogamous cluster into these nice, neat mini-clusters.

To take a look, choose AutoCluster Endogamy on GEDmatch and make your preset selection.

There’s a YouTube video about this tool by GeneaVlogger, here.

Next I ran into Patricia Coleman, a fellow genealogist scientist, who wrote an excellent article about finding segment links to the opposite parent using AutoSegment AutoClusters, here. Check out her blog and published papers, here.

We are incredibly fortunate to have such dedicated researchers and scientists in our community.

Unfortunately, I was running out of time on the show floor.

Sisters of Heart

OK, now, I’m going to say something really sappy. Consider yourself warned.

By this time, I needed to find food and quickly eat before my session, which was scheduled to start at 1:15. This meant I needed to be in the room by 12:45.

Janine was doing consultations in the FamilyTreeDNA booth and couldn’t get away for food either.

Thankfully, with the storm approaching, there weren’t long lines at the food vendors. I peeked outside as I walked down the hallway looking for a food booth that wasn’t very busy.

It was ominously dark and gloomy outside, and had begun to snow.

I found the food stand that looked least bad and got in line. Neither Janine nor I knew what was available at the food vendors, but we’ve known each other for enough years and attended enough conferences that we kind of know what the other likes.

I was standing in line taking pictures of the menu and the pre-made foods in the cooler and messaging them to Janine. People must have wondered if I couldn’t find something better to take pictures of. I just chuckled. I’ll spare you the food pictures because they were unremarkable,

They were out of everything Janine thought looked good. Apparently, everyone else thought those items looked good, too. When it was my turn to order, and I had to choose, I messaged Janine that we were sharing a turkey wrap and asked if she wanted fruit.

“YES! Fruit sounds wonderful.”

Great!

I got both items and paid.

“So do chips. Chips sound great, too.”

Perfect.

I paid again.

Then I saw the muffins. Chocolate sour cream swirl muffins with large shiny sugar crystals baked on top.

No need to message Janine about this one.

Yep, I paid for the third time.

Then, I apologized to the people behind me, hoped they didn’t recognize me, and hurried back to the FamilyTreeDNA booth.

Janine’s customer had just finished up, so I sat down in that seat and spread out our goodies on the table between us. The turkey wrap was cut in half, and we shared half of everything.

I love breaking bread and sharing food with my favorite people. There’s something about feeding the body that nourishes the soul and bonds the heart. I can’t explain it, and I really wasn’t thinking about it just then. Both of us just needed a minute to relax and eat before rushing off to do something else.

I asked Janine if she wanted the last part of my half of the turkey wrap. She told me to take the turkey out and eat it because I needed the protein.

Bless her heart. She was right.

I grabbed two forks in the food booth, and we both ate out of the fruit box positioned halfway between us.

Then, after discussing and laughing that the muffin looked like a geode, I cut it into four sections. We ate them on the cupcake paper with forks, like cake. It tasted wonderful. If you’re thinking that I couldn’t finish my turkey wrap, but had plenty of room for chocolate cake, you’d be exactly right!

Someplace in the midst of our impromptu picnic meal, I realized that four years ago at RootsTech 2020, was the last time we would see each other – for years. A week after RootsTech, everything shut down. People died. Both of us had family members who perished in the Covid epidemic.

Everyone was traumatized.

Neither of us knew if we’d ever see each other again, but neither of us verbalized that because – well – we just couldn’t. Some days during that time, it was all any of us could do to simply hold it together.

I realized just how important these very relaxed impromptu moments, built on years of shared space and breaking bread together, really are. It’s exactly why we don’t have any old photos of “normal” things, just special occasions. Normal isn’t special, until it is – when someone is suddenly gone. Then, “normal” is everything.

None of us know which meal together will be the last. We never know when our number will be called, or how. We really only ever have today.

I wish someone had taken a picture of us smiling and eating, sharing our meal with each other, something we’ve done countless times before. Something so normal that we don’t even think about it. I never thought about taking a picture of something so routine, and neither did anyone else. Why would they?

Regardless, that moment is burned into my memory, along with just how precious our time together is.

Then, the moment of quiet respite, eating chocolate muffins and sharing more than food, was over, and the fragile thought bubble was broken by the ticking of the clock. I had to jump up and run off to my next presentation, and a customer approached and asked Janine a question.

Thank Goodness we were both able to return to RootsTech and relish something so absolutely normal once again.

Highways of History – Flesh Out Your Ancestors Using Discover Case Studies

My class on Friday, “DNA Academy,” was full, and sadly, people were being turned away at the door. Saturday’s “Highways of History” class was held in a larger room, but many people stayed home, so the room was only about three-quarters full. I forgot to ask someone to take a picture, so I’ll just share a few slides.

I really enjoy using AI occasionally for images. This was ChatGPTs idea of Highways of History.

Using Big Y DNA results, I provided examples of using the Discover tools to reveal the stories of my ancestors. Not every Discover tool reveals something amazing about each ancestor, but together, they tell a story we can’t unravel any other way.

I seek out men who descend from every male ancestor paternally through all males and offer a scholarship for Big Y-700 testing.

Here are just a few examples of what I’ve found and documented:

  • A descendant of Etienne Hebert (c1626-c1670), my Acadian ancestor, matches an ancient DNA burial found in Metz, France. Etienne and his brother’s children cluster in a group with a common ancestor about 1650, and the ancient burial dates to about the year 500 CE during the time that Metz was a Gallo Celtic Village. Among other things, we learn that their common ancestors were Celtic.

  • An adopted male matches several Estes men. Based on his Big Y-700 mutations, I can place him in the Estes family tree within two generations. His position in the tree is confirmed by autosomal matches to the ancestors of the wife of Joseph Frank Estes. Autosomal matches confirmed the Big Y-700.

  • Germain Doucet, born in France in the late 1500s, had two sons. One was born in France about 1621, and the second in Acadia (now Nova Scotia) was born to either a second or third wife in 1641 and named after Germain. Based on Big Y-700 tests, the son born in 1621 has a European haplogroup, but Germain, born in 1641, has a Native American father, suggesting the possibility that he may have been adopted by the older Germain Doucet. This was quite an unexpected surprise.

  • A Bowling descendant of Hugh Bowling (1591-1651) born in Chorley, Lancashire, England, had almost no English matches. STR matches are from Saudi Arabia, Algeria, Cyprus, Germany, and Portugal, but the highest percentage are from Spain. Furthermore, his ancient Connections are from Hungary, Israel (4), Armenia, Rome, Italy, Turkey, Lebanon, Lincolnshire, and Norwich, England. Local history reveals a Roman Fort just 19 miles away from where Hugh Bowling lived, and the location, now excavated, was a settlement location for Roman Sarmatian soldiers.

  • Thomas Speak was born about 1634 in Downham, Lancashire, near Chorley, England where the family attended church. Big Y-700 testing shows that he and other English Speak men still living in the area share an ancestor about 1300 CE. When we visited in 2012, we discovered that Myles Standish’s family also attended the same church. Saxon Crosses are found in the graveyard outside, dating to circa 800-900 CE. A Standish male’s Big Y-700 test matches the Speak men, with their common ancestor dating to 850 CE, the same time that the Saxons were settling the region.

  • Bennett Greenspan’s Jewish ancestors were found in Ukraine in the mid-1700s, but he wanted to know more about where they came from originally. Were they Ashkenazi or Sephardic, or something else? By upgrading both close and distant matches to the Big Y-700, Bennett discovered that their common ancestors were in Spain in the year 296 when the two lines diverged and his line left. You can read Bennett’s story in more detail, here.

None of these mysteries or brick walls could have been solved without Big Y-700 tests and without the Discover tools.

This session was so much fun, and I can hardly wait to find more male ancestors and test their direct male-line descendants.

Goodbyes

By the time questions were answered, and I packed up my equipment, there were only about 15 minutes left until the Expo Hall closed at 3. Furthermore, I needed to retrieve my coat from the FamilyTreeDNA booth, retrieve my suitcase from the Marriott bellman, and order an Uber. My flight was only about two and a half hours away, assuming it left.

So far, it hadn’t been cancelled or delayed.

I mentioned my flight concerns to a colleague that I ran into on the way to the booth. He happens to live in Salt Lake City and gave me his phone number, with instructions to call if I got stranded.

My first (unspoken) thought was, “Thank you, but I’d never impose like that.” But then, I realized that was crazy and I really should call him if I needed help. What was wrong with me? I didn’t know him well, but I had known him and the company where he works for many years and felt completely safe. We are Facebook friends too, so I’ve joyfully watched him marry and start a family. I would have done exactly the same for him, and yes, I absolutely WOULD have wanted him to call. Plus, if I actually did wind up staying on his couch for a day or so, I would get time to “Grandma” his children, so HUGE BONUS!

You know who you are, and THANK YOU. I felt so much better after that. Genealogists are just the most amazing people!

Then, I ran into Lisa Rhea Baker who very generously gifted me with bracelets made by her veteran daughter as she healed from surgery. The bracelets around my wrist are beaded, and the one joining our hands is knotted in German colors. I’m wearing that one today. What a very talented and generous young lady.

I was very touched and so grateful. I asked her to thank her daughter on my behalf.

I saw Katherine Borges again in the booth as I was retrieving my coat and we quickly took a selfie. Neither of us realized we hadn’t gotten one earlier, although we did manage to have dinner with a small group where we all chattered like magpies.

Last, Goran, Paul and I took a quick selfie as I was preparing to run out the door. It was 3, closing time, and almost no one was left in the Expo Hall. I knew if I missed this flight, I’d not get another one. Everything was full.

I surely miss seeing these guys. Hopefully, I’ll see them again before the next RootsTech!

The Blizzard Strikes

I stepped outside.

The blizzard had begun in earnest. I could see a couple blocks down the street, but huge flakes of snow were pouring down. The wind was blowing viciously, whipping everything, making it difficult to hang onto my laptop rolling bag. The snow was sticking to everything.

At least it wasn’t slick yet, at least not where I was walking. If the wind hadn’t been so strong, it would have been pretty.

Would the plane be able to take off in this wind? The snow was blowing directly sideways now.

The only distance I had to walk was across the street. This is how much snow accumulated on my coat in just a minute or so.

A little later, Goran took this picture.

Ubers were becoming somewhat scarce, so two of us shared and made it to the airport in time for long TSA lines.

The plane was about 45 minutes late, which didn’t surprise me. I heaved a huge sigh of relief when it pulled up to the gate. At least it arrived, and as soon as it was cleaned a bit, we began to board.

Eventually, we pulled out of the gate and began waiting on the tarmac for the plane to be de-iced.

An hour later, we weren’t even halfway to the front of the line. The pilot estimated it would be another 90 minutes or so.

The snow continued to accumulate.

Would the pilot and crew time out and be unable to fly?

If we had to go back, there would be no prayer of getting another crew. Flights were already being canceled.

The woman beside me was ill. I felt awful for her, and it occurred to me that this might also be a reason to return to the gate.

At least the pilot allowed us to unbuckle our seatbelts and go to the restroom as we waited.

My flight had been scheduled to arrive just after midnight. But now, we were more than four hours late. What time would we get in? My poor husband. I told him to go to sleep and I’d just stay in the hotel in the airport. He said no, nothing doing.

I begged him to at least take a nap and recheck the flights at 3 or 4 AM.

The flight was extremely rough. We couldn’t get above or around the storm, and the seatbelt sign was only off for about 10 minutes during the entire flight.

I tried to sleep, but that wasn’t happening, even though I was beyond exhausted.

This is what love looks like. One single car in the cell lot at around 5 AM, as Jim waited patiently for me.

On the way home, in fact, all of the way home, we drove through the most incredible lightning storm I’ve ever seen.

It was someplace between worrisome/terrifying, and fascinating.

This lightning wasn’t reaching toward the earth in bolts. Instead, the entire sky lit up like daylight, horizon to horizon, flashing like an extremely bright strobe. It was so bright that, at times, it was nearly blinding, and the clouds looked like rainbows as the lightning flashed behind and through them. I had never seen anything like this.

This type of “sheet lightning” is crazy rare. Thankfully, it kept us awake and was stunningly beautiful in a very strange, ethereal way. We worried that we would be caught in a hellacious storm and unable to see in the downpour.

Florida is notorious for vicious storms and torrential downpours. It’s also the lightning strike capital of the US and ranks fourth in the world. This area, in particular, is known as Lightning Alley. Our house was struck last year.

As we exited the expressway, just a couple miles from home, the sky unzipped, and torrential rains began. Thankfully, we were spared for most of the drive.

I was incredibly glad to finally be home and hoped that others had been able to either escape the Utah storm or find a room in a hotel that did not lose power on Sunday. Reports said wind gusts in the Utah mountains were measured at 165 miles an hour, but Salt Lake City, tucked into a valley, was spared most of that.

What an incredible week in so very many ways.

I hope you enjoyed coming along with me. Dates have already been announced for RootsTech 2025.

_____________________________________________________________

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

Pedigree Collapse and DNA – Plus an Easy-Peasy Shortcut

Posted on by
24

Pedigree collapse can be responsible for you sharing more DNA than expected with another person.

What is pedigree collapse?

Pedigree collapse occurs when you descend from the same ancestor(s) through more than one path. In other words, you descend from those ancestors through two different children. Therefore, when matching with someone else who descends through those ancestors, you may share more DNA than would be expected from that level of relationship on the surface, meaning without pedigree collapse.

Endogamy is different and means that you descend from a community of ancestors who descend from the same group of ancestors. Often out-marriage is discouraged or otherwise impossible, so all of the group of people share common ancestors, which means they often match on segments without sharing close ancestors. Examples of descent from endogamous populations are Jewish, Amish, Brethren, Acadian, Native Hawaiian, Māori, and Native American people, among others.

I wrote about the difference between pedigree collapse and endogamy in the article, What’s the Difference Between Pedigree Collapse and Endogamy?

I’ve also written about endogamy in the following articles:

Degrees of Consanguinity

If you’re a genealogist, and especially if you’ve worked with Catholic church records, you’ve probably heard of “degrees of sanguinity,” which are prohibited blood relationships in marriage. For example, siblings are prohibited from marrying because they are too closely related, according to church doctrine.

By SVG remake by WClarke based on original by User:Sg647112c – Own work, CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=54804980

Today, we think of the genetic results of inbreeding, but originally, relationships (and consanguinity) also had to do with inheritance.

Essentially, marriages are prohibited by degree of sanguinity, and that degree is calculated based on this relationship chart. Prohibited degrees of consanguinity changed over time. Sometimes, a priest granted dispensation for a couple to wed who was of a prohibited degree of sanguinity. That’s a genealogy goldmine because it tells you where to look for common ancestors. It also tells you something else – that you may share more DNA with other descendants of that couple than one would otherwise expect.

More Than You Ever Expected

Recently, I’ve been working with an academic research team on a very interesting ancient DNA case that involves pedigree collapse. Doing the genealogy and genetic work on how much DNA was expected in a match without pedigree collapse, and how much was expected with pedigree collapse, was very interesting.

The team was working to confirm relationships between people in a cemetery. The burials shared more DNA than anticipated for who the people were believed to be. Enter pedigree collapse.

I can’t disclose the circumstances just yet – but I will as soon as possible. It’s an extremely interesting story.

We needed to ensure that readers, both academic and more generally understood pedigree collapse and our calculations. Why did burials share higher than expected DNA than indicated by the expected relationships? This puzzle becomes much more interesting when you add in pedigree collapse.

Academic researchers and scientists have access to models and mathematical algorithms that normal air-breathing humans don’t have easy access to.
So, what do you do if you and a match have a known pedigree collapse in your tree? How much DNA can you expect to share, and how do you calculate that?

These are all great questions, so let’s take a look.

I’m sharing the PowerPoint slides I prepared for our team on this topic. I’ve removed anything that would identify or even hint at the project and modified the slides slightly for easier consumption.

This presentation has never been given publicly, so you’re first! It seemed a waste to do this work and not share it!

Pedigree Collapse and DNA

Pedigree collapse occurs when you share an ancestor or ancestors through different pathways. In this case, the person at the bottom is the child of parents who were third cousins, but the father’s grandparents were also first cousins.

First cousin marriages were common in the not-too-distant past. Today, you could easily marry your third or fourth cousin and not even realize it unless someone in your family just happened to be a genealogist.

Genealogists use various tools to calculate the expected amount of shared DNA in relationships – first cousins, siblings, or half-siblings, for example. Both the Shared cM Project at DNAPainter and SegcM at DNA-Sci Tools provide tools.

Take a look at the article, DNA: In Search of…Full and Half-Siblings, for some great examples.

First cousins share common grandparents. Their child inherits DNA from two paths that lead back to the same ancestors. Some of that DNA will be the same, meaning the child will or can inherit the same ancestral segment from both parents, and some will be different segments from those ancestors that the parents do not share with each other.

Inheritance – How It Works

Let’s look at inheritance to see how this happens.

Let’s start with full and half-siblings.

Each child inherits half of their DNA from each parent, but not entirely the same half (unless they are identical twins.)

Therefore, full siblings will match on about 50% of their DNA, which is illustrated by the segments on the chromosome browser. However, and this will be important in a minute, about 25% of their DNA is exactly the same, when compared to each other, on the chromosome inherited from their father and mother at the same location.

On the chromosome browser, you can see that three siblings do match. One sibling (the grey background chromosomes) is the person both other full siblings are being compared to, in the example above.

What you can’t determine is whether they share the exact same DNA on both their mother and father’s Chromosome 1, where the matches overlap, for example. We know they both match their sibling, but the top person could match the sibling due to a match from their paternal chromosome in that location, and the bottom person could match due to their maternal chromosome. There’s no way to know, at least not from that view.

The areas where the siblings share exactly the same DNA on both their maternal and paternal chromosome, both, with each other are called Fully Identical REgions (FIR), as compared to Half Identical Regions (HIR) where the siblings match on either their maternal or paternal copy of the chromosome, but not both.

23andMe used to provide a tool that displayed both types of matches.

Since the data exposure incident at 23andMe, they no longer provide this lovely tool, and since that help page is now gone as well, I doubt this view will ever be returned. Fortunately, I grabbed a screenshot previously.

The dark purple segments are fully identical, meaning that these two full siblings match on both their maternal and paternal chromosomes in that location. The magenta are half identical, which means they match on EITHER the maternal or paternal chromosome in that location but not on both chromosomes. Of course, no color (light grey) means there is no match at that location.

Please note that because 23andMe counts fully identical regions (FIR) twice, their total matching cMs are elevated. The other companies do NOT count those regions twice.
GEDmatch also shows both full and half-identical regions as described more fully, here.

In this full-sibling example from GEDmatch, the green segments are fully identical regions across both the maternal and paternal chromosomes.

The definition of FIR is that two people match on both their mother’s and father’s DNA on the same chromosome. Therefore, in following generations, there technically should not be FIR matches, but in some instances we do find FIR matches outside of full siblings.

Moving down another generation, first cousins may share SOME fully identical DNA, especially if they are from an endogamous population or their mothers are related, but less, and it’s generally scattered.

Here’s my Mom’s GEDmatch comparison to her first cousin. The purple-legend segment shows a match, and the green within that match shows fully identical locations.

You can easily see that these are very scattered, probably representing “chance” or population-based fully identical matching locations within a segment. Comparatively, the green FIR segments for full siblings are dense and compact, indicating a segment that is fully identical.

Evaluating matches for dense FIR segments (known as runs of homozygosity – ROH) is a good indicator of parental relatedness.

Double Cousins

Of course, if these people were double first cousins, where the wives of the siblings were sisters to each other – the first cousins would have large patches of dense green FIR segments.

First cousins share grandparents.

Double first cousins occur when two people share both sets of grandparents, meaning that brothers marry sisters. Normal first cousins share about 12.5% of their DNA, but double first cousins share about 25% of their DNA.

In this case, Sharon and Donna descend from two brothers, James and Henry, who were sons of Joseph and Jane. In this scenario, James and Henry married unrelated women, so Sharon and Donna are first cousins to each other.

Double first cousins share both sets of grandparents so they would inherit FIR from both sets of siblings.

You need to be aware of this, but for now, let’s stick with non-double relationships. You’re welcome!

DNA Inheritance

Here’s a different example of DNA inheritance between two siblings.

  1. You can see that in the first 50 cM segment, both siblings inherited the same DNA from both parents, so they match on both their mother’s and father’s chromosomes. They match on both the 50 cM green and 50 cM pink segments. 23andMe would count that as 100 cMs, but other vendors only count a segment IF it matches, NOT if it matches twice. So, other vendors count this as a 50 cM match.
  2. In column two, these two people don’t match at all because they inherited different DNA from each parent. In this example, Person 1 inherited their maternal grandmother’s segment, and Person 2 inherited their maternal grandfather’s segment.
  3. In column three, our siblings match on their paternal grandmother’s segment.
  4. In column four, no match again.

How much can we expect to inherit at different levels – on average?

Different tools differ slightly, and all tools provide ranges. In our example, I’ve labeled the generations and how much shared DNA we would expect – WITHOUT pedigree collapse.

Ancestral couple Inherited cM Inherited %
Gen 1 – Their children 3500 cM 50
Gen 2 – Grandchildren 1750 cM 25
Gen 3 – Great-Grandchildren 875 cM 12.5
Gen 4 – GG-Grandchildren 437.5 6.25
Gen 5 – GGG-Grandchildren 218.75 3.125
Gen 6 – GGGG-Grandchildren 109.375 1.5625
Gen 7 – GGGG-Grandchildren 54.6875 .078125

Please note that this is inherited DNA, not shared (matching) DNA with another person.

Adding in pedigree collapse, you can see that we have three Gen 1 people involved, three Gen 2 descendants, and two Gen 3 and Gen 4 people.

Each of those people inherit and pass on segments from our original couple at the top.
We have three distinct inheritance paths leading from our original couple to Gen 5.
We have a first cousin marriage at Gen 2, at left, which means that their child, Gen 3, will have an elevated amount of the DNA of their common ancestors.

In Gen 4, two people marry who both descend from a common couple, meaning their child, Gen 5, descends from that couple in three different ways.

Did your eyes just glaze over? Well, mine did, too, which is why I had to draw all of this out on paper before putting it into PowerPoint.

The Gen 5 child inherits DNA from the ancestral couple via three pathways.
The next thing to keep in mind is that just because you inherit the DNA from an ancestor does not mean you match another descendant. Inheritance is not matching.

You must inherit before you can match, but just because you and someone else have inherited a DNA segment from a common ancestor does not guarantee a match. Those segments could be in different locations.

Categories of DNA

When dealing with inheritance and descent, we discuss four categories of DNA.

  • In the first generation, full siblings will, in about 25% of their locations, share the same DNA that has been inherited from both parents on the same chromosome. In other words, they match each other both maternally and paternally at that location. Those are FIR.
  • The DNA you inherit from an ancestor.
  • The DNA that both you and your cousin(s) inherit from a common ancestor and match on the same location. This is shared DNA.
  • The DNA that both you and your cousin(s) inherit from a common ancestor, but it’s not in the same location, so you do not match each other on that segment. Just because you inherit DNA from that ancestor does not necessarily mean that your cousin has the same DNA from that ancestor. This is inherited but not shared.

Inheritance is Not The Same as Matching

Inheritance is not the same thing as matching.

Inheriting our ancestor’s DNA isn’t enough. We need to match someone else who inherited that same segment in order to attribute the segment to that specific ancestor.

Depending on how close or distant the relationship, two people may share a lot of DNA (like full siblings), or one segment in more distant matches, or sometimes none at all. As we reach further back in time, we inherit less and less of our increasingly distant ancestors’ DNA, which means we match increasingly fewer of their descendants. I wrote about determining ancestral percentages in the article,  Ancestral Percentages – How Much of Them is in You?

Based on how much DNA we share with other known relatives, we can estimate relationships.

Pedigree collapse, where one descends from common ancestors more than once, increases the expected amount of inherited DNA, which in turn increases the probability of a shared match with other descendants.

Ancestral Couple Matching Between Shared DNA ~cM Shared DNA ~% Range (Shared cM Project) FIR – Identical DNA
Generation 1 Full Siblings 2600 50 1613-3488 25%
Generation 2 First Cousins 866 12.5 396-1397 0
Generation 3 Second Cousins 229 3.125 41-592 0
Generation 4 Third Cousins 73 0.78125 0-234 0

Here’s an example through third cousins, including expected FIR, fully identical regions where full siblings match each other on both their maternal and paternal chromosomes in the same location.

I provided a larger summary chart incorporating the information from public sources, here, minus FIR.

Of course, double cousins, where two pairs of siblings marry each other, represent another separate level of complexity. DNA-Sci’s Double Cousin Orogen explains this here and also provides a tool.

Double cousins, meaning when two pairs of siblings marry each other, are different from doubly related.

Doubly related means that two people descend from common ancestors through multiple paths, meaning multiple lines of descent. Doubly related is pedigree collapse. Double cousins is pedigree collapse on steroids.

Pedigree Collapse, aka Doubly Related

Calculating expected inherited DNA from multiple lines of descent is a bit more challenging.

A handy-dandy chart isn’t going to help with multiple relationships because the amount of expected shared DNA is based on the number of and distance of relationships.

Please note that this discussion excludes X-DNA matching which has its own inheritance path.

It’s time for math – but I promise I’ll make this relatively easy – pardon the pun.

What’s Behind the Math?

So, here’s the deal. I want you to understand why and how this works. You may not need this information today, but eventually, you probably will. This is one of those “refer back to it” articles for your personal library. Read this once as a conceptual overview, then read it again if you need to work through the relationships.

This is easy if you take it one step at a time.

First, we calculate each path separately.

In the first generation, full siblings inherit identical (FIR) DNA on both their mother’s and father’s chromosomes.

In the second generation, the male inherits the maternal segment, and the female inherits the paternal segment.

In the third generation, their child inherits those segments intact from both of their parents. The child inherits from the ancestral couple twice – once through each parent.

In generation 1, those two segments were FIR, fully identical regions. Both of those men married unrelated wives. When their children, Gen 2, were born, they had either the maternal or paternal segment from their father because they had an entirely different segment in that location from their mother.

However, the child in Gen 3 inherited the original green segment from their father and the original pink segment from their mother – reuniting those FIR segments in later generations.

First Cousin’s Child

Let’s calculate the inheritance for the child of those two first cousins who married.

Ancestral couple Inherited cM Inherited %
Gen 3 – Great-Grandchildren 875 cM 12.5
Gen 3 – Great-Grandchildren 875 cM 12.5
Total 1750 cM 25

Normally, a Gen 3 person inherits roughly 875 cM, or 12.5% of their great-grandparent’s DNA. However, since their grandparents were first cousins, they inherit about twice that amount, or 1750 cM.

While a Gen 3 person inherits as much as a grandchild (25%) normally would from the original couple, they won’t match on all of that DNA. When matching, we need to subtract some of that DNA out of the equation for two reasons:

  • In the first generation, between siblings, some of their DNA was fully identical and cannot be identified as such.
  • In the second generation, they will each have some parts of the ancestral couple’s DNA that will not match the other person. So, they inherit the same amounts from their common ancestors, but they can only be expected to match on about 25% of that amount two generations later.

However, the child of first cousins who marry inherits more DNA of the common ancestors than they would if their parents weren’t related. It’s just that some of that DNA is the same, potentially on the maternal and paternal chromosomes again, and some won’t match at all.

While matching DNA is the whole point of autosomal DNA testing, fully identical DNA matching regions (FIR) cannot be identified that way. For the most part, other than identifying full and half-siblings, sometimes pedigree collapse, and parent-relatedness, fully identical DNA isn’t terribly useful for genealogy. However, we still need to understand how this works.

It’s OK if you just want to say, “I know we’ll share more DNA due to pedigree collapse,” but if you want to know how much more to expect, keep reading. I’d really like for you to understand use cases and be able to track those segments.

Remember, we will learn a super-easy shortcut at the end, so for now, just read. It’s important to understand why the shortcut works.

Sibling Inheritance Versus Matching

In order to compare apples to apples, sometimes we need to remove some portion of DNA in our calculations.

Remember story problems where you had to “show your work”?

Calculating Expected DNA

Here’s the step-by-step logic.

Ancestral couple Inherited Non-Identical cM Inherited %
Gen 1 first son 3500 50
Gen 1 second son 3500 50
Less identical segments (FIR) -1750 (subtracted from one child for illustration) 25
Gen 2 son 1750 25
Gen 2 daughter married Gen 2 son 875 12.5
Gen 3 – Their child path through Gen 2 son 875 cM 12.5
Gen 3 – Their child path through Gen 2 mother 437.5 cM 6.25
Their child total without removing identical segments 1750 cM 25
Their child total after removing identical segments 1312.5 18.75

Category cMs Most Probable Degree Relationship
No Pedigree Collapse 875 98% Great grandparent or great-grandchild, great or half aunt/uncle, great or half niece/nephew, 1C 3
Pedigree Collapse without identical segment removal 1750 100% Grandparent, grandchild, aunt/uncle, half-sibling, niece/nephew 2
Pedigree Collapse after identical segment removal 1312.5 56% grandparent, grandchild, aunt/uncle, niece/nephew, half-sibling 2

Just because you HAVE this much shared (and/or identical) DNA doesn’t mean you’ll match on that DNA.

Next, let’s look at Gen 5 child who inherited three ways from the ancestors.

If you think, “This will never happen,” remember that it did, which is why I was working through this story problem. It’s not uncommon for families to live in the same area for generations. You married who you saw – generally, your family and neighbors, who were likely also family.

Let’s take a look at that 5th generation child.

The more distantly related, the less pedigree collapse affects matching DNA. That’s not to say we can ignore it.

Here’s our work product. See, this isn’t difficult when you take it step by step, one at a time.

Ancestral couple Inherited Non-Identical cM Inherited %
Gen 3 Child total after removing identical segments 1312.5 18.75
Gen 4 father – half of Gen 3 father 656.25 9.375
Gen 5 child – half of Gen 4 father 328.125 4.6875
Gen 5 child – mother’s side calculated from ancestral couple normally 218.75 3.125
Total for Gen 5 Child 546.875 7.8125

Inheritance Ranges

Lots of factors can affect how much DNA a person in any given generation inherits from an ancestor. The same is true with multiple paths from that same ancestor. How do we calculate multiple path inheritance ranges?

As with any relationship, we find a range, or combined set of ranges for Gen 5 Child based on the multiple pathways back to the common ancestors.

Gen 5 Child Inherited Non-Identical cM Inherited %
Without removing either paternal or maternal identical cMs 656.25 9.375
After removing paternal identical cMs only 546.875 7.8125

 
After removing maternal cMs only 546.875 7.8125

 
After removing both paternal and maternal identical cMs 362.50 6.25
Normal Gen 5 no pedigree collapse 218 3.125

What About Matching?

Inheritance and matching are different. Most of the time, two people are unlikely to share all of the DNA they inherited from a particular ancestor. Of course, inheriting through multiple paths increases the likelihood that at least some DNA from that ancestor is preserved and that it’s shared with other descendants.

Two people aren’t expected to match on all of the segments of DNA that they inherit from a particular ancestor. The closer in time the relationship, the more segments they will inherit from that ancestor, which increases the chances of matching on at least one or some segments.

Clearly, pedigree collapse affects matching. It’s most pronounced in closer relationships, but it may also be the only thing that has preserved that ONE matching segment in a more distant relationship.

So, how does pedigree collapse actually affect the likelihood of matching? What can we actually expect to see? Is there a name for this and a mathematical model to assist with calculations?

I’m so glad you asked! It’s called Coefficient of Relationship.

Coefficent of Relationship

My colleague, Diahan Southard, a scientist who writes at YourDNAGuide has authored two wonderful articles about calculating the statistical effects of pedigree collapse.

You can also read another article about the methodology of calculating coefficient of relationship, here, on WaybackMachine.

Diahan is a math whiz. I’m not, so I needed to devise something “quick and dirty” for my own personal use. I promised you a “cheat sheet,” so here’s the methodology.

Two Inheritance Paths – First and Third Cousins

Let’s look at an example where two people are both first cousins and third cousins because their grandparents were also first cousins.

Let’s calculate how these two people are related. They are first cousins and also third cousins.

When calculating the effects of pedigree collapse, we calculate the first relationship normally, then calculate the second relationship and add a portion of the result.

Here’s the math.

Using the Shared cM Project for the expected amount of shared DNA for both relationships, we’ve calculated the expected range for this pedigree collapse relationship.

Tying this back to degrees of relatedness.

Let’s look at ways to do Quick Calculations using the publicly available Shared cM charts and my composite tables, here.

Using Average Shared DNA

This first methodology uses average expected amount of shared, meaning matching, DNA. Please note, I’m not necessarily expecting you to DO this now, just read to follow.

Using Average Inherited DNA

Here’s a second method using average inherited DNA, meaning people wouldn’t be expected to match on all of the inherited DNA – just a portion.

You can’t always use the shared cM charts because all relationships aren’t represented, so you may need to use the amount of expected inherited DNA instead of shared DNA amounts.

Methodology Differences

Remember, none of these methodologies are foolproof because DNA inheritance is random. You may also have additional relationships that you’re aware of.

So, what’s the easiest method? Neither, actually. I’ve found an even easier method based on these proven methodologies.

Easy-Peasy Pedigree Collapse Shortcut Range Calculation in 4 Steps

Now that you understand the science and reasoning behind all of this, you can choose from multiple calculation methodologies after drawing a picture of the relevant tree.

You’re probably wondering, “What’s the easiest way to do this?”

  • These quick calculation methods are the easiest to work with for non-scientists and non-math whizzes. These are the calculations I use because, taking into account random recombination, you can’t do any better than get close.
  • Also, remember, if you’re dealing with double relationships, meaning double first cousins, you’ll need to take that into consideration, too.
  • If endogamy is involved, your matches will be higher yet, and you should use the highest calculations below because you need to be on the highest end of the range – and that may still not be high enough.

In these Easy-Peasy calculations, you calculate for the lowest, then the highest, and that’s your range. Please note that these are options, and truly, one size does not fit all.

  1. For the lowest end of the range, simply use the average of the highest relationship. In this case, that would be 1C, which is 866 cM. Remember that you may not share DNA with third cousins. 10% of third cousins don’t share any DNA, and 50% of fourth cousins don’t.
  2. For the highest end of the range, find the second relationship in the Shared cM chart, divide the average by half, and add to the value from the closest relationship. In this case, half of the 3C value of 76 is 38.
  3. Add 38 to 866 for the highest end of the range of 904.
  4. If there’s yet another path to ANY shared ancestor, add half that amount too to calculate the high end of the range – unless it’s 4C or more distant, then don’t add anything.

You can see that this easy-peasy range calculation for pedigree collapse compares very well to the more complex but still easy calculations.

  • Easy-peasy calculation: 866-904
  • Other calculation methods: 850-903
  • For this same relationship combination, Diahan’s statistical calculation was 850 cM.

Back to Genealogy

What’s the short story about how pedigree collapse affects genealogy?

Essentially, in close generations, meaning within a few generations of two first cousins marrying, descendants can expect to inherit and share significantly more DNA of the common ancestors, but not double the amount. As we move further away from those marriages in time, the effect becomes less pronounced and more difficult to detect. You can see that effect when calculating multiple paths where at the fourth cousin level, or more distant, those cousins have a 50% or greater possibility of not sharing DNA segments.

Of course, with multiple paths to the same ancestor, your chances of inheriting at least some segments from the common ancestor are increased because their DNA descends through multiple paths.

Today, close marriages are much less common and have been for several generations in many cultures, so we see fewer instances where pedigree collapse makes a significant difference.

Within a population or group of people, if pedigree collapse becomes common, meaning that there are multiple paths leading back to common ancestors, like our three-path example, DNA segments from the common ancestors are found among many people. Significant pedigree collapse becomes endogamy, especially if marriage outside of the group is difficult, impossible, or discouraged.

Normally, pedigree collapse is not recorded in actual records. It’s left to genealogists to discover those connections.

The exception, of course, is those wonderful Catholic parish records where the priest granted dispensations. Sometimes, that’s our only hint to earlier genealogy. In the case of the marriage of Marie-Josesphe LePrince to Jacques Forest, the priest wrote “dispense 3-3 consanguinity,” which tells us that they shared great-grandparents. It also tells us that their grandparents were siblings, that the bride and groom were second cousins, and that their children and descendants inherited an extra dose of DNA from their common great-grandparents.

How does that affect me today? Given that I’m their seventh-generation descendant – probably not at all. Of course, they are Acadian, and the Acadians are highly endogamous, which means I match many Acadians because all Acadians share the DNA of just a few founders, making it almost impossible to track segments to any particular ancestor. If it weren’t for endogamy, I would probably match few, if any, of their descendants.

Now, when you see those Catholic church dispensations or otherwise discover pedigree collapse, you can be really excited, because you understand the effects of pedigree collapse and how to calculate resulting matches! You might, just might, have retained a DNA segment from those ancestors because you inherited segments through multiple paths – increasing the probability that one survived.

_____________________________________________________________

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

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

Posted on by
24

“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

Posted on by
14

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?

Posted on by
10

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