Category Archives: Group Time Tree

Y-DNA Haplogroup O – When and How Did It Get to the Americas?

Posted on by
10

Y-DNA Haplogroup O has been found in male testers descended from a Native American ancestor, or in Native American tribes in the Americas – but sometimes things are more complex than they seem. The story of when and how haplogroup O arrived in the Americas is fascinating – and not at all what you might think.

Introduction

The concept of Native American heritage and indigenous people can be confusing. For example, European Y-DNA haplogroup R is found among some Native American men. Those men may be tribal members based on their mother’s line, or their haplogroup R European Y-DNA may have been introduced either through adoption practices or traders after the arrival of Europeans.

There is unquestionable genetic evidence that the origin of Haplogroup R in the Americas was through colonization, with no evidence of pre-contact indigenous origins.

Y-DNA testing and matching, specifically the Big Y-700 test, with its ability to date the formation of haplogroups very granularly, has successfully identified the genesis of Y-DNA haplogroups and their movement through time.

We’ve spent years trying to unravel several instances of Native American Y-DNA Haplogroup O and their origins. Native American, in this context, means that men with haplogroup O are confirmed to be Native American at some point in documented records. This could include early records, such as court or probate records, or present-day members of tribes. There is no question that these men are recognized as Native American in post-contact records or are tribal members, or their descendants.

What has not been clear is how and when haplogroup O entered the Native American population of these various lineages, groups, or tribes. In other words, are they indigenous? Were they here from the earliest times, before the arrival of colonists, similar to Y-DNA haplogroups C and Q?

This topic has been of great interest for several years, and we have been waiting for additional information to elucidate the matter, which could manifest in several ways:

  1. Ancient pre-contact DNA samples of haplogroup O in the Americas, but none have been found.
  2. Current haplogroup O testers in Native American peoples across the North and South American continents, forming a connecting trail genetically, geographically, and linearly through time. This has not occurred.
  3. Big-Y DNA matches within the Americas between Haplogroup O Native American lines unrelated in a genealogical timeframe whose haplogroup formation pre-dates European contact. This has not occurred.
  4. Big-Y DNA matches between Haplogroup O men whose haplogroups were formed in the Americas after the Beringian migration and expansion that scientists agree occurred at least 12-16K years ago, and possibly began earlier. Earlier human lineages, if they existed, may not have survived. A later Inuit and Na-Dené speaker circumpolar migration occurred 4-7K years ago. This has not occurred.
  5. Big-Y DNA matches with men whose most recent common ancestor haplogroup formation dates connect them with continental populations in other locations, outside of North and South America. This would preclude their presence in the Americas after the migrations that populated the Americas. This has occurred.

The Beringian migration took place across a now-submerged land bridge connecting the Chutkin Peninsula in Russia across the Bering Strait with the Seward Peninsula in Alaska.

By Erika Tamm et al – Tamm E, Kivisild T, Reidla M, Metspalu M, Smith DG, et al. (2007) Beringian Standstill and Spread of Native American Founders. PLoS ONE 2(9): e829. doi:10.1371/journal.pone.0000829. Also available from PubMed Central., CC BY 2.5, https://commons.wikimedia.org/w/index.php?curid=16975303

Haplogroup O is clearly Native American in some instances, meaning that it occurs in men who are members of or descend from specific Native American tribes or peoples. One man, James Revels, is confirmed in court records as early as 1656. However, ancestors of James Revels fall into category #5, as their upstream parental haplogroup is found in the Pacific islands outside the Americas after the migration period.

Based on available evidence, the introduction of haplogroup O appears to be post-contact. Therefore, haplogroup O is not indigenous to the Americans in the same sense as haplogroups Q and C that are found widespread throughout the Americas in current testers who are tribal members, descendants of tribal members, and pre-contact ancient DNA as mapped in the book, DNA for Native American Genealogy.

Ancient DNA

Haplogroup C is found in both North and South America today, as are these ancient DNA locations.

Haplogroup Q is more prevalent than Haplogroup C, and ancient DNA remains are found throughout North and South America before colonization.

No ancient DNA for Haplogroup O has been discovered in the Americas. We do find contemporary haplogroup O testers in regional clusters, which we will analyze individually.

Let’s take a look at what we have learned recently.

Wesley Revels’ Lineage

Wesley Revels was the initial Y-DNA tester whose results identified Haplogroup O as Native American, proven by a court record. That documentation was critical, and we are very grateful to Wesley for sharing both his information and results.

Wesley’s ancestor, James Revels, was Native American, born about 1656 and bound to European planter, Edward Revell. James was proven in court to be an Accomack “Indian boy” from “Matomkin,” age 11 in 1667. James was bound, not enslaved, until age 24, at which time he was to be freed and receive corn and clothes.

James had died by 1681 when he was named several times in the Accomack County records as both “James, an Indian” and “James Revell, Indian,” in reference to his estate. James lived near Edward Revell, his greatest creditor and, therefore, administrator of his estate, and interacted with other Indian people near Great Matompkin Neck. Marie Rundquist did an excellent job of documenting that here. Additional information about the Revels family and Matomkin region can be found here.

The location where Edward Revell lived, Manokin Hundred, was on the water directly adjacent the Great Matomkin (now Folly Creek) and Little Matomkin Creeks, inside the Metomkin Inlet. The very early date tells us that James Revels’s paternal ancestor was in the colonies by 1656 and probably born about 1636, or perhaps earlier.

Lewis and Revels men are later associated with the Lumbee Tribe, now found in Robeson and neighboring counties in North Carolina. The Lewis line descends from the Revels lineage, as documented by Marie and Wesley. Other men from this line have tested and match on lower-level STR markers, but have not taken the much more granular and informative Big-Y test.

Until recently, the men who matched Wesley Revels closely on the Big-Y test were connected with the Revels line and/or the Lumbee.

Wesley has a 37-marker STR match to a man with a different surname who had not tested beyond that level, in addition to several 12-marker STR matches to men from various locations. Men who provided known ancestral or current locations include one from Bahrain, two from the Philippines, and three from China. Those men have not taken the Big-Y, and their haplogroups are all predicted from STR results to O-M175 which was formed in Asia about 31,000 years ago.

12-marker matches can reach thousands of years back in time. Unless the matches share ancestors and match at higher levels, 12-marker matches are only useful for geographic history, if that. The Big Y-700 test refines haplogroup results and ages from 10s of thousands of years to (generally) within a genealogically relevant timeframe, often within a couple hundred years.

One of Wesley’s STR matches, Mr. Luo, has taken a Big Y-700 test. Mr. Luo descends directly from Indonesia in the current generation and is haplogroup O-CTS716, originating about 244 BCE, or 2244-ish years ago. Mr. Luo does not match Wesley on the Big-Y test, meaning that Wesley and Mr. Luo have 30 or more SNP differences in their Big-Y results, which equates to about 1,500 years. The common ancestor of Wesley Revels and Mr. Luo existed more than 1,500 years ago in Indonesia. It’s evident that Mr. Luo is not Native American, but his location is relevant in a broader analysis.

There is no question that Wesley’s ancestor, James Revels, was Native American based on the court evidence. There is also no question that the Revels’ paternal lineage was not in the Americas with the Native American migration group 12-16K years ago.

The remaining question is how and when James Revels’ haplogroup O ancestor came to be found on the Atlantic seaboard in the early/mid 1600s, only a few years after the founding of Jamestown.

The results of other Haplogroup O men may help answer this question.

Mr. Lynn

Another haplogroup O man, Mr. Lynn, matches Wesley on STR markers, but not on the Big-Y test.

Mr. Lynn identified his Y-DNA line as Native American, although he did not post detailed genealogy. More specifically, we don’t know if Mr. Lynn identified that he was Native on his paternal line because he matches Wesley, or if the Native history information was passed down within his family, or from genealogical research. Mr. Lynn could also have meant generally that he was Native, or that he was Native “on Dad’s side,” not specifically his direct patrilineal Y-line.

Based on Mr. Lynn’s stated Earliest Known Ancestor (EKA) and additional genealogical research performed, his ancestor was John Wesley Lynn (born approximately 1861, died 1945), whose father was Victor Lynn. John’s death certificate, census, and his family photos on Ancestry indicate that he was African American. According to his death certificate, his father, Victor Lynn, was born in Chatham Co., NC, just west of Durham.

Family members are found in Baldwin Township, shown above.

I did not locate the family in either the 1860 or 1870 census. In 1860, the only Lynn/Linn family in Chatham County was 50-year-old Mary Linn and 17-year-old Jane, living with her, presumably a daughter. Both are listed as “mulatto” (historical term) with the occupation of “domestic.” They may or may not be related to John Wesley Lynn.

In 1870, the only Linn/Lynn in Chatham County is John, black, age 12 or 13 (so born in 1857 or 1858), farm labor, living with a white family. This is probably not John Wesley Lynn given that he is found with his mother in 1880 and the ages don’t match.

In 1880. I find Mary Lynn in Chatham County, age 48, single, black, with daughter Eliza Anne, 20, mulatto, sons John Wesley, 14 so born about 1866, and Charles 12, both black. Additionally, she is living with her nieces and nephews, Cephus, black, 12, Lizzie, 7, mulatto, Malcom, 4, mulatto, William H, 3, mulatto (I think, written over,) and John age 4, mulatto. The children aged 12 and above are farm labor.

In 1880, I also find Jack Lynn, age 28, black, married with 3 children, living beside William Lynn, 25, also married, but with no children.

Trying to find the family in 1870 by using first name searches only, I find no black Mary in 1870 or a mulatto Mary with a child named Jack or any person named Cephus by any surname. I don’t find Jack or any Lynn/Linn family in Chatham County.

The 1890 census does not exist.

In the 1900 census, I find Wesley Lynn in Chatham County, born in January of 1863, age 37, single, a boarder working on the farm of John Harris who lives beside Jack Lynn, age 43, born in April of 1857. Both Lynn men are black. I would assume some connection, given their ages, possibly or probably brothers.

In 1940, John Wesley Lynn, age 74, negro (historical term), is living beside Victor Lynn, age 37, most likely his son.

I could not find Victor Lynn, John Wesley Lynn’s father in any census, so he was likely deceased before 1880 but after 1867, given that Mary’s son Charles Lynn was born in 1868, assuming Mary’s children had the same father. The fact that Mary was listed as single, not married nor widowed suggests enslavement, given that enslaved people were prohibited from legally marrying.

About the only other assumption we can make about Victor Sr. is that he was probably born about 1832 or earlier, probably in Chatham County, NC based on John Wesley’s death certificate, and he was likely enslaved.

Subclades of Haplogroup O

Both the Revels and Lynn men are subclades of haplogroup O and both claim Native heritage – Wesley based on the Revels genealogy and court documents, and Mr. Lynn based on the Native category he selected to represent his earliest known paternal ancestor at FamilyTreeDNA.

Both men have joined various projects, including the American Indian Project, which provides Marie and me, along with our other project co-administrators, the ability to work with and view both of their results at the level they have selected.

How Closely Related Are These Haplogroup O Men?

How closely related are these two men?

By Viajes_de_colon.svg: Phirosiberiaderivative work: Phirosiberia (talk) – Viajes_de_colon.svg, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=8849049

  • Do the haplogroups of the Revels men and Mr. Lynn converge in a common ancestor in a timeframe BEFORE colonialization, meaning before Columbus “discovered” the Caribbean islands when colonization and the slave trade both began?
  • Do the haplogroups converge on North or South American soil or elsewhere?
  • Is there anything in the haplogroup and Time Tree information that precludes haplogroup O from being Native prior to the era of colonization?
  • Is there anything that confirms that a haplogroup O male or males were among the groups of indigenous people that settled the Americas sometime between 12 and 26 thousand years ago? Or even a later panArctic or circumpolar migration wave?

Haplogroup O is well known in East Asia, Indonesia, and the South Pacific.

Another potential source of haplogroup O is via Madagascar and the slave trade.

The Malagasy Roots Project has several haplogroup O individuals, including the Lynn and Revels men, who may have joined to see if they have matches. We don’t know why the various haplogroup O men in the project joined. Other haplogroup O men in the project may or may not have proven Malagasay heritage.

Information provided by the project administrators is as follows:

The people of Madagascar have a fascinating history embedded in their DNA. 17 known slave ships came from Madagascar to North America during the Transatlantic Slave Trade. As a result, we find Malagasy DNA in the African American descendants of enslaved people, often of Southeast Asian origin. One of the goals of this project is to discover the Malagasy roots of African Americans and connect them with their cousins from Madagascar. Please join us in this fascinating endeavor. mtDNA Haplogroups of interest include: B4a1a1b – the “Malagasy Motif”, M23, M7c3c, F3b1, R9 and others Y-DNA Haplogroups include: O1a2 – M50, O2a1 – M95/M88, O3a2c – P164 and others

Resources:

http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2987306/  http://www.ncbi.nlm.nih.gov/pmc/articles/PMC1199379/  http://mbe.oxfordjournals.org/cgi/pmidlookup?view=long&pmid=19535740  http://www.biomedcentral.com/1471-2156/15/77  http://www.biomedcentral.com/1471-2164/10/605

The Malagasy group only has one other man who is haplogroup O and took the Big-Y test, producing haplogroup O-FTC77008. Of course, we don’t know if he has confirmed Madagascar ancestry, and his haplogroup is quite distant from both Revels and Lynn in terms of when his haplogroup was formed.

Viewing the Malagasy Project’s Group Time Tree, above, the common ancestor between those three men lived about 28K BCE, or 30,000 years ago.

Haplogroup O Project Group Time Tree

The Haplogroup O Project Time Tree provides a better representation of haplogroup O in general given that it has a much wider range of samples.

On this tree, I’ve labeled the haplogroup formation dates, along with the Revels/Lewis line which descends from O-FT45548. This haplogroup includes one additional group member whose surname is locked, as he hasn’t given publication permission. The haplogroup formation date of 1766 occurs approximately 85 years after James Revel’s birth, so is attributable to some, but not all of his descendants. At least one descendant falls into the older Haplogroup O-BY60500.

The common ancestor of all three, meaning Revels, Lewis, and the man whose name is locked and does not know his genealogy, is haplogroup O-BY60500, born about 1741.

Their ancestral haplogroup before that, O-FT11768, is much older.

Two Filipino results are shown on and descending from the parent branch of O-FT11768, formed about 3183 BCE, or about 5183 years ago. This tells us that the ancestors of all these men were in the same place, most likely the Philippines, at that time.

3183 BCE (5180 years ago) is well after the Native American migration into the Americas.

Discover Time Tree

Obviously, not every tester joins a project, so now I’m switching to the Discover Time Tree which includes all Y-DNA haplogroup branches. Their common haplogroup, O-FT11768, has many branches, not all of which are shown below. I’m summarized unseen branch locations at bottom left.

Expanding the Time Tree further to view all of the descendant haplogroups of O-FT11768, we see that this was a major branch with many South Pacific results, including the branch of O-FT22410, bracketed in red, which has three members.

One is Mr. Lynn whose feather indicates Native American as his EKA country selection, one is a man whose ancestor is from Singapore, and one is an unknown individual who did not enter his ancestor’s country of origin.

Geography

Wesley’s STR match list, which can reflect matches further back in time than the Big-Y test, includes islands near Singapore. This geography aligns with what is known about haplogroup O.

The distance between this Asian region and continental America, 9000+ miles distant by air, is remarkable and clearly only navigable at that time by ship, meaning ships with experienced crew, able to navigate long distances with supplies and water.

We know that in 760 CE, about 1240 years ago, Mr. Lynn’s haplogroup O-F24410 was formed someplace in the South Pacific – probably in Malaysia or a nearby island. This region, including the Philippines, is home to many haplogroup O men. The majority of haplogroup O is found in Asia, the South Pacific, and Diaspora regions.

We know that Hawaii was populated by Polynesian people about 1600 years ago, prior to the age of colonization. Hawaii is almost 7000 miles from Singapore.

Here’s the challenge. How did these haplogroup O men get from the South Pacific to Virginia? Mr. Lynn and the Singapore tester share a common ancestor about 1240 years ago, or 760 CE.

There is no known or theorized Native American settlement wave across Beringia as late as 760 CE. We know that the parent haplogroup was someplace near Singapore in approximately 760 CE.

Two Filipino men and the Revels’ ancestors were in the same location in the Pacific Islands 5180 years ago. How did they arrive on the Eastern Shore in Virginia, found in the Native population, either in or before 1656 when James Revels was born?

What happened in the 3500 years between those dates that might explain how James Revel’s ancestor made that journey?

Academic Papers

In recent years, there has been discussion of possible shoreline migration routes along the Russian coast, Island hopping along Alaska, Canada, and what is now the US, known as the Kelp Highway or Coastal Migration Route – but that has yet to be proven.

Even if that is the case, and it’s certainly a possibility, how did this particular group of men get from the Pacific across the continent to the Atlantic shore in such a short time, leaving no telltale signs along the way? The Coastal Migration Theory hypothesis states that this migration occurred from 12-16 thousand years ago, and then expanded inland over the next 3-5K years. They could not have expanded eastward until the glaciers receded. Regardless, the parent haplogroup and associated ancestors are still found in the Philippines and South Pacific 5000 years ago – after that migration and expansion had already occurred.

The conclusion of the paper is that there is no strong evidence for a Pacific shoreline migration. Regardless, that’s still thousands of years before the time range we’re observing.

We know that the Lynn ancestor was with men from Indonesia in 760 CE, and the Revels ancestor was with men from the Pacific Islands, probably the Philippines, 5180 years ago. They couldn’t have been in two places at the same time, so the ancestors of Revels and Lynn were not in the Americas then.

A 2020 paper shows that remains from Easter Island (Rapa Nui) show Native American DNA, and suggests that initial contact occurred between the two cultures about 1200 CE, or about 800 years ago, but there is not yet any pre-contact or post-contact ancient Y-DNA found in the Americas that shows Polynesian DNA. Furthermore, the hypothesis is that the DNA found on Easter Island came from the Americas, not vice versa. The jury is still out, but this does show that trans-Pacific contact between the two cultures was taking place 800 years ago, at least two hundred years pre-European contact.

Australasian migration to South America is also suggested by one set of remains found in Brazil dating from more than 9000 years ago, but there have been no other remains found indicating this heritage, either in Brazil, or elsewhere in the Americas.

Based on the Time Tree dates of the Haplogroup O testers in our samples, we know they were in the Islands of Southeast Asia after this time period. Additionally, there are no Australia/New Zealand matches.

The Spanish

The Spanish established an early trade route between Manila and Acapulco beginning in 1565. Consequently, east Asian men left their genetic signature in Mexico, as described in this paper.

Historians estimate that 40-129K immigrants arrived from Manilla to colonial Mexico between 1565 and 1815, with most being enslaved upon arrival. Approximately one-third of the population in Manilla was already enslaved. Unfortunately, this paper focused only on autosomal genome-wide results and did not include either Y-DNA, nor mitochondrial. However, the paper quantifies the high degree of trade, and indicates that the Philippines and other Asian population haplotypes are still prevalent in the Mexican population.

In 2016, Dr. Miguel Vilar, the lead scientist with the National Geographic Genographic project lectured in Guam about the surprising Native American DNA found in the Guam population and nearby islands. He kindly provided this link to an article about the event.

Guam was colonized by Spain. In the image from the Boxer Codex, above, the local Chamorro people greet the Manila Galleon in the Ladrones Islands, as the Marianas were called by the Spanish, about 1590.

Native Hawaiians descend from Polynesian ancestors who arrived in the islands about 400 CE, or about 1600 years ago. Captain Cook, began the age of European contact in Hawaii in 1778.

Five Possibilities

There are five possible origins of haplogroup O in the Americas.

  • Traditional migration across Beringia with the known migrations, estimated to have occurred about 12-16K years ago.
  • A Kelp Highway Coastal Migration which may have occurred about 12-16K years ago and dispersed over the next 3-5K years.
  • Circumpolar migration – specifically Inuit and Na-Dene speakers, about 4-6K years ago.
  • Post-contact incorporation from the Pacific Islands resulting from shipping trade on colonial era ships sometime after 1565.
  • Post-contact incorporation from Madagascar resulting from the importation of humans who may or may not have been enslaved upon arrival.

Do we have any additional evidence?

Other Haplogroup O DNA

From my book, DNA for Native American Genealogy:

Testers in haplogroup O-BY60500 and subclade O-FT45548 have proven Native American heritage.

We have multiple confirmed men from a common ancestor who is proven to be an enslaved Accomack “Indian boy,” James Revell, born in 1656, “belonging to the Motomkin” village, according to the Accomack County, Virginia court records. These men tested as members of haplogroup O-F3288 initially, after taking the Big Y-500 test. However, upgrading to the Big Y-700 produced more granular results and branches reflecting mutations that occurred since their progenitor was born in 1656.

Unfortunately, other than known descendants, these men have few close Y-DNA or Big Y-700 matches.

Without additional men testing from different unrelated lines, or ancient haplogroup O being discovered, we cannot confirm that this haplogroup O male’s ancestor was not introduced into the Matomkin Tribe in some way post-contact. Today, one descendant from this line is a member of the Lumbee Tribe.

However, that isn’t the end of the haplogroup O story.

The Genographic Project data shows one Haplogroup O Tlingit tribal member from Taku, Alaska, along with several testers from Mexico that indicate their paternal line is indigenous. Some people from Texas identify their paternal line as Hispanic.

Another individual indicates they were born on the Fountain Indian Reserve, in British Columbia and speaks the St’at’imcets language, an interior branch of Coastal Salish.

Haplogroup O has been identified as Native American in other locations as well.

Much of the information about Haplogroup O testers was courtesy of the Genographic Project, meaning we can’t contact those people to request upgraded tests, and we can’t obtain additional information in addition to what they provided when they tested. As an affiliate researcher, I’m very grateful to the National Geographic Society’s Genographic project for providing collaborative data.

When the book was published, the Discover Time Tree had not yet been released. We have additional information available today, including the dates of haplogroup formation.

FamilyTreeDNA Haplotree and Discover

The FamilyTreeDNA Haplotree (not to be confused with the Discover Time Tree) shows 10 people at the O-M175 level in Mexico, 10 people in the US report Native American heritage, 2 in Jamaica, and one each in Peru, Panama, and Cuba. There’s also one tester from Madagascar.

Altogether, this gives us about 35 haplogroup O males in the Americas, several with Native heritage.

Please note that I’ve omitted Hawaii in this analysis and included only North and South America. The one individual selecting Native Hawaiian (Kanaka Maoli) is in haplogroup O-M133.

Let’s look at our three distinct clusters.

Cluster 1 – Pacific Northwest – Alaska and Canada

We have a cluster of three individuals along the Pacific Coast in Alaska and Canada who have self-identified as Native, provided a tribal affiliation, and, in some cases, the spoken language.

How might haplogroup O have arrived in or near Vancouver, Washington? We know that James Cook “discovered” Hawaii in 1778, naming it the Sandwich Islands. By 1787, a female Hawaiian died en route to the Pacific Northwest, and the following year, a male arrived. Hawaii had become a provisioning stop, and the Spanish took Hawaiians onto ships as replacement workers.

Hawaiian seamen, whalers, and laborers began intermarrying with the Native people along the West Coast as early as 1811. Their presence expanded from Oregon to Alaska. Migration and intermarriage along the Pacific coast began slowly, but turned into a steady stream 30 years later when we have confirmed recruitment and migration of Hawaiian people

In 1839, John Sutter recruited a small group of 10 Hawaiians to travel with him to the then-Mexican colony of Alta, California.

By the mid-1800s, hundreds of Hawaiians lived in Canada and California. In 1847, it was reported that 10% of San Francisco’s residents were Hawaiian. Some of those people integrated with the Native American people, particularly the Miwok and Maidu. The village of Verona, California was tri-lingual: Hawaiian, a Native language, and English, and is today the Sacramento-Verona Tribe.

This article provides a history of the British Company who administered Fort Vancouver, near Vancouver, Washington, that included French-Canadians, Native Americans and Hawaiians. In 1845, 119 Hawaiians were employed at the fort. One of the 119, Opunuia, had signed on as an “engagé,” meaning some type of hired hand or employee, with the Hudson Bay Company for three years, after which he would be free to return home to Honolulu or establish himself in the Oregon Country. He married a woman from the Cascade Tribe.

The descendants of the Hawaiian men and Native women were considered tribal members. In most tribes, children took the tribal status and affiliation of the mother.

The Taku and Sitka, Alaska men on the map are Tlingit, and the man from British Columbia is from the Fountain Indian Reserve.

Hawaiian recruitment is the most likely scenario by which haplogroup O arrived in the tribes of the Pacific Northwest. In that sense, haplogroup O is indeed Native American but not indigenous to that region. The origins of haplogorup O in the Pacific Northwest are likely found in Hawaii, where it is indigenous, and before that, Polynesia – not due to a Beringian crossing.

Cluster 2 – Mexico

We find a particularly interesting small cluster of 4 haplogroup O individuals in interior Mexico.

In the 1500s, Spain established a trade route between Mexico and Manilla in the Philippines.

In 1564, four ships left Mexico to cross the Pacific to claim Guam and the Philippines for King Philip II of Spain. The spice trade, back and forth between Mexico and the Philippines began the following year and continued for the next 250.

Landings occurred along the California coast and the western Mexican coastline. The majority of the galleon crews were Malaysian and Filipino who were paid less than the Spanish sailors. Slaves, including people from the Marianas were part of the lucrative cargo.

One individual in Texas reports haplogroup O and indicates their paternal ancestors were Hispanic/Native from Mexico. A haplogroup O cluster claiming Native heritage is found near Zacatecas, Fresnillo and San Luis Potosi in central Mexico. Additionally, mitochondrial haplogroup F, also Asian, is found there as well. Acapulco is the lime green pin.

An additional haplogroup O tester with Native heritage is found in Lima, Peru.

Haplogroup O men are found in Panama, Jamaica and Cuba, but do not indicate the heritage of their paternal ancestral line. None of these men have taken Big-Y tests, and some may well have arrived on the slave ships from Madagascar, especially in the Caribbean. This source attributes some enslaved people in Jamaica to Hawaiian voyages.

I strongly suspect that the Mexican/Peru grouping in close proximity to the Pacific coastline is the result of the Manilla-Mexico 250-year trade route. The Spanish also plied those waters regularly. Big Y testing of those men would help flesh-out their stories – when and how haplogroup O arrived in the local population.

Cluster 3 – East Coast

At first glance, the East Coast grouping of men with a genetic affinity to the people of the Philippines and Indonesia seems more difficult to explain, but perhaps not.

On the East Coast, we have confirmed reports of whalers near Nantucket as early as 1765 utilizing crewmen from Hawaii, known then as the Sandwich Islands, Tahiti, and the Cape Verde Islands off of Africa. A thorough review of early literature might well reveal additional information about early connections with the Sandwich Islands, and in particular, sailors, crew, or enslaved people.

The Spanish and French were the first to colonize the Philippines by the late 1500s. They had discovered the Solomon Islands, Melanesia, and other Polynesian Islands, and by the early 1600s, the Dutch were involved as well.

The Encyclopedia Britanica further reports that Vasco Balboa first sailed into the Pacific in 1513 and seven years later, Ferdinand Magellan rounded the tip of South America. The Spanish followed, establishing a galley trade between Manila, in the Philippines and Acapulco in western Mexico.

While I found nothing specific stating that the earliest voyages brought men from the Philippines and Oceania back to their European home ports with them, we know that early European captains on exploratory voyages took Native people from the east coast of the Americas on their return journey, so there’s nothing to preclude them from doing the same from the Pacific. The early explorers stayed for months among the Oceanic Native peoples. If they were short on sailors for their return voyage, Polynesian men filled the void.

We know that the Spanish took slaves as part of their trade. We know that the ships in the Pacific took sailors from the islands. If the men themselves didn’t stay in the locations they visited, it’s certainly within the realm of possibility that they fathered children with local, Native women. Furthermore, given that the slave trade was lucrative, it’s also possible that some Pacific Island slaves were taken not as crew but with the intention of being sold into bondage. Other men may have escaped the ships and hidden among the Native Tribes along the eastern seaboard.

Fishing in Newfoundland and exploration in what would become the US was occurring by 1500, so it’s certainly possible that some of the indigenous people from Indonesia and the Philippines were either stranded, sold to enslavers, escaped, or chose to join the Native people along the coastline in North America. Ships had to stop to resupply rations and take on fresh water.

We know that by the mid-1600s, James Revels, whose father carried haplogroup O, had been born on the Atlantic coast of Virginia or Maryland, probably on the Delmarva Peninsula, short for Delaware, Maryland, Virginia, where the Accomac people lived.

There are other instances of haplogroup O found along the east coast.

On the eastern portion of the haplogroup O map from the book, DNA for Native American Genealogy, we find the following locations:

  • Hillburn, NY – man identified as “Native American Black.”
  • Chichester County, PA – Genographic tester identified the location of his earliest known ancestor – included here because O is not typically found in the states.
  • Accomack County, VA – Delmarva peninsula – James Revels lineage
  • Robeson County, NC – Lewis and Revels surname associated with the Lumbee
  • Chatham County, NC – Lynn ancestor’s earliest known location
  • Greene County, NC – enslaved Blount ancestor’s EKA in 1849

The genesis of Mr. Blount’s enslaved ancestor is unclear. Fortunately, he took a Big Y-700 test.

Mr. Blount’s only Big-Y match is to a man from the United Arab Emirates (UAE), but the haplogroup history includes Thailand, which is the likely source of both his and his UAE matches’ ancestors at some point in time. Their common ancestor was in Thailand in 336 CE, almost 1700 years ago.

All surrounding branches of haplogroup O on the Time Tree have Asian testers, except for the one UAE gentleman.

The Blount Haplogroup O-FTC77008 does not connect with the common ancestral haplogroup of Lynn and Revels, so these lineages are only related someplace in Oceana prior to O-F265, or more about  30,000 years ago. Their only commonality other than their Asian origins is that they arrived on the East Coast of the Americas.

We know that the Spanish were exploring the Atlantic coastline in the 1500s and were attempting to establish colonies. In 1566, a Spanish expedition reached the Delmarva Peninsula. This spit of land was contested and changed hands several times, belonging variously to the Spanish, Dutch, and British by 1664.

Furthermore, we also know that the ships were utilizing slave labor. One of the Spanish ships wrecked in the waters off North Carolina near Hatteras or Roanoke Island before the Lost Colony was abandoned on Roanoke Island in 1587. The Croatan Indians reported that in memorable history, several men, some of whom were reported to be slaves, had survived the wreck and “disappeared” into the hinterlands – clearly running for their lives.

These men, if they survived, would have been incorporated into the Native population as there were no other settlements at the time. Variations of this scenario may have played out many times.

James Revels’ ancestor could have arrived on any ship, beginning with exploration and colonization in the early 1500s through the mid-1650s.

By the time the chief bound the Indian boy who was given the English name James to Edward Revell, James’s Oceanic paternal ancestor could have been 4, 5 or 6 generations in the past – or could have been his father.

The Accomack was a small tribe, loosely affiliated with the Powhatan Confederacy along the Eastern Shore. By 1700, their population had declined by approximately 90% due to disease. A subgroup, the Gingaskins, intermarried with African Americans living nearby. After Nat Turner’s slave rebellion of 1831, they were expelled from their homelands.

The swamps near Lumberton in Robeson County, NC, became a safe haven for many mixed-race Native, African, and European people. The swamps protected them, and they existed, more or less undisturbed, for decades. Revels and Lewis descendants are both found there.

Many Native Americans were permanently enslaved alongside African people – and within a generation or so, their descendants knew they were Native and African, but lost track of which ancestors descended from which groups. Life was extremely difficult back then. Generations were short, and enslaved people were moved from place to place and sold indiscriminately, severing their family ties entirely, including heritage stories.

Returning to the Discover Time Tree Maps

Wesley Revels has STR matches with several men from Indonesia, China, and the Philippines. It would be very helpful if those men would upgrade to the Big Y-700 so that we can more fully complete the haplogroup O branches of the Time Tree.

The common Revels/Lewis ancestor, accompanied by two descendant men on different genetic branches from the Philippines, was born about 5180 years ago. There is no evidence to suggest Haplogroup O-FT11768 was born anyplace other than in the Philippines.

How did the descendant haplogroups of O-FT45548 (Revels, Lewis, and an unnamed man) and O-F22410 (Lynn) arrive in Virginia or anyplace along the Atlantic seaboard?

Hawaii wasn’t settled until about 1600 years ago. We know Hawaiians integrated with the Pacific Coast Native tribes in the 1800s, but James Revels was in Virginia in 1656..

We know that the Spanish established a mid-1500s trade route between Manila and Acapulco, leaving their genetic signature in western Mexico.

None of these events fit the narrative for the Revels or the Lynn paternal ancestor.

Furthermore, the Revels and Lynn lines do not connect on North American soil, as both descend from the same parent haplogroup, O-FT11768, 5180 years ago in the Philippines. This location and history suggest a connection with the Spanish galleon trade era. The haplogroup formation clearly predates that trade, which means those men were still in the Philippines, not already living on the American continents. Therefore, the descendants of the haplogroup O-FT11768 arrived in Virginia and North Carolina sometime after that haplogroup formation 5100 years ago.

The Lynn ancestor connects with a man from Singapore in 760 CE, or just 1240 years ago. A descendant of haplogroup O-F22410 arrived in North Carolina sometime later.

It does not appear, at least not on the surface, that there is a connection through Madagascar, although we can’t rule that out without additional testers. If the connection is through Madagascar, then their ancestors were likely transported from Indonesia to Madagascar, then as enslaved people from Madagascar to the Atlantic colonies to be sold. However, James Revels was not enslaved. He was clearly Native and bound to a European plantation owner, who did, in fact, free him as agreed and subsequently loaned him money.

Based on the dates involved, and when we know they were in Oceania, an arrival along the west coast, followed by a quick migration across the country to a peninsula of land in the Atlantic, is probably the least likely scenario. There is also no historical or ancient haplogroup O DNA found anyplace between the west and east coasts, nor in the Inuit or Na-Dene speakers. The Navajo, who speak the Na-Dené language, migrated to the Southwest US around 1400 CE, but haplogroup O has not been found among Na-Dené speakers.

It’s a long way from Singapore and the Philippines to Madagascar, so while the coastal migration scenario is not impossible, it’s also not probable, especially given what we know about the Spanish Pacific trade that existed profitably for 250 years.

However, one haplogroup O subgroup arrived in the UAE by some methodology after 336 CE.

It’s entirely possible, indeed probable, that haplogroup O arrived in the Americas for various reasons, on different paths, in different timeframes.

Haplogroup O was found in people in the Americas after colonization had begun. There has been no ancient Haplogroup O DNA discovered, and there’s evidence indicating that these instances of haplogroup O could not have arrived in any of the known Beringia migrations nor the theorized Coastal or Kelp migration. We know the East Coast Cluster is not a result of the West Coast 19th-century migration because James Revels was in court one hundred and fifty years before the Hawaiians were living among the Native people along the Pacific coastline.

There’s nothing to indicate that the Mexican group that likely arrived beginning in the mid-1500s for the next 250 years as a result of the Indonesian trade route migrated to the east coast, or vice versa. That’s also highly unlikely.

The most likely scenario is that Mr. Lynn’s, Mr. Blount’s, and James Revels’ ancestors were brought on trade ships, either as sailors or enslaved men. They may not have stayed, simply visited. They may each have arrived in a completely different scenario, meaning Mr. Blount’s ancestors could have been enslaved arrivals from Madagascar, Mr. Lynn’s from Indonesia, and Mr. Revel’s as a crew member on a Spanish ship. We simply don’t know.

James Revels’ descendants were Native through his mother’s tribe, as confirmed in the 1667 court records. However, the Revels and Lynn lineages weren’t Native as a result of their paternal haplogroup O ancestors crossing Beringia into the Americas with Native American haplogroups Q and C. Instead, the Lynn and Revels migration story is quite different. Their ancestors arrived by ship. The journey was long, perilous, and far more unique than we could have imagined, taking them halfway around the world by water.

Timeline

There’s a lot of information to digest, so I’ve compiled a timeline incorporating both genetic and historical information for easy reference.

  • 30,000 years ago (28,000 BCE) – haplogroup O-F265, common Asian ancestor  of Mr. Blount, the Revels/Lewis group, Mr. Lynn, and an unknown Big-Y tester in the Malagasy group project
  • 12,000-16,000 years ago – Indigenous Americans arrived across now-submerged Beringia
  • 12,000-16,000 years ago – possible Coastal Migration route may have facilitated a secondary source of indigenous arrival along the Pacific coastline of the Americas
  • 4000-7000 years ago – circumpolar migration arrival of Inuit and Na-Dené speakers found in the Arctic polar region and the Navajo in the Southwest who migrated from Alaska/Canada about 1400 CE
  • 5180 years ago (3180 BCE) – haplogroup O-FT11768, the common ancestor of Mr. Lynn and the Revels/Lewis group with many subgroups in the Philippines, Hawaii, Singapore, Brunei, China, Sumatra, and Thailand
  • 2244 years ago (244 BCE) – haplogroup O-CTS716, the common ancestor of Wesley Revels and Mr. Luo from Indonesia
  • The year 336 CE, 1684 years ago – haplogroup O-FTC77008, the common ancestor of Mr. Blount, UAE tester and a man from Thailand
  • 400 CE, 1600 years ago  –  Hawaii populated by Polynesian people
  • 760 CE, 1240 years ago – haplogroup O-F22410, common ancestor of Mr. Lynn with a Singapore man
  • 1492 CE, 528 years ago – Columbus begins his voyages to the “New World,” arriving in the Caribbean
  • By 1504 CE – European fishing began off of Newfoundland
  • 1565 – Spain claimed Guam and the Philippines
  • 1565 – Spanish trade between Manilla and Acapulco begins and continues for 250 years, until 1815, using crews of men from Guam, the Philippines, and enslaved people from the Marianas.
  • 1565 – St. Augustine (Florida) was founded by the Spanish as a base for trade and conquest along the eastern seaboard
  • 1566 – A Spanish expedition reached the Delmarva peninsula intending to establish a colony, but bad weather thwarted that attempt.
  • 1585-1587 – voyages of discovery by the English and the Lost Colony on Roanoke Island, North Carolina
  • 1603 – English first explored the Delmarva Peninsula, home to the Accomac people, now Accomack County, VA, where James Revels’s court record was found in 1667
  • 1607 – Jamestown, Virginia, founded by the English
  • 1608 – Colonists first arrived on the Delmarva Peninsula and allied with Debedeavon, whom they called the “laughing King” of the Accomac people. At that time, the Accomac had 80 warriors. Debedeavon was a close friend to the colonists and saved them from a massacre in 1622. He died in 1657.
  • 1620 – The Mayflower arrived near present-day Provincetown, Massachusetts
  • 1631-1638 – Dutch West India Company established a colony on the Delmarva Peninsula, but after conflicts, it was destroyed by Native Americans in 1638. The Swede’s colony followed, and the region was under Dutch and Swedish control until it shifted to British control in 1664
  • 1656 – Birth of James Revels, confirmed in a 1667 court record stating that he was an Accomack “Indian boy” from “Matomkin,” judged to be age 11, bound to Edward Revell. This location is on the Delmarva Peninsula.
  • 1741 CE –  Haplogroup O-BY60500 formation date that includes all of the Revels and Lewis testers who descend from James Revels born in 1656
  • 1765 – Whalers near Nantucket using crewmen from Hawaii (Sandwich Islands), Tahiti, and the Cape Verde Islands off of Africa
  • 1766 CE – Formation date for haplogroup O-FT45548, child haplogroup of O-BY60500, for some of the Lewis and Revels men who all descend from James Revels born in 1656
  • 1778 – Captain Cook makes contact with Hawaiian people
  • 1787 – The first male arrived in the Pacific Northwest from Hawaii
  • 1811 – Hawaiian seamen begin intermarrying with Native American females along the Pacific shore, eventually expanding their presence from Oregon to Alaska
  • 1839 – John Suter recruits Hawaiian men to travel with him to California
  • 1845 – Hawaiians employed by Fort Vancouver, with some marrying Native American women

Conclusions

It’s without question that James Revels was Native American very early in the settlement of the Delmarva Peninsula, now Accomack County, Virginia, but his common ancestor with Filipino men 5100 years ago precludes his direct paternal ancestor’s presence in the Americas at that time. In other words, his Revel male ancestor did not arrive in the Beringian indigenous migration 12,000-16,000 years ago. His ancestor likely arrived post-contact, based on a combination of both historical and genetic evidence.

Haplogroup O is not found in the Arctic Inuit nor the Na-Dene speakers, precluding a connection with either group, and has never been found in ancient DNA in the Americas.

Haplogroup O in the Revels lineage is most likely connected with the Spanish galleon trade with the Philippines and the early Spanish attempts to colonize the Americas.

The source of Haplogroup O in the Pacific Northwest group is likely found in the recruitment of Hawaiian men in the early/mid-1800s.

The Mexican Haplogroup O group likely originated with the Manilla/Mexico Spanish galleon trade.

The source of the Blount Haplogroup O remains uncertain, other than to say it originated in Thailand thousands of years ago and is also found in the UAE. The common Blount, UAE, and Thailand ancestor’s haplogroup dates to 336 CE, so they were all likely in or near Thailand at that date, about 1687 years ago.

What’s Next?

Science continuously evolves, revealing new details as we learn more, often clarifying or shifting our knowledge. Before the Discover tool provided haplogroup ages based on tests from men around the world, we didn’t have the necessary haplogroup origin and age data to understand the genesis of haplogroup O in the Americas. Now, we do, but there is invariably more to learn.

New evidence is always welcome and builds our knowledge base. Haplogroup O ancient DNA findings would be especially relevant and could further refine what we know, depending on the location, dates of the remains, who they match, and historical context.

Additional Big Y-700 tests of haplogroup O men, especially those with known genealogy or ancestor location, including Madagascar, would be very beneficial and allow the haplogroup formation dates to be further refined.

If you are a male with haplogroup O, please consider upgrading to the Big Y-700 test, here.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

New Discover Tool – Compare Haplogroups & More at FamilyTreeDNA

Posted on by
5

FamilyTreeDNA has introduced a great new Y-DNA tool – Compare – as part of Discover. I wrote about how to use Discover, here.

The new Compare feature compares two haplogroups, including where they fall on the haplotree in relationship to each other, time to most recent common ancestor (TMRCA), TimeTree, and more.

It’s easy.

All you do is enter two haplogroups.

Click to enlarge any image

Here’s how.

Enter Haplogroups

You can enter the haplogroups to compare either through your account at FamilyTreeDNA or directly into Discover.

If you’ve signed in and taken any Y-DNA test, you can click through to Discover from your account, or, you can simply navigate to Discover. The Compare feature is publicly available and free, of course.

You can compare any Y-DNA haplogroup with any other haplogroup from your match list, from a project, or just at random.

Let’s say I was viewing the Estes surname project or the Estes project Group Time Tree, and found my ancestor’s lineage. Maybe I don’t know that haplogroup R-M269 is a very common mid-level predicted haplogroup, and I don’t know that R-ZS3700 is only discovered and confirmed via a Big Y-700 test.

I want to compare their haplogroups.

As an excited genealogist, I have questions.

  • How far apart are haplogroup R-ZS3700 and R-M269?
  • Have either or both of these men taken a Big Y test?
  • What commonalities do the two haplogroups have?
  • Does one descend from another?

In this case, I know these haplogroups are found in a specific ancestral cluster in a surname project, but I could compare any two haplogroups at random.

Compare!

Let’s let Compare do its magic.

If you click through to Discover from your Y-DNA page, “you” are the orange profile. Otherwise, the orange profile is the first haplogroup entered.

Compare shows me LOTs of information.

To begin with, you can see which two haplogroups are being compared. This report tells us that R-ZS3700 is a direct descendant of R-M269. By looking at the dates in the little pedigree chart, you can see that R-ZS3700 originated in the year 1700, roughly, and R-M269 in about 4350 BCE, or approximately 6350 years ago.

This tells me, indirectly, that R-ZS3700 has taken a Big Y test, and the R-M269 man has not. The other clue is the message at bottom left encouraging an upgrade. One or both men have not taken the Big Y.

In the center-left, we have the path from ZS3700, the most refined haplogroup, to R-M269 on top, and beneath, the path from R-M269 to Y-Adam.

You can mouse over any of these haplogroups to view a brief description and their age.

There’s still more, though.

At the bottom right, you can see that both of these haplogroups connect to Collin Charvis, with the younger, more refined haplogroup more closely connected, of course.

Both haplogroups have connections to the Allen Ancient Genome Diversity Project out of the Reich lab. Now I’m getting really excited!

Check each haplogroup in Discover for additional information about these ancient and modern connections.

Scrolling down to the bottom of the page, we see the Discover Compare Timeline with the two compared haplogroups.

What About Completely Different Haplogroups?

When haplogroups are entirely different, Discover Compare searches for date and time information, then searches for commonalities.

In this example, the two haplogroups, J-FT1 and I-BY44445, are entirely different. The path to their common, joining haplogroup is shown in the tree at right.

At left, the ancestral path of each is shown, reaching back to their common haplogroup, then, at the bottom, the common haplogroup, IJ-P124 is tracked back to Y-Adam.

Even with these widely divergent haplogroups, both have an Entrepreneur connection, albeit in different haplogroups. The lucky haplogroup J-FT1 person connects with Bennett Greenspan, founder of FamilyTreeDNA.

Both have ancient connections found in Germany as well.

Let’s look at a few more examples.

The commonality between these haplogroup I and R samples is that both have an actor connection, and both have a connection in ancient DNA from a common study.

Of course, reviewing each haplogroup that you’ve compared shows you their individual information. In this case, you can view more about the Salme 2-Õ ancient individual.

You can also google the common study to discover what is known about the location, excavation, and the heritage of the people who lived there.

As I played with this new Compare tool, I found additional categories for Presidential connections, Author connections, Clan connections, and Location connections, such as the US State of Maryland in one case and the country of Hungary in another.

I’ve been asking for some time for a tool to compare haplogroups, so I’m very pleased! FamilyTreeDNA went the extra mile to include additional information.

Your family members who might not be particularly interested in DOING genealogy might be quite interested in this interesting information – and would be glad to let you test their Y-DNA and research genealogy on behalf of your family. Fingers crossed! That’s a win-win for everyone.

FamilyTreeDNA has included a share function in the upper right-hand corner of each page for exactly this reason. Let’s share and get our family members excited about genetic genealogy. The more cousins that test, the more you’ll know, and the more refined the Y-DNA haplotree becomes.

There is probably a lot more to discover, pardon the pun, in the new Compare feature. It was just released today, so I’m sure I haven’t found everything.

Check Compare out with your matches’ or ancestors’ haplogroups, and let me know what fun things you find.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

DNA: In Search Of…Your Grandparents

Posted on by
15

Are you searching for an unknown relative or trying to unravel and understand unexpected results? Maybe you discovered that one or both of your parents is not your biological parent. Maybe one of your siblings might be a half-sibling instead. Or maybe you suddenly have an unexpected match that looks to be an unknown close relative, possibly a half-sibling. Perhaps there’s a close match you can’t place.

Or, are you searching for the identity of your grandparent or grandparents? If you’re searching for your parent or parents, often identifying your grandparents is a necessary step to narrow the parent-candidates.

I’ve written an entire series of “In Search of Unknown Family” articles, permanently listed together, here. They will step you through the search process and help you understand how to unravel your results. If you’re new, reading these, in order, before proceeding, would be a good idea.

Identifying a Grandparent

I saved this “grandparents” article for later in the series because you will need the tools and techniques I’ve introduced in the earlier articles. Identifying grandparents is often the most challenging of any of the relationships we’ve covered so far. In part because each of those four individuals occupies a different place in your tree, meaning their X, Y-DNA and mitochondrial DNA is carried by different, and not all, descendants. This means we sometimes have to utilize different tools and techniques.

If you’re trying to identify any of your four grandparents, females are sometimes more challenging than males.

Why?

Women don’t have a Y chromosome to test. This can be a double handicap. Female testers can’t test a Y chromosome, and maternal ancestors don’t have a Y chromosome to match.

Of course, every circumstance differs. You may not have a male to test for paternal lines either.

The maternal grandfather can be uniquely challenging, because two types of DNA, Y-DNA and mitochondrial DNA matching are immediately eliminated for all testers.

While I’ve focused on the maternal grandfather in this example, these techniques can be utilized for all four grandparents as well as for parents. At the end, I’ll review other grandparent relationships and additional tools you might be able to utilize for each one.

In addition to autosomal DNA, we can also utilize mitochondrial DNA, Y-DNA and sometimes X DNA in certain situations.

Testing, Tests and Vendors

As you recall, only men have a Y chromosome (blue arrow), so only genetic males can take a Y-DNA test. Men pass their Y chromosome from father to son in each generation. Daughters don’t receive a Y chromosome.

Everyone has their mother’s mitochondrial DNA (pink arrow.) Women pass their mitochondrial DNA to both sexes of their children, but only females pass it on. In the current generation, represented by the son and daughter, above, the mother’s yellow heart-shaped mitochondrial DNA is inherited by both sexes of her children. In the current generation, males and females can both test for their mother’s mitochondrial DNA.

Of course, everyone has autosomal DNA, inherited from all of their ancestral lines through at least the 5th or 6th generation, and often further back in time. Autosomal DNA is divided in half in each generation, as children inherit half of each parents’ autosomal DNA (with the exception of the X chromosome, which males only inherit from their mother.)

The four major vendors, Ancestry, 23andMe, FamilyTreeDNA and MyHeritage sell autosomal DNA tests, but only FamilyTreeDNA sells Y-DNA and mitochondrial DNA tests.

Only 23andMe and FamilyTreeDNA report X matching.

All vendors except Ancestry provide segment location information along with a chromosome browser.

You can read about the vendor’s strengths and weaknesses in the third article, here.

Ordering Y and Mitochondrial DNA Tests

If you’re seeking the identities of grandparents, the children and parents, above, can test for the following types of DNA in addition to autosomal:

Person in Pedigree Y-DNA Mitochondrial
Son His father’s blue star His mother’s pink heart
Daughter None Her mother’s pink heart
Father His father’s blue star His mother’s gold heart
Mother None Her mother’s pink heart

Note that none of the people shown above in the direct pedigree line carry the Y-DNA of the green maternal grandfather. However, if the mother has a full sibling, the green “Male Child,” he will carry the Y-DNA of the maternal grandfather. Just be sure the mother and her brother are full siblings, because otherwise, the brother’s Y-DNA may not have been inherited from your mother’s father. I wrote about full vs half sibling determination, here.

Let’s view this from a slightly different perspective. For each grandparent in the tree, which of the two testers, son or daughter, if either, carry that ancestor’s DNA of the types listed in the columns.

Ancestor in Tree Y-DNA Mitochondrial DNA Autosomal DNA X DNA
Paternal Grandfather Son Neither Son, daughter Neither
Paternal Grandmother Has no Y chromosome None (father has it, doesn’t pass it on to son or daughter) Son, daughter Daughter (son does not receive father’s X chromosome)
Maternal Grandfather Neither Neither Son, daughter Son, daughter (potentially)
Maternal Grandmother Has no Y chromosome Son, daughter Son, daughter Son, daughter (potentially)

Obtaining the Y-DNA and mitochondrial DNA of those grandparents from their descendants will provide hints and may be instrumental in identifying the grandparent.

FamilyTreeDNA

You’ll need to order Y-DNA (males only) and mitochondrial DNA tests separately from autosomal DNA tests. They are three completely different tests.

At FamilyTreeDNA, the autosomal DNA test is called Family Finder to differentiate it from their Y-DNA and mitochondrial DNA tests.

Their autosomal test is called Family Finder whether you order a test from FamilyTreeDNA, or upload your results to their site from another vendor (instructions here.)

I recommend ordering the Big Y-700 Y-DNA test if possible, and if not, the highest resolution Y-DNA test you can afford. The Big Y-700 is the most refined Y-DNA test available, includes multiple tools and places Big Y-700 testers on the Time Tree through the Discover tool, providing relatively precise estimates of when those men shared a common ancestor. If you’ve already purchased a lower-precision Y-DNA test at FamilyTreeDNA, you can easily upgrade.

I wrote about using the Discover tool here. The recently added Group Time Tree draws a genetic Y-DNA tree of Big-Y testers in common projects, showing earliest known ancestors and the date of the most recent common ancestor.

You need to make sure your Family Finder, mitochondrial DNA and Y-DNA (if you’re a male) tests are ordered from the same account at FamilyTreeDNA.

You want all 3 of your tests on the same account (called a kit number) so that you can use the advanced search features that display people who match you on combinations of multiple kinds of tests. For example, if you’re a male, do your Y-DNA matches also match you on the autosomal Family Finder test, and if so, how closely? Advanced matching also provides X matching tools.

X DNA is included in autosomal tests. X DNA has a distinct matching pattern for males and females which makes it uniquely useful for genealogy. I wrote about X DNA matching here.

If you upload your autosomal results to FamilyTreeDNA from another company, you’re only uploading a raw DNA file, not the DNA itself, so FamilyTreeDNA will need to send you a swab kit to test your Y-DNA and mitochondrial DNA. If you upload your autosomal DNA, simply sign in to your kit, purchase the Y-DNA and/or mitochondrial DNA tests and they will send you a swab kit.

If you test directly at FamilyTreeDNA, you can add any test easily by simply signing in and placing an order. They will use your archived DNA from your swab sample, as long as there’s enough left and it’s of sufficient quality.

Fish In All Ponds

The first important thing to do in your grandparent search is to be sure you’re fishing in all ponds. In other words, be sure you’ve tested at all 4 vendors, or uploaded files to FamilyTreeDNA and MyHeritage.

When you upload files to those vendors, be sure to purchase the unlock for their advanced tools, because you’re going to utilize everything possible.

If you have relatively close matches at other vendors, ask if they will upload their files too. The upload is free. Not only will they receive additional matches, and another set of ethnicity results, their results will help you by associating your matches with specific sides of your family.

Why Order Multiple Tests Now Instead of Waiting?

I encourage testers to order their tests at the beginning of their journey, not one at a time. Each new test from a vendor takes about 6-8 weeks from the time you initially order – they send the test, you swab or spit, return it, and they process your DNA. Of course, uploading takes far less time.

If you’re adding elapsed time, two autosomal tests (Ancestry and 23andMe), two uploads (FamilyTreeDNA and MyHeritage,) a Y-DNA and a mitochondrial DNA test, if all purchased serially, one after the other, means you’ll be waiting about 6-8 months.

Do you want to wait 6-8 months? Can you afford to?

Part of that answer has to do with what, exactly, you’re seeking.

A Name or Information?

Are you seeking the name of a person, or are you seeking information about that person? With grandparents, you may be hoping to meet them, and time may be of the essence. Time delayed may not be able to be recovered or regained.

Most people don’t just want to put a name to the person they are seeking – they want to learn about them. You will have different matches at each company. Even after you identify the person you seek, the people you match at each company may have information about them, their photos, know about their life, family, and their ancestors. They may be able and willing to facilitate an introduction if that’s what you seek.

One cousin that I assisted discovered that his father had died just 6 weeks before he made the connection. He was heartsick.

Having data from all vendors simultaneously will allow you to compile that data and work with it together as well as separately. Using your “best” matches at each company, augmented by both Y-DNA and mitochondrial DNA can make MUCH shorter work of this search.

Your Y-DNA, if you’re a male will give you insights into your surname line, and the Big-Y test now comes with estimates of how far in the past you share a common ancestor with other men that have taken the Big-Y test. This can be a HUGE boon to a male trying to figure out his surname line.

Y-DNA and mitochondrial DNA, respectively, will eliminate many people from being your mother or father, or your direct paternal or direct maternal line ancestor. Both provide insights into which population and where that population originated as well. In other words, it provides you lineage-specific information not available elsewhere.

Your Y-DNA and mitochondrial DNA can also provide critically important information about whether that direct line ancestor belonged to an endogamous population, and where they came from.

Strategies

You may be tempted to think that you only need to test at one vendor, or at the vendor with the largest database, but that’s not necessarily true.

Here’s a table of my closest matches at the 4 vendors.

Vendor Closest Maternal Closest Paternal Comments
Ancestry 1C, 1C1R Half 1C, 2C I recognized both of the maternal and neither of the paternal.
23andMe 2C, 2C 1C1R, half-gr-niece Recognized both maternal, one paternal
MyHeritage Mother uploaded, 1C Half-niece, half 1C Recognized both maternal, one paternal
FamilyTreeDNA Mother tested, 1C1R Parent/child, half-gr-niece Recognized all 4

To be clear, I tested my mother at FamilyTreeDNA before she passed away, but if I was an adoptee searching for my mother, that’s the first database she would be in. As her family, we were able to order the Family Finder test from her archived DNA after she had passed away. I then uploaded her DNA file to MyHeritage, but she’ll never be at either 23andMe or Ancestry because they don’t accept uploads and she clearly can’t test.

Additionally, being able to identify maternal matches by viewing shared matches with my mother separates out close matches from my paternal side.

Let’s put this another way, I stand a MUCH BETTER chance of unraveling this mystery with the combined closest matches of all 4 databases instead of the top ones from just one database.

I’m providing analysis methodologies for working with results from all of the vendors together, in case your answer is not immediately obvious. Taking multiple tests facilitates using all of these tools immediately, not months later. Solving the puzzle sooner means you may not miss valuable connection opportunities.

You may also discover that the door slams shut with some people, but another match may be unbelievably helpful. Don’t unnecessarily limit your possibilities.

Here’s the testing and upload strategy I recommend.

What When Ancestry 23andMe MyHeritage FamilyTreeDNA GEDmatch
Order autosomal test Initially Yes Yes Upload Upload Upload
Order Big-Y DNA test if male Initially Yes
Order mitochondrial DNA test Initially Yes
Upload free autosomal file From Ancestry or 23andMe Yes Yes Yes
Unlock Advanced Tools When upload file $29 $19 $9.95 month
Includes X Matching No Yes No Yes Yes
Chromosome Browser, segment location information No Yes Yes Yes Yes

When you upload a DNA file to a vendor site, only upload one file per site, per tester. Otherwise, multiple tests simply glom up everyone’s match list with multiple matches to the same person and can be very confusing.

  • One person took an autosomal test at a company that accepts uploads, forgot about it, uploaded a file from another vendor later, and immediately thought she had found her parent. She had not. She “found” herself.
  • Another person though she had found two sisters, but one person had uploaded their own file from two different vendors.

Multiple vendor sites reveal multiple close matches to different people which increase your opportunity to discover INFORMATION about your family, not just the identity of the person.

Match Ranges

Given that we are searching for an unknown maternal grandfather, your mother may not have had any (known) full siblings. The “best” match would be to a full or half siblings to your parents, or their descendants, depending on how old your grandparents would be.

Let’s take the “worst case” scenario, meaning there are no full siblings AND there are many possible generations between you and the people you may match.

Now, let’s look at DNAPainter’s Shared cM tool.

You’re going to be looking for someone who is either your mother’s half sibling on her father’s side, or who is a full sibling.

If your mother is adopted, it’s possible that she has or had full siblings. If your mother was born circa 1920, it’s likely that you will be matching the next generation, or two, or three.

However, if your mother was born later, you could be matching her siblings directly.

I’m going to assume half siblings for this example, because they are more difficult than full siblings.

Full sibling relationships for your mother’s siblings are listed at right. Your full aunt or uncle at top, then their descendant generations below.

At left, in red, are the half-sibling relationships and the matching amounts.

You can see that if you’re dealing with half 1C3R (half first cousin three times removed,) you may not match.

Therefore, in order to isolate matches, it’s imperative to test every relevant relative possible.

Who’s Relevant for DNA Testing?

Who is relevant to test If you’re attempting to identify your maternal grandfather?

The goal is to be able to assign matches to the most refined ancestor possible. In other words, if you can assign someone to either your grandmother’s line, or your grandfather’s line, that’s better than assigning the person to your grandparents jointly.

Always utilize the tests of the people furthest up the tree, meaning the oldest generations. Their DNA is less-diluted, meaning it has been divided fewer times. Think about who is living and might be willing to test.

You need to be able to divide your matches between your parents, and then between your grandparents on your mother’s side.

  • Test your parents, of course, and any of their known siblings, half or full.
  • If those siblings have passed away, test as many of their children as you can.
  • If any of your grandparents are living, test them
  • If BOTH of your grandparents on the same side aren’t available to test, test any, preferably all, living aunts or uncles.
  • If your maternal grandmother had siblings, test them or their descendants if they are deceased.
  • If your parents are deceased, test your aunts, uncles, full siblings and half-siblings on your mother’s side. (Personally, I’d test all half-siblings, not just maternal.)
  • Half-siblings are particularly valuable because there is no question which “side” your shared DNA came from. They will match people you don’t because they received part of your parent’s DNA that you did not.

Furthermore, shared matches to half-siblings unquestionably identify which parent those matches are through.

Essentially, you’re trying to account for all matches that can be assigned to your grandparents whose identities you know – leaving only people who descend from your unknown maternal grandfather.

Testing your own descendants will not aid your quest. There is no need to test them for this purpose, given that they received half of your DNA.

I wrote about why testing close relatives is important in the article Superpower: Your Aunts’ and Uncles’ DNA is Your DNA Too – Maximize Those Matches!

Create or Upload a Tree

Three of the four major vendors, plus GEDMatch, support and utilize family trees.

You’ll want to either upload or create a tree at each of the vendor sites.

You can either upload a GEDCOM file from your home computer genealogy software, or you can create a tree at one of the vendors, download it, and upload to the others. I described that process at Ancestry, here.

Goal

Your goal is to work with your highest matches first to determine how they are related to you, thereby eliminating matches to known lineages.

Assuming you’re only searching for the identity of one grandparent, it’s beneficial to have done enough of your genealogy on your three known grandparents to be able to assign matches from those lines to those sides.

Step 1 is to check each vendor for close matches that might fall into that category.

The Top 15 at Each Vendor

Your closest several autosomal matches are the most important and insightful. I begin with the top 15 autosomal results at each vendor, initially, which provides me with the best chance of meaningful close relationship discoveries.

Create a Spreadsheet or Chart

I hate to use that S word (spreadsheet), because I don’t want non-technical people to be discouraged. So, I’m going to show you how I set up a spreadsheet and you can simply create a chart or even draw this out on paper if you wish.

I’ve color-coded columns for each of my 4 grandparents. The green column is the target Maternal Grandfather whose identity I’m seeking.

I match our first example; Erik, at 417 cM. Based on various pieces of information, taken together, I’ve determined that I’m Erik’s half 1C1R. His 8 great-grandparent surnames, or the ones he has provided, indicate that I’m related to Eric on my paternal grandfather’s line.

You’ll want to record your closest matches in this fashion.

Let’s look at how to find this information and work with the tools at the individual vendors.

23andMe

Let’s start at 23andMe, because they create a potential genetic tree for you, which may or may not be accurate.

I have two separate tests at 23andMe. One is a V3 and one is a V4 test. I keep one in its pristine state, and I work with the second one. You’ll see two of “me” in the tree, and that’s why.

23andMe makes it easy to see estimated relationships, although they are not always correct. Generally, they are close, and they can be quite valuable.

Click on any image to enlarge

The maternal and paternal “sides” may not be positioned where genealogists are used to seeing them. Remember, 23andMe has no genealogy trees, so they are attempting to construct a genetic tree based on how people are related to you and to each other, with no prior knowledge. They do sometimes have issues with half-relationships, so I’d encourage you to use this tree to isolate people to the three grandparents you know.

In my case, I was able to determine the maternal and paternal sides easily based on known cousins. This is the perfect example of why it’s important to test known relatives from both sides of your family.

My paternal side, at right, in blue, was easy because I recognized my half-sister’s family, and because of known cousins who I recognized from having tested elsewhere. I’ve worked with them for years. The blue stars show people I could identify, mostly second cousins.

My maternal side is at left, in red. Normally, for genealogists, the maternal side is at right, and the paternal at left, so don’t make assumptions, and don’t let this positioning throw you.

I’m pretending I don’t know who my maternal grandfather is. I was able to identify my maternal grandmother’s side based on a known second cousin.

That leaves my target – my maternal grandfather’s line.

All of the matches to the left of the red circle would, by process of elimination, be on my maternal grandfather’s side.

The next step would be to figure out how the 5 people descending from my maternal grandfather’s line are related to each other – through which of their ancestors.

On the DNA Relatives match list, here’s what needs to be checked:

  • Do your matches share surnames with you or your ancestors?
  • Do they show surnames in common with each other?
  • Is there a common location?
  • Birth year which helps you understand their potential generation.
  • Did they list their grandparents’ birthplaces?
  • Did they provide a family tree link?
  • Do they also match each other using the Relatives in Common feature?
  • Do they triangulate, indicated by “DNA Overlap” in Relatives in Common?
  • Who else is on the Relatives in Common list, and what do they have in common with each other?
  • Looking at your Ancestry Composition compared with theirs, what are your shared populations, and are they relevant? If you are both 100% European, then shared populations aren’t useful, but if both people share the same minority ancestry, especially on the same segments, it may indeed be relevant – especially if it can’t be accounted for on the known sides of the family.

Reach out to these people and see what they know about their genealogy, if they have tested elsewhere, and if they have a genealogy tree someplace that you can view.

If they can tell you their grandparents’ names, birth and death dates and locations, you can check public sources like WikiTree, FamilySearch and Geni, or build trees for them. You can also use Newspaper resources, like Newspapers.com, NewspaperArchive and the newspapers at MyHeritage.

I added the top 15 23andMe matches into the spreadsheet I created.

You’ll notice that not many people at 23andMe enter surnames. However, if you can identify individuals from your 3 known lines, you can piggyback the rest by using Relatives in Common in conjunction with the genetic tree placement.

Be sure to check all the people that are connected to the target line in your genetic tree.

You’ll want to harvest your DNA segments to paint at DNAPainter if you don’t solve this mystery with initial reviews at each vendor.

Ancestry

Let’s move to Ancestry next.

At Ancestry, you’ll want to start with your closest matches on your match list.

Ancestry classifies “Close Matches” as anyone 200 cM or greater, which probably won’t reach as far down as the matches we’ll want to include.

Some of the categories in the Shared cM Chart from DNAPainter, above, don’t work based on ages, so I’ve eliminated those. I also know, for example, that someone who could fall in the grandparent/grandchild category (blue star,) in my case, does not, so must be a different relationship.

Second cousins, who share great-grandparents, can be expected to share about 229 cM of DNA on average, or between 41 and 592 cM. First cousins share 866 cM, and half first cousins share 449 cM on average.

I have 13 close matches (over 200 cM), but I’m including my top 15 at each vendor, so I added two more. You can always go back and add more matches if necessary. Just keep in mind that the smaller the match, the greater the probability that it came from increasingly distant generations before your grandparents. Your sweet spot to identify grandparents is between 1C and 2C.

I need to divide my close matches into 4 groups, each one equating to a grandparent. Record this on your spreadsheet.

You can group your matches at Ancestry using colored dots, which means you can sort by those groups.

You can also select a “side” for a match by clicking on “Yes” under the question, “Do you recognize them?”

Initially, you want to determine if this person is related to you on your mother’s or father side, and hopefully, through which grandparent.

Recently, Ancestry added a feature called SideView which allows testers to indicate, based on ethnicity, which side is “parent 1” and which side is “parent 2.” I wrote about that, here.

Make your selection, assuming you can tell which “side” of you descends from which parent based on ethnicity and/or shared matches. How you label “parent 1,” meaning either maternal or paternal, determines how Ancestry assigns your matches, when possible.

Using these tools, which may not be completely accurate, plus shared matches with people you can identify, divide your matches among your three known grandparents, meaning that the people you cannot assign will be placed in the fourth “unknown” column.

On my spreadsheet, I assign all of my closest matches to one of my grandparents. Michael is my first cousin (1C) and we share both maternal grandparents, so he’s not helpful in the division because he can’t be assigned to only one grandparent.

The green maternal grandfather is who I’m attempting to identify.

There are 4 people, highlighted in yellow, who don’t fall into the other three grandparent lines, so they get added to the green column and will be my focus.

I would be inclined to continue adding matches using a process known as the Leeds Method, until I had several people in each category. Looking back at the DNAPainter cM chart, at this point, we don’t have anyone below 200 cM and the matches we need might be below that threshold. The more matches you have to work with, the better.

At Ancestry, you cannot download your matches into a spreadsheet, nor can you work with other clustering tools such as Genetic Affairs, so you’ll have to build out your spreadsheet manually.

Check for the same types of information that I reviewed at 23andMe:

  • Review trees, if your matches have them, minimally recording the surnames of their 8 great-grandparents.
  • Review shared matches, looking for common names in the trees in recent generations.
  • View shared matches with people with whom you have a “Common Ancestor” indication, which means a ThruLine. You won’t have Thrulines with your target grandparent, of course, but Thrulines will allow you to place the match in one of the other columns. I wrote about ThruLines here, here and here.
  • ThruLines sometimes suggests ancestors based on other people’s trees, so be EXCEEDINGLY careful with potential ancestor suggestions. That’s not to say you should discount those suggestions. Just treat them as tree hints that may have been copy/pasted hundreds of times, because that’s what they are.

I make notes on each match so I can easily see the connection by scanning without opening the match.

Now, I have a total of 30 entries on my spreadsheet, 15 from 23and Me and 15 from Ancestry.

Why Not Use Autosclusters?

Even with vendors who allow or provide cluster tools, I don’t use an automated autocluster tool at this point. Autocluster tools often omit your closest matches because your closest matches would be in nearly half of all your clusters, which isn’t exactly informative. However, for this purpose, those are the very matches we need to evaluate.

After identifying groups of people that represent the missing grandparent, using our spreadsheet methodology, autoclusters could be useful to identify common surnames and even to compare the trees of our matches using AutoTree, AutoPedigree and AutoKinship. AutoClusters cannot be utilized at Ancestry, but is available through MyHeritage and at GEDmatch, or through Genetic Affairs for 23andMe and FamilyTreeDNA.

Next, let’s move to FamilyTreeDNA.

FamilyTreeDNA

FamilyTreeDNA is the only vendor that provides Family Matching, also known as “bucketing.” FamilyTreeDNA assigns your matches to either a paternal or maternal bucket, or both, based on triangulated matches with someone you’ve linked to a profile in your tree.

The key to Family Matching is to link known Family Finder matches to their profile cards in your tree.

Clicking on the Family Tree link at the top of your personal page allows you to link your matches to the profile cards of your matches.

FamilyTreeDNA utilizes these linked matches to assign those people, and matches who match you and those people, both, on at least one common segment, to the maternal or paternal tabs on your match list.

Always link as many known people as possible (red stars) which will result in more matches being bucketed and assigned to parents’ sides for you, even if neither parent is available to test.

I wrote about Triangulation in Action at FamilyTreeDNA, here.

You can see at the top of my match list that I have a total of 8000 matches of which 3422 are paternal, 1517 are maternal and 3 match on both sides. Full siblings, their (and my) children and their descendants will always match on both sides. People with endogamy across both parents may have several matches on both sides.

If your relevant parent has tested, always work from their test.

Because we are searching for the maternal grandfather, in this case, we can ignore all tests that are bucketed as paternal matches.

Given that we are searching for my maternal grandfather, I probably have not been able to link as many maternal matches, other than possibly ones from my maternal grandmother. This means that the maternal grandfather’s matches are not bucketed because there are no identified matches to link on that side of my tree.

If you sort by maternal and paternal tabs, you’ll miss people who aren’t bucketed, meaning they have no maternal or paternal icon, so I recommend simply scanning down the list and processing maternal matches and non-bucketed matches.

By being able to confidently ignore paternally bucketed matches and only processing maternal and non-assigned matches, this is equivalent to processing the first 48 total matches. If I were to only look at the first 15 matches, 12 were paternal and only 3 are maternal.

Using bucketing at FamilyTreeDNA is very efficient and saves a lot of work.

Omitting paternal matches also means we are including smaller matches which could potentially be from common ancestors further back in the tree. Or, they could be younger testers. Or simply smaller by the randomness of recombination.

FamilyTreeDNA is a goldmine, with 16 of 20 maternal matches being from the unknown maternal grandfather.

Next, let’s see what’s waiting at MyHeritage.

MyHeritage

MyHeritage is particularly useful if your lineage happens to be from Europe. Of course, if you’re searching for an unknown person, you probably have no idea where they or their ancestors are from. Two of my best matches first appeared at MyHeritage.

Of course, your matches with people who descend from your unknown maternal grandfather won’t have any Theories of Family Relativity, as that tool is based on BOTH a DNA match plus a tree or document match. However, Theories is wonderful to group your matches to your other three grandparents.

MyHeritage provides a great deal of information for each match, including common surnames with your tree. If you recognize the surnames (and shared matches) as paternal or maternal, then you can assign the match. However, the matches you’re most interested in are the highest matches without any surnames in common with you – which likely point to the missing maternal grandfather.

However, those people may, and probably do, have surnames in common with each other.

Of the matches who aren’t attributed to the other three grandparents, the name Ferverda arises again and again. So does Miller, which suggests the grandparent or great-grandparent couple may well be Ferverda/Miller.

Let’s continue working through the process with our spreadsheet and see what we can discover about those surnames.

Our 60 Results

Of the 60 total results, 15 from each vendor, a total of 24 cannot be assigned to other columns through bucketing or shared matches, so are associated with the maternal grandfather. Of course, Michael who descends from both of my maternal grandparents won’t be helpful initially.

Cheryl, Donald and Michael are duplicates at different vendors, but the rest are not.

Of the relevant matches, the majority, 12 are from FamilyTreeDNA, four each are from Ancestry and MyHeritage, and three are from 23andMe.

Of the names provided in the surname fields of matches, in matches’ trees in the first few generations, and the testers’ surnames, Ferverda is repeated 12 times, for 50% of the time. Miller is repeated 9 times, so it’s likely that either of those are the missing grandfather’s surname. Of course, if we had Y-DNA, we’d know the answer to that immediately.

Comparing trees of my matches, we find John Ferverda as the common ancestor between two different matches. John is the son of Hiram Ferverda and Eva Miller who are found in several trees.

That’s a great hint. But is this the breakthrough I need?

What’s Next?

The next step is to look for connections between the maternal grandmother, Edith Lore, who is known in our example, and a Ferverda male. He is probably one of the sons of Hiram Ferverda and Eva Miller. Do they lived in the same area? In close proximity? Do they attend the same church or school? Are they neighbors or live close to the family or some of their relatives? Does she have connections with Ferverda family members? We are narrowing in.

Some of Hiram and Eva’s sons might be able to be eliminated based on age or other factors, or at least be less likely candidates. Any of their children who had moved out of state when the child was conceived would be less likely candidates. Age would be a factor, as would opportunity.

Target testing of the Ferverda sons’ children, or the descendants of their children would (probably) be able to pinpoint which of their sons is more closely related to me (or my mother) than the rest.

In our case, indeed, John Ferverda is the son we are searching for and his descendant, Michael is the highest match on the list. Cheryl and Donald descend from John’s brother, which eliminates him as a candidate. Another tester descends from a third Ferverda son, which eliminates that son as well.

Michael, my actual first cousin with a 755 cM match at one vendor, and 822 cM at a second vendor, is shown by the MyHeritage cM Explainer with an 88% probability that he is my first cousin.

However, when I’m trying to identify the maternal grandfather, which is half of that couple, I need to focus one generation further back in time to eliminate other candidates.

The second and third closest matches are both Donald at 395 cM and Cheryl at 467 cM who also share the same Ferverda/Miller lineage and are the children of my maternal grandfather’s brother.

On the spreadsheet, I need to look at the trees of people who have both Ferverda and Miller, which brought me to both Cheryl and Donald, then Michael, which allowed me to identify John Ferverda, unquestionably, as my grandfather based on the cM match amounts.

Cheryl and Donald, who are confirmed full siblings, and my mother either have to be first cousins, or half siblings. Their match with mother is NOT in the half-sibling range for one sibling, and on the lower edge with the other. Mother also matches Michael as a nephew, not more distantly as she would if he were a first cousin once removed (1C1R) instead of a nephew.

Evaluating these matches combined confirms that my maternal grandfather is indeed John Ferverda.

What About X DNA?

The X chromosome has a unique inheritance path which is sometimes helpful in this circumstance, especially to males.

Women inherit an X chromosome from both parents, but males inherit an X chromosome from ONLY their mother. A male inherits a Y chromosome from his father which is what makes him male. Women inherit two X chromosomes, one from each parent, and no Y, which is what makes them female.

Therefore, if you are a male and are struggling with which side of your tree matches are associated with, the X chromosome may be of help.

Your mother passed her X chromosome to you, which could be:

  • Her entire maternal X, meaning your maternal grandmother’s X chromosome
  • Her entire paternal X, meaning your maternal grandfather’s X chromosome (which descends from his mother)
  • Some combination of your maternal grandmother and maternal grandfather’s chromosomes

One thing we know positively is that a male’s X matches are ALWAYS from their maternal side only, so that should help when dividing a male’s matches maternally or paternally. Note – be aware of potential pedigree collapse, endogamy and identical-by-chance matches if it looks like a male has a X match on his father’s side.

Unfortunately, the X chromosome cannot assist females in the same way, because females inherit an X from both parents. Therefore, they can match people in the same was as a male, but also in additional ways.

  • Females will match their paternal grandmother on her entire X chromosome, and will match one or both of their maternal grandparents on the X chromosome.
  • Females will NEVER match their paternal grandfather’s X chromosome because their father did not inherit an X chromosome from his father.
  • Males will match one or both of their maternal grandparents on their X chromosome.
  • Males will NEVER match their paternal grandparents, because males do not receive an X chromosome from their father.

The usefulness of X DNA matching depends on the inheritance path of both the tester AND their match.

When Can Y-DNA or Mitochondrial DNA Help with Grandparent Identification?

If you recall, I selected the maternal grandfather as the person to seek because no tester carries either the Y-DNA or mitochondrial DNA of their maternal grandfather. In other words, this was the most difficult identification, meaning that any of the other three grandparents would be, or at least could be, easier with the benefit of Y-DNA and/or mitochondrial DNA testing.

In addition to matching, both Y-DNA and mitochondrial DNA will provide testers with location origins, both continental and often much more specific locations based on where other testers and matches are from.

Y-DNA often provides a surname.

Let’s see how these tests, matches and results can assist us.

  • Paternal grandfather – If I was a male descended from John Ferverda paternally, I could have tested both my autosomal DNA PLUS my Y-DNA, which would have immediately revealed the Ferverda surname via Y-DNA. Two Ferverda men are shown in the Ferverda surname DNA project, above.

That revelation would have confirmed the Ferverda surname when combined with the high frequency of Ferverda found among autosomal matches on the spreadsheet.

  • Maternal grandmother – If we were searching for a maternal grandmother, both the male and female sibling testers (as shown in the pedigree chart) would have her mitochondrial DNA which could provide matches to relevant descendants. Mitochondrial DNA at both FamilyTreeDNA and 23andMe could also eliminate anyone who does not match on a common haplogroup, when comparing 23andMe results to 23andMe results, and FamilyTreeDNA to FamilyTreeDNA results at the same level.

At 23andMe, only base level haplogroups are provided, but they are enough to rule out a direct matrilineal line ancestor.

At FamilyTreeDNA, the earlier HVR1 and HVR2 tests provide base level haplogroups, while full sequence testing provides granular, specific haplogroups. Full sequence is the recommended testing level.

  • Paternal grandmother – If we were searching for a paternal grandmother, testers would, of course, need either their father to test his mitochondrial DNA, or for one of his siblings to test which could be used in the same way as described for maternal grandmother matching.

Summary

Successfully identifying a grandparent is dependent on many factors. Before you make that identification, it’s very difficult to know which are more or less important.

For example, if the grandparent is from a part of the world with few testers, you will have far fewer matches, potentially, than other lines from more highly tested regions. In my case, two of my four grandparents’ families, including Ferverda, immigrated in the 1850s, so they had fewer matches than families that have been producing large families in the US for generations.

Endogamy may be a factor.

Family size in past and current generations may be a factor.

Simple luck may be a factor.

Therefore, it’s always wise to test your DNA, and that of your parents and close relatives if possible, and upload to all of the autosomal databases. Then construct an analysis plan based on:

  • How you descend from the grandparent in question, meaning do you carry their X DNA, Y-DNA or mitochondrial DNA.
  • Who else is available to test their autosomal DNA to assist with shared matches and the process of elimination.
  • Who else is available to test for Y-DNA and/or mitochondrial DNA of the ancestor in question.

If you don’t find the answer initially, schedule a revisit of your matches periodically and update your spreadsheet. Sometimes DNA and genealogy is a waiting same.

Just remember, luck always favors the prepared!

Resources

You may find the following resource articles beneficial in addition to the links provided throughout this article.

_____________________________________________________________

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

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Project Administrators: How to Prepare Your Project for FamilyTreeDNA’s New Group Time Tree

Posted on by
10

Last week, FamilyTreeDNA  gave us a sneak peek into their new Group Time Tree that displays Big Y testers in time tree format within group projects that they have joined. I wrote about this in the article, Sneak Preview: Introducing the FamilyTreeDNA Group Time Tree.

The Group Time Tree is an excellent way to recruit new members, because people can see how other people with the same surname fit together in terms of common ancestors. Additionally, the time tree shows when they are related meaning TMRCA, time to the most recent common ancestor.

Here’s an example of the Estes project group time tree with some of the subgroups I’ve defined selected.

Click to enlarge any image

Feel free to view the public Estes project, here, and the Estes Group Time Tree, here.

View my subgroupings, and how they appear on the Group Time Tree. See if that’s how you want your project to work. You can use the search box to search for your own project, or other projects.

Preparation

As a volunteer project administrator, there are a number of things you’ll either need to do, or may want to do to prepare for the wider introduction of the exciting Group Time Tree. You’ll want your project members to benefit as much as possible.

Project Must Be Publicly Displayed

In order for your project to be able to be displayed in the Group Time Tree format, it must be a public project, meaning it has a public presence and viewing is not restricted to members only. The minimal selection for the Group Time Tree is that Y SNPs must be public.

Under Project Administration, Public Website, you’ll see the following configuration options.

Please click to enlarge

  • “Display Project Statistics” must be checked to facilitate displaying the Country Map showing the locations around the world of your Big Y project members.
  • You will want to enable the members Surname, and the Earliest Known Ancestor if you want them to display in the Group Time Tree. If at least one of these is not selected, the Group Time Tree will not be displayed.
  • Option 1: Under “YDNA Options,” at right, if you select “Public” for “Member DNA Test (YDNA) Results,” both SNP and haplogroup results will be shown in the public project, but of course, only Big Y tester’s results are shown on the Group Time Tree. You do NOT have to select public here to enable the Group Time Tree, but if you DON’T select public here, then you MUST select “Public” for “Y DNA SNP” (Option 2) or the Group Time Tree will not be enabled.
  • If you select either “Project Members Only” or “Do Not Display” for “Member DNA Test (YDNA) Results,” there will be no public project display for individual results.
  • Option 2: If you do NOT select “Public” for “Y-DNA SNP”, there will be no Group Time Tree display unless the “Member DNA Test (YDNA) Results” (Option 1) are set to Public.

In other words, for the Group Time Tree to be enabled, Option 1 or Option 2 MUST be set to “Public.”

Here’s a chart to help.

Field Selection Group Time Tree Result
Display Project Statistics Not selected No Country Map displayed.
Display Project Statistics Selected Country Map Displayed if group project publicly enabled.
Members Last Name and/or Earliest Known Ancestor Must select one or both If at least one is not selected, Group Time Tree is not enabled.
Option 1: Member DNA Test (YDNA) Results Public STR and haplogroup results show in BOTH the traditional public project display and the Group Time Tree.
Option 1: Member DNA Test (YDNA) Results Project Members Only or Do Not Display Will not display in the traditional project display. If this option is set to anything but Public, then Option 2 must be Public to enable the Group Time Tree.
Option 2: Y-DNA SNP Public Will display Group Time Tree even if Member DNA Test Results are not public.
Option 2: Y-DNA SNP Not Public Will NOT display Group Time Tree unless Option 1 set to Public.
Option 1 and Option 2 Neither set to Public No public group project display and no Group Time Tree.
Option 1 and Option 2 Both set to Public Public display of STR results, haplogroup, SNP results, and Group Time Tree.

Don’t forget to “Save” when you’re finished with your project configuration.

Country Map

For the Country Map to be displayed, you must enable the Project Statistics, above.

The Country Map reflects Big Y results for everyone within the project. If you do not want to include the Y-DNA of men within the project who not associated with the direct paternal surname of the project, you can disable the public display of their Y-DNA results.

An example would be a male who has joined a surname project because he is autosomally related to the surname, but does not carry the Y-DNA of that surname ancestor. I have this situation a LOT in the Estes project, because I “gather” my family members there and encourage cousins to join.

Here’s how to disable the display of those results within the project.

Suppress Display of Tests of Individuals

Select Public Results Display Settings.

Then, select the option for what you wish to implement for the various project members.

Options are:

  • Show Y DNA
  • Hide Y DNA
  • Show mtDNA
  • Hide mtDNA

Group Project Subgroupings

In the Estes project, I opted to colorize the descendants of Abraham Estes, the immigrant, all teal. Now, with the new Group Time Tree subgroup display, I may wish to change that. I might want the descendants of different sons to be different colors.

I definitely want different genetic Estes lineages to be different colors.

If you have people in your project whose Y-DNA is not relevant to the project, and you don’t want to suppress the display of their Y DNA results, you can group them together in a separate subgroup so you can deselect that group altogether when displaying the Group Time Tree, although their results will appear on the Country Map.

You can create subgroups and then group members under Project Administration, Member Subgrouping.

Weekly Updates

The Group Time Tree is only updated once a week, so there will be approximately a week’s delay after you make project configuration changes before you will see the results reflected in the Group Time Tree.

That’s why it’s a good idea to review your settings now so that when it goes live, you’ll be ready and it will display the way you want.

Padlock

If one of your project members has a padlock in place of their surname and Paternal Ancestor, they are a project member but have not opted-in to the public display within the project.

In their own settings, they can change that by Opting-In to the Group Project Profile Sharing. You can provide them with these instructions.

Under Account Settings, select Project Preferences.

Then, scroll down to Group Project Profile.

Select Opt-in to Sharing.

Encourage Big Y Upgrades and General Fund Donations

I’ve been encouraging everyone in my projects to upgrade to the Big Y-700 and providing several scholarships. Don’t hesitate to send bulk emails to your project members asking for general fund donations to upgrade someone who is willing but needs a scholarship. I’ve had amazingly good luck with the scholarship approach and the Big Y results benefit everyone in the project, including women who don’t have a Y chromosome to test.

Encourage Members to Complete Earliest Known Ancestor and Locations

The three haplotrees supported by FamilyTreeDNA  all depend on location information:

  • The Public Y-DNA and Mitochondrial DNA Haplotrees include country flags
  • The Discover Haplogroup tool includes the Country Frequency and country flags under the Haplogrop Story
  • The Group Time Tree includes country flags for the Earliest Known Ancestor (EKA) of individual testers

Please encourage members to complete their Earliest Known Ancestor name and location. Remember, this information is NOT extracted from uploaded trees.

In a few days, I’ll publish step-by-step instructions for how to add EKA and location information.

Now is a good time to update your project selections so you’ll be ready for the official rollout of the Group Time Tree.

Accessing Your Group Time Tree

Until the official rollout, there are two ways to access your group’s time tree:

  1. Click here and then enter the name of the group project in the search box.
  2. Replace the word “estes” with your project’s exact name in the following url: https://discover.familytreedna.com/groups/estes/tree

_____________________________________________________________

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

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research

Sneak Preview: Introducing the FamilyTreeDNA Group Time Tree

Posted on by
25

Drum roll please!!!

This is a sneak peek of a new tool being rolled out by FamilyTreeDNA in a VERY EARLY BETA soft launch.

Right now, the only way to view the Group Time Tree is by using the link to my group project, below, then, search for a different project name. I’ll show you, but first, let’s talk about this VERY COOL new tool for Big Y group project results.

The Group Time Tree is a feature that group project administrators and project members have wanted for a VERY long time!

At FamilyTreeDNA, the words “group” and “project” are both used to describe Group Projects which are projects run by volunteer administrators. FamilyTreeDNA customers can join any number of projects to collaborate with other testers who have a common interest.

Four basic types of public group projects exist:

  • Surname Group Projects
  • Haplogroup Group Project
  • Geographic Group Projects which can include other types of special interests
  • Mitochondrial Lineage Group Projects

What Does the Regular Discover Time Tree Do?

The Discover tool that was recently introduced (here) provides a Time Tree view of any specific haplogroup (but no surnames or ancestors) in relation to:

  • Big Y testers (not SNP-only testers and not STR results because they can’t be used for time-to-most-recent-common-ancestor (TMRCA) calculations)
  • Ancient Connections
  • Notable Connections

Using the regular Discover Haplogroup took, here’s an example of the haplogroups of the Estes (and other) men, beginning with the R-BY154784 lineage near the bottom. Time is at the top. The only way you know they are Estes men is because I told you. The Discover tool is haplogroup specific, not surname specific.

What Does the New Group Time Tree Do?

The brand-new Group Time Tree is an extension of the Discover technology, but focused within projects and includes both surnames and earliest known ancestors for people who have opted-in to have their results display in public group projects. This tool only works for group projects that have the public display enabled, and includes only data that the administrator has included. Not all administrators have enabled the display of the “Paternal Ancestor” field, for example.

Now, you can see Big Y group project members:

  • All mapped together on a genetic time tree, or
  • By project subgroups defined by the project administrator

I want to provide a friendly reminder that this is a BETA tool and will be fully rolled out in the not-too-distant future. In the meantime, it’s fun to have a sneak preview!!!

Estes DNA Group Project

Before going further, here are some screen shots of the Estes DNA Group Project for comparison.

I’ve created multiple color-coded groups within the project based on the genealogy and Y-DNA matches of the participants. The teal groups all descend from the Estes line from Kent, England, and match each other. Since not every man with an Estes surname descends from this line, there are also other color-identified groups.

Additionally, in the Estes project, I do not restrict members to males with the Estes surname, so there are several non-Estes men who have joined. Their Y-DNA shows in the project so I have placed them in an “Autosomal – Not Y DNA” group because they are Estes-related autosomally, not through the direct Y-DNA surname line.

I’ve grouped other clusters of Estes-surname males who do not descend from the Kent line into other color-coded groups, which turned out to be extremely beneficial for the new Group Time Tree.

Let’s see how the Estes Project works with the new Group Time Tree.

The Estes Group Time Tree

Here’s the link to the Estes Group Time Tree. I’ll be using the Estes data for this article, then show you how to view other group projects of your choosing from this link. So please read these instructions.

The Group Time Tree shows a genetic family tree of direct paternal lineages on a time scale. It shows how Big Y tested members of Group Projects are related to each other and when their shared ancestors are estimated to have lived.

Click on any image to enlarge

This is the first display I see.

Looking around, I notice the menu.

Select either “All search results” or the group or groups you want to view.

If you compare the groups above on the menu to the project screen shots, you’ll notice that the colors along the left side equate to the colors of the project subgroupings. We have Eastridge, meaning those who are not genetically Estes, then “Estes Autosomal, Not Y DNA,” then a group of teal project groupings who descend from the Estes Kent line.

I clicked on “Select All Search Results” which displayed everyone in the project from all haplogroups. This resulted in the Estes men being scrunched on the right-hand side, below, due to the long timeframe involved, which is not useful.

What is VERY useful is the Paternal Ancestor column which is the earliest known ancestor (EKA) for each tester’s line. Hopefully, this will encourage everyone to enter their EKA and location. You can find instructions, here.

Ok, let’s “De-select all” and just focus on specific groups.

Much better. I can see a much more relevant timeline for the men in the line being researched. The Estes men are no longer scrunched up along the right side because the left-to-right time is much shorter – 1500ish vs 100,000ish years.

The colored dot on the location flag indicates which colored group these men have been assigned to by the project administrator.

It’s very easy to see if two groups (or two men) descend from the same paternal line.

Next, I added the Eastridge group back into the display as an experiment.

The common ancestor between the single Eastridge Big Y tester and the Estes men is back in the Stone Age, about 35,000 BCE.

I do feel compelled to mention that this information can’t necessarily be extrapolated for all Eastridge men, because there are a few men with Eastridge surnames that are actually genetically Estes men. Someplace along the line, the name got changed. This is the perfect example of why every man needs to test their Y-DNA.

You can remove the menu by clicking on Subgroups.

You make the menu re-appear by clicking on Subgroups again.

I LOVE – LOVE – LOVE that I can see the ancestors and the clusters and I didn’t have to do this grouping myself. These men could have been in one big group in the project and the software would have created the clusters for me.

For example, there has been debate for decades about whether or not Moses Estes of South Carolina was descended from Abraham Estes, the immigrant, and if so, through which son.

Based on the Big Y-700 test (the Big Y-500 did not reveal this) and clustering, we know assuredly that Moses Estes of SC:

  • Descended from the Kent line
  • Descended from Abraham who has mutation R-BY490
  • Did NOT descend from Abraham’s son Moses whose descendants have mutation R-ZS3700

I’ve been keeping this project spreadsheet for years now. It’s wonderful to be able to see a genetic tree visualization. The Big Y men are blocked in red.

I’m hopeful that the balance of the men who have NOT yet taken the Big Y-700 will upgrade now because there’s so much more to learn. This is especially true for men who reach a brick wall prior to Abraham. The Big Y-700 test, perhaps combined with STRs, will place them in a lineage.

I’m sure that we would discover new haplogroups among Abraham’s descendants if they would all upgrade. There are more men who have not tested at the Big Y level than those that have.

Display Options

Under display options, you can add Ancient or Notable connections, remove confidence bars, and adjust the tree height.

Discoveries for Administrators

As a project administrator, one thing I discovered is that I might want to regroup within some of my projects to take full advantage of the color coding on the Group Time Tree. If you are a project administrator, you may want to ponder the same.

I also discovered that when I clicked on Country Map, I did not have Project Statistics enabled.

If you make project configuration changes, this report will only be updated weekly, so it’s not immediate.

The country map shows the distribution of all the countries within the project, not specific groups within projects

You can view Country Maps in either map or table format, but remember that if the project is a surname project and includes autosomal testers, the map view will not be representative of the surname itself. This view shows all groups.

Viewing Another Group Project

To view a different group project, simply enter that project name in the search box. For now, this is how you’ll be able to view group projects until this tool is fully rolled out.

I entered the surname “Speak” and was presented with these options.

Obviously, the surname Speak or a variation is found in these projects. Just click to view.

Your Turn

If you have not yet taken or upgraded to the Big Y-700 test, now’s the time. Order or upgrade, here.

If you have already taken the Big Y-700 test, or want to view a project, click on this link, and search for your project of choice.

Have fun!!!

_____________________________________________________________

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

Share the Love!

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

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

You Can Help Keep This Blog Free

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

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Book

Genealogy Books

Genealogy Research