New Native American Mitochondrial DNA Haplogroups

At the November 2016 Family Tree DNA International Conference on Genetic Genealogy, I was invited to give a presentation about my Native American research findings utilizing the Genographic Project data base in addition to other resources. I was very pleased to be offered the opportunity, especially given that the 2016 conference marked the one year anniversary of the Genographic Project Affiliate Researcher program.

The results of this collaborative research effort have produced an amazing number of newly identified Native American mitochondrial haplogroups. Previously, 145 Native American mitochondrial haplogroups had been identified. This research project increased that number by 79% added another 114 haplogroups, raising the total to 259 Native American haplogroups.

Guilt by Genetic Association

Bennett Greenspan, President of Family Tree DNA, gave a presentation several years ago wherein he described genetic genealogy as “guilt by genetic association.” This description of genetic genealogy is one of the best I have ever heard, especially as it pertains to the identification of ancestral populations by Y and mitochondrial DNA.

As DNA testing has become more mainstream, many people want to see if they have Native ancestry. While autosomal DNA can only measure back in time relative to ethnicity reliably about 5 or 6 generations, Y and mitochondrial DNA due to their unique inheritance paths and the fact that they do not mix with the other parent’s DNA can peer directly back in time thousands of years.

Native American Mitochondrial DNA

Native American mitochondrial DNA consists of five base haplogroups, A, B, C, D and X. Within those five major haplogroups are found many Native as well as non-Native sub-haplogroups. Over the last 15 years, researchers have been documenting haplogroups found within the Native community although progress has been slow for various reasons, including but not limited to the lack of participants with proven Native heritage on the relevant matrilineal genealogical line.

In the paper, “Large scale mitochondrial sequencing in Mexican Americans suggests a reappraisal of Native American origins,” published in 2011, Kumar et al state the following:

For mtDNA variation, some studies have measured Native American, European and African contributions to Mexican and Mexican American populations, revealing 85 to 90% of mtDNA lineages are of Native American origin, with the remainder having European (5-7%) or African ancestry (3-5%). Thus the observed frequency of Native American mtDNA in Mexican/Mexican Americans is higher than was expected on the basis of autosomal estimates of Native American admixture for these populations i.e. ~ 30-46%. The difference is indicative of directional mating involving preferentially immigrant men and Native American women.

The actual Native mtDNA rate in their study of 384 completely sequenced Mexican genomes was 83.3% with 3.1% being African and 13.6% European.

This means that Mexican Americans and those south of the US in Mesoamerica provide a virtually untapped resource for Native American mitochondrial DNA.

The Genographic Project Affiliate Researcher Program

At the Family Tree DNA International Conference in November 2015, Dr. Miguel Vilar announced that the Genographic Project data base would be made available for qualified affiliate researchers outside of academia. There is, of course, an application process and aspiring affiliate researchers are required to submit a research project plan for consideration.

I don’t know if I was the first applicant, but if not, I was certainly one of the first because I wasted absolutely no time in submitting my application. In fact, my proposal likely arrived in Washington DC before Dr. Vilar did!

One of my original personal goals for genetic genealogy was to identify my Native American ancestors. It didn’t take long before I realized that one of the aspects of genetic genealogy where we desperately needed additional research was relative to Native people, specifically within Native language groups or tribes and from individuals who unquestionably know their ancestry and can document that their direct Y or mtDNA ancestors were Native.

Additionally, we needed DNA from pre-European-contact burials to ascertain whether haplogroups found in Europe and Africa were introduced into the Native population post-contact or existed within the Native population as a result of a previously unknown/undocumented contact. Some of both of these types of research has occurred, but not enough.

Slowly, over the years, additional sub-haplogroups have been added for both the Y and mitochondrial Native DNA. In 2007, Tamm et al published the first comprehensive paper providing an overview of the migration pathways and haplogroups in their landmark paper, “Beringian Standstill and the Spread of Native American Founders.” Other research papers have added to that baseline over the years.

beringia map

“Beringian Standstill and the Spread of Native American Founders” by Tamm et al

In essence, whether you are an advocate of one migration or multiple migration waves, the dates of 10,000 to 25,000 years ago are a safe range for migration from Asia, across the then-present land-mass, Beringia, into the Americas. Recently another alternative suggesting that the migration may have occurred by water, in multiple waves, following coastlines, has been proposed as well – but following the same basic pathway. It makes little difference whether the transportation method was foot or kayak, or both, or one or more migration events. Our interest lies in identifying which haplogroups arrived with the Asians who became the indigenous people of the Americas.

Haplogroups

To date, proven base Native haplogroups are:

Y DNA:

  • Q
  • C

Mitochondrial DNA

  • A
  • B
  • C
  • D
  • X

Given that the Native, First Nations or aboriginal people, by whatever name you call them, descended from Asia, across the Beringian land bridge sometime between roughly 10,000 and 25,000 years ago, depending on which academic model you choose to embrace, none of the base haplogroups shown above are entirely Native. Only portions, meaning specific subgroups, are known to be Native, while other subgroups are Asian and often European as well. The descendants of the base haplogroups, all born in Asia, expanded North, South, East and West across the globe. Therefore, today, it’s imperative to test mitochondrial DNA to the full sequence level and undergo SNP testing for Y DNA to determine subgroups in order to be able to determine with certainty if your Y or mtDNA ancestor was Native.

And herein lies the rub.

Certainty is relative, pardon the pun.

We know unquestionably that some haplogroups, as defined by Y SNPs and mtDNA full sequence testing, ARE Native, and we know that some haplogroups have never (to date) been found in a Native population, but there are other haplogroup subgroups that are ambiguous and are either found in both Asia/Europe and the Americas, or their origin is uncertain. One by one, as more people test and we obtain additional data, we solve these mysteries.

Let’s look at a recent example.

Haplogroup X2b4

Haplogroup X2b4 was found in the descendants of Radegonde Lambert, an Acadian woman born sometime in the 1620s and found in Acadia (present day Nova Scotia) married to Jean Blanchard as an adult. It was widely believed that she was the daughter of Jean Lambert and his Native wife. However, some years later, a conflicting record arose in which the husband of Radegonde’s great-granddaughter gave a deposition in which he stated that Radegonde came from France with her husband.

Which scenario was true? For years, no one else tested with haplogroup X2b4 that had any information as to the genesis of their ancestors, although several participants tested who descended from Radegonde.

Finally, in 2016, we were able to solve this mystery once and for all. I had formed the X2b4 project with Marie Rundquist and Tom Glad, hoping to attract people with haplogroup X2b4. Two pivotal events happened.

  • Additional people tested at Family Tree DNA and joined the X2b4 project.
  • Genographic Project records became available to me as an affiliate researcher.

At Family Tree DNA, we found other occurrences of X2b4 in:

  • The Czech Republic
  • Devon in the UK
  • Birmingham in the UK

Was it possible that X2b4 could be both European and Native, meaning that some descendants had migrated east and crossed the Beringia land bridge, and some has migrated westward into Europe?

Dr. Doron Behar in the supplement to his publication, “A Copernican” Reassessment of the Human Mitochondrial DNA Tree from its Root” provides the creation dates for haplogroup X through X2b4 as follows:

native-mt-x2b4

These dates would read 31,718 years ago plus or minus 11,709 (eliminating the numbers after the decimal point) which would give us a range for the birth of haplogroup X from 43,427 years ago to 20,009 years ago, with 31,718 being the most likely date.

Given that X2b4 was “born” between 2,992 and 8,186 years ago, the answer has to be no, X2b4 cannot be found both in the Native population and European population since at the oldest date, 8,100 years ago, the Native people had already been in the Americas between 2,000 and 18,000 years.

Of course, all kinds of speculation could be (and has been) offered, about Native people being taken to Europe, although that speculation is a tad bit difficult to rationalize in the Czech Republic.

The next logical question is if there are documented instances of X2b4 in the Native population in the Americas?

I turned to the Genographic Project where I found no instances of X2b4 in the Native population and the following instances of X2b4 in Europe.

  • Ireland
  • Czech
  • Serbia
  • Germany (6)
  • France (2)
  • Denmark
  • Switzerland
  • Russia
  • Warsaw, Poland
  • Norway
  • Romania
  • England (2)
  • Slovakia
  • Scotland (2)

The conclusion relative to X2b4 is clearly that X2b4 is European, and not aboriginally Native.

The Genographic Project Data Base

As a researcher, I was absolutely thrilled to have access to another 700,000+ results, over 475,000 of which are mitochondrial.

The Genographic Project tests people whose identity remains anonymous. One of the benefits to researchers is that individuals in the public participation portion of the project can contribute their own information anonymously for research by answering a series of questions.

I was very pleased to see that one of the questions asked is the location of the birth of the participant’s most distant matrilineal ancestor.

Tabulation and analysis should be a piece of cake, right? Just look at that “most distant ancestor” response, or better yet, utilize the Genographic data base search features, sort, count, and there you go…

Well, guess again, because one trait that is universal, apparently, between people is that they don’t follow instructions well, if at all.

The Genographic Project, whether by design or happy accident, has safeguards built in, to some extent, because they ask respondents for the same or similar information in a number of ways. In any case, this technique provides researchers multiple opportunities to either obtain the answer directly or to put 2+2 together in order to obtain the answer indirectly.

Individuals are identified in the data base by an assigned numeric ID. Fields that provide information that could be relevant to ascertaining mitochondrial ethnicity and ancestral location are:

native-mt-geno-categories

I utilized these fields in reverse order, giving preference to the earliest maternal ancestor (green) fields first, then maternal grandmother (teal), then mother (yellow), then the tester’s place of birth (grey) supplemented by their location, language and ethnicity if applicable.

Since I was looking for very specific information, such as information that would tell me directly or suggest that the participant was or could be Native, versus someone who very clearly wasn’t, this approach was quite useful.

It also allowed me to compare answers to make sure they made sense. In some cases, people obviously confused answers or didn’t understand the questions, because the three earliest ancestor answers cannot contain information that directly contradict each other. For example, the earliest ancestor place of birth cannot be Ireland and the language be German and the ethnicity be Cherokee. In situations like this, I omitted the entire record from the results because there was no reliable way to resolve the conflicting information.

In other cases, it was obvious that if the maternal grandmother and mother and tester were all born in China, that their earliest maternal ancestor was not very likely to be Native American, so I counted that answer as “China” even though the respondent did not directly answer the earliest maternal ancestor questions.

Unfortunately, that means that every response had to be individually evaluated and tabulated. There was no sort and go! The analysis took several weeks in the fall of 2016.

By Haplogroup – Master and Summary Tables

For each sub-haplogroup, I compiled, minimally, the following information shown as an example for haplogroup A with no subgroup:

native-mt-master-chart

The “Previously Proven Native” link is to my article titled Native American Mitochondrial Haplogroups where I maintain an updated list of haplogroups proven or suspected Native, along with the source(s), generally academic papers, for that information.

In some cases, to resolve ambiguity if any remained, I also referenced Phylotree, mtDNA Community and/or GenBank.

For each haplogroup or subgroup within haplogroup, I evaluated and listed the locations for the Genographic “earliest maternal ancestor place of birth” locations, but in the case of the haplogroup A example above, with 4198 responses, the results did not fit into the field so I added the information as supplemental.

By analyzing this information after completing a master tablet for each major haplogroup and subgroups, meaning A, B, C, D and X, I created summary tables provided in the haplogroup sections in this paper.

Family Tree DNA Projects

Another source of haplogroup information is the various mitochondrial DNA projects at Family Tree DNA.

Each project is managed differently, by volunteers, and displays or includes different information publicly. While different information displayed and lack of standardization does present challenges, there is still valuable information available from the public webpages for each mitochondrial haplogroup referenced.

Challenges

The first challenge is haplogroup naming. For those “old enough” to remember when Y DNA haplogroups used to be called by names such as R1b1c and then R1b1a2, as opposed to the current R-M269 – mitochondrial DNA is having the same issue. In other words, when a new branch needs to be added to the tree, or an entire branch needs to be moved someplace else, the haplogroup names can and do change.

In October and November 2016 when I extracted Genographic project data, Family Tree DNA was on Phylotree version 14 and the Genographic Project was on version 16. The information provided in various academic papers often references earlier versions of the phylotree, and the papers seldom indicate which phylotree version they are using. Phylotree is the official name for the mitochondrial DNA haplogroup tree.

Generally, between Phylotree versions, the haplogroup versions, meaning names, such as A1a, remain fairly consistent and the majority of the changes are refinements in haplogroup names where subgroups are added and all or part of A1a becomes A1a1 or A1a2, for example. However, that’s not always true. When new versions are released, some haplogroup names remain entirely unchanged (A1a), some people fall into updated haplogroups as in the example above, and some find themselves in entirely different haplogroups, generally within the same main haplogroup. For example, in Phylotree version 17, all of haplogroup A4 is obsoleted, renamed and shifted elsewhere in the haplogroup A tree.

The good news is that both Family Tree DNA and the Genographic project plan to update to Phylotree V17 in 2017. After that occurs, I plan to “equalize” the results, hopefully “upgrading” the information from academic papers to current haplogroup terminology as well if the authors provided us with the information as to the haplogroup defining mutations that they utilized at publication along with the entire list of sample mutations.

A second challenge is that not all haplogroup projects are created equal. In fact, some are entirely closed to the public, although I have no idea why a haplogroup project would be closed. Other projects show only the map. Some show surnames but not the oldest ancestor or location. There was no consistency between projects, so the project information is clearly incomplete, although I utilized both the public project pages and maps together to compile as much information as possible.

A third challenge is that not every participant enters their most distant ancestor (correctly) nor their ancestral location, which reduces the relevance of results, whether inside of projects, meaning matches to individual testers, or outside of projects.

A fourth challenge is that not every participant enables public project sharing nor do they allow the project administrators to view their coding region results, which makes participant classification within projects difficult and often impossible.

A fifth challenge is that in Family Tree DNA mitochondrial projects, not everyone has tested to the full sequence level, so some people who are noted as base haplogroup “A,” for example, would have a more fully defined haplogroup is they tested further. On the other hand, for some people, haplogroup A is their complete haplogroup designation, so not all designations of haplogroup A are created equal.

A sixth challenge is that in the Genographic Project, everyone has been tested via probes, meaning that haplogroup defining mutation locations are tested to determine full haplogroups, but not all mitochondrial locations are not tested. This removes the possibility of defining additional haplogroups by grouping participants by common mutations outside of haplogroup defining mutations.

A seventh challenge is that some resources for mitochondrial DNA list haplogroup mutations utilizing the CRS (Cambridge Reference Sequence) model and some utilize the RSRS (Reconstructed Sapiens Reference Sequence) model, meaning that the information needs to be converted to be useful.

Resources

Let’s look at the resources available for each resource type utilized to gather information.

native-mt-resources

The table above summarizes the differences between the various sources of information regarding mitochondrial haplogroups.

Before we look at each Native American haplogroup, let’s look at common myths, family stories and what constitutes proof of Native ancestry.

Family Stories

In the US, especially in families with roots in Appalachia, many families have the “Cherokee” or “Indian Princess” story. The oral history is often that “grandma” was an “Indian princess” and most often, Cherokee as well. That was universally the story in my family, and although it wasn’t grandma, it was great-grandma and every single line of the family carried this same story. The trouble was, it proved to be untrue.

Not only did the mitochondrial DNA disprove this story, the genealogy also disproved it, once I stopped looking frantically for any hint of this family line on the Cherokee rolls and started following where the genealogy research indicated. Now, of course this isn’t to say there is no Native IN that line, but it is to say that great-grandma’s direct matrilineal (mitochondrial) line is NOT Native as the family story suggests. Of course family stories can be misconstrued, mis-repeated and embellished, intentionally or otherwise with retelling.

Family stories and myths are often cherished, having been handed down for generations, and die hard.

In fact, today, some unscrupulous individuals attempt to utilize the family myths of those who “self-identify” their ancestor as “Cherokee” and present the myths and resulting non-Native DNA haplogrouip results as evidence that European and African haplogroups are Native American. Utilizing this methodology, they confirm, of course, that everyone with a myth and a European/African haplogroup is really Native after all!

As the project administrator of several projects including the American Indian and Cherokee projects, I can tell you that I have yet to find anyone who has a documented, as in proven lineage, to a Native tribe on a matrilineal line that does not have a Native American haplogroup. However, it’s going to happen one day, because adoptions of females into tribes did occur, and those adopted females were considered to be full tribal members. In this circumstance, your ancestor would be considered a tribal member, even if their DNA was not Native.

Given the Native tribal adoption culture, tribal membership of an individual who has a non-Native haplogroup would not be proof that the haplogroup itself was aboriginally Native – meaning came from Asia with the other Native people and not from Europe or Africa with post-Columbus contact. However, documenting tribal membership and generational connectivity via proven documentation for every generation between that tribally enrolled ancestor and the tester would be a first step in consideration of other haplogroups as potentially Native.

In Canada, the typical story is French-Canadian or metis, although that’s often not a myth and can often be proven true. We rely on the mtDNA in conjunction with other records to indicate whether or not the direct matrilineal ancestor was French/European or aboriginal Canadian.

In Mexico, the Caribbean and points south, “Spain” in the prevalent family story, probably because the surnames are predominantly Spanish, even when the mtDNA very clearly says “Native.” Many family legends also include the Canary Islands, a stopping point in the journey from Europe to the Caribbean.

Cultural Pressures

It’s worth noting that culturally there were benefits in the US to being Native (as opposed to mixed blood African) and sometimes as opposed to entirely white. Specifically, the Native people received head-right land payments in the 1890s and early 1900s if they could prove tribal descent by blood. Tribal lands, specifically those in Oklahoma owned by the 5 Civilized Tribes (Cherokee, Choctaw, Chickasaw, Creek and Seminole) which had been previously held by the tribe were to be divided and allotted to individual tribal members and could then be sold. Suddenly, many families “remembered” that they were of Native descent, whether they were or not.

Culturally and socially, there may have been benefits to being Spanish over Native in some areas as well.

It’s also easy to see how one could assume that Spain was the genesis of the family if Spanish was the spoken language – so care had to be exercised when interpreting some Genographic answers. Chinese can be interpreted to mean “China” or at least Asia, meaning, in this case, “not Native,” but Spanish in Mexico or south of the US cannot be interpreted to mean Spain without other correlating information.

Language does not (always) equal origins. Speaking English does not mean your ancestors came from England, speaking Spanish does not mean your ancestors came from Spain and speaking French does not mean your ancestors came from France.

However, if your ancestors lived in a country where the predominant language was English, Spanish or French, and your ancestor lived in a location with other Native people and spoke a Native language or dialect, that’s a very compelling piece of evidence – especially in conjunction with a Native DNA haplogroup.

What Constitutes Proof?

What academic papers use as “proof” of Native ancestry varies widely. In many cases, the researchers don’t make a case for what they use as proof, they simply state that they had one instance of A2x from Mexico, for example. In other cases, they include tribal information, if known. When stated in the papers, I’ve included that information on the Native American Mitochondrial Haplogroups page.

Methodology

I have adopted a similar methodology, tempered by the “guilt by genetic association” guideline, keeping in mind that both FTDNA projects and Genographic project public participants all provide their own genealogy and self-identify. In other words, no researcher traveled to Guatemala and took a cheek swab or blood sample. The academic samples and samples taken by the Genographic Project in the field are not included in the Genographic public data base available to researchers.

However, if the participant and their ancestors noted were all born in Guatemala, there is no reason to doubt that their ancestors were also found in the Guatemala region.

Unfortunately, not everything was that straightforward.

Examples:

  • If there were multiple data base results as subsets of base haplogroups previously known to be Native from Mexico and none from anyplace else in the world, I’m comfortable calling the results “Native.”
  • If there are 3 results from Mexico, and 10 from Europe, especially if the European results are NOT from Spain or Portugal, I’m NOT comfortable identifying that haplogroup as Native. I would identify it as European so long as the oldest date in the date ranges identifying when the haplogroup was born is AFTER the youngest migration date. For example, if the haplogroup was born 5,000 years ago and the last known Beringia migration date is 10,000 years ago, people with the same haplogroup cannot be found both in Europe and the Americas indigenously. If the haplogroup birth date is 20,000 years ago and the migration date is 10,000 years ago, clearly the haplogroup CAN potentially be found on both continents as indigenous.
  • In some cases, we have the reverse situation where the majority of results are from south of the US border, but one or two claim Spanish or Portuguese ancestry, which I suspect is incorrect. In this case, I will call the results Native so long as there are a significant number of results that do NOT claim Spanish or Portuguese ancestry AND none of the actual testers were born in Spain or Portugal.
  • In a few cases, the FTDNA project and/or Genographic data refute or at least challenge previous data from academic papers. Future information may do the same with this information today, especially where the data sample is small.

Because of ambiguity, in the master data table (not provided in this paper) for each base haplogroup, I have listed every one of the sub-haplogroups and all the locations for the oldest ancestors, plus any other information provided when relevant in the actual extracted data.

When in doubt, I have NOT counted a result as Native. When the data itself is questionable or unreliable, I removed the result from the data and count entirely.

I intentionally included all of the information, Native and non-Native, in my master extracted data tables so that others can judge for themselves, although I am only providing summary tables here. Detailed information will be provided in a series of articles or in an academic paper after both the Family Tree DNA data base and the Genographic data base are upgraded to Phylotree V17.

The Haplogroup Summary Table

The summary table format used for each haplogroup includes the following columns and labels:

  • Hap = Haplogroup as listed at Family Tree DNA, in academic papers and in the Genographic project.
  • Previous Academic Proven = Previously proven or cited as Native American, generally in Academic papers. A list of these haplogroups and papers is provided in the article, Native American Mitochondrial Haplogroups.
  • Academic Confirmed = Academic paper haplogroup assignments confirmed by the Genographic Project and/or Family Tree DNA Projects.
  • Previous Suspected = Not academically proven or cited at Native, but suspected through any number of sources. The reasons each haplogroup is suspected is also noted in the article, Native American Mitochondrial DNA Haplogroups.
  • Suspected Confirmed = Suspected Native haplogroups confirmed as Native.
  • FTDNA Project Proven = Mitochondrial haplogroup proven or confirmed through FTDNA project(s).
  • Geno Confirmed = Mitochondrial haplogroup proven or confirmed through the Genographic Project data base.

Color Legend:

native-mt-color-legend

Additional Information:

  • Possibly, probably or uncertain indicates that the data is not clear on whether the haplogroup is Native and additional results are needed before a definitive assignment is made.
  • No data means that there was no data for this haplogroup through this source.
  • Hap not listed means that the original haplogroup is not listed in the Genographic data base indicating the original haplogroup has been obsoleted and the haplogroup has been renamed.

The following table shows only the A haplogroups that have now been proven Native, omitting haplogroups proven not to be Native through this process, although the original master data table (not included here) includes all information extracted including for haplogroups that are not Native. Summary tables show only Native or potentially Native results.

Let’s look at the summary results grouped by major haplogroup.

Haplogroup A

Haplogroup A is the largest Native American haplogroup.

native-mt-hap-a-pie

More than 43% of the individuals who carry Native American mitochondrial DNA fall into a subgroup of A.

Like the other Native American haplogroups, the base haplogroup was formed in Asia.

Family Tree DNA individual participant pages provide participants with both a Haplogroup Frequency Map, shown above, and a Haplogroup Migration Map, shown below.

native-mt-migration

The Genographic project provides heat maps showing the distribution of major haplogroups on a continental level. You can see that, according to this heat map from when the Genographic Project was created, the majority of haplogroup A is found in the northern portion of the Americas.

native-mt-hap-a-heat

Additionally, the Genographic Project data base also provides a nice tree structure for each haplogroup, beginning with Mitochondrial Eve, in Africa, noted as the root, and progressing to the current day haplogroups.

native-mt-hap-a-tree-root

native-mt-hap-a-tree

Haplogroup A Projects

I enjoy the added benefit of being one of the administrators, along with Marie Rundquist, of the haplogroup A project at Family Tree DNA, as well as the A10, A2 and A4 projects. However, in this paper, I only included information available on the projects’ public pages and not information participants sent to the administrators privately.

The Haplogroup A Project at Family Tree DNA is a public project, meaning available for anyone with haplogroup A to join, and fully publicly viewable with the exception of the participant’s surname, since that is meaningless when the surname traditionally changes with every generation. However, both the results, complete with the Maternal Ancestor Name, and the map, are visible. HVR1 and HVR2 results are displayed, but coding region results are never available to be shown in projects, by design.

native-mt-hap-a-project

The map below shows all participants for the entire project who have entered a geographic location. The three markers in the Middle East appear to be mis-located, a result of erroneous user geographic location input. The geographic locations are selected by participants indicating the location of their most distant mitochondrial ancestor. All 3 are Spanish surnames and one is supposed to be in Mexico. Please disregard those 3 Middle Eastern pins on the map below.

native-mt-hap-a-project-map

Haplogroup A Summary Table

The subgroups of haplogroup A and the resulting summary data are shown in the table below.

native-mt-hap-a-chart-1

native-mt-hap-a-chart-2

native-mt-hap-a-chart-3

  • Total haplogroups Native – 75
  • Total haplogroups uncertain – 1
  • Total haplogroups probable – 1
  • Total new Native haplogroups – 38, 1 probable.
  • Total new Native haplogroups proven by FTDNA Projects – 9, 1 possibly
  • Total new Native haplogroups proven by Genographic Project – 35, 1 probable

Haplogroup B

Haplogroup B is the second largest Native American haplogroup, with 23.53% of Native participants falling into this haplogroup.

native-mt-hap-b-pie

The Genographic project provides the following heat map for haplogroup B4, which includes B2, the primary Native subgroup.

native-mt-hap-b-heat

The haplogroup B tree looks like this:

native-mt-hap-b-tree-root

native-mt-hap-b-tree

native-mt-hap-b-tree-2

B4 and B5 are main branches.

You will note below that B2 falls underneath B4b.

native-mt-hap-b-tree-3

Haplogroup B Projects

At Family Tree DNA, there is no haplogroup B project, but there is a haplogroup B2 project, which is where the majority of the Native results fall. Haplogroup B Project administrators have included a full project display, along with a map. All of the project participants are shown on the map below.

native-mt-hap-b-project-map

Please note that the pins colored other than violet (haplogroup B) should not be shown in this project. Only haplogroup B pins are violet.

Haplogroup B Summary Table

native-mt-hap-b-chart-1

native-mt-hap-b-chart-2

  • Total haplogroups Native – 63
  • Total haplogroups refuted – 1
  • Total new Native haplogroups – 43
  • Total new Native haplogroups proven by Family Tree DNA projects – 12
  • Total new Native haplogroups proven by Genographic Project – 41

Haplogroup C

Haplogroup C is the third largest Native haplogroup with 22.99% of the Native population falling into this haplogroup.

native-mt-hap-c-pie

Haplogroup C is primarily found in Asia per the Genographic heat map.

native-mt-hap-c-heat

The haplogroup C tree is as follows:

native-mt-hap-c-root

native-mt-hap-c-tree-1

native-mt-hap-c-tree-2

Haplogroup C Project

Unfortunately, at Family Tree DNA, the haplogroup C project has not enabled their project pages, even for project members.

When I first began compiling this data, the Haplogroup C project map was viewable.

native-mt-hap-c-project-map-world

Haplogroup C Summary Table

native-mt-hap-c-chart-1

native-mt-hap-c-chart-2

  • Total haplogroups Native – 61
  • Total haplogroups refuted – 2
  • Total haplogroups possible – 1
  • Total haplogroups probable – 1
  • Total new Native haplogroups – 8
  • Total new Native haplogroups proven by Family Tree DNA projects – 6
  • Total new Native haplogroups proven by Genographic Project – 5, 1 possible, 1 probable

Haplogroup D

Haplogroup D is the 4th largest, or 2nd smallest Native haplogroup, depending on your point of view, with 6.38% of Native participants falling into this haplogroup.

native-mt-hap-d-pie

Haplogroup D is found throughout Asia, into Europe and throughout the Americas.

native-mt-hap-d-heat

Haplogroups D1 and D2 are the two subgroups primarily found in the New World.

native-mt-hap-d-heat-d1

The haplogroup D1 heat map is shown above and D2 is shown below.

native-mt-hap-d-heat-d2

The Tree for haplogroup D is a subset of M.

native-mt-hap-d-tree-root

Haplogroup D begins as a subhaplogroup of M80..

native-mt-hap-d-tree-2

Haplogroup D Projects

D is publicly viewable, but shows testers last name, no ancestor information and no location, so I utilized maps once again.

native-mt-hap-d-project-map

Haplogroup D Summary Table

native-hap-d-chart-1

native-hap-d-chart-2

  • Total haplogroups Native – 50
  • Total haplogroups possibly both – 3
  • Total haplogroups uncertain – 2
  • Total haplogroups probable – 1
  • Total haplogroups refuted – 3
  • Total new Native Haplogroups – 25
  • Total new Native haplogroups proven by Family Tree DNA projects – 2
  • Total new Native haplogroups proven by Genographic Project – 22, 1 probably

Haplogroup X

Haplogroup X is the smallest of the known Native base haplogroups.

native-mt-hap-x-pie

Just over 3% of the Native population falls into haplogroup X.

The heat map for haplogroup X looks very different than haplogroups A-D.

native-mt-hap-x-heat

The tree for haplogroup X shows that it too is also a subgroup of M and N.

native-mt-hap-x-root

native-mt-hap-x-tree

Haplogroup X Project

At Family Tree DNA, the Haplogroup X project is visible, but with no ancestral locations displayed. I utilized the map, which was visible.

native-mt-hap-x-project-map

This map of the entire haplogroup X project tells you immediately that the migration route for Native X was not primarily southward, but east. Haplogroup X is found primarily in the US and in the eastern half of Canada.

Haplogroup X Summary Table

native-mt-hap-x-chart

  • Total haplogroups Native – 10
  • Total haplogroups uncertain, possible or possible both Native and other – 8
  • Total New Native haplogroups – 0

Haplogroup M

Haplogroup M, a very large, old haplogroup with many subgroups, is not typically considered a Native haplogroup.

The Genographic project shows the following heat map for haplogroup M.

native-mt-hap-m-heat

The heat map for haplogroup M includes both North and South America, but according to Dr. Miguel Vilar, Science Manager for the Genographic Project, this is because both haplogroups C and D are subsets of M.

native-mt-hap-m-migration

The haplogroup M migration map from the Genographic Project shows haplogroup M expanding across southern Asia.

native-mt-hap-m-root

The tree for haplogroup M, above, is abbreviated, without the various subgroups being expanded.

native-mt-hap-m1-tree

The M1 and M1a1e haplogroups shown above are discussed in the following section, as is M18b, below.

native-mt-hap-m18b-tree

The Haplogroup M Project

The haplogroup M project at Family Tree DNA shows the worldwide presence of haplogroup M and subgroups.

native-mt-hap-m-project-map

Native Presence

Haplogroup M was originally reported in two Native burials in the Americas. Dr. Ripan Malhi reported haplogroup M (excluding M7, M8 and M9) from two separate skeletons from the same burial in China Lake, British Columbia, Canada, about 150 miles north of the Washington State border, dating from about 5000 years ago. Both skeletons were sequenced separately in 2007, with identical results and are believed to be related.

While some researchers are suspicious of these findings as being incomplete, a subsequent paper in 2013, Ancient DNA-Analysis of Mid-Holocene Individuals from the Northwest Coast of North America Reveals Different Evolutionary Paths for Mitogenomes, which included Mahli as a co-author states the following:

Two individuals from China Lake, British Columbia, found in the same burial with a radiocarbon date of 4950+/−170 years BP were determined to belong to a form of macrohaplogroup M that has yet to be identified in any extant Native American population [24], [26]. The China Lake study suggests that individuals in the early to mid-Holocene may exhibit mitogenomes that have since gone extinct in a specific geographic region or in all of the Americas.

Haplogroup M Summary Table

native-mt-hap-m-chart

One additional source for haplogroup M was found in GenBank noted as M1a1e “USA”, but there were also several Eurasian submissions for M1a1e as well. However, Doron Behar’s dates for M1a1e indicate that the haplogroup was born about 9,813 years ago, plus or minus 4,022 years, giving it a range of 5,971 to 13,835 years ago, meaning that M1a1e could reasonably be found in both Asia and the Americas. There were no Genographic results for M1a1e. At this point, M1a1e cannot be classified as Native, but remains on the radar.

Hapologroup M1 was founded 23,679 years ago +-4377 years. It is found in the Genographic Project in Cuba, Venezuela and is noted as Native in the Midwest US. M1 is also found in Colorado and Missouri in the haplogroup M project at Family Tree DNA, but the individuals did not have full sequence tests nor was additional family information available in the public project.

The following information is from the master data table for haplogroup M potentially Native haplogroups.

Haplogroup M Master Data Table for Potentially Native Haplogroups

The complete master data tables includes all subhaplogroups of M, the partial table below show only the Native haplogroups.

native-mt-hap-m-chart-1

native-mt-hap-m-master-data-chart-2

Haplogroup M18b is somewhat different in that two individuals with this haplogroup at Family Tree DNA have no other matches.  They both have a proven connection to Native families from interrelated regions in North Carolina.

I initiated communications with both individuals who tested at Family Tree DNA who subsequently provided their genealogical information. Both family histories reach back into the late 1700s, one in the location where the Waccamaw were shown on maps in in the early 1700s, and one near the border of Virginia and NC. One participant is a member of the Waccamaw tribe today. A family migration pattern exists between the NC/VA border region and families to the Waccamaw region as well. An affidavit exists wherein the family of the individual from the NC/VA border region is sworn to be “mixed” but with no negro blood.

In summary:

  • Haplogroups M and M1 could easily be both Native as well as Asian/European, given the birth age of the haplogroup.
  • Haplogroup M1a1e needs additional results.
  • Haplogroup M18b appears to be Native, but could also be found elsewhere given the range of the haplogroup birth age. Additional proven Native results could bolster this evidence.
  • In addition to the two individuals with ancestors from North Carolina, M18b is also reported in a Sioux individuals with mixed race ethnicity

The Dark Horse Late Arrival – Haplogroup F

I debated whether I should include this information, because it’s tenuous at best.

The American Indian project at Family Tree DNA includes a sample of F1a1 full sequence result whose most distant matrilineal ancestor is found in Mexico.

Haplogroup F is an Asian haplogroup, not found in Europe or in the Americas.

native-mt-hap-f-heat

native-mt-hap-f-migration

Haplogroup F, according to the Genographic Project, expands across central and southern Asia.

native-mt-hap-f-root

native-mt-hap-f1a1-tree

According to Doron Behar, F1a1 was born about 10,863 years ago +- 2990 years, giving it a range of 7,873 – 13,853.

Is this Mexican F1a1 family Native? If not, how did F1a1 arrive in Mexico, and when? F1a1 is not found in either Europe or Africa.

In August, 2015, an article published in Science, Genomic evidence for the Pleistocene and recent population history of Native Americans by Raghaven et al suggested that a secondary migration occurred from further south in Asia, specifically the Australo-Melanesians, as shown in the diagram below from the paper. If accurate, this East Asian migration originating further south could explain both the haplogroup M and F results.

native-mt-nature-map

A second paper, published in Nature in September 2015 titled Genetic evidence for two founding populations of the Americas by Skoglund et al says that South Americans share ancestry with Australasian populations that is not seen in Mesoamericans or North Americans.

The Genographic project has no results for F1a1 outside of Asia.

I have not yet extracted the balance of haplogroup F in the Genographic project to look for other indications of haplogroups that could potentially be Native.

Haplogroup F Project

The haplogroup F project at Family Tree DNA shows no participants in the Americas, but several in Asia, as far south as Indonesia and also into southern Europe and Russia.

native-mt-hap-f-project-map

Haplogroup F Summary Table

native-mt-hap-f-chart

Haplogroup F1a1 deserves additional attention as more people test and additional samples become available.

Native Mitochondrial Haplogroup Summary

Research in partnership with the Genographic Project as well as the publicly available portions of the projects at Family Tree DNA has been very productive. In total, we now have 259 proven Native haplogroups. This research project has identified 114 new Native haplogroups, or 44% of the total known haplogroups being newly discovered within the Genographic Project and the Family Tree DNA projects.

native-mt-hap-summary

Acknowledgements

Haplogroup X2b4 is European, Not Native American

For many years, there has been a quandary in the genealogy community relative to the genesis of mitochondrial haplogroup X2b4.

The source of this question was the mitochondrial DNA test results of several of Radegonde Lambert’s descendants.

Radegonde Lambert, an Acadian woman, was born about 1621, possibly in Cap-de-Sable, Acadia according to the compiled research of professional genealogist Karen Theriot Reader.  She is thought by some to be the daughter of Jean Lambert, born in France but one of the original Acadian settlers, and a female reported to be a Mi’kmaq (Micmac) Indian, but with no confirmed documentation, despite years of looking.  An alternate origin for Radegonde is that she came to Acadia with her French husband, Jean Blanchard.

The DNA results of Radegonde’s direct matrilineal descendants proved to be haplogroup X2b4, but unfortunately, for a very long time, the ONLY people who took the full sequence mitochondrial DNA and had that haplogroup were descendants of Radegonde or people who did not know where their most distant matrilineal ancestor was originally from. So, the answer was to wait on additional test results – in other words, for more people to test.

Recently, I had reason to look at the results of one of Radegonde’s descendants again, and discovered that enough time has elapsed that new results are in, and based on full sequence matches and other evidence, it appears that X2b4 is indeed European and not Native.

X2b4 Mutations

Haplogroup X2b4 is characterized by several distinctive mutations, as follows.

Haplogroup or Subgroup Required Mutations
X T6221C, C6371T, A13966G, T14470C, T16189C!, C16278T!
X2 T195C!, G1719A
X2b C8393T, G15927A
X2b4 G3705A

Of the above mutations, only two, the mutations at 16189 and at 16278 are found in the HVR1 region, and only the mutation at 195 is found in the HVR2 region. The balance of these mutations are found in the coding region, so a haplogroup cannot be predicted at a higher level that X or perhaps X2 without the full sequence test.

Radegonde’s Mutations

Radegonde’s descendants carry all of these haplogroup defining mutations, and more. In fact, Radegonde’s descendants also have extra mutations at locations 16145 and 16301. We know this because at least a dozen of Radegonde’s descendants match exactly at the full sequence level, with no mutations. In other words, in those descendants, Radegonde’s mitochondrial DNA has remained unchanged for just shy of 400 years – and because they all match exactly, we know what Radegonde’s mitochondrial DNA looked like.

Turning now to other full sequence matches, we find that one of the individuals who matches Radegonde’s descendant with 3 mutations difference is from East Anglia in England, and his ancestors have never lived outside of England. In other words, this isn’t a case of someone whose ancestors immigrated and they may have incorrect genealogy.

Two more full sequence matches live in Norway and their ancestors have never lived elsewhere.

One match’s ancestor, Ally Lyon was born and married in Glenisa, Scotland in 1760.

Another match was born and lives in Germany and her ancestors were born there as well.

In summary, for matches, other than Radegonde and people who don’t know where their match was from, we have ancestors proven to be born in:

  • East Anglia
  • Norway
  • Norway
  • Glenisa, Scotland
  • Germany

Of Radegonde’s descendant’s matches, 5 individuals who tested still live in the country or location where their ancestor was born and their family/ancestors have never lived elsewhere.

Furthermore, there are no Native American mitochondrial DNA matches for haplogroup X2b or X2b4 in either contemporary testers or ancient burials

Base Haplogroups

It’s certainly possible and feasible for Native people to have base haplogroup matches from locations other than America, meaning haplogroup X in this case, but not for full sequence haplogroup matches, like X2b4, which suggest a common ancestor in a much closer timeframe.

Looking at the history of the migration of the Native people, if haplogroup X2b4 was indeed Native, and matched people in Europe, that would mean that haplogroup X2b4 would have been born more than 12,000 years ago when it’s believed that the Native people crossed the land bridge from Asia to the Americas. In order for migration to both the Americas and Europe from a common location to occur, probably in the Altai region of Asia, that date would probably have to be pushed back further, probably more in the range of 15,000 to 25,000 years ago to a common ancestor for descendants to be found in both the New World and Europe. It just isn’t feasible that haplogroup X2b4 was born that long ago.

When Was Haplogroup X Born?

Dr. Doron Behar in the supplement to his publication, “A Copernican” Reassessment of the Human Mitochondrial DNA Tree from its Root” provides the creation dates for haplogroup X through X2b4 as follows:

Haplogroup Created Years Ago Statistical Variance
X 31,718.5 11,709.2
X2 19,233.8 2640.9
X2b 9675.9 2466.0
X2b4 5589.2 2597.2

Statistical variance, in this instance means plus or minus, so this chart would read that haplogroup X was born 31,718 years ago plus or minus 11,709 years, so most likely 31,718 years ago, but sometime between 20,639 and 42,979 years ago. Think of a bell shaped curve with 31,718 in the center, or the highest part of the peak.

X2, on the other hand, was born roughly 19,000 years ago. We do know that haplogroup X2a is indeed Native, as is X2g and possibly X2e. So some of haplogroup X2 went east, incurring mutations that would become Native American haplogroup X2a, X2g and possibly X2e while others went west, winding up in Europe and incurring mutations that would become haplogroup X2b and subclades.

The X2b4 Project

Moving now to the X2b4 haplogroup project at Family Tree DNA, in addition to the X2b4 matches mentioned above for Radegonde’s descendants, we find other occurrences of X2b4 in:

  • The Czech Republic
  • Devon in the UK
  • Birmingham in the UK

The three locations in France, shown on the map below, are individuals who descend from Radegonde Lambert and believe her most distant ancestor to be French, so that is what they entered in their “most distant ancestor” location.

Other locations on the map (below) not noted as X2b4 (above) are X2b, the parent haplogroup of X2b4.

x2b4

Taking a look at the map, below, from the larger haplogroup X project that includes all of haplogroup X and all subclades, we see that haplogroup X is found widely in Europe, including X, X2 and X2b, among other subclades.

mtdna-x-project

National Geographic, Genographic Project

As a National Geographic affiliated researcher, I am privileged to have research access to the Genogaphic Project data base of just under 900,000 international participants.  While the identity of the participants is not held in the data base, their ancestor information, as they have provided, is included.  For haplogroup X2b4, there were 62 results, indicating just how rare this haplogroup is worldwide.  Unfortunately, not everyone provided the place of birth for their earliest known maternal ancestor.

Of the 37 individuals who did provide a birth location for their earliest maternal ancestor, none were Native American and the following locations for places of birth for their earliest maternal ancestor were listed, other than the United States and Canada.  Many of the participants and their grandparents are still living in the regions where their ancestors were born:

  • Ireland
  • Czech
  • Serbia
  • Germany (6)
  • France (2)
  • Denmark
  • Switzerland
  • Russia
  • Warsaw, Poland
  • Norway
  • Romania
  • England (2)
  • Slovakia
  • Scotland (2)

Conclusion

As you can see, based on Radegonde’s descendants full sequence matches in multiple European locations, Dr. Behar’s paper dating the birth of haplogroup X2b4 to approximately 5500 years ago, the Genographic Project X2b4 locations and other X2b and X2b4 haplogroup project members’ matches in Europe, it’s impossible for X2b4 to be Native American.

Therefore, Radegonde Lambert did not have a Native mother. Her mother was very probably French, like the rest of the Acadian immigrants.

Acknowledgements

I would like to thank:

  • nat-geo-logoNational Geographic Society Genographic Project and Dr. Miguel Vilar, Science Manager
  • My Haplogroup X2b4 project co-administrators, Marie Rundquist and Tom Glad
  • The haplogroup X project administrators, Carolyn Benson and Tom Glad
  • Radegonde Lambert’s descendants and others for testing, joining projects, and making their results public for all to share. Without public projects and results, discoveries like this would not be possible.
  • Family Tree DNA for providing the projects and support that enables us to further both scientific and genealogical research.

Further Analysis of Native American Haplogroup C-P39 Planned

Haplogroup C is one of two Native American male haplogroups. More specifically, one specific branch of the haplogroup C tree is Native American which is defined by mutation C-P39 (formerly known as C3b).  Ray Banks shows this branch (highlighted in yellow) along with sub-branches underneath on his tree:

C-P39 Ray Banks Tree

Please note that if you are designated at 23andMe as Y haplogroup C3e, you are probably C-P39. We encourage you to purchase the Y DNA 111 marker test at Family Tree DNA and join the haplogroup C and C-P39 projects.

It was only 11 years, ago in 2004 in the Zegura study, that C-P39 was reported among just a few Native American men in the Plains and Southwest.  Since that time The American Indian DNA project, surname projects and the AmerIndian Ancestry Out of Acadia DNA projects have accumulated samples that span the Canadian and American borders, reaching west to east, so haplogroup C-P39 is not relegated to the American Southwest.  It is, however, still exceedingly rare.

In August of 2012, Marie Rundquist, co-administrator of the haplogroup C-P39 DNA project performed an analysis and subsequent report of the relationships, both genealogical and genetic, of the C-P39 project members.  One of the burning questions is determining how far back in time the common ancestor of all of the C-P39 group members lived.

C-P39 MCRA

When Marie performed the first analysis, in 2012,, there were only 14 members in the project, representing 6 different families, and they had only tested to 67 markers. Most were from Canada.

C-P39 countries

My, how things have changed. We now have more participants, more markers to work with and additional tests to bring to bear on the questions of relatedness, timing and origins.

Today, there are a total of 43 people in the project and their locations include the Pacific Northwest, Appalachia, the Southwest and all across Canada, west to east.

If you are haplogroup C-P39 or C3e at 23andMe, please join the C-P39 project at Family Tree DNA today.  I wrote about how to join a project here, but if you need assistance, just let me know in a comment to the blog and Marie or I will contact you.  (Quick Instructions: sign on to your FTDNA account, click on projects tab on upper left toolbar, click on join, scroll down to Y haplogroup projects, click on C, select C-P39 project and click through to press orange join button.)

Marie is preparing to undertake a new analysis and provides the following announcement:

The C-P39 Y DNA project is pleased to announce a forthcoming updated and revised project report.  The C-P39 project has established a 111-marker baseline for our 2016 study and analysis will include:

  • 111 marker result comparisons
  • geo-locations
  • tribal / family relationships
  • C P39 SNP findings
  • new SNPs and Big Y results

The current C-P39 Y DNA study has a healthy diversity of surnames, geo-locations, and tribal / family lines represented.

The C-P39 Y DNA project will cover the costs of the necessary 111 marker upgrades by way of Family Tree DNA C-P39 Y DNA study project fund.

Thanks to all who have contributed to the project fund and to participants who have funded their own tests to 111 markers as part of our study.  To voluntarily contribute (anonymously if you like) to the C-P39 Y DNA project funds and help our project achieve this goal, please click on the link below and please do make certain that the “C-P39 Y-DNA” pre-selected project is highlighted when you do:

https://www.familytreedna.com/group-general-fund-contribution.aspx?g=Y-DNAC-P39

Thank you to project members contributing DNA test results to the C-P39 study and for encouraging friends and relatives to do the same!  Thank you also to Family Tree DNA management for their ongoing support.

The project needs to raise $3164 to upgrade all project members to 111 markers.  Many participants have already upgraded their own results, for which we are very grateful, but we need all project members at the 111 level if possible.

Please help fund this scientific project if you can.  Every little bit helps.  I’m going to start by making a donation right now!  You can make the donation in memory or in honor of someone or a particular ancestor – or you can be completely anonymous.  Please click on the link above to make your contribution!!!  We thank you and the scientific community thanks you.

The Best and Worst of 2015 – Genetic Genealogy Year in Review

2015 Best and Worst

For the past three years I’ve written a year-in-review article. You can see just how much the landscape has changed in the 2012, 2013 and 2014 versions.

This year, I’ve added a few specific “award” categories for people or firms that I feel need to be specially recognized as outstanding in one direction or the other.

In past years, some news items, announcements and innovations turned out to be very important like the Genographic Project and GedMatch, and others, well, not so much. Who among us has tested their full genome today, for example, or even their exome?  And would you do with that information if you did?

And then there are the deaths, like the Sorenson database and Ancestry’s own Y and mitochondrial data base. I still shudder to think how much we’ve lost at the corporate hands of Ancestry.

In past years, there have often been big new announcements facilitated by new technology. In many ways, the big fish have been caught in a technology sense.  Those big fish are autosomal DNA and the Big Y types of tests.  Both of these have created an avalanche of data and we, personally and as a community, are still trying to sort through what all of this means genealogically and how to best utilize the information.  Now we need tools.

This is probably illustrated most aptly by the expansion of the Y tree.

The SNP Tsunami Growing Pains Continue

2015 snp tsunami

Going from 800+ SNPs in 2012 to more than 35,000 SNPs today has introduced its own set of problems. First, there are multiple trees in existence, completely or partially maintained by different organizations for different purposes.  Needless to say, these trees are not in sync with each other.  The criteria for adding a SNP to the tree is decided by the owner or steward of that tree, and there is no agreement as to the definition of a valid SNP or how many instances of that SNP need to be in existence to be added to the tree.

This angst has been taking place for the most part outside of the public view, but it exists just the same.

For example, 23andMe still uses the old haplogroup names like R1b which have not been used in years elsewhere. Family Tree DNA is catching up with updating their tree, working with haplogroup administrators to be sure only high quality, proven SNPs are added to branches.  ISOGG maintains another tree (one branch shown above) that’s publicly available, utilizing volunteers per haplogroup and sometimes per subgroup.  Other individuals and organizations maintain other trees, or branches of trees, some very accurate and some adding a new “branch” with as little as one result.

The good news is that this will shake itself out. Personally, I’m voting for the more conservative approach for public reference trees to avoid “pollution” and a lot of shifting and changing downstream when it’s discovered that the single instance of a SNP is either invalid or in a different branch location.  However, you have to start with an experimental or speculative tree before you can prove that a SNP is where it belongs or needs to be moved, so each of the trees has its own purpose.

The full trees I utilize are the Family Tree DNA tree, available for customers, the ISOGG tree and Ray Banks’ tree which includes locations where the SNPs are found when the geographic location is localized. Within haplogroup projects, I tend to use a speculative tree assembled by the administrators, if one is available.  The haplogroup admins generally know more about their haplogroup or branch than anyone else.

The bad news is that this situation hasn’t shaken itself out yet, and due to the magnitude of the elephant at hand, I don’t think it will anytime soon. As this shuffling and shaking occurs, we learn more about where the SNPs are found today in the world, where they aren’t found, which SNPs are “family” or “clan” SNPs and the timeframes in which they were born.

In other words, this is a learning process for all involved – albeit a slow and frustrating one. However, we are making progress and the tree becomes more robust and accurate every year.

We may be having growing pains, but growing pains aren’t necessarily a bad thing and are necessary for growth.

Thank you to the hundreds of volunteers who work on these trees, and in particular, to Alice Fairhurst who has spearheaded the ISOGG tree for the past nine years. Alice retired from that volunteer position this year and is shown below after receiving two much-deserved awards for her service at the Family Tree DNA Conference in November.

2015 ftdna fairhurst 2

Best Innovative Use of Integrated Data

2015 smileDr. Maurice Gleeson receives an award this year for the best genealogical use of integrated types of data. He has utilized just about every tool he can find to wring as much information as possible out of Y DNA results.  Not only that, but he has taken great pains to share that information with us in presentations in the US and overseas, and by creating a video, noted in the article below.  Thanks so much Maurice.

Making Sense of Y Data

Estes pedigree

The advent of massive amounts of Y DNA data has been both wonderful and perplexing. We as genetic genealogists want to know as much about our family as possible, including what the combination of STR and SNP markers means to us.  In other words, we don’t want two separate “test results” but a genealogical marriage of the two.

I took a look at this from the perspective of the Estes DNA project. Of course, everyone else will view those results through the lens of their own surname or haplogroup project.

Estes Big Y DNA Results
https://dna-explained.com/2015/03/26/estes-big-y-dna-results/

At the Family Tree DNA Conference in November, James Irvine and Maurice Gleeson both presented sessions on utilizing a combination of STR and SNP data and various tools in analyzing their individual projects.

Maurice’s presentation was titled “Combining SNPs, STRs and Genealogy to build a Surname Origins Tree.”
http://www.slideshare.net/FamilyTreeDNA/building-a-mutation-history-tree

Maurice created a wonderful video that includes a lot of information about working with Y DNA results. I would consider this one of the very best Y DNA presentations I’ve ever seen, and thanks to Maurice, it’s available as a video here:
https://www.youtube.com/watch?v=rvyHY4R6DwE&feature=youtu.be

You can view more of Maurice’s work at:
http://gleesondna.blogspot.com/2015/08/genetic-distance-genetic-families.html

James Irvine’s presentation was titled “Surname Projects – Some Fresh Ideas.” http://www.slideshare.net/FamilyTreeDNA/y-dna-surname-projects-some-fresh-ideas

Another excellent presentation discussing Y DNA results was “YDNA maps Scandinavian Family Trees from Medieval Times and the Viking Age” by Peter Sjolund.
http://www.slideshare.net/FamilyTreeDNA/ydna-maps-scandinavian-family-trees-from-medieval-times-and-the-viking-age

Peter’s session at the genealogy conference in Sweden this year was packed. This photo, compliments of Katherine Borges, shows the room and the level of interest in Y-DNA and the messages it holds for genetic genealogists.

sweden 2015

This type of work is the wave of the future, although hopefully it won’t be so manually intensive. However, the process of discovery is by definition laborious.  From this early work will one day emerge reproducible methodologies, the fruits of which we will all enjoy.

Haplogroup Definitions and Discoveries Continue

A4 mutations

Often, haplogroup work flies under the radar today and gets dwarfed by some of the larger citizen science projects, but this work is fundamentally important. In 2015, we made discoveries about haplogroups A4 and C, for example.

Haplogroup A4 Unpeeled – European, Jewish, Asian and Native American
https://dna-explained.com/2015/03/05/haplogroup-a4-unpeeled-european-jewish-asian-and-native-american/

New Haplogroup C Native American Subgroups
https://dna-explained.com/2015/03/11/new-haplogroup-c-native-american-subgroups/

Native American Haplogroup C Update – Progress
https://dna-explained.com/2015/08/25/native-american-haplogroup-c-update-progress/

These aren’t the only discoveries, by any stretch of the imagination. For example, Mike Wadna, administrator for the Haplogroup R1b Project reports that there are now over 1500 SNPs on the R1b tree at Family Tree DNA – which is just about twice as many as were known in total for the entire Y tree in 2012 before the Genographic project was introduced.

The new Y DNA SNP Packs being introduced by Family Tree DNA which test more than 100 SNPs for about $100 will go a very long way in helping participants obtain haplogroup assignments further down the tree without doing the significantly more expensive Big Y test. For example, the R1b-DF49XM222 SNP Pack tests 157 SNPs for $109.  Of course, if you want to discover your own private line of SNPs, you’ll have to take the Big Y.  SNP Packs can only test what is already known and the Big Y is a test of discovery.

                       Best Blog2015 smile

Jim Bartlett, hands down, receives this award for his new and wonderful blog, Segmentology.

                             Making Sense of Autosomal DNA

segmentology

Our autosomal DNA results provide us with matches at each of the vendors and at GedMatch, but what do we DO with all those matches and how to we utilize the genetic match information? How to we translate those matches into ancestral information.  And once we’ve assigned a common ancestor to a match with an individual, how does that match affect other matches on that same segment?

2015 has been the year of sorting through the pieces and defining terms like IBS (identical by state, which covers both identical by population and identical by chance) and IBD (identical by descent). There has been a lot written this year.

Jim Bartlett, a long-time autosomal researcher has introduced his new blog, Segmentology, to discuss his journey through mapping ancestors to his DNA segments. To the best of my knowledge, Jim has mapped more of his chromosomes than any other researcher, more than 80% to specific ancestors – and all of us can leverage Jim’s lessons learned.

Segmentology.org by Jim Bartlett
https://dna-explained.com/2015/05/12/segmentology-org-by-jim-bartlett/

When you visit Jim’s site, please take a look at all of his articles. He and I and others may differ slightly in the details our approach, but the basics are the same and his examples are wonderful.

Autosomal DNA Testing – What Now?
https://dna-explained.com/2015/08/07/autosomal-dna-testing-101-what-now/

Autosomal DNA Testing 101 – Tips and Tricks for Contact Success
https://dna-explained.com/2015/08/11/autosomal-dna-testing-101-tips-and-tricks-for-contact-success/

How Phasing Works and Determining IBS vs IBD Matches
https://dna-explained.com/2015/01/02/how-phasing-works-and-determining-ibd-versus-ibs-matches/

Just One Cousin
https://dna-explained.com/2015/01/11/just-one-cousin/

Demystifying Autosomal DNA Matching
https://dna-explained.com/2015/01/17/demystifying-autosomal-dna-matching/

A Study Using Small Segment Matching
https://dna-explained.com/2015/01/21/a-study-utilizing-small-segment-matching/

Finally, A How-To Class for Working with Autosomal Results
https://dna-explained.com/2015/02/10/finally-a-how-to-class-for-working-with-autosomal-dna-results/

Parent-Child Non-Matching Autosomal DNA Segments
https://dna-explained.com/2015/05/14/parent-child-non-matching-autosomal-dna-segments/

A Match List Does Not an Ancestor Make
https://dna-explained.com/2015/05/19/a-match-list-does-not-an-ancestor-make/

4 Generation Inheritance Study
https://dna-explained.com/2015/08/23/4-generation-inheritance-study/

Phasing Yourself
https://dna-explained.com/2015/08/27/phasing-yourself/

Autosomal DNA Matching Confidence Spectrum
https://dna-explained.com/2015/09/25/autosomal-dna-matching-confidence-spectrum/

Earlier in the year, there was a lot of discussion and dissention about the definition of and use of small segments. I utilize them, carefully, generally in conjunction with larger segments.  Others don’t.  Here’s my advice.  Don’t get yourself hung up on this.  You probably won’t need or use small segments until you get done with the larger segments, meaning low-hanging fruit, or unless you are doing a very specific research project.  By the time you get to that point, you’ll understand this topic and you’ll realize that the various researchers agree about far more than they disagree, and you can make your own decision based on your individual circumstances. If you’re entirely endogamous, small segments may just make you crazy.  However, if you’re chasing a colonial American ancestor, then you may need those small segments to identify or confirm that ancestor.

It is unfortunate, however, that all of the relevant articles are not represented in the ISOGG wiki, allowing people to fully educate themselves. Hopefully this can be updated shortly with the additional articles, listed above and from Jim Bartlett’s blog, published during this past year.

Recreating the Dead

James Crumley overlapping segments

James and Catherne Crumley segments above, compliments of Kitty Cooper’s tools

As we learn more about how to use autosomal DNA, we have begun to reconstruct our ancestors from the DNA of their descendants. Not as in cloning, but as in attributing DNA found in multiple descendants that originate from a common ancestor, or ancestral couple.  The first foray into this arena was GedMatch with their Lazarus tool.

Lazarus – Putting Humpty Dumpty Back Together Again
https://dna-explained.com/2015/01/14/lazarus-putting-humpty-dumpty-back-together-again/

I have taken a bit of a different proof approach wherein I recreated an ancestor, James Crumley, born in 1712 from the matching DNA of roughly 30 of his descendants.
http://www.slideshare.net/FamilyTreeDNA/roberta-estes-crumley-y-dna

I did the same thing, on an experimental smaller scale about a year ago with my ancestor, Henry Bolton.
https://dna-explained.com/2014/11/10/henry-bolton-c1759-1846-kidnapped-revolutionary-war-veteran-52-ancestors-45/

This is the way of the future in genetic genealogy, and I’ll be writing more about the Crumley project and the reconstruction of James Crumley in 2016.

                         Lump Of Coal Award(s)2015 frown

This category is a “special category” that is exactly what you think it is. Yep, this is the award no one wants.  We have a tie for the Lump of Coal Award this year between Ancestry and 23andMe.

               Ancestry Becomes the J.R. Ewing of the Genealogy World

2015 Larry Hagman

Attribution : © Glenn Francis, http://www.PacificProDigital.com

Some of you may remember J.R. Ewing on the television show called Dallas that ran from 1978 through 1991. J.R. Ewing, a greedy and unethical oil tycoon was one of the main characters.  The series was utterly mesmerizing, and literally everyone tuned in.  We all, and I mean universally, hated J.R. Ewing for what he unfeelingly and selfishly did to his family and others.  Finally, in a cliffhanger end of the season episode, someone shot J.R. Ewing.  OMG!!!  We didn’t know who.  We didn’t know if J.R. lived or died.  Speculation was rampant.  “Who shot JR?” was the theme on t-shirts everyplace that summer.  J.R. Ewing, over time, became the man all of America loved to hate.

Ancestry has become the J.R. Ewing of the genealogy world for the same reasons.

In essence, in the genetic genealogy world, Ancestry introduced a substandard DNA product, which remains substandard years later with no chromosome browser or comparison tools that we need….and they have the unmitigated audacity to try to convince us we really don’t need those tools anyway. Kind of like trying to convince someone with a car that they don’t need tires.

Worse, yet, they’ve introduced “better” tools (New Ancestor Discoveries), as in tools that were going to be better than a chromosome browser.  New Ancestor Discoveries “gives us” ancestors that aren’t ours. Sadly, there are many genealogists being led down the wrong path with no compass available.

Ancestry’s history of corporate stewardship is abysmal and continues with the obsolescence of various products and services including the Sorenson DNA database, their own Y and mtDNA database, MyFamily and most recently, Family Tree Maker. While the Family Tree Maker announcement has been met with great gnashing of teeth and angst among their customers, there are other software programs available.  Ancestry’s choices to obsolete the DNA data bases is irrecoverable and a huge loss to the genetic genealogy community.  That information is lost forever and not available elsewhere – a priceless, irreplaceable international treasure intentionally trashed.

If Ancestry had not bought up nearly all of the competing resources, people would be cancelling their subscriptions in droves to use another company – any other company. But there really is no one else anymore.  Ancestry knows this, so they have become the J.R. Ewing of the genealogy world – uncaring about the effects of their decisions on their customers or the community as a whole.  It’s hard for me to believe they have knowingly created such wholesale animosity within their own customer base.  I think having a job as a customer service rep at Ancestry would be an extremely undesirable job right now.  Many customers are furious and Ancestry has managed to upset pretty much everyone one way or another in 2015.

AncestryDNA Has Now Thoroughly Lost Its Mind
https://digginupgraves.wordpress.com/2015/04/02/ancestrydna-has-now-thoroughly-lost-its-mind/

Kenny, Kenny, Kenny
https://digginupgraves.wordpress.com/2015/04/10/kenny-kenny-kenny/

Dear Kenny – Any Suggestions for our New Ancestor Discoveries?
https://digginupgraves.wordpress.com/2015/04/13/dear-kenny-any-suggestions-for-our-new-ancestor-discoveries/

RIP Sorenson – A Crushing Loss
https://dna-explained.com/2015/05/15/rip-sorenson-a-crushing-loss/

Of Babies and Bathwater
http://www.legalgenealogist.com/blog/2015/05/17/of-babies-and-bathwater/

Facts Matter
http://legalgenealogist.com/blog/2015/05/03/facts-matter/

Getting the Most Out of AncestryDNA
https://dna-explained.com/2015/02/02/getting-the-most-out-of-ancestrydna/

Ancestry Gave Me a New DNA Ancestor and It’s Wrong
https://dna-explained.com/2015/04/03/ancestry-gave-me-a-new-dna-ancestor-and-its-wrong/

Testing Ancestry’s Amazing New Ancestor DNA Claim
https://dna-explained.com/2015/04/07/testing-ancestrys-amazing-new-ancestor-dna-claim/

Dissecting AncestryDNA Circles and New Ancestors
https://dna-explained.com/2015/04/09/dissecting-ancestrydna-circles-and-new-ancestors/

Squaring the Circle
http://legalgenealogist.com/blog/2015/03/29/squaring-the-circle/

Still Waiting for the Holy Grail
http://legalgenealogist.com/blog/2015/04/05/still-waiting-for-the-holy-grail/

A Dozen Ancestors That Aren’t aka Bad NADs
https://dna-explained.com/2015/04/14/a-dozen-ancestors-that-arent-aka-bad-nads/

The Logic and Birth of a Bad NAD (New Ancestor Discovery)
https://dna-explained.com/2015/08/12/the-logic-and-birth-of-a-bad-nad-new-ancestor-discovery/

Circling the Shews
http://legalgenealogist.com/blog/2015/05/24/circling-the-shews/

Naughty Bad NADs Sneak Home Under Cover of Darkness
https://dna-explained.com/2015/08/24/naughty-bad-nads-sneak-home-under-cover-of-darkness/

Ancestry Shared Matches Combined with New Ancestor Discoveries
https://dna-explained.com/2015/08/28/ancestry-shared-matches-combined-with-new-ancestor-discoveries/

Ancestry Shakey Leaf Disappearing Matches: Now You See Them – Now You Don’t
https://dna-explained.com/2015/09/24/ancestry-shakey-leaf-disappearing-matches-now-you-see-them-now-you-dont/

Ancestry’s New Amount of Shared DNA – What Does It Really Mean?
https://dna-explained.com/2015/11/06/ancestrys-new-amount-of-shared-dna-what-does-it-really-mean/

The Winds of Change
http://legalgenealogist.com/blog/2015/11/08/the-winds-of-change/

Confusion – Family Tree Maker, Family Tree DNA and Ancestry.com
https://dna-explained.com/2015/12/13/confusion-family-tree-maker-family-tree-dna-and-ancestry-com/

DNA: good news, bad news
http://legalgenealogist.com/blog/2015/01/11/dna-good-news-bad-news/

Check out the Alternatives
http://legalgenealogist.com/blog/2015/12/09/check-out-the-alternatives/

GeneAwards 2015
http://www.tamurajones.net/GeneAwards2015.xhtml

23andMe Betrays Genealogists

2015 broken heart

In October, 23andMe announced that it has reached an agreement with the FDA about reporting some health information such as carrier status and traits to their clients. As a part of or perhaps as a result of that agreement, 23andMe is dramatically changing the user experience.

In some aspects, the process will be simplified for genealogists with a universal opt-in. However, other functions are being removed and the price has doubled.  New advertising says little or nothing about genealogy and is entirely medically focused.  That combined with the move of the trees offsite to MyHeritage seems to signal that 23andMe has lost any commitment they had to the genetic genealogy community, effectively abandoning the group entirely that pulled their collective bacon out of the fire. This is somehow greatly ironic in light of the fact that it was the genetic genealogy community through their testing recommendations that kept 23andMe in business for the two years, from November of 2013 through October of 2015 when the FDA had the health portion of their testing shut down.  This is a mighty fine thank you.

As a result of the changes at 23andMe relative to genealogy, the genetic genealogy community has largely withdrawn their support and recommendations to test at 23andMe in favor of Ancestry and Family Tree DNA.

Kelly Wheaton, writing on the Facebook ISOGG group along with other places has very succinctly summed up the situation:
https://www.facebook.com/groups/isogg/permalink/10153873250057922/

You can also view Kelly’s related posts from earlier in December and their comments at:
https://www.facebook.com/groups/isogg/permalink/10153830929022922/
and…
https://www.facebook.com/groups/isogg/permalink/10153828722587922/

My account at 23andMe has not yet been converted to the new format, so I cannot personally comment on the format changes yet, but I will write about the experience in 2016 after my account is converted.

Furthermore, I will also be writing a new autosomal vendor testing comparison article after their new platform is released.

I Hate 23andMe
https://digginupgraves.wordpress.com/2015/06/14/i-hate-23andme/

23andMe to Get Makeover After Agreement With FDA
https://dna-explained.com/2015/10/21/23andme-to-get-a-makeover-after-agreement-with-fda/

23andMe Metamorphosis
http://throughthetreesblog.tumblr.com/post/131724191762/the-23andme-metamorphosis

The Changes at 23andMe
http://legalgenealogist.com/blog/2015/10/25/the-changes-at-23andme/

The 23and Me Transition – The First Step
https://dna-explained.com/2015/11/05/the-23andme-transition-first-step-november-11th/

The Winds of Change
http://legalgenealogist.com/blog/2015/11/08/the-winds-of-change/

Why Autosomal Response Rate Really Does Matter
https://dna-explained.com/2015/02/24/why-autosomal-response-rate-really-does-matter/

Heads Up About the 23andMe Meltdown
https://dna-explained.com/2015/12/04/heads-up-about-the-23andme-meltdown/

Now…and not now
http://legalgenealogist.com/blog/2015/12/06/now-and-not-now/

                             Cone of Shame Award 2015 frown

Another award this year is the Cone of Shame award which is also awarded to both Ancestry and 23andMe for their methodology of obtaining “consent” to sell their customers’, meaning our, DNA and associated information.

Genetic Genealogy Data Gets Sold

2015 shame

Unfortunately, 2015 has been the year that the goals of both 23andMe and Ancestry have become clear in terms of our DNA data. While 23andMe has always been at least somewhat focused on health, Ancestry never was previously, but has now hired a health officer and teamed with Calico for medical genetics research.

Now, both Ancestry and 23andMe have made research arrangements and state in their release and privacy verbiage that all customers must electronically sign (or click through) when purchasing their DNA tests that they can sell, at minimum, your anonymized DNA data, without any further consent.  And there is no opt-out at that level.

They can also use our DNA and data internally, meaning that 23andMe’s dream of creating and patenting new drugs can come true based on your DNA that you submitted for genealogical purposes, even if they never sell it to anyone else.

In an interview in November, 23andMe CEO Anne Wojcicki said the following:

23andMe is now looking at expanding beyond the development of DNA testing and exploring the possibility of developing its own medications. In July, the company raised $79 million to partly fund that effort. Additionally, the funding will likely help the company continue with the development of its new therapeutics division. In March, 23andMe began to delve into the therapeutics market, to create a third pillar behind the company’s personal genetics tests and sales of genetic data to pharmaceutical companies.

Given that the future of genetic genealogy at these two companies seems to be tied to the sale of their customer’s genetic and other information, which, based on the above, is very clearly worth big bucks, I feel that the fact that these companies are selling and utilizing their customer’s information in this manner should be fully disclosed. Even more appropriate, the DNA information should not be sold or utilized for research without an informed consent that would traditionally be used for research subjects.

Within the past few days, I wrote an article, providing specifics and calling on both companies to do the following.

  1. To minimally create transparent, understandable verbiage that informs their customers before the end of the purchase process that their DNA will be sold or utilized for unspecified research with the intention of financial gain and that there is no opt-out. However, a preferred plan of action would be a combination of 2 and 3, below.
  2. Implement a plan where customer DNA can never be utilized for anything other than to deliver the services to the consumers that they purchased unless a separate, fully informed consent authorization is signed for each research project, without coercion, meaning that the client does not have to sign the consent to obtain any of the DNA testing or services.
  3. To immediately stop utilizing the DNA information and results from customers who have already tested until they have signed an appropriate informed consent form for each research project in which their DNA or other information will be utilized.

And Now Ancestry Health
https://dna-explained.com/2015/06/06/and-now-ancestry-health/

Opting Out
http://legalgenealogist.com/blog/2015/07/26/opting-out/

Ancestry Terms of Use Updated
http://legalgenealogist.com/blog/2015/07/07/ancestry-terms-of-use-updated/

AncestryDNA Doings
http://legalgenealogist.com/blog/2015/07/05/ancestrydna-doings/

Heads Up About the 23andMe Meltdown
https://dna-explained.com/2015/12/04/heads-up-about-the-23andme-meltdown/

23andMe and Ancestry and Selling Your DNA Information
https://dna-explained.com/2015/12/30/23andme-ancestry-and-selling-your-dna-information/

                      Citizen Science Leadership Award   2015 smile

The Citizen Science Leadership Award this year goes to Blaine Bettinger for initiating the Shared cM Project, a crowdsourced project which benefits everyone.

Citizen Scientists Continue to Push the Edges of the Envelope with the Shared cM Project

Citizen scientists, in the words of Dr. Doron Behar, “are not amateurs.” In fact, citizen scientists have been contributing mightily and pushing the edge of the genetic genealogy frontier consistently now for 15 years.  This trend continues, with new discoveries and new ways of viewing and utilizing information we already have.

For example, Blaine Bettinger’s Shared cM Project was begun in March and continues today. This important project has provided real life information as to the real matching amounts and ranges between people of different relationships, such as first cousins, for example, as compared to theoretical match amounts.  This wonderful project produced results such as this:

2015 shared cM

I don’t think Blaine initially expected this project to continue, but it has and you can read about it, see the rest of the results, and contribute your own data here. Blaine has written several other articles on this topic as well, available at the same link.

Am I Weird or What?
https://dna-explained.com/2015/03/07/am-i-weird-or-what/

Jim Owston analyzed fourth cousins and other near distant relationships in his Owston one-name study:
https://owston.wordpress.com/2015/08/10/an-analysis-of-fourth-cousins-and-other-near-distant-relatives/

I provided distant cousin information in the Crumley surname study:
http://www.slideshare.net/FamilyTreeDNA/roberta-estes-crumley-y-dna

I hope more genetic genealogists will compile and contribute this type of real world data as we move forward. If you have compiled something like this, the Surname DNA Journal is peer reviewed and always looking for quality articles for publication.

Privacy, Law Enforcement and DNA

2015 privacy

Unfortunately, in May, a situation by which Y DNA was utilized in a murder investigation was reported in a sensationalist “scare” type fashion.  This action provided cause, ammunition or an excuse for Ancestry to remove the Sorenson data base from public view.

I find this exceedingly, exceedingly unfortunate. Given Ancestry’s history with obsoleting older data bases instead of updating them, I’m suspecting this was an opportune moment for Ancestry to be able to withdraw this database, removing a support or upgrade problem from their plate and blame the problem on either law enforcement or the associated reporting.

I haven’t said much about this situation, in part because I’m not a lawyer and in part because the topic is so controversial and there is no possible benefit since the damage has already been done. Unfortunately, nothing anyone can say or has said will bring back the Sorenson (or Ancestry) data bases and arguments would be for naught.  We already beat this dead horse a year ago when Ancestry obsoleted their own data base.  On this topic, be sure to read Judy Russell’s articles and her sources as well for the “rest of the story.”

Privacy, the Police and DNA
http://legalgenealogist.com/blog/2015/02/08/privacy-the-police-and-dna/

Big Easy DNA Not So Easy
http://legalgenealogist.com/blog/2015/03/15/big-easy-dna-not-so-easy/

Of Babies and Bathwater
http://www.legalgenealogist.com/blog/2015/05/17/of-babies-and-bathwater/

Facts Matter
http://legalgenealogist.com/blog/2015/05/03/facts-matter/

Genetic genealogy standards from within the community were already in the works prior to the Idaho case, referenced above, and were subsequently published as guidelines.

Announcing Genetic Genealogy Standards
http://thegeneticgenealogist.com/2015/01/10/announcing-genetic-genealogy-standards/

The standards themselves:
http://www.thegeneticgenealogist.com/wp-content/uploads/2015/01/Genetic-Genealogy-Standards.pdf

Ancient DNA Results Continue to Amass

“Moorleiche3-Schloss-Gottorf” by Commander-pirx at de.wikipedia – Own work. Licensed under CC BY-SA 3.0 via Commons

Ancient DNA is difficult to recover and even more difficult to sequence, reassembling tiny little blocks of broken apart DNA into an ancient human genome.

However, each year we see a few more samples and we are beginning to repaint the picture of human population movement, which is different than we thought it would be.

One of the best summaries of the ancient ancestry field was Michael Hammer’s presentation at the Family Tree DNA Conference in November titled “R1B and the Peopling of Europe: an Ancient DNA Update.” His slides are available here:
http://www.slideshare.net/FamilyTreeDNA/r1b-and-the-people-of-europe-an-ancient-dna-update

One of the best ongoing sources for this information is Dienekes’ Anthropology Blog. He covered most of the new articles and there have been several.  That’s the good news and the bad news, all rolled into one. http://dienekes.blogspot.com/

I have covered several that were of particular interest to the evolution of Europeans and Native Americans.

Yamnaya, Light Skinned Brown Eyed….Ancestors?
https://dna-explained.com/2015/06/15/yamnaya-light-skinned-brown-eyed-ancestors/

Kennewick Man is Native American
https://dna-explained.com/2015/06/18/kennewick-man-is-native-american/

Botocudo – Ancient Remains from Brazil
https://dna-explained.com/2015/07/02/botocudo-ancient-remains-from-brazil/

Some Native had Oceanic Ancestors
https://dna-explained.com/2015/07/22/some-native-americans-had-oceanic-ancestors/

Homo Naledi – A New Species Discovered
https://dna-explained.com/2015/09/11/homo-naledi-a-new-species-discovered/

Massive Pre-Contact Grave in California Yields Disappointing Results
https://dna-explained.com/2015/10/20/mass-pre-contact-native-grave-in-california-yields-disappointing-results/

I know of several projects involving ancient DNA that are in process now, so 2016 promises to be a wonderful ancient DNA year!

Education

2015 education

Many, many new people discover genetic genealogy every day and education continues to be an ongoing and increasing need. It’s a wonderful sign that all major conferences now include genetic genealogy, many with a specific track.

The European conferences have done a great deal to bring genetic genealogy testing to Europeans. European testing benefits those of us whose ancestors were European before immigrating to North America.  This year, ISOGG volunteers staffed booths and gave presentations at genealogy conferences in Birmingham, England, Dublin, Ireland and in Nyköping, Sweden, shown below, photo compliments of Catherine Borges.

ISOGG volunteers

Several great new online educational opportunities arose this year, outside of conferences, for which I’m very grateful.

DNA Lectures YouTube Channel
https://dna-explained.com/2015/04/26/dna-lectures-youtube-channel/

Allen County Public Library Online Resources
https://dna-explained.com/2015/06/03/allen-county-public-library-online-resources/

DNA Data Organization Tools and Who’s on First
https://dna-explained.com/2015/09/08/dna-data-organization-tools-and-whos-on-first/

Genetic Genealogy Educational Resource List
https://dna-explained.com/2015/12/03/genetic-genealogy-educational-resource-list/

Genetic Genealogy Ireland Videos
https://www.youtube.com/channel/UCHnW2NAfPIA2KUipZ_PlUlw

DNA Lectures – Who Do You Think You Are
https://www.youtube.com/channel/UC7HQSiSkiy7ujlkgQER1FYw

Ongoing and Online Classes in how to utilize both Y and autosomal DNA
http://www.dnaadoption.com/index.php?page=online-classes

Education Award

2015 smile Family Tree DNA receives the Education Award this year along with a huge vote of gratitude for their 11 years of genetic genealogy conferences. They are the only testing or genealogy company to hold a conference of this type and they do a fantastic job.  Furthermore, they sponsor additional educational events by providing the “theater” for DNA presentations at international events such as the Who Do You Think You Are conference in England.  Thank you Family Tree DNA.

Family Tree DNA Conference

ftdna 2015

The Family Tree DNA Conference, held in November, was a hit once again. I’m not a typical genealogy conference person.  My focus is on genetic genealogy, so I want to attend a conference where I can learn something new, something leading edge about the science of genetic genealogy – and that conference is definitely the Family Tree DNA conference.

Furthermore, Family Tree DNA offers tours of their lab on the Monday following the conference for attendees, and actively solicits input on their products and features from conference attendees and project administrators.

2015 FTDNA lab

Family Tree DNA 11th International Conference – The Best Yet
https://dna-explained.com/2015/11/18/2015-family-tree-dna-11th-international-conference-the-best-yet/

All of the conference presentations that were provided by the presenters have been made available by Family Tree DNA at:
http://www.slideshare.net/FamilyTreeDNA?utm_campaign=website&utm_source=sendgrid.com&utm_medium=email

2016 Genetic Genealogy Wish List

2015 wish list

In 2014, I presented a wish list for 2015 and it didn’t do very well.  Will my 2015 list for 2016 fare any better?

  • Ancestry restores Sorenson and their own Y and mtDNA data bases in some format or contributes to an independent organization like ISOGG.
  • Ancestry provides chromosome browser.
  • Ancestry removes or revamps Timber in order to restore legitimate matches removed by Timber algorithm.
  • Fully informed consent (per research project) implemented by 23andMe and Ancestry, and any other vendor who might aspire to sell consumer DNA or related information, without coercion, and not as a prerequisite for purchasing a DNA testing product. DNA and information will not be shared or utilized internally or externally without informed consent and current DNA information will cease being used in this fashion until informed consent is granted by customers who have already tested.
  • Improved ethnicity reporting at all vendors including ancient samples and additional reference samples for Native Americans.
  • Autosomal Triangulation tools at all vendors.
  • Big Y and STR integration and analysis enhancement at Family Tree DNA.
  • Ancestor Reconstruction
  • Mitochondrial and Y DNA search tools by ancestor and ancestral line at Family Tree DNA.
  • Improved tree at Family Tree DNA – along with new search capabilities.
  • 23andMe restores lost capabilities, drops price, makes changes and adds features previously submitted as suggestions by community ambassadors.
  • More tools (This is equivalent to “bring me some surprises” on my Santa list as a kid.)

My own goals haven’t changed much over the years. I still just want to be able to confirm my genealogy, to learn as much as I can about each ancestor, and to break down brick walls and fill in gaps.

I’m very hopeful each year as more tools and methodologies emerge.  More people test, each one providing a unique opportunity to match and to understand our past, individually and collectively.  Every year genetic genealogy gets better!  I can’t wait to see what 2016 has in store.

Here’s wishing you a very Happy and Ancestrally Prosperous New Year!

2015 happy new year

Top 10 Most Popular Articles of 2015

Wordpress 2015

WordPress, the blogging software I use, provides a year-end summary that is quite interesting.

I really like this report, as I tend to be very focused on what I’m researching and writing, not on stats – so this is a refreshing break and summary. I thought you might be interested too.

The top 10 most viewed posts in 2015 were, in order from least to most:

10thPromethease – Genetic Health Information Alternative – From December 2013

People are beginning to ask about how they can obtain some of the health information that they were previously receiving from 23andMe.  For $5, at Promethease,  you can upload any of the autosomal files from either Family Tree DNA, 23andMe or Ancestry.com.  They will process your raw data and provide you with a report that is available to download from their server for 45 days.  They also e-mail you a copy.

9thX Marks the Spot – From September 2012

When using autosomal DNA, the X chromosome is a powerful tool with special inheritance properties.  Many people think that mitochondrial DNA is the same as the X chromosome.  It’s not.

8thThick Hair, Small Boobs, Shovel Shaped Teeth and More – From February 2013

Yep, there’s a gene for these traits, and more.  The same gene, named EDAR (short for Ectodysplasin receptor EDARV370A), it turns out, also confers more sweat glands and distinctive teeth and is found in the majority of East Asian people.

7thMythbusting – Women, Fathers and DNA – From June 2013

I’m sometimes amazed at what people believe – and not just a few people – but a lot of people.

Recently, I ran across a situation where someone was just adamant that autosomal DNA could not help a female find or identify her father.  That’s simply wrong. Incorrect.  Nada!  This isn’t, I repeat, IS NOT, true of autosomal testing.

6th4 Kinds of DNA for Genetic Genealogy – from October 2012 – This is probably the article I refer people to most often.  It’s the basics, just the basics.

There seems to be a lot of confusion about the different “kinds” of DNA and how they can be used for genetic genealogy.

It used to be simple.  When this “industry” first started, in the year 2000, you could test two kinds of DNA and it was straightforward.  Now we’ve added more DNA, more tools and more testing companies and it’s not quite so straightforward anymore.

5thIs History Repeating Itself at Ancestry? – from August 2012

Is history repeating itself at Ancestry?

I’ve been thinking about whether or not I should publish this posting.  As I write and rewrite it, I still haven’t made up my mind.  It’s one of those sticky wickets, as they are called.  One of the reasons I hesitate is that I have far more questions than answers.

4thWhat is a Haplogroup? – From January 2013

Sometimes we’ve been doing genetic genealogy for so long we forget what it’s like to be new.  I’m reminded, sometimes humorously, by some of the questions I receive.

3rdAutosomal DNA 2015 – Which Test is the Best? – From February 2015

This now obsolete article compared the autosomal tests from Family Tree DNA, Ancestry and 23andMe.  23andMe, as of year end (2015), is in the midst of rewriting their platform, which obsoletes some of the tools they offered previously.   As soon as the 23andMe transition to their new platform is complete, I’ll be writing an updated version of this article for 2016.  Until then, suffice it to say I am recommending Family Tree DNA and Ancestry, in that order.

2ndEthnicity Results – True or Not? – from October 2013

I can’t even begin to tell you how many questions I receive that go something like this:

“I received my ethnicity results from XYZ.  I’m confused.  The results don’t seem to align with my research and I don’t know what to make of them?”

1stProving Native American Ancestry Using DNA – From December 2012 – this has been the most popular article every year since 2012. This doesn’t surprise me, as it’s also the most common question I receive.

Every day, I receive e-mails very similar to this one.

“My family has always said that we were part Native American.  I want to prove this so that I can receive help with money for college.”

Interesting

I was surprised, at first, to see so many older posts, but then I realized they have had more time to accumulate hits.

Of these all-time Top 10, three of them, including the most popular, which is most popular by far, have to do with Native American ancestry, directly or indirectly. The most common questions I receive about ethnicity also relate to the discovery of Native American ancestry.

Thank you everyone for coming along with me on this on this wonderful journey.  It will be exciting to see what 2016 has to offer.  I already have some exciting research planned that I’ll be sharing with you.

Happy New Year everyone!  I’m wishing you new ancestors!

Native American Haplogroup C Update – Progress!!

native border

Haplogroup C-P39 is the Native American branch of Y DNA paternal haplogroup C.  It’s rare as chicken’s teeth.  Most Native American males fall into haplogroup Q, making our haplogroup C-P39 project participants quite unusual and unique.  So are the tools needed to identify branches on the Native American haplogroup C tree.

Last week, Family Tree DNA added a group of 9 SNPs found in haplogroup C to their product offering.  This was done without an announcement and without any fanfare – but it’s really important.  Without the ongoing support of Family Tree DNA, we wouldn’t have the Big Y test, nor the refining SNP tests that can be added to the Big Y in areas where the results are ambiguous.  Individuals who don’t want to purchase the Big Y can purchase these haplogroup defining SNPs individually as well.

The Native defining SNP for haplogroup C is P39.  People who test positive for C-P39 will then want to test Z30750 and Z30764.

  • Z30503
  • Z30601
  • FGC21495
  • Z30750
  • Z30764
  • PF3239
  • Z30729
  • FGC263
  • FGC31712

However, because haplogroup C-P39 is so rare – and to date – we have found several new SNPs in every man who has taken the Big Y test – and because those new, never before discovered SNPs are the bread crumbs that we need to follow to discover how our ancestors settled and dispersed across the Americas – we strong recommend the Big Y test at Family Tree DNA for all C-P39 men.  The Big Y test doesn’t just look at known SNP locations, it scans the entire Y chromosome for mutations.  Therefore, it’s both a genealogy and a research tool.

To that end, we very much want to fund this testing from the project coffers where necessary to advance our understanding.  Just to whet your appetite, we have participants now across Canada and also in the American Southwest.  We desperately want these men to take the Big Y test so we can get a much clearer picture of how they are related, and how many mutations they have individually – but don’t share – because that is how we estimate when they last shared a common ancestor.  In other words, the mutations build the branches of the tree.

This week, we’ve ordered another new C-P39 Big Y test.  If you are C-P39 – Native American haplogroup C – and have not yet taken the Big Y – please consider doing so.

If you are Native American and haplogroup C – please join the C-P39 and the American Indian projects.  You can do so from your home page at Family Tree DNA by clicking on the “Projects” tab at the upper left of your personal page, then on “join projects.”  You can search for the word “Indian” in the project list to find the American Indian project and scrolling down to the Y haplogroup projects and clicking on C will take you to the C-P39 link.

project join

If you can contribute to funding these Big Y tests, please do – even small amounts help.  The link to donate directly to the C-P39 project is: https://www.familytreedna.com/group-general-fund-contribution.aspx?g=Y-DNAC-P39

Each individual who takes the Big Y test is also encouraged to upgrade to 111 markers.  We need as much information as we can get.

Marie Rundquist and I are co-administrators of the C-P39 project, and she wrote the following verbiage in honor of the 5 year anniversary of the first discovery of what is now C-P39 in the Native Community.  We, as a community, have come a very long way in just 5 years!

It was in 2010, five years ago, when Keith Doucet first tested for the C P39 Y DNA (formerly C3b) Native American DNA type in the Amerindian Ancestry out of Acadia Family Tree DNA study — with numbers of Doucets (and Doucettes!) having the same, Native American, C P39 Y DNA result.  It’s amazing when you think of our journey and how much this research has benefitted our knowledge of our history in North America!

Who can ever forget Keith Doucet’s discovery? http://www.familyheritageresearchcommunity.org/doucet_dna.html

Or Emile Broome’s Y DNA discovery, also from 2010? http://www.familyheritageresearchcommunity.org/broome_dna.html

…and the subsequent discoveries of related Doucets and Doucettes and other project members from all regions of the US and Canada who tested in our project and whose results showed the same Native American C P39 Y DNA haplogroup type?

There is great similarity among the DNA test results for our C P39 Y DNA candidates despite differences in geographic locations and surnames, with testers from across the United States, including the American Southwest, the North East, the South, and Canada compared.  Initial Big Y DNA test results for project members have shown remarkable similarity as well.  Additional Big Y test results for tests underway and the availability of 9 new SNPs for our project members help us discover whether this trend is amplified by the additional tests or if we (the C P39 Y DNA project) can distinguish downstream uniqueness among our participants. The C P39 Y DNA test has received the generous support of its members, Family Tree DNA leadership and scientists, product managers, and volunteer administrators in establishing our superior C P39 Y DNA baseline and we are grateful for your support.

Visit the C P39 Y DNA project site to learn more. https://www.familytreedna.com/public/ydna_C-P39/

Thank you to our project members for your continued participation!  And thank you to Family Tree DNA for their ongoing dedication, research and support.  Collectively, we discover more of our history every day!

native border

Some Native Americans Had Oceanic Ancestors

This week has seen a flurry of new scientific and news articles.  What has been causing such a stir?  It appears that Australian or more accurately, Australo-Melanese DNA has been found in South America’s Native American population. In addition, it has also been found in Aleutian Islanders off the coast of Alaska.  In case you aren’t aware, that’s about 8,500 miles as the crow flies.  That’s one tired crow.  As the person paddles or walks along the shoreline, it’s even further, probably about 12,000 miles.

Aleutians to Brazil

Whatever the story, it was quite a journey and it certainly wasn’t all over flat land.

This isn’t the first inkling we’ve had.  Just a couple weeks ago, it was revealed that the Botocudo remains from Brazil were Polynesian and not admixed with either Native, European or African.  This admixture was first discovered via mitochondrial DNA, but full genome sequencing confirmed their ancestry and added the twist that they were not admixed – an extremely unexpected finding.  This is admittedly a bit confusing, because it implies that there were new Polynesian arrivals in the 1600s or 1700s.

Unlikely as it seems, it obviously happened, so we set that aside as relatively contemporary.

The findings in the papers just released are anything but contemporary.

The First Article

The first article in Science, “Genomic evidence for the Pleistocene and recent population history of Native Americans” by Raghaven et al published this week provides the following summary (bolding is mine):

How and when the Americas were populated remains contentious. Using ancient and modern genome-wide data, we find that the ancestors of all present-day Native Americans, including Athabascans and Amerindians, entered the Americas as a single migration wave from Siberia no earlier than 23 thousand years ago (KYA), and after no more than 8,000-year isolation period in Beringia. Following their arrival to the Americas, ancestral Native Americans diversified into two basal genetic branches around 13 KYA, one that is now dispersed across North and South America and the other is restricted to North America. Subsequent gene flow resulted in some Native Americans sharing ancestry with present-day East Asians (including Siberians) and, more distantly, Australo-Melanesians. Putative ‘Paleoamerican’ relict populations, including the historical Mexican Pericúes and South American Fuego-Patagonians, are not directly related to modern Australo-Melanesians as suggested by the Paleoamerican Model.

This article in EurekAlert and a second one here discuss the Science paper.

Raghaven 2015

Migration map from the Raghaven paper.

The paper included the gene flow and population migration map, above, along with dates.

The scientists sequenced the DNA of 31 living individuals from the Americas, Siberia and Oceana as follows:

Siberian:

  • Altai – 2
  • Buryat – 2
  • Ket – 2
  • Kiryak – 2
  • Sakha – 2
  • Siberian Yupik – 2

North American Native:

  • Tsimshian (number not stated, but by subtraction, it’s 1)

Southern North American, Central and South American Native:

  • Pima – 1
  • Huichol -1
  • Aymara – 1
  • Yakpa – 1

Oceana:

  • Papuan – 14

The researchers also state that they utilized 17 specimens from relict groups such as the Pericues from Mexico and Fuego-Patagonians from the southernmost tip of South America.  They also sequenced two pre-Columbian mummies from the Sierra Tarahumara in northern Mexico.  In total, 23 ancient samples from the Americas were utilized.

They then compared these results with a reference panel of 3053 individuals from 169 populations which included the ancient Saqqaq Greenland individual at 400 years of age as well as the Anzick child from Montana from about 12,500 years ago and the Mal’ta child from Siberia at 24,000 years of age.

Not surprisingly, all of the contemporary samples with the exception of the Tsimshian genome showed recent western Eurasian admixture.

As expected, the results confirm that the Yupik and Koryak are the closest Eurasian population to the Americas.  They indicate that there is a “clean split” between the Native American population and the Koryak about 20,000 years ago.

They found that “Athabascans and Anzick-1, but not the Greenlandis Inuit and Saqqaq belong to the same initial migration wave that gave rise to present-day Amerindians from southern North America and Central and South America, and that this migration likely followed a coastal route, given our current understanding of the glacial geological and paleoenvironmental parameters of the Late Pleistocene.”

Evidence of gene flow between the two groups was also found, meaning between the Athabascans and the Inuit.  Additionally, they found evidence of post-split gene flow between Siberians and Native Americans which seems to have stopped about 12,000 years ago, which meshes with the time that the Beringia land bridge was flooded by rising seas, cutting off land access between the two land masses.

They state that the results support all Native migration from Siberia, contradicting claims of an early migration from Europe.

The researchers then studied the Karitiana people of South America and determined that the two groups, Athabascans and Karitiana diverged about 13,000 years ago, probably not in current day Alaska, but in lower North America.  This makes sense, because the Clovis Anzick child, found in Montana, most closely matches people in South America.

By the Clovis period of about 12,500 years ago, the Native American population had already split into two branches, the northern and southern, with the northern including Athabascan and other groups such as the Chippewa, Cree and Ojibwa.  The Southern group included people from southern North America and Central and South America.

Interestingly, while admixture with the Inuit was found with the Athabascan, Inuit admixture was not found among the Cree, Ojibwa and Chippewa.  The researchers suggest that this may be why the southern branch, such as the Karitiana are genetically closer to the northern Amerindians located further east than to northwest coast Amerindians and Athabascans.

Finally, we get to the Australian part.  The researchers when trying to sort through the “who is closer to whom” puzzle found unexpected results.  They found that some Native American populations including Aleutian Islanders, Surui (Brazil) and Athabascans are closer to Australo-Melanesians compared to other Native Americans, such as Ojibwa, Cree and Algonquian and South American Purepecha (Mexico), Arhuaco (Colombia) and Wayuu (Colombia, Venezuela).  In fact, the Surui are one of the closest populations to East Asians and Australo-Melanese, the latter including Papuans, non-Papuan Melanesians, Solomon Islanders and hunter-gatherers such as Aeta. The researchers acknowledge these are weak trends, but they are nonetheless consistently present.

Dr. David Reich, from Harvard, a co-author of another paper, also published this past week, says that 2% of the DNA of Amazonians is from Oceana.  If that is consistent, it speaks to a founder population in isolation, such that the 2% just keeps getting passed around in the isolated population, never being diluted by outside DNA.  I would suggest that is not a weak signal.

The researchers suggest that the variance in the strength of this Oceanic signal suggests that the introduction of the Australo-Melanese occurred after the initial peopling of the Americas.  The ancient samples cluster with the Native American groups and do not show the Oceanic markers and show no evidence of gene flow from Oceana.

The researchers also included cranial morphology analysis, which I am omitting since cranial morphology seems to have led researchers astray in the past, specifically in the case of Kennewick man.

One of the reasons cranial morphology is such a hotly debated topic is because of the very high degree of cranial variance found in early skeletal remains.  One of the theories evolving from the cranial differences involving the populating of the Americans has been that the Australo-Melanese were part of a separate and earlier migration that gave rise to the earliest Americans who were then later replaced by the Asian ancestors of current day Native Americans.  If this were the case, then the now-extinct Fuego-Patagonains samples from the location furthest south on the South American land mass should have included DNA from Oceana, but it didn’t.

The Second Article

A second article published this week, titled “’Ghost population’ hints at long lost migration to the Americas” by Ellen Callaway discusses similar findings, presented in a draft letter to Nature titled “Genetic evidence for two founding populations of the Americas” by Skoglund et al.  This second group discovers the same artifact Australo-Melanesian DNA in Native American populations but suggests that it may be from the original migration and settlement event or that there may have been two distinct founding populations that settled at the same time or that there were two founding events.

EurekAlert discusses the article as well.

It’s good to have confirmation and agreement between the two labs who happened across these results independently that the Australo-Melanesian DNA is present in some Native populations today.

Their interpretations and theories about how this Oceanic DNA arrived in some of the Native populations vary a bit, but if you read the details, it’s really not quite as different as it first appears from the headlines.  Neither group claims to know for sure, and both discuss possibilities.

Questions remain.  For example, if the founding group was small, why, then, don’t all of the Native people and populations have at least some Oceanic markers?  The Anzick Child from 12,500 years ago does not.  He is most closely related to the tribes in South America, where the Oceanic markers appear with the highest frequencies.

In the Harvard study, the scientists fully genome sequenced 63 individuals without discernable evidence of European or African ancestors in 21 Native American populations, restricting their study to individuals from Central and South America that have the strongest evidence of being entirely derived from a homogenous First American ancestral population.

Their results show that the two Amazonian groups, Surui and Karitians are closest to the “Australasian populations, the Onge from the Andaman Island in the Bay of Bengal (a so-called ‘Negrito’ group), New Guineans, Papuans and indigenous Australians.”  Within those groups, the Australasian populations are the only outliers – meaning no Africans, Europeans or East Asian DNA found in the Native American people.

When repeating these tests, utilizing blood instead of saliva, a third group was shown to also carry these Oceanic markers – the Xavante, a population from the Brazilian plateau that speaks a language of the Ge group that is different from the Tupi language group spoke by the Karitians and Surui.

Skoglund 2015-2

The closest populations that these Native people matched in Oceana, shown above on the map from the draft Skoglund letter, were, in order, New Guineans, Papuans and Andamanese.  The researchers further state that populations from west of the Andes or north of the Panama isthmus show no significant evidence of an affinity to the Onge from the Andaman Islands with the exception of the Cabecar (Costa Rica).

That’s a very surprising finding, given that one would expect more admixture on the west, which is the side of the continent where the migration occurred.

The researchers then compared the results with other individuals, such as Mal’ta child who is known to have contributed DNA to the Native people today, and found no correlation with Oceanic DNA.  Therefore, they surmised that the Oceanic admixture cannot be explained by a previously known admixture event.

They propose that a mystery population they have labeled as “Population Y” (after Ypykuera which means ancestor in the Tupi language family) contributed the Australasian lineage to the First Americans and that is was already mixed into the lineage by the time it arrived in Brazil.

According to their work, Population Y may itself have been admixed, and the 2% of Oceanic DNA found in the Brazilian Natives may be an artifact of between 2 and 85% of the DNA of the Surui, Karitiana and Xavante that may have come from Population Y.  They mention that this result is striking in that the majority of the craniums that are more Oceanic in Nature than Asiatic, as would be expected from people who migrated from Siberia, are found in Brazil.

They conclude that the variance in the presence or absence of DNA in Native people and remains, and the differing percentages argue for more than one migration event and that “the genetic ancestry of Native Americans from Central and South America cannot be due to a single pulse of migration south of the Late Pleistocene ice sheets from a homogenous source population, and instead must reflect at least two streams of migration or alternatively a long drawn out period of gene flow from a structured Beringian or Northeast Asian source.”

Perhaps even more interesting is the following statement:

“The arrival of population Y ancestry in the Americas must in any scenario have been ancient: while Population Y shows a distant genetic affinity to Andamanese, Australian and New Guinean populations, it is not particularly closely related to any of them, suggesting that the source of population Y in Eurasia no longer exists.”

They further state they find no admixture indication that would suggest that Population Y arrived in the last few thousand years.

So, it appears that perhaps the Neanderthals and Denisovans were not the only people who were our ancestors, but no longer exist as a separate people, only as an admixed part of us today.  We are their legacy.

The Take Away

When I did the Anzick extractions, we had hints that something of this sort might have been occurring.  For example, I found surprising instances of haplogroup M, which is neither European, African nor Native American, so far as we know today.  This may have been a foreshadowing of this Oceanic admixture.  It may also be a mitochondrial artifact.  Time will tell.  Perhaps haplogroup M will turn out to be Native by virtue of being Oceanic and admixed thousands of years ago.  There is still a great deal to learn.  Regardless of how these haplogroups and Oceanic DNA arrived in Brazil in South America and in the Aleutian Islands off of Alaska, one thing is for sure, it did.

We know that the Oceanic DNA found in the Brazilian people studied for these articles is not contemporary and is ancient.  This means that it is not related to the Oceanic DNA found in the Botocudo people, who, by the way, also sport mitochondrial haplogroups that are within the range of Native people, meaning haplogroup B, but have not been found in other Native people.  Specifically, haplogroups B4a1a1 and B4a1a1a.  Additionally, there are other B4a1a, B4a1b and B4a1b1 results found in the Anzick extract which could also be Oceanic.  You can see all of the potential and confirmed Native American mitochondrial DNA results in my article “Native American Mitochondrial Haplogroups” that I update regularly.

We don’t know how or when the Botocudo arrived, but the when has been narrowed to the 1600s or 1700s.  We don’t know how or when the Oceanic DNA in the Brazilian people arrived either, but the when was ancient.  This means that Oceanic DNA has arrived in South America at least twice and is found among the Native peoples both times.

We know that some Native groups have some Oceanic admixture, and others seem to have none, in particular the Northern split group that became the Cree, Ojibwa, Algonquian, and Chippewa.

We know that the Brazilian Native groups are most closely related to Oceanic groups, but that the first paper also found Oceanic admixture in the Aleutian Islands.  The second paper focused on the Central and South American tribes.

We know that the eastern American tribes, specifically the Algonquian tribes are closely related to the South Americans, but they don’t share the Oceanic DNA and neither do the mid-continent tribes like the Cree, Ojibwa and Chippewa.  The only Paleolithic skeleton that has been sequenced, Anzick, from 12,500 years ago in Montana also does not carry the Oceanic signature.

In my opinion, the disparity between who does and does not carry the Oceanic signature suggests that the source of the Oceanic DNA in the Native population could not have been a member of the first party to exit out of Beringia and settle in what is now the Americas.  Given that this had to be a small party, all of the individuals would have been thoroughly admixed with each other’s ancestral DNA within just a couple of generations.  It would have been impossible for one ancestor’s DNA to only be found in some people.  To me, this argues for one of two scenarios.

First, a second immigration wave that joined the first wave but did not admix with some groups that might have already split off from the original group such as the Anzick/Montana group.

Second, multiple Oceanic immigration events.  We still have to consider the possibility that there were multiple events that introduced Oceanic DNA into the Native population.  In other words, perhaps the Aleutian Islands Oceanic DNA is not from the same migration event as the Brazilian DNA which we know is not from the same event as the Botocudo.  I would very much like to see the Oceanic DNA appear in a migration path of people, not just in one place and then the other.  We need to connect the dots.

What this new information does is to rule out the possibility that there truly was only one wave of migration – one group of people who settled the Americas at one time.  More likely, at least until the land bridge submerged, is that there were multiple small groups that exited Beringia over the 8,000 or so years it was inhabitable.  Maybe one of those groups included people from Oceana.  Someplace, sometime, as unlikely as it seems, it happened.

The amazing thing is that it’s more than 10,000 miles from Australia to the Aleutian Islands, directly across the Pacific.  Early adventurers would have likely followed a coastal route to be sustainable, which would have been significantly longer.  The fact that they survived and sent their DNA on a long adventure from Australia to Alaska to South America – and it’s still present today is absolutely amazing.

Australia to Aleutians

We know we still have a lot to learn and this is the tip of a very exciting iceberg.  As more contemporary and ancient Native people have their full genomes sequenced, we’ll learn more answers.  The answer is in the DNA.  We just have to sequence enough of it and learn how to understand the message being delivered.