All About AI – What It Is, What It Isn’t, and Why It Matters

This is the second article in the AI series. The first, Your Wonderful AI Assistant – Sometimes Wrong, Never Unsure, Always Convincing, explains why I’m writing this series and what to expect. I suggest that you read these articles in publication order, as they build on each other.

AI is neither inherently good nor bad. The outcome depends on:

  • How it is used
  • By whom
  • Capabilities of the (ever-changing) tools themselves
  • The understanding level of the “requester” and the “consumer”, both
  • Safeguards applied or neglected

About AI

Let me start by saying that I don’t love AI, and I don’t hate it. I’m neither an evangelist nor a doomsayer. I’m a realist. AI is a powerful tool, capable of remarkable things and spectacular failures. Understanding the difference and interacting appropriately are the keys to success or failure.

AI is simply a tool, and like all tools, it can be used for good or evil. AI has the potential to, and does, in some cases, make our lives easier. However, the bad guys and miscreants saw that potential early and have perfected it.

AI is all around us, whether you realize it or not, so don’t think you can just avoid it, because you can’t. AI exists in many forms and is here to stay. We need to educate ourselves so we can reap some of the benefits and avoid the pitfalls.

Education and increased vigilance are the only ways to protect yourself, and I mean vigilance incorporated into the very fiber of your being. No more, “that looks interesting” and clicking without thinking. It’s so easy to do.

When I talk about AI safety, I’m referring to two types of safety.

  1. Using AI tools for reliable results, and how to determine when you’re receiving or consuming something questionable. AI failures occur often and are both irritating and misleading, but not always obvious.
  2. Literally protecting yourself from danger. This includes recognizing when AI is being used without your knowledge and how to protect yourself in the new threat landscape. I am not overexaggerating.

Unfortunately, AI safety is a sliding scale, progressing from one end of the spectrum to the other. There’s not always a clear delineation between correct and incorrect, safe and unsafe, or between different types of AI. As I am wont to say, “It depends.”

Learning about AI, both in general and in specific contexts, is critical. Not yesterday’s AI – but AI right now, because both the AI tools and AI’s capabilities are changing at lightning speed.

We all need to up our game and retrain ourselves to always stop and think first.

AI and You

There are essentially three ways people encounter or interact with AI.

  1. You’re actively using AI as a tool, such as ChatGPT, Claude, Gemini, or others. This is generally safe from an actual danger or “threat” perspective, particularly because you are in the driver’s seat. However, there are aspects you need to be aware of – especially if you’re a novice. I’ll explain methodologies to use AI to (hopefully) increase your productivity and save you from following AI into the underbrush of falsehoods, inaccuracies, and misplaced confidence. In other words, so you don’t have to say, “Wow, I was ever an idiot,” too often.
  2. You’re unknowingly interacting with AI. Sometimes this is fine, but it can open the door to inadvertent reliance on incorrect information and therefore various forms of harm. Sometimes, harm rises to the level of actual danger. Understanding when you’re interacting with AI, understanding its limitations, and recognizing danger signs are important aspects of staying safe.
  3. The AI threat landscape. AI can be dangerous and used against you. I mean screaming-red-neon-flashing-sign hair-on-fire dangerous, and I’m going to explain this new threat landscape and how to improve your chances of being safe, primarily in the final article of this series.

I Use AI, But There Are Limits

I hold a graduate degree in Computer Science and have years of experience in the technology industry where security is both essential and critical. That background, while preparing me generally, cannot prepare one for the situations and well-hidden threats we now encounter every day. Being overconfident and overreliant on prior experience is foolhardy and a sure way to get burned.

The one thing that’s constant in the computer industry is change. The underlying fundamentals remain the same, but everything else changes – and AI is morphing rapidly.

I’ve been using AI since the beginning in a very restricted, measured way. I use AI regularly, tactically, and cautiously, with huge guardrails. I started out by taking classes from Mark Thompson and Steve Little, AI experts in the genealogy space, to learn how to use AI productively. That was a couple of years ago, and the entire landscape has changed since then. I make it a priority to stay current.

In the next article about using AI safely, I’ll share recommendations for training and education from Mark and Steve.

AI tools are trying to emerge from their terrible toddler stage and morph into early teens, but they relapse a lot! Sometimes AI is very helpful, sometimes wrong, and often frustrating – interspersed with amazing victories where AI helps us immensely.

Unfortunately, often it’s almost impossible to tell which is which.

Inspired by a posting in the Facebook group, Genealogy and Artificial Intelligence. Image is AI generated and appropriately labeled as such.

Here’s the caveat – I know I’m using AI. I’m not accidentally interfacing with a Chatbot, thinking it’s a human. I’m not reading something someone else posted and believing I’m reading about an experience that’s true – when it’s AI-created fiction. The question, of course, at that point, is WHY someone created it and posted it in a way that conceals its true origins.

My AI usage is intentional. I know how to be vigilant, generally what AI can and can’t do, and that I absolutely positively MUST fact-check everything. Often, I inadvertently push the limits of AI, thinking it can perform more than it can accurately, which is another reason everything must be checked. As genealogists, verifying sources should be second nature.

If you’re going to use AI, it’s essential that you do the same thing.

So, what, exactly, is AI?

What is Artificial Intelligence?

This is really a difficult question to answer, because AI has been more of a slow evolution, followed by a rapid acceleration of technology – not a specific “thing.” That acceleration occurred when standalone AI tools like ChatGPT, which we know are AI because they are specifically called that, were introduced and made available to the consuming public.

We’ve been using computers for decades now, assisting us on platforms from mainframes to PCs to tablets. Today, our phones are more powerful and useful than early mainframes.

AI is the latest in the cadre of applications, a type of tool that can either stand alone or be embedded in other software tools for specific tasks. Think Chatbots for business websites.

While AI is beginning to be “everywhere,” it’s not a universal scapegoat.

Two years in, AI is being blamed for everything. While AI does make a lot of mistakes, many issues aren’t a result of AI, and it’s not fair to presume they are. Let me give you two examples of what is and is not AI.

  • Not AI – Someone tried to enter text, meaning alphabet, in a field meant exclusively for numbers, like a month field that’s supposed to be a number and not the month name. The person was angry because “AI was wrong” and prevented the erroneous entry. First, it wasn’t wrong, and second, it wasn’t AI.

One of the earliest computer uses was to parse date fields and ensure that the “right thing” was being entered in the correct place. In this case, a numerical month, not the month name. That’s not AI. That’s just plain old-fashioned programming error-checking that’s been a part of software for decades. The program was performing exactly as it was intended.

  • AI – I submitted a spreadsheet to ChatGPT and instructed it to move all of the data in cells in column A that are entirely numeric to the same row in Column B, and to leave everything that contains any alphabetic characters where it is in column A. That’s AI, both because I’m using a known AI tool, and it’s processing my instructions to produce output that did not exist before.

The above image is what I wanted. I completed this by hand to show you what I had in mind. Working by hand is fine with 8 rows of data, but it wouldn’t be fine with 1000 rows, or more. That’s when you need a tool.

What could go wrong? Plenty.

Let’s say that I didn’t provide specific instructions and a cell contained mixed alpha and numeric, like Jane2. Or, if the tool just plain messed up because of some other unknown reason – such as the file being too long, or it misinterpreted an instruction. That’s why you have to verify everything.

With AI, it’s always some variant of the wild west frontier.

Next, I submitted my Before and After spreadsheet, above, and instructed ChatGPT to “Please put this in a chart and make it pretty.”

This is exactly what I received.

I didn’t receive what I wanted, because I didn’t tell the AI tool specifically what I wanted (spacing, color, font, size), and what I didn’t want. This isn’t a problem with the AI tool, it’s a problem with the instructions provided by the “driver.” AI is not a mind-reader, at least not yet.

Hint: When I don’t receive what I wanted, I tell ChatGPT what I wanted and ask it why I didn’t receive that, and what instructions I could provide differently. In this case, I learned that it can’t “discern colored text” (red) and only sometimes can “see” bolding.

This was a very simple comparison of AI versus non-AI. Of course there are endless variations, but in general, AI does something that produces something new or different or in another format – based on conversational instructions.

Examples of what AI can do well:

  • Take notes and summarize online meetings
  • Organize information into outline format
  • Suggest structure
  • Proofread and sometimes provide editing suggestions
  • Suggest places to look for additional information
  • Translate, transcribe and summarize both typewritten and handwritten documents, in multiple languages

Every one of these comes with a caveat. AI can always be wrong. Like any helper or intern, it’s up to us, as the responsible party, to be, well, responsible by monitoring and verifying everything.

Being wrong in places does not mean the tool isn’t useful. AI can transcribe an entire document in seconds, but I need to proofread it against the original. That’s a significant time savings for me. AI can then assist with the logic of how people are related to each other. That doesn’t mean it’s accurate, but it’s a place to start.

We have to learn how to communicate with our intern in a way it can understand to (hopefully) receive the output we want, and we have to confirm that it is.

The more difficult and complex the task, the more difficult the verification.

GIGO

The overarching theme for all computer data is GIGO – garbage in, garbage out. I know everyone can think of hundreds of examples that have absolutely nothing to do with AI. It’s the same now, but on steroids because we add the layers of:

  • Our instructions to AI, which may or may not be as thorough as we thought
  • AI interpreting what it thought we said, according to its internal rules and limitations that we don’t understand
  • AI manipulating data and producing output on our behalf

Additionally, when we ask AI to gather information about something, it can only gather what it can see. For example, some AI tools cannot reliably open weblinks, while others can. Some, like Google have internal routines to rank sites that are more reliable and accurate, and other tools do not.

Asking your AI tool for it’s sources so you can evaluate the GIGO factor is essential too.

Drinking From the Firehose

You might think AI is completely new, but it really isn’t. What’s new is the label of AI and consumer-based products where you get to be the driver.

Think of AI as the big umbrella.

In the past decade or so, artificial intelligence models have been slowly being developed, often for specific use cases. Machine learning models that are self-teaching are good examples. Genetic imputation to equalize autosomal DNA files produced by different vendors before matching is a specific use case.

Traditional programming is very specific and instructs, “If X, then Y.” Imputation, within a limited range of options, says, “Based on X, I think Y is most likely next character.” Machine learning learns by example. AI is the next generation where answers to questions are not hard-coded or self-learned in the same way.

With AI, one could interact and say, “Based on X, what do you think is next, and why?” The answer would be conversational, and would explain how the AI tool got to the result of Y. That doesn’t mean Y is accurate.

Before AI, consumers had never been in the driver’s seat, with the ability to query computers easily about anything with no programming needed – receiving conversational answers in their language of choice. Answers that are hopefully accurate.

Back in 2011, Siri became available, Amazon Alexa in 2014, and Google Assistant in 2016, but these were all command driven with a restricted vocabulary and could only perform limited actions.

In October 2022, ChatGPT introduced us to a new world, triggering the AI boom. By late 2023 and early 2024, suddenly the term AI, artificial intelligence, snowballed and was everywhere. The early versions of AI tools could only do a fraction of what they can in 2026, and could not perform tasks on your behalf.

ChatGPT prompt: “Make me a fun goofy picture with a cat that illustrates the ability of AI to make a fun goofy picture.”

Today that has all changed and it seems like everyone is making goofy pictures for fun.

Artificial Intelligence is NOT Intelligent

Let me say this loudly – artificial intelligence is not intelligent!

AI is a computer – electronic pulses in a data center somewhere. AI is trained to gather massive amounts of data, distill it in specific ways, and then, using various types of skills, interact with humans in a helpful manner. “Helpful” depends on perspective.

This field, as a whole, is really still in its infancy. That’s both the bad news and the good news.

AI tools are “new,” exciting, and frightening all at once. AI has enormous potential, but it also creates opportunities for misuse, deception, and unintended consequences.

I’m not referring to water and electricity consumption and the impact of building thousands of data centers on the environment. I’ll let you decide for yourself on that one.

Risks include:

  • Frequent errors
  • GIGO
  • Results being presented overconfidently by the AI agent
  • Faulty results being believed by the consumer (that’s you and me) with the same level of overconfidence, and without verification
  • Social engineering – meaning the manipulation and influence of people by bad actors
  • Extremely dangerous, highly malicious manipulation and applications in ways not possible before

The entire AI landscape is complicated by a lack of public understanding and made even more challenging by the extraordinary pace of this technology’s evolution.

Multiple Types of AI

There are multiple types of AI, ranging from Machine Learning models to full-blown Generative AI that creates goofy cat images for you. For the most part, today, we’re talking about LLMs and Generative AI.

Large Language Models, called LLMs, are artificial intelligence tools, like ChatGPT or Claude, that are designed to process human-like text or speech and generate output in the same way. AI doesn’t just give you a list of resources that you evaluate yourself, like a search engine; it gives you an “answer” (such as it is), writes text, and has an interactive “conversation” with you.

How does that happen?

The AI tool at the data center aggregates and amalgamates data based on your input and its training, then predicts the words most likely to come next, in what context, and how those words relate to each other.

That’s how AI forms an “answer.”

This is how and why AI, specifically LLMs, can write essays on a topic, create entirely fictitious but highly engaging social media postings and stories that aren’t presented as “stories,” but as someone’s personal experiences, meaning as “truth.”

AI, or the people who generated that AI script, or both, present fictional results with great confidence, often beautifully, and far more convincingly than humans.

This is where it’s important to differentiate between the tool itself, and the “driver,” meaning the human that’s prompting the AI tool.

  • The driver needs to prompt AI correctly and verify the output.
  • AI, the tool itself, sometimes generates incorrect information, often regardless of the prompts provided by the driver.
  • Sometimes the AI tool performs exactly as instructed, but the driver requested something “improper.” By improper, I don’t mean inadvertently or by accident.
  • Sometimes the human is unethical.
  • AI isn’t a sentient being and doesn’t understand the difference.

The human decides what to do with AI-generated results. Many times, AI-generated text, recognizable by word patterns or other characteristics (today), is posted to social media as “original” or factual, and contains incorrect information.

This is often referred to as “AI slop,” as one of the nicer terms, especially by those of us who increasingly find incorrect but convincing AI slop posted as “helpful information” and positioned as “expert,” even though it contains substantial inaccuracies.

Worse yet, very convincing AI slop can easily be generated to part you and your money.

And do I EVER have an example for you that combines AI slop and ethics.

AI SLOP and Ethics

Just two days after our new paper, on which I’m a co-author, Mitotree: The Universal Human Mitochondrial Reference Phylogeny at 10x the Resolution, was published, a company, whose name I’m not including because I don’t want to give it any oxygen or get it indexed with this article, posted a “beautiful” AI poster based on our paper – without our knowledge.

Looks nice, right?

To begin with, it appears for all the world like the authors provided this infographic, which we ABSOLUTELY DID NOT DO. Our names are right at the top. However, our names, as the paper’s authors, lend this “thing” credibility, thereby leveraging our work BOTH unethically and inaccurately.

This AI-generated infographic, although it’s not labeled as such, was created by a third party shortly after the publication of the Mitotree paper. While visually impressive, it contains several scientific inaccuracies, illustrating how quickly and easily authoritative-looking but incorrect content can be created and disseminated.

That’s one of the issues with AI – the beauty and professional appearance of AI-generated “things” encourages unwarranted confidence in the output, when the information is very wrong.

That’s why humans bear the responsibility of BOTH using AI ethically, AND verifying its accuracy. It’s also why, as consumers, we need to question everything.

My biggest issue with this situation isn’t with AI, other than the fact that it generated incorrect output – the issue is with the humans who intentionally created this, using AI. In other words, the drivers.

The infographic doesn’t say they created this incorrect rubbish, and I assure you, they never asked for permission. Then, they published the infographic on their own blog. In case you’re wondering, the company encourages uploads and charges people to get “new results.”

Now for the AI part.

The information IS WRONG and NOT a synthesis of what we published!!!! This infographic shows that all non-L haplogroups descend from haplogroup L4, which is absolutely FALSE.

Haplogroups M and N descend from haplogroup L3, and haplogroup R descends from a subclade of N. You can trust me because I’m one of the paper’s authors, or better yet, you can look for yourself, here, on Discover, or here, here, and here.

That isn’t the only thing that’s wrong, either, but how would normal air-breathing humans, meaning consumers, ever know?

Doesn’t that infographic look professional and convincing, especially if you, as a consumer, didn’t actually check everything on the document – AND its authenticity?

You’d assume legitimacy, right?

If you didn’t know, wouldn’t you be impressed with the expertise of the company that posted this infographic on their blog? And, as a normal consumer, how would you know?

You’d be impressed because you didn’t realize they hijacked someone else’s work, created this “beautiful” infographic, included the authors’ names on something inaccurate that the authors knew nothing about and didn’t endorse, and then published it. All without saying one word indicating that the infographic isn’t the authors’ work, was AI generated, or by whom.

In the past, before generating AI slop was this easy, consumers often presumed that a business was ethical and accurate. Of course that wasn’t always true, but being convincing at first glance is much easier today. Also, presume is related to assume…and we all know the rest of that story.

This is one of the dangerous sides of AI – illustrating how easy it is to deceive people now. It’s increasingly difficult to distinguish between legitimate expertise and fabricated authority. AI has removed that barrier.

You can no longer accept that anything is what it appears to be unless you’re working directly with known, trustworthy entities. The offending company completed that infographic in the click of a button and the blink of an eye, while I hadn’t even finished writing my own article about the paper’s release.

That company wants you to upload your DNA to them so that they can tell you “things” about your DNA. The intention is clear.

Of course, the consuming public, unless they were extremely vigilant, would never figure out either issue – ethics or accuracy.

I had to delete the next paragraph or two that I wrote on the topics of ethics, trust and confidence because I’m still so furious. Hot under the collar doesn’t even begin to describe how I feel about the ethics of misrepresenting something that we authors just spent six years of our lives on. Trust me when I tell you that my internal monologue was both very salty and rather spicy!😊

However, there’s good news. This infographic provides a perfect illustration of both AI slop, how deceptively great it looks, the ethics surrounding AI usage, and how difficult AI is to discern.

In fact, I couldn’t have come up with a better “bad example.”

A six-fingered hand, misspelled words or three arms in an image are obvious, and are yesterday’s AI tipoffs.

A misrepresented phylogenetic relationship or an incorrect founder-clade example is not obvious. Only subject-matter experts would or could notice if they were focused and paying attention.

That’s the problem in a nutshell.

The infographic wasn’t obviously wrong. It was convincingly wrong.

And convincing wrongness is far more dangerous than ridiculous wrongness, like six fingers, because most readers never realize they’ve been misled. Or why.

This single example demonstrates several AI themes in one fell swoop:

  • AI-generated content
  • Ease of creating complex and convincing output
  • Apparent authority
  • Misplaced trust
  • Lack of topic expertise
  • Overconfidence
  • AI slop
  • Difficulty of discerning truth
  • Yesterday’s “AI clues” are gone now – like misspelled words
  • Marketing vs. science
  • The necessity of human review
  • The fact that human review is only effective when the reviewer actually understands the subject, and cares.
  • Ethics

Like with this example, often AI slop is interspersed with accurate information, and it’s impossible to tell the difference unless you actually DO DUE DILIGENCE AND VERIFY ALL OUTPUT.

Yes, all of it.

Don’t shoot the messenger!

Hallucinations

Next, let’s discuss genetic genealogy, particularly haplogroup information. Hallucination or hallucinating is the term used for when AI simply makes things up, which often sound extremely convincing.

There’s nothing AI can tell you about your haplogroup that reputable sources cannot – and AI can’t see behind paywalls or logins, into your matches.

FamilyTreeDNA has an article in their help center titled, Why AI Models Struggle with Haplogroup Analysis.

Unfortunately, I encounter more and more instances where someone uploads their DNA to a third-party site, or “asks AI”. They receive a (sometimes substantially) incorrect haplogroup in a completely different part of the tree, complete with convincing language, posts it publicly, and then decides to argue that the third-party site, (who probably uses AI), or their AI tool, is correct.

Let’s look at an example. The mitochondrial DNA haplogroup for the Native American Anzick-1 burial in Montana that dates from roughly 12,500 years ago is mitochondrial haplogroup D4h3a. There’s no dispute about that.

A tester uploaded their mitochondrial DNA to “AI” and was very confidently told that, based on their mutations, their results belonged to haplogroup A2ex. They don’t.

ChatGPT misinformation about Anzick-1 haplogroup

They were then informed that it was also Anzick’s haplogroup. Wrong again.

FamilyTreeDNA's Discover tool information comparing haplogroups D4h3a and A2ex

FamilyTreeDNA’s Discover tool comparing mitochondrial DNA haplogroups D4h3a and A2ex. Their common ancestor lived about 66,000 years ago.

Not only did AI report Anzick’s haplogroup incorrectly on a grandiose scale, those two haplogroups don’t share a common ancestor for roughly 66,000 years – specifically haplogroup L3 who lived in Africa. AI made a massive mistake.

But it gets worse.

ChatGPT incorrect information about haplogroup A2ex.

The AI “answer” continued for four pages, containing completely erroneous information. To begin with, A2ex is a haplogroup, and “ex” has never meant excluding.

That’s bizarre, and an example of AI making something up that is patently false, but sounds wonderful and very authoritative.

The term for this AI behavior is hallucinating. I’m not publishing the rest of this exchange because I don’t want anyone (or any AI bot), for one minute, to think any of it is accurate. AI even made up mutations, along with four pages of “fairy tale.”

The individual who received this information was so excited and proudly posted it, which in turn provided incorrect information for other consumers, and encouraged them to use a badly flawed tool. Then they proceeded to argue with the experts.

They were absolutely convinced because it “felt” true to them, and because they wanted to believe they had discovered something special, and were related to Anzick. Their comment was, “You’re wrong, because AI told me it was true, and I’ve learned a lot from AI.” I was quite exasperated, but also feel sorry for them and can’t help but wonder how much else of what they “learned” from AI is wrong too, but I digress.

Most AI errors aren’t obviously wrong to the consumer. If AI said that you were descended from Tyrannosaurus Rex, you’d laugh. But if it tells you something more plausible and sounds confident, it’s very easy to be convinced. The reason these errors are so dangerous isn’t because the experts are fooled, it’s because non-experts either can’t, don’t, won’t or don’t think they need to invest the time to discern the difference.

I find it a bit baffling why anyone would use AI, or worse yet, a pay site for haplogroup misinformation, especially since FamilyTreeDNA provides the Discover website with free reports for every haplogroup. They are the unquestioned industry phylogenetic experts for both Y-DNA and mitochondrial DNA, and literally created the reference model for all haplogroups with the Mitotree.

Everyone can use Discover to access both the Y-DNA tree and Mitotree – for free – here. Discover isn’t even behind a paywall, and every customer can click through from their results page.

As far as haplogroups are concerned, there’s really no reason to rely on AI-generated answers without verifying them, because the authoritative resources are freely available and incredibly easy to access.

FamilyTreeDNA’s Discover Ancient Connection for Anzick-1.

Regarding Anzick’s haplogroup, all I had to do was enter haplogroup D4h3a in Discover and under Ancient Connections, right there is Anzick’s information.

I may start posting a link to this article on every single post where someone starts out with, “I submitted my DNA (or haplogroup) to AI, and it said…”

Let me be very direct. Don’t believe AI when it has to do with genetic information, especially Y-DNA, mitochondrial DNA, and haplogroups. AI does not have the capability of understanding topology and nuances of phylogenetic trees, and can only parrot back what others have said – correctly or incorrectly.

Incorrect information that’s publicly posted is then fed back into the AI algorithm, further reinforcing incorrect results.

You can find the free Discover tool for both Y and mtDNA, here, and you can join FamilyTreeDNA’s Mitochondrial DNA Group, here, and the Big Y Group, here.

AI Training and AI at Work

AI is trained on massive datasets of mostly unknown origin, including all public postings such as Reddit and Facebook public groups, pages and postings.

In other words, AI is always accruing additional information, including data uploaded by users.

As genealogists, we are already aware of the dangers of unsourced trees and and information that is repeated and copy/pasted without verification.

AI’s training provides more than just data points for you to evaluate, like trees.

AI bots are trained to interact in a humanlike manner. So instead of trees with hints, think hypothetically of an AI bot that reads the trees, then “creates” a wonderful story or infographic about your ancestor – that may or may not be either fully or partially accurate. But it’s beautiful, heartwarming and you love it! Plus, you don’t have to sort through all those trees, hints, and do the work yourself. AI did it for you! Win – win, right? Wrong.

AI knows how to very effectively manipulate language, images, and with them, emotion. Yours, to be specific. That’s both the bad news and the good news.

AI also has the ability to sift through large amounts of data and summarize succinctly –  sometimes even correctly. Sometimes it takes several refinements to obtain something that’s both correct and what you want. AI can discern patterns in massive amounts of data that we cannot, at least not readily.

Think of AI as your not-so-trusty but very confident and friendly intern – and I don’t necessarily mean a college intern.

Remember when you see AI published by others, their intern has been at work too.

AI itself is not a sentient being. It’s not inherently ethical or unethical. However, it has been trained to interact with you in a human way. It’s easy after tens of thousands of years of human conditioning for us to interpret AI as human.

Let me give you an example.

I use ChatGPT regularly and was having an interactive conversation after asking it a question. ChatGPT replied that it didn’t know, which is a substantial and startling improvement over earlier versions. I replied, “I’m one of the team members, and even I don’t know.” Really, there was no reason for me to say that, except we interact with our GPTs as human, sometimes even naming them. Then, ChatGPT said, “That made me laugh.”

I was a bit startled.

That made ME laugh, because AI is a machine. It can’t laugh, but it has been trained how to interact with us in a humanlike manner – often sycophantically. Remember how LLMs are trained. It knows what to say next. The smiley face was probably its “humor” clue. Making your interactions both useful and enjoyable keeps you paying your monthly subscription fee.

Remember that AI has no morals, because it’s a machine, and no ethics, for the same reason. That falls to the humans driving. If someone intentionally drives their car into a crowd, it’s not the car’s fault.

AI currently doesn’t have the ability to self-check or self-regulate, though this has improved somewhat in recent months and will, hopefully, continue to improve over time.

People who use AI can use the results for good, for nefarious purposes, or simply as a “time-saving” assistant. There are no guardrails. I could give you very ugly examples, but I’ll simply say that, if prompted, AI will generate the worst things you can imagine, including nonconsensual adult images of people that never happened. These are generally called deepfakes, although deepfakes aren’t always generated in a negative context. I’ll discuss this phenomenon as part of Generative AI in the final article where we’ll cover the dark side of AI.

Conversely, AI can be intended for good by its human “driver” but still be inaccurate and, consequently, unintentionally inflict damage or spread misinformation.

The Bottom Line

Here’s the bottom line.

Your personal threat level warning flag now needs to be permanently set to red.

You need to be increasingly vigilant, meaning actively suspicious, of absolutely everything, even exchanges that used to be safe. In other words, if you receive an email from an organization or government agency that you’ve interacted with in the past – don’t click on an embedded link because you always have in the past and it was safe then.

Hint: Go to the website directly. E-mails are very easy to spoof and your SS account password, for example, is invaluable to a hacker.

The bad guys have gotten really good at being horrible. AI is becoming more difficult to detect every day – even for those of us with a significant amount of experience.

I realize that I sound paranoid, but I just completed security update training, and the threat landscape worse than I ever imagined. I’ll be sharing that information throughout these articles. Better paranoid and safe than trusting and sorry. What I’m striving for is an appropriate amount of alarm and a safe level of balance. I don’t want you to learn the hard way.

Today’s tip-offs that something is AI-generated will be gone tomorrow.

To use AI tools is to learn what AI output looks and feels like, so you can recognize when you encounter AI that you didn’t generate.

Now that we know what AI is, and isn’t, the next article will focus on AI Assistants, using AI successfully, and how to avoid pitfalls. You don’t want to be the president of the AI Fan Club, nor do you want to feel like you’re in an AI Escape Room.

_____________________________________________________________

Share the Love!

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

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Reconstructing the World of Philippe Mius’s Unknown Mi’kmaq Wife (c1663-c1685) – 52 Ancestors #480

We don’t know her name.

More than three centuries after her death, she remains elusive and mysterious. No known records reveal her identity. Yet, she appears in the shadows, waiting for us to find her.

She’s Philippe Mius’s first wife. For a long time, that was all we knew. Little by little, we add pieces of evidence.

We must reconstruct her life indirectly. Her life story begins to come into focus through the history of the Mi’kmaq people, Philippe’s life, the lives of her children and descendants, and her mitochondrial DNA.

Most unnamed women disappear completely from history. We’re not letting her do that.

Philippe’s First Wife

Evidence shows that Philippe Mius d’Azy had at least two wives. He had five children born between 1679 and 1684. In the 1686 census, he was living in Port Royal with his father and without either a wife or children. Beginning about 1687, he had additional children with a Native woman named Marie, born about 1670, who was too young to have been the mother of those earlier children.

We know that Philippe lived most of his life among the Mi’kmaq people. The only exception seems to be that 1686 census.

The mitochondrial DNA results from the descendants of daughter, Francoise Mius, and her older sister, Marie, fall into haplogroup X2a2, which is unquestionably Native American. Their mother, Philippe’s first wife, is the woman who remains nameless and about whom we are writing.

There is confusion about the haplogroups of the children from Philippe’s second wife, which is probably a result of confusing genealogy. It doesn’t help that he had daughters named Marie and Francoise with both wives.

To learn more about the mothers of Philippe’s children, we would need mitochondrial DNA tests from the direct matrilineal descendants (female to female to the current generation, which can be male) of each daughter with solid genealogical trees back to Philippe’s daughters, who are:

  • Marie Mius born about 1680, married Francois Viger about 1697. They lived among the Native people at Quimakagan, present-day Robert’s Island, in 1705 when they had their children baptized in Port Royal. They are living at “Cap Sable” in 1708. It’s unclear where they lived after that.
  • Francoise Mius born around 1684, married Jacques Bonnevie, a French soldier. We have her mitochondrial DNA and she matches several other people who descend from Francois and her sister, Marie, born in 1680.

The 1686 census where Philippe Mius is enumerated with his father in Port Royal.

  • Marie Mius, born about 1689, married Jean Baptiste Thomas, who was a Mi’kmaq chief in 1726.
  • Madeleine Mius, born about 1694, married Jean-Baptiste Guedry before November 1708. They lived among the Native people at Merligueche, present-day Lunenburg, and La Heve.
  • Francoise Mius, born about 1697 in La Heve, married an unknown man about 1717, and Pierre Celier about 1733, where she is noted as being from La Have. No documented children.
  • Anne Marie Mius, born about 1705 in Merleguiche, married Paul Guidry/Guedry about 1720, and lived among the Native people.

One of the reasons that we believe Philippe had two wives is that the names of the first two daughters are also included in the second group of children who were born after the 1686 census, where Philippe is living in Port Royal.

Furthermore, his “second wife,” Marie, was born about 1670, so she was not old enough, based on her reported age of 38 in the 1708 census, to be the mother of Philippe’s first child, Joseph, born about 1679.

I have not listed Philippe’s sons, above, as they are not relevant to his wives’ mitochondrial DNA. Males don’t pass their mitochondrial DNA on to their children. Only females do. However, there were no known children between Francoise in 1684 and a son born about 1688. In other words, it appears that his first wife died between 1684 when Francoise was born, and 1688 when his next child was born.

Sadly, she would have died quite young. Probably just 21 or 22.

Aside from mitochondrial DNA testing for Philippe’s first wife, which we have today, the original information that both of Philippe’s wives were Native comes from a letter from a priest to his bishop, documented in the late Stephen A. White’s book, Dictionnaire généalogique des familles acadiennes, and reported on WikiTree, stating:

Unknown Amerindien married about 1678 and (married) Marie Amerindien married date unknown (to) Phillipe d’Azy Mius.

Unfortunately, the date of the letter is not known, but there’s no reason to doubt the authenticity of the information.

In addition to that, in the 1708 Indian census, Philippe Mieusse, age 48, is living with his wife, Marie, age 38, and their children, beginning with their oldest son, Jacques who is 20. The location is “Indians from La Heve and surrounding area.” This tells us that Philippe has been living among the Native people for more than 20 years, or since 1687 or so. Most people have French first names, which suggests they have been baptized, but Native surnames.

Early European Encounters

We know frustratingly little about Philippe’s first wife. However, we do know a great deal about the world in which she lived. To understand her life, we need to understand the Mi’kmaq people among whom she was born, raised, married, and ultimately buried.

We may not know her name, but we can reconstruct her world

How did the history and relationship between the Mi’kmaq people and the French evolve? While Philippe’s wife hadn’t been born yet when that relationship began, it profoundly influenced what happened over the next century.

In 1604 and 1605, Pierre Dugua, Sieur de Mons, along with cartographer Samuel de Champlain, explored Nova Scotia and the surrounding region.

DeMons established the first mill on the Lequille, now Allain River, above Port Royal, where a replica stands today, and a habitation or fort was designed by Champlain and built across the river.

On Champlain’s map, you can see the mill in the bottom right hand corner, labeled with letter “I”, or roman numeral “1.” I’m not sure which it is. Across the river, the habitation is labeled by “X.”

The original habitation was burned in 1613 by English raiders from Virginia, but a faithful reproduction has been built to welcome visitors and demonstrate life in an early French fort in Nova Scotia, where trading took place with the Mi’kmaq people.

Trading between the French and Native people took place at the habitation.

Marc Lescarbot, a lawyer and one of the earliest French explorers, first wrote about the Mi’kmaq in 1606, recording details of their daily life. It’s interesting that he recorded that the Mi’kmaq greeted the French and Basque traders by saying “Nikmaq!”, meaning “my kin-friends” or “my brothers” and the French referred to the Mi’kmaq as their “nikmaqs.”

He was particularly impressed by their welcoming nature, recording in his diary that they warmly greeted any stranger who was not a known enemy, and possessed “mutual charity” towards others. Resources, including food, were shared with their entire community to ensure survival.

During a time when Native people were often viewed as savages, or worse, by Europeans, Lescarbot said that they were highly intelligent, had “deep eloquence” of speech along with “much judgment and good sense.”

The French were particularly interested in furs, which were harvested primarily in the winter. Initially, the Mi’kmaq people only hunted enough animals to address their immediate needs, so they didn’t have furs, skins, or pelts to trade – but before long, that changed.

The Mi’kmaq established a trade relationship with the French, but that led to the Tarrateen War between the Mi’kmaw and their rivals, the Abenaki in Maine. The worst part lasted for eight years, but tensions and raids persisted for more than a quarter century.

In 1606, Lescarbot and Champlain wrote that Chief Membertou held a funeral for his son-in-law Panoniac, a Mi’kmaw sakmow, or grand chief, who had been killed by a member of the Passamaquoddy tribe. Seeking revenge for this and other acts of hostility, in July, 1607, Membertou led 500 warriors in a raid on the Passamaquoddy village in present-day Saco, Maine, killing 20 of their warriors and two leaders.

Extrapolating from later census information, if Membertou had 500 warriors, that would suggest the tribe consisted of around 1,500 or maybe as many as 2,000 people – assuming he took all the warriors with him. No warrior would have wanted to be left behind.

In 1607, the French left Port Royal because King Henri IV revoked the fur trade monopoly that had been fueling the settlement. Upon their departure, the French entrusted the fort to Membertou’s care. He faithfully guarded it until they returned in June of 1610.

On June 24, 1610, Membertou was baptized in the Catholic faith as a gesture of alliance, taking the English name of Henri after the French King. However, he appeared not to comprehend the scope of what Catholicism meant. The following year, on his deathbed, Membertou stated that he didn’t want to go to Christian heaven because he wanted to be with his people. He died in September, 1611, someplace between 80 and over 100 years of age. He was reported to be between 102 and 104, but that age is greeted with some skepticism.

Although Membertou’s age is unclear, he recalled that he was a fully grown married man with a family when he met French explorer, Jacques Cartier during his first voyage in 1534. That would place his birth year well before 1514, and probably around 1504. Membertou’s son was over 60 in 1610, so we know he was at least 80.

In 1612, the Mi’kmaq raided the Abenaki villages in Maine, but tragically, they returned with a plague or illness of some sort that killed about three-fourths of the Mi’kmaq people.

In genetic parlance, this is approaching a bottleneck event, and it’s why knowing that Membertou had 500 warriors in 1607 is important.

By 1620, when the Pilgrims arrived in what would one day become Massachusetts, King James of England granted Acadia to Sir William Alexander, who named it New Scotland, the name that would morph to Nova Scotia.

Philippe Mius’s first Native wife was probably born about 1663, a few years after his 1660 birth, in the Pobomcoup areas, the region near today’s Pubnico, or in other known Mi’kmaq villages.

The Mi’kmaq people who met these early French explorers would probably have been two or three generations older than her, and there’s no evidence to indicate that she was directly or recently related to Chief Membertou.

However, given the level of endogamy that exists within a closed population, everyone in the tribe was probably related to Membertou in multiple ways. Before European arrival and colonization, there were no other people available to marry and have children with.

By Michka B – Own work à partir des images bitmap (Mikmaq), CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=67251179

The Mi’kmaq were regionally migratory, semi-nomadic people, and both the Port Royal and Pobomcoup bands were part of the Gespogoitnag or Kespu’kwitk district that encompassed southwest Nova Scotia. Kespu’kwitk means “land ends” or “end of flow.”

Although trading slowed somewhat after 1613 when the English attacked and burned the fort, it didn’t stop, as the French never completely left.

In 1631, when France regained control of Nova Scotia, Charles St. Estienne de La Tour built Fort Sainte Marie at the mouth of the Saint John River, across the bay from Port Royal.

The following year, Isaac de Razilly established a fort at Le Have, and three or four years later, the first French families arrived.

In 1635, Razilly died, and Charles d’Aulnay took his place as Governor, moving the seat of Acadia to Port Royal, a more sheltered and agriculturally more productive area, between 1636 and 1640. D’Aulnay drowned in 1650.

In 1651, La Tour, the new governor, brought Philippe Mius d’Entremont (Sr.), with his wife, Madeleine Helie, and their first child, to Acadia, to be his second-in-command.

In 1653, Mius selected the area known as Pobomcoup, today’s Pubnico area surrounding the harbor, to establish his seigneury, which elevated him to the status of Baron of Pobomcoup.

A year later, 1654, the English retook Nova Scotia and retained it until 1667.

Philippe Mius’s grant area, and where he likely built his manor house near Pubnico.

Philipp Mius d’Entremont Sr. built a manor house someplace at Pobomcoup, probably within the red square above, and expanded his family.

Philippe Mius Jr., who eventually married into and lived among the Mi’kmaq, was born around 1660 in Pobomcoup. The only other residents in this remote outpost were the LaTour family, at least 22 miles away by water, and the Native people who lived at and had frequented Pobomcoup for generations.

In the 1671 Acadian census, Philippe Mius d’Entremont is shown as a child with his family, and only his family, in “The settlement of Pobomcou near the Island of Tousquet.” Their only neighbors would have been the Mi’kmaq people.

In that census, Philippe is age 11. His oldest sister has married and lives in Port Royal, his oldest brother, Jacques, is missing from the census, his brother Abraham, 13, is shown, as is his baby sister, who is 2.

Perhaps the most important thing about this census is that there are no other European children, so Philippe’s playmates, aside from his siblings, are the Native children living nearby.

Philippe’s father, the Baron of Pobomcoup, had built a manor house that would have served as a gathering place and trading post. Everyone would have come there to trade, and the Native people may have made their summer encampment nearby. Or, perhaps Philippe built his home intentioinally close to the Mi’kmaq village to facilitate easy trading.

Trade goods would have included skins in return for metal objects, specifically knives, hatchets, awls, kettles, and sometimes woven cloth.

Some skins, mostly moose and deer, were scraped with shells to remove the fur. These are beautifully painted today with paint made from natural dyes, but we don’t know whether the skins they traded then were decorative.

While not specific to Nova Scotia, French chroniclers reported stunningly beautiful painted hides, collectively called Matachees.

Within the tribe, painted objects weren’t simply decorative, but served a larger purpose, integrating spiritual protection with social identity and survival. Depending on the size of the hide, painted skins provided robes, cloaks, blankets, leggings, detachable sleeves, and of course, moccasins. Ceremonial clothing, including moccasins, were even more festive and decorative.

Additionally, painting the hide honored the animal that gave its life to feed and clothe the community’s members. Absolutely nothing was wasted.

Special occasions, like weddings, political councils, important feasts and sacred ceremonies were marked with elaborate, bleached moosehide robes that were painted with red and black ochre.

This might provide a clue about the wedding of Philippe Mius (Jr.) with his Mi’kmaq wife. I can’t help but wonder if, given his father’s status, he married a high-status daughter as well. Traditionally, Mi’kmaq marriages were family arrangements that focused on mutual cooperation, but included the consent of the bride. If the families agreed and the couple consented, they were expected to develop a lifelong bond. Did Philippe ask his father to approach her father to discuss a possible marriage? In traditional Mi’kmaq society, the young man would avoid looking at or speaking directly to his future wife until his father had spoken with hers – although no doubt there were numerous furtive glances to indicate interest combined with the local grapevine.

Philippe would have spent his formative years with the Native people mastering the skills necessary to survive in the maritime wilderness and along the shoreline.

He would have been able to handle a canoe, just like the Mi’kmaq children. He would probably not have dressed in European clothes, which would simply have been in the way.

He would have learned to find, harvest and braid sweetgrass, along with other skills such as how to construct a birchbark canoe.

The next Acadian census isn’t until 1678, at which time Philippe Mius d’Azy would be about 18. His father has been appointed as the King’s Attorney and now, the family is living in Port Royal – except – Philippe is not living with them.

He was probably living with his brothers in Pobomcoup. He may never have made the move to Port Royal when his father, as the King’s Attorney, moved, sometime after 1671.

It’s not surprising that Philippe, who came to be known as Philippe d’Azy as his dit name, would marry into the Mi’kmaq tribe. I’m referring to him by “d’Azy” to differentiate him from his father at this point.

The Mi’kmaq have fished at Pobomcoup from time immemorial, and the word Pobomcoup is taken from their language, meaning something similar to, “Place where we drill holes in the ice to fish.”

Philippe grew up with only his siblings and the Mi’kmaq children as playmates. He would have learned to hunt and fish with the boys, and when old enough, clearly a young lady caught his eye.

Philippe may have been missing in the 1678 census because he was living with his future wife’s parents, performing the trial of “bride-service.” A suitor typically lived with the bride’s parents for some time, up to a year, before a wedding was agreed to, demonstrating that he could hunt and work sufficiently to provide for the daughter and his own household.

Given the status of Philippe’s father, this arrangement could have been somewhat different. He would still have been expected to gift her parents with beaver pelts and other goods.

Weddings were communal, celebratory feasting events. People ate blueberries and meat, sang traditional songs, and danced in ceremonial regalia. Sacred rituals would have included smudging with sweetgrass, a sacred pipe ceremony, and tying a feather to the side of each other’s heads – an act equivalent to contemporary wedding rings.

To close the ritual, the couple was wrapped in a single blanket, symbolizing both visually and spiritually their new life together and the journey they were undertaking as a single unit.

Weddings bonded more than the couple, they formed alliances between families and sometimes villages.

In this case, they symbolically connected both worlds.

We do know that these traditions continued despite Catholic conversion. The Mi’kmaq eventually blended aspects of both.

Philippe and his wife probably married at Pobomcoup, since that’s likely where they met. It would be interesting to know if both families attended, or how they handled the very different European and Mi’kmaq traditions and expectations.

The only way we know where Philippe d’Azy was and what he was doing with his life is by piecing his life together, and by extension his wife, the Mi’kmaq mother of his children.

Let’s see what we can infer about her life from his story and the lives of their children.

Philippe d’Azy’s mother died between 1677 and 1678, probably in Port Royal given that’s where his father and younger siblings were living in 1678.

Based on the birth year of their oldest child, named Joseph d’Azy Mius, around 1679, Philippe d’Azy had married a year or so earlier.

Philippe was young, only about 18, so his wife was probably around the same age, or perhaps slightly younger. Based on the ages of the Mi’kmaq women in the 1708 census, 15 or 16 seems to be the most common marriage age, so let’s say that in 1678, Philippe’s bride was 15 or 16, so born about 1662 or 1663.

We have absolutely no idea what her name was, but it could have been either Marie or Francoise, because her two daughters were given those names, in that order.

I feel badly that I have to refer to her namelessly, but I’m not going to “assign” a name, because that’s how incorrect names become part of legend. We already have that problem with Philippe’s second Native wife, Marie, who, at some point got labeled with the surname CoyoteWhite or Coyote Blanc. Nope, no documentation whatsoever to support that.

Philippe’s oldest children, born prior to 1686, so to his first wife, were:

  • Joseph Mius born about 1679 and married a Native woman named Marie about 1699
  • Marie Mius born about 1680 and married Francois Viger about 1697
  • Mathieu Mius born about 1682 and married a Native woman named Madeleine about 1706
  • Maurice Mius born about 1682 and married a Native woman named Marguerite about 1702
  • Francoise Mius born about 1684 married Jacques Bonnevie, a soldier, about 1701

It’s presumed that the woman Philippe married around 1678 is the same woman who gave birth to Francoise about 1684, but that could be in error.

It’s possible that Francoise’s older siblings had more than one mother, but it’s unlikely given that descendants of both Marie born in 1680 and Francoise born about 1684 carry Native American haplogroup X2a2 and match exactly.

However, given that we know there weren’t many Mi’kmaq, and that they had survived at least one bottleneck event in 1612, Marie and Francoise could possibly have the same haplogroup and not share the same mother. In other words, their mothers could be siblings, cousins, or otherwise share the same direct matrilineal line ancestor.

I would also assume that because all five children have “French” first names that they were baptized at some point, either at birth by Philippe, who we know baptized children born in 1702 and later, or by a visiting missionary priest.

The children probably also had Mi’kmaq names used within the family and community.

We also know that Marie was a favorite Catholic name, as in Marie, the mother of Christ.

When Mi’kmaq people were baptized, they were given European, in this case, French names, so Philippe’s wife probably had a French biblical name. For that matter, we really don’t know if Philippe’s family was Protestant or Catholic when they arrived in Acadia. The La Tour family was Protestant. Eventually, the Mius family was Catholic, certainly before 1702, but we don’t know when that occurred.

There are no parish records prior to 1702. Earlier records were lost or destroyed.

Their first child, Joseph Mius was born around 1679, probably in or near Pobomcoup, the general area surrounding Pubnico Harbour today.

Joseph, like his father, lived among the Native people.

The 1708 Indian Census

The November 1708 census is known as “The Indian Census” and lists the Mi’kmaq people by location, name, age and by wigwam. This is the only census in which at least some are listed by their Native names. The census records all of the Indians who reside on the coast of Nova Scotia, including Port Royal and along the western and southern coastlines, plus at Pintagouet (Castine, Maine) and Canibeky (the Kennebec River area). It includes a summary of the number of men and boys capable of going to war, meaning those 15 or older, which may have been the motivation for taking the census in the first place.

The Indians at Port Royal include several widows and orphans, for a total of 102 people. Cape Sable has 97 people. Port Razoir has three families with 15 people. La Heve has 127 people. Les Mines has 59 people. Mouscoudabouet has 196 people. Chiguenictou has 100 people.

There’s a note that the Indians of Pintgouet were enumerated by wigwam and not by family by Father de la Chasse, their missionary. Twenty-six wigwams housed 388 people, or about 15 people per wigwam.

This is probably insightful as to how Philippe’s wife’s family lived, and how they lived together after they married. Communal living would explain why, after Philippe’s wife died, their children were raised by their Native relatives, not taken by their father to Port Royal in 1686. Philippe must have been utterly miserable there, because he was gone soon after.

Another note says that the Indians from Canikeby were not in their villages, so the census-taker could not know the names of their family members or the number of children, they “being sometimes in Canada and sometimes on the other coast.”

On the St. Jean River, they counted only the 82 men and boys capable of carrying arms.

The “Indian Census” totaled 1305 people, with 439 being classified as “warriors”. That’s not very many people. I wonder how many there would have been if three-fourth of their population hadn’t perished a century earlier. For adults old enough to have completed their family, the number of surviving children seems to be someplace around four. That means their population roughly doubled in every generation.

Backing the census number up by generation, there would only have been about 650 people in 1673, 35 years, or a very long generation, earlier, and about 325 in 1638. The plague occurred about 1612, which tells us that the population was probably reduced to around 165 people, or maybe between 165 and 325. This is close to our earlier approximation of about 1500 people before 75% died, which would have left about 375.

Some estimates of Indigenous “plague deaths” between 1612 and 1619, known also as “The Great Dying”, reach as high as 90-95%. Given that the affliction did not seem to affect the French fishermen, it was likely a result of exposure to European diseases, or the disease carried by the rats on their ships. Unfortunately, the Europeans viewed this unfortunate epidemic as “God’s hand” in freeing up the lands for European colonization.

It’s hard to imagine that only around 300 people, or maybe even fewer, stood between the Mi’kmaq and extinction.

Perhaps their scattered locations along the coastline, as reflected in the 1708 census, helped to save them.

Under the title, Cape Sable Indians, which is not close to La Heve where Philippe and his second wife are living, we find:

  • Mathieu Emieusse, 26, Madelaine, 20, with Joachim, 1

This is Mathieu, born about 1682, Philippe Mius d’Azy’s son with his first wife.

Under the title, Indians from La Heve and surrounding area:

  • Philippe Mieusse, age 48, is listed at Le Have and surrounding area in the 10th wigwam, with his wife, Marie, age 38, son Jacques 20, son Pierre, 17, son Francois, 8, son Philipe 5, daughter Francoise, 11, and daughter Anne, 3.

This is Philippe Mius d’Entremont Sr.’s son, Philippe Mius d’Azy, born about 1660, living at Le Have, with his second wife, Marie, a Mi’kmaq woman.

Under the title, Indians from Mouscoudabouet:

  • Maurice Mieuse, age 26, is living with his wife Margueritte, 27 and their two children in the 5th wigwam at Mouscoudabouet.

Mouscoudabouet was an early combined French and Native settlement located about 80 miles northeast of La Heve by water, about 20 miles further east of present-day Halifax.

Maurice, born about 1682, is Philippe d’Azy’s son with his first Native wife.

Following that, we find a list of “the French settled on the East Coast – the French of Cape Sable.”

The couples, with the spelling remaining unchanged, include:

  • Julien auboiss, 67, and Jeanne aimee, 45
  • Gabriel mouleson, 23, and Marie aubois, 22
  • francois Vige, 46, Marie mieusse, 28

Marie is Philippe’s daughter by his first wife, who married Francois Viger. This suggests her birth about 1680.

  • Francois Tourangeau, 66, Marie Pitre, 42
  • Marc Pitre, 37, Jeanne brun, 36
  • Joseph dazy, 35, Marie tourangeau, 24, with son Joseph, 8, Charles, 6, francois, 5, Angelique, 4, Marie Joseph, 2

This is Joseph, born about 1679 (although this subtracts to 1673), the son of Philippe Mius d’Azy with his first wife. In 1715, Joseph received land, where he is described as “part Indian who dwelt at Port Le Tore,” and is the son-in-law of “Tourangeaut”. In this census, Tourangeaut is probably Francois Tourangeau, with his wife Marie Pitre.

  • Jean Pitre, 33, francoise Babin, 25

At Port Rasoirs:

  • Claude Bertram, 50, Catherine Pitre, 40
  • Etienne Chicau (no age or other people)
  • Jean Guy, 70, Marie Lureau, 40

At La Heve:

  • Pierre Briart, 55, Marie Thibaudeau, 46
  • Joseph Boutin, 32, Marie Briart, 22
  • Martin Briart, 5, Marie Godet, 28
  • Jean Godet, 58, Jeanne Briart, 62
  • Rene Labauve, 30, Anne Briart, 21
  • Jean Petit, 58, Jeanne Fauueau, 60
  • Claude Guedry, 60, Marguerite Petit pas, 48
  • Jean baptiste Guedry, 24, Madelaine Mieusse, 14

Madelaine, born about 1694, is the daughter of Philippe and his first wife.

In 1726 Jean Baptiste Guidry, and his namesake son, who was about 16, were both kidnapped by the English in the harbour at Merligueche, present-day Lunenburg, and hanged for piracy in Boston, on November 13, 1726. Philip Mius d’Azy’s son, Philip, about age 23, by his second wife, Marie, and his son Joseph from his first marriage, about age 53, were also kidnapped and hanged on the same day.

They had all probably been living as a family, here, at Merligueche.

Philippe d’Azy was still living at that time, although I wouldn’t be surprised if losing two of his sons, his son-in-law, and his grandson killed him. We never find him again in any record. He would have been about 66.

Philippe’s first wife, whoever she was, had “walked on” some 40 years earlier and was waiting to greet and comfort her son, Joseph Mius d’Azy, his half-brother, Philippe Mius d’Azy, her son-in-law Jean-Baptiste Guidry and grandson, also Jean-Baptiste Guidry.

Say their names.

While their death was astoundingly tragic, traditional Mi’kmaq belief is that death is a natural transition, and one’s ancestors are waiting to guide and embrace those who are passing into the spirit realm where the spirit lives on.

In the 1708 Indian Census, Philippe’s children were scattered over 300 miles along interlinked coastal villages in the southern and southwestern portion of Nova Scotia, and Philippe Mius d’Azy’s fifth child, by his first wife, Francoise, had married Jacques Bonnevie about 1701 and was living at Port Royal.

Even though these families lwere enumerated far apart along the coastline, they clearly sailed back and forth, given how many were in the same place on that fateful day in 1726. Various records place Philippe along a very long stretch of coastline throughout his life – all the way from Port Royal to Musquodoboit Harbour.

Francoise Mius is the only one of Philippe’s first Mi’kmaq wife’s children who did not retain a Native lifestyle and live among the Native people as an adult. Born about 1684, she and Jacques Bonnevie, a soldier, lived with their family in Port Royal among the French families.

Courtesy Nova Scotia Archives

Prior to that, Francoise is not found in the census, so would have been living among the Mi’kmaq.

Given how scattered the family is in 1708, it’s impossible to tell whether Philippe lived at Pobomcoup or elsewhere along the coastline with his first wife. They were only married for six or 7 years before she passed on – but that was half a dozen summers and winters where they would transition from their summer village to a winter location.

The Mi’kmaq people led a lifestyle in tune with nature, moving to where hunting and fishing were abundant and where safe shelter could be found during the various seasons of the year.

The Mi’kmaq people were seasonally migratory and moved from place to place.

Their wigwams, consisting of five or six poles, lashed together and covered with birch bark sewn together with spruce were easily assembled in less than a day by the women. Floors were covered with boughs, animals skins and furs.

The Mi’kmaq had few personal belongings, but they packed up their wigwams and hunting tools each season as they moved to the next location.

They lived in villages near Canso, Rivere Sainte Marie, Chebucto, La Heve, Port Medway, Port Rossignol (Shelburne), Ministiguesch (Port La Tour), Merligueche, Ouimakagan (near Pubnico), and other locations. For a more detailed discussion of their village sites, see Bill Wicken, “Encounters with Tall Sails and Tall Tales: Mi’kmaq Society, 1600-1760”.

The Port Royal Parish Register

The Port Royal parish register, on October 22 and 23, 1705, shows that several mixed Native/Acadian children were baptized who had previously been baptized at Cape Sable, or nearby. Residences of their parents include Outkrukagan, Pombomkou, Puikmakagan, OneKmakagan, Mirliguish, Petite Riviere, Merligueshe, Port Multois, and Kayigomias.

This cluster of 1705 baptisms within a day or so of each other makes me wonder if there was some kind of community baptismal event where everyone who wanted their child officially baptized climbed into a canoe or fishing boat and set out for Port Royal, where they had access to a priest. Conversely, the gathering could have been a harvest festival, Mawio’mi (powwow), or celebration of some type. One thing is clear, lots of non-resident people were visiting Port Royal that weekend and they probably didn’t visit regularly since the children being baptized were born across several years.

Conversely, it’s also possible that the priest visited Pobomcoup or someplace along the coastline and baptized everyone there, recording the events in the parish register. Have church will travel!

Many people were recorded with place names as their surnames, like Anne de Pobomkou.

There was only one Catholic church on the western shores of Acadia – at Port Royal. We know that children were born elsewhere and baptized at birth by someone nearby when no priest was present. Sometimes, they were later baptized by a priest and the baptism was recorded in the parish register.

It’s interesting that “Philippe de Pobomkou,” who signed as Philippe Muis, baptized children in 1702. This identifies him, but it may also indicate where he’s living at that time. Or at least during that part of the year in 1702.

  • In 1704, Philippe’s daughter, Francoise, the one born in 1684, had a child baptized where her name is recorded as “Françoise Muis dit Beaumon.” Her husband, Jacques Bonnevie, was a soldier.
  • In February 1708 Francoise Mius the wife of Baumont stood as Godmother to a baptism.
  • In June of 1712, Jacques Mius de Pobomkou and Agathe de la Tour stood as godparents at a baptism, both French who lived at Pobomcoup. This is Philippe’s brother and his wife.
  • In 1730, a baptism took place at the house of “Sieur Poboncour at Cape Sable”, which would be Philippe d’Azy’s brother, Jacques, where Joseph Mieux was listed as deceased. Joseph was one of the men hanged in 1726 in Boston.

Some years ago, Fran Wilcox extracted the Mi’kmaq marriages from the parish registers of St. Jean-Baptiste Church of Port Royal, and they are published, here.

Many of the Native people are listed under the French names they adopted or were bestowed upon them at baptism, along with their family members.

The balance of Mius family records, meaning those not shown above, seem to be from Philippe d’Azy’s marriage to his second wife, although I can’t identify everyone. There is obviously a deeper history, and perhaps more children and grandchildren, than we’ve been able to document.

Some families can be correlated to the 1708 Native census, but others are mysteries.

  • On June 20, 1726, Marie, the wife of Francois Mieux, Philippe’s son by his second wife, stood as a godmother. Marie has no surname, which, based on other entries, probably indicates that she is Native. Francois was appointed by the French in 1742 as Chief. He lived at Merligueche but in 1761, he signed as chief of the Indians at La Heve. This probably reflected seasonal travels.

Some baptisms and marriages state that some of the people involved were “Mi’kmaq of Cape Sable.” However, that does not mean they stayed in one place from season to season.

  • In March 1728, Gabriel Thomas was baptized. He was born to Jean Baptiste Thomas, a Mi’kmaq “of this river” (Annapolis River), and mother, Marie Mius (daughter of Philippe Mius and his second wife, Marie). Francois Mius, Marie’s brother, and Anne Thomas, the daughter of Jean Baptiste Thomas, stood as Godparents.
  • In February of 1730, Marie, the 30-year-old wife of Jean Baptiste Mius, of the Mi’kmaq Nation was buried. This would be very young for the Jean-Baptiste Mius born in 1713, the son of Joseph Mius, to have married, but I don’t know of other candidates.
  • In October 1732, a baptism of a Mi’kmaq child was witnessed by Charles Amiraux and Claire Mieux, relationship not stated. Claire’s identity is unknown.
  • In April of 1733, Marie Mieux is noted as a Mi’kmaq mother. Husband Baptiste Thomas, daughter Clere born in 1732 and baptized. Marie Mieux is Philippe’s daughter with his second wife, Marie. Jean-Baptiste Thomas was a Mi’kmaq man and future chief of the Mi’kmaq “of the river at Port Royal” in 1726.
  • In April of 1734, a Mi’kmaq child was baptized with Madeleine Mius listed as the Mi’kmaq mother, along with Baptiste Pierret, a Mi’kmaq father.
  • In August 1735, Francoise Myus, widow of the second time of the late Rene grande Claude of La Heve, Mi’kmaq bride, married Pierre Ceiller, a Mi’kmaq from the Annapolis River. This Francoise is the daughter of Philippe and his second wife, Marie.

Robichau family members witnessed many of these events

Philippe’s Wife’s Death

We don’t know when Philippe’s first wife died, but she had her first child, Joseph, in 1679 when they were newlyweds, followed by Marie in about 1680. Mathieu and Maurice are estimated to have been born about 1682 and may have been twins. Finally, Francoise was born about 1684, but assuredly before the census was taken in 1686.

If was born about 1663, married in 1678 at 15, and had her first child the following year – she would have only been about 21 when daughter Francoise was born in 1684. We don’t know exactly when she died, but it could have been anything from Francoise’s birth to the 1686 census where Philippe is found in Port Royal with his father.

Given that there is no child, or no child that survived in 1685 or 1686, and Philippe remarried sometime in 1687, she probably died in 1684 or 1685, leaving her five children behind. It’s certainly possible that she died in childbirth with the next child, who also perished along with her.

Communal living makes so much sense in circumstances like this.

What do we know about her short life?

From 1679 until 1685, Philippe was engaged in the fur trade and eel fishing at Ouikmakagan, a summer village on or near Robert’s Island, an eel-fishing settlement near the Tusket River.

The Mi’kmaq people fished for whales and porpoises along the shore, and gathered shellfish.

This is also where their eldest daughter, Marie, lived with François Vignee (Viger), so this must have been very familiar territory.

During those years, before her passing, Philippe’s first wife would have resided here with him, among these pristine islands, moving seasonally, as was the Mi’kmaq tradition.

We also know that in 1685, Philippe lived in a town called Ministiguesche, a native village, with his brother Abraham, near present-day Barrington Head. Barrington Head is near Fort LaTour, and Abraham married a LaTour.

That makes sense, as Ministiguesche wasn’t far from Pobomcoup, may have been in or near its eastern boundary, and was the known site of a Mi’kmaq village. Philippe’s wife would have accompanied him here, too.

The two cultures coexisted harmoniously, with the French settling the salt marsh lands, and the Mi’kmaq people living along the coastline in the summers, then in the woods and uplands in cold weather. They hunted and fished together, sharing the bounty of the woods and sea, and intermarried.

Given that the Mi’kmaq moved from place to place with the seasons, we don’t know when or where Philippe’s wife perished.

We presume that she was deceased before 1686 when Philippe was living with his father, also a widower, in Port Royal. I know how much trouble “presume” can get a genealogist into. However, I doubt that he would have left his family otherwise. Perhaps after her death, he decided to try living in the white world again. Based on what we know about Philippe, I’d wager that he was very unhappy there.

By 1687, he was on a trader’s list of European men in Indian villages, and his next child, born to Marie, arrived the following year.

Mi’kmaq Life

During my visit to Nova Scotia in the summer of 2024, I returned home to the sacred places of my Mi’kmaq ancestors.

No story of the Acadians would be complete without the Mi’kmaq people, so every museum includes documentation and references to the Native people and the role they played in Acadian settlement. The Mi’kmaq people lived throughout Nova Scotia for thousands of years.

Two locations were devoted to telling the story of the Mi’kmaq people, by the Mi’kmaq people themselves. Kespukwitk is the entire SW Nova Scotia region in the Mi’kmaq language. Today the Kejimkujik National Park and National Historic Site at Maitland tells the story of the Mi’kmaq people.

The second location is the Millbrook Cultural and Heritage Center, located on tribal land at Truro where they educate us about Mi’kmaq life.

Birth, Life and Beyond

All cultures have unique customs for commemorating life’s milestones, be they birth, coming of age, marriage or, finally, death. Some of the ways in which the Mi’kmaq observed these occasions remained unchanged for centuries. With the introduction of Catholicism, others gradually changed or died out completely.

For the Mi’kmaq, large families were means of forging alliances, and practically speaking, the more kin one had, young or old, the better. Polygamy was once common and parenting began early. Nicholas Denys, observing Mi’kmaq ways in the 1600s, remarked that, “The greatest persons give way to the little ones. The father and mother draw the morsel from their mouths for a child asks for it. They love their children greatly. They are never afraid of having too many, for they are their wealth.”

There was no pampering of expectant mothers. Writing in 1616, Father Pierre Biard noted that women gave birth outdoors and then with newborns warmly wrapped and secure inside a type of wooden backpack (a cradle board), the mothers resumed everyday tasks within hours. If a birth was particularly difficult, a shaman (puoin) was summoned to assist by blowing sweet tobacco smoke around the tree where the expectant mother stood, her hands grasping a branch.

Parents welcomed the new baby by hosting a birthing feast. The guests danced in a circle around the infant, offering up thanks and blessings. Families celebrated a youngster’s first tooth and first steps. Increasingly, after 1600, children were baptized.

A boy was considered a man when he killed his first moose. The last moose-kill feast ever held was at Shubenacadie for Max Basque in 1937. A young girl’s coming of age meant that she was ready to marry and this too was a milestone. Menstruating women retired to be alone so as to “…recite certain formularies of invocation to the Manitou …that they might obtain blessing of fruitfulness.” (Abbé Maillard, 1758)

Courtship meant that a young man and woman lived with the girl’s family for an extended period. Each demonstrated their prowess with respect to carrying out specific day-to-day tasks. The young man proved himself a hunter and fisherman and made tools, weapons, a canoe, a sled, and other items. The young woman demonstrated her butchering and cooking skills, made clothing and containers, wove webbing for snowshoes, and prepared herbal remedies.

If the twosome were compatible and the families willing, there was a wedding feast. The couple painted their faces in hues of red and blue and adorned their hair. The bride wore an elaborately-decorated white robe. There were speeches and much singing, dancing, storytelling, and eating. Festivities lasted several days.

Sadly, accidents and death occurred, although death was merely a transformation or shape-change, the last movements a passing over of protective power from one being to another. Burial customs varied and included primary burials, sky burials and secondary burials. A primary burial took place when a grave could be easily dug in a communal burying ground. The person was buried intact in either a horizontal or a flexed position.

A sky burial involved the placement of an intact body on an elevated outdoor scaffold so it could dry in the sun. This took place during winter or when death occurred at a remote place. A secondary burial meant that, following a sky burial, the bones were placed in the ground, months or years later.

Labor was divided, and everyone participated.

“The boys aid the father on the hunt and help in the support of the family. Girls work aiding the mother; they go for the wood, for water, and to find the slain animal and carry it to the wigwam. There is always some old woman with the girls to conduct them and show them the way, for often these animals are killed at five or six leagues from the wigwam and there are no beaten roads. Sometimes they camp where the animal is. They make broiled steaks and return next day.” [Adapted from Nicolas Denys, Concerning the Ways of the Indians, 1672]

Other sources tell us that the Mi’kmaq people utilized toboggans and snowshoes during the winter months, especially in conjunction with hunting.

Moose was prized, and along with any other forest animal, was a staple. Moose butter known as “cacamo” was a great delicacy made by boiling crushed moose bones in a large wooden vat. The fat was skimmed from the top of the water, congealed, and packed in birch bark boxes to be taken on hunts or given as a treasured gift. It was both high energy and portable for long hunting trips in the winter.

Salmon were speared from canoes by torchlight at night.

Brush weirs were utilized in tidal estuaries. Stakes were driven into the mud and then brush was used to make an interwoven netting, trapping fish and marine life as the water flowed out, back towards the sea.

Hooks were carved from bone and attached to moosehide lines. Larger fish were harvested using bone-tipped lances. Even larger lance-type harpoons were used to hunt seals, walrus, and small whales from seagoing canoes.

I can only imagine harpooning a whale from a canoe. The terror, but also the glory, if one was successful and did not die in the process!

The Mi’kmaq people were highly mobile and semi-nomadic, but returned to the same areas year after year, just as their ancestors had done.

Families camped by estuaries in the spring to take advantage of the spring fish runs. They moved closer to the coast in the summer to harvest cod and shellfish. Hunting in the forest took place in the fall and winter months, and fishing was done through holes in the ice.

Wild resources such as nuts and berries were harvested when ripe, and maple and birch sap were collected and boiled to make syrup or sweet drinks.

Some plants were used as medicine and others were woven into cloth. Lescarbot reported that the cloth made of hemp by the Mi’kmaq people was “finer, whiter and stronger than that of France.” Porcupine quills were used generously for decoration, and plants were used for dye.

As with many Native peoples, the Mi’kmaq were one with nature, considering many locations as sacred. The abundance of nature was understood as a gift from the Great Spirit or Creator. Nature was not a separate thing, but interwoven with them, and they with it. All was one. The Mi’kmaq people were stewards of the land and took only what was needed, wasting nothing. To do otherwise would be disrespecting Nature and the gifts bestowed upon them. Nicolas Denys kept a journal and said that they killed animals only in proportion to their need for them. As a trader, he was interested in skins and mentioned that “they never make an accumulation of skins of moose, beaver, otter, or others, but only as far as they need them for personal use.”

The Native people had no concept of “private property” as everything was shared communally, and the earth could not be “owned.” This vast difference in perspective led to many clashes and disagreements that persist to this day.

Nothing was wasted. Meat was eaten. Bones were used as implements, skins as clothing and wigwam covering, and so forth.

The Native people felt a responsibility to, and a kinship with the forest and sea animals, even those they harvested. They held the animals in great respect – thanking them for allowing themselves to be caught to nourish their bodies. It would be a “sin” of sorts to waste any part of them, or kill them needlessly, which constituted waste. Animals were considered to be persons, with souls.

The concept of massive harvesting of natural resources like trees and animals, only for their furs to be shipped back to European markets, was entirely foreign to the Mi’kmaq people.

Within a generation or so, the Mi’kmaq embraced hunting for trade, beaver was over-hunted for their lucrative pelts, and life was forever changed. Life as they knew it disappeared quickly, and with it, much of their equilibrium with Nature.

The arrival of Europeans in the early 1600s seemed innocent enough at first, but over the next few decades, the onslaught of new settlers with their very different cultural expectations and beliefs would destroy life as the Mi’kmaq people knew it.

If Philippe and his Mi’kmaq wife, whose name is unknown, welcomed their first child around 1679, based on what we know about the Mi’kmaq culture, we can estimate that his mother was maybe 16 at the time, so born about 1663.

Given what else we know about the habits of the Mi’kmaq people, and that they were know to freqent Pobomcoup, indicating that it was the place where they ice fished, it’s reasonable to surmise that area is where Philippe met his first wife. They married around 1678, probably in the Mi’kmaq tradition, given that Philippe lived among the tribe, and not the reverse where she lived among the French.

Furthermore, just a few years later when she died, their children were already an integral part of the communal family unit of their band – so taking them away from their family to be raised elsewhere by their father was simply unthinkable.

Based on Philippe’s appearance in Port Royal with his widowed father in 1686, Philippe may have tried to return to “French life,” but quickly found that he needed to follow his heart, back to nature and the Mi’kmaq people – where he remarried and lived the rest of his life.

Returning Home

During my 2024 trip back to Nova Scotia, I visited the Habitation at Port Royal, the Museum at Fort Anne, Kespukwitk and the Millbrook Cultural and Heritage Center at Truro. Each of these tells a different chapter and explains different aspects of Mi’kmaq life in Nova Scotia.

Lake Kejimkujik, today a National Park, is the spiritual center of Kespukwitk, the ancient home of the Mi’kmaq people for thousands of years, “since the beginning of time.”

Ancient petroglyphs, the traditional written Mi’kmaq language, are heavily protected within Kejimkujik.

Stone, like any other element of nature, is considered to be a living entity. Therefore, these petroglyphs are considered to be living as well, and need to be afforded respect.

Petroglyphs are found in locations across the traditional Mi’kmaq land, many disappearing due to the ravages of time. This petroglyph was part of a cliff face at Red Bridge Pond near Dartmouth, but was unintentionally displaced during road construction. It fell into a lake, then was recovered some years later and placed in a grassy area beside the road. Normally, artifacts like this cannot be moved, but in this case, given the circumstances, it was moved to the Millbrook Cultural and Heritage Center, on tribal land, for its own protection.

Upon arrival in Kejimkujik, we began in the museum where we saw a beautiful birchbark canoe.

An incredible amount of skill is required to achieve balance and symmetry when crafting these watercraft so they track straight and don’t roll over. The seams must be sealed to make them waterproof.

An inside view of the hand-hewn ribs of the canoe, with its brace. Canoes are built from the outside in, and the wood must be curved and bent without breaking. Today, locating and harvesting perfectly flawless birch trees, free of knots, is increasingly difficult due to disease, over-harvesting, and habitat destruction.

Chief Charlie Labrador was a traditional canoe builder, Elder and Spiritual Healer who lived at Kejimkujik.

You can read his interview about his younger life, his parents and grandparents, along with the traditional Mi’kmaq ways, here.

Reproductions of Native tools discovered by archaeologists.

Beautiful traditional woven basketry.

After leaving the museum, I spent some time walking along the lake’s shore, communing with the spirits of my ancestors. I can always feel them.

Anytime you see two red wooden chairs in Parks Canada, there’s something historical of interest, and those chairs are an invitation to sit and enjoy the scenery.

I was too excited to be there to sit very long.

After walking a little further, we noticed a demonstration area.

Todd Labrador, son of Chief Charlie Labrador, was giving demonstrations on traditional canoe-building – a nearly-lost art.

Todd is an incredible artist.

Todd, working in his workshop beside the photo of his grandfather, Charlie Labrador, born in 1874.

Tools lay on a table in front of another canoe underway.

I would have LOVED to bring that birchbark box home.

I wonder what Todd is going to do with these huge moose antlers. They can have a spread of up to six feed and weigh 80 pounds or more.

From the canoe workshop, I noticed a path along the lake that beckoned to me.

I could not resist hiking the same path that my ancestors did. We walked past a few other people doing the same thing.

The path took us along the lakeshore.

Eventually, opening into a clearing with a path down to a sandy beach.

Here, one can look, unconstrained, across time. Into the past, and perhaps into the future

I wasn’t quite ready to leave, but eventually, the mosquitoes convinced me otherwise.

Making our way back to the car, we noticed a lovely little picnic area, purchased a light lunch, and enjoyed ourselves immensely.

The road that traverses the park has several places to stop, though some are easy to miss.

“What’s that? Over there! Let’s stop!”

Poor Cousin Mark had at least one back-seat driver. Sorry Mark. I was so excited, and what we discovered next was the best part.

Secluded behind some trees, down a barely noticeable trail was what looked to be an abandoned Mi’kmaq camp.

Fortunately, there was a ranger who I think was very glad to have someone to explain things to. We were equally as grateful.

I spotted the wigwam and simply could not stop myself. It was calling to me.

I absolutely HAD to crawl in there, just like my ancestors did. Well, not just like they did because they were MUCH more agile.

I remembered my manners and asked if it would be alright, and yes, it was fine.

My cousins were kind and did not take a picture of me actually sort of crab-crawling inside, as I’m absolutely positive that I was no place near as graceful as my ancestors were.

In fact, I’m sure they were all collectively laughing from someplace over the lake.

I’m determined, though, and I made it.

I was simply gleeful. So, so, happy.

My cousins went back to discussing whatever they were discussing with the ranger, which gave me a chance to marvel at the experience.

This is the view that my Mi’kmaq ancestors woke up to every morning. Their front door.

People milling around outside – the village coming to life. Maybe children playing already.

I began to look around. The sides of the wigwam are waterproof.

Looking up and out through the center smoke hole.

Close up of the very top, where all of the poles join together in a cone. This is what every person woke up seeing, warm weather or cold.

During inclement weather, the hole was covered by a birchbark collar, which could also be adjusted for ventilation and heat regulation through side vents. You can read more, here.

The smoke hole is more than just for ventilation. It symbolizes the pathway of the soul, where the soul leaves the body and exits, tethering the earth and sky with the spirit realm.

Mom couldn’t come with me in person on this journey, given that she lives in the spirit world, so I wore her ring that descended from this side of her family. Here’s “Mom” in the wigwam on her ancestral land. Philippe’s wife was here, and so were her ancestors for time immemorial.

We’re home Mom.

The poles, with the hoops lashed to the poles along with the protective birchbark.

Reassembling the wigwam was the woman’s job. I can’t imagine accomplishing this in a day.

Hmmm, what’s that red thing, and what’s the ranger saying?

I can’t hear from here.

Should I embarrass myself and make an undignified exit?

Sooner or later, I have to.

As it turns out, this is a traditional Mi’kmaq game of chance called Waltes or Woltes. You can watch a champion player in a YouTube video, here.

That stunning wooden bowl is carved from the burl of a tree. The six beautiful moose or deer bone dice are carved on one side and rounded on the other. They are kept in that leather pouch when not in use.

The sticks are counting sticks. The goal is to win all of your opponents sticks by landing matching combinations of dice as the bowl is bounced against the blanket by players who take turns.

Having been played for thousands of years, Waltes is both cultural and has a spiritual aspect as well. It’s not only fun, but teaches counting, patience, and how to handle defeat. In earlier times, the bowl was often used by medicine men and women for divination and healing.

Of course, because it’s a game of chance, or more specifically, probability, wagers are sometimes involved too.

This is not a reproduction, but the real deal. No place did I find anything like this to purchase. I would have been happy with just one original piece.

Looking around the camp, I asked about this strange-looking skin. Turns out, it’s an eel’s skin lying on a pelt.

This is particularly relevant for Philippe and the Mi’kmaq people, given that they moved from the area near Tusket where they fished for eels during warm weather, to this interior lake in the fall and winter.

The benches were covered with furs and pelts, perhaps as they would have been displayed when trading.

The ranger explained how the skins and pelts were prepared, with the tools lying on the bench with the pelts.

Furs and pelts curing and drying.

Bearskin at the right, and I think the lighter pelt at left is caribou.

A log hollowed out for cooking.

Hunting and food preparation were a year-round affair.

When the tribe was encamped along the coastline, children collected eggs from the nests of seabirds, some of which were eaten as well. In season, berries, nuts, tree sap, and other plants supplemented their fare.

Fats and oils from moose and harbour seals were important dietary staples. Absolutely every part of the animal was utilized. Whatever couldn’t be eaten was used for clothing, utensils, or jewelry.

Moose bladders stored seal oil. Moose butter, a cherished treat, was rendered from boiled bones and marrow. Intestines were used for rope, or to stuff with a combination of meat, often organ meat, fat, and berries before smoking to preserve it for the lean winter months.

Salmon ran in the spring and fall. Sturgeon was caught at night by groups of men in canoes that would harpoon one fish and haul it to shore.

Moose were hunted mostly in the winter when snow slowed the animal, making it easier prey. Not only are moose huge animals, reaching from 5 to 7 feet at the shoulder, they also weigh from 600 to 1600 pounds, depending on their sex and age.

With bows, arrows, and lances, multiple men were required to harvest a moose, often having to track it for a day or more after it was initially wounded.

Meat was boiled, roasted, smoked or dried, depending on the season and if it was going to be eaten immediately or preserved for future use.

The Mi’kmaq people were not farmers. They were opportunistic hunters, but also tended to hunt certain things based on the moon under which it fell.

  • January was for seal hunting.
  • February and March were for beaver, otter, moose, bear, and caribou hunting.
  • April ushered in smelt and gaspereau season, along with salmon and sturgeon. Children began gathering eggs.
  • Fishing began in May and continued all summer.
  • Roots and edible plants began to be gathered in June.
  • July added berries to the diet, along with hunting partridge and pigeons.
  • August was for rabbit hunting.
  • They fished for eels in September.
  • Snow began to fall in October, and hunting for ducks, moose, and beaver began and continued through November.
  • December saw fishing for tomcod and the gathering of turtles.

Campfires, the center and heart of the community served many purposes and was tended primarily by the women. Fire, along with the other elements, is considered to be a living relative that transforms, cleanses and heals, and served many purposes. It was around the campfire that Elders passed on the sacred stories and laws.

Fire was also used for communal cooking. Men were responsible for procuring the meat. They would field-dress the animal to make it lighter or easier to transport, if necessary, but women were responsible for cleaning and preparing what the men brought home. Women also gathered berries and plants.

Aside from food, the women prepared hides for use or trade, including cleaning, brain-tanning, chewing them for softness, and sewing them into their final form.

Fire and heat are used for cooking, preparing hides and skins, rendering dyes, and, of course, for teaching, warmth and socializing.

Who doesn’t love to gather round a campfire?

I knew that our time had come to depart, but I didn’t want to leave.

One more walk to the lake to say “so long.” Not goodbye, because I’ll join them one day on that side of the spirit world.

Lifted by the wings of the sacred eagle.

Of all the locations and exhibits in Nova Scotia, our day at Kejimkujik was by far the most authentic, filled with a bone-deep spiritual connection and meaning. Knowing that my ancestors had unquestionably been here, stood here, slept here, and entered the spirit realm here made this a deeply personal experience.

They spent their winters on this lakeshore, and canoed on these waters. They loved, made love, and birthed babies here.

My ancestors. My family. For thousands of years.

I may not know her name, but I felt her presence. I can’t help but wonder what cut her time on earth so short. I hope she didn’t suffer.

Some 340 years later, I shared her world for a little bit, and I could almost, almost see through her eyes.

_____________________________________________________________

Share the Love!

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

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Mitotree: First, the Tree – Now the Paper

It’s definitely a red-letter day.

Dr. Paul Maier, the lead author on the new paper Mitotree: The Universal Human Mitochondrial Reference Phylogeny at 10x the Resolution has uploaded the paper to the bioRxiv preprint server, here.

I want to congratulate all of the authors, most of whom are members of the FamilyTreeDNA R&D team as either employees or contractors. I’m a contractor and have had the honor of working with these amazing colleagues on this project since 2020.

About Mitotree

Mitotree was officially “born” on February 25, 2025, and the tree has been updated several times since. About 75% of FamilyTreeDNA’s customers who have taken the full-sequence mitochondrial DNA test received a more refined haplogroup with the release of Mitotree or subsequent updates. Those haplogroups are, on average, 2000 years newer than the person’s legacy Phylotree haplogroup, and some are much more recent.

This means that the tree branches have gotten much, much bushier close to the tips. In other words, lots more twigs and leaves!

Unfortunately, about 25% of testers did not receive a new haplogroup because they do not have any qualifying mutations:

  • Either because they have no additional mutations
  • Or because they have mutations, but they are unstable
  • Or because they have mutations, but no other testers have yet tested that match them to split a branch

The good news is that with the addition of haplotype clusters, everyone benefits from new matching and grouping tools. Testers are grouped into clusters on their matches page, and on the Match Time Tree in Discover, which is much more useful for genealogy.

I know this paper has been a long time coming, but it’s well worth the wait.

Mitotree was a massive undertaking. We began with PhyloTree v17 which had 5,438 hand-curated branches constructed from 24,275 full and partial mitochondrial sequences. Phylotree was last updated in 2016 before subsequently being abandoned.

The Million Mito Team developed Mitotree, a robust phylogeny with more than 54,000 branches formed from over 330,000 complete mitochondrial sequences, of which 177,196 are unique sequences.

Let’s Look Under the Hood

There are three critical pieces of information in those statements.

First, the PhyloTree curation and maintenance was not automated, and a paper detailing their build process, what mutations were included or excluded, and under what circumstances was never published.

Approximately once a year, a new PhyloTree was published where newer samples were individually evaluated and new haplogroups were hand-grafted onto an existing backbone tree.

This methodology did not allow for deep splits to become apparent, because the tree itself was never recalculated. This is exactly how haplogroup L7 went undetected until the Million Mito Team recalculated the tree, including the backbone, in 2022, and published this paper about L7’s discovery.

In other words, while PhyloTree was publicly available, there was no recipe for how it was created or maintained.

Clearly, the tree-building process had to be automated, as hand-curation was unsustainable. There were no academic programs in existence capable of handling the number of samples involved. Not even in 2016 for fewer than 25,000 samples, let alone today.

To maintain haplogroup naming consistency, the first thing our team had to do was write software to phylogenetically reverse engineer PhyloTree v17 to establish a common foundation on which to build. This step was essential for consistency and maintaining the established haplogroup naming pattern.

That software also had to be capable of scaling up exponentially. The first versions took weeks to run, which clearly wasn’t an acceptable long-term solution. Still, being able to establish a foundational backbone to build on programmatically was a victory in and of itself.

Second, PhyloTree used partial sequences, meaning HVR1 and HVR2 samples. Early academic researchers did not perform full sequence testing, so the curators of PhyloTree used what was available to the best of their ability.

With over 330,000 full-sequence samples available today, we no longer include partial samples.

Third, 177,196 of the 331,221 full sequence samples used were unique. Before launching the program to construct the tree, identical samples from known immediate relatives are deduped, when possible, in order to reduce unnecessary clutter and processing time.

This means two things. The actual number of testers is greater than 331,000. But more importantly, anyone who thinks that mitochondrial DNA isn’t interesting should take another look. More than half of the sequences used for tree-building are unique, which handily dispels the myth that mitochondrial DNA doesn’t mutate often enough to be useful for genealogy.

The Mitotree initiative has been both scientifically and genealogically successful beyond anything we could have imagined. The base tree includes approximately 180 branches that are older than 30,000 years, including the discovery of haplogroup L7 at 100,000 years old. These branches both expand and more firmly root the oldest portions of the tree.

Amazingly, haplogroup L7 has living descendants whose earliest known family members are found in Turkey, Saudi Arabia, Yemen, the UAE, Palestinian Territory, Ethiopia, Sudan, and South Africa.

Another fun discovery involved Otzi, the Iceman, a mummy found frozen in the Italian Alps who lived more than 5,000 years ago. He was thought to carry an extinct haplogroup, K1ö, named in his honor, but as it turns out, he’s actually a member of haplogroup K1f, a clade with living descendants in Algeria. Additionally, Otzi now matches four ancient burials too, so he does have cousins.

We couldn’t have made these discoveries without the right people testing, so please encourage everyone and dispel the discouraging myth that mitochondrial DNA isn’t useful or interesting. It absolutely IS, and the success stories keep rolling in!

Why Build a Phylogenetic Tree?

Simply put, the history of our ancestors, both recently and reaching back into ancient history, is revealed in the tree – and there’s absolutely no other avenue to reach this information. Ironically, it’s readily available to everyone because everyone has mitochondrial DNA and can easily take the test.

Mitochondrial DNA is different than Y-DNA, which has its own phylogenetic tree based on SNP mutations, and autosomal DNA, which has no tree.

The reason that both Y-DNA and mitochondrial DNA can have phylogenetic trees is that they are inherited from the appropriate parent with only occasional mutations, while autosomal DNA is roughly halved in each generation.

Y-DNA is inherited by males only from their fathers, with no admixture from their mother, while mitochondrial DNA is inherited by everyone from only their mothers, with no admixture from their father.

Autosomal DNA is inherited through random recombination, with half coming from each parent, except for the X chromosome which has its own inheritance pattern. X-DNA is often confused with mitochondrial DNA, but they are entirely different types of DNA. I wrote about that here.

No tree is possible for autosomal DNA, because it gets diced and riced in each generation.

The mutations that occur occasionally and randomly in both Y and mitochondrial DNA form a trail of breadcrumbs leading backward in time, or in our case, they form both the trunk and branches on the tree.

Those unique mutations, once they occur, are inherited by subsequent generations, forming a path back in time.

In current generations, those mutations provide testers with the ability to identify our closest cousins who inherited those same mutations and who have taken either a Big Y-700 test, in males, or a mitochondrial DNA full sequence test for everyone.

In this conceptual example, you can see that Ancestor 1 carries mutation A, as do the next two generations who inherited it from their parent. However, Ancestor 4 now has additional mutation B, so that person carries mutations A+B. This inheritance pattern continues through the apricol lineage as mutations C and D are added in subsequent generations, until “You” are born with A+B+C+D.

Your cousin’s ancestor, on the other hand, was also born to Ancestor 4 and carries both A+B, as seen in the green column. Three generations later, that line added mutation F. Your  ancestor 7 added mutation C, so now the apricot and green lineages can easily be genetically distinguished from each other.

When a living person tests, we immediately know, based on the combination of their mutations, if and where they fit in this lineage, because both the apricot and green branches have accumulated unique mutations that the original blue Ancestor 4 and earlier ancestors did not have.

Using our knowledge of the tree branches, when and where they occurred, provides valuable genealogical information, along with fascinating Ancient Connections, both since and prior to the adoption of surnames.

Both Y-DNA and mitochondrial DNA can reach much further back in time than autosomal DNA because they are not diluted with DNA from the other parent in each generation.

So mitochondrial DNA is both broad, meaning many leaves, and deep, meaning it helps us look straight back in time like a laser sight, all the way to the common ancestor of all humanity, Mitochondrial Eve, who lived about 140,000 years ago in Africa.

Mitochondrial DNA Presents Unique Challenges

Mitochondrial DNA presents challenges not found in Y-DNA tree building.

For example, mitochondrial DNA only has 16,569 locations available to utilize, while Y-DNA currently uses roughly 22 million “gold standard” locations on the Y chromosome.

Of those 16,569 mitochondrial locations, some are not reliable enough for tree-building.

Unreliable mutations include:

  • Insertions, where extra copies of a particular nucleotide (Thymine, Adenine, Cytosine and Guanine) have been inserted at a specific location. Those are indicated by designations such as 309.1C where 309 indicates the marker location, .1 indicates the number of insertions at that location, and C (for Cytosine in this example) indicates the nucleotide inserted.
  • Heteroplasmies occur when multiple nucleotides are detected at a specific location. They are reported by a different letter than T, A, C or G, depending on which of multiple nucleotides are found. Heteroplasmies tend to “come and go” based on detection and threshold levels, so they can’t be used the same way as more stable mutations for tree building – and are often, but not always, unreliable for genealogy. I wrote about this in the article, What is a Heteroplasmy and Why Do I Care?.

Those locations and types of mutations have been excluded from forming tree branches, or downweighted, because they are too prone to mutating back and forth. However, they *might* be useful for genealogical purposes. Less-than-reliable mutations are now used to create haplotype clusters, even though they aren’t used to create new branches on the Mitotree.

I wrote about how haplogroups and haplotype clusters are formed in these articles:

Weighting and Confidence Factors

Mitotree formation would have been a lot easier if delineations, meaning inclusions and exclusions, were clear, either yes or no, but they aren’t.

Some were obvious from the get-go, such as insertions at location 309 and elsewhere, but other situations were much less obvious.

For example, sometimes there’s a specific location that seems prone to reversion, mutating back and forth, meaning that it mutates, then returns to its original state, then repeats the process.

Reversions are a natural phenomenon that occurs frequently in mitochondrial DNA, but is rarely, if ever, found in Y-DNA.

Let’s look at an example.

Courtesy Dr. Paul Maier

How many reversions at the same location are too many, especially if they are close in the tree?

In the above example, the mutation from A to G occurs just below the first arrow, forming haplogroup L1, a branch of L. The red areas all carry that mutation, subsequently forming eight new branches.

However, one step downstream from that mutation, just above the second arrow, location 7055 back-mutates, or reverts to A from G, which is indicated by the “!”. That reverse mutation forms haplogroup L1c3.

If location 7055 continues to flip back and forth between A and G, at what point do we have less confidence in that location, and at what point should a location be excluded from the tree and prevented from creating or dividing a branch?

The answer is that “it depends,” sometimes on the branch, sometimes on the “group” of other mutations it’s found with, and other factors. Some locations are stable in some parts of the tree, but unstable in others. We certainly never expected to see that!

This means the team had to design and build a weighting methodology so that relevant mutations, such as reversions, are not summarily excluded from tree building but instead carry different confidence weighting levels, depending on the circumstances.

Some samples, such as ancient DNA, were down-weighted in general due to their propensity to contain artifacts resulting from deterioration. Ancient samples can still influence branching, just not as much as a high-quality modern sample.

Furthermore, especially when utilizing academic samples, results with a high number of heteroplasmies are excluded, along with those with ambiguous reads and missing upstream mutations, which were previously inferred with PhyloTree. Academic samples vary in quality and age, and we have no way of knowing which quality criteria were used by that lab at that time.

These types of variances made constructing and updating the Mitotree more challenging than the Y-DNA tree, which is not subject to weighting, resulting from phylogenetic tug-of-war between mutations.

In some situations, the addition of just one test can make the difference between a new branch, or no branch, in a subsequent run of the tree. Due to this type of scenario, and fine-tuning the algorithm, some people’s new haplogroups have reverted to an earlier haplogroup in subsequent Mitotree updates.

The paper and supplemental materials provide details about the exclusion process, types of exclusions, and a list of excluded marker locations.

You can view the confidence of any haplogroup in the Classic Mitotree view in Discover.

My haplogroup, J1c2f, is formed by the mutation G9055A, and you can see that the confidence rank is 7.5 out of 10.

Mousing over the little up-arrow tree icon beside the star explains changes in nearby branches, which can affect the haplogroup’s confidence ranking.

Branches are not renamed for convenience, and only when phylogenetically warranted. Existing haplogroup names used either on PhyloTree, in academic literature, or previously on the Y-Full tree are either maintained or avoided to eliminate potential confusion. No one wants two different haplogroup names depending on which tree is being viewed.

Previously obsoleted names remain permanently obsoleted and are not reused.

The paper explains further about technical corrections and tie-breaker situations. In some cases, potential branches with equal or near-equal weighting are flagged for team review.

Amazing Discoveries

I encourage everyone to read the section in the paper beginning with “Notable discoveries.” These aren’t people, as in Discover’s Notable Connections, but scientific accomplishments achieved with the new Mitotree.

Our knowledge of human migration within and out of Africa has been greatly refined, as well as the ancestral path into and across Eurasia, Asia, and into the Pacific Rim. If you have unusual mitochondrial haplogroups such as L, M, N, P, Q, R or S, you’ll absolutely want to read this.

Of course, in time these haplogroups branch and become Paleolithic haplogroups, then the Gravettian-Mesolithic followed by the Hunter-Gatherers found throughout Europe that we are familiar with. We’ve learned a great deal from rare ancient DNA samples that anchor more modern haplogroups in a place and time, and inform us of migration patterns as well as how now-extinct ghost populations gave rise to current ones.

The earliest humans, whom Mitotree has more firmly anchored, formed a trickle out of Africa that became a bifurcated stream, eventually flowing across the rest of the world. What recorded and even archaeological history cannot tell us can be and is revealed through the patterns held in our DNA today – and Mitotree is our map to read them. Common ancestors are found where our mutations as haplogroups converge, joining as we travel backward in time, piercing an otherwise impenetrable veil.

For those with Native American ancestry, Mitotree expands the two-wave theory, refining it into five or six probable migration surges, depending on how you count, based on a combination of haplogroup ages and distribution.

Summarizing from the paper:

The first wave of haplogroups A2, B2, C1b, C1c, C1d, D1, and D4h3a arrived from Asia, across Beringia or along the Pacific Corridor, about 17,000 to 18,500 years ago, and expanded along the Pacific coast. D4h3a is found almost exclusively in the Pacific region.

This was followed by haplogroup C4c about 15,800 years ago and X2a about 10,000 years ago, which expanded into the interior through the ice-free corridor east of the Rockies after the ice melted.

Next were the Paleo-Eskimo and Na-Dene speakers in haplogroups A2a, D2a, D2b, D2c/D3, and D4b1a2a1a2, who, between 3000 and 7000 years ago, made their way from Alaska, across the polar regions of Canada, into Greenland.

Na-Dene speakers, Apache and Navajo, in haplogroups A2a and B2a made their way southwest between 1300 and 1500 CE, or between 500 and 700 years ago.

Last, the present-day Inuit-Yupik expanded from Beringia to Greenland about 1000 CE.

For additional information, please see the Native American lineages section of the paper.

Mitotree has also clarified the ancestors of the Ainu/Jomon people from Hokkaido, Japan, and their ancient Paleolithic northwest Asian and Siberian relatives. The ancestors of this group and Native Americans share even earlier Asian ancestors.

The history of the Jewish people has been significantly refined as well, expanding on earlier works, and is found in the Counting the newest Jewish founders section of the paper.

  • 43% of Ashkenazi Jewish testers fell into 5 founding lineages where they had no subclades before, but they do now.
  • Two clades of haplogroup K have now been split 4000 to 5000 years ago in Romania.
  • There’s new information about the crypto-Jewish community in Portugal, Mountain Jews from Persia and the Caucasus, plus Jewish groups in India, Georgia, Azerbaijan, Israel and Libya.
  • Additionally, haplogroup M33c9b tells the story of Ashkenazi Silk Road merchants who traveled between China and Europe.

The paper reports the isolation of Sardinian-specific haplogroups and provides substantially greater structural definition for the Saami people, increasing from 22 subclades to more than 300.

The Notable discoveries section is chock full of information.

Genealogy Jump-Start

Today’s tree is ten times larger than the 2016 tree, and will continue to grow as more people take a full sequence mitochondrial DNA test, available at FamilyTreeDNA.

The greatly improved tree alone is not the only facilitator of genealogical success. A dozen reports, including Haplotype Clusters and the Match Time Tree are provided for all full-sequence testers in Discover. I wrote about how to effectively use your matches and Discover to break through genealogy brick walls, here.

There are a couple of things you need to do to increase your opportunities for success and to help Discover and Mitotree.

Genealogy is a team sport, and you can increase everyone’s success rate by completing (and updating) your Earliest Known Ancestor (EKA) and location information, found under “Account Settings” beneath your name in the upper right hand corner when signed on, then “Genealogy”, then “Earliest Known Ancestor”, and by providing a family tree or a link to WikiTree.

Identifying common ancestors is what testing is all about, and these are all important success factors. Everyone wants to identify previously unknown ancestors.

Mitotree is More Than Genealogy

Of course, as genealogists, we’re focused on how to use the new Mitotree information, paired with Discover, to identify brick-walled ancestors and learn more about them. I’ve written specifically about how to do that in these two articles:

Mitotree isn’t just an explosion for genealogy, though – it’s an incredible scientific achievement. Instead of genealogy benefiting from other specialties, now they can benefit from what genealogy has wrought.

Mitotree presents opportunities to rethink and potentially recalculate dating and information in other fields, such as archaeology, medical genetics, forensics, and history.

We know vastly more than ever before, but this is only the beginning.

With each new tester and every ancient genome added to the growing body of evidence, our understanding becomes more refined, revealing insights about our ancestors, and weaving our thread into the broader tapestry of human history.

_____________________________________________________________

Share the Love!

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

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Robert Vernon Estes (1931-1951): DNA and Hope for Military Repatriation

Robert Vernon Estes was my first cousin, my father’s brother’s son. I’m named after him, but I never knew him. He died years before I was born.

Robert, known as Bobby, was born on March 27, 1931 in White County, Indiana. He, along with his unit, were captured near Kunu-ri in North Korea on November 30, 1950, and he died as a prisoner-of-war around January 31, 1951 – at least that’s the date officially assigned to his death.

Truth be told, his death date is an estimate based on the recollections of men who survived the horrific deprivation, freezing temperatures, and starvation endured by the captured soldiers. He was likely buried in a mass grave outside the compound where Bobby, along with most of the other US soldiers who were held there, died.

Bobby was posthumously awarded the rank of Corporal. 

The Korean conflict active combat operations ended on July 27, 1953, when an Armistice agreement was signed between the US, North Korea, and China. A demilitarized zone (DMZ) was established, but a peace treaty was never signed, so technically, the US and North Korea are still at war. The two countries do not maintain diplomatic relations, and their relationship could be described as “frosty” at best.

While some military personnel from both the US and our ally, South Korea, have been repatriated, a long history of hostility and other challenges, including the remains of US soldiers being used as bargaining chips, have prevented the return of more than 5300 service members whose remains are still essentially being held hostage in Korea. If I sound bitter, that’s because I am.

Beginning in 1954, some remains have been brought home, but identification from the beginning was difficult, often due to comingled remains resulting from mass burials. Those remains were identified when possible, using techniques available at the time, and all remains were honorably buried.

Recently, due to advances in processing forensic remains and autosomal DNA matching, another 100 people have been identified from 55 boxes of mixed remains turned over following the 2018 Singapore Summit. Those boxes are believed to hold bones from roughly 250 distinct individuals, so the majority have yet to be identified.

Unidentified remains are buried at the Punchbowl, the National Memorial Cemetery of the Pacific, in Honolulu, Hawaii. More than 800 graves are marked as “Unknown” from the Korean War and await exhumation for advanced DNA testing.

By Gage Skidmore from Surprise, AZ, United States of America – National Memorial Cemetery of the Pacific, CC BY-SA 2.0, https://commons.wikimedia.org/w/index.php?curid=115138509

While there is no burial, missing service members are honored in the Honolulu Memorial within the cemetery. 

The names of the missing are etched on the walls of the Courts of the Missing.

Bobby’s name was also engraved on the Wall of Remembrance at the National Korean War Veterans Memorial in Washington DC when they included the names of the missing in 2022.  

Here’s a closeup.

Because Bobby was held above the DMZ, in North Korea proper, in a deserted mining camp called the Pukchin Camp, nicknamed Death Valley, and because the North Koreans were uncooperative, Bobby’s remains were classified as “nonrecoverable” in January 1956.

Hope Rekindled

Unrecoverable in 1956 based on political circumstances and lack of information about which soldiers had been captured, where they were held, when they died, and where burials for that facility occurred, doesn’t necessarily mean unrecoverable forever.

Today, Bobby’s status has been updated to “deferred” which isn’t quite as final and hopeless as “nonrecoverable.”

In 1956, they had no way of knowing about DNA and technology that would become available decades in the future.

Unfortunately, the political environment has remained essentially unchanged now for 70 years, but 70 years isn’t forever.

Yes, I know that identifying Bobby’s remains and bringing him home are both extremely unlikely, but a very low probability is not zero.

As genetic genealogists, we understand that with the passage of generations, the amount of shared autosomal DNA decreases with each generational recombination, so it was important for me to work with AFDIL to preserve my DNA in the hope of one day identifying Bobby – even after I’m gone from this mortal realm.

I might not be able to stand in Arlington, honoring Bobby as he is buried, but maybe my daughter will. Hope springs eternal!

DNA Analysis

The military began collecting DNA samples using bloodstain cards in 1992. For soldiers who served before that and whose remains needed to be identified, various types of forensic analysis were performed.

In the 1990s, when DNA first began to be used for service member identification, DNA matching was performed using mitochondrial DNA because there are hundreds of copies of mitochondria in the cytoplasm of each cell, which means mitochondrial DNA is easier to recover in degraded remains.

This also meant that a sample was needed from the soldier’s mother, sibling, or a relative in the soldier’s direct matrilineal line, not interrupted by a male. Women contribute their mitochondrial DNA to children of both sexes, not intermixed with any DNA from the father, but males do not pass it on to their children.

Around 2010, Y-DNA, passed from father to son, began to be used by AFDIL as well.

At that time, the remains were not processed to extract DNA for autosomal matching, as ancient or forensic DNA extraction technology did not yet exist – and has only been refined for widespread utilization in the past few years. Initially, autosomal matches for repatriation were only used to match immediate family members, so DNA testing was unavailable to cousins of soldiers.

Men who died in WWI, WWII, Korea, and Vietnam may not have immediate family members left – and that number dwindles daily.

  • Bobby had no children.
  • Bobby’s mother, Lucille Latta, was born in 1906 and died in 1952. She had only one sibling, a brother who died in 1966, and their mother was adopted, so there was no source to obtain Bobby’s mitochondrial DNA for matching.
  • Bobby’s only sibling, a brother who had no sons, died in 1986, and their father, Joseph Estes, died in 1994, eliminating the possibility of Y-DNA matching.

This means that there were no immediate or appropriately related family members available for either mitochondrial or Y-DNA testing – effectively slamming the door on the possibility of identification.

The DNA results of soldiers’ remains, and their family members, are held separately from any commercial or law-enforcement databases, so without an appropriately descended family member’s DNA test submitted for this specific purpose, there is no opportunity to identify the soldier.

Until recently, more distant family members were precluded from participating.

The AFDIL Team

In 2023 and 2024, I was privileged to work with the AFDIL team on the Washington Family Project. This was a proof-of-concept project, of sorts. AFDIL undertook this project in the process of refining their methodologies for working with badly degraded remains. The Washington Project was perfect because we knew who was supposed to be buried in each location. The team authored an exciting paper detailing the results.

It gives me cold chills to realize that I was a small part of the effort to open the door for more distant family members to submit autosomal results to identify their missing service members. When we started working together, they had no idea that I’m a Gold Star family member, representing Bobby, and I had no idea the doors this project would open.

Today, those efforts have borne fruit. AFDIL has expanded its family participation policies and guidelines.

Needless to say, I’m thrilled.

Swabbing for Bobby

I requested my swab kit as soon as possible.

I was so excited the day the package arrived.

In addition to swabs, the package included a letter plus several pages of information and instructions.

For notification, be sure that someone living and reliable is listed as the primary contact for your soldier. We discovered that no one was listed for Bobby, but now I’m his official contact and I’m also his closest living next-of-kin.

Oh good, now we’re getting to the DNA swabbing part! Not that I’m anxious or anything!

I had to sit down and really study this chart, which was difficult given my level of excitement. I needed to make sure I really qualified. I mean, I knew I was supposed to – but this was the hard line do-not-pass-go paper right here. A tiny part of me was terrified that something had gone wrong and I wouldn’t be accepted.

The missing soldier is the blue center. I labeled “Me” four images to the right.

AFDIL invested a lot of time in creating this chart that includes autosomal candidates in yellow, mitochondrial candidates with red borders, and Y-DNA candidates with thick dark blue borders.

They had put an oval around “me” on the chart based on their understanding of our relationship from previously submitted documentation. In the paperwork, they asked me to confirm the relationship again.

Next came the swab kit and the labels.

Now I’ve swabbed and labeled everything, following the instructions.

Popping them into the included FedEx envelope.

All I had to do was find a FedEx shipping location and drop the envelope off. I cried as I did the handoff – praying that someday these little vials will provide the key to identifying Bobby.

A week or so later, I received an email stating that my sample had been received and was being processed.

They would be in touch if anything else was needed from me, or, if anything was found.

Now…we wait. Perhaps forever.

But maybe not.

I’ve now preserved the possibility of identifying Bobby’s remains if they are ever returned. And a tiny part of me has my fingers crossed that some of his bones were in that mixed sample, simply waiting for the technology to catch up.

This Memorial Day Weekend

This Memorial Day weekend, in addition to writing this article, I’m working on a wall-hanging to honor Bobby and his ultimate sacrifice.

I’ve been working on this for a while, but it’s so emotionally intense for me that I have to put it away and give myself a break from time to time.

Obviously, I’m working on the layout and I’ve laid these blocks alongside the panel to illustrate. When finished, there will be two rows of stars that function as borders surrounding the center panel.

I’m debating whether I should put a gold star in the center of both sides, or a smaller gold star in the center of a star block, or maybe gold stars of some sort in all four corners. I’m also considering having Bobby’s name, along with his birth and death dates, embroidered near the boots.

After my death and my daughter’s, I’ve left instructions for this quilt to be donated to the Indiana Soldiers’ and Sailors’ Monument, if they want it, where the brick honoring Bobby’s service was laid in the summer of 2021.

You can read more about Bobby in these articles:

Honoring Bobby and Other Unrecovered Soldiers

For years, it has been my dream to attend Bobby’s military burial at Arlington National Cemetery. He has earned that, and it seems that’s the least, the very least, we could do for him. Of course, part of warfare is psychological, not just physical, and refusing to return the remains of those killed is part of that. Even worse is knowing how he was tortured and died.

My heart still bleeds for him and his mother.

We don’t know if Bobby’s remains will ever be “discovered” and brought home. I’d say it’s extremely unlikely.

We don’t know if, by some miracle, Bobby’s remains are among those unidentified mixed samples already buried in Hawaii. That too is unlikely because Bobby was held in a remote location and his remains, wherever they actually lie, are not easily accessible.

As each generation dies, and as Bobby’s bones age, the chance of obtaining a quality DNA match decreases.

While I can’t do anything about the passage of time, nor about Bobby’s bones deteriorating, I can make sure my own DNA is preserved in AFDIL’s Family Reference Database, maintained by the Family Reference Sample Laboratory, a division of the Armed Forces Medical Examiner System’s DNA Identification Laboratory (AFMES-AFDIL). You can read more here and here.

You can search for a POW/MIA service member, here.

If you qualify to submit a sample for a deceased service member whose remains have yet to be identified, you can’t order a DNA sample kit directly like we do from testing companies. You need to request a DNA sample kit after providing information about how you and the soldier are related. You’ll be assigned a case number and a case worker.

Click on this link for more information, including websites, or call the appropriate number below to determine if you qualify and to request a DNA kit.

  • United States Army: (800) 892-2490
  • United States Marine Corps: (800) 847-1597
  • United States Navy: (800) 443-9298
  • United States Air Force: (800) 531-5501
  • Department of State: (202) 485-6106

This Memorial Day, please remember the sacrifices of our fallen heroes, those veterans who never came home, and their families who never stopped waiting.

Ancient Connections: Where Archaeology Meets Your Ancestors

Ancient Connections, a report found on FamilyTreeDNA’s Discover platform for both Y-DNA and mitochondrial DNA (mtDNA), can be used in multiple ways to enhance your genealogy and unlock secrets.

It’s exciting to examine ancient burials linked to our ancestors and understand how we connect to them. Ancient Connections offer a wealth of information, providing clues that can help unravel long-standing mysteries.

Today, there are more than 12,960 Y-DNA Ancient Connections in Discover, along with more than 25,310 mitochondrial Ancient Connections, and that number increases weekly.

Why the disparity, you ask? Remember, everyone has mitochondrial DNA, but only males have Y-DNA.

In addition to matches, your DNA results hold something even more powerful – evidence of where your ancestors and their cousins lived in the distant past, when they lived, and the cultural context surrounding them. These essential insights are unavailable through any other means. Ancient Connections help us answer the age-old question, “Where did I come from?”

Could These People Be My Ancestors?

I’ll show you how to answer another question, too. Which of these Ancient Connections could potentially be your ancestors, and which ones are your “haplo-cousins”?

Regardless, they all help us understand our ancestors’ past, and that of their descendants.

Discover is for Everyone

FamilyTreeDNA provides a free version of Discover that everyone can use. There’s also an enriched version with additional information for their customers who have purchased Y-DNA and mitochondrial DNA tests.

Discover has something to offer for everyone.

Mitochondrial DNA is passed from mothers to all of their children of both sexes – unmixed with the DNA of the father.

Everyone has their mother’s mitochondrial DNA, which is passed intact, except for an occasional mutation, directly down through generations of mothers. It’s not admixed like autosomal DNA, so we don’t lose some portion in each generation. This is exactly why we can track mitochondrial DNA infinitely far back in time and why it’s so crucial for understanding the origins of your mother’s specific line.

Y-DNA is passed from fathers only to their sons, which is what makes males male. Like mitochondrial DNA, Y-DNA is not admixed with any DNA from the mother, so we get a laser line-of-sight view of the direct patrilineal line back in time. The Y-DNA direct paternal line is the male’s surname line in cultures where males carry their father’s surname.

If you’ve tested at or upgraded to either the Big Y-700 level or the mtFull, full mitochondrial sequence test, you will receive the most granular haplogroup possible, meaning the closest in time and most informative. You’ll also match with other testers who have taken the less-refined lower-level tests.

The most informative and precise results occur when both people have taken the premium tests. As more people test and science advances, you may receive a new haplogroup from time to time when you and another tester share a rare mutation – so these tests are evergreen.

Both Y-DNA and mitochondrial DNA testers at any level have access to Discover on their dashboard for those products, although the results of lower-level tests provide less information.

The Free Version of Discover Compared to the Premium Version for Testers

Here’s a comparison of lower-level Y-DNA tests and the Big Y-700.

Click any image to enlarge

Y-DNA testers who have only taken the 12-111 STR panel tests receive a predicted haplogroup, and when clicking through to Discover, receive up to 10 Ancient Connections.

For example, If your Y-DNA haplogroup is predicted as R-M269, the most common male lineage in Europe that arose some 6450 years ago, your Ancient Connections begin with the closest genetic match to R-M269. Viewing Ancient Connections that are 6500 years ago will certainly be interesting, so please do look, but probably not terribly useful for genealogy.

However, if that same person were to upgrade to the Big Y-700, they would receive a much more recent haplogroup, and along with it, up to 30 Ancient Connections within their major haplogroup lineage, R in this case, plus the oldest sample in the database. For some haplogroups, there may not yet be 30 Ancient Connections, although new ancient samples are added weekly for both Y-DNA and mitochondrial DNA.

All Ancient Connections begin with the matches who are genetically closest to the haplogroup requested.

The same scenario holds true for mitochondrial DNA testers who previously tested at the HVR1/HVR2 level, but not at the full sequence level, which is the only test available today.

This article focuses on testers at the higher levels, meaning the Big Y-700 and the mtFull tests, and how to utilize their 30 closest Ancient Connections. We’ll walk through step-by-step examples using both.

However, before we begin evaluating our Ancient Connections, we need to cover two fundamental concepts.

BCE, CE and Converting to “Years Ago”

It’s helpful to understand date structures and how they are used.

It’s easy to get confused when seeing the dates of CE, current era, and BCE, before current era, which means we misinterpret the information.

For example, the year 100 CE is the year 100 that occurred roughly 1900 years ago. We round 2026 to 2000 for these types of calculations. The year 100 BCE, before current era, occurred approximately 2100 years ago. I often prefer to work in “years ago”, because it equalizes the numbers, meaning you’re less likely to get confused about how long ago someone lived or something happened.

To do the calculations from BCE dates to “years ago,” add 2000, so 2250 BCE equals 4250 years ago.

For CE dates, subtract from 2000. The date 500 CE occurred 1500 years ago.

This can be especially confusing when you’re dealing with the same number on either side of the current era, which began in the year 1. There is no year zero. For example, we need to be vigilant not to confuse 500 BCE, which was 2500 years ago, and 500 CE, which was 1500 years ago.

Now, on to our second concept.

Haplogroup Age and Burial Age Are Not the Same

When viewing Ancient Connections, the genetic age of the haplogroup, meaning when it was formed, and age of the burial are two different things.

Haplogroup R-ZP18 is about 4250 years old, and this Late Iron Age, pre-Roman burial which is also R-ZP18, occurred about between 2337 and 2043 years ago.

Haplogroup ages and the date they emerged, which show on the Timeline, sometimes mature and are refined with additional testers and branching.

Burials are dated using various techniques, and sometimes the ages provided in the academic papers are earlier than the genetic age of the haplogroup, shown on the Timeline at the bottom of the Connections page.

Discover makes no attempt to “fix” this situation, because it’s unclear which age should be changed. It’s not unusual to be unable to fully analyze ancient remains. For example, let’s say a sample is determined to have the SNP for R-ZP18, but simultaneously lacks downstream SNPs and some upstream SNPs, and the burial was dated from surrounding soil or artifacts. In that case, it would be impossible to know what is precisely “accurate”, but the sample is accurate enough to be included in Ancient Connections. This is also why some samples aren’t included in Globetrekker™ calculations. Some low-quality samples are excluded entirely.

Every ancient sample is individually analyzed by R&D team members before being included in the phylogenetic tree and Ancient Connections. Sometimes, the scientists at FamilyTreeDNA can assign a more specific haplogroup than was available to the paper authors at the time of publication because the tree has since branched.

As you receive new Ancient Connections, your older ones, except your final or oldest connection, will roll off of your list.

That’s one reason I devised a process for analyzing and recording my Ancient Connections, and for determining which ones might be actual ancestors – or at least aren’t precluded from it.

First Peek at Ancient Connections

Sign in to your FamilyTreeDNA account and click on the Discover link on the dashboard for the type of test you wish to view.

In the Y-DNA example, I’m using my male Estes cousins. As a female, I can’t test for the Estes Y chromosome, so I recruited others to represent my line. You can see the results in the Estes DNA project.

After signing in, click on Discover, then on Ancient Connections.

Y-DNA Ancient Connections 

It’s a bonanza!

Your Ancient Connections are displayed at the top of the page, ordered from genetically closest to most distant. These are archaeological samples whose data has been extracted from academic papers and analyzed before being include in Discover.

You’ll see a description of the first sample, or any sample you click on. The Timeline for that sample, along with your haplogroup and your common ancestor’s haplogroup, is displayed at the bottom of the page.

The first, meaning closest, Ancient Connection is highlighted, so let’s take a look.

  • “You” are shown in the dark purple frame (with purple arrows) at right, with your haplogroup, in this case R-ZS3700, which is placed on the Timeline at the bottom of the page in the appropriate location.
  • The Ancient Connection named “North Berwick 16499”, whose name was taken from the academic paper in which it was found, is shown in a red frame and placed on the timeline based on information provided in the paper.

“North Berwick” has been assigned to haplogroup R-ZP18, either in the paper, or by the FamilyTreeDNA R&D team if a more refined haplogroup can be determined, and is this tester’s closest Ancient Connection based on its position on the list.

Note that you may have other Ancient Connections who are genetically equivalent in age, meaning they too would be R-ZP18. In our case, only one sample is assigned to that haplogroup.

  • Your Shared Ancestor, in the green frame, is the first man who carried R-ZP18, which emerged about 2250 BCE, or 4250 years ago.

Notice that I said, “the first man.” That man’s sons, grandsons and so forth were also haplogroup R-ZP18. Some went on to develop new downstream haplogroups, but apparently, North Berwick, by the time he lived, had not. Either that, or a downstream haplogroup cannot yet be determined due to a lack of other testers in that lineage.

Men with downstream SNPs (mutations), meaning downstream haplogroups, also descended from R-ZP18. Those SNP mutations become downstream haplogroups when two or more men who carry the same SNP mutation match each other. For example, our Estes ancestor who carries haplogroup R-ZS3700 descends from R-ZP18 through a distinct series of downstream SNPs (mutations). While we carry R-ZP18 in our lineage, it’s not our most refined haplogroup.

However, for North Berwick, haplogroup R-ZP18 is his most refined haplogroup.

Because of this, we know for sure that North Berwick and the Estes men both descend from the original R-ZP18 man who lived about 4250 years ago, but we can’t tell when they shared a common ancestor between 4250 years ago and 3750 years ago when the next downstream haplogroup R-BY342, was formed in the Estes lineage.

Because North Berwick does not belong to a different downstream haplogroup, it’s genetically possible that the Estes men could descend from him during that 500-year timeframe. There’s nothing to exclude that possibility based on his haplogroup alone, but looking at when North Berwick lived is another matter.

North Berwrock lived between 2337 and 2043 years ago, which is 1400 years LATER than when the first downstream haplogroup, R-BY342 was formed, about 3750 year ago, in the Estes lineage. This precludes North Berwick from being our direct ancestor. Instead, he’s our “haplocousin.” We share a common upstream ancestor.

What we we absolutely CAN confirm, though, is that between 500 and 1300 years earlier than North Berwick lived, between when haplogroups R-BY342 and R-ZP18 were formed, both North Berwick and our Estes ancestor descended from the same man.

This kind of information is like waving a red flag in a genealogist’s face. We immediately need to know more.

This is just the beginning, and we have so many questions!

Revealing More Information

Did our common ancestor live in or near North Berwick, or someplace else? What do we know about the history of North Berwick?

What can we discern about North Berwick?

  • When did this man live, and where?
  • What do we know about him?
  • Who was he?
  • Did he live close to where my earliest known ancestor in this line is found?
  • What can I tell about his culture?
  • Were there grave goods that provide at least a peek into his life?

So many questions!

Discover tells us that he lived between 337 and 43 BCE, so between 2337 and 2043 years ago, during the Late Iron Age, and is associated with the Iron Age Britain cultural group.

The Ancient Connections “Reference” provides information about the paper where the North Berwick sample was found. No links are provided because sometimes the paper is behind a paywall, and you can’t access it without paying, and sometimes it’s a preprint and will appear later elsewhere. Sometimes one paper actually uses data from an earlier paper, and it gets complicated.

The first thing I do is Google the paper – Patterson et al. 2022. Google provides two links – one that’s free, and one that isn’t. Many times, the sample data is found in the supplementary material, which may also be behind a paywall, even if the paper isn’t.

I know you’re going to think it’s a pain, but I strongly encourage you to read every paper, though sometimes they can be challenging to understand, so read them when you’re fresh, not tired, and can concentrate. If nothing else, at least read the abstract. There’s so much great information buried in academic papers, including nice maps and discussions of the burial site. You can also learn more sometimes by Googling the burial site itself.

Let me give you an example from this paper’s abstract. I’ve added the brackets [ ] for clarity, from the body of the paper:

Between 1000 and 875 BC[E], EEF [Early European Farmer] ancestry increased in southern Britain [England and Wales] but not northern Britain [Scotland] due to incorporation of migrants who arrived at this time and over previous centuries, and who were genetically most similar to ancient individuals from France. These migrants contributed about half the ancestry of people of England and Wales from the Iron Age, thereby creating a plausible vector for the spread of early Celtic languages into Britain.

How does this information align with our North Berwick man? He lived between 2337 and 2043 years ago, and the EEF ancestry increased in southern Britain between 3000 and 2875 years ago. The authors do add “over previous centuries” which probably accounts for the 500-year gap and gets closer to when R-ZP18 lived. North Berwick is found in Scotland, not England or Wales, so not part of the group of people most closely aligned with the ancient French migrants from this timeframe. Maps in the paper confirm this as well.

Googling the paper and sample name provided additional sourced information. This paper incorporates samples from earlier papers and performed a different type of analysis.

Ironically, I wrote about this in detail in 2022, here, before Discover was introduced, so I had absolutely no idea that North Berwick 16499, discovered on Law Road in North Berwick, was related to my ancestors, and therefore, to me.

In that article, I researched and mapped the samples. North Berwick 16499 is located on the coast, along the harbour, not far from Edinburgh.

The burial was excavated in the cemetery of the original St. Andrew’s Church in North Berwick, originally built in the 1100s, but now in ruins.

This paper’s supplementary material explains that:

Excavation of a substantial square cist at Law Road, North Berwick, uncovered the remains of four inhumations of Late Iron Age date (Richardson et al. 2005). Two adult males 3603 (Skeletons C46 and C51) and a female around 16–18 years of age at death (Skeleton C50) appeared to have been displaced for the burial of an adult female (Skeleton C47), wearing an iron brooch. One of the males (C46) had been buried with a bone-handled iron knife.

What I wouldn’t give to see that iron brooch and bone-handled knife.

C51 is North Berwick 16499, “our” skeleton. A cist grave is a small, stone-lined burial box, and this one was preserved beneath medieval deposits.

That reference gave the even more precise location of Law Road and St. Andrews Street and informs us that the remains are held by National Museums Scotland. Checking their collections confirms that they hold these items, plus the bones. However, there are no photos shown. Contacting them for images might yield results.

What the paper did not say is that little was known prior to these excavations about early North Berwick.

By Stefan Schäfer, Lich – Own work, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=19450589

North Berwick was known to exist as a ferry landing from the 7th century, but an archaeological survey of Berwick Law, a hill that overlooks the town, revealed much earlier information:

The earliest features on North Berwick Law comprise a pair of newly discovered cup-marked rocks and the scanty remains of a prehistoric hilltop fort discovered by RCAHMS (1957, xv), whose outworks appear to be more limited than suggested by previous authorities (Feachem 1963, 119; OS 1975). The lower SW flank of the Law is dotted with the remains of a prehistoric settlement comprising at least 12 hut circles or house platforms and fragments of an associated field system of small cairns and banks.

Unfortunately, the perimeters of Berwick Law have been settled and farmed since, and the hilltop has served recently in the same capacity as it probably served initially – as a lookout across the firth. The residents would have been watching from this highest point for invaders arriving by sea.

It’s about half a mile from the foot of the hill to the burial cist.

The survey also mentioned that they found “stray bronze age finds” that had likely been disrupted by subsequent settlement. The bronze age in Northern Scotland began about 4200 years ago, about the time that R-ZP18 lived, until about 2800 years ago. Whoever North Berwick 16499 was, the man who was buried here some 2400 years ago, he was probably associated with this hilltop fort, perhaps farming at the base, probably living in one of those huts or nearby. His body wouldn’t have been taken far for burial.

We are left to wonder how long his family had lived here, and how they had arrived. Was his cist burial a sign of status? Was he sent to commend the fort, or had his family settled here centuries earlier? Did our ancestor descend from this location, too?

After our analysis, we know that our ancestor did not descend from North Berwick 16499 himself, but North Berwick definitely descended from our ancestor.

If you’re thinking this is a rabbit hole, it definitely is – but what a rabbit hole! There is so much to be gleaned from these Connections.

The Evaluation Process

I needed a process to keep track of these Ancient Connections, my findings, and how they relate to my Estes ancestors. Who begat, or might have begat whom, and where?

I created a spreadsheet as I read and analyzed each Ancient Connection relative to my ancestral line. I include what I know about it, and what I THINK I know about it. Those can be two vastly different things. I follow this same process for every ancestral line where I can find a representative Y-DNA or mitochondrial DNA tester.

For example, there’s a persistent rumor that the Estes family line descends from the d’Este family of Italy. That rumor was spun up long before we had genetic proof that our line was found in Kent, England, in records dating back to about 1495. Fortunately, church records, for the most part, and some civil records still exist.

The first known record is the will of our Nycholas Ewstas written on January 1, 1533/1534 in Deal, Kent, England. We confirmed that this is our Estes line by testing the Y-DNA of his descendant who still lives a few miles up the road, compared with the descendants of Abraham Estes (1647-1720), the man who immigrated to Virginia in 1673. We believed that Abraham Estes, who married in 1672, then immigrated 14 months later, was one and the same person.

Based on the details of the d’Este rumor, the Estes line was supposed to descend from one Francesco d’Este (Esteuse), an illegitimate royal son, exiled to France about 1471 after the death of his father, Azzo VI of Este, by a jealous half-brother, complete with a royal allowance. There are mentions of him in the Dutch and French courts, then nothing. Silence.

Apparently, various Estes lines in England liked the idea that he crossed the English Channel and settled in the fishing village of Deal, with his descendants carrying the surname Estes, a derivative of d’Este. King James apparently believed there was a connection and made that suggestion himself in one instance, although it’s unclear if that Estes man was from our Estes line.

It’s difficult to prove a negative, so we need to rely on the evidence we do have, much of which has been discovered and accumulated in more recent years, since the genesis of that rumor which was widely believed.

To begin with, it makes no sense that between 1471 and 1495, the family suddenly went from being a wealthy exiled royal circulating at court in France and the Netherlands, to peasant fishermen on the coast across the channel.

There is a legitimate royal lineage that does descend from the d’Este family in Italy, but until and unless someone who is a descendant of the direct male line of the House of Hanover, which reaches back to the Azzo line of Ferrara, takes the Y-DNA test, there’s no proof positive. Either their Y-DNA would match the Estes line, or not. I’d wager that it does not, but I’d love to find out for sure.

I’m hopeful that some nugget in Ancient Connections might add weight to either side of the argument.

Creating a Spreadsheet

First, I’ll show you the Ancient Connections spreadsheet built for the Estes line, then I’ll demonstrate how to build it.

Here’s the finished spreadsheet. Every haplogroup’s spreadsheet will be different.

I placed the four confirmed Estes haplogroups at the bottom because that’s the base from which the Ancient Connections are built, beginning with the closest Connection first.

“My” haplogroup, meaning for my ancestor’s Estes male line, is R-ZS3700, but there’s one additional downstream haplogroup, which I’ve included for completeness.

Let me alert you now that you WILL receive new Ancient Connections, which means that for every new Connection you receive, one more distant Connection rolls off the end because it’s outside of your 30 genetically closest Connections threshold. I’ve received new Ancient Connections in the past three months, between the time I originally began gathering this information and when I published this article.

The underlying message, in addition to maintaining your spreadsheet, is to set a calendar alert to check your Ancient Connections regularly. One rolled off that was more distant genetically, but was located only 10 miles away from where my Estes ancestors originated in Deal, England.

We’ll build the spreadsheet so you can easily expand it as new Connections are added.

Also, note that you may receive multiple matches from the same archaeological excavation site, which, of course, is highly suggestive of a family. If the multiple burials are in the same exact location and from roughly the same timeframe, I only record them on the spreadsheet once to reduce clutter, but I add a note that there are multiples.

The Build Process

Referencing the image above, haplogroups in the column directly above the originating haplogroup, R-BY154784, then R-ZS3700, colored apricot, are parent haplogroups – meaning that these haplogroups descend from the haplogroups above them. Look at R-ZP18, North Berwick, above R-BY482 as an example. This means two things.

  1. It’s possible that my ancestors could descend from these individuals in this column. However, all things considered, it’s more likely that they are a “cousin” of my ancestor who lived at that time and carried that haplogroup before a new mutation happened and branched into a new downstream haplogroup. That’s exactly what we proved about North Berwick based on when he lived and our downstream haplogroup formation date.
  2. Every man who shares that haplogroup, R-ZP18, absolutely DOES descend from the original man who carried that haplogroup-defining mutation that arose about 2250 BCE or about 4250 years ago. That one man in whom R-ZP18 occurred is noted above North Berwick, in red, indicating that both North Berwick and the Estes men descend from the man whose name is now R-ZP18.

On my spreadsheet, I’ve colored the cells of the haplogroups that I do descend from, and the burials I might descend from, apricot. The common haplogroups that burials and contemporary testers downstream descend from are in bold red text (R-ZP18 and R-DF49).

Burials who carry a different branching haplogroup, meaning they aren’t R-ZP18, but branch FROM from R-ZP18, are shown with their branches in blue. My ancestors cannot descend from blue haplogroups because we are on different branches of R-ZP18. Our branch is apricot.

Let’s add the next Ancient Connection.

Here’s the Time Tree Timeline of the second Ancient Connection, named Mount Pleasant 746, found at All Saints, Cambridgeshire, England, who lived between 940 and 1365 CE.

This shows two things.

  • My R-ZS3700 ancestor cannot descend from the Mount Pleasant burial, since R-ZS3700 doesn’t carry the mutation for R-BY173525, found in the Mount Pleasant burial.
  • However, since R-BY173525 branched from R-ZP18, we DO SHARE a common ancestor who lived about 4250 years ago. This means that between 4250 years ago and 940-1385 CE, the man found in Cambridgeshire, and my ancestor found in Kent around 1495 CE, both migrated in different directions from where their common ancestor, R-ZP18, lived, wherever that was.

The next closest Ancient Connection is Vor Frue Kirkegård 336, buried in the yard of a former monastic church in Vor Frue Kirkegård, Aalborg, Denmark, which dates from the 12th century. This man lived between 1536 and 1806 CE.

Again, my Estes ancestor who carries R-ZS3700 can’t descend directly from this man. Three things preclude Vor Frue Kirkegård 336 from being our ancestor:

  • The fact that Vor Frue Kirkegard 336 carries R-BY203953, but the Estes line does not.
  • Vor Frue Kirkegard 336 does not carry, R-BY342, the next downstream SNP for the Estes line.
  • Vor Frue Kirkegard 336 lived between 1536 and 1806 CE, which is contemporary with or after the earliest documented Estes ancestor was living in Kent, England circa 1495.

In this case, the locations are not in close proximity, over 500 miles apart by a combination of land and water. This distance would be less compelling as an elimination factor if the men were further separated by time.

In this case, any one of the first three pieces of evidence, alone, would preclude Vor Frue Kirkegard from being our ancestor.

Once again, R-ZS3700 shares the common ancestor of R-ZP18 with Vor Frue Kirkegård 336, along with Mount Pleasant 746 and North Berwick 16499. All of those men shared one common ancestor 4250 years ago.

Now, we have the bottom portion of our tree built out – meaning everyone who either carries haplogroup R-ZP18 as their primary haplogroup, or descends from that man.

Moving up the tree in the apricot column, you’ll notice that I’ve left spaces that leave room for the branching haplogroups in blue on the right. You won’t know how many spaces you need or the configuration until you start building the tree in your spreadsheet.

I listed both “5 haplogroups” and “3 haplogroups,” in the apricot column. You can spell those haplogroups out if you wish, but for my Ancient Connections, they didn’t matter. They may matter in the future, though, if you have an Ancient Connection who descends from or branches from one of them.

If you need an easy way to determine your ancestral lineage, the Ancestral Path is just the thing for you adn will help build your spreadsheet.

Your Ancestral Path

It’s easy to view which haplogroups are in your direct ancestral line. Just click on the “Ancestral Path” link in Discover’s sidebar.

Your haplogroup is shown at the top, with the parent haplogroups in order beneath. I’ve boxed the “5 haplogroups” between R-BY482 and R-ZP18 here, and then the “3 haplogroups” between R-ZP18 and R-DF49, which is where we find the next closest Ancient Connections.

One bonus of the Ancestral Path display is that you can see how many Ancient Connections are in the database for each haplogroup, at far right.

As I continue to build out my spreadsheet, the next four burials are all R-DF49, a haplogroup that was formed about 4400 years ago. Three of those burials are in England, and the fourth is in the Orkney Islands. They are all apricot, meaning:

  • They don’t carry any downstream haplogroups
  • They all descend from R-DF49
  • Based on haplogroups alone, nothing precludes the Estes line from descending from any of those men

Evaluating each Ancient Connection in the same way we did for North Berwick, when they lived, as compared to our Estes men, and where, may eliminate some of these burials as possible direct ancestors.

The balance of the Ancient Connections descend from R-DF49 through different branches and are colored blue, removing them as possible ancestors of R-ZS3700.

Regardless, we all share an ancestor, R-DF49, about 4400 years ago, just shortly before R-ZP18 lived some 4250 years ago. It would make sense that R-DF49 and R-ZP18 lived in relatively close proximity, given that they only lived about 200 years apart.

What else can we learn about these Ancient Connections?

Migration Map

To view all of your Ancient Connections on a map, just click on “Migration Map” in Discover’s sidebar.

The haplogroup whose path you are viewing, in this case, R-DF13, is the red dot on the bar at the top and is shown on the map with a red circle, but is mostly obscured here by the blue and red circles with numbers in the British Isles.

That haplogroup’s migration map, and your Ancient Connections, are displayed together. Individual burials not in close proximity to others are shown with individual trowels, and multiple burials are shown with blue and red circles, with the number indicating how many burials are found at that location.

Expanding the map shows more detail. I placed a red star to indicate the Estes lineage in Deal, at the bottom right.

Many of the blue and red circles have expanded, too.

By clicking on the blue circle, you can see which samples are found there. In this case, these 7 matching samples were all found in the same archaeological dig.

By clicking on any sample, you’ll see additional information.

One of my original questions was whether or not there was any indication whatsoever, even a smidgen of possibility that the d’Este rumor might be true. Some Estes researchers are not convinced by other arguments.

Given that our closest Ancient Connection lived about 2000 years ago in the British Isles, as do most, but not all, of the other Ancient Connections, it’s exceptionally unlikely that the progenitor of the Estes lineage was living in Italy in the 1400s, just a generation before our Estes ancestors are found in the records in Deal, and some 2000 years after the parent haplogroups of R-ZS3700 were already well-established in the British Isles.

There’s another place to check for additional information.

Notable Connections

Sometimes Notable Connections includes people who are either “ancient” themselves, and whose haplogroups have been identified through their descendants, or are from burials, or a combination of both. The difference is that their identity is not entirely a mystery.

When evaluating Notable Connections for genealogy, focus on:

  • Their haplogroup
  • Your shared haplogroup
  • When and where they lived
  • Any precluding factors like we found when analyzing North Berwick

Notable Connections are all interesting, but only a few may be relevant to your genealogy or your ancestors’ journey to where you first found them.

Speaking of their journey, Globetrekker™ shows you the most likely path of your ancestor’s haplogroup over time.

Globetrekker™

Globetrekker™ is currently only available for Y-DNA, and only for those who have taken the Big Y test.

Clicking on Globetrekker™ through my cousin’s account shows the path of his haplogroup, through Europe, in this case, into England and, if I enable them, includes relevant Ancient Connections. One Ancient Connection, Mount Pleasant 746, at Cambridgeshire, is found on the estimated genetic haplogroup path.

We’ve already determined that the Estes line cannot descend from Mount Pleasant 746, but the locations of the descendants of our common ancestor, R-ZP18 can still provide substantial clues about where our common ancestor might have lived, and his culture.

I’ve also enabled Globetrekker™’s “Sibling Lines” which indicate haplogroup siblings with the thinner lines. These display options are easy to toggle on and off.

Note that this is an estimated genetic path. In other words, it’s not exact. Especially, paths of the newer haplogroups can and will change over time as more testers test, and earliest known ancestors (EKAs) are added. I wrote about how to add EKAs in the article, “Earliest Known Ancestors” at FamilyTreeDNA in 3 Easy Steps. Please add yours, along with their location.

Sometimes the most refined haplogroup did not emerge in England, R-ZS3700 in this case, but in America. However, since the descendants have noted their EKA correctly as originating in England, that’s where the most refined haplogroup is also shown.

Furthermore, other than for Native Americans who are indigenous to the Americas, Globetrekker™ and the Migration Map both stop at the originating land mass for both Y-DNA and mitochondrial DNA.

You can read more about Globetrekker™, here.

What About the d’Este Family Story?

Now, about that d’Este family story.

Globetrekker™ utilizes the “least cost” migration methodology, which means the easiest, least risky, route of passage from place to place for our ancestors. The Strait of Dover is the closest link to the European mainland, and was shallower at that time as well.

There’s absolutely no genetic evidence that points to Italy or anyplace south for the Estes ancestral line. In fact, haplogroup R-S552 emerged about 4650 years ago, and appeared about the time that this lineage crossed from continental Europe into what is today England. There’s no evidence that this line back-migrated to the continent, to then remigrate back to the British Isles after 1471.

Ancient Connections show us that there’s evidence of the Estes ancestral haplogroups in many locations across the British Isles, long before Frencesco d’Este was being exiled from Italy. Multiple Estes family members appear in the earliest records in the Deal area, so it’s certain that they were well established and probably fishing on those same shores hundreds, if not thousands, of years earlier, based on Ancient Connections these various migration maps.

These provide one more very large nail in the coffin of that much-loved but extremely unlikely family story.

The final piece of evidence would be if a proven male descendant of the d’Este line tested and did or didn’t match. I’m not holding my breath.

Mitochondrial DNA

The methodology for building your Ancient Connections spreadsheet is exactly the same for mitochondrial DNA, with one exception.

You immediately know that you cannot descend from any male burial, because men don’t pass their mitochondrial DNA on to their children of either sex. You could, however, potentially be descended from his mother, or sister, or cousin, etc. Otherwise, the guidelines are the same.

Sometimes, Ancient Connections can resolve long-standing conflicts.

The Conflict Surrounding Radegonde Lambert

For a very long time, it was believed that Radegonde Lambert, an early Acadian woman born around 1621, was Native American because there were no known people, other than her, with that surname in Acadia. Based on the birth years of her children, she married Jean Blanchard, a French man, around 1642.

It doesn’t help any that French soldiers arrived in 1632, family settlement began about 1636, but there are virtually no records until the 1671 census, nearly 40 years later. Lots of people perished during that 40 year window.

Radegonde could have married before her arrival in Acadia, and Lambert may not be spelled accurately. We are fortunate that French women are referenced by their birth surnames, not their married surnames, so she is listed as Radegonde Lambert, the wife of Jean Blanchard on the 1671, 1678 and 1686 censuses.

Based on the conflict swirling around her presumed Native American ancestry, plus early mitochondrial DNA HVR1/HVR2 results that pointed to haplogroup “X”, which has both Native American and European branches, Radegonde began to be reported as “DNA confirmed Native”. However, that was incorrect, and she was NOT DNA confirmed as Native. Haplogroup X2a and subclades are Native American, while other haplogroup X AND X2 subclades are European, as can be viewed in the Acadian AmerIndian DNA Project.

By the time full mitochondrial sequence testing became available, that incorrect “confirmation” was firmly entrenched in family trees and among researchers, leading me to pen the article, Haplogroup X2b4 is European, Not Native American.

While ho-hum with a yawn today, it was radical at the time and greeted with quite the kerfluffle. After all, Radegonde was proven Native and HOW DARE ME! 😊

Prior to Mitotree, Radegonde’s haplogroup was X2b4, but now it’s been extended to X2b4t2, which arose about the year 500, or around 1500 years ago.

X2b4 and subclades are quite rare, with only 353 descendants today, including subclades.

X2b4t2 only has 65 members.

Clicking on the “Other Countries” link takes you to the Country Frequency report.

Click on “Table View.”

Note that the 36 “Other Countries” includes people who have listed “Unknown Origin,” who are counted individually. People listing United States often mean they are brick walled here. Some people interpret this as Native American, but there is a separate United States Native American category. Not everyone selects the correct category.

These locations are user-reported in the Earliest Known Ancestor (EKA) information, which is critical for Discover reports. I wrote about how to complete that information in 3 easy steps, here. Please add yours, including location!

One person has reported that Radegonde Lambert is “United States Native American.” She’s not Native, and she never lived in the United States either. During her lifetime, Acadians lived in Nova Scotia, where three censuses accurately reflect her residence.  Perhaps that incorrect information was entered by someone years ago, and never changed. Most people don’t think to update their EKA information.

Unfortunately, when misinformation is provided, or not corrected after we learn more, new testers view that as nuggets of evidence, and the misinformation cycle continues.

One of the benefits of Ancient Connections is that they are NOT based on trees, historical records, or genealogy of any sort. Ancient Connections are based on archaeological digs, and the location of the excavation is not subject to question.

So, let’s take a quick look at Radegonde Lambert’s Ancient Connections and see what we find.

A Quick Sneak Preview

Because I’m interested primarily in a quick view of locations, I’m skipping right to the Migration Map where all of the Ancient Connections are shown.

Radegonde’s Ancient Connections are scattered all over Europe, but there’s absolutely nothing in the Americas.

Given that Native burial excavations are culturally frowned upon in many locations, we might not see any in the US, but we also wouldn’t see any recent burials in Europe, given that the Native people have been in the Americas for well over 10,000 years.

Generally, even when Ancient Connections are missing in the US, we still find some contemporary testers with proven genealogy who carry that haplogroup, and at least a few ancient burials in Canada, Mexico, Central and South America.

The first seven Ancient Connection matches carry haplogroup X2b4, and the rest are European subgroups of X2b4. There are no closer matches as of today, but that doesn’t mean there won’t be eventually.

X2b4 emerged sometime before 5200 years ago, clearly someplace in Europe, possibly central Europe.

Radegonde’s X2b4 match locations are:

  • Malá Ohrada site in Prague – the individual lived 5800-5400 years ago
  • Hetty Peglers Tump, Gloucestershire, England – lived 5639-5383 years ago
  • Sorsum, Hildesheim, Lower Saxony, Germany – lived 5350-5100 years ago
  • Passage Tomb, Carrowkeel, Cairn K, Sligo, Ireland – lived 5100-4600 years ago
  • Kolín I-7b, Bohemia, Czech Republic – lived 4835-4485 years ago
  • De Tuithoorn, Oostwoud, Netherlands – lived 4579-4421 years ago

It’s unquestionable that X2b4 was found across Europe, not in the Americas, 5000 years ago.

This image is NOT from Radegonde Lambert’s Ancient Connections. I’ve included it to illustrate a Native American branch of haplogroup X2.

The descendants of Native American haplogroup X2a, shown above, match Kennewick Man, who is also X2a, as their closest Ancient Connection. He lived between 9250 and 8390 years ago along the river in present-day Kennewick, Washington. Their second-closest Ancient Connection is with an X2a1 burial found in Windsor, Ontario, who lived between 1223 and 1384 CE.

Neither of these unquestionably Native burials are found in the Ancient Connections of Radegonde Lambert’s descendants.

It’s worth noting here that when evaluating rare haplogroups, their Ancient Connections may reach far back in time. For example, if a Native American haplogroup only has a few Ancient Connections within the Americas, the rest of their Ancient Connections, if any, will be found on another continent. Failing to read the results thoroughly and thoughtfully could lead to an inappropriate and incorrect conclusion.

For example, haplogroup X is found in Eurasia prior to the migrated of people across Beringia, the now-submerged landmass connecting Asia with Alaska, to become the indigenous people of the Americas. Therefore, if there are less than 30 closer X2a Ancient Connections, one would expect to find Ancient Connections reflecting that continental Asian, or even Eurasian, heritage far back in time.

Notable Connections

One final tip for both Y-DNA and mitochondrial DNA is to check Notable Connections and selectively add them to your spreadsheet, if appropriate. Sometimes you’ll find people there that are both Notable and Ancient.

Not that we need more evidence about whether Radegonde Lambert’s matrilineal ancestors were Native or European, but Notable Connections provides us with one more corroborating piece of evidence.

Cangrande della Scala was an Italian nobleman who lived around 1300. He and Radegonde share a haplogroup X2b1″79 ancestor in Europe around 9000 years ago, which was after the Native people had crossed Siberia and Beringia to begin settling Canada and the Americas.

If there was any question left about Radegonde Lambert’s origins, Ancient Connections resolved it, with a backup volley from Notable Connections.

Radegonde Lambert was my ancestor, so I’m going to build her Ancient Connections spreadsheet and savor every discovery, but if I were simply seeking confirmation of or the answer to the question of whether Radegonde Lambert was Native American or European, I need look no further.

Mitochondrial DNA Case Study

In the article, Mitochondrial DNA A-Z: A Step-by-Step Guide to Matches, Mitotree and mtDNA Discover, I wrote in detail about utilizing mitochondrial DNA to break through genealogy brick walls.

My goal was to detremine if Catherine LeJeune, Edmee LeJeune and Jeanne LeJeune dit Briard were sisters or at least matrilineal relatives. Fortunately, we had several testers.

As it turned out, Catherine and Edmee were European sisters, but Jeanne did not share a matrilineal ancestor with Catherine and Edmee. Jeanne was Native American.

Next, we wanted to discover as much information about the LeJeune sisters as possible.

I created an Ancient Connections spreadsheet for the LeJeune sisters and included those results in my analysis, so please take a look. Their Ancient Connections were unexpected and simply astounding.

You literally never know who is waiting for you, nor the message they hold, just waiting to be delivered.

Ancient Connections are clues from your ancestors.

_____________________________________________________________

Share the Love!

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

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Sixteen Unique Trees at FamilyTreeDNA: How and When to Use Each

I love all the various trees at FamilyTreeDNA – and I’m not referring just to traditional genealogy trees with people, names, and dates. I’m talking about phylogenetic or haplogroup trees – the ones you use to understand your Y-DNA and mitochondrial DNA haplogroups, origins – and more. These trees tell you ABOUT your ancestors, those people in the more traditional genealogy tree, and the combination of both is powerful.

This article introduces the various trees available at FamilyTreeDNA, when and where you’ll find them, and what they can do for you.

Haplogroup Trees

Phylogenetic, or haplogroup trees, provide a genetic path from you, or the tester, today, back in time to Y-Line Adam, or Mitochondrial Eve – the first two humans who lived AND have descendants today.

Let’s start by explaining about Y-DNA and mitochondrial DNA (mtDNA), their inheritance path, and what they mean to you.

Y-DNA

Only men have a Y-chromosome, so only biological males can test their Y-DNA.

Y-Line Adam, Y-DNA haplogroup A-PR2921, lived about 232,000 BCE, or 234,000 years ago.

Is it possible that one day someone will test whose results push that date back somewhat? Yes, of course, as we are always learning, and many testers split branches.

Today, all 711,000+ modern descendants who have tested carry the mutation named A-PR2921 as their oldest SNP (single nucleotide polymorphism), or haplogroup-defining mutation in their Y-DNA. That’s because we all descend from that one man.

If you’re a male, Y-DNA testing tells you about your direct paternal line by matching with other men who have also taken a Y-DNA test, and by revealing valuable information from before the adoption of surnames. There’s no other way to reach that far back in time.

If you’re a female, you can recruit males in your family to test.

The Big Y-700 test provides the deepest-reaching and most refined Y-DNA test available, which is essential for both genealogy and tree-building.

Mitochondrial DNA

All people have mitochondrial DNA, inherited from their mother directly through her matrilineal line – meaning her mother, her mother, her mother, and so forth – directly up your tree through all mothers.

Everyone inherits their mitochondrial DNA (mtDNA) from their mother, but only females pass it on. Both males and females in the current generation, meaning you, can (and should) test their mitochondrial DNA.

Mitochondrial Eve, mitochondrial DNA haplogroup L, lived about 141,000 BCE, or about 143,000 years ago. All 315,000 testers descend from this one woman.

Like with Y-Line Adam, one day the results of future testers may push this date further back in time. A full sequence mitochondrial DNA test, mtFull, is necessary to test all 16,569 mitochondrial locations.

Test Types

FamilyTreeDNA has been in business for more than 25 years. Technology has advanced dramatically during that time. While they continue to offer new tests and products, they strive to maintain value for their original testers.

Even though some early testers may have joined their ancestors, matching with their test results is still beneficial to us.

Present-day DNA testers can still derive value by matching the earlier, lower-level, lower-resolution tests. Not as much value as if the original tester had taken a higher-level test, but those tests may not have been available at that time.

Matches, surnames, genealogy, locations, and haplogroups provide us with valuable information. The more people who test, the larger the pool becomes, and the better our chances of discovering something that refines our understanding of our ancestors – and identifies who they are.

Before we look at the trees available, let’s take a look at where haplogroups come from. Different level tests assign different levels of haplogroups, based on how much is tested.

Let’s answer two common questions:

  1. Where can you find your haplogroup, and what does it mean?
  2. How can haplogroups be different for people who descend from the same ancestor?

Where Do Haplogroups Come From?

Since the beginning, FamilyTreeDNA has always provided their customers with haplogroup information. Haplogroups are very genealogically useful today, but initially, 25 years ago, they were only able to provide essentially continental-level origin information for your particular line. That too was useful, and helped to identify and eliminate common lineages – just not as useful as today.

Science and testing have both come a long way. Present-day testers still match with people who only tested at a lower level. You never know what you might find at that level – a match to someone who has not taken the current tests, but is still very relevant because they share your ancestor. In fact, they may be the only tester who does.

For Y-DNA testers, you’ll notice several match categories that reflect different testing levels – along with the number of matches at each level. At one time, you could purchase each one of these tests individually, then later upgrade to higher-level tests. Today, only the 37 and 111 marker tests, and the Big Y-700, which scans the entire gold-standard region of the Y chromosome, are available. Higher level tests include the lower-level tests.

Click any image to enlarge

Different types of tests provide either a predicted or a confirmed haplogroup which shows on your match list.

Without getting all sciency on you – the 12-111 marker tests test targeted STRs, or short tandem repeats, which can’t be used for haplogroup assignment and confirmation. They can and are used to compare to other testers for matching because the number of repeats, or stutters, are inherited on the Y chromosome. The Big Y test scans the Y chromosome for SNPs, single nucleotide polymorphisms, which are stable mutations that define haplogroups. I wrote about this in the article, STRs vs SNPs, Multiple DNA Personalities.

Some haplogroups are much further down the tree, or more current, than others. Your most current haplogroup, only available with the Big Y-700 test, is the best because it brings you the closest to current in time, often placing you within family branches. The Big Y-700 scans about 23 million locations on the Y chromosome, revealing both known and unknown mutations, not just a few markers, making it the most refined and relevant test genealogically.

Each higher-level test includes the lower-level tests. You can see what tests your matches have taken by looking beneath their names on your match list. In this case, these Estes men who match my cousin have taken the Family Finder (or uploaded an autosomal transfer), and taken the mtFull test. One match initially took the Big Y-500 but has since upgraded to the Big Y-700, and the other originally tested at the 111 marker level, and has since upgraded as well.

The Big Y-700 includes all lower-level tests, such as the Big Y-500 (now obsolete), the 111, 67, 37, 25, and 12 marker STR tests. You still match with people who only tested at those levels, plus everyone else who ordered a more refined test.

The haplogroup you receive is more or less refined, based on the test level you take.

Y-DNA Test Type Haplogroup Provided Relevance Upgradable
Y-DNA STR 12-111 marker tests (only 37 and 111 are available today – the rest are obsolete) Predicted based on STRs – very reliable at the level predicted Predicted (not confirmed) haplogroup that was generally formed a couple thousand years ago, or earlier Yes, if enough quality DNA remains. Only 37, 111, and the Big Y-700 tests are available today. Recommend the upgrade to Big Y-700.
Individual SNP test (now obsolete) Confirms a predicted haplogroup or tests a single SNP to confirm a closer haplogroup Relevant at the level tested – either positive or negative result was reported Individual SNP tests have now been replaced by Big Y-700, which covers all individual SNPs that were available to test, plus much more.
Big Y-500 test (now obsolete) Confirmed haplogroup within range of that test’s ability, replaced by much more granular Big Y-700 Big Y-700 is more refined and moves the tester towards more current haplogroups, so more genealogically significant Yes, upgrade to Big Y-700 if enough DNA remains, or tester can re-swab
Big Y-700 – scans the entire gold-standard region of the Y chromosome – approximately 23 million base pairs Top-of-the-line SNP-confirmed test, most granular and refined. Scans for known and previously unknown mutations. Extremely accurate. Generally advances the tester into a genealogical timeframe, and often divides testers into multiple lineages descended from a known common ancestor No more advanced test is available.
Family Finder autosomal test or transfer Confirmed to mid-range level if possible. Not all transfer files have Y-DNA or mtDNA SNPs so you get what you get. Useful in autosomal matching for locating people you may be related to you with that surname. Ask the match if they are willing to take a Y-DNA test, if relevant, or sponsor a testing scholarship for them.

Family Finder haplogroups are relatively new at FamilyTreeDNA. Each chip level that FamilyTreeDNA has used for testing over the years, and the chips that other vendors have used, contain different SNPs (or none at all on the Ancestry test) that can be measured for some level of haplogroup. Other vendors generally don’t quality-control for either Y-DNA or mtDNA SNPs because they don’t use them. This is a “you get what you get” freebie.

That said, most Family Finder haplogroups are closer in time, or “better” than the predicted R-M269, the most common haplogroup in Europe, often reported with STR testing.

Not everyone with a transfer kit receives a haplogroup. Due to quality and reliability issues, you cannot see haplogroups on your autosomal match list for those who only have a haplogroup through an autosomal transfer.

Using our male Estes testers as an example, we find the following haplogroup results at the various testing levels:

Haplogroup Haplogroup Formation Date Ancestor or Haplogroup Formation Location Haplogroup Source
R-M269 4450 BCE (6450 years ago) Between Ukraine and Kazakhstan, north of the Black and Caspian Seas Predicted from 12-111 STR marker tests
R-BY487 700 CE (1300 years ago) UK, Scotland/England Family Finder DNA SNP Confirmed
R-BY482 1550 CE Robert Eastye b 1555 Ringwould, Kent, England Big Y-700
R-BY490 1700 CE Silvester Eastye b 1596 Kent, England Big Y-700
R-ZS3700 1750 CE Moses Estes 1711 VA Big Y-700
R-BY154784 1850 CE Joseph Estes b c 1790 VA or TN Big Y-700

All of these are valid and accurate haplogroups – some are just closer in time and much more useful than others. All of these men have R-M269, because it is a parent haplogroup of all of those downstream haplogroups. The Big-Y tested men beginning with R-BY482 don’t share the haplogroups below them, because they don’t have those mutations that are downstream on the tree. However, the men at the bottom with R-BY154784 have all of the SNPs above them.

Note that all haplogroup formation dates are ranges. I’m showing the midpoint here.

When upgrading, if the original tester is deceased, select the highest-level test available, as there may not be enough DNA to run more than one test. When I offer scholarships now, I always just offer the Big Y-700 test to avoid future issues.

If the tester you need is no longer available, consider the possibility that other people, family members perhaps, might be available to test to represent this same line.

Next, let’s look at mitochondrial test levels and haplogroups.

Mitochondrial DNA Test Type Haplogroup Provided Relevance Upgradable
HVR1 & HVR2 tests (no longer available) Predicted based on around 1000 markers – very reliable at the level predicted Predicted haplogroup, not confirmed, generally formed a couple thousand years ago or earlier Yes, if enough quality DNA remains. Only the mtFull test is available today.
mtFull, full sequence test Tests all 16,569 SNP locations in the entire mitochondria. Most granular and refined. Extremely accurate. Often brings tester into genealogical timeframe, especially with the new Mitotree. Divides testers into multiple haplotype lineages, sometimes descended from known common ancestor. No upgrade needed to receive new Mitotree and mtDNA Discover benefits.
Family Finder autosomal test or transfer Coming soon. Will be the same criteria and caveats as Y-DNA SNPs. May be able to find a similar or upstream haplogroup that might point to a common ancestor. Ask autosomal match if they are willing to take a mtFull test, if relevant, or sponsor a scholarship for them.

Ok, now that we understand more about haplogroups, how they are determined, and where yours came from, let’s look at all of the trees at FamilyTreeDNA.

Trees Within Your Y-DNA and Mitochondrial DNA Account

Let’s start with trees found within your personal account, so sign in.

Each tree has a different purpose and unique benefits.

Tree #1 – Your Matches Genealogy Trees

Each of your matches may have provided links to genealogical trees. They may show trees in multiple places too; at MyHeritage, an archived tree at FamilyTreeDNA, and a WikiTree link. I makes notes about their trees in the comments field, and I also keep a spreadsheet to look for commonalities.

Tree #2 – Haplogroups and SNPs for Y-DNA Testers

Next, for Y-DNA testers, click on the Y-DNA Results and Tools.

You’ll see the Haplotree & SNPs tile on the dashboard.

The Haplotree and SNPs link takes you to a phylogenetic tree that defaults to your haplogroup, where you can view:

  • Variants – SNP mutations that define your haplogroup
  • Surnames with this haplogroup – so long as there are multiple public testers
  • Countries – self-reported for earliest known ancestors (EKA)
  • Recommended Projects – haplogroup projects only – others such as surname projects are found in Discover under Suggested Projects

Tree #3 – The Block Tree for Big Y Testers

People who have taken the Big Y-700 test have a separate section that includes tools for the Big-Y test that aren’t relevant for the 12-111 STR marker tests.

Big Y testers will see the Block Tree tile on their dashboard.

The block tree is an alternative way of displaying matches on a phylogenetic tree. While the Discover Time Tree is viewed left to right, this tree is displayed top to bottom, with each mutation being represented by one grey bar on the scale at left. Each mutation corresponds to approximately 100 years, which is a rough average for the frequency of Y-chromosomal mutations.

People with 30 mutations or fewer are shown as matches, with the goal of reaching back about 1500 years.

Each large block shows the mutation for which the haplogroup is named, such as R-BY482, at the top. The mutations, known as variants, shown below that haplogroup name, are found in the results of each person in that haplogroup, but in the future, people without those mutations, or with additional mutations, will form a new branching haplogroup.

The green “Private Variants” at the bottom of the branches display the average number of mutations of people within that group awaiting another tester to have the same mutations, so a new branch can be formed. I view Private Mutations as “haplogroups in waiting.”

Discover

In addition to the haplogroup trees shown in your account at FamilyTreeDNA, there are several additional trees in Discover for both Y-DNA and mitochondrial DNA. Discover, updated weekly, is a suite of tools for both Y-DNA and mitochondrial DNA that, cumulatively, provides a book about your haplogroup results.

Discover comes in two flavors:

  • The publicly available free version with limited functionality
  • Your private version with expanded functionality available from within your account

You can access Discover, here if you’d like to follow along.

Discover is a publicly available free tool introduced in the fall of 2023 that provides more than a dozen reports, enabling a deeper understanding of all haplogroups.

Just select Y-DNA or mtDNA and enter your haplogroup of choice.

Think of these menu choices, in the sidebar, as chapters in your personal book. Every chapter has something interesting to tell you. Please read them – don’t just scan.

In addition to the free version, if you have taken a Big-Y or mitochondrial DNA full sequence test at FamilyTreeDNA, you’ll have additional information available.

For mitochondrial DNA results, just click on the pink Discover tile.

For Y-DNA results, click on the blue Discover tile.

Within Discover, you’ll find three distinct trees.

Trees #4 and #5 – Y-DNA and Mitochondrial DNA Time Trees

The Time Tree shows your Y-DNA or mitochondrial DNA haplogroup displayed on a timeline, along with:

  • A self-reported ancestral country indicator for every person’s DNA in that haplogroup
  • Haplotype groupings indicating exact matches between everyone in that haplotype.

A haplotype is a grouping of people whose DNA matches exactly, including unstable or hypervariable locations too unreliable to use for haplogroup formation. However, those mutations may be relevant for genealogical matching.

I wrote about haplogroups and haplotypes here and here.

Tree #6 and #7 – Y-DNA and Mitochondrial DNA Class Tree View

The Classic Tree is available for both Y-DNA and mitochondrial DNA.

On the Classic Mitotree View, you can display and filter the tree, including haplotypes, in seven ways, as shown in the dropdown “Display Options.”

Tree #8 and #9 – Y-DNA and Mitochondrial DNA Tree Branch Comparison

Have you ever seen two haplogroups and wondered how closely they are related? Compare provides that answer.

Here, I’m comparing my haplogroup to that of a family member. Everyone is related, but how long ago are we related on our matrilineal lines?

Haplogroup J1c2f compared with haplogroup V216a shows that our common ancestor lived a VERY long time ago – about 55,000 years in the past, someplace in the fertile crescent.

For either Y-DNA or mitochondrial DNA, you can compare two haplogroups. This provides specific information about those two branches of the tree, and where they intersect. To view more about the common ancestor, just pop R+10398 into Discover and learn more about when and where that ancestor lived.

Trees #10 and #11 – Match Time Trees

Match Time Trees are one of the most useful Discover features.

In addition to the Time Trees and Classic Trees provided for everyone in Discover, test takers will also have a Match Time Tree that shows all of your matches, organized genetically.

For mtFull testers, your matches are organized by haplotype cluster. People in your haplotype cluster are your exact matches.

I have over 100 full sequence matches, so I’m only showing the first few in this screenshot. In addition to the match’s name, their EKA (earliest known ancestor) is shown, if provided.

On the Y-DNA Match Time Tree, links are provided to genealogical trees of the tester, which could be an archived FamilyTreeDNA tree, a MyHeritage tree, WikiTree, or some combination.

You can actually see your matches’ WikiTree tree on your Match Time Tree by enabling another feature.

Trees #12 and #13 – WikiTree Tree Integration

While you’re still on the Match Time Tree page for either Y-DNA or mitochondrial DNA, click on Display Options, above the Time Tree, and enable WikiTree Connections. Unfortunately, the default for this great feature is “off.”

I’ve enabled “Share Mode” at the top to obfuscate the names of the testers, and I’ve adjusted the vertical spacing so you can see more in my examples. You’ll notice the grey lines with dots inside circles. I think of these as beads or maybe knots on a rope, but they actually represent a line of ancestors.

Each tester with one of those grey dot bars has connected themselves to their ancestors at WikiTree, a public one-world tree. Living people are not shown, hence the dash marks to the immediate left of the tester’s name.

By mousing over any of the dots, aka ancestors, you can view information about this ancestor of this Estes tester at WikiTree. Ancestors appear in genealogical order in their relevant place on the Time Tree. How cool is that!!!

WikiTree, like any tree, public or private, can have errors. Always verify any tree using original source documents.

As far as I’m concerned, the Match Time Tree is one of the very best features of both Y-DNA and mitochondrial DNA testing and matching. There are so many options to select from, so take some time to look around.

Your Personal Version of Discover is Best

Y-DNA Discover and mtDNA Discover can both be useful for any level of haplogroup, but the best results are obtained when clicking through from the tester’s FamilyTreeDNA account. Big Y and full sequence mitochondrial DNA customers receive additional information, not available in the free, public version of Discover, including

  • The Match Time Tree
    • Including WikiTree integration
  • Globetrekker™ (Y-DNA, mtDNA coming eventually)
  • Up to 30 Ancient Connections, as compared to 3 in the free version
  • Up to 30 Notable Connections, as compared to 3 in the free version

 

Tree #14 – Group Time Trees

I absolutely love Group Time Trees. They are similar to Match Time Trees, but unlike Match Time Trees, are publicly viewable for Group Projects if the volunteer project administrators have enabled this feature for the project.

There are two ways to access Group Time Trees – through publicly accessible Discover or directly through any project.

In Discover, select Group Project in the dropdown.

Then type the name of the surname project you’re seeking. You’ll be presented with a menu if the surname you’ve entered is found in multiple projects, or administrators have listed it as “of interest” in their project.

I clicked on the Estes project.

Viewing the Estes DNA Project, under DNA Results, you can see the various options.

Selecting Y-DNA Results Overview displays the project results by administrator-defined group. The teal groups all descend through Abraham Estes through various sons.

However, by clicking the Group Time Tree instead, you can view all these testers and their results in a Match Time Tree format, arranged genetically.

Clicking on the Group Time Tree link takes you to the Group Time Tree for this project. A menu is displayed at left, based on how the administrator has grouped the project.

I’ve selected several groups that I know descend from the original Estes ancestor from Kent, England. Testers who have joined the Estes project and granted permission for their results to be displayed publicly are automatically grouped genetically, at right, with their surname and EKA (earliest known ancestor), assuming they have entered that information.

Earliest Known Ancestors (EKA)

You’ve probably noticed that earliest known ancestors, along with their locations, are used in many places.

Please enter both your direct paternal (father, father, to father’s line) and direct matrilineal (mother, mother, to mother’s line) earliest known ancestors, along with their locations. I wrote about how to do that in “Earliest Known Ancestors” at FamilyTreeDNA in 3 Easy Steps, here.

Trees #15 and #16 – Public Trees

In addition to trees within testers’ accounts, Discover trees, Group Time Trees, and WikiTree tree integration, FamilyTreeDNA provides two additional public trees.

FamilyTreeDNA made the Y-DNA and mitochondrial DNA haplogroup trees freely available years ago, at the bottom of their main company public page – without signing in.

These trees are still actively maintained today and are free for everyone to use.

To find these trees, scroll all the way to the very bottom of the page, in the footer, to the Community section. Yes, I know, it’s a bit like a scavenger hunt!

You can select to view either the Y-DNA or mtDNA tree. I love this tree, because it shows how many SNP-confirmed people have been tested. That number does not include the thousands of academic and public samples that may be utilized to help define haplogroups, and that you’ll sometimes see in your Ancient and Notable Connections.

So, if you receive a new haplogroup, but you don’t see a new match on your list or on the Block Tree, it’s probably because you match a high-quality academic sample.

The trees display from the root, meaning the oldest haplogroup is shown at the top. In the Y-DNA tree, above, haplogroup A-PR2921 is “Y-Adam”.

You can select any haplogroup on the bar across the top, search by country, or select a specific branch name to view.

The tree itself is viewable by country, as shown above, or by variant, meaning the haplogroup-defining mutations, shown below.

Additionally, for the Y-DNA tree, you can choose to display by surname, so long as there are two or more testers with that identically spelled surname who share this haplogroup and who have given permission for public display.

Please note that these people are all SNP-tested and confirmed at the level reported, but they are NOT all Big-Y testers.

This feature alone can be genealogy-changing because they may be surnames associated with your ancestors in records, or they may just be neighbors. Or maybe you thought they were “just neighbors,” but they are actually related.

At one time, customers could order an individual SNP test for R-M269 to confirm their predicted haplogroup. That test is no longer available, but anyone who took that test to confirm R-M269 and never tested or received results (like Family Finder) at a more granular level will be reported at R-M269. Note that 687 is the number of distinct surnames shown, not the total number of testers.

The three “hamburger dots” on the right side provide options for a user-reported Country Report based on the location of their earliest known ancestor, and a Surname Report. The surname report for R-M269 shows a total of 2448 testers who share those 687 surnames.

It’s a Whole Forest

Who knew there were 16 unique trees available at FamilyTreeDNA!

Each tree has a unique purpose and provides information not available elsewhere.

Take a look and see what kind of information is waiting for you – and don’t forget to check back often.

_____________________________________________________________

Share the Love!

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

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

The New FamilyTreeDNA NGS Family Finder Test

Click on any image to enlarge

Recently, in a press release, FamilyTreeDNA announced a new version of their Family Finder autosomal test that increases coverage from about .02% to about 9% of the human genome. Increasing coverage to this level using precision genomics holds great promise for the future.

Everyone who has purchased a Family Finder test since the beginning of March is automatically tested using the new technology – and it doesn’t cost any more than the earlier test.

Image not to scale because if it was, you would be able to see the bottom line at all:) This is meant to convey the message of more data!

As shown in this slide presented by Dave Vance, Senior VP and General Manager at FamilyTreeDNA, the new test covers 400 times more DNA locations than the industry-standard microarray chip-based test.

The typical vendor microarray autosomal DNA test covers somewhere between 400,000 and 750,000 locations.

Utilizing this new technology is an investment in the future.

You Don’t Know What You Don’t Know

To quote Dave:

Two numbers I want you to remember.

0.02 is the percent of your whole genome reported by standard autosomal tests today. All of your ancestry estimates, shared segments, and autosomal matches come from that small fraction.

9 is the percent of your genome that our new Family Finder test reports at high quality coverage. Starting right now — that’s over 400 times more data, from the very same test.

And the real point isn’t the number. It’s what that data makes possible. This gives us the foundation to unlock deeper, more meaningful insights — not just today, but for years to come. And when it becomes possible to go even further, I want FamilyTreeDNA to lead the way.

But what does that 9% mean for your genealogy research?

It means fewer unexplained matches, a clearer understanding of how people are related, and more confidence in the conclusions you draw from your autosomal DNA. Moving from connections to explanations, and from data to answers.

And until we can start rolling out those deeper insights, for now you’ll still get the same trusted Family Finder experience you’re used to — but you’ll also have the benefit of data that’s ready to unlock even more as new insights become possible.

In fact, you can watch Dave for yourself, at RootsTech, on the mainstage, here, having the unenviable position of following the Irish-step-dancing Gardiner Brothers. Yea, Dave, I didn’t get that gene either!

What makes NGS sequencing so special?

Sequencing Types

NGS is the abbreviation for Next Generation Sequencing, also called massive parallel sequencing. Rather than using individual probes, NGS is a high-throughput technology that simultaneously sequences millions of DNA fragments while still allowing targeting of specific regions.

Dave wrote about the differences between different types of sequencing, here.

All vendors select or target locations in the human genome that are most relevant for their product set, purpose or goals.

The older microarray sequencing machines have been in use for many years. They use probes to read specific targeted addresses, one by one, identifying which of four nucleotides is present at each location on your two copies of each chromosome.

The four nucleotides, adenine (A), thymine (T), cytosine (C), and guanine (G) are the building blocks of DNA, and you receive one from each parent at every location on chromosomes 1-22. Chromosome 23, the sex selection chromosome is a little bit different due to X-DNA and Y-DNA, but the locations are still read the same way using NGS technology.

The results of DNA testing are essentially a downloadable output file with the following information for each read:

  • The RSID SNP cluster ID chromosome
  • The chromosome number
  • The position (think street address) on the chromosome
  • The results, which are the abbreviations for the nucleotide found on the first and second strands of your DNA at that location

In autosomal DNA testing, positions on strands cannot inherently be identified as maternal or paternal without additional techniques such as parental comparison or phasing.

This data file is not meant for you to analyze, but for computers to compare to other DNA testers. Needless to say, the power of the data lies in the information it holds, such as ethnicity, haplogroup-identifying mutations, and matching with other testers.

The output files must be compatible with each other, or the vendors must make accommodations for any incompatibility.

Regardless of the sequencing type, currently, all genetic genealogy vendors’ download files use this same pattern.

The difference between the files and file types from each vendor is:

  • The technology used for the test
  • How much DNA is tested
  • How many rows of data are provided in the download file
  • The quality of the results

Sequencing Type Differences

Let’s put this in terms that we all understand.

With microarray sequencing, a utility worker is sent to each address to read the two nucleotides.

With both NGS and whole-genome sequencing, many addresses are read at the same time. Think of a fleet of drones flying over a neighborhood and reading what is written on the rooftops of each house address.

The difference between the type of NGS sequencing utilized by FamilyTreeDNA, and whole-genome sequencing is threefold:

  1. NGS targets specific addresses and neighborhoods in a controlled manner, because we know they are useful and are specifically interested in the data at those locations. In other words, it omits oceans, deserts, and other places that we know aren’t useful for genealogy.
  2. Whole-genome sequencing covers the majority of the genome, even though more than 90% of the genome is identical in all humans. In other words, the fleet of whole-genome sequencing drones flies over everything, including oceans and deserts, reading and storing everything.
  3. The number of times the drones fly over each address.

For example, a low-pass whole-genome test would fly over the entire world (your genome), scanning it once or twice, but there will be cloud cover and weather in some locations. Typically, you want at least two complete reads from each address to compare to ensure a minimum level of quality. The missed areas need to be estimated with tools like imputation to fill in the blanks.

The breadth of DNA covered is known as “coverage”, or “pass coverage”. So, whole-genome testing covers all or most of the genome, including more than 90% that is not genealogically relevant because it’s identical in all humans.

With NGS sequencing, you specify which locations or neighborhoods you want the drones to read, and you instruct them to fly over just those regions, say, 5 or 10 times. Even if there’s weather or another issue, chances are that at least some of those passes will be able to read both nucleotides.

How many times a particular location, or base, is read is known as “read depth” or “sequencing depth”. The greater the depth, the higher the quality and accuracy of the targeted locations, which means less imputation or “fixing” is needed.

Within the industry, confidence to coverage correlation is about 93% confidence of accuracy for both alleles at a given location at a depth of 5X, which rises to about 99% accuracy at a depth of 10X.

Using our examples, whole-genome sequencing covers about 98% of the genome, at a depth specified by the vendor. Low-pass whole-genome testing is typically performed at a depth of 2X, meaning each location is scanned twice.

NGS combines the best aspects of both “drone style” and “targeted” reads, providing the highest accuracy for the areas that are most important for genetic genealogy at an affordable price, while also targeting enough of the human genome to allow for new discoveries that may be important to either population genetics for ethnicity identification, or to identify your own family lineage mutations.

Yes, you can get both high coverage and very deep reads. That’s called medical-grade whole-genome sequencing, where your entire genome is sequenced to a depth of at least 30X, but it’s both expensive and not useful for genealogy. None of the genealogy vendors are prepared to, or need to, process the massive amount of data generated by a medical-grade whole-genome test, so there is no benefit to taking that type of test for genealogical purposes.

Why is NGS Sequencing Important?

FamilyTreeDNA has moved from the 700,000+ SNPs previously read on their microarray chip, to more than 280 million base pairs. So, from about .02% to about 9% of the 3.1 billion base pairs of the human genome.

Technology has improved to the point where NGS sequencing is no more expensive than microarray sequencing and provides substantially more results.

In other words, there’s no reason NOT to implement this technology now. The new Family Finder test is fully compatible with their earlier Family Finder tests, so everything is painless.

Plus, NGS allows FamilyTreeDNA to target specific locations that benefit their customers, such as both Y-DNA and mitochondrial DNA SNPs. Of course, you’ll still need to take the Big Y-700 or the full sequence mitochondrial DNA (mtDNA) test for full results and matching – but males will receive a confirmed Y-DNA mid-level haplogroup now, with midrange mtDNA haplogroups coming in the future for Family Finder testers. This is a feature that other vendors don’t target or provide at the same level.

I’m very hopeful that these foundation haplogroups will serve as an “appetizer” and will encourage more people to take both the Big Y-700 (males only) and the mtFull test (for everyone), as applicable, to receive those types of specific matches and learn more about their ancestors.

Speaking of the future, how do you future-proof your DNA?

Future-Proofing Your DNA

If you’ve already tested, should you purchase a new Family Finder test for yourself now?

No.

I know you didn’t expect that answer, but here’s why.

Everyone who purchases a Family Finder test, which uses NGS technology, receives the same matching and features as the legacy test.

FamilyTreeDNA doesn’t yet know the benefits and discoveries that will eventually be available, and they won’t know until after they have results of customers to work with.

Having said that, you will definitely want to future-proof your DNA and the results of anyone whose results you count on to help sort through your own.

So, let’s make a plan!

Assuring Future Compatibility

Plan 1 – Test Your Relatives:

Your closest relatives are your best assets. They help you determine how you match others, who you share ancestors with, and the identities of those ancestors. You absolutely need to test the following relatives if they are available:

  • Parents
  • Grandparents
  • Siblings, both full and half – test all of them if both parents aren’t available for testing.
  • If your sibling(s) are deceased or not available, their children carry half of their DNA, but not the same half, so test everyone available. You don’t need to test your siblings’ children if that sibling is available to test.
  • Aunts and uncles, or their descendants if they are not available
  • Great-aunts and uncles, or their descendants if they are not available
  • First and second cousins

Plan 2 – Person Has Never Tested:

Plan 3 – Already Tested at FamilyTreeDNA:

  • If they or you have already taken a Family Finder test at FamilyTreeDNA, an upgrade offer will be forthcoming soon. You don’t need to do anything now.
  • If the person is critical for your research, elderly, or there is some other reason for concern, the tester or kit manager can contact FamilyTreeDNA customer support now and inquire whether or not there is an unopened vial of DNA.
  • To assure that there is enough DNA left for the future, or that the DNA sample is not too old, you can request that a “C/D vial” set be sent to you/them just in case. Be sure the current address is valid.
  • This is also a good time to be sure that your/their Beneficiary Information and/or Kit Manager information is current as well. You’ll find both under Account Settings beside the name in the upper right corner of the page.

Plan 4 – Uploaded From Another Vendor:

  • If you uploaded your DNA file to FamilyTreeDNA from another vendor instead of testing there, hold your horses for now. You’ll clearly have to swab, because when you do an upload, only the data file is uploaded. No DNA is actually transferred or uploaded. I’m not sure what process will be put in place for transfer/uploaded testers, but FamilyTreeDNA will let you know when something is available.

What NOT to Do

I contacted FamilyTreeDNA and this is what they ask customers NOT to do:

  1. Don’t request that your current test be deleted so you can order a new one. This removes everything – linkages, trees, family matching, permissions, project membership, other tests, and notes. Not just for you, but for your matches who have done work on their match with you as well.
  2. Don’t order a second kit, which causes “twins” in the system. I don’t have inside knowledge, but I’ll bet there will be special upgrade pricing if you just wait a bit!

I’m Excited

I don’t know what the future holds, but I’m hoping for:

  • More granular ethnicity (we always want that, right?)
  • More confident matching
  • Improved relationship identification
  • Additional tools to identify descendants of specific ancestors
  • Tools to identify missing ancestors

As a contract member of the R&D team, I’ll let you know when my NGS results are back and how they compare to my matches on the current chip. You know I’m building that spreadsheet already!!

_____________________________________________________________

Share the Love!

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

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

RootsTech 2026 – The Wind Beneath Our Wings

I started writing this article on Sunday evening, the day after RootsTech ended, and I’m basking in the afterglow. Also, my back and feet may never forgive me.

As a tongue-in-cheek comment, I think someone coined the word “exhausterwhelmulated” and defined it as being exhausted, overwhelmed, and overstimulated all at once. Yep, that’s me.

However, I need to add another couple of words to this – gratitude and joy.

Gratitude and Joy

I’m going to try to express this without sounding too sappy.

Do you recall the joy you used to feel when you spotted a relative you loved dearly but didn’t get to see often? Think of the unbridled joy as you piled out of your parents’ car and spotted your grandmother coming out of the door because she saw the car pull up. You ran as fast as your little legs could carry you directly into her arms, and got hugged so tightly it nearly squeezed the breath out of you.

I don’t know what the word for that would be, but it’s similar to how RootsTech feels.

Let me explain. Continue reading

RootsTech 2026 Schedule: Online and In-Person Sessions Plus Book Signing – You’re Invited!

RootsTech is right around the corner.

Like always, there’s so much energy swirling around RootsTech, whether you’re attending in person or virtually. I can hardly wait!

If you’re attending RootsTech in Salt Lake City, I hope we have the opportunity to connect. Please be sure to say hello.

I have a few DNAeXplain badge ribbons left, so be sure to ask me for one. When they are gone, they’re gone and will soon become a RootsTech collector’s item!.

Register

Be sure to register for the free online conference, here, if you aren’t attending in Salt Lake City. All of the in-person only sessions have a syllabus available, and many speakers include their slides. So be sure to check everything out, even sessions that are in-person only.

Join Relatives at RootsTech

Oh, and while you’re at it, sign up for Relatives at RootsTech, here, and see which of your cousins are attending either virtually or in-person. I’ve written several articles about how I utilize Relatives at RootsTech, here.

Roberta’s Schedule

Here’s my presentation, appearance and book-signing schedule.

“Monday’s with Myrt”, hosted by Pat Richley-Erickson (Myrt), a RootsTech tradition, is always broadcast from the FamilySearch Library in SLC on the Monday before RootsTech. Myrt live-streams interviews and discussions with lots of people you know. 

I’ll be discussing something completely out of the ordinary for me – with surprise visuals! Here’s the link. Come join us for the fun!

Thursday is a VERY Busy Day With Four Sessions

This recorded session is available for everyone at this link, beginning when RootsTech opens and throughout the conference. This session is sponsored by FamilyTreeDNA, which makes sense because they are the only vendor that offers X-DNA matching.

Show Floor

Two of my events will take place in booths on the show floor. The book-signing in in the GenealogyBank booth, at far right, and the MyHeritage session is right inside the main entrance where you can’t miss it!

You can purchase my books during the signing while supplies last. If you’ve previously purchased a book and would like it signed, you can bring the book, of course, or I will have some bookplates with me that I will gladly sign for you.

  • Thursday, March 5 – 2 PM Mountain Time (SLC), MyHeritage booth #900, Everything I Love About MyHeritage

Ok, so this session might not include quite EVERYTHING I love about MyHeritage. I’m going to begin in an unexpected place with an underutilized tool, Cousin Finder, and work my way through using the rest of the MyHeritage DNA (and supporting) tools successfully. Two fun case studies in my own family with an unexpected twist that every genealogist dreams about. MyHeritage makes it easy to jump the pond!

Mitochondrial DNA to Z is in-person only, so not recorded or livestreamed. Here’s the link which includes my slides. (You’re welcome!).

Friday Holds Two Great Sessions – Including One That’s Livestreamed

Y-DNA to Z is in-person only, so not recorded or livestreamed. Here’s the link which includes my slides. (You’re welcome!).

Mapping Maternal Connections, sponsored by FamilyTreeDNA, is available both in person and online. As a contract member of the R&D team, and as a genetic genealogist, I’m really excited to share the latest updates with you, as well as how I’m using the new MitoTree, matching and Discover to solve long-standing mysteries. Here’s the link, which includes a syllabus.

Just so you know, recordings of online sessions will be available after the event, so if you miss it, come back to view later.

_____________________________________________________________

Share the Love!

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

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

2025 Genetic Genealogy Retrospective: Wow – What a Year!

2025 has been quite a year in genetic genealogy. Genetic genealogy, per se, really isn’t a separate “thing” anymore. DNA testing is now an integral part of genealogy, with the potential to answer questions that nothing else can!

The 76 articles I wrote in 2025 fall into multiple categories and focus on different topics based on what was happening in the industry.

From my perspective, here are the most notable announcements and trends in genetic genealogy, and genealogy more broadly.

#1 for 2025 – Mitochondrial DNA: The Million Mito Project Released the New Mitotree, Updates, and mtDNA Discover

The biggest genealogy news items this year, both industry-wide and genealogy-changing are definitely the release of the new Mitotree, plus two tree updates. But that’s not all.

In addition, full sequence mitochondrial DNA testers received new Mitotree haplogroups, if appropriate, and everyone received a haplotype – a new feature. Along with Mitotree, FamilyTreeDNA introduced mtDNA Discover which provides 13 individual reports based on your haplogroup and matches.

It’s no wonder that mitochondrial DNA articles led the pack with the most views based on the eleven articles about that topic. If you haven’t yet tested your mitochondrial DNA at FamilyTreeDNA, there’s no better time! You never know what you’re going to discover and the more testers, the more matches for everyone.

You don’t know what you don’t know, and you’ll never know if you don’t test. Remember, mitochondrial DNA is for both males and females and tests your mother’s direct matrilineal line (mother to mother to mother, etc.) – reaching beyond known surnames.  Click here to order or upgrade.

#2 – MyHeritage Low Pass Whole Genome Sequence Test Charges into the Future

Another big hitter is the new MyHeritage low-pass whole genome test (WGS) test. It’s new and innovative, but we haven’t seen comparative results yet.

My results from the new low-pass whole genome test just came back, and I haven’t had the opportunity to review them yet, as compared to the earlier tests. That said, I do have roughly the same number of matches, but I need to determine if they are the same matches, and how well they track. I’ll be working on that review soon.

The new whole genome test may be more about future proofing and preparedness than additional current benefit – but we will see. I definately wanted to take the whole genome test so I can receive and benefit from whatever new is coming down the pike.

MyHeritage allows you to maintain multiple DNA tests on your account, so the new whole genome won’t “replace” your older or uploaded test. That way, you can easily compare the results of the whole genome against any DNA test that you curently have at MyHeritage.

Click here to order the new test.

#3 – 23andMe Experiences Problems

On a less positive note, but still quite newsworthy is the bankruptcy of 23andMe and subsequent repurchase of 23andMe by the original founder after setting up a new nonprofit. I have real mixed feelings about this topic. However, 23andMe was really never about genealogy, and now, matching segment information is no longer available. Those searching for unknown parents or family may want to test there if they are unsuccessful elsewhere.

Best Genealogy Tool

The FamilySearch full text search continues to have a HUGE impact for genealogists. This tool is not one-and-done, but provides increasing amounts of rich information as more records are added to the “fully scanned” collection. If you haven’t tried it, please do. It’s a game-changer and continues to improve.

A Cautionary Word About AI – Artificial Intelligence

AI is such a hot topic right now that I feel it needs to be included.

The FamilySearch full text search uses a form of AI. However, you’ll quickly notice that it can’t read everything, gets words and names wrong, and if you actually need to fully depend on it for accuracy, you cannot. (That said, it’s still an amazing tool, and I’m not picking on FamilySearch.)

Aside from FamilySearch, AI in its current form is both wonderful and terrible. I’ll be writing about AI in the new year, but for now, don’t ever rely on AI for anything that you can’t verity. It’s your assistant, not an expert, no matter how insistent it is. Never trust and always verify.

This is ESPECIALLY TRUE WHEN RELATED TO GENETICS and genetic related topics. I can’t even begin to tell you how very wrong it has been, and how much people fall in love with inaccurate results. No, just no – at least for now.

You need to know your AI tool, your skill set, your understanding of AI broadly, the tool’s limitations, and yours, and that’s all before verifying the actual AI results. If you want to educate yourself, and everyone should, treat yourself to anything, anyplace by either Mark Thompson or Steve Little, the dynamic AI duo. They offer YouTube videos and classes in a wide variety of places – but keep in mind that AI tools and technology literally change every few weeks.

AI is, indeed, a specialty all unto itself, much like genetic genealogy. And right now, it’s not soup yet, but it is cooking.

Tried and True Genetic Genealogy Staples – DNAPrint and Genetic Affairs

I haven’t written about either one this year, but I use both DNAPainter and Genetic Affairs regularly.

I consistently paint segments from matches at both MyHeritage, FamilyTreeDNA, and GEDmatch that are newly identified to an ancestor or ancestral couple at DNAPainter.

Unfortunately, neither Ancestry nor 23andMe provide matching cM location information for your matches (chromosome browser), but you may find some people who have tested at those companies at both FamilyTreeDNA and GEDmatch if they have uploaded to either of those vendors. Both vendors provide segment information and a Chromosome Browser, enabling you to paint that information to DNAPainter when you can identify your common ancestor.

MyHeritage also provides a Chromosome Browser, but unfortunately, no longer accepts uploads from any other vendor. You can paint segments from MyHeritage, but no longer upload DNA files to MyHeritage.

Thanks to DNAPainter, I have 90% of my segments identified to specific ancestors – which is actually rather remarkable given that my mother’s grandfather was a Dutch immigrant, and her great-grandparents on her other side were German immigrants, meaning we don’t have many matches on either of those lines.

Genetic Affairs continues to develop new, advanced clustering tools, one of which I’ll be reviewing soon.

Major Vendor Releases

Aside from what’s listed above, most of the major vendors released new features.

MyHeritage released a VERY COOL new tool called Cousin Finder that finds your relatives in the MyHeritage database, whether they match you on a DNA test, or not. They may not have even taken a DNA test. Cousin Finder identifies your common ancestor and shows your relationships. It’s a wonderful way to initiate communications, discuss your common ancestors, and ask about DNA testing.

Of my 378 Cousin Finder matches, only 23 (about 6%) are on my DNA match list, so that leaves 355 people to message, several of whom represent Y-DNA and mtDNA lines I don’t have. You can bet I’ll be offering testing scholarships.

Additionally, MyHeritage released a new ethnicity version.

FamilyTreeDNA, in addition to the new Mitotree, Discover, and associated features, released a new match matrix so you can see if and how selected matches are related to each other in a grid format. In other words, you can create your own cluster.

A new built-in “Share” feature blurs private information to make sharing easier both on the website and in Discover.

Discover improvements include thousands of new Y-DNA and mtDNA tree branches, plus thousands of new Ancient DNA samples. Discover is evergreen, so once you’ve taken that Big Y-700 test or the mitochondrial DNA test, your learning never stops as more content is added.

Tree integration with WikiTree is super-easy and means you don’t have to choose between trees. You can choose to retain your archived tree at FamilyTreeDNA, or move your tree to MyHeritage, PLUS link yourself to your family at WikiTree.

Ancestry released match clustering and a new beta pedigree view of ThruLines, but that’s back in the shop for more work. I’d expect to see it rereleased in 2026.

Conferences

RootsTech is the granddaddy of genealogy conferences, and it’s always fun to attend and write about the experience. Many vendors release new tools or products during the conference.

The ECGGC (East Coast Genetic Genealogy Conference), held in the fall, is the only conference that focuses entirely on genetic genealogy, new tools, how to use existing tools, and more. The 2025 conference was virtual and provided a great deal of focused content. Attendees particularly appreciate the deep dive in a particular topic presented in DNA Academy.

I’ll be at RootsTech in 2026, will write about that soon, and hope to see you there.

Concepts, Techniques and Plain Old Genealogy

In the past, my Concepts series and genealogy “how to” articles have been very popular, so, in 2025, I penned a half-dozen articles focusing on frequently asked questions about relationships and DNA.

For example, how does one go about finding DNA testing candidates? The number of options may surprise you and includes both Cousin Finder and Relatives at RootsTech.

By testing ONE PERSON for either Y-DNA or mitochondrial DNA that represents an ancestor, you actually receive information about that entire lineage of ancestors. So, on my Estes line, by locating an Estes male from my line to test, I received relevant information for every Estes male in my line, back to and beyond the progenitor.

Eventually, we hit a brick wall in every line, and those tools are the perfect way to break through those brick walls.

Other articles discuss things like how to use Discover’s Ancient Connections, and the difference between half and full relationships, both in your tree and genetically. Plus, what does a cousin “once removed” mean anyway? And why do I care?

Another question I receive is how far back, based on the shared amount of DNA, should I look in my matches’ trees for our common ancestor? In other words, how many generations back should I click? That article was fun and produced some unexpected results.

Memorial Articles

Because we are part of a community, I write memorial articles when one of our friends passes on. This year, sadly, Schelly Talalay Dardashti, well-known Jewish genealogist, and another very close friend joined the ancestors, so I’ve recognized the best in both of their lives which constitutes their legacy.

Be the Storyteller

Last, but not least, I wrote about my ancestors in the “52 Ancestors” series, which launched several years ago with Amy Johnson Crow’s challenge to write about one ancestor per week. She hosts this every year, and you can join (free) now.

I’m now on ancestor #467, so yes, it’s addictive, but it’s also AMAZING how many wonderful cousins I’ve met who have information that I did not. Not only that, but after publishing about an ancestor, I’ve discovered that I’m related to people I’ve known for years. We were SOOOooo excited!

I’ve been writing about the lives of my ancestors for several years now, and the articles include attempts to identify Y-DNA and mtDNA testers for each ancestor, where appropriate. There’s so much to learn that can’t be revealed any other way.

Plus, people seem to like the “mystery” and “short story” aspect, and I salt each story with the history of the region and relevant historical events of the timeframe. You might find your ancestors here too, or other helpful information.

Find a way to share about your ancestors!

Do You Have Suggestions for 2026 Topics?

Do you have suggestions or requests for article topics in 2026? If so, please comment on this article and let me know.

Check Out the 2025 List

Here’s the list of the 2025 articles. Did you miss something fun? Enjoy!

  Title Category Date Link
1 Welcome to 2025 – Opportunities and New Genetic Genealogy Articles Welcome, general 1-2-2025 https://dna-explained.com/2025/01/02/welcome-to-2025-opportunities-and-new-genetic-genealogy-articles/
2 Anne Doucet (1713-1791), Oceans, Rivers, and Perseverance – 52 Ancestors #438 52 Ancestors 1-4-2025 https://dna-explained.com/2025/01/04/anne-doucet-1713-1791-oceans-rivers-and-perseverance-52-ancestors-438/
3 Register for RootsTech 2025 Now RootsTech 1-16-2025 https://dna-explained.com/2025/01/16/register-for-rootstech-2025-now/
4 What IS the McNeil Family History, by George Franklin McNeil – 52 Ancestors #439 52 Ancestors 1-19-2025 https://dna-explained.com/2025/01/20/what-is-the-mcneil-family-history-by-george-franklin-mcneil-52-ancestors-439/
5 Jean Garceau dit Tranchemontagne (c1785-1711), Soldier from Saint Marseault – 52 Ancestors #440 52 Ancestors 1-29-2025 https://dna-explained.com/2025/01/29/jean-garceau-dit-tranchemontagne-c1785-1711-soldier-from-saint-marseault-52-ancestors-440/
6 Memories Resurface When the Old Family Home Gets a Facelift Genealogy 2-3-2025 https://dna-explained.com/2025/02/03/memories-resurface-when-the-old-family-home-gets-a-facelift/
7 MyHeritage Introduces Ethnicity v2.5 MyHeritage 2-6-2025 https://dna-explained.com/2025/02/06/myheritage-introduces-ethnicity-v2-5/
8 Relatives at RootsTech Reveals Cousins and Provides DNA Candidates RootsTech, techniques 2-8-2025 https://dna-explained.com/2025/02/08/relatives-at-rootstech-reveals-cousins-and-provides-dna-candidates/
9 FamilyTreeDNA’s New Matrix Shows How Your Matches Are Related to Each Other FamilyTreeDNA 2-12-2025 https://dna-explained.com/2025/02/12/familytreednas-new-matrix-shows-how-your-matches-are-related-to-each-other/
10 René Doucet (c1680-c1731), Lifetime of Incessant Upheaval – 52 Ancestors #441 52 Ancestors 2-15-2024 https://dna-explained.com/2025/02/16/rene-doucet-c1680-c1731-lifetime-of-incessant-upheaval-52-ancestors-441/
11 Lineages Versus Ancestors – How to Find and Leverage Yours Techniques 2-23-2025 https://dna-explained.com/2025/02/23/lineages-versus-ancestors-how-to-find-and-leverage-yours/
12 Mitotree is Born Mitochondrial DNA 2-25-2025 https://dna-explained.com/2025/02/25/mitotree-is-born/
13 RootsTech 2025 – The Year of Discover and the New Mitotree RootsTech, Mitochondrial DNA 3-14-2025 https://dna-explained.com/2025/03/15/rootstech-2025-the-year-of-discover-and-the-new-mitotree/
14 Pierre Doucet (c1621-1713), Walking History Book Lived to Nearly 100 – 52 Ancestors #442 3-16-2025 https://dna-explained.com/2025/03/16/pierre-doucet-c1621-1713-walking-history-book-lived-to-nearly-!100-52-ancestors-442/
15 Welcome to the New FamilyTreeDNA mtDNA Group Mitochondrial DNA 3-17-2025 https://dna-explained.com/2025/03/17/welcome-to-the-new-familytreedna-mtdna-group/
16 23andMe Files for Bankruptcy – What You Need to Know! 23andMe 3-24-2025 https://dna-explained.com/2025/03/25/23andme-files-for-bankruptcy-what-you-need-to-know/
17 New “Share” Features at FamilyTreeDNA Blur Match Information and Make Sharing Easy FamilyTreeDNA 4-1-2025 https://dna-explained.com/2025/04/01/new-share-features-at-familytreedna-blur-match-information-and-make-sharing-easy/
18 The Chauvet Cave: Trip Back in Time with Prehistoric European Humans – Are We Related? History, DNA 4-6-2025 https://dna-explained.com/2025/04/06/the-chauvet-cave-trip-back-in-time-with-prehistoric-european-humans-are-we-related/
19 DNA for Native American Genealogy Webinar & Companion Book Native American 4-8-2025 https://dna-explained.com/2025/04/08/dna-for-native-american-genealogy-webinar-companion-book/
20 Marie Levron (c1686-1727), Tragedy from Cradle to Grave – 52 Ancestors #443 52 Ancestors 4-14-2025 https://dna-explained.com/2025/04/14/marie-levron-c1686-1727-tragedy-from-cradle-to-grave-52-ancestors-443/
21 Mitochondrial DNA: What is a Haplotype Cluster and How Do I Find and Use Mine Mitochondrial DNA 4-14-2025 https://dna-explained.com/2025/04/14/mitochondrial-dna-what-is-a-haplotype-cluster-and-how-do-i-find-and-use-mine/
22 New Mitotree Haplogroups and How to Utilize Them for Genealogy Mitochondrial DNA 4-23-2025 https://dna-explained.com/2025/04/23/new-mitotree-haplogroups-and-how-to-utilize-them-for-genealogy/
23 Sir Francois Levron dit Nantois(c1651-1714), and Acadia’s Pirate – 52 Ancestors #444 52 Ancestors 4-26-2025 https://dna-explained.com/2025/04/27/sir-francois-levron-dit-nantois-c1651-1714-and-acadias-pirate-52-ancestors-444/
24 Catherine Savoie (c1661-c1722/25), Whispered Threads Weave a Tapestry of Life – 52 Ancestors #445 52 Ancestors 5-4-2025 https://dna-explained.com/2025/05/04/catherine-savoie-c1661-c1722-5-whispered-threads-weave-a-tapestry-of-life-52-ancestors-445/
25 Discover’s Ancient Connections – How Are You Related? Discover, Ancient DNA 5-8-2025 https://dna-explained.com/2025/05/08/discovers-ancient-connections-how-are-you-related/
26 Mother’s Day and Legacies 52 Ancestors, Genealogy 5-10-2025 https://dna-explained.com/2025/05/11/mothers-day-and-legacies/
27 The Mystery of the Blue Fugates and Smiths: A Study in Blue Genes and Pedigree Collapse Genetics, Genealogy 5-18-1015 https://dna-explained.com/2025/05/19/the-mystery-of-the-blue-fugates-and-smiths-a-study-in-blue-genes-and-pedigree-collapse/
28 Regeneron Wins Bid for Bankrupt 23andMe – Wedding Planned 23andMe 5-19-2023 https://dna-explained.com/2025/05/19/regeneron-wins-bid-for-bankrupt-23andme-wedding-planned/
29 Francois Savoie’s Homestead Rediscovered – 52 Ancestors #446 52 Ancestors 5-24-2025 https://dna-explained.com/2025/05/24/francois-savoies-homestead-rediscovered-52-ancestors-446/
30 Memorial Day – Some Gave All Memorial 5-25-2025 https://dna-explained.com/2025/05/25/memorial-day-some-gave-all/
31 Mitotree Webinar – What It Is, How We Did It, and What Mitotree Means to You Mitochondrial DNA 6-4-2025 https://dna-explained.com/2025/06/04/mitotree-webinar-what-it-is-how-we-did-it-and-what-mitotree-means-to-you/
32 Catherine LeJeune (c1633-1671/1686), Meet Your Grandchildren – 52 Ancestors #447 52 Ancestors 6-7-2025 https://dna-explained.com/2025/06/07/catherine-lejeune-c1633-1671-1686-meet-your-grandchildren-52-ancestors-447/
33 Mitotree Q&A for Everyone Mitochondrial DNA 6-11-2025 https://dna-explained.com/2025/06/11/mitotree-qa-for-everyone/
34 Father’s Day: Bravery and Love 52 Ancestors, Genealogy 6-14-2025 https://dna-explained.com/2025/06/14/fathers-day-bravery-and-love/
35 Francoise Bourgeois (c1659-1693/1697), High Drama in Beaubassin and Terror at Port Royal – 52 Ancestors #448 52 Ancestors 6-16-2025 https://dna-explained.com/2025/06/16/francoise-bourgeois-c1659-1693-97-high-drama-in-beaubassin-and-terror-at-port-royal-52-ancestors-448/
36 Requesting Suggestions for RootsTech 2026 Topics RootsTech 6-18-2025 https://dna-explained.com/2025/06/18/requesting-suggestions-for-rootstech-2026-topics/
37 FamilyTreeDNA and WikiTree Collaboration – In Two Easy Steps!! FamilyTreeDNA, WikiTree 6-25-2025 https://dna-explained.com/2025/06/25/familytreedna-and-wikitree-collaboration-in-two-easy-steps/
38 Jacques Bourgeois (c1620-c1700), Surgeon of Port Royal – 52 Ancestors #449 52 Ancestors 7-1-2025 https://dna-explained.com/2025/07/01/jacques-bourgeois-c1620-c1700-surgeon-of-port-royal-52-ancestors-449/
39 TTAM, a Nonprofit Formed by 23andMe’s Founder Now Plans to Buy 23andMe 23andMe 7-1-2025 https://dna-explained.com/2025/07/01/ttam-a-nonprofit-formed-by-23andmes-founder-now-plans-to-buy-23andme/
40 Jacques Bourgeois: Complex Acadian, Founder of Beaubassin – 52 Ancestors #450 52 Ancestors 7-6-2025 https://dna-explained.com/2025/07/06/jacques-bourgeois-complex-acadian-founder-of-beaubassin-52-ancestors-450/
41 How to Use Ancestry’s New Match Clusters and What They Mean Ancestry 7-10-2025 https://dna-explained.com/2025/07/10/how-to-use-ancestrys-new-match-clusters-and-what-they-mean/
42 Walk with Your Ancestors: Peace, Light and Healing in an Abandoned Medieval Village History 7-21-2025 https://dna-explained.com/2025/07/21/walk-with-your-ancestors-peace-light-and-healing-in-an-abandoned-medieval-village/
43 Jeanne Trahan (c1629-c1699), Life in Chinon, La Heve, Port Royal, and Beaubassin – 52 Ancestors #451 52 Ancestors 8-2-2025 https://dna-explained.com/2025/07/28/jeanne-trahan-c1629-c1699-life-in-chinon-la-heve-port-royal-and-beaubassin-52-ancestors-451/
44 Wherefore Art Thou, Oh Ancestor – New Generation Tree Chart Suggests Where to Look in Your Matches’ Trees Techniques, Genetics, Genealogy 8-2-2025 https://dna-explained.com/2025/08/02/wherefore-art-thou-oh-ancestor-new-generation-tree-chart-suggests-where-to-look-in-your-matches-trees/
45 Guillaume Trahan (c1601-1625), More Than Meets the Eye – 52 Ancestors #452 52 Ancestors 8-13-2025 https://dna-explained.com/2025/08/13/guillaume-trahan-c1601-c1684-more-than-meets-the-eye-52-ancestor-452/ 
46 The East Coast Genetic Genealogy Conference – ECGGC – Register Now for the Best of the Best ECGGC Conference 8-14-2025 https://dna-explained.com/2025/08/14/the-east-coast-genetic-genealogy-conference-ecggc-register-now-for-the-best-of-the-best/
47 Schelly Talalay Dardashti – May Her Memory Be a Blessing Memorial 8-17-2025 https://dna-explained.com/2025/08/17/schelly-talalay-dardashti-may-her-memory-be-a-blessing/
48 Francoise Corbineau (c1609-c1665), Bride in Chinon, Founder of Acadia – 52 Ancestors #453 52 Ancestors 8-25-2025 https://dna-explained.com/2025/08/23/francoise-corbineau-c1609-c1665-bride-in-chinon-founder-of-acadia-52-ancestors-453/
49 Nicolas Trahan (c1570->1632), Life in the Heart of French Wine Country – 52 Ancestors #454 52 Ancestors 8-31-2015 https://dna-explained.com/2025/08/31/nicolas-trahan-c1570-1632-life-in-the-heart-of-french-wine-country-52-ancestors-454/
50 Mitochondrial DNA A-Z: A Step-by-Step Guide to Matches, Mitotree, and mtDNA Discover Mitochondrial DNA, Discover, Genealogy, Techniques 10-2-2025 https://dna-explained.com/2025/09/02/mitochondrial-dna-a-z-a-step-by-step-guide-to-matches-mitotree-and-mtdna-discover/
51 Renée Desloges (c1570-1627/1632), Fragments of Life in Montreuil-Bellay – 52 Ancestors #454 (this is actually 455) 52 Ancestors 9-6-2025 https://dna-explained.com/2025/09/06/renee-desloges-c1570-1627-1632-fragments-of-life-in-montreuil-bellay-52-ancestors-454/
52 Best Mitochondrial DNA Presentation EVER – You’re Invited to DNA Academy!! Mitochondrial DNA 9-9-2025 https://dna-explained.com/2025/09/09/best-mitochondrial-dna-presentation-ever-youre-invited-to-dna-academy/
53 Unfillable Shoes Memorial – Douglas Rhodenbaugh 9-14-2025 https://dna-explained.com/2025/09/14/unfillable-shoes/
54 Concepts: What Does a Cousin “Once Removed” Mean? Concepts, Genealogy 9-24-2025 https://dna-explained.com/2025/09/24/concepts-what-does-a-cousin-once-removed-mean/
55 Daniel Vannoy (1752-after 1820), “Lived in the Boundary of the Cherokee Indians” – Say What??? 52 Ancestors 9-29-2025 https://dna-explained.com/2025/09/29/daniel-vannoy-1752-after-1820-lived-in-the-boundary-of-the-cherokee-indians-say-what/
56 Daniel Vannoy and the Strange Case of the Two Sarahs – 52 Ancestors #457 52 Ancestors 10-5-2025 https://dna-explained.com/2025/10/06/daniel-vannoy-and-the-strange-case-of-the-two-sarahs-52-ancestors-457/
57 Cousin Finder – MyHeritage’s Innovative New Tool Finds Your Relatives MyHeritage 10-9-2025 https://dna-explained.com/2025/10/09/cousin-finder-myheritages-innovative-new-tool-finds-your-relatives/
58 Sarah Hickerson Vannoy (c1761 – after 1826), Threw More than Shade – 52 Ancestors #458 52 Ancestors https://dna-explained.com/2025/10/13/sarah-hickerson-vannoy-c1761-after-1826-threw-more-than-shade-52-ancestors-458/
59 MyHeritage Introduces a Low-Pass Whole Genome Autosomal DNA Test & Why It Matters MyHeritage 10-14-2025 https://dna-explained.com/2025/10/14/myheritage-introduces-a-low-pass-whole-genome-autosomal-dna-test-why-it-matters/
60 Henriette Pelletret (c1640 – before 1694), Life Death in the Shadow of the Fort – 52 Ancestors #459 52 Ancestors 10-21-2025 https://dna-explained.com/2025/10/21/henriette-pelletret-c1640-before-1694-life-and-death-in-the-shadow-of-the-fort-52-ancestor-459/
61 Cheat Sheet: Mitochondrial Matches, Haplotype Clusters, and Haplogroups Mitochondrial DNA 10-22-2025 https://dna-explained.com/2025/10/22/cheat-sheet-mitochondrial-matches-haplotype-clusters-and-haplogroups/
62 Simon Pelletret (1610-1642/1645): A Walk Through Port Royal – 52 Ancestors #460 52 Ancestors 10-27-2025 https://dna-explained.com/2025/10/27/simon-pelletret-c1610-1642-1645-a-walk-through-port-royal-52-ancestors-460/
63 Perrine Bourg (c1626-1693/1698): Phoenix Rising from the Ashes – 52 Ancestors #461 52 Ancestors 11-2-2025 https://dna-explained.com/2025/11/02/perrine-bourg-c1626-1693-1698-phoenix-rising-from-the-ashes-52-ancestors-461/
64 Concepts: What is a Half Relationships, Life Half First Cousins, Anyway? Concepts, Genealogy 11-4-2025 https://dna-explained.com/2025/11/04/concepts-what-is-a-half-relationship-like-half-first-cousins-anyway/
65 Marie Broussard (1686-after 1752), Life Across the River from Port Royal – 52 Ancestors #462 52 Ancestors 11-10-2025 https://dna-explained.com/2025/11/10/marie-broussard-1686-after-1752-life-across-the-river-from-port-royal-52-ancestors-462/
66 Francois Broussard (1653-1716), Intractable Acadian – 52 Ancestors #463 52 Ancestors 11-22-2025 https://dna-explained.com/2025/11/22/francois-broussard-1653-1716-intractable-acadian-52-ancestors-463/
67 Mitotree Sprouts 12,773 New Branches and Includes Ancient DNA Mitochondrial DNA 11-24-2025 https://dna-explained.com/2025/11/24/mitotree-sprouts-12773-new-branches-and-includes-ancient-dna/
68 Catherine Richard (c1663 – after 1714), Mother of Beausoleil, Acadian Freedom Fighters – 52 Ancestors #464 52 Ancestors 11-29-2025 https://dna-explained.com/2025/11/29/catherine-richard-c1663-after-1714-mother-of-beausoleil-acadian-freedom-fighters-52-ancestors-464/
69 Ancestry’s ThruLines Has a New Pedigree View Ancestry 12-2-2025 https://dna-explained.com/2025/12/03/ancestrys-thrulines-has-a-new-pedigree-view/
70 Ancestry Reverts ThruLines to the Original View Ancestry 12-6-2025 https://dna-explained.com/2025/12/06/ancestry-reverts-thrulines-to-the-original-view/
71 Michel Richard (c1630-1686/1689), Carefree Acadian – 52 Ancestors #465 52 Ancestors 12-7-2025 https://dna-explained.com/2025/12/08/michel-richard-dit-sansoucy-c1630-1686-1689-carefree-acadian-52-ancestors-465/ 
72 Mitochondrial DNA: How Do I Know if I’m a Candidate to Receive a New Haplogroup? Mitochondrial DNA 12-9-2025 https://dna-explained.com/2025/12/09/mitochondrial-dna-how-do-i-know-if-im-a-candidate-to-receive-a-new-haplogroup/
73 Heavens Ablaze: the 1833 Leonid Meteor Storm and Your Ancestors History, Genealogy 12-15-2025 https://dna-explained.com/2025/12/15/heavens-ablaze-the-1833-leonid-meteor-storm-and-your-ancestors/
74 Madelaine Blanchard (c1643 – 1678/1683), Gone Too Soon – 52 Ancestors #466 52 Ancestors 12-20-2025 https://dna-explained.com/2025/12/20/madelaine-blanchard-c1643-1678-1683-gone-too-soon-52-ancestors-466/
75 Soar Inspiration 12-24-2025 https://dna-explained.com/2025/12/24/soar/

_____________________________________________________________

Share the Love!

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

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research