RootsTech 2023 – Truly United

Finally, finally, we were on our way, winging our way across the world from near and far – flying and motoring into snowy Salt Lake City for RootsTech. It seemed like we had been preparing forever, and Murphy visited many of us as gremlins trying to keep us away – but we persevered, and Murphy’s ploy just didn’t work.

Grab a cup of your favorite beverage, because you’re going to RootsTech with me!

I started out very early in dense fog which was a precursor to a nightmare at the airport. We didn’t know that yet, and the sun emerged beautifully as we were on our way.

Utah was blanketed with snow a few days before our arrival. We were hoping for no more snow.

The snow cover made for stunningly beautiful photos from the air.

The Kennecott Copper Mine outside Salt Lake City is three miles wide, nearly a mile deep and looked very interesting and beautiful laced with snow. These terraces are actually roughly 500 miles of dirt road. This used to be a mountain that was 8400 feet in elevation.

During the flight, I read about my ancestor, Stephen Hopkins and couldn’t help but think about how shocked he would have been that I flew across the country some 413 years after he was shipwrecked in Bermuda on the way to Jamestown, eventually lived in Jamestown for 4 years, sailed back to England, remarried, then arrived on the Mayflower in Plymouth Colony.

His ships and mine were very, very different.

FamilySearch Library

Some of us arrived early for research or meetings, or both.

FamilySearch took the opportunity presented during the Covid shutdown to remodel and upgrade the facilities significantly. The new library is both beautiful and super-functional.

The workstations now have three monitors.

There’s a lovely new break room with vending machines, tables, and a fridge.

To put things in perspective, the break room is larger than the preserved pioneer cabin that stands beside the library.

I’m struck by the contrast of the small cabin standing beside the FamilySearch library at left, and museum at right, and just a block away from skyscrapers.

Rather than leave and waste valuable research time, we had a picnic lunch in the break room.

I went to Salt Lake City early to visit the FamilySearch Library and attempt to break down a brick wall. I think I might have done that. We will see.

Other researchers did the same thing, and you can view a special GenFriends episode, here, hosted by Cheryl Hudson Passey, where several of us shared our excitement about our research, discoveries and simply gathering together again.

I was very excited to meet my cousin, Audrey Hill, for the first time in person, at the library. We’ve been collaborating for several months on our John Hill (1737-1805) and Catherine Mitchell (1738-1827) line. She’s already following up on a lead I never did (my bad.) Go Audrey!!

I spent two days perusing book after book after book in the Virginia and Maryland counties where my Dobkins and Johnson ancestors were known to have lived, then moved to the historically adjacent counties.

I was incredibly discouraged, but on the evening of the second day, back at my hotel again, I reviewed all of the library resources and noticed that I had missed one book that was shelved elsewhere.

Glory be, I *think* I’ve found him and his family.

My Peter Johnson line’s Y-DNA matches the Jochimsson (Yocum) line, so I have a LOT of work to do. But now at least I know where to dig!

I needed this entire book, not just a few pages.

Fortunately for me, Jim volunteered to scan the entire book at one of the new book-scanning stations.

I’m SOOO excited.

RootsTech and the FamilySearch library ran golf carts back and forth between the facilities throughout the conference.

Decisions, decisions.

Well, if you can’t decide, just go to the chocolate shop to think things over😊

The Night Before

Preconference events began on Wednesday evening with the media dinner which allows us to understand the layout, when to be someplace, and where that place might be. It also allows provides accurate information to pass on to you.

Of course, many of us have known each other for years. As the first event of RootsTech, after three years of being apart, it felt like one huge family reunion with everyone catching up. So many hugs!!!

And selfies.

It was wonderful to see Marie Cappart again. I’ll never forget walking down the street in Amsterdam with two friends and hearing someone shouting my name from some distance away. I turned around and there was Marie, running toward me, arms outstretched. What are the chances??

The influencers and media were treated to a tour of the show floor after setup was supposed to be complete.

Finishing touches were being put on the Expo Hall and booths. I guess I never realized how large these booths are and that they actually have to be “constructed”.

The next morning, the show would open and thousands of excited genealogists would descend on the Salt Palace for the next three days.

RootsTech Opens

Finally, the Salt Palace, with its legendary signs outside, was ready to receive genealogy guests.

Everyone was so happy to see each other again. My friends, Janna Helstein, Schelly Taladay Dardashti and Daniel Horowitz with MyHeritage photobombing the group. This was the best of several photos because we were all joyfully laughing so hard.

The absolute best part of RootsTech 2023 was seeing people again, in person. Zoom and similar platforms have been sanity-saving for the past three years – but they aren’t people.

Humans are, I think, wired for connection to each other.

I’ve worked “home office” for decades now, but not without regular contact with others.

The classes were great and there was a lot that was wonderful at RootsTech – but hands down, the best part was hugging so many people.

In case you aren’t aware, genealogists are huggers.

If someone were to have followed me around taking photos, there would have been hundreds of hugs. And I don’t mean polite greeting distant hugs. I mean the “OMG I haven’t seen you in a lifetime and everyone was concerned we might never see each other again” holding tight, never-letting-go hugs.

Mags Gaulden and I spotted each other in front of the WikiTree booth, and some kind soul took our picture. I tried to do a nice thing for her and made DNA masks, not remembering that she was allergic to my cat assistants. Thank goodness Mags realized it quickly enough to remove the masks before they had the opposite of the intended effect. I really do not want to be listed in her obituary! “Cause of death: Roberta’s masks.”

Tears streamed down people’s faces as they saw each other, especially that first day. And I don’t mean because of cat hair, either.

There were thousands of selfies joyfully taken. Lots of “blooper” ones too, but just the giddiness of being together again was intoxicating and overshadowed the challenges of the past few years. For a minute, or a few, everyone could just forget about everything else and enjoy our three-day adrenaline high.

And of course, sometimes things change, and many people weren’t there, for a variety of reasons. I missed so many people and there was more than one moment of silence.

Attendance

Here’s the RootsTech Expo Hall from the second floor. It felt like “coming home” after a long absence.

I was standing inside when the doors opened on the first day. People were waiting, but not the mob like past years.

In a Zoom call with RootsTech staff a week or ten days before the conference, they said they had 6000 paid admissions at that time, and a week or so later, they said they were anticipating the same number of attendees as 2020 which was about three times that number.

That number was clearly aspirational, but it didn’t happen.

I’ve been attending RootsTech since 2018, and the actual in-person attendance, based on observation, was lower than it has been since I’ve been attending. Of course, while we may be getting used to Covid, it’s not over and still a significant concern to many. I had my doubts.

Now that I’ve said that about attendance, let me expand. There were over a million registered online for the virtual sessions PLUS the livestreamed sessions that were held in person as well. I don’t know how many more than a million attended, but that number will only grow because those sessions remain available for viewing after RootsTech. In other words, Rootstech sessions have become a library which you can find and enjoy, here.

Clearly, more people in total were reached in 2023 than in 2020.

Questions for Attendees

This year, I had three in-person classes, and no virtual classes. All three were well-attended.

I don’t know how many people attended my sessions, but I know I took about 2000 DNAeXplain ribbons that were passed out to attendees at the exit doors of my classes if they wanted them for their RootsTech badges. I brought home maybe 100.

After everything is set up for the session (thank you Jim,) I always chat with the people in my sessions that show up early. There’s no reason not to have a little fun for everyone.

My first session was at 9:30 the first day, right after the conference opened at 9. I was passing out ribbons personally to people who were early and I saw the confused looks. So I demonstrated what to do with the ribbons with my own badge.

Ribbons on badges are a RootsTech staple, and it’s the only conference I’ve ever attended with that tradition. I realized, based on the confused looks, that we had several first-time attendees.

I was so excited to welcome people at the beginning of my first session, back to in-person genealogy, and that feeling was palpable throughout the room and the conference as a whole.

How Many First-Time Attendees?

When my session started, I asked how many people were attending RootsTech for the first time, and I was very surprised to discover that roughly half the room raised their hands.

Half!!!

That’s HUGE. No wonder there were so many confused looks about the ribbons.

My three sessions, in order, were:

  • DNA for Native American Genealogy: 10 Ways to Find Your Native American Ancestors
  • DNA Journey – Follow Your Ancestors Path
  • Big Y for the Win

I mention this because of the next questions I asked.

Who Has Taken a DNA Test for Genealogy?

In the first session, “DNA for Native American Genealogy,” I asked who had taken a DNA test, and more than half raised their hands, but several had not. Frankly, that surprised me given how long DNA testing has been available now. I talked to people afterwards, and the common thread for those who had not seemed to be:

  • They didn’t know which vendor or which DNA test to take for this purpose.
  • They thought the ancestor was too far back in time and they would not have any Native results. In my session, I talked about testing the older generations and your cousins. Also, that you don’t know what you don’t know. I asked how many people would purchase a book if they thought the answer to that question even MIGHT be inside, and every single person raised their hand.

I also pointed people to the Native section on my blog, to my book, DNA for Native American Genealogy, and to my second blog focused entirely on early Native American records, www.nativeheritageproject.com.

In the second class, “DNA Journey – Follow Your Ancestor’s Path,” probably three fourths of the class had taken a DNA test. That session was really fun. I used several case studies to illustrate how different kinds of DNA have broken down brick walls AND showed me exactly, and I mean literally exactly where my ancestors were from. I used Y-DNA, mitochondrial DNA and autosomal to accomplish this. Who among you DOESN’T want to stand where your ancestors stood?

Yep, we all do.

I think it was in the second class that I asked a question about how many people had taken the three different types of tests, and here’s the breakdown:

  • Who has taken a DNA test? – The majority of the room
  • Who has taken an autosomal test – It looked to be the same number of people as above
  • Who has taken (or sponsored) a Y-DNA test – Maybe 10% of the room
  • Who has taken a mitochondrial DNA test – A scattering of people

As genealogists, we need to do more Y-DNA and mitochondrial DNA testing, because we don’t know what we don’t know and may well be missing.

In the third class, “Big Y for the Win,” which included both Y-DNA STR testing and the Big Y-700, comparing and contrasting the tests, how to use them, and why the Big Y provides significant advantages, most of the people had taken some type of DNA test.

The second question I asked in the Big Y class was how many people had taken or sponsored a Big Y test, and significantly more than half had, which is what I would have expected.

However, given the session topic, I was surprised to learn that few had used the new, free, Discover Tools, or the recently released Group Time Tree. Both were developed and created by FamilyTreeDNA to maximize the usefulness of Y-DNA haplogroups, and they are amazing.

How Many People Have Tested?

As part of the information that I gathered during the conference, Ancestry has tested 23 million people and MyHeritage 6.5 million. I don’t have a current number for FamilyTreeDNA or 23andMe, but the last numbers I heard some months ago were 2 and 5 million, respectively.

There are clearly more (and new) people who are interested in genealogy and are still DNA testing candidates – especially Y-DNA and mitochondrial DNA which have separate inheritance paths, providing additional and unique benefits as compared to autosomal tests.

Keynotes

The keynote sessions were livestreamed, so you can still view them here. Be sure to watch Steve Rockwood’s welcome. He may be the CEO, but he’s an exceptionally caring, inspirational and humble, man.

I attended two of three keynote sessions. Each keynote session actually included three speakers, which was initially confusing.

Steve Rockwood’s message is that “All Means All” – everyone is included. He also thanked and encouraged people to not be further divisive during this difficult time, and instead to choose inclusion.

Steve asked several questions and in answer to his queries, attendees were encouraged to hold up their phones with their flashlight on. As you can see, the entire huge room is filled with light – our light. One at a time. We can all be the light. You can hear Steve’s message for yourself, here.

Another session I enjoyed immensely was Jordin Sparks, the youngest ever American Idol winner. I’ve been in concert venues that were smaller, so it was a real treat to enjoy this inspirational story plus four of her amazing songs.

I really encourage you to watch this video, especially if you love music. Even Jordin’s guitarist was wiping his eyes!

She literally played to a packed house and I don’t think there was a dry eye anyplace.

Jordin has an incredible voice and an inspirational story. Do yourself a favor and listen, here.

MyHeritage Keynote and Announcements

Aaron Godfrey, VP of Marketing with MyHeritage announced new products and initiatives during the keynote on day 2.

The new Photo Dater app, available soon, will estimate when a photo was taken based on clothes, hairstyles and other items in the photo.

Additionally, Aaron announced the cM Explainer, a wonderful new tool which predicts relationship estimates between DNA matches and includes the ages of the testers, among other factors. cM Explainer is incorporated into your DNA matches at MyHeritage in addition to being independently available for free, here.

I’ll be reviewing this new feature in an article, soon.

In another surprise, Aaron announced that MyHeritage has donated another 5000 kits to DNA Quest, for adoptees, here.

MyHeritage also introduced color coding for family trees, here. If you’re a MyHeritage user, this feature is already available for you on your tree, so check it out.

MyHeritage takes the “most new announcements at RootsTech” award with these new features.

Vendor Booth Sessions

Truth be told, I didn’t even get to visit all of the various booths. I meant to, but it just didn’t happen.

At least two vendors offered sessions throughout all three days. There were probably others, but between my three RootsTech sessions, three booth sessions and the book signing, in addition to keynotes, meetings and interviews, I just wasn’t able to attend many booth sessions.

The ones I did attend were wonderful. I focused on DNA, of course. Let’s start with FamilyTreeDNA.

Sherman McRae presented “Unexpected Y-DNA Results” in the FamilyTreeDNA booth where he’s showing how to utilize the Y-DNA Time Tree in the Discover tool, and the Group Time Tree.

You can view Sherman’s main session, Connect the Forefathers, here.

You just never know when a pilgrim is going to show up for your session.

Janine Cloud, an enrolled Cherokee tribal member and manager of Group Projects at FamilyTreeDNA discussed Y-DNA, mitochondrial and autosomal avenues to prove Native ancestors using DNA, using her own Cherokee ancestors as an example.

Dr Paul Maier, Population Geneticist, Goran Runfeldt, Head of Research and Michael Sager, Phylogeneticist answer questions about Y-DNA in the AMA (Ask Me Anything) session.

Paul and Goran also hosted an AMA for mitochondrial DNA as well, an often overlooked but valuable resource.

In addition to the Native American AMA session for FamilyTreeDNA which I gave with Janine, I gave two booth presentations for MyHeritage, “Time Travel with Your Ancestors” and “AutoClusters for the Win,” both of which were recorded meaning you  just might see them in the future.

The Time Travel session utilized the MyHeritage AI tools to see what my ancestors who came from specific regions or cultures might have looked like in that time and place. In the slide above the AI photo of my grandmother is combined with the document and with the Genetic Group that incorporates that part of Germany.

I combined the AI images with MyHeritage records that link those ancestors to a specific location, showing the predicted ethnicity, genetic groups when applicable, and then the actual location – some of which I’ve visited. My ancestor owned that windmill in the Netherlands, above. Combining these tools is so much FUN. My heritage provided the AI photos, records and ethnicity. I’m the one who did the traveling, of course, but in this way, time travel is possible!

I really enjoyed using this story-telling methodology that incorporates all 4 types of genealogy research and clues.

In the AutoClusters for the Win session in the MyHeritage booth, I discussed how I utilized AutoClusters to solve an adoption case in my own family, and how you can use this very powerful tool as well. The methodology I used works equally as well for genealogy mysteries.

In another MyHeritage booth presentation, Janna Helshtein told an amazing and moving story about her grandparents, their escape from the Holocaust, move to Israel, and more – in their own “voices” using MyHeritage’s Deep Story.

We all sat spellbound.

Janna also offers a free guide on how she created and integrated the Deep Story verbiage that her grandparents “spoke.” It was actually quite easy.

There was more to Janna’s story, but I don’t want to spoil it for you.

I believe MyHeritage intends to make their booth sessions available through social media.

Here, Janna and I are celebrating with a quick picnic style lunch after her presentation. She truly knocked it out of the park.

Shifting Attendance

I’m sharing my opinion here, and not anything a RootsTech spokesperson told me.

I was surprised that the in-person attendance was down as much as it was, truthfully. I think in-person was down by either half or maybe even two-thirds. Some decline wouldn’t have surprised me, but this much was sobering.

I was also VERY surprised that roughly half of the attendees were new. And that number could have actually been higher. That’s a good thing, meaning new people are being attracted to genealogy.

These two things, together, suggest the following to me:

  • The passing of time, Covid, and aging-out of some people caused some decline. I know several people who passed away during the past three years, not to mention those whose lives changed dramatically due to their partner’s illness, passing or life circumstances. Several people lost jobs or moved, or both, or are in that process now.
  • Now let’s flip this and say that the virtual and FREE capability for much of RootsTech made the conference accessible and available to many who could not attend in person. For that, I’m very grateful. I have a friend who has been very ill and participated by taking selfies of herself with the livestreamed sessions on her monitor behind her. She posted her photos on social media to be with us. That warmed my heart so much.
  • I think that the reason there were so many new people was because they were able to attend virtually during 2021 and 2022. Essentially this means that while virtual RootsTech was challenging for everyone on the behind-the-scenes production side, to put it mildly, it served to recruit many new genealogists who would not have participated in person had they not previously attended online.

Based on discussions at the media dinner table, and other statements by Steve Rockwood, CEO of FamilySearch, FamilySearch, including RootsTech, is reaching out to young people and to other areas of the world as well.

According to Steve, who, by the way, turns out to be my 11th cousin according to Relatives at RootsTech and the FamilySearch Tree, RootsTech will forever be a blended conference event.

This year, in addition to the local emcee, there were 15 people in other countries hosting in their locations, times and in their native languages.

This year there were 304 virtual classes, 205 in person, and some of those were streamed online as well.

Don’t forget that Relatives at RootsTech is still available through March 31st and you can contact cousins to collaborate. Some may represent Y-DNA or mitochondrial DNA testing lines that you need for matching and to complete your tree.

Vendors

That brings me to the topic of vendors.

Three of the four major DNA vendors were present, meaning Ancestry, FamilyTreeDNA and MyHeritage. 23andMe was absent in 2020 and again this year. Their last DNA innovation was their genetic tree in September of 2019.

Many of the smaller vendors were not in attendance. I had made friends with several of the Mom and Pop vendors and almost none of them were there this year, nor were many of the organizations and smaller companies. I spoke with several people and they said, almost universally, that the cost of the virtual booths over the past two years, the work involved, and the fact that those virtual booths did not generate many sales, not even equal to the amount of the booth rent, had soured the experience.

Not only are conference booths very expensive, so is the invested labor and time. For those of you who don’t know, booth rent is only a part of it. You want carpet? That’s more. A chair? That’s more. Two chairs? More. A trash basket? More. Oh, you need wireless to handle sales? LOTS more.

I’d say that the Expo Hall was only half to one third of the size it had been previously. Mind you, it’s still huge, especially compared to many other conferences, but I missed seeing many of my favorite vendors.

For example, neither Genealogical.com nor Deseret Books were there this year, so there was no bookstore, and neither were many of the fun t-shirt vendors or others that sold jewelry or genealogy-related merchandise.

I hope that FamilySearch will put their creative caps on and perhaps reach out to their vendors, both past and current, and figure out a way to make RootsTech vendors attractive to the online crowd. Perhaps a “search” game where you have to visit vendor booths to find items. Maybe there could be some permanent online stores as well.

There were fewer food vendors too, but in case anyone was wondering, I could still smell cinnamon-almonds throughout the facility😊

I did run into some of my long-time vendor friends.

My friend Jessica Taylor with Legacy Tree Genealogists. I regularly refer people seeking genealogists who understand both genealogy and DNA to Legacy Tree Genealogists.

I don’t need to tell you how much I love DNAPainter and it was great to see Jonny Perl and Patricia Coleman in the DNAPainter booth.

I feel kind of bad because I obviously caught Rob Warthen and Carol Carman by surprise in the East Coast Genetic Genealogy Conference booth, but it’s the only photo I have of their booth.

Last fall’s ECGGC conference was very successful and I’m planning to speak in person this year, in Baltimore, October 6-8, 2023. Save the date. Last year was the first year and it was wonderful.

My Book Signing

FamilyTreeDNA was kind enough to host my book signing for DNA for Native American Genealogy in conjunction with the Native American Ask Me Anything session. Many thanks to Joe Brickey for her help with this event as well.

After the AMA session, which was the final event of Saturday, just before closing, we took a group picture with the FamilyTreeDNA team, or at least the staff members in the booth at that time.

I did learn that perhaps the last thing Saturday might not be the best time for a book signing, because lots of people leave on Friday night. On the other hand, on Saturday, admission to the conference is free, at least to the show floor, with lots of children’s activities and programs for LDS families. Saturday is always very busy in terms of traffic, with sometimes more Saturday visitors than paying conference attendees. It will be interesting to see final RootsTech conference numbers.

The Thank You That Made My Day!!!

One lovely lady, Charis, came up to me after my first session and explained that she saw an ad for RootsTech. She decided she needed to purchase a ticket and attend. She had never heard of me, but she is very focused on documenting her Native ancestry. She sat in the front row in my first session and paid rapt attention. (Speakers do notice, in case you wondered.)

Charis came up to me afterwards and told me that this class alone was worth her registration fee.

She made my day, but I thought to myself that she would attend other sessions that she would find equally as valuable. After all, the conference was just beginning. She found me the next day and repeated what she had said. On day 3, she attended the Ask Me Anything session, arriving early. She said the said the same thing, AGAIN, and I asked if we could take a picture together. As presenters, we take our time, spend our money to attend these conferences, and invest the effort because we want to help people.

People like Charis make this all worthwhile.

Sweetness Personified

I’m sorry, I just can’t resist sharing the sweetest picture series ever.

In 2020, I met my cousin, Heidi Campbell and her baby at RootsTech. Three years later, I saw Heidi again, with a beautiful new addition to the family.

I just can’t tell you how wonderful it was to hold this baby. The last baby I held was Heidi’s little one, three years ago. The look on Heidi’s face is priceless too when he’s reaching for my glasses. He had the biggest smile EVER on his face and he’s booping noses with me. We had so much fun.

My heart just melted into a huge puddle. I so much wish they lived close so I could “grandma.” Thank you, Heidi, for sharing your sunshine with me.

Rolling Up the Sidewalks

On Saturday, literally at one minute after 3 when the conference closed, the workers at the Salt Palace started rolling up the sidewalks, or in this case, the carpets.

It’s a wrap!!!

Afterglow

At the Salt Lake City airport, I ran into two people and had the opportunity to talk to them again and hug goodbye once more. You’d think we would all have had enough of genealogy, but not a chance. More hugs, gratitude for togetherness, and anticipation for next year.

Winging my way home again, having walked about 6 miles each day, according to Fitbit, I was tired, desperately tired, and my everything hurt. However, I was also incredibly fulfilled to have connected again with old friends and met so many new people that I now look forward to seeing again. We are very fortunate to be members of such a wonderful, diverse and universal community.

I couldn’t help but think, as we crossed the winding Mississippi River, how fortunate we are that we have “time travel” in this way. I’m also struck with how many different ways we have to time travel, with Y-DNA and mitochondrial DNA at FamilyTreeDNA, autosomal testing and ethnicity at various vendors, and actual historical records that are becoming ever-more available remotely.

Using artificial intelligence, we can “see” our ancestor’s heritage in our own faces, or, in this case, the face of my grandfather using the MyHeritage AI Time Machine.

Using our DNA, we can identify the parts of those ancestors that we carry today, reaching back in time several generations with autosomal DNA. In addition to autosomal, both Y-DNA and mitochondrial DNA provide close matches and reach back in time, focused on one specific line, providing insights for millennia.

Time travel, truly reimagined.

There are so many ways to discover and connect with our ancestors available to us today. If we don’t carry the DNA of ancestors a few generations upstream, perhaps selected cousins do. We have several tools and databases at our disposal to find testers.

The DNA of our ancestors can and does actually lead us home, to them and, sometimes, exactly where they lived, as I illustrated with several case studies in my presentation, “Follow Your Ancestors Path.” Today, these options are available to everyone.

RootsTech is in the history books for another year, with new friendships made and old ones renewed. Indeed, we were finally reunited with each other, and introduced to cousins we had never met before. We shared tools, methodologies and information to identify our ancestors. We all left fervently hoping to be reunited again next year.

Please enjoy the amazing RootsTech musical finale here.

_____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

More Opportunities at RootsTech 2023 – Book Signing & Booth Lecture Sessions

There are even MORE virtual and in-person opportunities at RootsTech beginning on March 2nd.

Collage graphic courtesy of Dr. Penny Walters

This is sort of like Where’s Waldo, except it’s “Where’s Roberta” at RootsTech 2023.

I’m giving my three RootsTech sessions of course, but that’s not all. I’m appearing for presentations in both the FamilyTreeDNA and MyHeritage booths, plus having a book signing for my book, DNA for Native American Genealogy.

Unfortunately, none of my RootsTech sessions are livestreamed, so please attend in person if you’re in Salt Lake City.

The Expo Hall vendor floor plan is here.

The entire floor plan, including the session rooms is here.

Here’s my schedule, followed by the FamilyTreeDNA and MyHeritage booth schedules. Both have wonderful, free, DNA and genealogy sessions.

Roberta – Thursday March 2

9:30 – 10:30 AM – DNA for Native American Genealogy – 10 Ways to Find Your Native American Ancestor – Room 155A

1 – 1:30 PM – Time Travel with Your Ancestors – MyHeritage Booth

3 PM – DNA Journey – Follow Your Ancestor’s Path – Room 255B

Roberta – Friday March 3

1:30 – 2:30 PM – Big Y DNA for the Win – Room 150

4 PM – AutoClusters for the Win – MyHeritage Booth

Roberta – Saturday March 4

1:30 – 2:00 PM – Native American AMA (Ask Me Anything) – FamilyTreeDNA Booth

2:00 – 2:30 PM – Book Signing – DNA for Native American Genealogy – FamilyTreeDNA Booth

About the Book Signing

It’s unfortunate that there won’t be a book vendor at RootsTech this year, but I’ll have some copies of my book along for purchase and signing.

For right now, plan on bringing either $30 in cash, or a check. I’m trying to work out credit card processing, but no promises.

If I run out of books, the show-special pricing of $30 will be honored by the publisher if you order and pay at the book signing.

I’m bringing book plates to sign so I can sign the plate for you, even if you need to order.

If you already purchased the book, come on by and I’ll be glad to sign a book plate for you as well, at least until I run out😊

Expo Hall Opportunities

Many vendors will be offering sessions in their booths, both in person and virtual. Please check them out.

You can register for RootsTech for free which gives you remote access and also access to the Expo Hall if you attend in person. Of course, the paid registration gives you access to the in-person sessions at RootsTech.

I wrote about how to sign up and navigate the RootsTech site, here.

There are a lot more sessions available in the Expo Hall, both virtual and in person, in the vendor booths.

I’m highlighting both FamilyTreeDNA and MyHeritage since they both focus on DNA and have scheduled free sessions from their own specialists plus industry leaders. Most booth sessions tend to be about half an hour.

MyHeritage Hall Lecture and Booth Schedule

Click to enlarge

I’m sure after the virtual Expo Halls opens, their schedule will be available there too.

FamilyTreeDNA Hall Lecture and Booth Schedule

FamilyTreeDNA (FTDNA) published two blog posts, one about the free virtual RootsTech sessions, here, and one about the in-person sessions, here. If you subscribe to their blog, here, you’ll received updates during the week as they feature different sessions. Also, check their virtual booth after the Expo Hall opens.

SLC Local Time Thursday March 2 Friday March 3 Saturday March 4
9:30 (AM) Y DNA: An Overview of your Results – Katy Rowe – Ballroom A – livestreamed Let’s Play Connect Forefathers! -Sherman McRae – Ballroom A – livestreamed
10:30 What You Can Do with DNA – Katy Rowe – FTDNA Booth Native American Roots – Janine Cloud – FTDNA Booth Which Test is Best for Me? – Janine Cloud – FTDNA Booth
1:00 PM FamilyTreeDNA Sponsor Spotlight – Main Stage Y-DNA AMA (Ask Me Anything) – Dr. Paul Maier, Goran Runfeldt, Michael Sager Mitochondrial DNA AMA (Ask me Anything) – Dr. Paul Maier, Goran Runfeldt
1:30 Unexpected Y-DNA Result – Sherman McRae – FTDNA Booth Just in Time for Groups – Jim Brewster – Virtual Live Demo through FTDNA Expo Hall booth Native American AMA (Ask Me Anything) – Roberta Estes – FTDNA Booth
2:00 Book Signing – DNA for Native American Genealogy – Roberta Estes – FTDNA booth
3:00 Unexpected Y DNA Result – Sherman McRae – FTDNA booth
4:00 Which Test is Best for Me? – Janine Cloud – FTDNA Booth

Rootstech Live Webinars Versus Livestreamed Sessions

There has been some confusion about the difference between RootsTech Live Webinars and Livestreamed sessions, and how to access each. I know this is confusing, so bear with me.

  • It appears that the free virtual registration will give you access to the live webinars, because the speakers and their sessions are listed both under the in-person and the virtual on-demand classes, here.
  • The paid registration gives you access to the sessions that will be given in person and also livestreamed.

There is no list (or filter ability) of livestreamed or live webinar sessions, but it’s easy to see if you go to the list of in-person sessions, here, and look under location where it will say “Live Webinar” if the session is just a webinar. However, this list does NOT tell you if the session is livestreamed.

Let’s look at an example.

Here are the first two sessions for Thursday.

Click to enlarge

The first session listed is a Live Webinar, meaning there is no in person room to visit. This sessions ALSO appears on the virtual list of classes, if you look there.

The second session physically takes place in Ballroom A. If you click on the session, and scroll to the bottom, you’ll see this statement about livestreaming. That means you go to Ballroom A if you are in SLC or you can view the session by visiting this link and clicking at the red arrow to join. I believe these will be available later too, but I have no confirmation of that.

This session is NOT listed in the free “on demand” sessions, so I believe any in-person session is only available with a paid registration.

The message is to plan your RootsTech sessions in advance.

Over and Out Until RootsTech

How can it possibly just be just four days until RootsTech. The suspense builds every single day because we know there will be announcements and it will be wonderful to see our genea-friends in person again. It feels like it has been forever.

This is it for me until RootsTech. My schedule is absolutely jam-packed slammed busy, but I will try to write and publish something everyday so you folks can “come along” with me.

I have a media pass this year, so I’ll be trying to grab photos of people, including the main stage speakers, and asking what are hopefully relevant questions. Maybe some behind the scenes things too. I’m not sure how much access we have.

There are sure to be some interesting surprises, planned or unplanned. There always are. Personally, I’m just extremely grateful that RootsTech wasn’t this week, given their 2 feet of snow, or I would have been interviewing people in the hotel lobby and maybe coordinating games of Euchre or perhaps modifying Jeopardy for “Who’s Your Ancestor?” “I’ll take pilgrims for $200.”

It would be miserable to be snowed in literally one block from the FamilySearch Library and not be able to get there. Mother Nature, hopefully, has gotten this out of her system as this week promises to be less weather-challenged. Knock wood!

____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Relatives at RootsTech – How to Use & Connect with DNA

Relatives at RootsTech is back and I’m so very glad to see it.

Let me show you how to use this wonderful tool, including tips for how to get even more out of the experience.

It’s important to start now to accumulate your cousins, because there’s a display limit of 300 in each category, so you’ll want to begin recording your findings so that as more people sign up and are added to your list, you don’t “lose” the earlier relatives.

Let’s start with my link. Click here.

You’ll be prompted to sign in to your FamilySearch account, or create one. If you don’t have an account, create one now.

Right now, the number of participants is doubling every few days.

Let’s take a look at how Relatives at RootsTech works and how it can benefit you.

Surnames

At first glance, the surname tool doesn’t look terribly exciting, but there’s a hidden gem, especially for newer genealogists.

I entered my surname and one other, knowing there is probably no common locations other than the US. Kvochick is very rare and unique.

The results show two interesting things. First, the genesis of the surname, and second, the total number of people in the FamilySearch tree in both of the common locations for both surnames.

Be sure to try variant spellings too.

After you sign in, you’ll be asked to update your profile which is how you join in on the fun. If you signed up for Relatives at RootsTech last year, that doesn’t count for this year. You need to opt-in for this year’s festivities.

RootsTech Relatives

After you sign in, you’ll see how many of your relatives have joined.

Of the 60,461 total who have joined, according to the FamilySearch tree, I’m related to about 15% of them. That sure gives new perspective to how many people we’re related to. And just think if those brick walls didn’t exist. We’d be related to just about everyone. Far enough back, we’re all related, literally.

Your Relatives at RootsTech are displayed in three ways.

By location, ancestor or family line.

Relatives by Location

Your first view will be by all locations (including people who did not select a location,) but displayed in closest to most distant relationship order. For me, that’s the most interesting part.

These people, my closest relatives, are the people most likely to have critical pieces of information that I don’t have or know about. Like family stories, or photos, for example.

I know one of these people, but not the rest. I’m dying to know who they are and how we are related.

For me, the map itself isn’t terribly useful, but it would be if some members of your family were from distinct locations.

Not everyone opts in to have their location displayed. The “173” in the center is the people who generically selected United States.

Relatives by Family Line

The Family Line display shows you the number of people by parent or grandparent. Unfortunately, you can only view 300 of your matches in each line, which is disappointing.

However, there’s a better way to view your relatives.

Relatives by Ancestor

For me, the best way to view relatives is by ancestor. This also circumvents the 300 limit to some extent, unless you have more than 300 relatives for any one ancestor.

I have two relatives who also descend from Curtis Benjamin Lore. It’s Jen and Jill again, my closest relatives.

I’m quite interested in these people, because Curtis is my great-grandfather and he was a very interesting man. I know Jen and Jill are interested in genealogy too, or they would not have signed up for RootsTech Relatives, this year, in the past few days. This is not a stale list.

I’ll be messaging them as soon as I’m finished with this article!!!

Please note that FamilySearch does not label half-relationships accurately.

Jen and Jill are my HALF second cousins twice removed, which will affect the expected amount of shared DNA. Their ancestors, Edith and Maude were half-sisters through their father, not full sisters. One of the reasons I’m so interested in communicating with Jen and Jill is because I’m not at all sure that those half-sisters knew each other existed.

Maintaining Contact

For each relative found, you can view your relationship, message them, or add them to your contact list. Be aware – your contact list “saves” this person, but it does not tell you how you’re related. That’s where either a Word document, with screen shots of how you’re related, or a spreadsheet where you can detail that information is important.

If you have messaged people in the past, those messages are still in your message box in the upper right-hand corner.

I generally provide my email address when I message relatives.

Displaying the Relationship

If you click on the “Relationship” button, you’ll see how FamilySearch believes you’re related to each match.

My relationship with an Acadian cousin, beginning with our common ancestor, is shown above. Grab a screen shot so you can remember. I drop them into a spreadsheet or Word document.

These matches are based on FamilySearch’s one world type of tree. I don’t have to tell you to be cautious because, like any tree, there are erroneous connections. This connection, at least on my side (left hand,) seems to be accurate. I don’t have Jeanne Chebrat’s second marriage to Jehan Piorier in my file, so I’ll need to check that out. Many times FamilySearch, WikiTree, Ancestry, or MyHeritage has connected documents or sources. In this case, here’s the WikiTree entry for Jeanne.

See, I’ve found something interesting already.

Search for People

On the toolbar, if you click on the right arrow, you’ll notice there’s one more option – Search.

If you think one your cousins might be attending, either virtually or in person, you can search by surname. I entered Estes out of curiosity.

This is quite interesting, because some other poor soul is also named Roberta Estes. You KNOW I’ll be messaging her. I’m pretty sure I know who this is, because we’ve been getting mixed up for years. Unless, of course there are actually three of us interested in genealogy.

However, where this Search option really shines is if you’re looking for males who descend from a particular line as candidates for Y-DNA testing.

Bingo!

I suggest doing this name search for each surname in your tree.

The Share Button is Critically Important

Sharing is the key to encouraging people to participate.

This button on the main page is how I generated the link for you to use to see if we’re related.

There’s a “Share” button in several locations. However, you’ll want to be sure you know exactly what you’re sharing. In some cases, it will be the surname comparison information or other information that you’re viewing. 

However, on the bottom of your Relatives pages, Share will generate a message link to/through several programs or apps so people can sign in to see if they are related to you.

You can also just copy the link and send it to someone in a text message or otherwise.

If you generate a message to share, you’ll see what will be posted, so you’ll know for sure exactly what you’re sharing. I wanted to post the link for my friends on Facebook to see if we are related, and that’s exactly what was generated.

If you follow the link to see if we are related, be sure to tell me, or anyone else whose link you follow.

Next, Connect with DNA

Relatives for RootsTech is a wonderful segway into DNA testing.

Remember, with the 300-relative limit, different searches will produce different results including people that won’t be included due to the 300 limit in other searches. Be creative and search in multiple ways. Add your relatives to your spreadsheet or Word document, then record whether they’ve DNA tested, at which vendor(s) and if you match there.

There are various ways to utilize Relatives at RootsTech for DNA.

  • Y-DNA candidates for the direct paternal line for males – The Search by surname can provide you with Y-DNA testing candidates. They may already have tested their Y-DNA with FamilyTreeDNA or their autosomal DNA with at least one vendor, so just message them and ask. Tell them which databases you’re in. Viewing Relatives by Ancestor can be very useful for this same purpose, especially if you have multiple unrelated lines with the same surname.
  • Mitochondrial DNA – the Relatives by Ancestor tool is very useful for locating mitochondrial DNA testing candidates, especially since you can easily see how they are descended from your common ancestor. Mitochondrial DNA is passed from women through all females to the current generation, which can be male or female. Any of your cousins, of either sex, are candidates so long as they descend from your target ancestor through all females.
  • DNA Pedigree Chart – If you’re building your own DNA Pedigree Chart with the Y-DNA and mitochondrial DNA of each ancestral line, consider offering a DNA testing scholarship to people who carry those lines that are missing in your DNA Pedigree Chart.
  • Testing Candidates – Anyone is a good candidate for autosomal testing. No second cousin or closer has ever not matched. Ask your cousins if they have tested and tell them which DNA databases you are in. Furthermore, suggest that they upload their DNA to FamilyTreeDNA and MyHeritage for free to utilize their tools and find matches that aren’t in the other databases. GEDmatch isn’t a testing company, but is another free database where you may find people who tested at Ancestry. Unfortunately, Ancestry does not provide segment information for matching or painting, so hopefully you’ll be able to find your Ancestry matches elsewhere.
  • Databases – Be sure you’re in all of the databases (Ancestry, 23andMe, FamilyTreeDNA, MyHeritage and GEDmatch) so you can be found and you can find your relatives.
  • DNAPainter – If you’re painting your segments at DNAPainter, you can paint your matching segments from 23andMe, FamilyTreeDNA, MyHeritage or GEDmatch. Ancestry is the only vendor that does not provide matching segment information for their customers.
  • DNA Search – If your cousin has used their actual name when registering at FamilySearch, sort by ancestor, then search your DNA matches at the various vendors for that cousin’s name. The beauty of Relatives at RootsTech is that the relationship is already sorted by ancestor, so that piece of the puzzle has already been assembled for you, which is exactly the opposite of most DNA matches. Of course, this does not preclude errors or connections through multiple ancestors.

Limited Time – March 31 is the End

If I had a FamilySearch genie and could get one wish, it would be that they would leave Relatives for RootsTech up and available until the next RootsTech. I need time to work on these relationships.

However, that’s not the case, and Relatives for RootsTech ends on March 31st.

Therefore, it’s important to begin building your spreadsheet, or however you’re going to record your relatives, NOW. Check your list often so none of those precious matches will roll off of your list and become unavailable. Access to the complete relative match list, meaning no 300 limit would be my second wish from the FamilySearch genie.

To preserve the ability to communicate with your relatives, message them now or at least add them to your contact list – WITH A NOTE IN YOUR SPREADSHEET AS TO HOW YOU’RE RELATED. Otherwise, that information will not be available after March 31st.

You’ll want to use the same spreadsheet from year to year, as some of the relatives signing up this year probably did last year too.

Ready, Set, Relatives at RootsTech

Have fun. Be sure to let me know if we’re related and how!!!

____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

ThruLines Suggests Potential Ancestors – How Accurate Are They?

I wanted to evaluate the accuracy of Ancestry’s ThruLines suggested Potential Ancestors when compared with a tree I know is accurate. I conducted an experiment where I created a small tree on Ancestry for a DNA tester that included only the first two generations, meaning grandparents and great-grandparents.

Click to enlarge any image.

This gave Ancestry enough data to work with and means that for the upstream ancestors, Ancestry’s ThruLines suggested specific people as ancestors.

How well did Ancestry do? Are the Potential Ancestors suggested by Ancestry accurate? How do they make those suggestions anyway? Are they useful?

I do have a second, completely separate, full tree connected to my other DNA test, and I do know who those ancestors are, or, in some cases, I know who they aren’t. I’ve had the privilege of working intensively on my genealogy for decades, so I can easily compare what is known and proven, or what has been disproven, to Ancestry’s suggested Potential Ancestors.

We’ll start with the great-grandparents’ generation, but first, let’s talk about how ThruLines works. I’ve previously written about ThruLines here and here.

How ThruLines Works

ThruLines is a tool for people who have taken an AncestryDNA test and who link themselves to their position on their tree. Linking is a critical step. If you don’t link the DNA test to the proper profile, the tester won’t have ThruLines. I provided step-by-step instructions, here.

I want to emphasize this again, ThruLines is a TOOL, not an answer. It may or may not be accurate and it’s entirely UP TO YOU to take that hint, run with it, and verify or disprove. Ancestry is providing you with a hint.

Essentially, the more ancestors that you provide to Ancestry, generally, the better they can do when suggesting additional Potential Ancestors. They do need something to work with. I wrote about that in the article Optimizing Your Tree at Ancestry for More Hints and DNA ThruLines.

If you don’t provide at least your parents and at least your grandparents in a tree, it’s unlikely that Ancestry will be able to provide Potential Ancestors for you.

I added two generations above the parents in this experiment in order to provide Ancestry with a significant “hook” to latch onto to connect with:

  • Other DNA testers who match the tester AND
  • Other people’s trees, whether the tree-owners have tested their DNA or not

So yes, to be clear, Ancestry DOES:

  • Use the trees of other people whose DNA you match AND have the same ancestors in their tree
  • Along with the trees of people you don’t match (or who haven’t DNA tested,) to propose ancestors for you

ThruLines only reaches back to ancestors within 7 generations, meaning the ancestor is the tester’s 5th great-grandparent or closer.

Most suggested Potential Ancestors in ThruLines have descendants who have tested and are DNA matches to you, but not necessarily all.

On your tree itself, the ThruLines “3 people” icon shows on the ancestors that have Thrulines.

Click to enlarge

Looking at this graphic of my tree, you can see that ThruLines ends at the 7th generation, but Potential Ancestors continue to be suggested beyond 7 generations. Note generation 9, below, which is beyond ThruLines but has Potential Ancestors suggested based entirely on other people’s trees.

ThruLines stops at 7 generations, but Potential Ancestor suggestions do not.

In the above example, in generation 7, Michael McDowell (1720-1755) is a known ancestor and has a ThruLine, but his wife is unknown. Ancestry has suggested a Potential Mother for Michael McDowell (1747-1840) who is also the spouse of Michael McDowell (1720-1755).

Here’s the ThruLines suggestion for Michael McDowell’s wife.

Ironically, there are no DNA matches for either Michael or Eleanor. However, there are DNA matches for their child who clearly descends from Michael. This may be an example of a situation where the other testers are beyond the 7th generation, so they don’t show as matches for our tester in Michael’s generation. The other possibility, of course, is a glitch in ThruLines.

(For those familiar with the Michael McDowell (1720-1755) lineage, Eleanor is his mother, not his wife. His wife is unknown, so this Potential Ancestor is incorrect.)

Potential Ancestors Without DNA Matches

A person may still be suggested as a Potential Ancestor even without any DNA matches.

I have seen situations where a parent has DNA matches to several ThruLine ancestors, but their child has the same suggested ancestor with zero DNA matches listed because the child and the match are one generation too far removed to be listed as a DNA match on ThruLines.

Yet, if you search the child’s match list for the individual listed as a DNA match to their parent through that ancestor, that match is also on the child’s match list.

In the chart that follows, you can see that ancestors in the midrange of generations have many DNA matches, but as you approach the 7th generation, the number of matches drops significantly, and some even have zero. That’s because both people of a match pair have to be within the generational boundary for ThruLines to list them as matches.

In some cases, the ancestor is not suggested for the child in ThruLines because the ancestor is the 6th great-grandparent of the child. If you look directly at the child’s tree, the Potential Ancestor may be suggested there.

Points to Remember

  • The difference between ThruLines and Potential Ancestors is that Potential Ancestors are still suggested beyond the hard 7 generation or 5 GG boundary for ThruLines.
  • ThruLines may suggest Potential Ancestors with or without DNA matches.
  • Potential Ancestors, either within or beyond ThruLines must connect to someone in your tree, or another Potential Ancestor or ancestors who connect to someone in your tree.

Incorrect Ancestors and Discrepancies

An incorrect ancestor can be listed in multiple people’s trees, and Ancestry will suggest that incorrect ancestor for you based on the associated trees. At one point, I did a survey of the number of people who had the incorrect Virginia wife listed for my ancestor, Abraham Estes, and the first 150 trees I viewed had the wrong wife. We have church record proof of her death in England before his children were born by his colonial Virginia wife. Garbage in, garbage out.

That doesn’t mean those trees aren’t useful. In some cases, the information “saved” to that person in those incorrect trees shows you exactly what is out there and can’t be correct. For example, if there is a death record and burial for someone, they can’t also be alive 50 years later in another location. Or someone born in 1780 can’t have been a Revolutionary War veteran. Sometimes you’ll discover same name confusion, or multiple people who have been conflated into one. Other times, you may actually find valid hints for your own ancestor misplaced in someone else’s tree. Always evaluate.

You “should” have the same number of matches to the man and woman of a couple if neither of them had descendants with another partner, but sometimes that doesn’t happen. I would presume that’s due to tree discrepancies among your matches or other trees on Ancestry.

If the same ancestor is listed with multiple name spellings or similar differences, I have no idea how Ancestry determines which version to present to you as a Potential Ancestor. That’s why ThruLines are hints. Ancestry does show you the various trees they utilized and allows you to peruse them for hints for that suggested ancestor.

Just click on the Evaluate button. Unfortunately, neither of these trees have any records for this ancestor.

If you click on the tree, you are then given the opportunity to add Eleanor (meaning the potential ancestor) to your tree from their tree.

I STRONGLY, STRONGLY suggest that you DO NOT do this. By adding information directly from other people’s trees, you’re introducing any errors from their tree into your tree as well.

If you click through to their tree, you’ll often find that they used someone else’s tree as their “source,” so misinformation propagates easily. Seeing “Ancestry Family Trees” as a source, especially in multiple records, provides you with an idea of the research style of that tree owner. This also conveys the message to less-experienced researchers that copy/pasting from other trees is a valid source.

Use this information provided as hints and do your own research and evaluation.

Where Do Potential Ancestors Come From?

Let’s view an example of an incorrect Potential Ancestor suggestion and proof-steps you can utilize to help validate or potentially disprove the suggestion.

We know that George Middleton Clarkston/Clarkson is NOT the father of James Lee Clarkson based on Y-DNA testing where the descendants of the two men not only don’t match, they have a completely different haplogroup. They do not share a common paternal ancestor. Furthermore, proven descendant groups of both men do not have autosomal DNA matches.

However, George Middleton Clarkson is suggested as a Potential Ancestor in ThruLines as the father of James Lee Clarkson.

Mousing over the ThruLines placard shows 98 DNA matches to other people who claim descent from George Middleton Clarkson. How is it possible to have 98 matches with descendants of George Middleton Clarkson, yet he’s not my ancestor?

Many people just see that “98,” which is a high number and think, “well, of course he’s my ancestor, otherwise, I wouldn’t match all those descendants.” It’s not that simple or straightforward though. It’s certainly possible to all be wrong together, especially if you’re dealing with long-held assumptions in the genealogy community and trees copies from other people’s trees for decades.

To view the ThruLine detail for George Middleton Clarkson, just click on the placard.

The ThruLine for George Middleton Clarkson has three attributed children with DNA matches. Let’s evaluate.

  • ThruLines Child 1 is my own James Lee Clarkson that has been erroneously attached to George Middleton Clarkson. However, the Y-DNA of the three various lines, above, does not match. That erroneous connection alone counts for 80 of those 98 matches. If all of those people who match me do descend from our common ancestor, James, those matches all make sense.

According to early histories, James Lee Clarkson was believed to be George’s son based on geographic proximity between the state of Franklin in eastern Tennessee and Russell County, Virginia, but then came DNA testing which said otherwise.

This DNA grouping from the Clarkson/Claxton DNA Project at FamilyTreeDNA shows that the men, above, which includes descendants of James Lee Claxton/Clarkson, all match each other.

  • ThruLines Child 2 is Thomas Clarkston who has 17 DNA matches through 7 of his children.

By clicking on the green evaluate button for Thomas, we see that two of the DNA related trees have records, but three do not.

The first tree is quite interesting for a number of reasons.

  1. Thomas Clarkson is found in Lee County, VA, in relatively close proximity to where James Lee Clarkson is first found in Russell County, VA as an adult in 1795.
  2. There is no actual documentation to connect Thomas Clarkson with George Middleton Clarkson who was hung in 1787 in the lost State of Franklin, Tennessee, now Washington and Greene Counties in Tennessee. It has been “accepted” for years that Thomas descends from George Middleton based on information reportedly passed down within that family long before the internet.

The Claxton/Clarkson DNA Project at FamilyTreeDNA shows the Thomas lineage. This lineage reaches back into England based on Y-DNA matches – a huge and important hint for the Thomas descendants that they won’t be able to obtain anyplace else.

Note that Thomas’s Y-DNA does not match that of James Lee Clarkson/Claxton which means these people must match me through a different line. That’s not surprising given that many of the families of this region intermarried for generations.

  • ThruLines Child 3 is David Claxton, who has one DNA match, so let’s look at that by clicking on the green evaluate button.

You’ll see that this ancestor through David Claxton was recommended based on:

  • One DNA match with a tree with 0 source records, and
  • Zero Ancestry member trees of people whose DNA I don’t match, or that haven’t DNA tested

Checking this tree shows no sources for the following generations either, so I have no way to evaluate the accurace of the tree.

However, I did track his descendants for a generation or so and found them in Wilson County, TN, which allowed me to find them in the Clarkson/Claxton Y DNA Project at FamilyTreeDNA.

In the Clarkson/Claxton DNA project, we see that this David Claxton of Wilson County, TN is in a third DNA group that does not match either the James Lee Claxton or the Thomas Claxton line.

Furthermore, look at the hints for the descendants of David Claxton based on the Y-DNA matches. This link appears to reach back to a Clayton in Kirkington, Yorkshire.

ThruLines Conflation

In this case, three men of similar or the same surnames were cobbled together as sons of George Middleton Clarkson where clearly, based on Y-DNA testing, those three men are not related to each other paternally and do not share a common paternal ancestor. They cannot all three be descendants of George Middleton Clarkson.

It’s amazing how much is missed and erroneously inferred by NOT testing Y-DNA. In very short order, we just proved that the ThruLine that connected all three of these men to George Middleton Clarkson as their ancestor is inaccurate.

In defense of Ancestry, they simply used user-submitted erroneous trees – but you have it within YOUR power to search further, and to utilize Y-DNA or mitochondrial DNA testing for additional clarification. This Clarkson/Claxton information was freely available, publicly, by just checking.

You can find surname or other projects at FamilyTreeDNA, by scrolling down, here, or simply google “<surname you seek> DNA Project.”

How Can These People All Match the Tester?

If we know that the male Claxton/Clarkson line is not the link between these matches, then why and how do these people all DNA match the tester? That’s a great question.

It’s possible that:

  • They match the tester through a different ancestor
  • There has been a genetic disconnect in the Claxton/Clarkson line and the match is through the mother, not the Claxton/Clarkson male
  • Some of the other testers’ genealogy is in error by including George Middleton Clarkson in their trees
  • People accept the George Middleton Clarkson suggestion, adding him to their tree, propagating erroneous information
  • The descendants of James Lee Clarkson/Claxton match because he is their common ancestor, but connecting him to George Middleton Clarkson is erroneous
  • The 15 cM match (and potentially others) is identical by chance
  • The Y-DNA disproved this possibility in this case. In other cases, the matches could have been from the same biological Clarkson/Claxton line, but the testers have their ancestor incorrectly attached to George Middleton Clarkson/Claxton. In this case, we can’t say which of David Claxton, James Lee Claxton and/or Thomas Claxton are or are not individually erroneously connected to George Middleton Clarkson, but we know for a fact that David’s, James’ and Thomas’s descendant’s Y-DNA does not match each other, so they can’t all three be descendants of George Middleton Clarkston. Furthermore, there is no solid evidence that ANY of these three men are his descendant. We know that these three men do not share a common direct paternal ancestor.

I recommend for every male line that you check the relevant Y-DNA project at FamilyTreeDNA and see if the information there confirms or conflicts with a suggested ancestor, or if a descendant hasn’t yet tested. I also STRONGLY recommend that a male in the relevant surname line that carries that surname be asked to test in order to verify the lineage.

ThruLine Ranking

I’m going to rank Ancestry’s suggested Potential Ancestors by awarding points for accuracy on their Potential Ancestor ThruLines suggestions and subtracting points for incorrect Potential Ancestor suggestions. This chart is at the end with links to my 52 Ancestor’s articles for those ancestors.

OK, let’s take a look, beginning with the great-grandparent generation.

Great-Grandparents

I entered all of these ancestors and they are connected to their children, the tester’s grandparents. They are not connected to their parents for purposes of this article, although I do know who the parents are, so let’s see how Ancestry does making Potential Ancestor suggestions through ThruLines.

Ancestors (above example) that are NOT framed by a dotted line and who are NOT labeled as a “Potential Ancestor” have been connected in their tree by the DNA tester, meaning you.

The next generations, below, are all framed by dotted lines, meaning they are Potential Ancestor suggestions provided by Ancestry. Potential Ancestors are always clearly marked with the green bar.

Eight 2nd Great Grandparents

In this generation, because I have not connected them, Ancestry has suggested Potential Ancestors for all sixteen 2X Great-Grandparents.

I’ve provided gold stars for the correct ancestor information meaning both the name and the birth and death date within a year or a decade when they died between census years.

Of these 16, three are completely accurate and the rest were at least partially accurate.

I repeated this process for each one of the suggested Potential Ancestors in the 3rd, 4th and 5th great grandparent categories as well, completing a ranking chart as I went.

Ranking Chart

I’ve ranked Ancestry’s accuracy in their Potential Ancestor recommendations.

  • +2 points means the name AND birth and death years are accurate within a year or decade if they died within a census boundary
  • +1 point means that EITHER the name OR the birth and death dates are (mostly) accurate, but not both
  • 0 means uncertain, so neither positive or negative
  • -1 point means that NEITHER the name NOR birth and death dates are accurate but it’s clear that this is meant to be the correct person. In other words, with some work, this hint could point you in the right direction, but in and of itself, it is inaccurate.
  • -2 means that the person suggested is the wrong person

I’ve been generous where there was some question. I’ve linked these ancestors where I’ve written their 52 Ancestors stories. [LNU] means last name unknown. It’s worth noting that one of the trees Ancestry has available to utilize for Potential Ancestors is my own accurate tree with many source documents for my ancestors.

# Generation Ancestry Name & Birth/Death Years Correct Name & Birth/Death Years # Matches Points Awarded Y or mtDNA Confirmed
1 2nd GGP John R. Estes 1788-1885 John. R. Estes 1787-1885 110 2 Yes
2 2nd GGP Nancy Ann Moore 1789-1865 Ann Moore or Nancy Ann Moore c1785-1860/1870 112 1 Need mtDNA through all females
3 2nd GGP Lazarus Dotson 1785-1861 Lazarus Dodson 1795-1861 46 -1 Yes
4 2nd GGP Elizabeth Campbell 1802-1842 Elizabeth Campbell c 1802-1827/1830 46 1 Yes
5 2nd GGP Elijah R. Vannoy 1782-1850 Elijah Vannoy 1784-1850s 82 -1 Yes
6 2nd GGP Rebecca Lois McNeil 1781-1839 Lois McNiel c1786-c1830s 81 -1 Yes
7 2nd GGP William Crumley ?-1859 William Crumley 1788-1859 97 1 Yes
8 2nd GGP Lydia Brown Crumley 1796-1847 Lydia Brown c1781-1830/1840 112 -1 Yes
9 2nd GGP Henry Bolton 1741-1846 Henry Frederick Bolton 1762-1846 152 -1 Yes
10 2nd GGP Nancy Mann 1777-1841 Nancy Mann c1780-1841 134 1 Yes
11 2nd GGP William Herrel 1803-1859 William Harrell/Herrell c1790-1859 31 1 Yes
12 2nd GGP Mary McDowell 1785-1871 Mary McDowell 1785-after 1872 45 2 Yes
13 2nd GGP Fairwick Clarkson 1800-1874 Fairwix/Fairwick Clarkson/Claxton 1799/1800-1874 82 2 Yes
14 2nd GGP Agnes Sander Muncy 1803-1880 Agnes Muncy 1803-after 1880 106 1 Yes
15 2nd GGP Thomas Charles Speak 1805-1843 Charles Speak 1804/1805-1840/1850 60 1 Yes
16 2nd GGP Ann McKee 1805-1860 Ann McKee 1804/1805-1840/1850 60 1 Yes
17 3rd GGP George M. Estes 1763-1859 George Estes 1763-1859 76 1 Yes
18 3rd GGP Mary C. Younger 1766-1850 Mary Younger c1766-1820/1830 75 -1 Yes
19 3rd GGP William Moore 1756-1810 William Moore 1750-1826 72 1 Yes
20 3rd GGP Susannah Harwell 1748-1795 Lucy [LNU] 1754-1832 69 -2 Need Lucy’s mtDNA through all females
21 3rd GGP Lazarous Dotson 1760-1826 Lazarus Dodson 1760-1826 42 1 Yes
22 3rd GGP Janet Jane Campbell 1762-1826 Jane [LNU] c1760-1830/1840 38 -2 Need mtDNA through all females
23 3rd GGP John Campbell 1772-1836 John Campbell c1772-1838 65 1 Yes
24 3rd GGP Jane Dobkins 1780-1860 Jane Dobkins c1780-c1860 22 2 Yes
25 3rd GGP Francis Vanoy/Vannoy 1746-1822 Daniel Vannoy 1752-after 1794 76 -2 Yes
26 3rd GGP Millicent “Millie” Henderson 1755-1822 Sarah Hickerson 1752/1760-before 1820 76 -2 Need mtDNA through all females
27 3rd GGP William McNeil/McNeal 1760-1830 William McNiel c1760-c1817 116 1 Yes
28 3rd GGP Elizabeth Shepherd McNeil 1766-1820 Elizabeth Shepherd 1766-1830/1840 115 -1 Yes
29 3rd GGP William Crumley 1767-1837 William Crumley c1767-c1839 59 1 Yes
30 3rd GGP Hannah Hanner “Hammer” 1770-1814 unknown 60 -2 Have her mtDNA
31 3rd GGP Jotham Sylvanis Brown 1765-1859 Jotham Brown c1740-c1799 100 -2 Yes
32 3rd GGP Ruth Johnston Brown Phoebe Cole 1747-1802 97 -2 Incorrect person but have correct mtDNA
33 3rd GGP Henry Bolton 1720-1757 Henry Bolton 1729-1765 88 1 Yes
34 3rd GGP Sarah Corry 1729-1797 Sarah Corry 1729-1797 80 2 Need mtDNA through all females
35 3rd GGP Robert James Mann 1753-1801 James Mann 1745-? 77 -1 Need Y-DNA
36 3rd GGP Mary Jane Wilson 1760-1801 Mary Brittain Cantrell c1755-? 80 -2 Incorrect but have correct mtDNA
37 3rd GGP John Herrell 1761-1829 John Harrold c1750-1825 19 -1 Yes
38 3rd GGP Hallie Mary [LNU] c1750-1826 18 -2 Need mtDNA through all females
39 3rd GGP Michael McDowell-McDaniel 1737-1834 Michael McDowell c17471840 25 -2 Yes
40 3rd GGP Sarah Isabel “Liza” Hall Isabel [LNU] c1753-1840/1850 27 -2 Need mtDNA through all females
41 3rd GGP James Lee Clarkson 1775-1815 James Lee Clarkson c1775-1815 170 2 Yes
42 3rd GGP Sarah Helloms Cook 1775-1863 Sarah Cook 1775-1863 188 1 Yes
43 3rd GGP Samuel Munsey-Muncy 1767-1830 Samuel Muncy after 1755-before 1820 108 1 Yes
44 3rd GGP Anne W. Workman 1768-1830 Anne Nancy Workman 1760/1761-after 1860 107 -1 Yes
45 3rd GGP Rev. Nicholas Speak 1782-1852 Nicholas Speak/Speaks 1782-1852 93 2 Yes
46 3rd GGP Sarah Faires Speak 1782-1865 Sarah Faires 1786-1865 93 -1 Yes
47 3rd GGP Andrew McKee 1760-1814 Andrew McKee c1760-1814 86 2 Yes
48 3rd GGP Elizabeth 1765-1839 Elizabeth [LNU] c1767-1838 88 2 Yes
49 4th GGP Moses Estes 1742-1815 Moses Estes c1742-1813 27 1 Yes
50 4th GGP Luremia Susannah Combes 1747-1815 Luremia Combs c1740-c1820 33 -1 Need mtDNA through all females
51 4th GGP Marcus Younger 1735-1816 Marcus Younger 1730/1740-1816 30 2 Yes
52 4th GGP Susanna Hart* 1725-1806 Susanna [possibly] Hart c1740-before 1805 26 -1 Yes
53 4th GGP William Moore 1725-1757 James Moore c1718-c1798 25 -2 Yes
54 4th GGP Margaret Hudspeth 1725-1808 Mary Rice c1723-c1778/1781 26 -2 Need Mary Rice mtDNA through all females
55 4th GGP Samuel “Little Sam” Harwell 1716-1793 Incorrect 36 -2
56 4th GGP Abigail Anne Jackson 1712-1793 Incorrect 33 -2
57 4th GGP Rawleigh “Rolly” Dodson 1730-1793 Raleigh Dodson 1730-c1794 19 2 Yes
58 4th GGP Elizabeth Mary Booth 1728-1793 Mary [LNU] c1730-1807/1808 27 -2 Need Mary’s mtDNA through all females
59 4th GGP Nancy Ann Steele 1728-1836 Unknown mother of Jane [LNU], wife of Lazarus Dodson 16 -2 Need Jane’s mtDNA through all females
60 4th GGP James Campbell 1742-1931 Charles Campbell c1750-c1825 28 -2 Y DNA confirmed NOT this line
61 4th GGP Letitia Allison 1759-1844 Incorrect 31 -2
62 4th GGP Jacob Dobkins 1750-1833 Jacob Dobkins 1751-1835 91 1 Yes
63 4th GGP Dorcas (Darcas) Johnson 1750-1831 Darcus Johnson c1750-c1835 92 2 Yes
64 4th GGP John Francis Vannoy 1719-1778 John Francis Vannoy 1719-1778 47 2 Yes
65 4th GGP Susannah Baker Anderson 1720-1816 Susannah Anderson c1721-c1816 59 2 Need mtDNA through all females
66 4th GGP Thomas Hildreth Henderson 1736-1806 Charles Hickerson c1725-before 1793 37 -2 Have Hickerson Y-DNA
67 4th GGP Mary Frances “Frankie” McIntire 1735-1811 Mary Lytle c1730-before 1794 37 -2 Need mtDNA from all females
68 4th GGP Rev. George W. McNeil 1720-1805 George McNiel c1720-1805 143 1 Yes
69 4th GGP Mary Sarah Coates 1732-1782 Sarah/Sallie or Mary [maybe] Coates c1740-1782/1787 139 1 Need mtDNA through all females
70 4th GGP John James Sheppard Shepherd 1734-1810 Robert Shepherd 1739-1817 136 -2 Have Shepherd Y-DNA
71 4th GGP Sarah Ann Rash 1732-1810 Sarah Rash 1748-1829 178 -1 Yes
72 4th GGP John Crumbley 1737-1794 William Crumley 1736-1793 77 -2 Have Crumley Y-DNA
73 4th GGP Hannah Mercer 1742-1774 Hannah Mercer c1740-c1773 73 2 Yes
74 4th GGP John Hanner (Hainer) Incorrect 19 -2
75 4th GGP Jotham Brown 1740-1799 Incorrect 183 -2 Have Brown Y-DNA
76 4th GGP Phoebe Ellen Johnston 1742-1810 Incorrect 182 -2
77 4th GGP Moses Johnston 1746-1828 Incorrect 45 -2
78 4th GGP Eleanor Havis 1753-1837 Incorrect 47 -2
79 4th GGP Henry Boulton 1693-1737 John Bolton before 1693-after 1729 23 -2 Have Bolton Y-DNA
80 4th GGP Elizabeth Bryan 1658-1742 Elizabeth Goaring 1795-1729 22 -2 Need mtDNA through all females
81 4th GGP Thomas Curry (Corry) 1705-1729 Thomas Curry 1705-1729 25 2 Need Curry Y-DNA
82 4th GGP Monique “Moniky” Curry 1704-1729 Monique Demazares 1705-1729 25 1 Need mtDNA through all females
83 4th GGP Robert James Mann 1740-1787 John Mann 1725-1774 26 -2 Need Mann Y-DNA
84 4th GGP Sarah Susannah McCloskey 1716-1797 Frances Carpenter 1728-1833 28 -2 Need mtDNA through all females
85 4th GGP Benjamin “Col. Ben” Colonel Wilson 1733-1814 Incorrect 28 -2
86 4th GGP Mary Ann Seay 1735-1814 Incorrect 29 -2
87 4th GGP John Hugh McDowell 1695-1742 Michael McDowell c1720-after 1755 7 -2 Incorrect but have correct Y-DNA McDowell Y-DNA
88 4th GGP Mary Magdalena Woods 1705-1800 Incorrect 8 -2
89 4th GGP Ebenezer Hall 1721-1801 Incorrect 6 -2
90 4th GGP Dorcas Abbott Hall 1728-1797 Incorrect 6 -2
91 4th GGP George Middleton Clarkston/Clarkson 1745-1787 Incorrect 98 -2 Incorrect but have correct Clarkson Y-DNA
92 4th GGP Catherine Middleton 1764-1855 Incorrect 94 -2
93 4th GGP William Henry Cook 1750-1920 Joel Cook before 1755 – ? 83 -2 Need Cook Y-DNA
94 4th GGP Elizabeth Wall 1747-1826 Alcy [LNU] c 1755-? 91 -2 Yes
95 4th GGP Obediah Samuel Muncy 1735-1806 Samuel Muncy 1740-1799 33 -1 Yes
96 4th GGP UFN Obediah Muncy wife Unknowen (sic) 1728-1843 Agnes Craven 1745-1811 27 -2 Need Agnes Craven Need mtDNA through all females
97 4th GGP Joseph Workman 1732-1813 Joseph Workman c1736-c1813 64 2 Yes
98 4th GGP Phoebe McRay McMahon 1745-1826 Phoebe McMahon c1741-after 1815 64 1 Yes
99 4th GGP Charles Beckworth Speake/Speaks 1741-1794 Charles Speake c1731-1794 47 1 Yes
100 4th GGP Jane Connor 1742-1789 Incorrect, unknown first wife 40 -2 Need mtDNA through all females
101 4th GGP Gideon Farris 1748-1818 Gideon Faires before 1749-1821 54 -1 Yes
102 4th GGP Sarah Elizabeth McSpadden 1745-1821 Sarah McSpadden c1745-c1820 55 1 Yes
103 4th GGP Hugh McKee 1720-1795 Unknown 34 -2
104 4th GGP Mary Nesbit 1732-1795 Unknown 35 -2
105 4th GGP Private (sic) Unknown father of Elizabeth, wife of Andrew McKee 35 -2
106 4th GGP Anna Elizabeth Carney [wife of “private”] Incorrect 35 -2
107 5th GGP Moses Estes 1711-1788 Moses Estes 1711-1787 13 2 Yes
108 5th GGP Elizabeth Jones “Betty” Webb 1718-1782 Elizabeth [LNU] 1715/1720-1772/1782 5 -2 No known daughters
109 5th GGP George W. Combs 1714-1798 John Combs 1705-1762 6 -2 Need Combs Y-DNA
110 5th GGP Phebe Wade ?-1830 Incorrect 6 -2 Need mtDNA of John Combs first wife through all females
111 5th GGP Sarah Ferguson 1700-1781 Incorrect 3 -2
112 5th GGP Anthony Hart 1700-? Possibly Anthony Hart but no evidence 3 0
113 5th GGP Charles Rev. Moore 1685-1734 Incorrect 4 -2
114 5th GGP Mary Margaret Barry Moore 1690-1748 Incorrect 4 -2
115 5th GGP Ralph Hudspeth II* 1690-1776 Incorrect 9 -2
116 5th GGP Mary Carter 1699-1737 Incorrect 3 -2
117 5th GGP Samuel Harwell 1674-1767 Incorrect 3 -2
118 5th GGP Mary Ann Coleman*8th Ggm (sic) 1678-1723 incorrect 6 -2
119 5th GGP Ambrose (Sar) Jackson 1695-1745 Incorrect 6 -2
120 5th GGP Anne Amy Wyche 1692-1765 Incorrect 6 -2
121 5th GGP George E Dodson (DNA) (sic) 1702-1770 George Dodson 1702-after 1756 23 -1 Yes
122 5th GGP Margaret Dogett Dagord 1708-1770 Margaret Dagord 1708-? 24 1 Need mtDNA through all females
123 5th GGP James Booth 1700-1741 Incorrect 4 -2
124 5th GGP Frances Dale Booth (15great aunt) (sic) 1688-1777 Incorrect 3 -2
125 5th GGP Samuel Scurlock Steele 1709-1790 Incorrect 2 -2
126 5th GGP Robert R. Campbell 1718-1810 Incorrect 34 -2
127 5th GGP Lady: Letitia Crockett 1719-1760 Incorrect 8 -2
128 5th GGP John A. Dobkins 1717-1783 John Dobkins c1710-c1788 20 1 Yes
129 5th GGP Mary Elizabeth Betty Moore 1739-1815 Elizabeth [LNU] c1711-? 20 -2 Need mtDNA through all females
130 5th GGP Peter Johnson 1715-1796 Peter Johnson/Johnston c1720-c1794 0 1 Yes
131 5th GGP Mary Polly Phillips 1729-1790 Mary Polly Phillips c1726-? 1 2 Need mtDNA through all females
132 5th GGP Francis Janzen Vannoy Van Noy 1688-1774 Francis Vannoy 1688-1774 8 1 Yes
133 5th GGP Rebecca Anna Catherine Anderson 1698-1785 Rebecca Annahh Andriesen/ Anderson 1697-1727 13 -1 Need mtDNA through all females
134 5th GGP Cornelius Anderson (Andriessen) 1670-1724 Kornelis Andriesen 1670-1724 5 2 Yes
135 5th GGP Annetje Annah Opdyck 1670-1746 Annetje Opdyck c1675-after 1746 5 2 Need mtDNA through all females
136 5th GGP Thomas Hildret Henderson 1715-1794 Incorrect

 

3 -2
137 5th GGP Mary Frisby 1709-1794 Incorrect 3 -2
138 5th GGP Alexander (Alex) McEntire 1707-1802 Incorrect 12 -2
139 5th GGP Hannah Janet McPherson 1711-1792 Incorrect 15 -2
140 5th GGP Thomas James McNeil 1699-1803 Incorrect 25 -2
141 5th GGP Mary Hannah Parsons 1697-1784 Incorrect 27 -2
142 5th GGP John Coates 1699-1732 Incorrect 21 -2
143 5th GGP Sarah Ann Titcombe 1710-1732 Incorrect 22 -2
144 5th GGP George Sheppard, Shepherd 1716-1751 George Shepherd c1700-1751 42 1 Have Shepherd Y-DNA
145 5th GGP Elizabeth Mary Angelicke Day (Daye) 1699-? Elizabeth Mary Angelica Daye 1699-after 1750 41 1 Need mtDNA through all females
146 5th GGP Joseph Rash 1722-1776 Joseph Rash before 1728-c1767 36 1 Yes
147 5th GGP Mary Warren 1726-1792 Mary Warren 1726-? 36 1 Yes
148 5th GGP James L Crumley/Cromley 1712-1784 James Crumley c1711-1764 11 -1 Yes
149 5th GGP Catherine Bowen Gilkey 1712-1784 Catherine [LNU] c1712-c1790 11 -1 Need mtDNA through all females
150 5th GGP Edward Willis Mercer 1704-1763 Edward Mercer 1704-1763 5 1 Yes
151 5th GGP Ann Lueretias Coats 1710-1763 Ann [LNU] 1699/1705-c1786/1790 5 -2 Need mtDNA through all females
152 5th GGP Daniel Brown 1710-1798 Incorrect 39 -2
153 5th GGP Mary Brown 1717-1777 Incorrect 40 -2
154 5th GGP Zopher “Elder” Johnson/Johnston* 1700-1804 Incorrect 51 -2
155 5th GGP Elizabeth Williamson Cooper 1703-1794 Incorrect 49 -2
156 5th GGP Joseph Benjamin Johnson (6th ggf) (sic) 1709-1795 Incorrect 3 -2
157 5th GGP Elizabeth Shepard 1709-1786 Incorrect 3 -2
158 5th GGP John (Boulware) Havis (Rev/war) (sic) 1728-1807 Incorrect 4 -2
159 5th GGP Susannah Gentile Boullier (Boulware) 1733-1817 Incorrect 3 -2
160 5th GGP Henry Boulton Jr. 1652-1720 Incorrect 22 -2
161 5th GGP Elizabeth Bryan 1658-1742 Incorrect, linked in two generations Duplicate not processing -2
162 5th GGP Norton Bryan 1634-1672 Incorrect 2 -2
163 5th GGP Elizabeth Middlemore 1640-1658 Incorrect 2 -2
164 5th GGP Guillam Demazure 1685-1706 Guillam Demazares before 1685-after 1705 2 2 Need Y-DNA
165 5th GGP Marie Demazure 1686-1705 Marie [LNU] before 1686-after 1705 2 1 Need mtDNA through all females
166 5th GGP John Robert Mann {Minnis} 1711-1772 Incorrect 3 -2
167 5th GGP Anne Vincent 1711-1747 Incorrect 3 -2
168 5th GGP Joseph David McCluskey 1693-1756 Incorrect 3 -2
169 5th GGP Barbara S Rohlflag 1695-1755 Incorrect 3 -2
170 5th GGP Willis Wilson, Jr. 1710-1794 Incorrect 4 -2
171 5th GGP Elizabeth Goodrich ?-1789 Incorrect 4 -2
172 5th GGP Reverend James Matthew Seay 1696-1757 Incorrect 7 -2
173 5th GGP Elizabeth (James M Seay) Wilson or Lewis 1696-1752 Incorrect 6 -2
174 5th GGP Ephriam Samuel McDowell 1673-1774 Murtough McDowell before 1700-1752 0 -2 Yes
175 5th GGP Margaret Elizabeth Irvine 1674-1728 Eleanor [LNU] before 1700-after 1730 1 -2 Need mtDNA through all females
176 5th GGP Michael Marion Woods 1684-1782 Incorrect 9 -2
177 5th GGP Mary Catherine Woods 1690-1742 Incorrect 9 -2
178 5th GGP Joseph Hall 1680-1750 Incorrect 0 -2
179 5th GGP Sarah Kimball Hall Haley 1686-1752 Incorrect 0 -2
180 5th GGP Edward Abbott 1702-759 Incorrect 0 -2
181 5th GGP Dorcas Mehitable Chandler 1704-1748 Incorrect 0 -2
182 5th GGP James Anderson Clarkston 1717-1816 Incorrect 17 -2
183 5th GGP Thomasina Elizabeth Middleton 1720-1796 Incorrect 17 -2
184 5th GGP Harlace Middleton Incorrect 5 -2
185 5th GGP Capt. Vallentine Felty Kuke Cook 1730-1797 Incorrect 25 -2
186 5th GGP Michael Wall 1728-1749 Incorrect 11 -2
187 5th GGP Rebecca Chapman 1725-1791 Incorrect 11 -2
188 5th GGP Samuel Scott Muncy 1712-1786 Samuel Muncy 1712-after 1798 50 -1 Yes
189 5th GGP Mary Daughtery Skidmore 1710-1797 Mary Skidmore c1710-1811 51 -1 Need mtDNA through all females
190 5th GGP Abraham Woertman Workman 1709-1749 Abraham Workman 1709-1813 26 1 Yes
191 5th GGP Hannah Annetje (Smith) Workman 1706-1747 Annetie Smith 1714-? 26 1 Need mtDNA through all females
192 5th GGP Hugh McMahon 1699-1749 Hugh McMahon 1699-1749 17 2 Need Y-DNA
193 5th GGP Agnas Norton 1699-1747 Agnas Norton after 1700-? 17 2 Need mtDNA through all females
194 5th GGP Thomas Bowling Speake V 1698-1765 Thomas Speak c1634-1681 11 -2 Yes
195 5th GGP Jane Barton/Brisco Smoote 1714-1760 Elizabeth Bowling 1641-before 1692 12 -2 No known daughters
196 5th GGP William Farris 1714-1776 William Faires/Farris before 1728-1776 11 1 Yes
197 5th GGP Deborah Johnson Faries 1734-1812 Deborah [LNU] 1734-1812 11 1 Need mtDNA through all females
198 5th GGP Thomas of Borden’s Grant McSpadden 1720-1765 Thomas McSpadden c1721-1785 19 1 Yes
199 5th GGP Mary Dorothy Edmondson (Edmundson, Edmiston, Edmisten) 1721-1786 Dorothy [possibly Edmiston] 1721-? 28 1 Yes
200 5th GGP Thomas Alexander McKee, Sr 1693-1769 Incorrect 7 -2
201 5th GGP Tecumseh Margaret Opessa Pekowi 1695-1780 Incorrect 6 -2
202 5th GGP Thomas F Nesbit 1707-1783 Incorrect 7 -2
203 5th GGP Jean McKee 1707-1790 Incorrect 7 -2
Total -163

Please note that I will provide a free Y-DNA testing scholarship at FamilyTreeDNA for any male descending through all men from the male ancestor where it’s noted that Y-DNA is needed. Y-DNA is typically the surname line in most western countries.

I will also provide a mitochondrial DNA testing scholarship at FamilyTreeDNA for anyone who descends from the women where it’s noted that mitochondrial DNA is needed. Mitochondrial DNA passes through all females to the current generation, which can be male or female.

If this is you or a family member, please reach out to me.

The Scores

Of the 203 ancestors for which Ancestry provided a Potential Ancestor, they could have amassed a total of 406 points if each one provided an accurate name and accurate birth and death dates within a reasonable margin. If they were completely wrong on every one, they could have earned a negative score of -406.

Ancestry’s ThruLine accuracy score was -163, meaning they were wrong more than right. Zero was the break-even point where there was equally as much accurate information as inaccurate.

In fairness though, the older ancestors are more likely to be wrong than the more recent ones, and there are more older ancestors given that ancestors double in each generation. Once Ancestry provided a wrong ancestor, they continued down that wrong path on up the tree, so once the path was incorrect, it never recovered.

Regardless of why, Ancestry suggested incorrect information, and as we know, many people take that information to heart as gospel. In fact, many people even call these *TrueLines* instead of *ThruLines*.

Ok, how did Ancestry do?

Category Total Percent
+2 – Both Name and Date Accurate or Within Range 24 11.82%
+1 – Name and/or Date Partly Accurate 41 20.2%
0 – Uncertain 1 0.49%
-1 – Neither Name nor Date Accurate, but Enough Context to Figure Out With Research 22 10.84%
-2 – Inaccurate, the wrong person 115 56.65%

 Take Aways – Lessons Learned

This leads us to the lessons learned portion.

  • Never, ever, take ThruLines or Potential Ancestors at face value. They are hints and nothing more. Ancestry states that “ThruLines uses Ancestry trees to suggest how you may be related to your DNA matches through common ancestors.” (Bolding is mine.)
  • Verify everything.
  • Never simply copy something from another tree or accept a hint of any kind without a thorough evaluation. No, your ancestor probably did not zigzag back and forth across the country every other year in the 1800s. If you think they did, then you’ll need lots of information to prove that unusual circumstance. Extraordinary circumstances require extraordinary proof.
  • Never add extraneous “things” to names like “DNA match” or name someone “Private,” unless, of course, that was actually their name. Extraneous “pieces” in names confuses Ancestry’s search routines too, so you’re hurting your own chances of finding relevant information about your ancestor, not to mention ThruLines for others.
  • Naming someone “Private” isn’t useful if they are attached to other non-private people as ancestors, siblings and descendants. Just sayin…
  • Once the first incorrect ancestor is suggested, ThruLines continues to go up the incorrect tree.
  • In the the older or oldest generations, a small number of DNA matches for a particular ancestor may simply mean that lots of people are beyond the ThruLines match reporting thresholds. Unfortunately, Ancestry does NOT have a function where you can hunt for matches by ancestor.
  • In the the older or oldest generations, a small number of DNA matches may also mean it’s either the wrong ancestor, or they have few descendants, or few have tested.
  • The number of matches, in either direction, is not directly predictive of the accuracy of the suggested ancestor.
  • One of the best ways to validate ancestor accuracy is to match other descendants through multiple children of the ancestor, assuming that the children have been assigned to that ancestor properly. Recall George Middleton Clarkson where the three male children assigned to him do not have the same Y-DNA.
  • Another validation technique is to also match descendants of both parents of the ancestor(s) in question, through multiple children.
  • Remember that paper trail documentation is an extremely important aspect of genealogy.
  • Do not rely on trees without sources, or on trees with sources without verifying that every source is actually referencing this specific person.
  • Same name confusion is a very real issue.
  • For male ancestors, always check the Y-DNA projects at FamilyTreeDNA to verify that males attached as children have descendants with matching Y-DNA.
  • Always test males for their surname line. You never know when you’ll either prove or disprove a long-held belief, or discover that someplace, there has been a biological break in that line.
  • Y-DNA matches can provide extremely valuable information on earlier ancestral lines which may lead to breaking through your brick wall.
  • Mitochondrial DNA testing and matching of descendants is sometimes the only way of proving maternity or discovering matches to earlier ancestors.
  • Both Y-DNA and mitochondrial DNA, via haplogroups, can provide origins information for that one specific line, meaning you don’t have to try to figure out which ancestor contributed some percentage of ethnicity or population-based DNA.
  • Everyone can test their mitochondrial DNA, inherited from their direct matrilineal line, and men can test their Y-DNA, which is their surname line.
  • Remember that ThruLines can only be as good as the trees upon which it relies.
  • Review the source trees for each Potential Ancestor provided, evaluating each source carefully, including notes, images and web links. You just never know where that diamond is hiding.

How Can Ancestry Improve ThruLines, Potential Ancestors and Provide Customers with Better Tools?

To improve ThruLines and/or Potential Ancestors, Ancestry could:

  • My #1 request would be to implement a “search by ancestor” feature for DNA matches. This would be especially beneficial for situations where matches are beyond the 5GG threshold, or if someone is testing a hypothesis to see if they match descendants of a particular person.
  • Provide a “dismiss” function, or even a function where a customer could provide a reason why they don’t believe a connection or suggestion is accurate. This could travel with that link for other users as well so people can benefit from commentary from and collaboration with others.
  • Provide all DNA matches to people who share a specific ancestor, even if one person is beyond the 5 GG level. Currently, if both people are beyond that threshold, the match won’t show for either, so that’s no problem. The hybrid way it works today is both confusing and misleading and the hard cutoff obfuscates matches that have the potential to be extremely useful. Often this is further exacerbated by the 20 cM thresold limit on shared matches.
  • Add a feature similar to the now defunct NADs (New Ancestor Discoveries) where Ancestry shows you a group of your matches that descend from common ancestors, but those ancestors are NOT connected to anyone in your tree. However, DO NOT name the tool New Ancestor Discoveries because these people may not be, and often are not, your ancestors. If you’re related to a group of people who all have these people in THEIR tree as ancestors, that alone is a powerful hint. You might be descended from their ancestors, from the spouse of one of their children – something. But it’s information to work with when you have brick walls where Ancestry cannot connect someone as a potential ancestor directly to someone in your tree. Even locations of those brick-wall-breaker possible ancestors would be a clue. In fact, it’s not terribly different than the Potential Ancestors today, except today’s Potential Ancestors are entirely tree based (beyond ThruLines) and dependent upon connecting with someone in your tree. These new Brick-Wall-Breaker Potential Ancestors are (1.) NOT connected to your tree, and (2.) are all a result of DNA matches with people who have these ancestors in their tree.
  • If you already map your segment information at DNAPainter, the Brick-Wall-Breaker ancestral lineage connection would be immediately evident if Ancestry provided DNA segment location information. In other words, there are answers and significant hints that could be available to Ancestry’s customers.
  • Extend ThruLines for (at least) another two generations. Today ThruLines ends at the point that many people begin running into brick walls about the time the US census began. Using a 25-year generation, the current algorithm gives you 175 years (about 1825 starting with the year 2000), and a 30-year generation gives you 210 years (about 1790). Extending that two additional generations would give testers two more generations, several more Potential Ancestors, and 50-60 more years, approaching or reaching across the US colonial threshold.
  • Extending ThruLines and adding that Brick-Wall-Breaker functionality wouldn’t be nearly as important if customers could search by ancestor and download their match with direct ancestor information, similar to the other vendors, but since we can’t, we’re completely reliant on ThruLines and Potential Ancestors for automated connections by ancestor. Downloading your match list including a list of each person’s direct ancestors and matching segments would provide resources for many of these customer needs, without Ancestry having to do significant major development. If nothing else, it could be an interim stepping-stone.

_____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Sarah Cook (1774/1775-1863), Epitome of Perseverance – 52 Ancestors #386

Sarah Cook was the wife of James Lee Claxton, or Clarkson. That name changed like a chameleon and trust me, those changes caused Sarah massive headaches too.

Much of what we know about Sarah comes from her application for her husband’s War of 1812 pension benefits and bounty land. These applications were quite difficult and fraught with bureaucratic red tape. This process of application and reapplication requiring several affidavits must have been horribly frustrating for Sarah, but it is quite the boon for genealogists, telling us a lot about Sarah and the people in her life.

It’s in those documents that we discover that Sarah’s father’s name is Joel Cook and that she was married on October 10, 1799 (or 1805) in Russell County, Virginia by Justice of the Peace, John Tate.

Ironically, while Sarah gave two different years in which she was married, her marriage month and day remained constant.

I tend to think that 1799 is accurate, in part because three of her children were born before 1805, by which time she and James were living in Claiborne County, TN.

On June 16, 1805 and twice in September, James Claxton appears in the Claiborne County court notes. It’s very unlikely that he married in Russell County on October 10 of that year. It’s equally unlikely that Sarah had three children before marrying James, and moved to another county and state without the benefit of marriage.

They would not have returned to Russell County, a week’s hard journey across the mountains by wagon to be married by the Justice of the Peace there.

In 1810, in Claiborne County, James Claxton bought land from John Hall – 100 acres on the north side of Powell River.

By 1810, Sarah would have had about 6 children. Number 7 was born in 1811, and number 8 was born between 1813 and 1815.

Sadly, Sarah said goodbye to James for the last time on November 13, 1814, as he left to do his patriotic duty and serve his county in the War of 1812. In February of 1815, just days before the end of the war, James died in distant, cold Fort Decatur, hundreds of miles away from home, on the banks of the Tallapoosa River across from the Creek Nation in what would become Alabama in 1819.

James was buried beside the fort in a now-lost grave, probably marked only with a wooden cross at the time, if that. No one other than his fellow soldiers that dug his grave was at his funeral, such as it was. There probably wasn’t much of a funeral, because every minute the men were outside the fort, they were exposed to attack. Not only that, but many men at Fort Decatur were sick, very sick.

Sarah never got to bring James home, never got to bury him, never got to dress and wash his body, never got to weep over his grave, and never got to plant flowers and speak to him in the springtime. James may never have seen his last child who was probably born after he died.

Sarah was left with at least 8 children, and that’s 8 children that we know about. We don’t know how many might have passed away as infants or as children. It would have been terribly unusual for all children born to a woman to live to adulthood.

If Sarah and James were married for 15 and a half years, and had 8 children, that would have meant Sarah had a baby about every 2 years – about normal for a pioneer couple.

I do wonder if Sarah gave birth the last time after James’ death. Perhaps she did, but before she knew that he had died.

Sarah may not have known that James had perished until the rest of the men in his unit made their way home, on foot, after their discharge in May of 1815.

The soldiers from eastern Tennessee marched the 400 miles or so to Fort Decatur, and they would have marched home, much the worse for wear, only half as many as marched to Fort Decatur the previous November. At the rate of 15 miles per day, the sad march home by the bedraggled men would have taken almost a month, about 26 days – only to bear the burden of telling the families of the men who weren’t with them where they were.

I can envision Sarah, holding a baby and the hands of 7 stairstep children as she excitedly waited for James to appear with the rest of the soldiers. She had probably given the children baths and they would have been wearing their best clothes to welcome Daddy back home.

The soldiers must have been excited to be returning home, but horribly saddened and dreaded seeing the hopeful faces of the families of the men who were buried back at Fort Decatur or along the way.

Perhaps it was Tandy Welch who served beside James and was at his deathbed – the man who would one day become Sarah’s son-in-law – that imparted the terrible news.

I have always wondered if somehow Sarah knew. Maybe she had the second-sight, or maybe she just had a “feeling.” Maybe she was hoping against hope, watching the group of soldiers approach, then pass by, one by one, until one of the men she knew walked up to her and put his hands on her arms to steady her.

Untold grief had arrived, and with it, Sarah’s life as she knew it was upended.

Sarah’s Birth

Based on Sarah’s age given on the various petitions she signed related to James Claxton’s military service, she was born in either 1774 or 1775. In 1851, Sarah gave a deposition on March 8th and in that deposition states her age as 76, which means she was born in 1775. Given that the deposition was given the first week of March, there’s a roughly 25% chance Sarah had already had her birthday in 1851. If Sarah’s birthday happened after March 8th, then her birth year would subtract to 1774.

On October 16, 1858, Sarah signed a deposition in which she states that she is 83 years old, which means that she was born about 1775.

In 1853, Sarah gave a deposition on November 29, 1853 and gave her age as 79, indicating that she was born in 1774.  By the end of November, there was only a one in twelve chance that Sarah had NOT yet had her birthday in 1853.

We even have Sarah’s signature along with son, Fairwick.

Given the two bracketing depositions, it’s most likely from these records alone that Sarah was born sometime between March 9, 1774 and November 28, 1774, someplace in Virginia, according to the 1850 census.

While we find it odd today that someone would provide inconsistent information about their age, birth date or marriage year, it was quite common in that place and time to not know your birthday or year. Even today, sometimes I have to think about how old I am and substract to be sure.

Sarah’s Death

Sarah spent the rest of her life after James’ death as a single woman. She was only 40 or so when he died and lived for 48 years as a widow, longer than she lived before James died and three times as long as she was married. She was reported to be 88 years old on December 21, 1863 when she passed away, which would have put her birth firmly in 1775.

According to this paperwork filed in conjunction with James’s pension, Sarah “died very suddenly of no particular disease being recognized,” with Rebecca Wolf and Nancy Eaton in the room with her when she died.

I wish Sarah had a gravestone, but given that she died in the midst of the Civil War, a gravestone probably wasn’t possible.

I’m positive that Sarah is buried in the Claxton/Clarkson Cemetery in Hancock County, Tennessee where she lived with her son Fairwick and where he is buried as well.

In the photo above, the Claxton/Clarkson Cemetery, now called the Cavin Cemetery, is fenced on the Claxton/Clarkson original land. Sarah is buried here someplace in one of the many unmarked graves.

Sarah’s Records

In contrast with most women of her era, Sarah was quite active in land acquisition.  Some land may have been awarded to her as a result of her husband’s military service, but certainly not all of her land was thanks to James.

First, we find Sarah mentioned in her son’s land survey.

Claiborne County Survey Book 29 – page 693, Claiborne Co. Tn number 28765 March 16, 1826 – Farwix Claxton assignee of JP Shackleford, assignee of Farwix Claxton, assignee of Sarah Claxton – 100 acres granted to Farwix Claxton and his heirs lying in the county aforesaid adj Sarah Claxton on the north side of Powell’s river, crossing a public road, Sarah’s old corner. Surveyed Oct 14, 1826, filed June 4, 1853, chainers Henry Cook and John Plank

Is the Henry Cook who was the chainer significant, given that Sarah was a Cook before marriage?

It’s rather unusual that this survey wasn’t registered until in 1853, but surveys weren’t free and neither was registering deeds.

Did Fairwick and Sarah each have a 100-acre survey?  It would appear so.

On the same day in 1826, Sarah’s own 100 tract was surveyed, but the survey wasn’t entered for another 4 years, probably indicating Sarah didn’t have the money to pay the surveyor and the registration fee, both. This new survey adjoins her “old tract” which was probably the land that James Claxton purchased in 1810.

On August 16, 1826, Sarah had another 30 acres surveyed. In this deed, she is called Sally, which would have been the nickname for Sarah. So, now we know her nickname as well, called such by the surveyor who clearly knew her personally. This parcel too adjoined her “old tract.”

Chainers were often family members, and Henry Cook, found in all 3 of these surveys, may have been related to Sarah. John Plank was the neighbor, and he would surely have wanted to be sure this land was surveyed accurately.

In the 1830 census, Sarah is shown living with 5 people in her household.

  • 1 male 15-20 – unknown, probably Henry Claxton
  • 1 male 30-40 – unknown
  • 1 female 15-20 – probably daughter Martha Patsy
  • 1 female 30-40 – uncertain
  • 1 female 50-60, which would have been Sarah herself

Sarah’s daughter Rebecca had married John Collingsworth in 1829, so they could be the couple age 30-40 living with Sarah, although the dates and ages don’t align exactly.

In 1832, 25 acres was surveyed for Farwix Claxton on the Powell River adjoining his mother’s land. His brother, Henry, was a chain carrier for the surveyor.

A drawing from the Claiborne County survey book dated December 18, 1832 shows the survey for Sarah Claxton’s 30 acres bordering on Henry Clarkson’s and Levi Parks’ grant and on the Montgomery grant. Shadrack Moore and Henry Clarkson were chainers and the land was on the Powell River near 4 Mile Creek.

We are actually quite fortunate, because we know exactly where this bend of the Powell River was located. In fact, it was even called Claxton’s bend, as shown in this 1831 survey.

In 1834, in the Claiborne County Court Notes we find a lawsuit that may have forced the children of James Claxton to sell their land to their mother to protect it from being sold out from under them by court order. Fairwick, it seems, owed a debt.

Hugh Graham vs Fairwick Claxton – Fidelie S. Hurt JP returned with warrant judgement and execution for sum of 38.30 with the following returned endorsements on said execution to wit: There being no goods or chattels of def in my county I have levied this execution of F. Claxton “undivided interest in 100 ac of land on Powels River whereon Sarah Claxton now lives – June 16 1834”.  Order of sale issued.

It appears that the family was right, because they executed the deed of sale in March and the following June, the next court session, the court orders the land to be sold.  However, by this time, the land had already been sold and Fairwix had enough money in hand to pay his debt, if he so chose. However, if he chose not to pay the debt, the land his mother was living on was protected from his creditors. I’m assuming that Fairwix did indeed pay his debt, because we find nothing else in the court records that suggests otherwise.

We are quite fortunate because the resulting 1834 deed lists the children of James Claxton and Sarah, or at least the ones who were adults by this time. I would wager there were some heated discussions about this transaction, and how it would or might occur. I can’t imagine Sarah and her other children being happy about this turn of events.

1834 – Fairview (Fairwick) Claxton to Sarah Claxton, 1834, Book O-233 for $70.00 – original reads March 27th, 1834, between Farwick Clarkson, Andrew Hurst and wife Mahala, John Plank and wife Elizabeth, Levi Parks and wife Susannah, John Collinsworth and wife Rebecca, Jacob Parks and wife Patsy, heirs at law of James Clarkson deceast of the one part and Sarah Clarkson widow of the aforesaid James Clarkson decd of the other part, all of Claiborne Co. Tn. In consideration of:

    • Farwick Clarkson, $70 (signs with a signature – but all of the rest make marks. Fairwick’s wife is not included for some reason.)
    • Andrew Hurst and wife Mahala – $70
    • John Plank and wife Elizabeth – $70 or 20
    • Levi Parks and wife Susannah – $70
    • John Collensworth and wife Rebecca – $20
    • Jacob Parks and wife Patsy “Polly” – $20

To Sarah Clarkson, widow aforesaid, 100 acres, Claiborne on the North side of Powell river where Sarah lives and land that was conveyed to James Clarkson from John Hall of Sumner Co. Tn… beginning at Hobbs line, bank of Powell river. Witnessed by John Riley and Johiel Fugate. Registered Jan. 1, 1841

Sarah’s youngest child, Henry is conspicuously absent from this deed which probably suggests he was still living with Sarah and was yet underage.

Did Sarah have to borrow the money to pay her children? Did the children accept IOUs from their mother in order to convey the land to her?  Did they expect to receive their payment after her death?  Were they angry with their brother, Fairwick, or were there forces at work that we can’t understand from a distance of 179 years?

Because of the surveys, deeds and later generation lawsuits, we know exactly where Sarah’s land is today. Seen here, looking across the fence from the road, we see the old barn in the distance with the fenced cemetery in front of the barn.

This land, beautiful, but oh so rocky would have proved difficult for Sarah to work as a farm. Not to be deterred, she did work that farm, for 48 years after James died, raised her family, and from all indicators, was successful by any measure they had in her lifetime.

In 1839, Sarah was listed on the Claiborne County Tax list with 100 acres of land worth $250. The tax was 12 and a half cents and 30 acres was valued as school land, although I’m not entirely sure what that meant.

Almost everyone had a “school land” amount, and clearly everyone didn’t have a school on their property. Sarah’s entire tax was 12 and a half cents.

In the 1840 census, Sarah Claxton is shown living with one male, age 60-70 and two females aged 60-70.

One of those females would have been Sarah, but I have no idea who the other is. I have only a slight inkling of who the male might be. He might possibly have been John Helloms who we find living with Sarah in 1850.

Helloms

I hate it when my research starts forest fires of rumors that I can’t later extinguish. More than two decades ago, I discovered that Sarah was living with an elderly Helloms male in the 1850 census and made the mistake of excitedly sharing my discovery with other researchers. It appears that they were excited too, and before long, Sarah’s maiden name was Helloms in countless online trees. Sarah’s maiden name was actually Cook, discovered later, but there is no catching up with a tidal wave of misinformation once it is unleashed.

In 1850, Sarah is age 75, born in Virginia, with one John Helloms, age 70, listed as idiotic, living with her. Both Sarah and John were born in Virginia. Sarah’s grandson through son Fairwick, Samuel Claxton lives next door, probably on the same land and just another house away we find Farwick with his wife, now age 50. The census was taken on December 13th, but was supposed to be taken as of April in that year. In any case, Sarah’s birth year subtracts to be 1775.

This is the record that caused many researchers to infer that Sarah’s middle name was Helloms, and that John Helloms was her brother. Until we discovered Sarah’s birth name given in James’ War of 1812 records, that assumption that John Helloms was probably her brother and she was caring for a family member stood as the conventional wisdom. However, that was incorrect and illustrates quite aptly why one should never draw even tentative conclusions, at least not out loud. Unfortunately, the majority of trees available still show Sarah’s maiden name as Helloms.

Conversely, it’s probably accurate to speculate that Sarah is somehow involved with or related to the Helloms family. In the Claiborne County Court Notes of the Court of Pleas and Quarter Sessions 1819 – 1822, on page 106 we find:

May 9, 1820 – Sarah Claxton admitted to administer on all the singular goods and chattels rights and credits of William Hulloms (this is clearly the name) decd who entered into bond with Josiah Ramsey for her security and was qualified as the law directs.

The combination of this record and that of John Hulloms living with Sarah in 1850 was truly convincing that her maiden name was Hulloms or Helloms, but it wasn’t, as sworn to by Sarah herself. However, there is very clearly a connection in some fashion to the Helloms of Hulloms family.

It’s worth noting that there is no Helloms entry in the reconstructed 1790 Virginia census using tax records from the 1780s, as provided by www.binnsgenealogy.com, but there are several Helms.  There is, however, one William Hulloms in Westmoreland County on the 1791 “census.”

There is also a William Hulloms in Ashe County, NC in 1790, although he appears to be fairly young with 3 young children – so he can probably be ruled out – but not positively.

An 1804 tax list for Knox County, TN shows a William Helloms Sr. with 229 acres on Hickery Creek with 1 white poll, along with a John Hellams with 237 acres on Hickery Creek with 2 black polls (but no white polls.)

While these might be red herrings, they may not be. Clearly there is some connection to the Helloms/Hulloms family, by whatever spelling. Sarah was a close enough relative to become administrator of William’s estate and 30 years later we find John Helloms, “idiotic,” living with Sarah.

The Helloms/Hulloms mystery stands to this day.

John Riley

Sarah continued to be involved in the community, and once again, we find her interacting with John Riley.

On August 8, 1855 she is noted as having a receipt for $24.22 in the estate of John L. Riley.

John Riley appears throughout Sarah’s life, including having been at her wedding in Russell County, according to depositions relating to Sarah’s attempts to receive both a pension and bounty land as a result of James’ death during the War of 1812.

The Russell County, Virginia deed abstracts tell us that John Riley lived on Mockason Creek in Russell County, at the foot of Clinch Mountain adjoining the Hustons and Fugates and with James Tate as a neighbor as well. John Tate was the JP that married Sarah Cook and James Claxton/Clarkson.

Members of the Riley family, along with James Claxton and the Fugates migrated together to the Powell River in then Claiborne County, Tennessee.

The Riley family was one of the earliest founders in Russell County, information provided by the Riley family history. In other words, the Riley family was already well established in the region, with their first land grant in 1774, long before the Cook family arrived 20 years later in about 1795.

The Last Census

Sarah lived an amazingly long time in an era with little medical care, or at least not as we know medical care today. They didn’t have antibiotics, or assistance during childbirth other than midwives. No matter how skilled they were, fate determined in many cases whether you survived or not.

In the last census where Sarah appears, 1860, she is 85 years old, born in Virginia, and still living in her own household beside son, Fairwick. Living with her we find her grandson, Robert Shiflet, spelled Shifley in the census, along with his wife Sary (Sarah, named for her grandmother) and their daughter Elizabeth.

Sarah’s occupation at age 85? Housework. Not retired. How does a woman ever retire from housework?

It looks like Sarah spent her entire life taking care of a long list of people. Perhaps as she aged, some of those same people helped make her life a little easier. I hope so.

Sarah’s granddaughter, Sarah Claxton Shiflet is shown above. I can’t help but wonderif she looked like her grandmother.

The Civil War

The Civil War in Hancock County was brutal. Families into the late 1900s told stories of hiding their livestock and what little food they had in caves, and finally, secreting themselves there as well.

To begin with, this part of Tennessee was highly divided. Tennessee was the last state to secede and join the Confederacy on July 2, 1861. Most of the men in this part of Hancock County crossed the state line into Virginia, then into Kentucky, under cover of darkness in the night and enlisted with the Union forces. But not all.

Hancock County saw fighting, as did every county in eastern Tennessee. Making the situation even worse, this area was a crossroads for the marauding soldiers of both the north and south, and all soldiers arrived hungry. The area was savaged.

Most of the families in Hancock County did not own slaves. The land was rocky and difficult to farm. I would describe the lifestyle as subsistence living. Most people were too poor to afford slaves, had they been inclined. However, the neighbor, William Harrell owned one slave, a female name Harriet and her son, who, it turned out, was also William Herrell’s son, Cannon.

In 1862, at the height of the Civil War, Confederate troops occupied Tazewell, the county seat of neighboring Claiborne County, burning the town in November.

Cumberland Gap, directly north of Tazewell was a strategic military point between the north and the south, and the Gap itself changed hands several times during the war.  Each time, the forces encamped at the Gap didn’t have enough supplies to feed the men, and the soldiers of both sides ravaged the landscape of everything available to eat, leaving the residents with virtually nothing.

Food was scarce and life was incredibly dangerous throughout the Civil War. At least two and probably four of Sarah’s grandchildren died during the Civil War. We don’t know why Sarah died. It could easily have been attributed, at least in part, to the war.

By the time the war ended in 1865, Sarah was gone – having joined James a half-century later in watching over her family from the other side.

Military Records

Poor Sarah. James’ military files were then, and remain, a mess.

After I initially received part of them about 25 years ago, I managed to misplace some. When reordering those same records, they aren’t there. I’m glad I took notes at the time. I wish I had made copies, but that was before scanners.

To begin with, the military recorded his service records as Claxton on the unit’s roster, and Sarah applied as Clarkson. Eventually, they got that straightened out, but the Civil War interfered in that process too.

Sarah did succeed in receiving half of James’ pay for 5 years. She eventually received a 40-acre land grant, which she subsequently had cancelled, persevering to obtained an 80-acre grant instead, claiming she had been short-shifted. Forty acres was awarded to those who served for 30 days and 80 acres was awarded for four months service. Apparently, the powers-that-be agreed that an error had occurred, because Sarah received her 80-acre grant. We don’t know where that land was located, or if she simply sold the grant. By that time, she already had obtained her own land grants in Claiborne, now Hancock, County, TN and I’m sure she wasn’t the least bit interested in moving elsewhere. Sarah would have needed her family to help with the farm, and eventually, probably to help care for her.

For all the headaches this process caused Sarah, it provided wonderful information not available elsewhere.

On May 3, 1861, Sarah signed a Power of Attorney assigning Fairwix, her son, as her attorney to act on her behalf. In most of her documents, in later years, she signed with an X. Note that her surname is spelled as Clarkston. Unfortunately, the surname vacillates between Claxton, Clarkson and Clarkston. Based on Y-DNA matches, it appears to have originally been Claxton , but there is little consistency in James’s records.

This list of pensioners and their payments from Knoxville, TN shows Sarah Clarkson, widow of James, as a pensioner. Unfortunately, this record series is titled U.S., Revolutionary War Pensioners, 1801-1815, 1818-1872, which is clearly incorrect, because he served in the War of 1812, not the Revolutionary War.

This record shows that Sarah was restored to the pension list in May of 68, meaning 1868 of course, correcting sheet June 8/69 in the amount of 3.50 per month. James was a Private. Commencement is February 3,1858, and then September 4, 1860.

The columns appear to be March and September of each year, and she is noted with 4 and 2 until in 1861, then 1, and then September of 1863, it looks like she did not receive anything. Sarah died in December of 1863, so it looks like her heirs were finally paid in full in January 1869.

What this summary record doesn’t tell us is that Sarah had been dealing with this in one form or another since 1816, shortly after James’ death. Nor does it hint at the disruption caused for these families by the Civil War. For that, we need to look at Sarah’s various applications beginning in the 1850s.

Benefit Applications

In the 1850’s, Congress passed several acts benefiting military survivors and widows. It was during that period that Sarah Clarkson applied for both James’ pension and bounty land. An act passed on September 28, 1850 provided for the granting of bounty land warrants. We know about the circumstances of James’ death because Sarah applied for both land and his pension.

According to the Treasury Department letter dated Dec. 30, 1853, James Claxton enlisted on November 8, 1814 and died on February 11, 1815. His widow, Sarah, had received a soldier’s half-pay pension of $4 per month under the Act of April 16, 1816 which was to last for 5 years, at that time. This means, of course, that James was paid $8 a month. In other words, he marched 400 miles and died at Fort Decatur for the sum of $24.

Hancock Co, State of Tennessee – On this 8th day of March 1851 personally appeared before me a JP John Riley of Hancock Co., Tn. and John Taylor of Lee Co., Va. who being duly sworn according to law declare that Sarah Clarkson is the widow of James Clarkson decd who was a private in the company commanded by Capt. John Brockman in the 4th regiment of East Tennessee militia commanded by Col. Baylis – in the War with Great Britain declared by the United States of the 18th day of June 1812. That said Sarah Clarkson was married to James Clarkson decd in Russell Co. in the St. of Va on the 10th of October 1805 by one John Tate a JP in their presence, that the name of the said Sarah Clarkson before her marriage aforesaid was Sarah Cook, that her husband the said James Clarkson died at Fort Decature on the 20th of Feb. AD 1815 and that she is still a widow, and they swear that they are disinterested witnesses. Signed by both John Riley and John Taylor and witnessed by AM Fletcher. Sworn before William T. Overton JP

There’s John Riley again. A disinterested witness means that they don’t stand to benefit from the statement.

A second sworn statement is given below:

On March 8th, 1851 personally appeared before me Sarah Clarkson aged 76 years a resident of Hancock Co. Tn. who being duly sworn according to law declares that she is the widow of James Clarkson decd who was a private in the company commanded by Capt. Brock (number of regiment not recollected) regiment of E. Tennessee militia commanded by Colonel (too light to read) in the war with Great Britain declared June 18th, 1812. That her said husband was drafted at Knoxville Tn. on or about the 13th of November AD 1814 for the term of 6 months and continued in actual service as she is informed and believes in said War for the term of 3 months and 7 days and died at Fort Decatur or near there on or about the 20th of February 1815 as will appear on the muster rolls of his company on account of sickness. She further states that she was married to the said James Clarkson in Russell Co. VA on October 10th 1805 by one John Tate JP and that her name before her marriage was Sarah Cook and that her said husband died at Fort Decatur as aforesaid on the 20th of February AD 1815 and that she is still a widow. She makes this declaration for the purpose of obtaining the bounty land to which she may be entitled under the act passed September 25th, 1850. Witness Fairwick Clarkson (possibly others as the bottom of page is cut off) and she makes her mark.

James Lee Claxton’s death date is given variously as February 11 and February 20, by different sources.

In another statement, Sarah gave her marriage date to James Lee Claxton as October 10, 1799 which meshes better with the births of their children. By 1805, James and Sarah were living on the Powell River in what is now Hancock County, Tennessee, raising a family. Their oldest son, Fairwick (Fairwix, Farwick, Farwix) Claxton/Clarkson, also my ancestor, was born in 1799 or 1800.

A third document tells us a little more about the circumstances of James death.

State of Tennessee, County of Hancock, on the 29th day of August in the year of our Lord 1853, personally appeared before me a JP within and for the county and state aforesaid. Foster Jones and Tandy Welch citizens of said state and county who being duly sworn according to law declare that they were personally acquainted with James Clarkson decd (sometimes called and written Claxton) who was a private in the company commanded by Capt. Brock in the 4th regiment as well as recollected of E. Tennessee militia commanded by Col. Bales in the War with Great Britain declared June 18 1812 and that the said James Clarkson (or Claxton) sickened and died before the expiration of the time for which he engaged to serve in the said war and he belonged to the said company and regiment to which we did and that we each of us have applied under the act of Sept. 28 1850 and obtained land warrants for our service in said war. Tandy Welch and Foster Jones both make their marks, AM Fletcher a witness and Stephen Thompson a witness.

Another statement indicates that both Tandy Welch and Foster Jones swore that they witnessed the death of James Claxton.

Tandy Welch, the man who was at James’ side when he died, five years later, on June 22, 1820, married James’ daughter, Mary. I wonder, did Tandy promise James, on his death bed, to take care of his family?

On November 29, 1853, personally appeared before me Mrs. Sarah Clarkston, a resident of Hancock County aged 79 years…widow of James Clarkson…married about 1799…drew 5 years half pay in 1816…obtained 40 acres of land bounty dated Sept. 22, 1853 number 92928.

One of the absolute best things about these applications is that we actually have Sarah’s signature and it’s not an X.

We also have her son, Fairwick’s signature, as well, in several locations. Now that I see this, the surname looks identical so I wonder if he signed for her. On other documents, she signed with an X.

Sarah filed another deposition in March of 1854, claiming she was entitled to 80 acres instead of 40. The 40-acre grant was canceled (a copy of the canceled certificate is in the pension file) and the 80-acre grant was approved. Sarah also received a widow’s pension of $3.50 per month. However, under the Act of Congress of February 4, 1862 her pension was suspended due to the war with the Confederate States of America. As Tennessee had seceded to join the Confederacy, all pensions payments in the state were stopped. This, combined with the effects of the war itself in Hancock County surely had to be a hardship for Sarah.

After the war had ended, Fairwix Clarkson applied for a restoration and arrears of payment on September 25, 1866. He filed as the administrator of the estate of Sarah Clarkson, who had died on December 21, 1863, at his home on the Jonesville Road. That’s some “Merry Christmas,” especially in combination with the ongoing war.

After the Civil War, on September 24, 1866, to obtain payment, Fairwick, as administrator of Sarah’s estate was required to sign an oath of allegiance, which he gladly did, I’m sure. His son, Samuel Claxton/Clarkson (below) would yet die of injuries and illness he received in the war, enlisted as a union soldier.

Missing Documents

In addition to the information, above, now available at Fold3, I’m missing the following documents:

  • Sarah started receiving James’s half pay amount under the 1816 Act, but I don’t have that 1816 application and associated paperwork. She mentions in later documents that she submitted proof of her marriage in 1816.
  • Anything between 1816 and 1851
  • I do not have the 80-acre bounty land grant, or any information about it.

One of these documents included the statement that her father was Joel Cook.

I paid an on-the-ground researcher to pull these files at the National Archives, and the records mentioned above seem to have been misfiled someplace, probably together. The only saving grace is that I know I didn’t dream it, because the documents we do have refer to earlier, now missing, documents.

James Taylor

In addition to John Riley, another family that Sarah was involved with in early Claiborne County was James Taylor. James, then living in Kentucky, also signed that he was present at her marriage.

Who was James Taylor?

According to an 1816 survey in Russell County, James Taylor’s land shared a property line with Joel Cook, at the mouth of Musick’s spring branch.

92 – August 19, 1816 – James Taylor – 330 ac – part Treasury Warrant 11962 dated May 10, 1782 – on both sides of the north fork of Clinch River – corner to a big survey of Andrew Hebourn – corner to John Wilson – corner to Hebourn, James Madison & Harris Wilson – on the west side of a gap – corner to Joel Cook – at the mouth of Musicks spring branch – corner to Abednego White – corner to Henry Bowen.

Sarah’s Burial

Although no record officially tells us, I’m positive that Sarah is buried right here, in the Claxton cemetery, where the rest of her family is found.

Sarah’s son, Fairwick is buried here, along with his son, Samuel.

Samuel’s name is misspelled for eternity as Saluel. If one couldn’t read, how would they have known? Or did they get such a good “discount” on the stone because of the error that they just decided to leave the name alone? After all, they knew who he was.

 

This cemetery, now called the Cavin Cemetery, is found in Claxton bend on the original Claxton land on what would then have been known as the Jonesville Road. This picture, taken from the road, shows old barn behind the cemetery.

Me, inside the cemetery one VERY hot May day.

My cousin and I were infamously trapped inside the Clarkson Cemetery by an amorous bull who wanted to add us to his harem.

Oh, the things memories are made of.

There are many fieldstone headstones and even more graves entirely unmarked.

Sarah is here someplace.

Sarah’s Life and Times

We know that Sarah endured a great deal in her lifetime, but nothing ever defeated her except the grim reaper himself, and then not until she was 88 years of age. Sarah was the epitome of perseverance and tenacity. Indeed, she persisted.

Her life was incredible. She was a child during the Revolutionary War, lost her husband in the War of 1812 and lived to lose grandchildren in the Civil War, dying herself in the midst of the fighting.

During her lifetime Sarah moved across state lines and lived on the frontier when land on the Powell River was first being settled. She and James were the first settlers on Claxton’s Bend, and their choice of location would inform who their children and grandchildren would marry. There was no one else to marry except your neighbors.  That old adage about the choices of the parents affecting the children into the 7th generation holds true. My children are that 7th generation.

Not long after Sarah and James moved to Claiborne County, Sarah’s father, Joel Cook, sold the family land in Russell County and literally disappeared. It’s speculated that he went to Kentucky, but we really don’t know.

In any event, if the family ties had not already been severed when Sarah moved to Claiborne County, they surely were at that point by simple virtue of geography.

We don’t know if Sarah had any children that died young. We do know she had 8 children that lived between her marriage in October 1799 and James’s death in February of 1815. Four may have been two sets of twins, but twins that survived in that time are rare. It’s more likely that we just don’t know their accurate birth years. Keep in mind that Sarah gave conflicting information herself about the year in which she was married – and she was certainly present and old enough to remember. If she was born in 1774 or 1775, she would have been 14 or 15 when she married in 1799.

Birth and marriage years didn’t seem to matter terribly in that time and place. Close enough was good enough.

Sarah and James had 8 known children:

  • Fairwick born 1799/1800 in Virginia, died Feb. 11, 1874 in Hancock County, TN, the 59th anniversary of his father’s death. He married Agnes Muncy and had 8 children.
  • Mahala born Dec. 7, 1801 in Virginia, died March 1892 in Claiborne Co, TN, married Andrew Hurst, had 10 children.
  • Elizabeth born 1803 in TN, died May 1, 1847 in Claiborne Co., TN, married John Plank, had 11 children.
  • Mary Polly born September 4, 1803, died June 22, 1887 in Hancock Co., TN, married Tandy Welch Sr., had 17 children.
  • Susannah “Sukey” born October 11, 1808, died May 22, 1895 in Iowa, married Levi Parks, had 11 children.
  • Rebecca born December 6, 1808, died September 4, 1880 in Union Co., TN, married John Collingsworth, had 12 children.
  • Martha Patsy “Polly” born September 11, 1811, died December 23, 1898 in Claiborne County, TN, married Jacob J. “Tennessee” Parks, had 9 children.
  • Henry born ? 21, 1815, died August 1838, married Martha “Patsy” Gillus Walker, had 3 children.

If Henry was indeed born in 1815, Sarah was pregnant when James marched off to war, and James never saw his son, Henry, who died young himself.

We receive information about Sarah’s children at her death from this 1868 letter detailing her son Fairwix’s attempts to obtain her War of 1812 pension payments that were suspended during the Civil War.

Sarah’s children and grandchildren here are stated as:

  • Fairwix who was loyal and who had 3 sons in the Federal Army. Samuel, Henry Avery and John – two of whom died in the war, and Samuel who died later of illness contracted during the war.
  • Mahala Hurst who left the county long before the war.
  • Polly Welch of Hancock County thoroughly loyal through the Rebellion.
  • Patsy Parks of Claiborne County – she and her family thoroughly loyal.
  • Rebecca Collingsworth of Union County who is reported as disloyal but from personal knowledge can say nothing.
  • Sukey Parks who moved to Iowa many years before the war.
  • Two children of Henry Clarkson deceased who died some 20 years ago named Edward H. and Flora A. Clarkson who were both loyal all during the war.
  • The heirs of Elizabeth Plank who died some 20 years ago and all of whose children were considered loyal.

In 1815, when James died, Sarah was 40 years old, give or take a few months, and she had 8 children at home, or 7 and 1 on the way. The oldest, Fairwick or Fairwix, was 15 or 16. The youngest, Henry, if born yet, was just a baby. It’s certainly possible that Henry was born after James’ death, meaning of course that James left a pregnant wife when he enlisted. James enlisted in November of 1814 and died in February of 1815. Henry’s birth was recorded in 1815. If Sarah became pregnant about the time James left, that tells us that Henry was born sometime before September of 1815. It’s certainly possible that Sarah was pregnant, with 7 children, when she received the devastating news that James had perished.

The younger children would have had no memory of their father.

Life couldn’t have been easy. Later depositions taken regarding the death of Fairwick gave us a glimpse into the drama that took place in these early very-interrelated family families living on the banks of the Powell River. All was not a bed of roses.

The Civil War introduced additional strife and upheaval. The families in this area were horribly divided, a rift that was to last for decades, certainly into the 20th century.  When I first visited Claiborne and Hancock Counties in the 1980s, more than 115 years after the Civil War ended, the families still identified each other by which side their “kin” had fought for in “the War.” While most of the families in this part of Hancock County fought for the Union, that wasn’t universal and almost every family had its share of “disloyal” or traitors. Of course, the definition of traitor depended on your perspective.

The division was still palpable and real in the early 1900s when these families still actively feuded and denied any relation to each other over Civil War alliances.

Sarah’s grandsons and great-grandsons marched off to war. For Sarah, this must have been a horrible déjà vu, a repeat of her James marching off to the War of 1812, never to return. Sure enough, just like James, some didn’t

In Sarah’s lifetime, two of her children died. Henry, her baby, died in August of 1838 and Elizabeth who married John Plank died in 1847.

Sarah’s grandson, James Claxton, son of Fairwick who named him for his father, James, had died by 1845, and Fairwick raised James’ 4 children. Of course, they lived next door to Sarah, so in reality, the entire family raised those children.

One of those boys that Sarah raised, William, died on May 4, 1863, serving the Union, at Camp Dennison, Ohio.

Fairwick lost 2 sons and a son-in-law during the Civil War. The Civil War was cruel to this family.

John Clarkson enlisted for the Union on March 15, 1862 and was killed on March 20, 1863 in Nashville, TN, almost 9 months to the day before Sarah died. John was likely buried near where he fell, so the family never got to bury him or say their goodbyes. For Sarah, a repeat of what happened to her beloved James.

The other two died a few months after Sarah. Perhaps she greeted them on the other side. Henry died February 2, 1864 in Louisville, KY and John Wolfe, Fairwick’s son-in-law and Sarah’s grandson-in-law, died March 16, 1864.

Before Sarah’s death, Fairwick’s other son-in-law, Calvin Wolf, had been captured in Atlanta, Georgia during a battle, also serving the Union, and was held prisoner under utterly horrific conditions at Andersonville Prison for 3 very long years. Sarah died without knowing what happened to this man, or what would become of her granddaughter and her great-grandchildren. Miraculously, somehow Calvin survived.

Sarah’s grandson, Levi Hurst, the son of Mahala Clarkson, shown above, who had married Andrew Hurst, also died in the Civil War. Levi was a Confederate and died September 18-20, 1863 at the Battle of Chickamauga, three months before Sarah’s death.

It must have been incredibly difficult for Sarah to have grandchildren literally fighting each other on both sides of the war.

Mahala’s granddaughter, Charity, appears to have died sometime between the 1850 and 1860 census, or she married and left no trail. Mahala’s son James Hurst married Elizabeth Farmer and we lose track of him as well.

In case you’re keeping track, that’s a total of 2 grandchildren, 2 grandchildren-in-law and 1 great-grandchild killed in the un-Civil war, along with 1 who served three tortuous years as a POW.

Sarah suffered another kind of grief as well – that of departure. Her daughter, Susannah married Levi Parks about 1824. Sarah witnessed the births of 11 grandchildren, born to Susannah. The last arrival, a baby girl joined the family in 1848, just before Susannah and Levi would sell their belongings, hitch up a wagon, and head for David County, Iowa. That sweet baby girl born in 1848 would die in 1850, the first member of that family to be buried in Iowa soil. Departure was, in those days, a form of death – because Sarah and Susannah, mother and daughter, both very clearly knew that their departure was a final goodbye and they would not be reunited until after their deaths.

So, Sarah grieved the absence of Susannah and all 11 of her children, and then the death of the baby. That bad news would have arrived by letter, if Sarah ever knew at all. It’s somehow ironic that I can discover more today about what happened to Sarah’s children who moved away than Sarah could in her own lifetime.

We know less about what happened to the rest of Sarah’s children and grandchildren, but it stands to reason that those families were negatively affected by the war as well.

Sarah Cook and James Lee Claxton had 8 children and 91 grandchildren. Sarah wouldn’t have known all of her grandchildren, because daughter Susannah Parks moved to Iowa in the 1840s and Rebecca moved to Union County, TN. Two other daughters, Patsy and Mahala were living close by in neighboring Claiborne County, so Sarah probably saw them from time to time.

Mary who married Tandy Welch (cabin shown above) and their family lived close, as did Fairwick of course, who lived next door, and several of his children.

Henry, Sarah’s son, had lived just down the road, before his death, near the Edward Walker cabin, above, where his wife, Martha “Patsy” Gillus Walker had lived with the Edward Walker family.

After Henry’s death, Henry’s widow, Martha, married William Claxton, son of Fairwick and moved to neighboring Claiborne County where they became estranged from the Claxton family. I told you there was drama!

Sarah said premature goodbyes to a lot of family members in her lifetime, if she got to say goodbye at all. Aside from her parents, Sarah lost her husband, several children and grandchildren to early deaths and warfare.

She was one of very few people who saw three monumental wars in her lifetime.

Sarah’s life was anything but easy and pain-free, yet, she persevered, a testament to fortitude.

Sarah’s Mitochondrial DNA

I was fortunate enough to connect with a cousin who descends from Sarah Cook Claxton through all females. I am ever so grateful to her for testing her mitochondrial DNA.

Several of her matches have taken the full sequence test, the test needed to obtain the full haplogroup designation, which allows us to narrow the scope of the geography where Sarah’s ancestors may have been found.

Sarah’s mitochondrial DNA is haplogroup H100, meaning she is the 100th branch named in haplogroup H.

On the FamilyTreeDNA  haplogroup tree, you can see that H100 is a branch of H.

Haplogroup H100 is found in the FamilyTreeDNA  database in Ireland, Canada, France, Saudi Arabia, the US and Scotland. Saudi Arabia? That’s unusual.

Our tester who descends from Sarah shows exact full sequence matches to four people, none of whom have entered their most distant ancestor information, and only one has provided a tree. Their ancestor is first found in Ohio in the 1800s.

Sarah’s descendant is fortunate to have 7 additional mutations that, along with her four exact matches, will likely form a new haplogroup together when the new mitotree is released. That should also provide a time estimate for a common ancestor which will help everyone immensely.

Sarah inherited her mitochondrial DNA from her mother whose name was Alsy, probably short for Alice.

Alsy was born sometime around 1750, probably in Virginia. Hopefully, eventually, we’ll have mitochondrial DNA matches to Virginia families. Then, Sarah’s mitochondrial DNA, combined with genealogy records and autosomal matches will help us break down that next brick wall.

_____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

The Best of 2022

It’s that time of year where we look both backward and forward.

Thank you for your continued readership! Another year under our belts!

I always find it interesting to review the articles you found most interesting this past year.

In total, I published 97 articles in 2022, of which 56 were directly instructional about genetic genealogy. I say “directly instructional,” because, as you know, the 52 Ancestors series of articles are instructional too, but told through the lives of my ancestors. That leaves 41 articles that were either 52 Ancestors articles, or general in nature.

It has been quite a year.

2022 Highlights

In a way, writing these articles serves as a journal for the genetic genealogy community. I never realized that until I began scanning titles a year at a time.

Highlights of 2022 include:

Which articles were your favorites that were published in 2022, and why?

Your Favorites

Often, the topics I select for articles are directly related to your comments, questions and suggestions, especially if I haven’t covered the topic previously, or it needs to be featured again. Things change in this industry, often. That’s a good thing!

However, some articles become forever favorites. Current articles don’t have enough time to amass the number of views accumulated over years for articles published earlier, so recently published articles are often NOT found in the all-time favorites list.

Based on views, what are my readers’ favorites and what do they find most useful?

In the chart below, the 2022 ranking is not just the ranking of articles published in 2022, but the ranking of all articles based on 2022 views alone. Not surprisingly, six of the 15 favorite 2022 articles were published in 2022.

The All-Time Ranking is the ranking for those 2022 favorites IF they fell within the top 15 in the forever ranking, over the entire decade+ that this blog has existed.

Drum roll please!!!

Article Title Publication Date 2022 Ranking All-Time Ranking
Concepts – Calculating Ethnicity Percentages January 2017 1 2
Proving Native American Ancestry Using DNA December 2012 2 1
Ancestral DNA Percentages – How Much of Them in in You? June 2017 3 5
AutoKinship at GEDmatch by Genetic Affairs February 2022 4
442 Ancient Viking Skeletons Hold DNA Surprises – Does Your Y or Mitochondrial DNA Match? Daily Updates Here September 2020 5
The Origins of Zana of Abkhazia July 2021 6
Full or Half Siblings April 2019 7 15
Ancestry Rearranged the Furniture January 2022 8
DNA from 459 Ancient British Isles Burials Reveals Relationships – Does Yours Match? February 2022 9
DNA Inherited from Grandparents and Great-Grandparents January 2020 10
Ancestry Only Shows Shared Matches of 20 cM and Greater – What That Means & Why It Matters May 2022 11
How Much Indian Do I Have in Me??? June 2015 12 8
Top Ten RootsTech 2022 DNA Sessions + All DNA Session Links March 2022 13
FamilyTreeDNA DISCOVER Launches – Including Y DNA Haplogroup Ages June 2022 14
Ancient Ireland’s Y and Mitochondrial DNA – Do You Match??? November 2020 15

2023 Suggestions

I have a few articles already in the works for 2023, including some surprises. I’ll unveil one very soon.

We will be starting out with:

  • Information about RootsTech where I’ll be giving at least 7 presentations, in person, and probably doing a book signing too. Yes, I know, 7 sessions – what was I thinking? I’ve just missed everyone so very much.
  • An article about how accurately Ancestry’s ThruLines predicts Potential Ancestors and a few ways to prove, or disprove, accuracy.
  • The continuation of the “In Search Of” series.

As always, I’m open for 2023 suggestions.

In the comments, let me know what topics you’d like to see.

_____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

“Nature scientific reports” 2022 Editor’s Choice Collection – We Made It!!!!

You’ll excuse me while I jump for joy and do a happy dance. You might say I’m over the moon, pardon the pun. There’s nothing to lift your spirits quite like a pleasant surprise!I

In June, when our article, African mitochondrial haplogroup L7: a 100,000-year-old maternal human lineage discovered through reassessment and new sequencing was published, you may or may not have noticed that the journal name was “nature, scientific reports.” No, they don’t capitalize the words in the journal’s title.

I know I didn’t mention how difficult is it to get published in this particular journal, so you’ll just have to trust me about how many grey hairs I can attribute to that process.

Taking that into account, imagine my surprise today when I discovered our paper in the Editor’s Choice collection for 2022. That’s not only amazing, it was entirely unexpected. Ironically, they didn’t notify the authors, so we found out quite by accident.

“Congratulations!!!”

“For what?”

“Editor’s Choice”

“Editor’s Choice for what? Where?”

“Nature scientific reports – the Editor’s Choice articles for 2022. Your L7 paper. It’s there in Ancient DNA.”

“WHAT?????”

I had to look right away, of course, never mind that I was standing in line at the bank at the time. I hope they didn’t notice the strange woman giving out a little yelp and accompanying leap. Ok, maybe it was a tiny leap, more like a happy hop, but it still counts.

Here, you can look too!

I was dumbstruck. Truth be told, I didn’t even realize there WAS a yearly Editor’s Choice collection. My bad. I probably shouldn’t admit that😊

The editor’s intro mentions that Svante Pääbo won the Nobel Prize in Physiology or Medicine this year for his work over the past several years on sequencing the genomes of extinct hominins, founding the field of paleogenetics.

Excuse my fan-girl exuberance, but it has truly been a banner year for genetics. I can’t help but be incredibly geeked! I had to read the announcement two or three times to be sure I was seeing what I was seeing.

Our paper was selected as one of 5 in the Mitogenomics section of the ancient DNA category and has accumulated just over 9700+ views which is actually amazing for a scientific paper. So, thank you everyone who read it. I’m glad we made the paper “open access,” which means free.

I wrote about our discovery, here and we published a video, here, but our paper is slightly different than the ancient DNA of the other papers in that category. The other papers utilize DNA extracted from ancient remains, but the “ancient DNA” of haplogroup L7, reaching back 100,000 years, was discovered in living people, with the exception of one 16,000-year-old ancient sample from Malawi that had initially been misclassified as L5, but has since been moved to L7.

That’s super-exciting because we know that this hen’s-teeth rare lineage still exists in a few people. Maybe you’re one of them. Maybe you carry a different but equally-as-rare mitochondrial lineage – your mother’s direct maternal line.

I hope you’ll test your mitochondrial DNA, here, to see what secrets are waiting for you.

_____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Native American: Is She or Isn’t She?

Many people have an oral history that a specific female ancestor is Native American.

Autosomal DNA results may or may not show some percentage of Native American ancestry. If your results DO include a percentage of Native American, you still need to figure out which ancestors were Native. Where did that piece of your genetic heritage come from?

If your results don’t include Native ancestry, that doesn’t necessarily mean you don’t have a Native Ancestor. Sometimes you just didn’t inherit a discernable segment of DNA from that ancestor, or maybe the vendor you tested with didn’t pick that up.

Be sure to upload your raw DNA file to both FamilyTreeDNA and MyHeritage for free to gain another perspective. Here’s my free step-by-step guide for downloading and uploading your DNA files from and to all the major vendors.

FamilyTreeDNA provides painted segment information as well that shows you which segments are Native American.

One of my challenges is that I do have Native American autosomal DNA segments. Determining where they came from has been challenging, although the ethnicity chromosome painting at FamilyTreeDNA has been very useful in confirming the source of those segments.

Is there a way to augment autosomal results and be more specific and directed in my search? Can I focus on an individual ancestor? Especially females who are particularly difficult to research, given name changes in each generation?

Yes, you can.

Chasing the Truth

Sometimes, especially historically, when a female ancestor’s genealogy wasn’t known, people presumed that they must have been Native American. I’ve come across this several times now.

The good news is that using mitochondrial DNA, you can find out conclusively if you test someone who descends from that woman through all females to the current generation, which can be male.

I had Native American oral history connected to two ancestors, both of whom I was able to confirm or refute by finding a cousin who inherited that ancestor’s mitochondrial DNA and agreed to test. Women give their mitochondrial DNA to both sexes of their children, but only daughters pass it on. In the current generation, males or females can test.

I also found an unexpected ancestor who was Native. I had no oral history about her – so you just never know what you’ll discover.

Sarah Faires

Oral history in some descendant families indicated that Sarah Faires’s was Native American, possibly because her ancestors were unknown. There was a supposition that “she must have been Native.”

We were able to obtain the mitochondrial DNA of Sarah whose haplogroup turned out to be H49a1, so clearly not Native.

If Sarah’s direct maternal line (her mother, her mother, her mother, on up her tree) had been Native American, she would have fallen into subclades of haplogroup A, B, C, D or X, although not all of those subclades are Native.

You can view the entire list of Native American mitochondrial DNA haplogroups, here and you can view H49a1 on the public mitochondrial haplotree, here.

H49a1 is most frequently found in Germany, followed by Sweden, England and Denmark.

Elizabeth Vannoy

My father’s grandmother, Elizabeth Vannoy, was reported to be Cherokee, both orally and in several letters between family members.

One of my first genealogy goals was to prove that history, but I wound up eventually doing just the opposite.

Elizabeth Vannoy’s mitochondrial DNA haplogroup is J1c2c, not Native.

Haplogroup J1c2c is found most often in England, France, Sweden and Hungary.

I was able to connect Elizabeth to her parents. Then, eventually, thanks to mitochondrial DNA, working with a cousin, we connected another four maternal generations conclusively, and I’m still working on the fifth generation.

Anne Marie Rimbault

My cousin had no idea that her ancestor, Anne Marie, born about 1631, in Acadia, wife of Rene Rimbault, was Native American when she tested her mitochondrial DNA.

Mitochondrial DNA results explained why Anne Marie’s parents had never been identified in the French records. She was Native American – a member of the Mi’kmaq tribe that intermarried with the French men in the Acadian settlement, proven by her A2f1a haplogroup.

Haplogroup A2f1a is shown on the mitochondrial haplotree as First Nations in Canada and Native American in the US, plus one French flag reflecting a tester who only knew that her ancestor was French-Canadian and believed she had come from France.

Her mitochondrial DNA matches are scattered across the Northern US and Canada, but her closest matches are found in the Acadian and French-Canadian communities.

Is She, or Isn’t She?

Testing your own mitochondrial DNA if you think your direct maternal ancestor may be Native will unquestionably answer that question. Finding a mitochondrial DNA candidate for each of your ancestral lines will reveal which ancestor is Native, or you can target test to see if any specific ancestor is Native.

Unlike autosomal DNA, mitochondrial DNA never loses its potency and doesn’t mix with the DNA of the father. The segments aren’t divided in each generation and don’t wash out over time.

Do you have oral history about female Native American ancestors? Do you have ancestors whose parents are unknown? Mitochondrial DNA testing will resolve that question, plus provide matching with other testers. You don’t know what you don’t know.

If you’re interested in learning more about how to find your Native American ancestors, you might enjoy my book, DNA for Native American Genealogy. There’s lots of information there, including search tips, ancient DNA, maps and known tribes by haplogroup.

Do you have female ancestors who might be Native American?

____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Join Me for DNA Day, Live

I’m excited to be presenting for an entire day of DNA on October 1st. You can join in too, because the Orange County Genealogical Society has graciously made this event open to the entire genealogy community via Zoom. You can sign up at this link.

Apparently, there’s some serendipity involved, because the Y, mitochondrial DNA, and X DNA sessions were specifically requested when I asked for RootsTech topic suggestions. You’re not going to have to wait nearly that long, because I’m covering all three at DNA Day.

These sessions will:

  • Educate about the topic at hand, meaning Y, mitochondrial DNA, and X DNA, and when to use each.
  • Discuss how to utilize the results from all three of these tests and types of DNA for genealogy, including the new FamilyTreeDNA Y DNA Discover tool. I’m providing step-by-step instructions.
  • Provide real-world analysis examples with case studies. These are always so much fun! I’ve actually made a couple of discoveries while preparing for these sessions.

The last session of the day, “DNA Tossed Salad,” ties everything together. I’ll discuss how I manage the results and the tools I use, particularly for autosomal tests, and what I “do” with matches.

Each session will have the opportunity for Q&A.

I’ve included information for every level, beginner through advanced. Here’s the registration link again. Hope to see you on October 1st!!!

_____________________________________________________________

Follow DNAexplain on Facebook, here, or follow me on Twitter, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

DNA: In Search of…Full and Half-Siblings

This is the fifth article in our series of articles about searching for unknown close family members, specifically; parents, grandparents, or siblings. However, these same techniques can be applied by genealogists to identify ancestors further back in time as well.

Please note that if a family member has tested and you do NOT see their results, ask them to verify that they have chosen to allow matching and for other people to view them in their match list. That process varies at different vendors.

You can also ask if they can see you in their results.

All Parties Need to Test

Searching for unknown siblings isn’t exactly searching, because to find them, they, themselves, or their descendant(s) must have taken a DNA test at the same vendor where you tested or uploaded a DNA file.

You may know through any variety of methods that they exist, or might exist, but if they don’t take a DNA test, you can’t find them using DNA. This might sound obvious, but I see people commenting and not realizing that the other sibling(s) must test too – and they may not have.

My first questions when someone comments in this vein are:

  1. Whether or not they are positive their sibling actually tested, meaning actually sent the test in to the vendor, and it was received by the testing company. You’d be surprised how many tests are living in permanent residence on someone’s countertop until it gets pushed into the drawer and forgotten about.
  2. If the person has confirmed that their sibling has results posted. They may have returned their test, but the results aren’t ready yet or there was a problem.
  3. AND that both people have authorized matching and sharing of results. Don’t hesitate to reach out to your vendor’s customer care if you need help with this.

Sibling Scenarios

The most common sibling scenarios are when one of two things happens:

  • A known sibling tests, only to discover that they don’t match you in the full sibling range, or not at all, when you expected they would
  • You discover a surprise match in the full or half-sibling range

Let’s talk about these scenarios and how to determine:

  • If someone is a sibling
  • If they are a full or half-sibling
  • If a half-sibling, if they descend from your mother or father

As with everything else genetic, we’ll be gathering and analyzing different pieces of evidence along the way.

Full and Half-Siblings

Just to make sure we are all on the same page:

  • A full sibling is someone who shares both parents with you.
  • A half-sibling is someone who shares one parent with you, but not the other parent.
  • A step-sibling is someone who shares no biological parents with you. This situation occurs when your parent marries their parent, after you are both born, and their parent becomes your step-parent. You share neither of your biological parents with a step-sibling, so you share no DNA and will not show up on each other’s match lists.
  • A three-quarters sibling is someone with whom you share one parent, but two siblings are the other parent. For example, you share the same mother, but one brother fathered you, and your father’s brother fathered your sibling. Yes, this can get very messy and is almost impossible for a non-professional to sort through, if even then. (This is not a solicitation. I do not take private clients.) We will not be addressing this situation specifically.

Caution

With any search for unknown relatives, you have no way of knowing what you will find.

In one’s mind, there are happy reunions, but you may experience something entirely different. Humans are human. Their stories are not always happy or rosy. They may have made mistakes they regret. Or they may have no regrets about anything.

Your sibling may not know about you or the situation under which you, or they, were born. Some women were victims of assault and violence, which is both humiliating and embarrassing. I wrote about difficult situations, here.

Your sibling or close family member may not be receptive to either you, your message, or even your existence. Just be prepared, because the seeking journey may not be pain-free for you or others, and may not culminate with or include happy reunions.

On the other hand, it may.

Please step back and ponder a bit about the journey you are about to undertake and the possible people that may be affected, and how. This box, once opened, cannot be closed again. Be sure you are prepared.

On the other hand, sometimes that box lid pops off, and the information simply falls in your lap one day when you open your match list, and you find yourself sitting there, in shock, staring at a match, trying to figure out what it all means.

Congratulations, You Have a Sibling!

This might not be exactly what runs through your mind when you see that you have a very close match that you weren’t expecting.

The first two things I recommend when making this sort of discovery, after a few deep breaths, a walk, and a cup of tea, are:

  • Viewing what the vendor says
  • Using the DNAPainter Shared cM Relationship Chart

Let’s start with DNAPainter.

DNAPainter

DNAPainter provides a relationship chart, here, based on the values from the Shared cM Project.

You can either enter a cM amount or a percentage of shared DNA. I prefer the cM amount, but it doesn’t really matter.

I’ll enter 2241 cM from a known half-sibling match. To enter a percent, click on the green “enter %.”

As you can see, statistically speaking, this person is slightly more likely to be a half-sibling than they are to be a full sibling. In reality, they could be either.

Looking at the chart below, DNAPainter highlights the possible relationships from the perspective of “Self.”

The average of all the self-reported relationships is shown, on top, so 2613 for a full sibling. The range is shown below, so 1613-3488 for a full sibling.

In this case, there are several possibilities for two people who share 2241 cM of DNA.

I happen to know that these two people are half-siblings, but if I didn’t, it would be impossible to tell from this information alone.

The cM range for full siblings is 1613-3488, and the cM range for half-siblings is 1160-2436.

  • The lower part of the matching range, from 1160-1613 cM is only found in half-siblings.
  • The portion of the range from 1613-2436 cM can be either half or full siblings.
  • The upper part of the range, from 2436-3488 cM is only found in full siblings.

If your results fall into the center portion of the range, you’re going to need to utilize other tools. Fortunately, we have several.

If you’ve discovered something unexpected, you’ll want to verify using these tools, regardless. Use every tool available. Ranges are not foolproof, and the upper and lower 10% of the responses were removed as outliers. You can read more about the shared cM Project, here and here.

Furthermore, people may be reporting some half-sibling relationships as full sibling relationships, because they don’t expect to be half-siblings, so the ranges may be somewhat “off.”

Relationship Probability Calculator

Third-party matching database, GEDmatch, provides a Relationship Probability Calculator tool that is based on statistical probability methods without compiled user input. Both tools are free, and while I haven’t compared every value, both seem to be reasonably accurate, although they do vary somewhat, especially at the outer ends of the ranges.

When dealing with sibling matches, if you are in all four databases, GEDmatch is a secondary resource, but I will include GEDmatch when they have a unique tool as well as in the summary table. Some of your matches may be willing to upload to GEDmatch if the vendor where you match doesn’t provide everything you need and GEDmatch has a supplemental offering.

Next, let’s look at what the vendors say about sibling matches.

Vendors

Each of the major vendors reports sibling relationships in a slightly different way.

Sibling Matches at Ancestry

Ancestry reports sibling relationships as Sister or Brother, but they don’t say half or full.

If you click on the cM portion of the link, you’ll see additional detail, below

Ancestry tells you that the possible relationships are 100% “Sibling.” The only way to discern the difference between full and half is by what’s next.

If the ONLY relationship shown is Sibling at 100%, that can be interpreted to mean this person is a full sibling, and that a half-sibling or other relationship is NOT a possibility.

Ancestry never stipulates full or half.

The following relationship is a half-sibling at Ancestry.

Ancestry identifies that possible range of relationships as “Close Family to First Cousin” because of the overlaps we saw in the DNAPainter chart.

Clicking through shows that there is a range of possible relationships, and Ancestry is 100% sure the relationship is one of those.

DNAPainter agrees with Ancestry except includes the full-sibling relationship as a possibility for 1826 cM.

Sibling Matches at 23andMe

23andMe does identify full versus half-siblings.

DNAPainter disagrees with 23andMe and claims that anyone who shares 46.2% of their DNA is a parent/child.

However, look at the fine print. 23andMe counts differently than any of the other vendors, and DNAPainter relies on the Shared cM Project, which relies on testers entering known relationship matching information. Therefore, at any other vendor, DNAPainter is probably exactly right.

Before we understand how 23andMe counts, we need to understand about half versus fully identical segments.

To determine half or full siblings, 23andMe compares two things:

  1. The amount of shared matching DNA between two people
  2. Fully Identical Regions (FIR) of DNA compared to Half Identical Regions (HIR) of DNA to determine if any of your DNA is fully identical, meaning some pieces of you and your sibling’s DNA is exactly the same on both your maternal and paternal chromosomes.

Here’s an example on any chromosome – I’ve randomly selected chromosome 12. Which chromosome doesn’t matter, except for the X, which is different.

Your match isn’t broken out by maternal and paternal sides. You would simply see, on the chromosome browser, that you and your sibling match at these locations, above.

In reality, though, you have two copies of each chromosome, one from Mom and one from Dad, and so does your sibling.

In this example, Mom’s chromosome is visualized on top, and Dad’s is on the bottom, below, but as a tester, you don’t know that. All you know is that you match your sibling on all of those blue areas, above.

However, what’s actually happening in this example is that you are matching your sibling on parts of your mother’s chromosome and parts of your father’s chromosome, shown above as green areas

23andMe looks at both copies of your chromosome, the one you inherited from Mom, on top, and Dad, on the bottom, to see if you match your sibling on BOTH your mother’s and your father’s chromosomes in that location.

I’ve boxed the green matching areas in purple where you match your sibling fully, on both parents’ chromosomes.

If you and your sibling share both parents, you will share significant amounts of the same DNA on both copies of the same chromosomes, meaning maternal and paternal. In other words, full siblings share some purple fully identical regions (FIR) of DNA with each other, while half-siblings do not (unless they are also otherwise related) because half-siblings only share one parent with each other. Their DNA can’t be fully identical because they have a different parent that contributed the other copy of their chromosome.

Total Shared DNA Fully Identical DNA from Both Parents
Full Siblings ~50% ~25%
Half Siblings ~25% 0
  • Full siblings are expected to share about 50% of the same DNA. In other words, their DNA will match at that location. That’s all the green boxed locations, above.
  • Full siblings are expected to share about 25% of the same DNA from BOTH parents at the same location on BOTH copies of their chromosomes. These are fully identical regions and are boxed in purple, above.

You’ll find fully identical segments about 25% of the time in full siblings, but you won’t find fully identical segments in half-siblings. Please note that there are exceptions for ¾ siblings and endogamous populations.

You can view each match at 23andMe to see if you have any completely identical regions, shown in dark purple in the top comparison of full siblings. Half siblings are shown in the second example, with less total matching DNA and no FIR or completely identical regions.

Please note that your matching amount of DNA will probably be higher at 23andMe than at other companies because:

  • 23andMe includes the X chromosome in the match totals
  • 23andMe counts fully identical matching regions twice. For full siblings, that’s an additional 25%

Therefore, a full sibling with an X match will have a higher total cM at 23andMe than the same siblings elsewhere because not only is the X added into the total, the FIR match region is added a second time too.

Fully Identical Regions (FIR) and Half Identical Regions (HIR) at GEDmatch

At GEDMatch, you can compare two people to each other, with an option to display the matching information and a painted graphic for each chromosome that includes FIR and HIR.

If you need to know if you and a match share fully identical regions and you haven’t tested at 23andMe, you can both upload your DNA data file to GEDmatch and use their One to One Autosomal DNA Comparison.

On the following page, simply enter both kit numbers and accept the defaults, making sure you have selected one of the graphics options.

While GEDmatch doesn’t specifically tell you whether someone is a full or half sibling, you can garner additional information about the relationship based on the graphic at GEDmatch.

GEDMatch shows both half and fully identical regions.

The above match is between two full siblings using a 7 cM threshold. The blue on the bottom bar indicates a match of 7 cM or larger. Black means no match.

The green regions in the top bar indicate places where these two people carry the same DNA on both copies of their chromosome 1. This means that both people inherited the same DNA from BOTH parents on the green segments.

In the yellow regions, the siblings inherited the same DNA from ONE parent, but different DNA in that region from the other parent. They do match each other, just on one of their chromosomes, not both.

Without a tool like this to differentiate between HIR and FIR, you can’t tell if you’re matching someone on one copy of your chromosome, or on both copies.

In the areas marked with red on top, which corresponds to the black on the bottom band, these two siblings don’t match each other because they inherited different DNA from both parents in that region. The yellow in that region is too scattered to be significant.

Full siblings generally share a significant amount of FIR, or fully identical regions of DNA – about 25%.

Half siblings will share NO significant amount of FIR, although some will be FIR on very small, scattered green segments simply by chance, as you can see in the example, below.

This half-sibling match shares no segments large enough to be a match (7 cM) in the black section. In the blue matching section, only a few small green fragments of DNA match fully, which, based on the rest of that matching segment, must be identical by chance or misreads. There are no significant contiguous segments of fully identical DNA.

When dealing with full or half-siblings, you’re not interested in small, scattered segments of fully identical regions, like those green snippets on chromosome 6, but in large contiguous sections of matching DNA like the chromosome 1 example.

GEDmatch can help when you match when a vendor does not provide FIR/HIR information, and you need additional assistance.

Next, let’s look at full and half-siblings at FamilyTreeDNA

Sibling Matches at FamilyTreeDNA

FamilyTreeDNA does identify full siblings.

Relationships other than full siblings are indicated by a range. The two individuals below are both half-sibling matches to the tester.

The full range when mousing over the relationship ranges is shown below.

DNAPainter agrees except also gives full siblings as an option for the two half-siblings.

FamilyTreeDNA also tells you if you have an X match and the size of your X match.

We will talk about X matching in a minute, which, when dealing with sibling identification, can turn out to be very important.

Sibling Matches at MyHeritage

MyHeritage indicates brother or sister for full siblings

MyHeritage provides other “Estimated relationships” for matches too small to be full siblings.

DNAPainter’s chart agrees with this classification, except adds additional relationship possibilities.

Be sure to review all of the information provided by each vendor for close relationships.

View Close Known Relationships

The next easiest step to take is to compare your full or half-sibling match to known close family members from your maternal and paternal sides, respectively. The closer the family members, the better.

It’s often not possible to determine if someone is a half sibling or a full sibling by centiMorgans (cMs) alone, especially if you’re searching for unknown family members.

Let’s start with the simplest situation first.

Let’s say both of your parents have tested, and of course, you match both of them as parents.

Your new “very close match” is in the sibling range.

The first thing to do at each vendor is to utilize that vendor’s shared matches tool and see whether your new match matches one parent, or both.

Here’s an example.

Close Relationships at FamilyTreeDNA

This person has a full sibling match, but let’s say they don’t know who this is and wants to see if their new sibling matches one or both of their parents.

Select the match by checking the box to the left of the match name, then click on the little two-person icon at far right, which shows “In Common” matches

You can see on the resulting shared match list that both of the tester’s parents are shown on the shared match list.

Now let’s make this a little more difficult.

No Parents, No Problem

Let’s say neither of your parents has tested.

If you know who your family is and can identify your matches, you can see if the sibling you match matches other close relatives on both or either side of your family.

You’ll want to view shared matches with your closest known match on both sides of your tree, beginning with the closest first. Aunts, uncles, first cousins, etc.

You will match all of your family members through second cousins, and 90% of your third cousins. You can view additional relationship percentages in the article, How Much of Them is in You?.

I recommend, for this matching purpose, to utilize 2nd cousins and closer. That way you know for sure if you don’t share them as a match with your sibling, it’s because the sibling is not related on that side of the family, not because they simply don’t share any DNA due to their distance.

In this example, you have three sibling matches. Based on your and their matches to the same known first and second cousins, you can see that:

  • Sibling 1 is your full sibling, because you both match the same maternal and paternal first and second cousins
  • Sibling 2 is your paternal half-sibling because you both match paternal second cousins and closer, but not maternal cousins.
  • Sibling 3 is your maternal half-sibling because you both match maternal second cousins and closer, but not paternal cousins.

Close Relationships at Ancestry

Neither of my parents have tested, but my first cousin on my mother’s side has. Let’s say I have a suspected sibling or half-sibling match, so I click on the match’s name, then on Shared Matches.

Sure enough, my new match also matches my first cousin that I’ve labeled as “on my mother’s side.”

If my new match in the sibling range also matches my second cousins or closer on my father’s side, the new match is a full sibling, not a half-sibling.

Close Relationships at MyHeritage

Comparing my closest match provided a real surprise. I wonder if I’ve found a half-sibling to my mother.

Now, THIS is interesting.

Hmmm. More research is needed, beginning with the age of my match. MyHeritage provides ages if the MyHeritage member authorizes that information to be shared.

Close Relationships at 23andMe

Under DNA Relatives, click on your suspected sibling match, then scroll down and select “Find Relatives in Common.”

The Relatives in Common list shows people that match both of you.

The first common match is very close and a similar relationship to my closest match on my father’s side. This would be expected of a sibling. I have no common matches with this match to anyone on my mother’s side, so they are only related on my father’s side. Therefore they are a paternal half-sibling, not a full sibling.

More Tools Are Available

Hopefully, by now, you’ve been able to determine if your mystery match is a sibling, and if so, if they are a half or full sibling, and through which parent.

We have some additional tools that are relevant and can be very informative in some circumstances. I suggest utilizing these tools, even if you think you know the answer.

In this type of situation, there’s no such thing as too much information.

X Matching

X matching, or lack thereof, may help you determine how you are related to someone.

There are two types of autosomal DNA. The X chromosome versus chromosomes 1-22. The X chromosome (number 23) has a unique inheritance path that distinguishes it from your other chromosomes.

The X chromosome inheritance path also differs between men and women.

Here’s my pedigree chart in fan form, highlighting the ancestors who may have contributed a portion of their X chromosome to me. In the closest generation, this shows that I inherited an X chromosome from both of my parents, and who in each of their lines could have contributed an X to them.

The white or uncolored positions, meaning ancestors, cannot contribute any portion of an X chromosome to me based on how the X chromosome is inherited.

You’ll notice that my father inherited none of his X chromosome from any of his paternal ancestors, so of course, I can’t inherit what he didn’t inherit. There are a very limited number of ancestors on my father’s side whom I can inherit any portion of an X chromosome from.

Men receive their Y chromosome from their fathers, so men ONLY receive an X chromosome from their mother.

Therefore, men MUST pass their mother’s X chromosome on to their female offspring because they don’t have any other copy of the X chromosome to pass on.

Men pass no X chromosome to sons.

We don’t need to worry about a full fan chart when dealing with siblings and half-siblings.

We only need to be concerned with the testers plus one generation (parents) when utilizing the X chromosome in sibling situations.

These two female Disney Princesses, above, are full siblings, and both inherited an X chromosome from BOTH their mother and father. However, their father only has one X (red) chromosome to give them, so the two females MUST match on the entire red X chromosome from their father.

Their mother has two X chromosomes, green and black, to contribute – one from each of her parents.

The full siblings, Melody, and Cinderella:

  • May have inherited some portion of the same green and black X chromosomes from their mother, so they are partial matches on their mother’s X chromosome.
  • May have inherited the exact same full X chromosome from their mother (both inherited the entire green or both inherited the entire black), so they match fully on their mother’s X chromosome.
  • May have inherited the opposite X from different maternal grandparents. One inherited the entire green X and one inherited the entire black X, so they don’t match on their mother’s X chromosome.

Now, let’s look at Cinderella, who matches Henry.

This female and male full sibling match can’t share an X chromosome on the father’s side, because the male’s father doesn’t contribute an X chromosome to him. The son, Henry, inherited a Y chromosome instead from his father, which is what made them males.

Therefore, if a male and female match on the X chromosome, it MUST be through HIS mother, but could be through either of her parents. In a sibling situation, an X match between a male and female always indicates the mother.

In the example above, the two people share both of their mother’s X chromosomes, so are definitely (at least) maternally related. They could be full siblings, but we can’t determine that by the X chromosome in this situation, with males.

However, if the male matches the female on HER father’s X chromosome, there a different message, example below.

You can see that the male is related to the female on her father’s side, where she inherited the entire magenta X chromosome. The male inherited a portion of the magenta X chromosome from his mother, so these two people do have an X match. However, he matches on his mother’s side, and she matches on her father’s side, so that’s clearly not the same parent.

  • These people CAN NOT be full siblings because they don’t match on HER mother’s side too, which would also be his mother’s side if they were full siblings.
  • They cannot be maternal half-siblings because their X DNA only matches on her father’s side, but they wouldn’t know that unless she knew which side was which based on share matches.
  • They cannot be paternal half-siblings because he does not have an X chromosome from his father.

They could, however, be uncle/aunt-niece/nephew or first cousins on his mother’s side and her father’s side. (Yes, you’re definitely going to have to read this again if you ever need male-female X matching.)

Now, let’s look at X chromosome matching between two males. It’s a lot less complicated and much more succinct.

Neither male has inherited an X chromosome from their father, so if two males DO match on the X, it MUST be through their mother. In terms of siblings, this would mean they share the same mother.

However, there is one slight twist. In the above example, you can see that the men inherited a different proportion of the green and black X chromosomes from their common mother. However, it is possible that the mother could contribute her entire green X chromosome to one son, Justin in this example, and her entire black X chromosome to Henry.

Therefore, even though Henry and Justin DO share a mother, their X chromosome would NOT match in this scenario. This is rare but does occasionally happen.

Based on the above examples, the X chromosome may be relevant in the identification of full or half siblings based on the sexes of the two people who otherwise match at a level indicating a full or half-sibling relationship.

Here’s a summary chart for sibling X matching.

X Match Female Male
Female Will match on shared father’s full X chromosome, mother’s X is the same rules as chromosomes 1-22 Match through male’s mother, but either of female’s parents. If the X match is not through the female’s mother, they are not full siblings nor maternal half-siblings. They cannot have an X match through the male’s father. They are either full or half-siblings through their mother if they match on both of their mother’s side. If they match on his mother’s side, and her father’s side, they are not siblings but could be otherwise closely related.
Male Match through male’s mother, but either of female’s parents. If the X match is not through the female’s mother, they are not full siblings nor maternal half-siblings. They cannot have an X match through the male’s father. They are either full or half-siblings through their mother if they match on both or their mother’s side. If they match on his mother’s side, and her father’s side, they are not siblings but could be otherwise closely related. Both males are related on their mother’s side – either full or half-siblings.

Here’s the information presented in a different way.

DOES match X summary:

  • If a male DOES match a female on the X, he IS related to her through HIS mother’s side, but could match her on her mother or father’s side. If their match is not through her mother, then they are not full siblings nor maternal half-siblings. They cannot match through his father, so they cannot be paternal half-siblings.
  • If a female DOES match a female on the X, they could be related on either side and could be full or half-siblings.
  • If a male DOES match a male on the X, they ARE both related through their mother. They may also be related on their father’s side, but the X does not inform us of that.

Does NOT match X summary:

  • If a male does NOT match a female on the X, they are NOT related through HIS mother and are neither full siblings nor maternal half-siblings. Since a male does not have an X chromosome from his father, they cannot be paternal half-siblings based on an X match.
  • If a male does NOT match a male, they do NOT share a mother.
  • If a female does NOT match another female on the X, they are NOT full siblings and are NOT half-siblings on their paternal side. Their father only has one X chromosome, and he would have given the same X to both daughters.

Of the four autosomal vendors, only 23andMe and FamilyTreeDNA report X chromosome results and matching, although the other two vendors, MyHeritage and Ancestry, include the X in their DNA download file so you can find X matches with those files at either FamilyTreeDNA or GEDMatch if your match has or will upload their file to either of those vendors. I wrote step-by-step detailed download/upload instructions, here.

X Matching at FamilyTreeDNA

In this example from FamilyTreeDNA, the female tester has discovered two half-sibling matches, both through her father. In the first scenario, she matches a female on the full X chromosome (181 cM). She and her half-sibling MUST share their father’s entire X chromosome because he only had one X, from his mother, to contribute to both of his daughters.

In the second match to a male half-sibling, our female tester shares NO X match because her father did not contribute an X chromosome to his son.

If we didn’t know which parents these half-sibling matches were through, we can infer from the X matching alone that the male is probably NOT through the mother.

Then by comparing shared matches with each sibling, Advanced Matches, or viewing the match Matrix, we can determine if the siblings match each other and are from the same or different sides of the family.

Under Additional Tests and Tools, Advanced Matching, FamilyTreeDNA provides an additional tool that can show only X matches combined with relationships.

Of course, you’ll need to view shared matches to see which people match the mother and/or match the father.

To see who matches each other, you’ll need to use the Matrix tool.

At FamilyTreeDNA, the Matrix, located under Autosomal DNA Results and Tools, allows you to select your matches to see if they also match each other. If you have known half-siblings, or close relatives, this is another way to view relationships.

Here’s an example using my father and two paternal half-siblings. We can see that the half-siblings also match each other, so they are (at least) half-siblings on the paternal side too.

If they also matched my mother, we would be full siblings, of course.

Next, let’s use Y DNA and mitochondrial DNA.

Y DNA and Mitochondrial DNA

In addition to autosomal DNA, we can utilize Y DNA and mitochondrial DNA (mtDNA) in some cases to identify siblings or to narrow or eliminate relationship possibilities.

Given that Y DNA and mitochondrial DNA both have distinctive inheritance paths, full and half-siblings will, or will not, match under various circumstances.

Y DNA

Y DNA is passed intact from father to son, meaning it’s not admixed with any of the mother’s DNA. Daughters do not inherit Y DNA from their father, so Y DNA is only useful for male-to-male comparisons.

Two types of Y DNA are used for genealogy, STR markers for matching, and haplogroups, and both are equally powerful in slightly different ways.

Y DNA at FamilyTreeDNA

Men can order either 37 or 111 STR marker tests, or the BIg Y which provides more than 700 markers and more. FamilyTreeDNA is the only one of the vendors to offer Y DNA testing that includes STR markers and matching between men.

Men who order these tests will be compared for matching on either 37, 111 or 700 STR markers in addition to SNP markers used for haplogroup identification and assignment.

Fathers will certainly match their sons, and paternal line brothers will match each other, but they will also match people more distantly related.

However, if two men are NOT either full or half siblings on the paternal side, they won’t match at 111 markers.

If two men DON’T match, especially at high marker levels, they likely aren’t siblings. The word “likely” is in there because, very occasionally, a large deletion occurs that prevents STR matching, especially at lower levels.

Additionally, men who take the 37 or 111 marker test also receive an estimated haplogroup at a high level for free, without any additional testing.

However, if men take the Big Y-700 test, they not only will (or won’t) match on up to 700 STR markers, they will also receive a VERY refined haplogroup via SNP marker testing that is often even more sensitive in terms of matching than STR markers. Between these two types of markers, Y DNA testing can place men very granularly in relation to other men.

Men can match in two ways on Y DNA, and the results are very enlightening.

If two men match on BOTH their most refined haplogroup (Big Y test) AND STR markers, they could certainly be siblings or father/son. They could also be related on the same line for another reason, such as known or unknown cousins or closer relationships like uncle/nephew. Of course, Y DNA, in addition to autosomal matching, is a powerful combination.

Conversely, if two men don’t have a similar or close haplogroup, they are not a father and son or paternal line siblings.

FamilyTreeDNA offers both inexpensive entry-level testing (37 and 111 markers) and highly refined advanced testing of most of the Y chromosome (Big Y-700), so haplogroup assignments can vary widely based on the test you take. This makes haplogroup matching and interpretation a bit more complex.

For example, haplogroups R-M269 and I-BY14000 are not related in thousands of years. One is haplogroup R, and one is haplogroup I – completely different branches of the Y DNA tree. These two men won’t match on STR markers or their haplogroup.

However, because FamilyTreeDNA provides over 50,000 different haplogroups, or tree branches, for Big Y testers, and they provide VERY granular matching, two father/son or sibling males who have BOTH tested at the Big Y-700 level will have either the exact same haplogroup, or at most, one branch difference on the tree if a mutation occurred between father and son.

If both men have NOT tested at the Big Y-700 level, their haplogroups will be on the same branch. For example, a man who has only taken a 37/111 marker STR test may be estimated at R-M269, which is certainly accurate as far as it goes.

His sibling who has taken a Big Y test will be many branches further downstream on the tree – but on the same large haplogroup R-M269 branch. It’s essential to pay attention to which tests a Y DNA match has taken when analyzing the match.

The beauty of the two kinds of tests is that even if one haplogroup is very general due to no Big Y test, their STR markers should still match. It’s just that sometimes this means that one hand is tied behind your back.

Y DNA matching alone can eliminate the possibility of a direct paternal line connection, but it cannot prove siblingship or paternity alone – not without additional information.

The Advanced Matching tool will provide a list of matches in all categories selected – in this case, both the 111 markers and the Family Finder test. You can see that one of these men is the father of the tester, and one is the full sibling.

You can view haplogroup assignments on the public Y DNA tree, here. I wrote about using the public tree, here.

In addition, recently, FamilyTreeDNA launched the new Y DNA Discover tool, which explains more about haplogroups, including their ages and other fun facts like migration paths along with notable and ancient connections. I wrote about using the Discover tool, here.

Y DNA at 23andMe

Testers receive a base haplogroup with their autosomal test. 23andMe tests a limited number of Y DNA SNP locations, but they don’t test many, and they don’t test STR markers, so there is no Y DNA matching and no refined haplogroups.

You can view the haplogroups of your matches. If your male sibling match does NOT share the same haplogroup, the two men are not paternal line siblings. If two men DO share the same haplogroup, they MIGHT be paternal siblings. They also might not.

Again, autosomal close matching plus haplogroup comparisons include or exclude paternal side siblings for males.

Paternal side siblings at 23andMe share the same haplogroup, but so do many other people. These two men could be siblings. The haplogroups don’t exclude that possibility. If the haplogroups were different, that would exclude being either full or paternal half-siblings.

Men can also compare their mitochondrial DNA to eliminate a maternal relationship.

These men are not full siblings or maternal half-siblings. We know, unquestionably, because their mitochondrial haplogroups don’t match.

23andMe also constructs a genetic tree, but often struggles with close relative placement, especially when half-relationships are involved. I do not recommend relying on the genetic tree in this circumstance.

Mitochondrial DNA

Mitochondrial DNA is passed from mothers to all of their children, but only females pass it on. If two people, males or females, don’t match on their mitochondrial DNA test, with a couple of possible exceptions, they are NOT full siblings, and they are NOT maternal half-siblings.

Mitochondrial DNA at 23andMe

23andMe provides limited, base mitochondrial haplogroups, but no matching. If two people don’t have the same haplogroup at 23andMe, they aren’t full or maternal siblings, as illustrated above.

Mitochondrial DNA at FamilyTreeDNA

FamilyTreeDNA provides both mitochondrial matching AND a much more refined haplogroup. The full sequence test (mtFull), the only version sold today, is essential for reliable comparisons.

Full siblings or maternal half-siblings will always share the same haplogroup, regardless of their sex.

Generally, a full sibling or maternal half-sibling match will match exactly at the full mitochondrial sequence (FMS) level with a genetic distance of zero, meaning fully matching and no mismatching mutations.

There are rare instances where maternal siblings or even mothers and children do not match exactly, meaning they have a genetic distance of greater than 0, because of a mutation called a heteroplasmy.

I wrote about heteroplasmies, here.

Like Y DNA, mitochondrial DNA cannot identify a sibling or parental relationship without additional evidence, but it can exclude one, and it can also provide much-needed evidence in conjunction with autosomal matching. The great news is that unlike Y DNA, everyone has mitochondrial DNA and it comes directly from their mother.

Once again, FamilyTreeDNA’s Advanced Matching tool provides a list of people who match you on both your mitochondrial DNA test and the Family Finder autosomal test, including transfers/uploads, and provides a relationship.

You can see that our tester matches both a full sibling and their mother. Of course, a parent/child match could mean that our tester is a female and one of her children, of either sex, has tested.

Below is an example of a parent-child match that has experienced a heteroplasmy.

Based on the comparison of both the mitochondrial DNA test, plus the autosomal Family Finder test, you can verify that this is a close family relationship.

You can also eliminate potential relationships based on the mitochondrial DNA inheritance path. The mitochondrial DNA of full siblings and maternal half-siblings will always match at the full sequence and haplogroup level, and paternal half-siblings will never match. If paternal half-siblings do match, it’s happenstance or because of a different reason.

Sibling Summary and Checklist

I’ve created a quick reference checklist for you to use when attempting to determine whether or not a match is a sibling, and, if so, whether they are half or full siblings. Of course, these tools are in addition to the DNAPainter Shared cM Tool and GEDmatch’s Relationship Predictor Calculator.

FamilyTreeDNA Ancestry 23andMe MyHeritage GEDmatch
Matching Yes Yes Yes Yes Yes
Shared Matches Yes – In Common With Yes – Shared Matches Yes – Relatives in Common Yes – Review DNA Match Yes – People who match both or 1 of 2 kits
Relationship Between Shared Matches No No No Yes, under shared match No
Matches Match Each Other* Yes, Matrix No Yes, under “View DNA details,” then, “compare with more relatives” Partly, through triangulation Yes, can match any kits
Full Siblings Yes Sibling, implies full Yes Brother, Sister, means full No
Half Siblings Sibling, Uncle/Aunt-Niece/Nephew, Grandparent-Grandchild Close Family – 1C Yes Half sibling, aunt/uncle-niece-nephew No
Fully Identical Regions (FIR) No No Yes No Yes
Half Identical Regions (HIR) No No Yes No Yes
X matching Yes No Yes No Yes
Unusual Reporting or Anomalies No No, Timber is not used on close relationships X match added into total, FIR added twice No Matching amount can vary from vendors
Y DNA Yes, STRs, refined haplogroups, matching No High-level haplogroup only, no matching No No, only if tester enters haplogroup manually
Mitochondrial DNA Yes, full sequence, matching, refined haplogroup No High-level haplogroup only, no matching No No, only if tester enters haplogroup manually
Combined Tools (Autosomal, X, Y, mtDNA) Yes No No No No

*Autoclusters through Genetic Affairs show cluster relationships of matches to the tester and to each other, but not all matches are included, including close matches. While this is a great tool, it’s not relevant for determining close and sibling relationships. See the article, AutoClustering by Genetic Affairs, here.

Additional Resources

Some of you may be wondering how endogamy affects sibling numbers.

Endogamy makes almost everything a little more complex. I wrote about endogamy and various ways to determine if you have an endogamous heritage, here.

Please note that half-siblings with high cM matches also fall into the range of full siblings (1613-3488), with or without endogamy. This may be, but is not always, especially pronounced in endogamous groups.

As another resource, I wrote an earlier article, Full or Half Siblings, here, that includes some different examples.

Strategy

You have a lot of quills in your quiver now, and I wish you the best if you’re trying to unravel a siblingship mystery.

You may not know who your biological family is, or maybe your sibling doesn’t know who their family is, but perhaps your close relatives know who their family is and can help. Remember, the situation that has revealed itself may be a shock to everyone involved.

Above all, be kind and take things slow. If your unexpected sibling match becomes frightened or overwhelmed, they may simply check out and either delete their DNA results altogether or block you. They may have that reaction before you have a chance to do anything.

Because of that possibility, I recommend performing your analysis quickly, along with taking relevant screenshots before reaching out so you will at least have that much information to work with, just in case things go belly up.

When you’re ready to make contact, I suggest beginning by sending a friendly, short, message saying that you’ve noticed that you have a close match (don’t say sibling) and asking what they know about their family genealogy – maybe ask who their grandparents are or if they have family living in the area where you live. I recommend including a little bit of information about yourself, such as where you were born and are from.

I also refrain from using the word adoption (or similar) in the beginning or giving too much detailed information, because it sometimes frightens people, especially if they know or discover that there’s a painful or embarrassing family situation.

And, please, never, ever assume the worst of anyone or their motives. They may be sitting at their keyboard with the same shocked look on their face as you – especially if they have, or had, no idea. They may need space and time to reach a place of acceptance. There’s just nothing more emotionally boat-capsizing in your life than discovering intimate and personal details about your parents, one or both, especially if that discovery is disappointing and image-altering.

Or, conversely, your sibling may have been hoping and waiting just for you!

Take a deep breath and let me know how it goes!

Please feel free to share this article with anyone who could benefit.

_____________________________________________________________

Follow DNAexplain on Facebook, here or follow me on Twitter, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research