K mtDNA Haplogroup

Спасибо Джеймс!!))

I cannot add anything to what James has said, he is our favorite source of origin information. However, I do suggest viewing the YFull tree for K1c1 - https://www.yfull.com/mtree/K1c1/ . YFull has been busy adding branches, 6 new branches to K1c1, 8 new branches to K1c1b, and 2 new branches to K1c1h. They are not official, but interesting anyway. Check your extra mutations against the ones listed for each branch. Edit: Oops, I forgot James already mentioned YFull and K1c1. My article does have some general information about mtDNA and K1 and K1c that might be helpful.

Si je comprend bien, tous les halogroup (Mt-DNA) ont la même ancêtre commun. If i understand well, All the mt-DNA halogroup have tha same maternal line ancestor

Aussi tous le membres de la même haplogroup.

There may be a list of Sephardic surnames somewhere. But what percentage of Sephardic do you have at https://www.familytreedna.com/my/my-origins ?

I have NO percentage of Sephardic. I'm like 97% Askenazic. So how does one explain how more than 25% of my mtDNA haplogroup have Spanish sounding surnames. No one seems to want to address this question.

It's an interesting observation, and does sound like more than a coincidence. The actual surnames mean nothing of course, but obviously Spanish women have Spanish husbands in Spain, with Spanish surnames, which is an indication of a Spanish cluster. I see no special emphasis on Spain being reported for K1a4a1b2, in either FTDNA or YFull, but you may have an extra mutation or 2 (therefore a branch or 2 farther down) that is associated with a lineage that clusters in southwest Europe. In general, the farther you walk down the tree branches, the tighter the geographical region. As I mentioned before, those with K1a4a are widely spread across all of Europe and Eurasia, from Scandinavia to North Africa, from Spain to Turkey and Russia. One reminder - K1a4 branches are not normally associated with Ashkenazi ethnicity. I would stick to autosomal testing for detecting that.

My-Origin is mainly population-oriented estimation, i.e. based on algorithm which derived out of samples taken from living people at the time of taking. Means, that this estimation is based on the closest population available. This means that since most of your closest relatives are or have lived in Europe in the recent 200-300 years, that is what this estimation is going to show. Not surprisingly, since it is algorithm and taken DNA, you will find different estimations from different companies. For example, in FTDNA I am approx. 98% Ashkenazi, and ~2% West Asian. (200-300years estimation). In 23&ME it was mainly Ashkenazi, but also 0.4% Iberian- still based on the same 200-300 years. Just a note, One of my grandmothers has pure Sephardic surname. In DNA.land which is based on another algorithm it shows 91% Ashkenazi, 2.1 Iberian, 5.1% Northwest Africa (and some also from east Africa), and 1.7% West Asian. DNA.Land is based on different algorithm which is more current DNA oriented. i.e. this goes back in some cases to 400-500 years ago. So, I took the same files (from FTDNA) to another service for testing, “Gene2Me” via Sequencing. Their service is based on a very large scale and different algorithm which is truly based on a pure by location DNA. i.e to whom and how much my DNA is related. So, the results are “surprising”: with 16% Ashkenazi west Asian oriented, and additional 54% pure middle east (i.e. total of 70% middle east including all countries in the middle east), ~13% Italian, ~8% Iberian, and ~8% Balkan. This algorithm is precise and actually gives the evidence and impact of 1000’s of years.

Thanks for the feedback. I kind of preferred that all 44 matches within mtDNA K1a4a had a common ancestor without now having to deal with mutations and subgroups. Perhaps it will eventually make sense to me.

Another question: If a person has an extensive family tree that traces back in time hundreds of years directly from his mother, would another person, who has the same haplogroup such as mtDNA K1a4a, legitimately be able to claim those same ancestral DNA relationships to those same ancestors of the other person?

Jody, I'm not sure you are appreciating the immense timescales for mtDNA mutations. You're used to yDNA, where a mutation reported by the Big Y700 test corresponds to an average of 83 years, about 2.5 to 3 generations. A mitochondrial mutation corresponds to an average of about 2000 years! Yes, those 44 matches do all have a single common female ancestor, but she probably lived thousands of years ago. If you are K1a4a1b2, your common ancestor is estimated by YFull to be about 3600 years ago (roughly 1700 to 6800 years ago according to the latest YFull dating). YFull currently estimates K1a4a to be something like 9000 to 17000 years old, which is far older than known recorded history, has passed through many populations that have disappeared. Those with K1a4a are widely spread across all of Europe, Eurasia, and North Africa, and includes many different nationalities and languages. There are probably hundreds, maybe thousands of current lineages who are all K1a4a, and perhaps tens of thousands of K1a4a people. As we have said before, mtDNA is fun and really interesting, but rarely ever helpful for genealogy. I hate to put it so grimly, but we have to be realistic. Tracing back several hundred years is a paltry amount of time in mtDNA, since a single GD of difference can represent on average 1000 to 3000 years. I hope I didn't totally discourage you! :)

Rob, thanks for your clarification. I dont believe anyone should get discouraged when clear and concise explanations are presented.

I'm afraid your type is too numerous to be of much use in the search for ancestors. As an academic paper put it, "K1a1b1a ... accounts for 63% of Ashkenazi K lineages (or about 20% of total Ashkenazi lineages)..."

Thank you, James.

No. Mitochondrial DNA goes back too far. The estimated time to the most recent common ancestor for K1a4a is 7500 years ago according to Y-full. Nobody has a tree that deep. The best you can hope for is that by examining trees with a close genetic distance to you, maybe you can follow sister lines down to your tree. However, trees hundreds of years old on the maternal line tend to have mistakes from my experience, so be cautious.

If both persons took the full mtDNA test and both were just K1a4a, not in a further branch, and were perfect matches to each other on HVR1, HVR2, and the Coding Region, then they might be recently related.