When you see a DNA match, do you wonder how far back in your trees your common ancestors live? How do you know where to search?
I’ve been working through my DNA match list person by person, reviewing the information and trees for each match, searching for common ancestors.
Whether you’re looking at individual matches, shared matches, clusters or triangulation groups, trees are essential for finding common ancestors.
My favorite vendor-provided tree is my MyHeritage tree. They’ve done a great job, so I’m using their tree for my examples today.
Here’s the question I’m trying to answer – based on how much DNA I share with someone, how far up that person’s tree, roughly, do I need to look for our most recent common ancestor? And, is there something else I can tell?
Tree Size Matters aka How Far Up the Tree Do I Need to Look?
So, if you click on your matches’ trees, how far up their tree do you need to look for a common ancestor? How many times will you need to click to expand their tree beyond the 4 (Ancestry) or 5 (MyHeritage) generations initially displayed, assuming your match has a tree that size? How far out, meaning how many generations do you need to hope and pray they have extended their tree?
Conversely, how many generations do YOU need to include for your tree to be useful for:
- Other testers to find common ancestors with you
- Theories of Family Relativity provided by MyHeritage, suggesting common ancestors with other testers
- ThruLines at Ancestry
- Family Matching (bucketing) at FamilyTreeDNA which assigns your matches either maternally or paternally. (Note – FamilyTreeDNA is transitioning their trees to the MyHeritage platform.)
If you’re thinking that the size of YOUR tree doesn’t matter, think again.
Not only can the vendors not help you effectively without a tree – genealogy is a collaborative sport. Other people NEED the generations in your tree to locate your common ancestors, just like you NEED to see as many generations in their tree as possible. The vendors NEED as complete a tree as you can provide to help you further.
DNA+Trees Bulldoze Brick Walls
But maybe the most important aspect is that you NEED trees to break through brick walls – especially in conjunction with DNA and tools like clustering that show you visual images of genetic commonality.
We all need to be team players when we have that option – meaning we know who are ancestors are. Our brick walls can be solved, and you can be a puzzle piece of solving brick walls for others too.
Some of my closest friends and cousins are a direct result of DNA matches and genealogy collaboration over the years. (You know who you are!) I’ve even discovered that several friends are cousins too – which I would never have happened without DNA and trees.
Guidelines for What’s Reasonable
What is a reasonable number of generations to peruse for common ancestors?
The answer is – it depends! (I’m sorry…)
Let’s sort through this.
Given that, on AVERAGE, inherited autosomal DNA from a particular ancestor is halved in each successive generation during recombination between the parents, we can calculate the expected average. However, in reality – DNA isn’t always halved. Sometimes segments are passed intact, divided but not in half, or not inherited at all. That’s why you may not match some third cousins, but match some 7th cousins. Random recombination is, in fact, random.
Every segment has its own individual history.
That’s part of the reason we use triangulation, to confirm that a specific segment originated with a particular couple or ancestral line.
Here are a few rules of thumb, with links to articles that explain the various terms and concepts:
- There are no known instances of second cousins or closer NOT matching.
- Some (but not all) people find their common ancestor in the first 5 or 6 generations.
- Many people have proven, triangulated matches to the 10th generation, but those are more difficult to prove, often due to incomplete trees (brick walls) at that distance on either your side, your match’s side, or both. I have no brick walls at 5 generations, counting my parents as generation 1, but I have 6 female brick walls in the 6th generation.
- If you’re lucky, you can spot your common ancestral surname on the first page of your match’s tree – and follow that line back. Note that there may be additional common ancestors, so view each of their lines to the end. The MyHeritage tree makes this super easy!
- Pedigree collapse, where you, and/or the other person share multiple lines, known or unknown, is a complicating factor. Pedigree collapse often means you share more DNA than would be expected for a specific relationship.
- Endogamy, which is pedigree collapse on steroids, is real and will cause many smaller matches.
- Based on the number of distant versus close cousins you have, you will have MANY more smaller matches than larger ones.
- And last, but not least, some matches, especially smaller ones, are identical by chance (IBC), not identical by descent (IBD).
All of that said, we can estimate the number of generations back in our matches’ trees where we might need to look for that common ancestor.
As I’ve been reviewing all of my matches, I realized that I can look at the match cM size and mentally size up just about where in their tree I will find our common ancestor. In essence, I’ve “bottled that” for you, here.
Using Trees Effectively
One of the reasons I love the MyHeritage tree is that as you need to click further back in trees beyond the generations initially displayed, which occurs often – the next generations open to the right, the earlier generations just shift left and they all remain visible.
I know that might not sound important, but it is – incredibly – especially when you’re evaluating several matches. Otherwise, it’s easy to lose track of where you are in someone’s tree. I have 9 generations open, above, and I can just keep going – with the more recent generations just shifting left.
But there’s more!
When viewing matches’ trees, I can also click on anyone in their tree, and a profile box opens to the left with additional information about that person, leaving the tree open so I don’t lose my place and have to click around to find it again. I can’t even begin to tell you how wonderful this is, and it’s unique to MyHeritage. You can tell the MyHeritage tree was designed by actual genealogists.
This feature is incredibly useful because many, if not most, of the common ancestors with your matches will be beyond the first page displayed.
Thank you, thank you, MyHeritage!!!
Estimating the Number of Generations by the Amount of Shared DNA
How far up the tree you’ll need to look can be estimated by the amount of DNA that you share with a particular match.
Vendors estimate the relationship of DNA matches by either the percentage of shared DNA or the number of shared centimorgans (cMs), but there’s no quick reference to show you, generationally, where to focus in you and your matches’ trees for your common ancestor.
That’s the handy reference Generation Tree Chart that I’ve created here.
In the article, Shared cM Project 2020 Analysis, Comparison and Handy Reference Charts, I compiled information from multiple sources into one chart detailing HOW MUCH DNA can be expected to be shared at various relationship levels. Shared cM Project information is also visualized at DNAPainter
What I need to know now, though, isn’t an estimate of how closely we are related, but how many generations back to look for our common ancestor in my and their trees.
As I’m clicking through my matches, the majority, by far, are smaller than larger. That makes sense, of course, because we have many more distant relatives than close relatives.
At FamilyTreeDNA, I have 8758 matches who are not immediate or close family.
| Number of Matches | Relationship Range | cM Range |
| 10 | Half-1C and 1C1R | 318-637 cM |
| 4 | 2C and equivalent | 159-318 cM |
| 7 | Between 2C-3C, such as half-2C | 80-159 cM |
| 79 | 3C and equivalent | 40-80 cM |
| 814 | 3C-4C and equivalent | 20-40 cM |
| 7548 | 4C and equivalent | 9-20 cM |
| 293 | Below 4C and equivalent | 7-9 cM |
I know the people in the first two categories and some of the people in the third category, but the genetic/ancestral scavenger hunt begins there.
All Cousins Are Not Equivalent
You’re probably wondering about the word “equivalent.” Genetically, people of different relationships carry the same amount of expected DNA. We not only have 5th cousins (5C), for example, we have:
- Half-fifth-cousins
- Fifth-cousins-once-removed (5C1R)
- Fifth-cousins-twice-removed (5C2R)
- And so forth
I wrote about determining cousin relationships, meaning halves and removed,here.
Genetically speaking, a 5C2R carries the same expected amount of shared DNA as a 6C, so they are functional equivalents. How do we resolve this and where do we look in our trees for our common ancestors?
I’m so glad you asked!
Where Do Various Cousin Levels Fall in My Tree?
We know that first cousins share grandparents, but as we get further back in our tree, it’s difficult to remember or calculate how many generations back a 6th cousin is in our tree.
I’ve used my MyHeritage tree to display 1st through 10th cousins, labeled in red, and the generation number they represent, in black. So, my common ancestors with my second cousins are found 3 generations out in my tree.
Making things more challenging, however, is that unless we know the match already, we’re trying to figure out how closely the match is actually related to us based on their DNA. Not all cousins of any level share the same amount of DNA, so the best vendors can do is provide an estimate or relationship range.
To determine our actual relationship, we need to find our most recent common ancestor.
Where, approximately, in my tree would I look for each category of match, especially that huge group of 7548 people?
Good question!
The Generation Tree Chart is Born
I needed a quick reference for approximately how many generations back in time our common ancestors existed by how much DNA we share, so I know how far back in someone’s tree I need to look.
I’ve reorganized the data from my earlier articles and created a new resource.
The Generation Tree Chart
The Generation Tree Chart:
- Is not meant to identify parents or close relatives.
- Does not include parents or grandparents.
- Counts your parents as generation 1. Some people count themselves as generation 1. If you’re discussing this table, keep in mind that you may be one generation “off” in your discussions with someone who counts differently.
- This chart clusters the relationships according to color, based on how much DNA people of that relationship are expected to share. For example, a first-cousin-twice-removed (1C2R) shares the same expected amount of DNA with you as a second-cousin (2C).
- All cousin relationships that are expected to share the same amount of DNA are in the same color band.
- If you’re using this chart with Ancestry’s numbers, use the unweighted (pre-Timber) amount of DNA.
The colored bands correlate to shared DNA, but the shared ancestor isn’t necessarily the same generation back in time.
This is my “show your work” chart. You’ll notice a few things.
- The “Avg % Shared” column is the amount of shared DNA expected based on a 50% division (recombination) in each generation, which almost never happens exactly.
- The “Expected cM” column is the expected cM amount based a 50% division in each generation.
- I’ve incorporated the DNAPainter mean, low and high range for each relationship.
- The expected number of shared cMs, in the “Expected cM” column is almost always smaller than the “cM Mean” from DNAPainter. The mean is the midpoint reported in the Shared cM Project for all respondents of that relationship who reported their shared DNA – minus the outliers.
This fact that reported is often significantly higher than expected is particularly interesting. In the closer generations, it doesn’t really matter, but beginning about the 6th blue band and the 7th red band in the chart, the mean is often twice the expected amount.
Remember that DNAPainter numbers are based on the Shared cM Project which relies on user-reported relationships and their associated cM match amounts. You can view Blaine Bettinger’s paper about the most recent Shared cM Project version (2020) and his methodologies here.
My theory is that the more distantly people match, the less likely they are to report the relationship accurately. They may be reporting the relationship they believe to be accurate, life a full versus a half cousin, but that’s not actually the case. It’s also possible that there are multiple unknown relationships or pedigree collapse, or both.
Furthermore, from the red band to the end of the chart, the reported amounts are significantly higher than expected, which is probably a function, in part, of “all or nothing” segment transmission. In other words, if someone’s parent carries a 10 cM segment, you’re probably going to inherit all of it or none of it. If it’s actually divided to 5 and 5 cM, you’re not going to see it on any match list.
In my case, I have several 8 cM triangulated matches who descend from common Dodson ancestors whose descendants intermarried a couple of generations later. Therefore, these matches are, respectively, both my 6C2R and 7C3R from the same line (20 cM total match), two matches at 6C1R (66 cM and 19 cM), and one 6C (51 cM). These people also triangulate on multiple segments. Given the high amount of shared DNA for this relationship level, I suspect additional pedigree collapse someplace. At least one person also matches on an unrelated line that I never realized before doing this match-by-match analysis, which opens up new possibilities.
Next, the meat of this chart.
- The “Generations Back in Tree” column shows where your common ancestor with someone in that cousin generation would be expected. For example, in the first three bands, all of the first cousin variants are found two generations back, and your grandparents are your common ancestors.
All of the 2C variants descend through great-grandparents, which are 3 generations back in your tree.
Plase note that you can easily find the amount of DNA that you share with a match in the “Expected cM” and “Mean” Columns, and look to the right to see the Generations Back in Tree.
For example, if I have a match where I share 20 cM of DNA, I’m going to be looking between the red band and the second white band. The generations back in tree range from 4-6, or the common ancestor could potentially be further back. In other words, if I’m lucky, I’ll spot common ancestors on the first tree page displayed, but I may well need to display additional generations.
- The “Common Ancestors” column displays the common ancestor with anyone in that cousin generation. So, anyone in any variation of 3C shares great-great-grandparents with you.
- “How Many” shows how many great-great-grandparents you have – 8.
Color Bands and Generations
Color bands represent the same amount of expected DNA, but the various relationships that are included in those bands represent at least two different “Generations Back in Tree.”
For example, looking at the green band, the half 1C3R will be found in the grandparents generation, or generation 2, the 2C2R and half 2C1R are in the great-grandparents, or generation 3, and the 3C is found in the great-great-grandparents, or generation 4.
Where I really needed this chart, though, was in the more distant generations. While we are clearly dealing with a range, if I see a match with 11 or 12 cM, our common ancestor is nearly always at least 6 generations out, and often more.
The Net-Net of This Exercise
The majority of my matches, 7548, fall into the red band of 9-20 cM, which should be the 4th or 5th generation, either great-great or GGG-grandparents, but in reality, common ancestors will often be found more distantly in matches’ trees.
Most of your matches will be 20 cM or below, meaning they are at least 4/5 generations distant, or further – which translates to NOT the first tree page displayed. This why using the MyHeritage tree is so convenient, because when you click to the next generations, they just open and it’s VERY easy to quickly click and expand every generation with no back-clicking needed. Tip – when viewing profile cards for their ancestors, be sure to note locations which are important hints too. You can also click to “research this person.”
If your match doesn’t have a tree developed to at least 5 generations, it’s unlikely that you will be able to find a common ancestor for someone with less than a 20 cM match. However, all is not lost because you may recognize a surname, and if you build out the tree for your match, you may find your common ancestor. I build out my matches’ trees often! (Yes, it’s painful and irritating, but just do it! After all, we’re genealogists. We got this.)
For people with smaller cM matches, you may be looking even further out. I have some solid triangulated matches with multiple people at 6 and 7 generations..
The further out in time, the more triangulated people you need to be confident that your common ancestor who contributed that segment is identified correctly. At that distance, most people will have dead end lines and brick walls, probably yourself included.
However, my research methodology has the potential to break through brick walls.
Brick Walls Breakers
When I’m working on match and triangulation clusters, not only am I looking for MY known ancestors, I’m also looking for common surnames, or more specifically, common ancestors between my matches trees.
In some cases, common ancestors only mean that I’m viewing first cousins to each other, but in other cases, those common ancestors between my matches, but not me, MAY POINT DIRECTLY TO A MISSING BRICK WALL ancestor of mine.
Another hint that this might be the case is when the shared cMs seem high relative to how far back your common identified ancestor is in your tree – which is the case with my Dodson cluster. There may be a second relationship obscured there, especially if they match each other more “normally” and it’s only my matches that are higher than expected with multiple people in this cluster.
Research Methodology
If you’re wondering how I approach this process, I use a spreadsheet organized by triangulation cluster because everyone in a triangulation cluster matches each other on a particular segment. This means that the triangulated segment comes from a common ancestor (or is idencal by chance.) Each match has it’s own row in the cluster on my spreadsheet.
This spreadsheet could also be organized by shared match or matrix cluster, but I prefer smaller triangulation clusters where everyone matches each other and me on the same segment – because it points to ONE shared souce of the DNA – meaning one ancestor or ancestral couple.
I downloaded my match list at FamilyTreeDNA where I can see which matches are assigned either maternally or paternally based on identified, linked relationships, and who matches on the same segments. I used that spreadsheet as the foundation of this spreadsheet, but I could also add people who match on that segment and triangulate from other vendors who provide matching segment information, such as MyHeritage.
Using my Dodson example group, this group of people above, on my father’s side, hence the blue color, also triangulates on other segments. Other clusters are significantly larger, with around 50 cluster members.
One person, JA, descends from Dodson cousins who intermarried, which is pedigree collapse, so they may carry more Dodson/Durham DNA than they would otherwise.
If someone has a small tree, I often use traditional genealogy resources to expand their tree if I recognize a surname.
I track my other ancestors’ surnames that I notice in their trees, which provides a clue for additional ancestors. Of course, common surnames sometimes aren’t useful. However, one match, JC, found in this group is a proven Crumley line cousin who has colonial Virginia ancestors, but no prior knowledge of a Dodson/Durham line – so this could be a HUGE hint for one of JC’s brick walls.
This example cluster from my mother’s side includes my mother, who I haven’t listed, and also RM, a known second cousin who I tested. Based on his known common ancestors with me, I know immediately that these segment matches all track to John David Miller and Margaret Elizabeth Lentz, or beyond. Sure enough DW has a tree where our common ancestor is David Miller, father of John David Miller, and TK is related to DW based on an obituary. So far, we know this segment originated with David Miller and his wife, Catherine Schaeffer, but we don’t know if the segment originated with the Miller or Schaeffer parent.
One additional cluster member shows a Cyrus Miller out of Pennsylvania and my initial attempt at extending their tree using WikiTree, MyHeritage and Ancestry to find a common ancestor was not fruitful, but a deep dive might well produce more, or the common ancestor could reach back into Europe.
As new people test and match, I can add them to the spreadsheet in the clusters where they fit.
Summary Generation Tree Chart
Here’s a summary version of the Generation Tree Chart for you to use, without the cM high and low ranges, and without the red boxes. This is the one I use the most.
Here’s the full chart, including the ranges, but with no red boxes.
The Bottom Line
To derive the most benefit, we all need to develop our trees as far as possible, and share with others. A rising tide lifts all ships!
It’s impossible to identify common ancestors without trees, which means it’s also impossible to use genetic genealogy to break through brick walls.
Please check your trees at the various vendors, if you have multiple trees, and at WikiTree, to be sure you’ve added your most distant known ancestor in each line.
Link your known relatives to their position in your tree at FamilyTreeDNA, which allows them to triangulate behind the scenes and assign (bucket) your matches either maternally or paternally on your match list.
What new information is waiting for you in your matches? Do you have brick walls that need to fall?
_____________________________________________________________
Share the Love!
You’re always welcome to forward articles or links to friends and share on social media.
If you haven’t already subscribed (it’s free,) you can receive an e-mail whenever I publish by clicking the “follow” button on the main blog page, here.
You Can Help Keep This Blog Free
I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the affiliate links in the articles or to the vendors below if you are purchasing products or DNA testing.
Thank you so much.
DNA Purchases and Free Uploads
- FamilyTreeDNA – Y, mitochondrial and autosomal DNA testing
- MyHeritage DNA – Autosomal DNA test
- MyHeritage FREE DNA file upload – Upload your DNA file from other vendors free
- AncestryDNA – Autosomal DNA test
- AncestryDNA Plus Traits
- 23andMe Ancestry – Autosomal DNA only, no Health
- 23andMe Ancestry Plus Health
Genealogy Products and Services
- MyHeritage Subscription with Free Trial
- Legacy Family Tree Webinars – Genealogy and DNA classes, subscription-based, some free
- Legacy Family Tree Software – Genealogy software for your computer
- OldNews – Old Newspapers with links to save to MyHeritage trees
- MyHeritage Omni comprehensive “everything included” subscription plan
- Newspapers.com – Search newspapers for your ancestors
- NewspaperArchive – Search different newspapers for your ancestors
My Books
- DNA for Native American Genealogy – by Roberta Estes, for those ordering the e-book from anyplace, or paperback within the United States
- DNA for Native American Genealogy – for those ordering the paperback outside the US
- The Complete Guide to FamilyTreeDNA – Y-DNA, Mitochondrial, Autosomal and X-DNA – for those ordering the e-book from anyplace, or paperback within the United States
- The Complete Guide to FamilyTreeDNA – Y-DNA, Mitochondrial, Autosomal and X-DNA for those ordering the paperback from outside the US
Genealogy Books
- Genealogical.com – Lots of wonderful genealogy research books
- American Ancestors – Wonderful selection of genealogy books
Genealogy Research
- Legacy Tree Genealogists – Professional genealogy research
































































































