GENEALOGY-DNA-L Archives

Archiver > GENEALOGY-DNA > 2006-06 > 1151515032


From: "bbhunt10" <>
Subject: Re: [DNA] Fw: Rare Haplotype Advice
Date: Wed, 28 Jun 2006 12:17:12 -0500
References: <380-220066227233622730@earthlink.net> <009801c69aba$e6f0e7a0$2878ebcf@12040>


Ron wrote-"It has been said that about 10% of births have a biological
father other than who is reported."


Am wondering, what is the source of your statistic? Am interested due to
some instances in my family research.

Barb


----- Original Message -----
From: "Ron Scott" <>
To: <>
Sent: Wednesday, June 28, 2006 8:58 AM
Subject: Re: [DNA] Fw: Rare Haplotype Advice


> Eric,
>
> Valuable information is, however, sometimes obscured in paper trails,
> namely, by unreported adoptions and infidelity. It never hurts to do
> testing on living relatives. If you've already done this, then you should
> have some matches. It has been said that about 10% of births have a
> biological father other than who is reported.
>
> Ron
>
> ----- Original Message -----
> From: "Eric Olson" <>
> To: <>
> Sent: Tuesday, June 27, 2006 6:36 PM
> Subject: RE: [DNA] Fw: Rare Haplotype Advice
>
>
>> Ron,
>>
>> True, and in such a case I need to keep an eye on the databases for a
>> haplotype mismatching mine by 1 or 2. Such mutation(s) would have to
>> have
>> occurred prior to 1834, because that is the birth date of the
>> ancestor-in-common of the cousins. (The proven paper trail goes back one
>> more generation to a birth about 1775.) Three mutations of slower
>> markers
>> seems a stretch, and probably would predate the genealogical time of
>> surnames.
>>
>> But today I find no matches closer than a GD of 3 in ySearch. Ditto with
>> SMGF. There are 30+ exact matches at YHRD, with that limited number of
>> markers, in a north-south swatch running from the Adriatic Sea to the
>> Baltic Sea. But no surnames in that database.
>>
>> I wonder at what rate new data is being uploaded to ySearch? Or SMGF?
>>
>> Regards,
>> Eric Olson
>>
>> Ron wrote:
>>
>>> Eric,
>>>
>>> You could try having a brother, your father, or maybe an uncle do the
>> test
>>> :P
>>>
>>> Seriously though, there was more than likely a marker or two that
>>> mutated
>> in
>>> the not too distant past that might explain this.
>>>
>>> Ron
>>>
>>> ----- Original Message -----
>>> From: "Eric Olson" <>
>>> To: <>
>>> Sent: Tuesday, June 27, 2006 11:44 AM
>>> Subject: Rare Haplotype Advice
>>>
>>>
>>> > With zero matches in the databases (except for the accidental cousin
>> from
>>> > Genographic), I decided to follow some one's advice and use a
>>> > truncated
>>> > haplotype for search purposes. So I edited the 37 marker set to 23 by
>>> > eliminating the 14 fastest markers (as noise?) which are presented in
>> red
>>> > at FTDNA. Running this core 23 marker set through ySearch yielded
>>> > zero
>>> > matches closer than at a genetic distance of 3/23, and only 6 of
>>> > those,
>>> > scattered across Europe in England, Germany, Norway, Spain and Poland.
>> I
>>> > conclude that I am not even remotely related to anyone in the ySearch
>>> > database.
>>> >
>>> > I suspect this happens a lot. I see nothing I can do to help the
>>> > situation except wait, perhaps forever, for a match to show up. I am
>>> > trying to break down a genealogical brick wall late 1700s in PA.
>>> > Recruiting cousins and uncles would generate matches of course, but
>> they
>>> > would be useless matches for this purpose. The haplotype has been
>>> > confirmed with the finding of the accidental cousin from Genographic.
>> By
>>> > accidental I mean he tested independently but was already in the known
>>> > family tree.
>>> >
>>> > Am I missing something else I could be doing, or must I simply wait
>>> > and
>>> > cross my fingers and hope that a match may show up someday?
>>> >
>>> > Eric Olson
>>> >
>>> >
>>
>> ______________________________
>
>
>
> ==============================
> Census images 1901, 1891, 1881 and 1871, plus so much more.
> Ancestry.com's United Kingdom & Ireland Collection. Learn more:
> http://www.ancestry.com/s13968/rd.ashx
>
>

This thread: