When the Branches Meet: Pedigree Collapse in the Family Tree

I've been doing genealogy long enough to know that not everyone is excited to learn about pedigree collapse in their own family tree. It can feel uncomfortable, even alarming, the first time you spot it - two lines on your pedigree chart that should stay separate, quietly merging into the same ancestor. But here's the thing every genealogist eventually learns: pedigree collapse isn't a scandal. It's math.

What Pedigree Collapse Actually Is

In theory, your family tree doubles with every generation you go back - 2 parents, 4 grandparents, 8 great-grandparents, 16 great-great-grandparents, and so on. Keep doubling, and by the time you're only 20 generations back, you'd need over a million ancestors to fill out the chart.

Except no population in human history has ever been that large for that long. So the branches of your tree start folding back into each other. The same ancestor fills more than one slot on your pedigree chart. That folding is pedigree collapse, and it is a simple genealogical fact: it has happened in every family tree on earth, if you go back far enough. It is nothing to be ashamed of.

It's in My Own Tree

Once you start looking, you find it closer than you might expect.

My 4th-great-grandparents, John W. Younger and Mary Elizabeth Church, were first cousins and they married in Tennessee in 1846. They shared a single set of grandparents - meaning that one couple, further up the tree, occupies two branches instead of one.

On my husband's side, the collapse runs even deeper. His 4th-great-grandparents, James S. Bishop and Eliza Inskeep, were double first cousins - married in Ohio in 1822. A double-cousin match means both of their parents were siblings to each other's parents, so two entire sibling pairs, one generation up, fold into shared ancestry. That's a significant collapse for one couple to carry, and it echoes forward through every one of their descendants, including my husband.

Why It Happened

There's a reasonable, unglamorous explanation for all of this: cousin marriage was widely accecpted for most of human history, and it's only in recent generations that it's fallen out of favor in much of the population. On the American frontier especially, communities were small and mobile out of necessity, not choice. The Bishop and Inskeep families settled in early Logan County, Ohio, where the pool of eligible, similarly-situated spouses was limited. A cousin match wasn't a scandal to them - it was simply who was there.

What makes the Bishop-Inskeep line particularly interesting to me as a researcher is that the family didn't scatter after that marriage. The Bishops and Inskeeps stayed rooted in Logan County for generations, intermarrying with the same small cluster of neighboring families. So it's no real surprise that a second, more distant cousin match shows up further along the line, collapsing the pedigree even further. Once a community is that interconnected, subsequent collapse isn't an anomaly - it's the expected outcome.

Why This Matters for Your Own Research

If you find something similar in your own tree, resist the urge to feel embarrassed on your ancestors' behalf. Instead, treat it as a clue. Pedigree collapse is often a sign that you're looking at a tight-knit, geographically stable community - the kind of community where land records, church rolls, and probate files tend to name the same handful of families over and over. That repetition, frustrating as it can be when you're trying to sort out which "James Bishop" is which, is also a gift: it means there's usually more documentation, not less, once you learn to read the pattern.

Pedigree collapse doesn't shrink your family tree. It just tells you the truth about how small the world used to be.