GENEALOGY-DNA-L ArchivesArchiver > GENEALOGY-DNA > 2006-06 > 1150665854
Subject: Re: [DNA] HVR2 exact match
Date: Sun, 18 Jun 2006 17:24:14 EDT
In a message dated 6/18/2006 7:46:48 A.M. Central Daylight Time,
HVR1 Haplogroup J*, HVR2 73G, 228A, 263G, 295T, 309.1C, 315.1C, 462T, 489C.
When I contacted folks who were exact matches on my father's HVR2 mtdna, I
was told that the matches could have been 30 or more generations back....
Yes, it CAN be. It can also be recently. The KEY is to examine the where
and when of all of your lineages to see if there is any kind of geographical
One of my cousins has about 6 exact matches, and until the most recent, when
we looked at the lineages, they all led back toward the VA/NC border area.
On a map, it's quite impressive the way they start out all over the place in
the living testee's and gradually work their way back across the nation
toward a small geographical area. The oldest name we had among them was born c.
1760 and we aren't sure if the maiden name is Oliver or Day. We still haven't
found all the connections, but we are looking for marriages between the
names we have. Perhaps some day we will find them.
The most recent match is in New York. Oddly enough, however, Oliver and Day
are both names which occur in proximity to his oldest known surname LeForge.
Therefore, it's not entirely impossible that we are still looking at a
common ancestress within genealogical time -- perhaps sisters one of whom
migrated to VA and one of whom went to the New England area.
If you don't LOOK at your lineages, you might miss a connection much more
recent than 30 generations ago. Dismissing mtDNA as "too old to be of
genealogical value" is -- to me -- like skipping a book of a Virginia county's
records because "I don't have any evidence my line was ever there" (and possibly
missing the sister's will which names her brothers and their children).
Your HVR2 combination appears to be "not so common." That is added
incentive for at least looking at the lineages of all the matches.