Category Archives: Family Tree DNA

The Mystery of the Blue Fugates and Smiths: A Study in Blue Genes and Pedigree Collapse

Posted on by
11

The story of the Blue Fugates, an Appalachian family, is quite interesting, from a genetic perspective, a genealogical perspective, and a genetic genealogy perspective.

Who Are the Blue Fugates?

Martin Fugate, supposedly an orphan from France, and his bride, Elizabeth Smith, who had married by 1840, have long been attributed as the progenitors of the Blue Fugate Family of Troublesome Creek, in and around Perry County, Kentucky.

Their descendants were known as “The Blue Fugates” and also “The Blue People of Kentucky” because some of their children and descendants carried a recessive autosomal genetic trait, Methemoglobinemia.

Methemoglobinemia causes the skin to appear blue due to an oxygen deficiency in the red blood cells. Some people only exhibit this characteristic, or even just blue tinges in their fingernails and lips, when they are cold or agitated, such as when infants cry. Yet others are very, very blue.

Inheritance

In order for someone to exhibit the autosomal recessive trait of blueness due to Methemoglobinemia, they must inherit a copy of the gene from BOTH PARENTS. That’s why this trait is so rare.

  • If the parents have only one copy each, they are carriers and will not have the condition themselves.
  • If one parent carries either one or two copies, and the other parent does NOT carry a copy, their offspring CANNOT carry two copies of the mutation and will not be blue.
  • If both parents carry a copy, and both parents pass their copy on to their offspring, the offspring will probably exhibit some level of blueness – from just a tinge when they are cold, ill or or upset, to very, very blue.

I’m not a physician, so I’m not delving into the medical specifics of Methemoglobinemia, but suffice it to say that levels of 10-20% of methemoglobin in the blood produce blue skin, higher levels can produce more severe medical conditions, and levels beneath that may not be visually detectible.

What’s important for the genealogy aspect of this story is that both parents must carry a copy AND pass their copy on for the condition to express in their offspring.

We’ve learned a lot since the 1800s when this was first observed in various members of the Fugate family in Perry County, KY, and since the 1960s when this phenomenon was first studied in the Fugate family and their descendants. To be clear, there are also references to the blue Combs and blue Ritchies in and around Perry County – but the common factor is that they have ancestors that descend from the Fugate family AND the Smith family ancestors, both.

During my research, I’ve proven some of what was initially accepted as fact was incorrect – and I’d like to correct the record. Bonus points too, because it’s just such a great genealogy story!

My Interest

I’ve been inordinately interested in the Fugate family for a long time – but not because of their famous blueness.

The Fugate family has been found for more than 225 years alongside my Cook, Claxton, Campbell, and Dobkins families. First, in Russell County, VA, where Josiah Fugate was granted land along Sword’s Creek in 1801 that adjoined Harry Smith, Richard Smith, and others, including my brick-wall ancestor, Joel Cook. Keep in mind that we have never discovered the birth surname of Joel’s wife or Joel’s parents.

Joel’s daughter, Sarah, married James Claxton about 1799 or 1800 in Russell County, and in February of 1802, James Claxton and Zachariah Fugate, among others, were ordered to view and lay out a new road. They were clearly neighbors, living on the same road, and knew each other well. We don’t know who James’ parents were either.

The Fugates first lived adjacent to the Cook, Riley, Stephens, and Claxton families on Mockason Creek in Russell County, then later migrated with the same group of families to Claiborne County where they lived along the Powell River near the Lee County, VA line, and are very closely associated with the Dobkins and Campbell lines.

Sometime between 1802 and 1805, several Russell County families moved 110 miles down the mountain range and settled together on the Powell River in Claiborne County, TN.  About the same time, others from the same cluster moved to what would eventually become Perry County, KY.

In 1805, the Fugates were ordered as road hands on the north side of Wallen’s Ridge in Claiborne County, the part that would become Hancock County in the 1840s, along with James Claxton and several Smiths.

In 1808, James Claxton witnessed a deed to Henley Fugate and John Riley.

The unsubstantiated family rumor, repeated as fact but with no source, has always been that William Fugate married the sister of my John Campbell. If that were true, tracking the Fugates would help me track my Campbells – yet another brick wall. Hence, my early interest in the Fugate family. Until now, I’ve never solved any part of that puzzle.

In 1827, in Claiborne County, Henry Cook, road overseer, is assigned John Riley, Henly Fugate, William Fugate, Fairwick Claxton (son of James who had died in 1815), and others. These families continued to be allied, living close to each other.

In 1842, William Fugate (1799-1855), born to William Fugate and Sarah Jane Stephens in Russell County, is involved in the estate of John Campbell, born about 1772, who had died in 1838. John Campbell was the husband of Jane “Jenny” Dobkins, daughter of Jacob Dobkins (1751-1835).

William Fugate of Claiborne County signed a deposition in 1851 saying he came to Claiborne County, TN, in 1826. Claiborne County is rugged terrain, located on the south side of the Cumberland Gap, where Virginia, Tennessee, and Kentucky intersect.

In 1853, both William Fugate and Jehiel Fugate are neck-deep in lawsuits surrounding the estate of Jacob Dobkins, who died in 1835, lived on Powell River, and whose daughters married John Campbell and his brother George Campbell

I recently discovered that this William Fugate was born about 1799 in Russell County, VA, and according to his son’s death certificate, William’s wife was Nancy Riley, which makes a lot of sense, given the proximity of these families. I must admit, I’m glad to solve this, but I’m also disappointed that he wasn’t married to John Campbell’s sister.

So, why does any of this matter in the Blue Fugate story?

In part, because I knew decades ago that Martin Fugate, of the Kentucky Blue Fugates, was not an orphan from France who had somehow made his way to the eastern shores of Maryland, then to Perry County, KY by 1820 when he supposedly received a land grant. That land grant date doesn’t square with Martin’s birth year of 1820 either, nor his marriage about 1840, both of which are substantiated by the census.

You can see from the information gleaned from Russell County that the Fugate family was there well before 1800. In fact, a Martin Fugate is shown on the 1789 tax list and other Fugates were there earlier, as early as 1771, according to extracted Russell County records in the book “The Fugate Family of Russell County, Virginia” by David Faris. The Fugate descendants continued to press on westward from there. Fugate, unlike Smith, Cook, and even Campbell, is not a common surname.

“Orphan” stories are often early ways that people said “I don’t know”, without saying, “I don’t know where he came from”, so they speculated and said “maybe he was an orphan.” Then that speculation was eventually passed on as fact.

That might have been happening in Perry County in the 1960s, but in Claiborne County in the 1980s, family members were telling me, “Martin waren’t no orphan,” and would roll their eyes and sigh with great exasperation. You could tell this was far from the first time they had had to combat that story. To be clear, the Fugate family lived down along Little Sycamore Creek with my Estes, Campbell and other ancestral families. In the 1980s, I was finding the oldest people possible and talking to them.

Some records in Russell County, where the Fugates of Perry County, KY, and the Fugates of Claiborne County, TN, originated, did and do exist, so could have been researched in the 1960s, but you would have had to know where to look. No one back then knew that the Perry County Fugates originated in Russell County, so they wouldn’t have known to look there. Research wasn’t easy. If they had known to look in Russell County, they would have had to travel there in person to review records. Early records exist in Perry County, too, but in the 1960s, not even the census was available, and people simply didn’t remember back to the early to mid-1800s.

Truthfully, no one would ever have doubted those early stories that had been handed down. They were revered, in all families, and treated as gospel. Those stories were the only connection they had to their ancestors – and the generations inbetween who passed them on. Nope, no one was going to question what Grandpa or Uncle Joe said.

So, in the 1960s, when the Blue Fugates in Perry and adjacent Breathitt County, KY were first studied by Dr. Cawein and his nurse, Ruth Pendergrass, they gathered oral family history and constructed a family pedigree from that information. They documented who was blue from first-hand eye-witness accounts – which would only have stretched back into the late 1800s, best case.

It probably never occurred to anyone to validate or verify earlier information that was provided. Plus, it would have been considered rude. After all, they weren’t genealogists, and they were trying to solve a medical mystery. The information they collected did not conflict with what was known about the disease and how it was transmitted, so they had no reason to doubt its historical accuracy.

The Mystery of the Blue Fugates?

The Blue Fugates were a family renowned for their blue skin – at least some of them had blue skin. That’s part of what makes this story so interesting.

Originally, it was believed that only one progenitor couple was involved, Martin Fugate and his wife, Elizabeth Smith, but now we know there were two. Maybe I should say “at least two.”

Martin Fugate and his bride, Elizabeth Smith, whose first known child was born in 1841, according to the 1850 census, are progenitors of the Blue Fugate Family of Troublesome Creek, but they aren’t the only progenitors.

Martin was not shown in the Perry County, KY 1840 census, but two Zachariah Fugates are present, 8 Fugate families are found in neighboring Breathitt County, more than a dozen in Russell County and surrounding counties in Virginia, and four, including two William Fugates, in Claiborne County, TN. The younger of the two lived next door to John Dobkins, son of deceased Jacob Dobkins.

Martin Fugate (c1820-1899) of Perry County and his second cousin, Zachariah Fugate (1816-1864), who each married a Smith sister, are both progenitors of the Blue Fugates through their common ancestor, their great-grandfather, Martin Fugate, who was born in 1725 and died in 1803 in Russell County, VA.

Obviously, if Martin (c1820-1899) had a Fugate second cousin who also lived in Perry County, Martin wasn’t an orphan. That knowledge is due to more recently available information, like census and other data – and that’s part of what I want to correct.

In 1948, Luke Combs, from Perry County, KY, took his sick wife to the hospital, but Luke’s blueness caused the medical staff to focus on him instead, thinking he was experiencing a medical emergency. He wasn’t. His skin was just blue. In 1974, Dr Charles H. Behlen II said, ‘Luke was just as blue as Lake Louise on a cool summer day.’ The Blue Fugates were “discovered” by the rest of the world, thanks to Luke, but they were nothing new to local people, many of whom did not welcome the notoriety.

In the 1960s, hematologist Madison Cawein III, with the assistance of Ruth Pendergrass, studied 189 members of the extended Fugate family, treated their symptoms, and published his findings. He included a pedigree chart, but not everyone was keen on cooperating with Dr. Cawein’s research project.

The Fugate family history collected for the study was based on two things:

  • Personal knowledge of who respondents knew was blue
  • Remembered oral history beyond the reach of personal knowledge.

That remembered oral history reported that Martin Fugate and Elizabeth Smith’s youngest son, Zachariah Fugate (born in 1871), married his mother’s (older) sister, Mary Smith, (born about 1820), and had a family. I’ve added the dates and information in parentheses, or they would have immediately known that marriage was impossible. Or, more directly, even if they married when Zachariah was 14, Mary would have been 70 years old, and they were certainly not going to produce offspring. This is the second piece of information I want to correct. That marriage never happened, although people were accurate that:

  • Martin Fugate and his wife, Elizabeth Smith, did have a son named Zachariah Fugate
  • One Zachariah Fugate did marry Mary Smith, sister of Elizabeth Smith

It’s just that they were two different Zachariah Fugates, born 75 years apart. Same name confusion strikes again.

I constructed this census table of Martin Fugate with Elizabeth Smith, and Zachariah Fugate with Mary Smith. They lived next door to each other in Perry County – and it seemed that every family reused the same “honoring” names for their children – and had been doing such for generations.

In the 1960s, when the information was being compiled for Dr. Cawein, the census and other documents that genealogists rely on today were not readily available.

Furthermore, genetically, for the mystery Dr. Cawein was attempting to solve, it didn’t really matter, because it was still a Smith female marrying a Fugate male. I know that it made no difference today, but he wouldn’t have known that then. To track down the source of the blueness, he needed to identify who was blue and as much about their ancestors as possible.

The Zachariah Fugate (1816-1864) who married Elizabeth Smith’s sister, Mary Smith, was Martin Fugate’s second cousin by the same name, Zachariah. Both Martin (c1820-1899) and his second cousin, Zachariah (c1816-1864), married to Smith sisters, had blue children, which helps cement the fact that the responsible genes were passed down through BOTH the Fugate and Smith lines, and weren’t just random mutations or caused by environmental or other factors.

Proof

In case you’re wondering exactly how I confirmed that Martin and Zachariah did indeed marry Elizabeth and Mary Smith – their children’s birth and death records confirmed it. These records correlate with the census.

Unlike most states, Kentucky has some pre-1900 birth and death records.

Wilson Fugate’s birth in February, 1855 was recorded, naming both of his parents, Martin Fugate and Elizabeth Smith.

Martin Fugate and Elizabeth Smith’s son, Henley or Hendley, died in 1920, and his death certificate gave the names of both parents. Betty is a nickname for Elizabeth.

On the same page with Wilson Fugate’s birth, we find a birth for Zachariah Fugate and Mary Smith, too.

Hannah Fugate was born in December 1855.

Zachariah Fugate and Mary Smith’s son, Zachariah died in 1921, and his death certificate gives his parents as Zach Fugate and Polly Smith, a nickname for Mary.

There are more death records for children of both sets of parents.

Both couples, Martin Fugate and Elizabeth Smith, and Zachariah Fugate and Mary Smith, are progenitors of the Blue Fugate family.

Of Martin’s 10 known children, 4 were noticeably “blue” and lived long, healthy lives. At least two of Zachariah’s children were blue as well.

Some people reported that Martin, himself, had deep blue skin. If so, then both of his parents would have carried that genetic mutation and passed it to him.

Unfortunately, color photography didn’t exist when Martin (c1820-1899), lived, so we don’t know for sure. For Martin’s children to exhibit blue skin, they would have had to inherit a copy of the gene from both parents, so we know that Martin’s wife, Elizabeth, also inherited the mutation from one of her parents. Ditto for Zachariah Fugate and Mary Smith. The chances of two families who both carry such a rare mutation meeting AND having two of their family members marry are infinitesimally small.

Dr. Cawein’s Paper

In 1964, Dr. Cawein published his findings, but only with a pedigree chart with no names. What was included was an explanation about how remote and deep the hills and hollows were, and that out-migration was almost impossible, explaining the propensity to marry cousins.

Legend:

  • Measured – Found to have elevated methemoglobin
  • Measured – Found to have decreased methemoglobin
  • Not measured – Reported to be “blue”
  • Measured – Found to be normal

Cawein further stated that data was collected by interviewing family members who personally knew the individual in question and could say if they were actually blue.

Cawein erroneously reported that “Martin Fugate was an orphan born about 1800, landed in Maryland, obtained a land grant in Perry County, KY in 1820, and married a local gal. From 1820 to about 1930, the population consisted of small, isolated groups living in creek valleys and intermarriage was quite common.” Bless his heart.

Later, geneticist Ricky Lewis wrote about the Blue Fugates, sharing, among other things, the provenance of that “blue” family photo that circulates on the internet, revealing that it is a composite that was assembled and colorized back in 1982. She also erroneously stated that, “after extensive inbreeding in the isolated community—their son married his aunt, for example—a large pedigree of “blue people” of both sexes arose.” Bless her heart too.

Dr. Lewis is incorrect that their son married his aunt – but she’s right that intermarriage between the families is responsible for the blue descendants. In colonial America, and elsewhere, cousin marriages were fairly common – everyplace. You married who you saw and knew. You saw your family and neighbors, who were generally your extended family. No left-handed apology needed.

Pedigree collapse, sharing the same ancestors in multiple places in your tree, is quite common in genealogy, as is endogamy among isolated populations.

Today, things have changed somewhat. People move into and out of an area. The younger generation moves away a lot more and has for the past 100+ years. Most people know their first cousins, but you could easily meet a second or third cousin and never know you were related.

While early stories reported that Martin Fugate (c1820-1899) was an orphan from France, mysteriously appearing in Kentucky around 1820, later genealogical evidence as well as genetic research proves that Martin Fugate was actually born about 1820, in Russell County, VA and his ancestors, over several generations, had followed the typical migration path across Virginia into Kentucky.

We’ve also proven that Martin’s son, Zachariah (born 1871) was not the Zachariah who married Elizabeth Smith’s sister, Mary, who was 50 years old when Zachariah was born.

What else do we know about these families?

The Back Story

Compared to the Smith story, the Fugate story was “easy.”

Don’t laugh, but I spent several days compiling information and charting this in a way I could see and understand in one view.

I hesitate to share this, but I’m going to because it’s how I think. I also put together a very basic Fugate tree at Ancestry, here. Many children and siblings are missing. I was just trying to get this straight in my mind.

Click to enlarge any image

This spreadsheet is color-coded:

  • The text of each lineage has a specific color. For example, Fugates are blue.
  • Some people (or couples) are found in multiple descendants’ lines and are duplicated in the tree. Duplicated people also have a cell background color. For example, Mahala Richey (Ritchey, Ritchie) is highlighted yellow. James and Alexander Richey have green text and apricot background because they are duplicated.
  • The generation of parents who had blue children is marked with black boxes and the label “Blue Kids.”
  • Only the blue kids for this discussion are listed below those couples.
  • The bluest person was Luna Fugate (1886-1964).
  • While Luna’s husband, John Stacey, also descended from the Smith/Combs line, only one of their children expressed the blue trait. That child’s lips turned blue when they cried. John and Luna were actually related in three ways. Yes, my head hurts.
  • The last known “blue” person was Luna Fugate’s great-grandchild, whose name I’ve obfuscated.

Ok, let’s start with the blue Fugates on our spreadsheet. You’ll probably want to follow along on the chart.

Martin Fugate (1725-1803) and wife Sarah, had several children, but only two, the ones whose grandchildren married Smith sisters are known to have had blue children.

On our chart, you can see that Martin (1725-1803) is blue, and so is Son 1, William Fugate and Sarah Stephens, along with Son 2, Benjamin Fugate and Hannah Devers. Both William and Benjamin are mentioned in Martin’s estate in 1803 in Russell County, VA.

Two generations later, Martin Fugate (c1820-1899) and Elizabeth Smith had four blue children, and Zachariah Fugate (c1816-1864) and Mary Smith had at least two blue children. Furthermore, Zachariah Fugate’s sister, Hannah (1811-1877), married James Monroe Richie.

The Richey’s are green, and you can see them on both the left and right of the chart. Hannah’s husband descended from the same Richey line that Elizabeth Smith did. It was no surprise when their child, Mahala Ritchie (1854-1922), married Levi Fugate, to whom she was related three ways, they became the parents of a blue child. Their daughter, Luna Fugate, was known as “the Bluest of the Blue Fugates.”

Mahala Ritchie (1854-1922) could have inherited her blue gene (or genes) from either her mother Hannah Fugate, or her father, James Monroe Ritchie, or both. We don’t know if Hannah was blue or not.

We do know that Mahala married Levi Fugate, her third cousin through the Fugate line, and her third and fourth cousin also through the Richie and Grigsby lines, respectively. This is the perfect example of pedigree collapse.

You can see the purple Grigsby lines in the center and to the right of the pedigree chart too, with Benjamin Grigsby, highlighted in blue, being common to both lineages.

Zachariah Fugate (1816-1864) and Mary Smith had at least two blue sons, but I am not tracking them further. Suffice it to say that Blue John married Letha Smith, his first cousin, the granddaughter of Richard Smith and Nancy Elitia Combs. Lorenzo, “Blue Anze”, married a Fugate cousin, so it’s no surprise that Zachariah and Mary were also progenitor couples of the Blue Fugates.

Martin’s son, Levi Fugate, married Mahala Ritchie, mentioned above, and had Luna Fugate who would have been personally known to Dr. Cawein. Luna, pictured above, at left, was known as the bluest of the Blue Fugates.

Luna married John Stacey who some thought wasn’t related to Luna, so it was confusing why they had one child that was slightly blue. However, John turns out to be Luna’s second cousin, third cousin once removed and first cousin once removed through three different lines. His great-grandparents were Richard Smith and Nancy Combes. Since one of their children had a slight blue tinge, John, while not visibly blue himself, clearly carried the blue gene.

Where Did the Blue Gene Come From?

The parents of Elizabeth Smith and Mary Smith were Richard Smith and Nancy (Eletia) Combs. His Smith ancestors include both the Richeys and Caldwells.

James Richey (1724-1888) married Margaret Caldwell (1729-1802) and his father, Alexander Richey (1690-1749) married Jeanne Caldwell (1689-1785). While the Caldwell females weren’t closely related, Jeanne was the daughter of Joseph Alexander Caldwell (1657-1730) and Jane McGhie, and Margaret Caldwell (1729-1802) was the great-granddaughter of that couple. The Caldwells are shown in magenta, with both Richey/Caldwell couples shown as duplicates. The Richey are highlighted in apricot, and the Caldwell’s with a light grey background. It was difficult to show how these lines connect, so that’s at the very top of the pedigree chart.

When just viewing the Smith-Combs line, it’s easier to view in the Ancestry pedigree.

The Smith, Richey, Combs, Grigsby, and Caldwell lines are all repeated in different locations in the trees, such as with Hannah Fugate’s husband. These repeated ancestors make it almost impossible for us to determine where in the Smith ancestral tree that blue gene originated.

We don’t know which of these ancestral lines actually contributed the blue gene.

Can We Figure Out Where the Blue Gene Came From?

How could we potentially unravel this mystery?

We know for sure that the blue gene in the Fugate side actually descends from Martin Fugate who was born in 1725, or his wife, Sarah, whose surname is unknown, because their two great-grandchildren, Martin (c1820-1899) and Zachariah (1816-1864) who both married Smith sisters had blue children. For those two intervening generations between Martin Fugate (1725-1803) and those two great-grandsons, that blue gene was quietly being passed along, just waiting for a blue Fugate gene carrier to meet another blue gene carrier. They found them in the Smith sisters.

None of Martin (1725-1803) and Sarah’s other children were known to have had any blue children or descendants. So either they didn’t carry the blue gene, or they didn’t marry someone else who did – that we know of.

We can’t tell on the Smith side if the blue gene descends from the Smith, Richey, Grigsby or Caldwell ancestors, or maybe even an unknown ancestor.

How can we narrow this down?

If a Fugate in another geographic location married someone from one of these lineages, say Grigsby, for example, and they had blue offspring, and neither of them shared any of the other lineages, then we could narrow the blue gene in the Smith line to the Grigsby ancestor.

Unfortunately, in Perry and surrounding counties in Kentucky, that would be almost impossible due to intermarriage and pedigree collapse. Even if you “think you know” that there’s no connection through a third line, given the deep history and close proximity of the families, the possibility of unknown ancestry or an unexpected parent is always a possibility.

Discover

While the blue gene is not connected to either Y-DNA or mitochondrial DNA, we do have the Fugate’s Y-DNA haplogroup and the Smith sisters’ mitochondrial DNA.

Y-DNA

The Big Y-700 haplogroup for the Martin Fugate (c1820-1899) line is R-FTA50432, which you can see, here..

You can see the Blue Fugate Family by clicking on Notable Connections.

If you’re a male Fugate descendant who descends from anyone other than Martin Fugate (c1820-c1899), and you take a Big Y test, you may well discover a new haplogroup upstream of Martin (c1820-1899) that represents your common Fugate ancestor.

If you descend from Martin, you may find youself in either of the two haplogroups shown for Martin’s descendants, or you could split the line to form a new haplogroup.

We don’t have the mitochondrial DNA of Martin Fugate (c1820-1899), which would be the mitochondrial DNA of his mother, Nancy Noble. We also don’t have the the mtDNA of Mary (Polly) Wells, the mother of Zachariah Fugate (c1816-1864). If you descend from either of these women in a direct matrilineal line, through all women, please take a mitochondrial DNA test and reach out. FamilyTreeDNA will add it as a Notable Connection.

We do, however, have the mitochondrial DNA of Elizabeth and Mary Smith

Mitochondrial DNA of Elizabeth and Mary Smith

The mitochondrial DNA of both Elizabeth and Mary Smith follows their mother’s line – Nancy Combs through Nancy (Eletia?) Grigsby. Nancy’s mother is unknown, other than the possible first name of Margaret.

Nancy Grigsby’s descendant is haplogroup K1a61a1, which you can see here.

The Blue Fugates show under Notable Connections.

The Smith sisters’ haplogroup, K1a61a1, tells us immediately that their ancestor is European, eliminating other possibilities.

The time tree on Discover is quite interesting

Haplogroup K1a61a1 was formed about the year 1400. Descendants of this haplogroup are found in the UK, Scotland, England, several unknown locations, and one person who selected Native American, which is clearly in error. Haplogroup K is not Native American.

By focusing on the haplotype clusters, identified by the F numbers in the elongated ovals, our tester may be able to identify the mother of Nancy Grigsby, or upstream lineages that they can work back downstream to find someone who married Thomas Grigsby.

This story is far from over. In fact, a new chapter may just be beginning.

If you’re a Fugate, or a Fugate descendant, there’s still lots to learn, even if autosomal DNA is “challenging,” to say the least, thanks to pedigree collapse. Testing known females lineages can help us sort which lines are which, and reveal their hidden stories.

Other resources if you want to read more about the Fugates: The Blue People of Troublesome Creek, Fugates of Kentucky: Skin Bluer than Lake Louise, Those Old Kentucky Blues: An Interrupted Case Study, and Finding the Famous Paintings of the Blue People of Kentucky.

_____________________________________________________________

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

Discover’s Ancient Connections – How Are You Related?

Posted on by
Reply

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

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

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

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

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

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

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

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

Ok, are you ready for some fun???

Let’s find out how to leverage these tools.

Ancient Connections

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

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

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

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

Radegonde Lambert

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

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

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

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

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

Sign on and Identify Your Haplogroup

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

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

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

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

Click Through to Discover

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

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

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

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

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

The Classic Tree

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

Click on any image to enlarge

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

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

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

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

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

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

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

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

In descending order, for Radegonde, we have haplogroups:

  • X2b4
  • X2b4d’g
  • X2b4g

Your Match Page

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

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

I wrote about haplotype clusters, here.

Click on any image to enlarge

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

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

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

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

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

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

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

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

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

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

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

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

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

Radegonde’s Discover Haplogroup

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

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

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

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

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

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

Parent Haplogroups

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

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

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

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

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

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

Ancient Connections

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Ancient Connections Analysis Chart

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

Legend:

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

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

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

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

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

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

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

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

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

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

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

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

According to Discover, Haplogroup X2b4:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The Migration Map

The Migration map in Discover provides two different features.

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

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

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

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

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

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

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

Radegonde Lambert and Kennewick Man

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

Let’s work through our evaluation process using Discover.

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

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

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

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

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

One went east and one went west.

X2a became Native American and X2b became European.

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

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

Let’s Compare

Discover has a compare feature.

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

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

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

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

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

More Ancient Connections

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

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

Zlatý kůň Woman

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

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

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

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

Like all other Ancient Connections, it’s unlikely that I descend from Zlatý kůň Woman herself, but she is assuredly my very distant cousin.

What else do we know about Zlatý kůň Woman? Quoting from her Ancient Connection:

She lived during one of the coldest periods of the last ice age, surviving in harsh tundra conditions as part of a small hunter-gatherer group. She died as a young adult, though the cause of death remains unknown.

Her brain cavity was larger than that of modern humans in the comparative database, another trait showing Neanderthal affinity. While the exact colors of her features cannot be determined from available evidence, researchers created both a scientific grayscale model and a speculative version showing her with dark curly hair and brown eyes.

Zlatý kůň Woman may or may not have direct descendants today, but her haplogroup ancestors certainly do, and Radegonde Lambert is one of them, which means Radegonde’s matrilineal ancestors and descendants are too.

Ancient Connections for Genealogy

While Ancient Connections are fun, they are more than just amusing.

You are related through your direct matrilineal (mitochondrial) line to every one of your mtDNA Discover Ancient Connections. Everyone, males and females, can take a mitochondrial DNA test.

I find people to test for the mitochondrial DNA of each of my ancestral lines – like Radegonde Lambert, for example. I wrote about various methodologies to find your lineages, or people to test for them, in the article, Lineages Versus Ancestors – How to Find and Leverage Yours.

Radegonde’s mitochondrial DNA is the only key I have into her past, both recent and distant. It’s the only prayer I have of breaking through that brick wall, now or in the future.

Interpreted correctly, and with some luck, the closer Ancient Connections can provide genealogical insight into the origins of our ancestors. Not just one ancestor, but their entire lineage. While we will never know their names, we can learn about their cultural origins – whether they were Vikings, Phoenicians or perhaps early Irish buried in Passage Graves.

On a different line, an Ancient Connection burial with an exact haplogroup match was discovered beside the Roman road outside the European town where my ancestral line was believed to have been born.

Ancient Connections are one small glimpse into the pre-history of our genetic line. There are many pieces that are missing and will, in time, be filled in by ancient remains, Notable Connections, and present-day testers.

Check your matches and your Ancient Connections often. You never know when that magic piece of information you desperately need will appear.

What is waiting for you?

_____________________________________________________________

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

New Mitotree Haplogroups and How to Utilize Them for Genealogy

Posted on by
8

Have you received a new Mitotree haplogroup? Or maybe you didn’t? Are you wondering why you might not have received a new haplogroup? How do the new haplogroups work anyway? And how do you work with them?

Great questions!

Approximately 75% of full sequence testers received a new haplogroup with the Mitotree Beta release, which means that about 25% did not. Keep in mind that new sequences are being added to the database, so the tree will be sprouting new haplogroups with each subsequent release.

Check For Your New Haplogroup

Click on any image to enlarge

Sign in to your account at FamilyTreeDNA and look at the Badges in the bottom right corner of your page.

Your Beta haplogroup is your new Mitotree haplogroup, and your Legacy haplogroup is your old one – prior to Mitotree. They may be the same. My haplogroup, shown above, did not change.

This is a good place to note that the tree is not “done,” yet, nor will it ever be. New samples are added daily as more people test and as academic samples from published papers are added to the database as well. Additionally, FamilyTreeDNA is tweaking the algorithm, so the tree branching structure may change from time to time.

When your haplogroup changes, you’ll receive a notification email.

Some people’s haplogroup will remain the same. There can be several reasons why you might not have received a new haplogroup.

Before we discuss that, I’d like to stress that your haplogroup remaining the same isn’t exactly a bad thing because there is SO MUCH new content for everyone. It’s like receiving a whole new book about your mother’s direct matrilineal line.

mtDNA Discover Offers 13 New Reports for Everyone

MtDNA Discover was released with the new Mitotree, and it includes a dozen new reports for EVERY haplogroup.

Discover is available publicly, and also through your FamilyTreeDNA dashboard which provides a customized experience for mtFull testers with additional information that is not available in the free version.

Think of these Discover reports as chapters in your personal book – all about you and your matrilineal ancestors.

The Discover reports are provided in addition to the tools in the mtDNA Results and Tools section of your dashboard on FamilyTreeDNA.

There’s something for everyone, even if you don’t have a new haplogroup. There’s certainly new information that will help with your genealogy and with understanding the history and ancestral journey of your mother’s direct line maternal ancestors.

Three Reasons Why You Might Not Receive a New Haplogroup

Ok, so why might you not have received a new haplogroup?

The first reason that you might not have received a new haplogroup assignment is the simplest. The new tree is only updated periodically.

After your results are returned, and before the next Mitotree version is available, your Mitotree haplogroup Badge will show as “Analyzing.”

If one of your matches is waiting for a new haplogroup, their Mitotree Haplogroup will show as “Pending Analysis.”

There is no published tree-update schedule, but you’ll receive your new haplogroup soon.

However, you can probably determine your new haplogroup quite easily. If you have any exact matches on your mtDNA Match page, their haplogroup will be your haplogroup as well, so check your full sequence mtDNA Matches on your dashboard for a hint.

For, example, here’s one of my exact matches with their haplogroup.

The second reason you might not have a new haplogroup assignment is that you may not have taken the full sequence mitochondrial DNA test – mtFull.

Only testers with full sequence test results can receive an updated haplogroup, because the full mitochondria needs to be tested. The older HVR1/HVR2 Plus tests only tested a fraction of the full sequence – around 1000 locations of the 16,569 locations tested in the full sequence test.

If you have only taken the HVR1 or HVR1/HVR2 level test, you will only have one badge, and it will say “Predicted.”

The haplogroup for the Plus test is predicted at a high level based on those 1000 locations, while the full sequence test tests the entire mitochondria and uses all locations to confirm your most granular and detailed haplogroup possible.

On your dashboard, if both the Plus and Full icons are pink, you have taken the mtFull test. If the “Full” is grey, you have not. You can click on that grey button to upgrade.

You can also navigating to on Add Ons and Upgrades in the top bar to upgrade to the full sequence test.

The third reason why someone might not have received a new haplogroup assignment is if they didn’t match with anyone else who has the same mutations, or variants, for a particular haplogroup.

In other words, if my mitochondrial DNA has had a mutation or two since my assigned haplogroup was formed and no one else has tested that has those exact same mutations, there’s no one else to form a new haplogroup with, but there might be in the future as additional people test and the tree continues to grow.

Think of those additional mutations, called Private Variants, as foundation blocks, or haplogroup seeds since they are still private to you, and not yet used for a haplogroup.

It’s easy to see if you have any Private Variants by clicking on Discover on your mitochondrial dashboard.

Scientific Details – Private Variants, Building Blocks, Haplogroup Seeds

If you have taken the full sequence test, click through to mtDNA Discover from your dashboard. If you aren’t signed in and click through from your dashboard, you won’t be able to see your variants or other information customized for you.

Navigate to Scientific Details, then click on the Variants tab.

Click on image to enlarge

Be sure that “Show private variants” is toggled to “on,” which is blue with a checkmark.

At the very top, you’ll see two things:

  1. Your haplogroup, which is indicated by the solid pink square.
  2. An F number followed by your private variants, if any, and if so, which ones.

I have no private variants or haplogroup seeds available to form a new haplogroup, so I have no ability to receive a more refined haplogroup.

Haplotype Clusters

However, I’m NOT out of luck, because I have something else – a Haplotype Cluster, indicated by having an F#. My Haplotype Cluster is F1752176 and is indicated by the pink outlined box.

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

In a nutshell, haplogroups are only formed around reliable, relatively stable mutations, meaning those that are reliable and don’t tend to randomly mutate back and forth.

You may match exactly with a group of other people who share the same haplogroup, PLUS the same unstable mutations that don’t qualify to become haplogroup-defining.

Those groups of two or more people who match exactly on all mutations are members of the same  Haplotype Cluster – and Haplotype Clusters can be INCREDIBLY genealogically useful. In fact, let me go out on a limb here and say that I think they are even more genealogical useful than haplogroups, although both have their strengths. Let’s look at a good example.

Using Haplogroups and Haplotype Clusters Together

My family member, Jim, had a surprise waiting for him in his mitochondrial DNA. When he received his new haplogroup, I took a look to see what new information might be forthcoming.

His legacy haplogroup was V, and his new Mitotree haplogroup is V216a2 which is significantly more refined.

Before Mitotree and Haplotype Clusters, there wasn’t much to differentiate him from his other matches.

Let’s take a look at JUST his genetic information before adding genealogy.

If I click on the Time Tree for haplogroup V216a2, I see two testers with no cluster, meaning no one matches them exactly, and Jim’s cluster number F9712482.

Keep in mind that Jim might not match everyone in his haplogroup – only people at or beneath the matching threshold.

Jim’s new haplogroup, V216a2 was formed about 1056 CE, or about 975 years ago. Note that as the tree changes and becomes more refined, haplogroup formation dates change too. A haplogroup’s birth date is an approximate year when the mutations occurred that define that haplogroup, based on surrounding mutations and mutation rates.

Many people look at a haplogroup, especially one with a birth date of, say, 1056 CE, which is long before the formation of surnames, shrug their shoulders, and give up.

Don’t. Do. That.

So, let me say this as loudly as possible.

A haplogroup’s most recent common ancestor is NOT the EKA (earliest known ancestor) with any individual match. It’s the approximate date when ALL of the people with this haplogroup share a common ancestor.

When looking at haplogroups, don’t let locations thrown you. Keep in mind that country boundaries are fluid. What was at one time Hungary could be Germany or Romania or something else just a few years earlier or later. So don’t discount that information either. Think regions and take into consideration that people move around – and some people enter incorrect genealogy/location information.

Your common ancestor with the people, individually, who share your haplogroup,  is sometime between the haplogroup formation date and today. Everything else is a clue. 

Think about it this way. You share a haplogroup with your mother, and while you are both descended from the woman who lived when your haplogroup was formed – your most recent ancestor with that haplogroup is your mother – not the woman 975 years ago. Your most recent common ancestor (MRCA) with your mother and her sister is your grandmother – a lot closer in time than 1056 CE. 1056 CE the most recent common ancestor (MRCA) date for everyone in the haplogroup, not between you and any one person in particular. The MRCA date for you plus another person is sometime between now and 1056 CE.

So, let’s take a look at Jim’s results.

Finding Jim’s Gold Nugget

Jim has 27 coding region matches, of which six share both his new haplogroup, V216a2, AND Haplotype Cluster F9712482. His other matches are split between three related haplogroups, and multiple haplotype clusters.

Most of his family, meaning three of his grandparents, were from eastern Europe, meaning Germany, Hungary or the Austro-Hungarian empire as it was recorded in American records. Many genealogical records no longer exist in that region, or if they do, you have to know exactly where to look.

We were brick-walled with Jim’s matrilineal great-grandmother, Sophia Smith, who was born about 1877 and seemed to appear out of thin air.

Thanks to the new haplogroups, combined with Haplogroup Clusters, I knew to focus on his matches in this order:

  • Same haplogroup plus same Haplotype Cluster
  • Same haplogroup plus different Haplotype Cluster, because clusters are built around identical but less reliable mutations
  • Related haplogroup – this is unlikely to yield direct genealogical results, but can be very useful in terms of origins

Of Jim’s exact matches with the same Haplotype Cluster, three showed an earliest known ancestor (EKA) and three did not. Three provided a tree, and three did not. Of the trees, one was private and the other two provided no useful insight.

Of the people who provided EKA information, one EKA matches their tree information, one conflicts with their tree. After viewing their tree, it appears that they did not understand that the mitochondrial EKA is the most distant ancestor in your mother’s direct maternal line. They listed someone in their grandmother’s paternal line.

I find this easiest to deal with if I organize the research in a chart for each match.

Match # Earliest Known Ancestor EKA Location Tree Comment
#1 No No No
#2 No No No
#3 No No Yes – Private
#4 Yes – only one name “Egan” with brith and death dates Ireland Yes – Egan is surname of their grandmother EKA person listed tracks up wrong line in tree
#5 Yes Hungary No Elizabeth Schmidt Hornung b1888 d 1930
#6 Yes No Yes – matches EKA Ancestor born NC in 1811, no common names or location

Match #5 provided an EKA, but no tree, showed a country of origin as Hungary, and the identity of her EKA as “Elizabeth Schmidt Hornung b.1888 and d.1930.”

Hmmm…three things of interest here:

  • The location of Hungary, even though the oral history in Jim’s family said his great-grandmother was a Smith from the US, maybe New York. Jim’s family, including Sophia’s husband, was Eastern European. Remember, I couldn’t find any early records for Sophia Smith.
  • Smith is the anglicized version of Schmidt.
  • Hornung may be a married name.

I’m a genealogist, and Jim’s match had provided enough information that I was able to identify her ancestor, Elizabeth Schmidt, and find additional information.

Sure enough, Elizabeth Schmidt immigrated as an adult by herself, married Karl Hornung in Richland County, Ohio, the same location where Jim’s family was living. That information led me to another record, identifying a brother whose marriage license application provided their parents. Elizabeth’s parents were Ignatius Schmidt and Catherine Schlowe, and her sister was Sophia Schmidt, Jim’s great-grandmother. Deeper digging suggests that Ignatius and Catherine were from Timisoara in what is now Romania. I have been unable to confirm with birth, death or marriage records, but that part of Romania was part of the Austro-Hungarian Empire during that timeframe.

Immigration of siblings, alone, at different times after the 1910 census, without their parents, made this particularly difficult, as did cultural and language barriers – but mitochondrial DNA, and Jim’s Haplotype Cluster in particular, provided the key I needed.

Jim’s common ancestor with his Schmidt match is the birth date of Catherine Schlowe, which was probably about 1850 – NOT 1056 CE, which is the haplogroup formation date.

Don’t get discouraged by misinterpreting haplogroup origin information or missing genealogy information. All you need is that one good match. That gold nugget. Don’t forget that you can email your matches and ask for more information.

The Match Time Tree makes all of this easier.

Match Time Tree

The Match Time Tree shows match, haplogroup, location and Haplotype Cluster information all in one place.

It’s easy to use the Match Time Tree to view how all of your matches are grouped, along with their EKA, displayed together in one place.

Here are all of Jim’s matches. They were all originally haplogroup V, but now his matches have been divided into V216, V216a, V216a1, and V216a2 (Jim’s haplogroup).

I’ve obfuscated the names of his matches, but the EKA, when provided, is there. Each person is grouped into their haplotype cluster of exact matches, and the user-provided country of origin for their ancestor is shown by their profile photo.

Jim’s match with the descendant of Elizabeth Schmidt is indicated in the red boxes, and Jim has updated his own EKA and her country of origin.

Who is waiting for you in your match list?

Will extending and building out trees help?

Have you emailed your matches to see what additional information they can provide?

Female ancestors are sometimes the MOST difficult to find, often due to name changes  – so be sure to mine every possible avenue and don’t become discouraged if you don’t immediately see something “familiar.”

Every generation in a female lineage will probably carry a different surname and the match you need may not have researched as far back as your ancestor, or vice versa.

Don’t forget that autosomal matching can play an important role in confirming relationships.

But wait – there’s STILL more about Jim’s ancestors…

There’s Even More to Discover

There’s more to discover about Jim’s ancestors.

Jim’s Discover Ancient Connections tells me that 5200 years ago, Jim shared a common mitochondrial DNA ancestor with two Hungarian and a Slovakian Yamnaya cultural burial whose remains date to about 2800 BCE, or about 4800 years ago.

To be clear, the common haplogroup between Jim and all three burials dates to 5200 years ago, when their common haplogroup was formed, but the remains themselves are from about 4800 years ago – so only about 400 years difference between the haplogroup birth date and when those people lived, died and were buried.

How close are the remains to the location of Jim’s ancestor in Timisoara?

Using Google Maps, I placed the three Yamnaya burial locations (blue pins), plus Timisoara.

The two most distant points, Timisoara to Lesne, Slovakia, walking, is 393 km or 245 miles. The closest burial to Timisoara, located in Sárrétudvari, Hungary, is 157 km  or 119 miles.

So Jim’s ancestors remained in the same general area for someplace between 4,800 and 5,200 years. And, his great-grandmother was born not far from those burials. That alone is an INCREDIBLE find!

So, what happened to the people of the Yamnaya culture? I think we might have gained some insight into that question.

So, there’s even more to discover using Discover.

You don’t know what you don’t know about your matrilineal ancestors, so test your mitochondrial DNA at FamilyTreeDNA and break through those brick walls. I’ve already solved multiple long-standing mysteries and added generations to my own tree.

Plus, I really, REALLY want to know where every single ancestor “came from,” what culture they were a part of, and when. History is part of genealogy – and a part of our ancestral journey that we can’t reach any other way.

Fortunately, your matches, Scientific Details, Time Tree, Match Time Tree, and Ancient Connections help you visualize all of these various situations and aspects of your ancestor’s history, and evaluate your results.

Both haplogroups and Haplotype Clusters provide very fine degrees of granularity that were not previously available. MtDNA Discover adds a dozen new reports, and Ancient Connections allow you to time travel.

Let me know what you discover!

_____________________________________________________________

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

New “Share” Features at FamilyTreeDNA Blur Match Information and Make Sharing Easy

Posted on by
Reply

Have you ever wished you didn’t have to blur or otherwise redact each name and other sensitive information in order to share your DNA match results? Or maybe you’d like to share fun Discover pages? Well, you got your wish!

FamilyTreeDNA has introduced a new “Share” feature in two locations. The first Share feature is available in your personal account after signing in, and two additional features can be found in Discover.

  1. “Share Mode” on your personal page obfuscates the names and photos of your matches.
  2. “Share Mode” in Discover obfuscates the names and photos of your matches on your Match Time Tree.
  3. “Share Page” in Discover shares publicly available pages to social media or provides a sharing link for you.

These are extremely easy to use and help immensely, allowing you to share screenshots on social media and with family without revealing the names of your matches.

I’ll show you, step-by-step, how to use all three.

“Share Mode” in Your Personal Account

When you want to enable Share Mode, you just toggle it on.

Sign in to your account at FamilyTreeDNA.

Select Account Settings beneath your name in the upper right-hand corner.

Under Privacy and Sharing, toggle Share Mode to “ON.” Default is “OFF.”

Sharing turns itself back off each time you sign out, so you’ll need to do this each time you sign on and want to share.

To see the results, let’s take a look at my match page. Sharing works the same way for Y-DNA matching, mitochondrial or Family Finder.

Not only does Share obfuscate your matches’ names, it also blurs their picture, and your information as well, at upper right.

This is wonderful for presenters!

Using “Share Mode” in Discover

On your dashboard, for either Y-DNA or mitochondrial DNA, select “Discover Haplogroup Reports” in the appropriate section.

Discover has two ways to share.

You can share your Match Time Tree, or other pages – using different tools.

Only one Discover page, the Match Time Tree, contains potentially sensitive match information. There’s a “Share Mode” for the Match Time Tree that blurs private information.

However, you may want to share your other Discover reports on social media. “Share Page” provides a quick and easy way to share any publicly available page.

Let’s look at both of those options.

Discover “Share Page”

Every page in Discover, except for the Match Time Tree and Globetrekker, has a “Share Page” icon at the top.

You can share any Discover page on social media (except as noted below), whether you’ve clicked through to Discover from your dashboard, or you’re using the public version of Discover.

In this case, I clicked on “Share Page” to share my Haplogroup Story page to Facebook. On your social media platform of choice, or by sharing the link, your friends can click through to see the page you’ve shared – minus your name and photo.

Please note that there are four Discover pages that either do not share or will display reduced information when using “Share Page,” as follows:

  • Globetrekker is an amazing animated video of your ancestors’ trek across the planet which is reserved for FamilyTreeDNA clients who purchase the Big-Y test or the mtFull, full sequence mitochondrial DNA test. Globetrekker does not use the “Share Page” feature, and is not yet released for mtDNA Discover.
  • Ancient Connections uses the “Share Page” feature, but only publicly displays a few ancient DNA haplogroup matches. Several more are reserved for testers who have taken either the Big-Y or mitochondrial DNA full sequence test, and click through from their dashboard. In a kit I just checked, two or three displayed when shared publicly, but the tester had more than 20 when clicking through his dashboard.
  • Notable Connections uses the “Share Page” feature and functions like Ancient Connections.
  • The Match Time Tree does not use the “Share Page” feature, which populates to social media, but there is a “Share Mode” option which blurs your matches’ sensitive information, similar to your personal page. After blurring, you can take screen shots to share.

Discover Share Mode for the Match Time Tree

The Match Time Tree on Discover is an extension of matching – meaning that your matches are placed on the Time Tree with names of tester-provided Earliest Known Ancestors (EKA) and their country of origin listed.

To view your Match Time Tree, click through to Discover from your FamilyTreeDNA dashboard, then select “Match Time Tree.”

You need to enable “Share Mode” within Discover, even if you had it enabled on your personal page. Toggle “Share Mode” to ON at the top of your Match Time Tree page.

Enabling “Share Mode” obfuscates the names and photos of people on your match list, who now appear on your Discover Time Tree in their proper place. You’re there too!

To share this page publicly, you’ll need to take a screenshot – so please don’t forget to enable “Share Mode” within Discover before doing this.

Benefits of Sharing

The best thing we can do for DNA testing, speaking broadly, is to encourage additional testers who are excited about what they can discover.

Sharing our pages and discoveries on social media is a great way to generate excitement.

Who do you know that might be excited to discover that they share an ancestor with Leo Tolstoy or maybe “Wild Bill” Hickock, even if it’s hundreds of years ago?

How about discovering that an Ancient Connection is a Viking man who was buried in Shestovista, Ukraine about a thousand years ago, and you two shared an ancestor about 1900 years ago? Might that provide a clue about your genealogy? What was the life of your ancestor like?

Or, maybe your friends and relatives would be excited to view the path their ancestors took, marching across the map, until their ancestor arrives on the globe where their haplogroup is most recently anchored?

Trying to get Uncle John or Aunt Mary to test? What kind of information would they think is cool?

A scientist I know especially loves the Ancient Connections that extend far beyond the reach of surnames.

One of my ancestral lines has an ancient DNA match just 9 kilometers from the town where they are rumored to have originated in France. Along the ancient Roman road. How else would I have EVER made this discovery?

The more people that test, the larger the matching pool – and the better for all genealogists.

Thank you to FamilyTreeDNA for introducing “Share Mode,” which makes sharing matches with other researchers effortless, and for “Share Page” within Discover, which makes sharing publicly a breeze!

Who can you share and collaborate with?

______________________________________________________________

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. Just look for the black “follow” button on the right-hand side on 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.

_____________________________________________________________

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

RootsTech 2025 – The Year of Discover and the New Mitotree

Posted on by
3

Last week, RootsTech was a whirlwind and full of discoveries – which, ironically, was the 2025 theme.

I always take you along with me and share the RootsTech experience, start to finish, so here’s my 2025 “feet on the ground” report.

I might, just might, have overcommitted myself. I taught the half-day DNA Academy,  three more sessions, plus several other commitments such as book signings, get-togethers, and interviews.

One class, “DNA for Native American Genealogy,” was a live webinar from the floor of the expo hall. You can watch that here for free, if you’re interested.

Unfortunately, none of my other sessions were recorded, but I’ll see what other alternative options may be available to bring those to you.

Additionally, I did two book signings at the GenealogyBank booth, along with two other authors, Drew Smith and Sunny Morton. I’m sorry, I don’t have any pictures. I should have asked someone to take some.

There were long lines and books sold out. Still, you can order either of my books, The Complete Guide to FamilyTreeDNA – Y-DNA, Mitochondrial, Autosomal and X-DNA or DNA for Native American Genealogy, at Genealogical.com. Thank you to GenealogyBank for being so welcoming.

The book signing was particularly fun because people shared their success stories or their hopes of what they want to achieve. I met a couple of new cousins too! Even people waiting in line were helping each other with information about research resources.

I had created my “RootsTech plan” for sessions I wanted to attend, but I was only able to actually attend one of those. Several were happening at the same time as mine, or directly before or after. As a presenter, you arrive early to get set up and make sure everything is working correctly.

Then, after your session, attendees have questions and are interested in your topic, which is a good thing. So essentially, you can’t attend sessions either before or after your session either.

Before I share photos, I’d like to share something else.

It’s About the People

I have never attended RootsTech for the classes, although there are wonderful offerings – and I have enjoyed them immensely.

Having said that, for me, the best part of RootsTech is the people. People I know and love but never get to see – many of whom I met in-person at RootsTech initially. I get to meet my blog followers. I meet with or reconnect with friends and cousins from around the world. I am privileged to talk with people about their challenges and their victories – when they’ve broken through a brick wall using DNA that they could never have otherwise achieved. People collaborating and helping each other. It’s all beautiful.

The reason I started blogging in the first place, and the reason all 1750 articles are free, is because I wanted to help people do just that – confirm ancestors, find ancestors, and connect with their fsmily.

My cousins that I’ve met through genealogy are some of my closest friends and closest family members. Outliving everyone is a mixed blessing but it makes me extremely grateful for my various cousins since all of my siblings and close family, with the exception of the next generation, have transitioned to the land of the ancestors.

So, yea, for me, RootsTech is about connecting and reconnecting with the people.

That’s also why I never get anything done because I’m always talking with someone.

Additionally, this particular RootsTech was a celebration.

Mitotree Release

Just a few days before RootsTech, the Million Mito Team at FamilyTreeDNA released the brand new Mitotree, 5 years in the making, reconstructing the tree of humankind to reflect our combined heritage more accurately.

At RootsTech 2020, I was honored to announce the Million Mito Project, and the new Mitotree initiative was born.

At some point, I will write about the deep, personal significance of the Mitotree for me,  but for now, suffice it to say that there is something profoundly moving about rewriting the tree of humankind and in doing so, giving a voice to our ancestors from long ago. Yes, I know many of them are thousands or even tens of thousands of years old, but had they not survived, we would not be here today. Now we can identify who they are and that they lived.

Million Mito Team, left to right, Goran Runfeldt, Dr. Paul Maier, me, Dr. Miguel Vilar, Bennett Greenspan, John Detsikas

Our amazing Dream Team has given life to our ancestors and said their names once again, even if their name is a mitochondrial DNA haplogroup. Four team members, Goran, Paul, me and Bennett were at RootsTech. Where else can you actually approach and speak with the actual scientists?

When I say RootsTech is about the people, I know that I am related to every single individual at RootsTech, it’s just a matter of how far back in time. So are you.

Just think about the significance of that for a minute.

Every. Single. Person.

The other end of the mitochondrial DNA spectrum is genealogy, of course, and the new Mitotree with it’s haplotype clusters brings mitochondrial DNA results into the genealogical timeframe. In future articles, I’ll be writing about each one of the new tools, what they mean, and how to use them.

Dr. Paul Maier, lead scientist doing most of the hard science behind Mitotree, had the much-deserved honor of introducing the Mitotree to genealogists at RootsTech.

I’m not sure the audience understood they were witnessing history unfold, but they clearly were. We needed a drum roll and some balloons!

This wasn’t like most vendor announcements of a new product or feature – this was a major scientific achievement that led to genealogical benefits.

In celebration, I asked my friend to make double helix zipper pulls so that I could give them to colleagues, friends and cousins that I ran into at RootsTech. It’s my way of celebrating and sharing the joy!

Five years is a very long time to work on a project. The Mitotree is a massive accomplishment. Every customer at FamilyTreeDNA who has taken the full sequence test received their new haplogroup either the week before or during RootsTech, AND, the second updated version of the tree was released too.

While this is truly wonderful, the true highlight is the testimonials – seeing how Mitotree is actually helping people break through their brick walls.

Here’s just one.

Breathless Testimonial

I’m going to try to convey this exactly as it happened.

A lady that I don’t know literally runs up to me in the hallway. This isn’t unusual. She was so excited that what she said was one long breathless sentence, which I’m going to try to reconstruct here, although I’m adding a bit of punctuation. I also can’t remember how many “greats” were attached to the “grandmother,” but you’ll get the idea.

Roberta, Roberta, I’m so excited – I just wanted to let you know – I found my ancestor using mitochondrial DNA. I got my new haplogroup and I had like 47 matches before but now they are clustered together so I could focus…and there were three matches in my cluster…and one of them had an EKA but the other didn’t…so I built out the EKA matches’ tree and guess what??? They were from the same place and then I found that her great-great-grandmother’s sister is my great-great-grandmother but she had her surname so now I have more generations too. OMG I ‘m so excited I could never have broken through this wall without mtDNA because I had no surname. This is THE MOST CONSEQUENTIAL DNA TEST I’VE EVER TAKEN, and I’ve taken them all. Thank you, thank you!

And with that she quickly hugged me and ran off to something she was obviously late for.

I never got to say one word, which was fine, but I stood there with tears in my eyes, thinking to myself, “This – this is what it’s all about.”

It doesn’t get better than this!

I want to hear your stories too. I just scaled my fourth brick wall last night using the new Mitotree and mtDNA Discover features.

RootsTech Week

RootsTech week started early for me – as in leaving the house at 3 AM Sunday. I fly on Sunday because the flights are cheaper and because the pre-conference meetings and events begin on Monday.

We took off into the dawn, jetting our way westward through the azure blue sky.

I have never gotten over the majesty and beauty of the Rocky Mountains.

And then, of course, the Great Salt Lake, for which Salt Lake City is named.

Looking at the Salt Palace across the street from the Marriott hotel. The silver building is the new Hyatt which is attached to the conference center behind the windmills which extends another very long block to the right, out of view. The mountain range is visible in the distance, and the beautiful sunset.

Speaking of the Marriott hotel, several people have asked if it was any better this year, and if I got trapped in the fire exit again, like last year.

No, I didn’t get stuck because I didn’t tempt fate again. It looked just the same though, so I’m presuming nothing has changed. Furthermore, there was no heat in my room, so they gave me a space heater and a pass to the concierge level – which they did not do last year.

That was kind of them, but food ran out, and there was only one poor server in the restaurant. I’m not even going to mention the nauseating thing that happened with my food. Let’s just say I’m not picky, but I will NEVER eat there again, and that makes it particularly difficult because there’s very little close by, especially when you’re exhausted.

I’m hoping that RootsTech will negotiate someplace different for speakers in the future. I’ve stayed in a lot of Marriotts and most of them are just fine. I have never had issues like this with any of them, let alone repeat issues year after year.

The good news is that we’re not there for the hotel, and the fun began on Monday.

Monday

My interviews began on Monday morning with “Mondays with Myrt” at the FamilySearch Library, which you can view here beginning about 16 minutes.

Mondays with Myrt is a RootsTech tradition and Myrt incorporates people present in person and tuning in virtually as well. Left to right, Kirsty Gray from England, John Tracy Cunningham, me and Myrt. Kirsty had a huge breakthrough that she shared with us just a few minutes after it happened.

I met John at the ECGGS Conference last October. He’s one of the few people I know whose 8 great-grandparents were born in the same county. I’m so jealous. Mine were either born in or first generation immigrants from four countries.

Sometimes the broadcast waiting area is just as much fun as the actual broadcast – in part because it’s the first day of RootsTech week and everyone is so excited to see their friends that they haven’t seen in forever. Call is a reunion!

Do Kirsty Gray and I look like we’re about to get into mischief?

Behind me is the first group of folks to be interviewed.

Pat Richley-Erickson, aka Myrt, Cheryl Hudson Passey, Laura Wilkinson Hedgecock, and Jenny Horner Hawran.

This is the livestream room at the FamilySearch Library. The waiting area for the next group is to the right, and the three presently being interviewed are sitting on the left beside Myrt.

For those who know Gordon, aka Mr. Myrt, he’s coordinating interviewees outside the livestream room. His job is herding cats and he’s the nicest cat-herder you’ll ever meet!

Pre-RootsTech Library Research

I love the FamilySearch Library. It feels like coming home to me.

So many passionate genealogists at every level – learning and searching. Lots of volunteer helpers available, too.

Normally, I create a research plan for the library, but I had been so utterly slammed between preparing my several RootsTech sessions and the Mitotree release that I hadn’t really been able to prepare anything.

I did, however, have a group of ancestors in mind that settled in the Oley Valley in Pennsylvania, so I decided to focus on the Berks County books.

I won’t bore you with the details, but among other things, I found confirmation that the Hoch surname is also the same as High and Hoy, which explains some very confusing Y-DNA results. So even though I didn’t get much productive time there, I did find something very useful in the land records.

I also ran into cousins and friends, of course, which is why I didn’t get more actual research done.

I knew Judy Nimer Muhn, at left, was going to be at RootsTech as a speaker, and I knew we connected through Acadian lines, but we never took the time to really piece together that puzzle.

My cousins, Mark and Manny were also coming for RootsTech, and to visit the library, for the first time. Mark, Manny and I visited Nova Scotia together in the summer of 2024, chasing our ancestors.

You know, fate is a funny thing.

We all descend from Acadian, Francois Savoie who was born about 1621 in France, but settled in Acadia, today’s Nova Scotia. Mark, Manny and I knew that we are cousins through Francois, but Judy and I did not. Mark, Manny and I ran into a local historian, Charlie Thibodeau, the Acadian Peasant, last year, outside of Port Royal. It just so happened that he was taking another couple to see the remains of the Savoie homestead deep in the salt marshes at BelleIsle.

We asked if we could join them, and Charlie was kind enough to include us. It was a long, brutally hot, tick-infested hike through the swamp, but oh so worth it!

We also found the well, located between three homesteads.

The year before, Judy had been in the same place in Nova Scotia, found the same man, Charlie, at the BelleIsle Hall Acadian Cultural Centre, and he had taken her to the remains of the same homestead.

And here we all four are in Utah.

What are the chances?

Needless to say, we had a LOT to talk about, and still do. Unfortunately, I wasn’t able to get to Judy’s talk, but Mark and Manny attended.

I ran into Katy Rowe-Schurwanz, the FamilyTreeDNA Product Manager at the library too, and look what she’s wearing – a mitochondrial DNA scarf. How cool is that!

The rest of Tuesday and most of Wednesday morning were spent trying to update my several presentations to reflect newly released information by various vendors and practicing the timing of the presentations. I had another interview, and more people were arriving.

I found time to visit Eva’s Bakery about 3 blocks from the Salt Palace. If you’re ever in Salt Lake City, Eva’s is a must! Lunch is wonderful, and so are their French pastries.

Wednesday is “tech prep” day at RootsTech, along with speaker instructions and then the Speaker Dinner.

Steve Rockwood, President and CEO of FamilySearch always delivers an inspirational message and this year did not disappoint.

If you’ve wondered about RootsTech conference stats, they provided this information. I can’t even imagine trying to coordinate all of this – and that’s not including the vendors, expo hall, technology in the presentation rooms, food, security and so much more.

Last year, in 2024, the final attendance numbers were more than 16,000 people in person and 4 million virtual attendees. I noticed a few days ago that there were more than half a million people participating in Relatives at RootsTech, which is still live until April 12th.

On Wednesday evening, after the Speaker’s Dinner, vendors in the Expo Hall were putting the final touches on their booths and preparing for the thousands of excited genealogists who would descend Thursday morning.

Discover

This year’s RootsTech theme was “discover” and attendees were greeted with this display just inside the door.

Attendees listed their discoveries on Post-its and could either post them on the board or plastic boxes, or on the green tree.

I placed my discovery from the day before at the library on the Rootstech tree.

Some people place their wishes here, kind of like a technology wishing well.

I couldn’t help but think of the new Mitotree, now forever green and growing, so I posted a second discovery, “Mitotree.”

Thursday – Opening Day

For those who don’t know, the Salt Palace Convention Center is two lengthy blocks long, a block wide, and two or three stories high, depending on whether you are in the front or rear portion. In other words, it’s massive and you need a map!

The huge Expo Hall with vendors is located in the center on the first floor and vendors have aisle addresses. The show floor is always very busy, and this year was no exception. One of the things I love is that spontaneous conversations just spring up between people who often find commonalities – common ancestors, common locations, and more. People compliment each other and join others at tables. It’s like a big family gathering of sorts.

I always try to walk the entire Expo Hall, because I really enjoy seeing the vendors and their wares, but this year, I never actually had enough time to traverse all the aisles. I took several pictures as I was passing through and running into people, but not nearly enough. I know I missed a lot, but there just wasn’t enough time and I arrived at RootsTech already tired.

However, the energy of RootsTech is like no place else and just infects you.

It’s like you can’t drink from the genealogy firehose fast enough!

Let’s Take a Walk

Ok, come along on a walk with me.

Left to right, Lianne Kruger, a speaker, and Courtney, in the FamilyTreeDNA booth. I believe they said they are cousins.

Daniel Horowitz, genealogist extraordinaire, in the MyHeritage booth. More about MyHeritage’s announcements shortly.

Geoff Rasmussen in the Legacy Family Tree Webinars booth. For those who don’t know, there’s lots of good material at Legacy, and the freshly recorded webinars are always free for a week.

Several vendors offer booth talks, including MyHeritage. I love their photo tools and use their site in some capacity almost daily.

One of the RootsTech traditions is ribbons. Collect one, collect ‘em all. Liv’s ribbons almost reach the floor. I think she wins!

Selfies are also a RootsTech tradition. Me, here with Jonny Perl of DNAPainter fame. I owe Jonny an apology as he asked me if I had a minute, and I had to say no because I was on the way to one of my own classes. I never got back to his booth to view his new features. Sorry Jonny – don’t take it personally!

Jonny released a new Ancestral tree version titled Places, so take a look here at his blog. I need to go look at my ancestors Places.

You’ll find this new feature under Ancestral Trees, Places. These are my most recent 8 generations. Just think of all those brave souls who climbed on a ship and sailed for the unknown. Check this feature out and have fun.

In a booth talk, Dave Vance, Executive Vice-President and General Manager at FamilyTreeDNA is speaking about the three types of DNA, which are, of course, Y-DNA, mitochondrial and autosomal DNA – all useful for genealogy in different ways.

Dave is explaining how in-common-with matches, also known as shared matches, operate with the chromosome browser. You can use the chromosome browser, shared matches, the new Matrix Tool, and download your match segment information at FamilyTreeDNA, a combination of features not available at any other vendor.

WikiTree, a free a moderated one-world-tree is one of my favorite genealogy tools. One of their best features is that you find your ancestor, and in addition to lots of sources, their Y-DNA, mitochondrial DNA, and those who are related autosomally are listed. Here’s my grandfather, for example.

Several DNA connections are listed. The further back in my tree, the more DNA connections are found, becuase those ancestors have more descendants.

WikiTree volunteers were wandering around taking pictures of “WikiTreers” holding fun signs.

Paul Woodbury, a long time researcher with Legacy Tree Genealogists, who specializes in DNA. I don’t take private clients anymore, and regularly refer people to Legacy Tree.

Me with Janine Cloud taking our annual RootsTech selfie. Janine, the Group Projects Manager at FamilyTreeDNA and I co-administer one of those projects and accidentally discovered a few years ago that we are cousins too. How fun is this!!!

I wanted this shirt, but by the time I got back to the booth, it was too late. I’m going to order it online from Carlisle Creations, in case you want one too. This is so me.

Land records are critically important to genealogists. Rebecca Whitman’s class was about plotting land plats. What she’s holding is a surveyor’s chain. You’ve read about chain carriers? This is what they carried to measure land boundaries – literally metes and bounds. Some of my best discoveries have been thanks to land records.

The only session I actually got to attend was Gilad Japhet’s “What’s New and Exciting at MyHeritage.” For those who don’t know, Gilad is the founder and CEO of MyHeritage and it’s always great to hear about the new features straight from the top executive who is, himself, a seasoned genealogist. That’s why he started MyHeritage in the first place – 22 years ago in his living room.

Gilad had several wonderful announcements, but the one I’m most excited about is their new Cousin Finder. Cousin Finder finds and reveals cousins who are DNA candidates if they have not yet taken a DNA test.

I’ll be writing more about the MyHeritage announcements soon, but you can read their blog about Cousin Finder now, here, and their Roundup here about the rest of their announcements!

My Last Class – Reveal Your Maternal Ancestors & Their Stories

My last class at the end of the final day of RootsTech was “Reveal Your Maternal Ancestors & Their Stories – Solving Mitochondrial DNA Puzzles.”

Had I tried to coordinate this presentation with International Women’s Day, I could never have done it, but fate winked and here I was.

I’m often asked what it’s like from the presenters’ perspective. This is one of the smaller ballrooms. My earlier sessions were in larger rooms, maybe 3 times this size. I took this picture about 15 minutes before the session started as people were beginning to drift in.

The amazing RootsTech techs had me wired up to microphones and had verified that the audio and video equipment was working correctly, so now it was just waiting.

My cousin, John Payne, who co-administers the Speaks surname project with me, came by and took this great picture of the two of us. We’ve made huge inroads connecting the various Speake(s) lines in America, plus finally proving our home village in England, thanks to the Big Y-700 test, followed by church records. All is takes, sometimes, is that one critical match.

As I sat there, waiting to begin the mitochondrial DNA session, I couldn’t help but reflect upon all of the women who came before me and how fortunate I was to have been in the right place at the right time to be a member of the Million Mito team.

These are my direct matrilineal ancestors who give me, and my daughter, pictured at left, their mitochondrial DNA. I felt them with me as I sat there, waiting.

The woman at furthest right, Barbara Drechsel (1848-1930), immigrated to Indiana from Germany as a child with her parents in the 1850s. Before her came thousands of generations of women with no photos, of course, and no names before Barbara Freiberger, another eight generations earlier, born about 1621 in Germany.

Before that, which was before church and other records, prior to the 30 Years War, this lineage came from Scandinavia where some of my exact matches are still found today.

Before beginning, I said a positive affirmation and thanked my ancestors – so very honored to introduce them. I know they were proud of me, a member of the team that opened the door to the distant past. I wouldn’t be here if not for every one of their lives.

In this session, I would discuss, for the first time ever, the new Mitotree and my/our connection to all of humanity some 7000 generations ago, more or less.

The mutations we carry over those generations form an unbroken chain of breadcrumbs, connecting us to mitochondrial Eve who lived about 145,000 years ago. We revealed that breakthrough finding in the Haplogroup L7 paper, published in 2022.

I’m still in absolute awe that we have been able to both reach that far back in time AND, at the same time, make the newest haplogroups and haplotype clusters genealogically relevant. I will write more about that soon, but for now, I wrote about the Mitotree release here and you can find articles by Katy Rowe-Schurwanz here and here.

I’m very excited about my new mitochondrial DNA results for my ancestral lines that I track and have already made headway on several.

I’m not the only one.

Not only was I excited about my results, many other people have had breakthroughs too, including Mark Thompson, one of our genealogy AI experts who also spoke at RootsTech. I particularly love his AI generated image.

If you haven’t yet, check your mitochondrial DNA results.

It’s a Wrap

Another year done, another RootsTech under our belts. Hopefully everyone is over the “conference crud” by now and are busily applying their newfound knowledge.

You can view either live-cast sessions or RootsTech webinars, here.

I saw a meme posted sometime during the conference that coined the term “exhausterwhelmulated,” a combination of exhausted, overwhelmed and overstimulated at the same time.

I added exhilarated and elated to the mix and asked ChatGPT to draw me a picture of someone at a genealogy conference feeling those simultaneous emotions.

ChatGPT titled this request “Genealogy Conference Overload,” which made me laugh.

The first two attempts looked like the person had a headache, which I fully understood, so I asked ChatGPT to make the person look happy to be there.

This person, carrying a coffee like I often do, looks like they have just discovered the great irony that they have chased the wrong ancestor for some 20 years – with “laugh or I’ll cry” mania being their overwhelm “go to” in that minute.

This one made me laugh too!

Yes, indeed, I think every single one of us, especially at RootsTech, has experienced this exact adrenaline-fueled emotion.

We leave with a VERY long to-do list, exhausted but full of anticipation and buoyed by excitement. Filled with so much gratitude for our cousins and fellow genealogists, the speakers, vendors, DNA to solve thorny problems, new tools and records, FamilySearch who sponsors RootsTech itself and their amazing employees, plus the legions of the volunteers who make it all work.

Thank you! Thank you! Thank 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

Mitotree is Born

Posted on by
34

Mitotree is born and I can hardly contain my excitement.

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

Left to right, the Million Mito science team is:

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

The Million Mito Project Inception

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

Drum Roll – The Mitotree

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

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

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

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

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

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

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

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

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

The beta Mitotree includes:

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

More is on the way.

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

Today’s Releases

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

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

New Haplogroups

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

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

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

New mtDNA Matches Page

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

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

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

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

mtDNA Discover

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

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

Customization that occurs exclusively for FamilyTreeDNA mtFull sequence customers includes:

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

mtDNA Discover is similar to Y-DNA Discover.

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

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

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

Match Time Tree

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

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

Haplotype Clusters

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

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

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

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

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

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

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

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

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

More to Come

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

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

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

Resources

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

_____________________________________________________________

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Welcome to 2025! – Opportunities and New Genetic Genealogy Articles

Posted on by
9

It’s a new year with new opportunities. Lots of ancestors to find and others to confirm.

For me, the best part is actually learning about my ancestors’ lives. If you’re a subscriber, I’m sure you’ve already noticed that.

These adventures and misadventures are what inspire my blog articles. What works well, what doesn’t and how to use multiple tools to unveil more about our ancestors.

That’s what motivates me. I hope it motivates you, too.

New Articles in the Works

I’d like to share some of the articles and educational events I have planned for 2025, then ask what topics you’d like to see.

Articles on the drawing board include:

  • MyHeritage DNA File Download Instructions Update
  • Mitotree – when released
  • Mitochondrial Discover – when released
  • Genealogy Proof Series – The series continues with autosomal, Y-DNA, and mitochondrial DNA proof.
  • The Forest of the Trees – Lots of different kinds of trees for both Y and mitochondrial DNA at FamilyTreeDNA. How to use them, for what, and when. This will probably be written as a series.
  • New features and developments from vendors as they occur
  • Acadian Ancestors – I hope to complete my Acadian 52 Ancestors articles. For those who don’t know, “52 Ancestors” is a challenge to write about one ancestor each week for a year. You can sign up with Amy Johnson Crow here to learn more and receive weekly prompts. It’s fun and allows you to focus on one ancestor at a time, and the history that occurred in their lifetime.

Other Learning Opportunities

In addition to those articles, I’ll be at RootsTech in person presenting:

  • DNA Academy – the 2025 version, soup to nuts
  • DNA for Native American Genealogy
  • Reveal Your Maternal Ancestors and Their Stories Using Mitochondrial DNA
  • Guide to FamilyTreeDNA – Using Y-DNA, Mitochondrial DNA, Autosomal, X-DNA and Associated Tools

I’ll also participate in other educational events with Legacy Family Tree Webinars, WikiTree, the North Carolina Genealogy Society, and FamilyTreeDNA. I’ll provide more information about them later.

Finding Information

Remember, you can always use a keyword search on this blog to find any topic I’ve written about previously.

Also, Google’s AI has apparently trained itself using my blog articles, as have a couple of other AI tools. I know this because my blog comes up as a resource when I google questions. You can try that, too.

Your Turn – What Do You Want?

There are always new topics, new features, or different ways to explain things.

  • What would you like to see covered in 2025?
  • Are there any hot genetic genealogy topics that you’d love to learn more about?

Please make your suggestions in a comment on this article.

Here’s wishing you a wonderful 2025 with lots of ancestor discoveries.

_____________________________________________________________

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

2024 Retrospective – Plus New Color Version of Complete Guide to FamilyTreeDNA

Posted on by
3

I hope 2024 was a great year for you.

2024 was an amazing year that included the release of my new book, Complete Guide to FamilyTreeDNA, and two genealogy-focused trips. I was also able to use Y-DNA to extend multiple paternal lines and break down a mitochondrial brick wall. It hardly gets better than this, but I have a focus list for 2025 already – and I hope you do, too.

But before we move on to 2025, let’s take a look at what was popular in 2024. Did you miss anything? Now is a great time to review, and I’ve assembled a list of this year’s top ten articles for you.

2024 in Review

Each year, I look back at my blog’s end-of-year statistics to see which articles were the most popular. I published 75 articles in 2024, which is an article about every four and a half days.

The Top 10 List isn’t just compiled from this year’s new articles, but the top 10 articles read this year from all 1738 articles that I’ve published over the past 12.5 years. I’ve noted the publication year by the article name.

Four of this year’s top 10 also fall in the all-time top 10. Of course, articles that have been published longer have more time to accrue views.

Article 2024 All Time
Concepts – Calculating Ethnicity Percentages (2017) 1 2
442 Ancient Viking Skeletons Hold DNA Surprised – Does Your Y or Mitochondrial DNA Match? (2020) 2
Ancestral DNA Percentages – How Much of Them is in You? (2017) 3 5
Proving Native American Ancestry Using DNA (2012) 4 1
23andMe Trouble – Step-by-Step Instructions to Preserve Your Data and Matches (2024) 5
DNA Inherited from Grandparents and Great-Grandparents (2020) 6
Ancestry’s ThruLines and Shared Matches Now Require a Subscription (2024) 7
Native American Mitochondrial Haplogroups (2013) 8 10
FamilyTreeDNA Tree Integration with MyHeritage – Step-by-Step Instructions (2024) 9
Y-DNA: Step-by-Step Analysis (2020) 10

Consistently, Native American DNA, ethnicity, and inheritance prove to be overwhelmingly popular topics. This probably explains the success of my book, DNA for Native American Genealogy. It’s timeless, and there are always new people searching! Thank you to everyone who has purchased it.

Of course, articles about this year’s announcements in the genetic genealogy world are always popular. The articles that didn’t make the Top 10 List but are in the 11-20 category include articles from RootsTech, two more Native American articles,  determining full or half-siblings, pedigree collapse, the Washington family burial article, plus one about my Acadian ancestors and their DNA.

Thank you to everyone who subscribes, reads, and comments. Please share this article or site link with another genealogist who you think might benefit. As you know, it’s easy to subscribe and completely free.

You can also search for keywords in articles throughout the year to answer questions when you see them on social media or elsewhere. It’s easy and educational to post or send an article link.

Complete Guide to FamilyTreeDNA – Now Available in Color

Are you ready for a good laugh?

As I was reviewing these articles, I thought to myself, “where’s the announcement of the new color version of my book, “The Complete Guide to FamilyTreeDNA”?

I literally forgot to publish that article. How could I?? I mean…seriously. (My excuse is that I was traveling, plus conferences and back-to-back hurricanes.)

So, here’s the (slightly late) mini-announcement.

Initially, in May, The Complete Guide to FamilyTreeDNA was released in a full-color e-pub version, which is available from the publisher here. You can take a look at the table of contents here.

That was followed shortly by the release of the black and white print version, available in the US from the publisher, here, and worldwide from your country’s Amazon. Selling outside the US through Amazon removes the issues of expensive international shipping, VAT tax, and customs, which significantly increases the cost of the book and delays its delivery.

The decision was made to publish initially in black and white due to printing costs, but lots of people requested a color book.

For those who have already purchased the black-and-white version, the publisher has provided a free downloadable PDF with 26 of the most critical pages in color. We really had no idea that people would be eager to purchase a color version, but that has proven to be the case, and we didn’t want earlier purchasers to be disappointed.

Drum Roll

You spoke, and we listened.

In the fall, we released a full-color print-on-demand version of The Complete Guide to FamilyTreeDNA. Again, in the US, the book is available from the publisher, here, and at Amazon elsewhere.

This book truly is comprehensive and includes both DNA education, along with how to use the FamilyTreeDNA tools, many of which are unique in the industry. For example, no other vendor offers either Y-DNA or mitochondrial DNA testing and matching.

You don’t know what you don’t know, and I encourage you to find out!

Thank You!

Thank you so much for your ongoing support. Twelve years strong, going on 13.

Be thinking about what you’d like to see in 2025, because I’m going to be asking you tomorrow!

_____________________________________________________________

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. Just look for the black “follow” button on the right-hand side on 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 Books

Genealogy Books

Genealogy Research

Leave No Stone Unturned, No Ancestor Behind: 10 Easy Steps to Capture DNA Clues

Posted on by
5

There’s a lot, a whole lot that DNA testing can tell you. Not just your own tests, but the genetic information carried by your relatives that you do not.

Recently, I’ve been reviewing my brick walls, which led me to realize there are several ancestors who are missing their mitochondrial DNA and/or Y-DNA  results. I need these to learn more about my ancestors that can’t be revealed any other way – and to break down those pesky brick walls.

I’ve solved two mysteries recently, one thanks to a Big Y-700 test, and a second very unexpectedly thanks to mitochondrial DNA – both thanks to cousins who tested. These revelations were very encouraging, especially since there’s no way other than DNA for me to break through these brick walls. The mitochondrial test had been sitting there, waiting for what seemed like forever until just the right other person tested.

I am in the process of unlocking several brick-walled ancestors by providing testing scholarships to people who are appropriately descended from known ancestors in those lines.

Don’t leave information on the table. If I were to tell you there even MIGHT be a book available about your family, you’d overturn Heaven and Earth to find it – but you don’t need to do that. All you need to do is order DNA tests for cousins.

All cousins can provide useful autosomal DNA results, but you do need to find appropriate cousins for Y-DNA and mitochondrial DNA testing.

I’m sharing the steps for how I accomplish this! You’ll be amazed at what’s out there – and someone may already have tested!

Take Advantage of the Holidays

I’m sharing NOW because it’s the holidays and you’re likely to gather with people you don’t see any other time – and because the best sale of the year for both Y-DNA and mitochondrial DNA lasts from now through the end of the year.

These two factors combined mean strike while the iron is hot.

Prices for new tests and bundles are at an all-time low.

If you or your relatives have already taken a lower-level test, now is the time to upgrade to either the Big Y-700 or the mtFull Sequence test.

Step 1 – Test Yourself and Your Known Family

If you’re a male, order both the Big Y-700 test and mitochondrial DNA tests.

Be sure to click on “See More” for more useful tools.

When you receive your results, be sure to click on all of the tabs in your results, and do the same by clicking through to Discover from your account. Discover has 13 more goodies for you to help with your genealogy.

Both your personal page and Discover are essentially chapters of your own personal book about your DNA results. 25 very interesting chapters, to be precise, that are uniquely you.

I’ve written about understanding Y-DNA results here, and mitochondrial results here. My book, Complete Guide to FamilyTreeDNA, covers both along with Discover.

Discover provides robust information for Y-DNA haplogroups. If you’ve taken a Big Y-700 test, you’ll want to click through from your page to receive additional, personalized and more robust information than is available through the free public Discover tool. That said, the public version of Discover is an amazing tool for everyone.

After the new Mitotree is released for mitochondrial DNA, mitochondrial haplogroups will be available in Discover too.

I can’t even begin to stress how important these tools are – in particular the Time Tree, the Group Time Tree for members of group projects, and the Match Time Tree for your own matches.

Who Can Test For What?

Once you’ve tested yourself, you will want to take a look in your pedigree chart at branches further up your tree to see who can be tested to represent specific ancestors.

Let’s begin with my father’s side.

A mother contributes her mitochondrial DNA to all of her children, so your father carries the mitochondrial DNA of his mother.

If you’re a female, and your father is available to test, you’ll want to test BOTH his mitochondrial DNA and Y-DNA, because there’s no way for you to obtain that information from your own test. Females don’t have a Y chromosome, and men don’t pass on their mitochondrial DNA.

If you’re a male, you can test your own mitochondrial DNA and Y-DNA, but you’ll need to test your father’s mitochondrial DNA to obtain his mother’s. You might still want to test your father’s Y-DNA, however, because you may discover a personal family haplogroup. How cool is that??!! Your own tiny branch on the tree of mankind!

Your father’s mitochondrial DNA provides you with mitochondrial matches and haplogroup information for your paternal grandmother – in this case, Ollie Bolton.

If your father and his siblings can’t test, then all of the children of your paternal aunts carry your paternal grandmother’s mitochondrial DNA.

If they have no children or they can’t test, then the children of Ollie Bolton’s mother, Margaret Claxton/Clarkson all carry her mitochondrial DNA, and the children of Ollie’s sisters continue the line of descent through all daughters to the current generation.

The male children of Joseph “Dode” Bolton and Margaret Claxton carry his Y-DNA. Fortunately, that’s not one of our missing haplogroups.

Yes, you may have to climb up your tree and climb down various branches to find a testing candidate.

One of the reasons I’m using this example is because, while I have a high-level haplogroup for my grandmother, Ollie Bolton, we need a full sequence tester – and I’m offering a mitochondrial DNA testing scholarship for anyone descending from Margaret Claxton (or her direct female ancestors) through all females to the current generation, which can be male.

Ok, now let’s switch to the maternal side of your tree.

On the other side of your tree, your maternal grandfather or your mother’s brothers will provide the Y-DNA of your mother’s father’s line. Your mother’s uncles or their sons will provide your grandfather’s Y-DNA line, too. In this case, that’s John Whitney Ferverda, who carries the Y-DNA of his father, Hiram Bauke Ferverda/Ferwerda.

Your maternal grandfather or his siblings will provide the mitochondrial DNA of their mother, Evaline Louise Miller.

If they are deceased or can’t test, for mitochondrial DNA, look to the children of Evaline Miller’s daughters or their descendants through all females to the current generation, which can be male.

And yes, in case you’re wondering, I do need Evaline Miller’s mitochondrial line too and am offering a scholarship.

You might have noticed that I’ve been inching my way up my tree. All of my immediate relatives have passed over already, so I’m now looking for testers that I don’t know but who I’m related to.

If you’re seeing family members anytime soon, figure out if their Y-DNA, mitochondrial DNA, or autosomal DNA would be useful for your common genealogy. Take advantage of the opportunity.

Next, you’ll want to figure out which ancestors need haplogroups and locate appropriate cousins.

Step 2 – Identify Ancestors Who Need Haplogroups

Peruse your tree to determine which of your ancestors you need haplogroup information for. To make it easy, on my computer, but never in a public tree anyplace, I store the haplogroup of my ancestor as a “middle name” so I can easily see which ones I have and which ones I need. Sometimes, I have a high-level haplogroup and either need a new tester or someone to upgrade.

Sometimes, I have one tester from a line but need a second for confirmation.

In this example, I’m not missing confirmation on any Y-DNA haplogroups (although I am further upstream on different lines,) but I do need four different mitochondrial DNA lineages.

For easy reference, make a list of all of the lines you can’t confirm with two testers from different children of the same ancestor.

You just might get lucky and discover that someone has already tested!

Step 3 – Check FamilyTreeDNA Projects

Check FamilyTreeDNA Projects to see if someone has already tested to represent those ancestors on your list.

Click here for the Group Project Search. It’s located at the very bottom of the main FamilyTreeDNA page in the footer.

I’m going to use Estes as an example since I’m the volunteer administrator of that project and am very familiar with the lineages.

I’m searching for projects that include the surname Estes.

The projects displayed on the list are projects where the volunteer administrators listed Estes as a possible surname of interest. It doesn’t mean those projects will be of interest to everyone or every line with that surname, but evaluate each project listed.

You probably want the surname project, but if there’s not a surname project for your surname, try alternate spellings or consider checking other projects.

You can see at the bottom that 384 people of both sexes by the surname of Estes have tested at FamilyTreeDNA.

Now, let’s look at the Estes project. Note that not everyone with the Estes surname has joined the Estes project.

I’ve clicked on the “Estes” link which takes me to an additional information page where I can read a description and click to view the project.

For the Estes project, you do not have to join to view the results. Nor does your surname have to be Estes. All Estes descendants of any line are welcome. Everyone can benefit from the Advanced Matching within project feature to see who else you match within the project by selecting a wide range of individual and combined filters.

Click on the Project Website link shown in the search results.

If you’re searching for a male Estes ancestor, you’ll want to review the project’s Y-DNA Results and the Group Time Tree, for sure, and possibly the Map as well.

Let’s pretend I’m trying to determine if anyone has tested who descends from my ancestor, Abraham Estes, the founding Estes ancestor in Virginia who arrived in the mid-1600s.

In the Estes project, the volunteer administrator has divided the Estes male participants by sons of Abraham, the immigrant. Only three are shown here, but there are several.

Some of the participants have completed their Earliest Known Ancestor information, in the red box. Sometimes people don’t think to update these when they make breakthroughs.

If you descend from Abraham’s son, Sylvester, three men have taken the Big Y-700. That’s the test results you need.

If you descend from Abraham’s son, Abraham, no project participants have taken the Big-Y test to represent that line, although six people have tested, so that’s great news. Maybe you can offer an upgrade scholarship to one or some of those men.

In other words, to establish the haplogroup for that lineage, at least two men need to test or upgrade to the Big Y-700, preferably through two different sons of the common ancestor. A new, more defining haplogroup is often formed every two or three generations for Y-DNA.

Your genetic pedigree chart looks a lot like your genealogy pedigree chart.

Click any image to enlarge

The project Group Time Tree shows selected groups of men who have taken Big Y tests, along with their Earliest Known Ancestor, if they’ve provided the information. This is one of the reasons why the Big Y-700 is so critically important to genealogy. The time granularity is amazing and can answer the question of whether men by the same surname descend from the same common ancestor – and when.

If you’ve taken a Family Finder autosomal test at FamilyTreeDNA, or uploaded an autosomal file from another vendor, you may match one of these men or another male that descends from the Estes line if they, too, have taken an autosomal test.

This same process applies to mitochondrial DNA, but generally surname projects aren’t (as) relevant for mitochondrial DNA since the surname changes every generation. However, sometimes other projects, such as the Acadian AmerIndian Project are quite beneficial if you have Acadian ancestry, or a geographic or regional project like the French Heritage Project, or something like the American Indian Project.

Another great way to find testers is by utilizing your Family Finder test.

Step 4 – Family Finder at FamilyTreeDNA

The next step is to see if you match anyone with the surname you’re searching for by using your autosomal test results, so select your Family Finder Matches.

At FamilyTreeDNA you’ll want to search your matches by the surname you seek. This surname search lists any tester who has that surname, or anyone who has entered that surname in their surname list. Please note that this search does NOT read ancestors in your matches’ trees. You’ll still need to view trees.

Reviewing the 32 Estes Family Finder matches reveals several men, but one man with the Estes surname has already taken a Y-DNA 25-marker test, so he would be an excellent candidate to offer a Big Y-700 upgrade scholarship. If he’s not interested or doesn’t respond, there are several more men to contact.

Click on your match’s name to display the profile card, along with the Earliest Known Ancestors, both Y-DNA and mitochondrial DNA haplogroups if they have tested, and the assigned haplogroup based on their testing level.

Craft an email and offer a testing scholarship. This will help both of you. I’ll provide a sample email at the end of this article.

If you match a female with an Estes surname, her father, brother, uncle or cousin may either have already tested or be willing.

If you match someone who has a different surname, that means they have an Estes surname in their surname list and may know a potential tester. If your match has a tree, click to check.

I’ve found that matching through a company where you’ve both tested is the easiest way to encourage someone to take an additional test, but certainly, it’s not the only way.

Step 5 – WikiTree

WikiTree is a quick and easy way to see if anyone has taken a Y-DNA or mitochondrial DNA test that should reflect a particular ancestor’s Y-DNA or mitochondrial DNA.

I just googled “Moses Estes 1711-1787 WikiTree” and clicked to view.

Each ancestor includes both Y-DNA and mitochondrial DNA information, in addition to people who descend from that ancestor through only autosomal lines.

In this case, two men have provided their Y-DNA results that pertain to Moses Estes. They have tested at different levels, which is why they have different haplogroups. That doesn’t mean either is “wrong,” one is just more refined than the other. You can correlate their kit number with the Estes surname project. People often don’t update their haplogroup information at WikiTree when it’s updated at FamilyTreeDNA.

Please note that if the genealogy is wrong, either at WikiTree or individually, the haplogroup may not reflect the appropriate lineage for the ancestor. Check to be sure that there’s no conflict showing between two testers for the same ancestor. For example, the same ancestor clearly can’t have two different base haplogroups, like E and R. The Discover Compare tool can help you evaluate if two haplogroups are in the same part of the Y-DNA tree.

When possible, it’s always best to test a close family member to represent your lineage even if someone else has already tested.

Scan down the list of autosomal testers for that ancestor to see if there’s someone with the Estes surname.

WikiTree provides additional tools to find descendants.

Sign in to WikiTree. You’ll see the ID of the profile you’re viewing – in this case – Estes-167. Click the down arrow and select “Descendants.”

This view shows all descendants through five generations, but you can click on DNA Descendants to see only Y-DNA descendants, X-DNA, or mitochondrial DNA descendants for female ancestors.

You may find people who are living and have added themselves who you can contact to offer a DNA testing scholarship.

Step 6 – MyHeritage

At MyHeritage, you can also search your DNA matches by surname.

Click on “Review DNA Match” to view more detail, including locations. Look to see if you have a Theory of Family Relativity Match which suggests how you may be related. That’s golden!

There’s no Y-DNA information at MyHeritage, BUT, you can search by surname and view DNA matches that either carry that surname or have that surname in their tree as an ancestor.

I have a total of 75 “Estes” matches, and other than the kits that I manage, searching through my matches shows:

  • Two Estes men connected to the same small tree, but that’s OK, I’m a genealogist!

  • One Estes male match with a Theory of Family Relativity. My lucky day!

You can contact your match easily through the MyHeritage messaging system and offer a DNA testing scholarship at FamilyTreeDNA. You may also want to share your email address.

MyHeritage customers may not be familiar with Y-DNA or mitochondrial DNA testing, so you might want to share this article about the 4 Kinds of DNA for Genealogy.

MyHeritage testers can also upload their DNA file to FamilyTreeDNA for free to receive autosomal matches plus a complimentary mid-range Y-DNA haplogroup. This free haplogroup is not even close to the detailed resolution of a Big Y-700 test, but it’s something, and it may well be an enticing first step for people who are only familiar with autosomal testing.

Step 7 – At Ancestry

At Ancestry, select DNA Matches and then search by surname.

You can search by the surname of the tester, which is very useful, or by people who have Estes in their trees.

I started with the surname Estes, because it’s the most straightforward and I may find a perfect male candidate for Y-DNA. If someone’s “screen name” doesn’t show as Estes, they won’t appear in the results of this search. In other words, if your Ancestry screen name is “robertaestes” you won’t show in this search, but “Roberta Estes” will.

For mitochondrial DNA, you would want to search for the surname in your matches’ trees. Unfortunately, you cannot search for the specific ancestor in someone’s tree, at least not directly.

Of my 19 Estes surname matches, ten are males, and of them:

  • Three have unlinked trees
  • Three have very small linked trees, but I can work on extending those if need be
  • Three have public linked trees AND a common ancestor, which means ThruLines

I can review which ancestor we share by clicking on my match’s name

The Estes side of this man’s tree has only one person and is marked “private,” but Ancestry has suggested common ancestors based on other people’s trees. (Yes, I know trees are dicey, but bear with me.)

It’s also worth mentioning that you can be related through multiple lines. I share surnames from Acadian lines with this man, but that really doesn’t matter here because I’m only using autosomal matching to find an Estes male.

Click on “View Relationship” to see our common Estes ancestor’s ThruLine.

The ThruLine shows how Ancestry thinks we’re related on the Estes line.

I can also click on “View ThruLines” to see all Thrulines for John R. Estes, which shows four additional males, some of which did NOT appear in the Estes surname search, and some of which don’t appear further up the tree. In other words, check all Estes ThruLine ancestor generations.

Don’t rely solely on Ancestry’s surname search.

Go directly to your ThruLines on the DNA menu.

Ancestry only reaches back seven generations, which for me is Moses Estes and Luremia Combs. Moses has 95 matches, but he has been given some incorrect children. Again, for this purpose, it doesn’t matter. Within all ThruLine matches, I found three Estes males who all descend through John R. Estes. Check every generation.

However, Luremia Combs shows promise for mitochondrial DNA descendants. Unfortunately, only two of her daughters are represented in ThruLines, and both of their descendants descend through Luremia’s grandsons. That’s too bad, because I need Luremia’s mitochondrial DNA line.

It’s easy to message your Ancestry matches. You may want to mention that they can upload their DNA file to FamilyTreeDNA for free where they will receive more matches and males will receive a complimentary mid-level Y-DNA haplogroup.

Please note that, in general, ThruLines need to be evaluated very carefully and are prone to errors, especially if you accept Ancestry’s suggestions of ancestors instead of carefully building out your own tree. Regardless, you can still find Estes cousin matches in your match list and by using ThruLines to find people that do not show up in an “Estes” match search.

Step 8 – At 23andMe

At 23andMe, you can search for anyone who either has the Estes surname or has included that surname in their “Family surnames” list. Keep in mind that your matches at 23andMe are restricted to either 1500 if you don’t have a subscripition, or about 4500 if you do have a subscription.

On my match list, I have two males with the Estes surname.

23andMe provides a mid-level Y-DNA haplogroup. You can’t use this to confirm the lineage when comparing with FamilyTreeDNA, especially given that 23andMe provides no genealogy or user-provided tree, but it is a clue.

Both Estes men at 23andMe have Y-DNA haplogroup R-CTS241. You could use this in some cases to potentially eliminate these matches at 23andMe. For example, if men in your lineage in the Estes project are in haplogroup R and your 23andMe matches are showing as haplogroup E, or any other base haplogroup, their common ancestor is tens of thousands of years ago.

Comparing the 23andMe haplogroup, which in this case is about 4500 years old, to contemporary testers who have taken the Big Y-700, which reaches within a few generations, isn’t terribly useful. These matches are extremely useful to identify individuals to reach out to for further information and potentially offer a Y-DNA testing scholarship at FamilyTreeDNA.

Remember, this also applies to females who have included Estes in their family surnames, given that they may have Estes male relatives.

By clicking to view your match, you can see if they have provided Family Background information, including a link to a family tree someplace.

Sometimes, there’s great information here, and other times, nothing.

You can’t verify this lineage without genealogy information.

I suggest leaving a genealogy-focused message, including where they can see your tree in addition to your Estes connection. Also include your e-mail.

You may want to say that if they descend appropriately, you have a Y-DNA or mitochondrial DNA testing scholarship, or you may want to wait to see how they descend. You can also ask if they have already taken a Y-DNA or mitochondrial DNA test at FamilyTreeDNA.

Step 9 – FamilySearch and Relatives at RootsTech

We’re getting ready for RootsTech 2025 which takes place in March. In the month or so before the last two RootsTechs, FamilySearch provided an absolutely wonderful tool called “Relatives at RootsTech.”

I’ve written about this several times, but essentially, you can see, by ancestor, other people who are registered both in-person and virtually for RootsTech, and how they descend.

Here’s an example.

In both years, I’ve found several people who descended from common ancestors AND were very willing to take the relevant DNA test. That’s a huge win-win for everyone.

The best part is that because these people have freshly registered for RootsTech, the reply rate is almost 100%.

I’ll write about this as soon as RootsTech makes it available this year. Fingers crossed that they do!

Step 10 – Social Media

Social media wouldn’t be my first choice to find DNA testers, but I have found perfectly willing cousins this way. You may be less successful on Facebook or other social media platforms, but if you’re striking out elsewhere, there’s absolutely no downside to trying.

You can enter a surname and search on Facebook, but I prefer to do a Google search like “Estes genealogy on Facebook” or even just “Estes genealogy,” which will produce far more widespread information, some of which may be irrelevant.

That Facebook Google search provided the names of two groups. People join groups because they have an interest, and I’ve had good luck in Facebook genealogy groups.

A Search of “Estes” on Facebook itself, then selecting “people” provided a list of Estes Facebook users.

I’ve had far better luck by joining a group that is focused on Estes genealogy, or even a county genealogy group that includes Estes families, than individuals. People who join any Estes group or project likely have an interest in that surname.

If you have a common surname, or there’s a park named after your surname, like Estes Park, you’ll probably want to focus by using Google searches for Estes genealogy.

The Descendants of Abraham Estes Facebook group has 222 members, of whom at least 31 are males with the Estes surname. Facebook just might be an underestimated resource.

If there isn’t a genealogy-focused group for your surname, you might want to consider starting one and encouraging people to join.

It can’t hurt, and it just might help. Before you start reaching out to random people on Facebook, please do a privacy checkup – I wrote about how, here.

Sale Prices

Remember, the sale prices at FamilyTreeDNA for new tests and upgrades last through year-end.

In my experience, it’s best to test as soon as someone agrees. You never know what will happen otherwise. I’ve had people pass away before they could swab. And yes, we’ve done funeral home swabs, too.

There’s no one-size-fits-all, but here’s a rough draft contact letter.

Potential Contact Letter

You’ll want to include several critical pieces of information.

Essentially:

  • Introduce yourself
  • Say their full name on their test AND the testing company in the title of an email. I manage many tests and if I receive an email that says, “Hi, can you tell me how we match” without telling me which person they match, I can’t even begin to answer.
  • Explain your genealogy connection
  • State your purpose in writing
  • Explain how a specific test will help them too
  • Offer to answer questions

Be sure to modify this letter to reflect your own voice and circumstances. You don’t want this to read like a form letter.

Dear cousin (insert their full name here,)

It was so nice to find our DNA match at <company name> (or we share a common ancestor, or appropriate circumstance.) (If you are managing someone else’s kit, say the name of who they match and explain that you manage their DNA kit.)

I descend from (ancestor plus birth and death date) who lived in Halifax County, Virginia and was married to (spouse.) You can view my tree at (insert link that does not require a subscription for viewing unless you match them on that platform. I use MyHeritage because everyone can view their trees)

I would very much like to confirm that our line descends from Abraham Estes (or relevant information meaning your reason for wanting them to test.)

Given that my surname is x (or I’m a female), we need to test the Y-DNA of a male who is descended from (ancestor) through all males to the current generation. (Or mitochondrial DNA descended through females to the current generation which can be male.)

FamilyTreeDNA provides this testing and shows who you match on that specific line using the Y chromosome (mitochondrial DNA).

This testing may connect us with earlier ancestors. Genetics can be used to determine when we share common Estes ancestors with others who test, where we come from overseas, and when. Even if we match ancient DNA samples that may tell us where our ancestors lived before surnames. In other words, where did we come from?

(Include a nice paragraph, but not a book about your ancestral lineage here.)

I have a DNA testing scholarship for someone from this line and you are the perfect candidate. I would like to take advantage of the current sales. If you’re interested, I only need two things from you.

First, permission so that I can order (or upgrade) and pay for the test, and second, an address where to send the test (unless it’s an upgrade). (If it’s an upgrade at FamilyTreeDNA, they can use a stored sample or will sent them a new kit if there’s not enough DNA.)

If you have any questions, please let me know. I’m very excited that we may be able to learn more about our heritage.

Please email me at xxx or call me at xxx if you have questions.

Your name

I know one person who offers to review results over Zoom. Someone else stresses that the tester’s email is attached to their test and they are always in control of their results. Another person asks them to join a project they manage to assure that they can follow their matches over time.

Customize this communication in your own voice and to fit the circumstances of each match.

It’s just me, but since I’m ordering while the tests are on sale, unless the person uploads their DNA file from another vendor, I add on a Family Finder test too and explain why. You never know if they will match you or another cousin, and they may have that match that eventually breaks down the next brick wall. Shared matches are powerful evidence and it’s a lot easier to add that test on now than try to contact them again later.

You Don’t Know What You Don’t Know

Which ancestors do you need Y-DNA or mitochondrial DNA results for? Methodically check each line.

There’s so much to learn. Don’t leave information on the table by virtue of omission.

Leave no stone unturned!

You don’t know what you don’t know.

Who’s waiting out there 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

Genealogy Proof Series – Creating Genealogy Proof Tables

Posted on by
5

This is the fifth article in the Genealogy Proof Series.

For maximum advantage, I recommend reading these articles in publication order.

In earlier articles, we’ve detailed how to gather resources for specific locations, how and where to search for surnames and the process of extracting and recording information from those sources.

Now, it’s time to use that information and assemble it in a logical way to provide “proof” that the person by the name of “John Smith,” or whoever you’re seeking, is actually YOUR John Smith.

I use a technique that I call Genealogy Proof Tables. We will cover two types here. You’ll need the first one to complete the second one.

Genealogy Proof Tables

Genealogy proof tables have two purposes:

  • Individual Proof Tables – For an individual ancestor, to compile the various pieces of evidence to prove a connection to their parent or parents and their child or children.
  • Lineage Proof Table – Evidence for an entire lineage, proving connections between all of the individuals in the lineage, one by one in both directions. For a lineage proof table we prove a connection to the parent and also to the descendant that is your ancestor for each generation.

Please note that sometimes you actually wind up disproving a relationship, or realizing you need more information, but that’s equally as important. Nothing worse than wasting time by barking up the wrong tree.

A genealogy proof table is a working document that can be used to focus on each ancestor in every ancestral line. What’s included in a proof table varies by which records are available, the timeframe and circumstances.

You may want to prepare proof tables to help yourself focus and evaluate your data. Proof tables can be sent to someone who asks questions like:

  • How do you know that?
  • What is your proof?
  • What are your sources to identify John as the son of George?

People should be asking those questions, and researchers should be able to answer them. You need to answer them for yourself for your own ancestors, even if no one asks.

The answer to these questions may well be that you’re still working on “proof,” but you’ll at least want to have documented everything available to date. For me, doing these exercises helps me think about what’s still missing and looking for additional sources if I actually don’t have “proof.”

Generally, I create a proof table for a specific ancestor, which I then roll up into a comprehensive proof table for the line. This approach helps me identify which pieces of evidence are conclusive and which ones are not.

The purpose of a proof table is to compile and rank information about that ancestor’s connection to their parents, including negative evidence. It’s not meant to be “everything I know” about that ancestor, just the things that relate to proving that this ancestor is in FACT the child of his parent or parents.

What is Proof?

Isn’t this the question of the ages for genealogists? I wrote an article, Ancestors: What Constitutes Proof?, here. In that article, I’ve provided a list of what isn’t proof and some challenges you may face.

Aside from what I’ll term normal genealogy roadblocks to be overcome, there are other challenges as well.

For example, you can have a birth certificate, a death certificate, a will, and personal knowledge that a person lived with their parents – but that child could have been adopted, or the father might not have been the biological father.

In this case, paper proof, no matter how compelling, isn’t actual proof. It can prove the identity of the person, but alone, cannot prove a biological relationship connection.

Sometimes, DNA evidence outweighs everything else, but without DNA evidence, paper proof is the closest we can get. The BCG defines the Genealogical Proof Standard, here.

We need our evidence to be as conclusive as possible.

What does Conclusive Mean?

Conclusive evidence means that any other evidence cannot reliably contradict it, or it’s so strong that it overbears any other evidence. (Thank you Bar Prep Hero.)

In a nutshell, that’s your goal – and all evidence is not created equal.

Evidence is Weighted

Some evidence is better or more solid than other evidence.

Furthermore, sometimes one single piece of evidence isn’t conclusive, but multiple pieces of evidence, taken together, create a body of work and are considered a “preponderance of evidence.” Having said that, I often cringe when I hear that term because sometimes it means there really isn’t good evidence or not enough research has been done.

How good is good enough? You can only work with what’s available and what you have. Unfortunately, one cannot unburn the courthouse!

Sometimes, you’ll need to use DNA evidence. From my perspective, you ALWAYS need to utilize DNA evidence to confirm at least the closest generations.

By closest, I mean that second cousins or closer always match, and you can often reliably use autosomal DNA within, minimally, 5 or 6 generations, but circumstances vary.

Many times I have solid matches to descendants of ancestors 9 or 10 generations in the past, but as you can see in this graphic created by Dr. Paul Maier at FamilyTreeDNA, beginning at eight generations, you may not inherit any DNA from a particular ancestor. Of course, to match someone else, you both need to have inherited the same DNA segment(s) from that ancestor.

You can almost always use Y-DNA to establish relationships beyond what autosomal can confirm, but with both Y-DNA and mitochondrial DNA, you need someone who is appropriately descended from the ancestor in question, as illustrated in this three-generation chart. Sometimes, you need two people descended from that ancestor, preferably through different children, because their Y-DNA or mitochondrial DNA needs to match.

Every situation is different.

How Much Evidence is Enough?

It depends.

Enough for what?

  • Enough to prove that your parent is the child of their parents?
  • Enough to prove to yourself that you’re searching in the right ancestral line?
  • Enough to prove that this John Doe is the same John Doe that moved from Virginia to someplace else, or conversely, the John Doe in Missouri is the one who moved from Virginia?
  • Enough to quality for a lineage society?

Again, from my perspective, enough is not enough until you have looked at every piece of evidence that even MIGHT be relevant for that ancestor.

Essentially, all of this is a bit fluid, so let’s look at an example.

Individual Proof Table

Let’s begin with a proof table for one person.

I’m going to create a proof table to attempt to prove that my paternal grandfather, William George Estes, is the son of Lazarus Estes and Elizabeth Vannoy.

I’ll be using actual documents and information from my files.

If you want to read my 52 Ancestors articles about these people, you can find William George Estes, here, Lazarus Estes, here, and Elizabeth Vannoy, here. I’m not specifically trying to prove that my father, William Sterling Estes, is the son of William George Estes, but some documents cover both men – plus, there’s the possibility of same-name confusion, given that both of their first names are William. I swear, every generation in this family has both Johns and Williams.

To begin, there are a few mandatory categories on every chart. For example, I always use the census when it’s available. You should include these categories even if you don’t have evidence for them, because it reminds you if you’ve searched and the search came up with nothing.

Some categories would be expanded, such as Organizational Societies. For example, if there’s a separate History and Genealogy Society for that county, you would want to check both, as well as the local library and regional or state organizations.

You’ll notice that I’ve assigned a weight to each piece of evidence. Weighting is subjective. Aunt Margaret was the daughter of Wiliam George Estes, so she should know – but often, she didn’t provide any source, like a document or Bible, and she was a bit “eccentric.” In some circumstances, I might weigh what she provided as a 5, but in the first item, I only gave it a 4 because she provided other dates that I found to be erroneous. Memories do fail people.

Red items are direct, confirming evidence of the relationship and that the William George Estes, my grandfather, is the same William George Estes who is the son of Lazarus Estes. Names are spelled or misspelled the way they are in the original source.

William George Estes Information Source Weight (1-5) Comments
Birth March 30, 1873 Aunt Margaret 4 Birth certificates not available in 1873
Father Lazarus Estes
Mother Elizabeth Vannoy
Identity of Parents From letters and discussions 1980s, 1990s Aunt Margaret, Aunt Minnie, children and grandchildren of William G. Estes 5 They knew their grandparents
1880 Census Wm. G. Estis age 7, listed with parents Lazarus and Elisibeth Estis, and siblings, including sister Cornie Claiborne County, TN Dist 8, page 107 on Ancestry 5 Family lives between William G.’s future wife’s uncles
1890 Census destroyed
Marriage Ollie Bolton, Sept 26, 1892. Claiborne County Marriage Index, page 382 5 No parents given
1900 census William G. age 27, with wife, Ollie, and two children Claiborne County, TN Dist 8, page 113 5 Lives next door to Lazarus and Elizabeth Estes and next to his sister Cornie and her husband
1910 census Age 38, with Ollie and two children, Estle and Robert Claiborne County, Civil Dist 4 5 Lives beside sister Cornie and her husband, three houses from Lazarus
Home Location – 1913 Family photos taken in 1913 and labeled “Fowler” Provided by Margaret 5 Written on the back of the family pictures
Home Location Fowler, Indiana Sept 1915 Newspaper article 5 Sons Wm. and Joe ran away and were returned to parents in Fowler
William G. Estes’s divorce from Ollie Fowler, Indiana Aunt Margaret 3 Ollie caught him cheating with her cousin Joyce Hatfield, who was visiting them in Indiana
Divorce from Ollie Unknown, maybe 1916 or 1917 Inferred
Children William S. and Joe “run away” to their grandparents 1915/1916 Fowler, Indiana to Claiborne County, TN Aunt Margaret’s letter, Uncle George, 1915 newspaper articles stated that they tried to run away but got caught 5 Margaret said that when William G. and Ollie divorced,  neither wanted sons Wm. and Joe, 13 and 11, and the boys jumped trains to make their way back to their grandparents, Lazarus and Elizabeth
William George returned to Claiborne County 1916/1917 ish Uncle George Estes, family historian 5 Lazarus was furious when William G. returned after cheating on Ollie and abandoning the boys and threw William G. out of Estes Holler
Move to Harlan County, KY After being thrown out of Estes Holler when he and Ollie divorced Uncle George, Aunt Margaret, Estel’s daughter 5 Settled in Harlan County, KY, just over the border from Claiborne Co., TN
Divorce from Ollie Unknown, about 1916/1917ish Fowler, Ind newspaper August 30, 1917 2 Ollie listed without Wm G and as visiting where she used to live
Marriage Joyce Hatfield, unknown if or when/where married Census, daughter Virginia’s birth Nov. 1918. 3 Inferred, no document found
Child Irene’s Death* August 1, 1916 – Irene Estes, mother Joyce Fury Shawnee, Claiborne Co., TN Informant of the death of daughter, Irenia.

*Please note that this has since been disproven. This William B. Estes who married Josie Fury is not our William G. Estes who married Joicie Hatfield.
Military/draft Registration – signed Sept. 12, 1918, gives birthdate as March 30, 1873 Tazewell, Claiborne County, TN 5 Wife is listed Joisce Estes.
1920 census Age 47, lives with Joise and daughter Virginia Claiborne Civil District 4 5 Future third wife, Crosha Brewer, and her child are living with them as lodgers
Divorce Joice Hatfield Unknown, approx 1921 or 1922 inferred Based on Crosha’s children’s ages
Son William S. Estes’s marriage to Martha Dodder Dec. 12, 1921 Calhoun County, MI 5 Parents are given as Ollie Estes and W. G. Estes
Wm G. Estes child with Croshia Brewer Josephine born March 19, 1923 Springdale, Arkansas 5 Birth certificate, death certificate, census
William George Estes Marriage Croshia Louise Brewer, Feb. 3, 1925, Wise County, VA VA Marriage Registers, page 171 5 Parents given as Lazarus & Elizabeth Estes
1930 census Cannot find the family
1940 census Age 67, living with Crochie and their 2 daughters Harlan Co., KY Lynch dist 5
1940s or 50s Photo with “his sister Cornie” and also one with “Worth Epperson” Claiborne County, TN 5 Photo is labeled and provided by Cornie’s family, who knew him
1950 census 76, lives with Crocie, daughter and boarder Harlan County, KY 5 My mother visited William G. and Crocie with my father in the 1950s.
Cornie Estes Epperson’s 1958 death certificate Born June 22, 1878 to Lazarus Estes and Betty Vannoy, age 79, died Feb. 18, 1958 Death Certificate 5 Correlates to census dates and other data indicating she is the daughter of Lazarus and sister of William G.
Cornie Epperson Obituary Gives Will Estes, of Lynch, KY as her brother. Newspaper clipping 4 Does not give her paents
William Sterling Estes obituary Aug. 28, 1963, Star Press in Muncie, Indiana, page 3 Residence Dunkirk, IN 4 Lists surviving father as W. G. Estes, Cumberland, KY
William George Estes’s death Nov 29, 1971, lived in Harlan Co., KY Kentucky Death Index 5 Parents not given
Obituary Parents not given, living children include Estil, Virginia, Margaret, and Minnie, their locations provided Nov. 30, 1971, Middlesboro Tribune 4 His nephew, Cornie Estes Epperson’s son, Kermit Epperson is a pallbearer
Social Security Claims Index for William G. Jan. 15, 1972 claim, birth 1873 Ancestry 5 SS # given, but no parents given
Social Security Claims Index for my father, William Sterling Estes No claim filed
Will No, rechecked film at FamilySearch 7-8-2024.
Legal No, checked court index in Harlan County
Land Tax No tax lists
Personal Tax No tax lists
Deeds Yes, 1915 deed from Lazarus to Cornie and Worth Epperson where they must pay his other heirs Claiborne County deed book, in person 5 Cornie Estes Epperson to pay William Estes $120
William George Estes signed receipt and release On July 22, 1957, Will signed on the edge of the above deed, releasing the claim on the deed and stating that the $120 had been paid. 5 Confirms his relationship to Lazarus Estes and Cornie Estes Epperson
Sibling Documents Have not looked extensively beyond Cornie
Newspapers Need to revisit when Claiborne County, TN newspapers are digitized
Organizational Searches such as Historical Societies Have not looked recently, need to recheck local libraries
DNA ThruLines to John Y. Estes, father of Lazarus Estes Ancestry 5 Proven via 35 cousin connections to Lazarus’s parents through 3 of John’s siblings
DNA Lazarus Estes ThruLines at Ancestry through Lazarus’s children Ancestry 5 20 matches, 9 through William George, 7 through Cornie, 5 through Charlie Thomas Estes
DNA at FamilyTreeDNA My autosomal matches to Buster Estes, Lazarus’s grandson FamilyTreeDNA 5 Including 556 matches in common and many triangulated segments to descendants of Wm. G., Lazarus, John Y. Estes and upstream ancestors
Other Relationship to wives and children Letters from Aunt Margaret 3 or 4 Clearly states relationship of William G. and Lazarus
Other Relationship to wives and children Letters from William G. to my father 3 or 4 Clearly states relationship of William G. with his siblings and family members

Some types of information are notably unreliable. For example, obituaries may omit people or confuse relationships. William George Estes’s obituary omits his daughter and incorrectly notes her husband, his son-in-law, as William’s child.

Death certificates often give parents incorrectly, especially the mother’s birth surname.

The names of parents in both obituaries and on death certificates are often third-hand information provided by people who are at least two generations removed and are under significant stress at that time. My mother’s obituary was republished two times due to errors made AFTER I provided correct information.

We have several pieces of information that strongly suggest that the William George Estes who was born to Lazarus Estes and Elizabeth Vannoy is the same William George Estes that married Ollie Bolton, but there’s more.

We know for sure that William Estes, who married Croshie/Crosha Brewer, is the same person because his parents are given in the county marriage record book. This is first-hand information and judged to be more reliable because we can reasonably expect that William George knew who his parents were, or at least who they were supposed to be.

If we discount entirely the fact that my aunts personally knew Lazarus as their grandfather, and look only at the paper evidence, we just need to tie William George in his later life to the same William George in his earlier life.

Here’s a photo passed from William George’s daughters to me. Cornie Epperson’s grandchildren had this same photo showing William George Estes with his sister, Cornie Epperson.

Here’s another with Will Estes and Cornie’s husband, Worth Epperson.

Cornie’s children told many stories about their Uncle Will, who rode the bus from Harlan County to Claiborne County, as he didn’t drive. The legendary favorite story was about the time that Will had a bullet in his shirt pocket. It accidentally got mixed into his pipe tobacco, which he put into his pipe and was smoking on the bus.

Yes, the bullet blew up. No one was hurt, and miraculously, the driver didn’t crash. Nevertheless, Will was banished from riding the bus forever thereafter.

That story alone connects the William George Estes living in Lynch, in Harlan County, as the same person, as do his children from all three wives. So do letters from my aunt to family members discussing several people involved, and letters from Will himself in the early 1960s detailing some pretty spicy antics.

However, we’re looking for more than oral history. What other documents do we have?

The Smoking Deed

This deed serves, in essence, as the will of Lazarus Estes and his wife, both of whom conveyed this deed.

Thankfully, it identifies both Cornie and William as their heirs, along with several other children, although it never actually states that the people mentioned are their children. The census confirms that these people, Cornie and William George, along with Martha (Estes) Norris, Charlie Estes, and Lum (James Columbus) Estes mentioned, are their children.

If you’re still wondering if William George Estes is their son, notice the release of lien, stamped on the upper left-hand side of the page decades later, in 1957, with his signature.

This signature matches Will’s other handwriting on letters that he sent in the 1960s, in my possession, and on my father’s delayed birth certificate signed in 1952.

This document provides their relationship, the type of evidence submitted, and both of their addresses and signatures. Evidence doesn’t get much better than this.

For additional signature confirmation, William G. signed his 1918 draft registration in Claiborne County. In Harlan County, KY, in 1957, he signed the delayed birth certificate for his son, Estle, who was born in Springdale, Arkansas, in November of 1894.

When Evidence Isn’t Conclusive

Unfortunately, this situation happens often, especially with generations further back in time where less information is available. Let’s look at an example.

Genealogists tried for years, decades actually, to identify the parents of John R. Estes.

His son was named John Y. Estes.

No one knew what the R. stood for, nor what the Y. stood for. Truthfully, we still don’t, at least not for sure.

Here’s what was said:

  • John R. Estes’s mother was Mary Younger, who was married to George Estes. This claim was made because John R.’s son was named John Y. Estes, the Y. standing for “Younger.” That was the hypothesis, but it was stated as fact.
  • The middle initial R in John R. Estes stands for Regan or Reagan because his grandson, John Reagan Estes, son of John Y. Estes, was “named for his grandfather.” This was told to me by his grandchildren who were living in the early 1990s, as information they were told.

I fully understand why one would think those are possibilities or why conclusions might be drawn. They are clearly possibilities, but without additional evidence, that’s all they are. Eventually, that possibility begins to be passed along as a fact. Then, people don’t want to question what was passed down from “people who should know.”

So, let me play devil’s advocate here.

The Y in John Y. could stand for any number of things. For example, the surname Yancey is also found in Halifax County, Virginia. Y could have come from anyplace. At that point in time, we were searching for the parents of John R. Estes, so Mary Younger seemed to make sense.

Having said that, we now know that John Y. Estes’s grandmother WAS Mary Younger, BUT, that does NOT mean that the Y. stands for Younger, nor does it serve as any kind of concrete evidence.

Might it stand for Younger? Yes, of course. But the Y itself serves only as a potential hint.

Can you use it for evidence? Nope, not without more information. I’ve searched high and low, so if you find “Younger” in a reliable record for this man, by all means, let me know. While confirmation would be wonderful, we really don’t NEED to know like we do with Reagan.

John Reagan Estes (1871-1960), the son of John Y. Estes, could well have been named for his grandfather, John R. Estes (1787-1885). John was his father’s first name as well as his grandfather’s. That does NOT mean that that Reagan was John R. Estes’s middle name. We have no idea where Reagan comes from. If I had a letter from John Reagan’s mother or sister, for example, saying John Reagan was named for his grandpa Estes, who was also named John Reagan, that would be evidence because we have a contemporaneous source and know the information wasn’t assumed or constructed later to “fit” the question about John R. Estes’s middle name.

I have dug for years for any Reagan connection to the Estes line, or to the wives’ lines in upstream generations in Virginia, hoping to prove that Reagan genealogical connection. I have never found it, although that clearly doesn’t mean it’s not there. For all we know, Reagan could have been the name of the preacher or the doctor who delivered someone. It may or may not have anything to do with John R. Estes, and even if it does, Reagan may not be an ancestral surname.

So, if you’re taking yourself down the path of ascribing too much weight to information that may or may not be evidence – don’t. What you can do that’s beneficial is more research. If you think the Y or the R might be a hint, DIG!!! You just might find that evidence. If you haven’t utilized the new FamilySearch full-text AI search, by all means, do. These are the perfect types of situations to research using this amazing tool.

Treat everything as a hint, but it’s not evidence until it’s confirmed.

While we’ve since proven that, indeed, John R. Estes is the son of Mary Younger using other types of evidence, the middle initial R. and the middle name Reagan two generations later still is and may remain a mystery.

In the Weeds

At this point, you might be thinking that we are SO FAR DOWN IN THE WEEDS, and you’d be right, but the answers to our specific question are found here.

Our original goal was to prove that William George Estes was the son of Lazarus Estes and Elizabeth Vannoy.

The items bolded in red in the Individual Proof Table for William George Estes, above, individually and certainly cumulatively “prove” that relationship, as far as a paper trail can go.

The other information, especially taken together, supports that and, more importantly, does not dispute or provide contradictory or conflicting evidence about any of the other evidence. In other words, we have concensus.

Lineage Proof Table

The table below is designed to document the proof that the individual listed under the name column is, in fact, the child of the father and mother below. Other information from the Individual Proof Table that we completed above is omitted because it’s not needed in a Lineage Proof Table.

The Proof rows between the child and their parents are the proof, or the best evidence we have, that connects the child conclusively to the parent or parents. Sometimes that proof can arrive indirectly, such as a sibling’s obituary that lists your ancestor as their sibling – allowing you to connect the sibling who died and your ancestor both to their parents through the census or other documents.

Proof listed will vary and could be personal knowledge (someone you knew within your lifetime), a Bible, a will, a deed, an obituary, a church baptismal document, a pension application, census records, and more.

The best proof, of course, is multiple contemporaneous pieces of evidence.

Proof can also be negative proof. For example, if there was a will but this person was missing, that should be noted. However, that alone is NOT negative proof, as sometimes a child who had already received their inheritance was not mentioned. It does need to be listed because, when combined with other evidence, it may become very important. So is the wording of the will. For example, does it say “all my children,” but omit the person you’re searching for?

Proofs also must take into consideration things like individuals with the same name. In other words, we need to prove that THAT particular John was the son of THAT particular George.

There are times when one must dig deeply as well as far and wide, using siblings and the FAN (friends and neighbors) methodology to reveal a nugget or put enough information together from multiple sources to prove a relationship collectively. For example, I have found proof two generations downstream in Virginia chancery suits that detail the descendants of someone who died and left a will two or three generations earlier.

If this Lineage Proof Table was for my own use, I would utilize a spreadsheet, and I would provide links and more detailed information. For ease of use in this article, I’ve constructed a chart here.

The entire purpose of this lineage document is to unquestionably connect the generations. If these proofs are strong and unquestionable, the only piece of evidence that could upend all of them, together, is an unknown DNA event where a parent or parents are not the individuals reflected in the non-genetic proofs.

Name Birth & Loc Death & Loc Father Mother DNA Confirmed
Me William Sterling Estes Separate lineage proof for mother’s line Father confirmed via paternal half-sister’s children and cousins’ autosomal DNA matches..
Proof My birth certificate, newspaper announcements
Proof Father’s obituary
Proof Social Security application after my father’s death
Proof Personal knowledge, photos, and memories
Proof DNA match at the expected level to my half-sister’s descendants and our upstream Estes relatives
William Sterling Estes Oct. 1, 1902 or 3, Tazewell, TN Aug. 27, 1963, Jay County, IN William George Estes 1873-1971 Ollie Bolton 1874-1955 Autosomal DNA matches to multiple Estes cousins & half-sister’s children
Proof Census and newspaper articles identifying my father as his parents’ child
Proof My father’s marriage license, personal knowledge, and his delayed birth certificate
Proof Death certificate and obituary
Proof Aunts’ knowledge and family letters
William George Estes March 30, 1873, Tazewell, TN Nov. 29, 1971, Harlan Co., KY Lazarus Estes 1845-1916/1918 Elizabeth Vannoy 1846-1918 Autosomal DNA triangulated to multiple descendants of both Lazarus Estes and Elizabeth Vannoy.
Proof Deed to Worth and Cornie Epperson where Lazarus lists William George Estes as one of his heirs – Claiborne Co., Deed Book M2, page 371.
Proof Various censuses showing parents and siblings, including sister Cornie Estes Epperson
Proof Marriage license to Crocie Brewer lists his parents
Proof Cousin George Estes knew these people and was at the funeral of Lazarus when he was a child, plus Aunt Margaret’s letters
Lazarus Estes May 1845, Claiborne Co., TN 1916-1918, Claiborne Co., TN John Y. Estes 1818-1895 Rutha Dodson 1820-1903 Y-DNA confirmed to haplogroup of Moses Estes, autosomal triangulated to descendants of Lazarus and Elizabeth and upstream ancestors through multiple matches.
Proof 1850 and 1860 census with his parents, 1870 census where he lives one house from parents with wife and children, 1880 census where his wife is still living a few houses from his parents, with their children, and John is found in Montague Co., TX
Proof October 1865 deed where John Y. Estes deeds all his possessions to his eldest son, Lazarus. Claiborne Co., Deed book B1, page 37
John Y. Estes December 29, 1818, Halifax Co., VA Sept. 19, 1895, Montague Co., TX John R. Estes 1785/88-1885 Nancy Ann Moore c 1785-1860/1870 Y-DNA confirmed through multiple sons. Autosomal triangulates to several descendants through multiple lines of other children.
Proof Personal written knowledge of Claiborne County attorney, P. G. Fulkerson, published in the local newspaper who listed parents, wife, siblings, and children of John Y. Estes and wife and children of John R. Estes
Proof John R. Estes signed as a witness for John Y. Estes in 1865 when he deeded goods to son Lazarus “for natural love and affection.” In 1850 census John R. Estes lives near sons Jechonias and John Y. Estes
Proof John Y. Estes’s and John R. Estes’s death conveyed in letters between family in Claiborne County, TN, Texas, and Oklahoma
John R. Estes 1785-1788, Halifax Co., VA May 1885, Claiborne Co., TN George Estes 1763-1869 Mary Younger  ~1775-1820/1830 Y-DNA confirmed through multiple lines. Autosomal confirmed triangulation of multiple lines of his children and his ancestors. Descendants’ DNA triangulates to that of Nancy Ann Moore’s ancestors.
Proof Halifax County 1812 personal property tax list where John R. Estes is listed as the son of George Estes and lives next to him.
Proof Halifax Co., VA chancery suit dealing with property of Moses Estes, father of George Estes, lists John R. and his wife’s name and location in Tennessee as Moses’s descendants.
Proof War of 1812 pension application
George Estes Feb. 3, 1763, Amelia Co., VA July 1859, Halifax Co., VA Moses Estes Jr. 1742-1813 Luremia Combs c1742-1820/1830 Y-DNA haplogroup descended from Moses Estes Sr. 1711-1787 and autosomal from his maternal and paternal lines, both.

I’ll stop here because you clearly understand the process. If I were applying for membership in a lineage society, I would simply continue this chart until I reached the individual in question. In this example, George Estes is a Revolutionary War soldier, so I could apply for DAR membership, assuming I meet their various criteria.

Another aid in documenting your ancestors is lineage organizations and their records, but keep in mind that their evidence, especially that submitted decades ago, may not be sufficient today.

DNA Confirmation

DNA can either confirm this relationship, even without a paper trail, or conversely, it can burn it all down.

The closer in time a DNA relationship is, the more likely you’ll be able to confirm it using autosomal DNA.

Sometimes, Y-DNA is a consideration, and it certainly would be in this circumstance, except that I’m not a male, and we don’t have a living Estes male descended directly from William George Estes (through all males) to test.

Mitochondrial DNA can’t be used in this circumstance either since William George Estes’s children have their mother’s mitochondrial DNA, not his.

For the purposes of today’s proof, I used the Family Finder autosomal DNA test.

Buster Estes, now deceased, grandson of Lazarus Estes through his son Charlie Tomas Estes, is my 1C1R, (first cousin once removed). He tested both his Y-DNA and took the autosomal  Family Finder test for me many years ago.

Additionally, Cornie Epperson’s grandchild and great-grandchild, my second cousin and 2C1R, agreed to autosomal DNA testing for me as well. Cornie’s grandchild agreed to test their mitochondrial DNA, which descends from Elizabeth Vannoy – for which I remain immensely grateful.

All of these cousins match me, as well as each other, appropriately, as would be expected for their respective relationships to me and to each other.

Since then, additional descendants of Lazarus Estes and Elizabeth Vannoy have tested and match others at the appropriate, expected level.

I also match other descendants of Elizabeth Vannoy’s parents, as do my cousins, so I can literally walk both Estes and Vannoy segments back in time.

In this case, NOT matching close Estes relatives would conclusively prove that I’m NOT related to the more distant Estes family.

However, if I didn’t match, it’s also possible that my father would not have matched those people either. I don’t have a full sibling through my father, but I do have a half-sibling whose descendants I match appropriately for the expected relationship. That proves that I’m my father’s biological child.

My half-sister died before DNA testing. NOT matching my sister’s descendants would confirm that we were not sisters, meaning we did not share the same father. One or the other of us would probably match Estes descendants, such as our second cousins. Fortunately, we match each other and Estes descendants.

Unfortunately, my half-brother Dave did not match me, nor any Estes family members, providing that we did not share a biological father – a heartbreaking discovery. He’s still my brother though, just not biologically, and I loved him dearly. (For the record, I found Dave’s father and his family after his death.)

I can prove that my father descends from his father because I also match the descendants of my father’s paternal half-siblings, as expected.

I also match (and triangulate with) the descendants of my grandfather’s sibling, Cornie Epperson, as expected, which proves my connection back to Lazarus and, therefore, my father and grandfather’s connection to Lazarus, too.

By the time we reach John R. Estes, son of George Estes, we can also use Y-DNA. While I personally can’t test for the Estes Y-DNA, a descendant of John R. Estes has taken the Big Y-700 test, needed for this level of detail, and they match the unique mutation (R-ZS3700) that occurred between Abraham Estes and his son Moses Estes Sr., then descended through Moses Jr. to George to John R., then on to our tester, confirming this paternal lineage.

Furthermore, I and other descendants of Lazarus Estes autosomally match Y-DNA descendants of John R. Estes as would be expected of 3rd or 4th cousins.

Therefore, by proxy, using both Y-DNA and Family Finder, we are all confirmed to descend from this entire Estes lineage, to and including Lazarus Estes and his son, William George Estes, through my father to me.

Whew!!!

Summary

Yes, it was a long, detailed path to get here using both traditional genealogical research and DNA results, but we did, and that’s really all that matters. I probably provided more examples than I really needed to, but I’m trying to answer as many “what about this” questions as I can, in advance. The Proof Table methodology isn’t cast in concrete and is easy to replicate and adapt based on your situation and the records at hand.

My final word of caution would be to make sure you don’t discount or omit negative evidence inadvertently. I made that mistake when I was less experienced because I didn’t realize the importance of negative evidence.

I’ve seen situations where a resource was not recorded because there “was nothing there,” when the fact that “nothing was there” is in itself important negative evidence that needs to be weighed and considered.

That’s one reason why preparing a list of all the resources in a particular area is so important. When you discover new resources or they become available, be sure to record and check those resources. For example, if a tax list for a particular county or district is uncovered, record that resource, even if the person you’re seeking isn’t listed there. The next question to ask is why they would not be listed, which may lead you to seek out or perhaps reevaluate other information.

Future Topics

I have three more articles planned in this series and expect to publish the next one in the winter.

  • DNA as Proof – or Not
  • Leveling up
  • Writing it Up

______________________________________________________________

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. Just look for the black “follow” button on the right-hand side on 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 Books

Genealogy Books

Genealogy Research