From
mtDNA Haplogroup K Project Members and Matches
At
400 Members
(Revised April 15, 2007)
I recently created maps of the
frequencies of several mtDNA Haplogroup K subclades from counts of the K
Project members and their exact matches in the FTDNA database. More may be
added in the future, so check back. However, some subclades and clusters, such
as K1a4a1 and “K1a11,” are still too small for a good map. The methodology for
all maps is explained in the discussion for the first map, so don’t just skip
to your subclade. The size of the circles may not be comparable between the
different maps. I discussed these subclades recently in my most recent
MitoSearch K1000
Survey.
“K1a10” and “Pre-K1a10”: The first map is for the 16048A cluster, to which I’ve given
the temporary name K1a10. I looked at the listed countries of origin of the
current FTDNA-tested members of the K Project, plus those of their exact
matches in the full FTDNA database. Of the 387 members when I checked, 26 (that
number hasn’t changed at 400 members, but the number of matches and counts for
countries may have changed slightly) had 16048A in 10 different high-resolution
haplotypes or five different low-resolution HVR1 haplotypes. Only three of the
26 didn't have HVR2 results. However, since 16048A is a positive indicator of
the cluster, I used all 26 and matches for this map. By the way, the total of
those with 16048A at FTDNA has now reached at least 70, which is up a lot from
the 54 the last time I counted. There could be others in haplotypes not
represented in the Project. Of those 70, only 27 have HVR2 results. That means
only four with high-res results are not in the K
Project, no doubt a higher percentage than in most subclades of K. That high
percentage is due to some recruiting by those in the cluster – and, I’ll
confess, by me, to get representatives of the more unusual haplotypes.
I counted the number of total mtDNA
entries, both hi- and low-res for each country, while looking at the matches.
Then I divided the low-res numbers for each country by the number of those in
16048A listing that country. The highest frequency - no surprise - was
I think the map supports our theory
that the 16048A mutation occurred in
K1a + 524 Insertions: [Added April 15, 2007] The dataset for this map includes all Project
members, and their exact matches, in K1a with one or more pairs of position 524
insertions, except for those already mapped in the K1a10 and
Pre-K1a10 clusters above, all of which also have the 195C mutation. Others are
in subclade K1a4a1 as determined by full-sequence tests; one of those has 195C.
On the map,
I have also created a Fluxus phylogenetic diagram
for this group, only including the Project members, not their matches. This
diagram, from which I have excluded the position 309 insertions, exhibits a
star pattern after the first pair of 524s, then a branching pattern after the
second pair.
Ashkenazi and “Pre-Ashkenazi” Subclades: Dr. Doron Behar’s 2006 paper identified
three K subclades which are primarily Ashkenazi Jewish: K1a1b1a, K1a9 and
K2a2a. In general, the FTDNA customers in those subclades are usually
descendants of fairly recent immigrants from
The K1a1b1a
map [updated on April 15, 2007] is
based on 29 K Project members and 56 exact matches. Thirteen countries are
included, although the Irish entry may be in another subclade. The highest
percentage is for
The Pre-K1a9
map is based on only six results, so it may not be as trustworthy as some
of the others. It might suggest that this subclade followed its daughter, K1a9,
as far as
A triangular pattern may also be
seen on the K1a9
map, with
The K2a
map shows one of the largest, and oldest, subclades in K. There are 30
members in K. All are high-resolution by definition, since it is defined by
HVR2 mutations. The map represents a total of 60 examples. The age of the
subclade no doubt accounts for its wide distribution. In this case, some in K2a
may have followed its daughter K2a2a as far as
The K2a2a
map shows the smallest, least widespread, and probably the youngest
Ashkenazi subclade. It is based on six members and a total of 16 entries. All
the entries have the same haplotype. (There is a slightly different haplotype
in MitoSearch.) There is a definite concentration in
Comparing the three Ashkenazi maps,
it appears that each subclade started in
K1b Subclades: K1b2 may be easily identified by the combination of the 146C and 195
mutations – and the lack of 497T. Of the three main subgroups under K1b1, only
K1b1a is mapped. That subclade always has 16319A and 152C; most also have
16463G. K1b1c and one branch of K1b1b have defining HVR mutations, but none of
those has shown up in the K Project. Both K1b1a and K1b2 have sequence with and
without 524 insertions, which is unusual for K.
The K1b1a
map shows that the subclade is not found in great numbers anywhere, but it
is widely scattered. If
The K1b2
map appears to show a more northerly distribution for this subclade as
compared to its sibling above. Because it is defined by HVR2 mutations, the map
is based on 15 high-res members. The total is only 21
entries, since most of the members don’t have any exact matches. The large
K1c and K1c2: This
set of maps is for subclade K1c2 and its parent K1c. For the two maps I used
only high-res results. Any haplotype not represented
in the K Project will not be included on the maps, so some countries mentioned
in MitoSearch are absent. Those would include
The two maps are at K1c
map and K1c2
map.
The first map is labeled K1c+, which
simply means any haplotype in K1c except those in K1c2. K1c1 requires a
full-sequence test to be accurately determined. By far the largest node is for
The second map for K1c2 has fewer
countries - Portugal is gone - demonstrating the relative youth of K1c2. K1c2
actually has 48 total entries compared to 38 for K1c+; many of those listed
USA, Canada or Unknown and so are not represented on the maps.
© 2007 William R. Hurst
Administrator, mtDNA Haplogroup K
Project