[MilCom] Re: MilCom Digest, Vol 25, Issue 12

[ColoradoRedlands at aol.com]

In a message dated 5/6/2006 4:46:34 PM Mountain Daylight Time,  
milcom-request at mailman.qth.net writes:

Date:  Sat, 6 May 2006 11:57:31 -0500
From: "GrayGhost"  <grayghost at cebridge.net>
Subject: Re: [MilCom] Re: MilCom Digest, Vol  25, Issue 8
To: "MILCOM" <milcom at mailman.qth.net>
Message-ID:  <004301c6712e$82fa16a0$532d4840 at u5a3b0>
Content-Type:  text/plain;    charset="iso-8859-1"

Thanks Chris, but he did  the identing not me :-)
I do not put in an indentification to unit / type  unless I hear it as too
many times there are more than one ident that can  be equated to callsign or
freq.  Primo example is the  interchangeability of aircraft among the 22nd
ARW & the 931st ARG out  of McConnell -- many times have had aircraft w/
Turbo or Kanza C/S and the  tail number belongs to the other unit.  Is why I
do not ident via C/S  only.....but that is just my 75 cents which might buy
you a cup of coffee  today
later later
walt




Thanks for the coffee Walt, I saved the money until this morning.
 
Yes, I know what you mean about the callsign-to-unit identification  
cunundrum.  I think most of us out here agree that what we do is make our  best 
guess/most likely identification on these things.  Many folks out  there can attest 
to having a visual ID on a particular aircraft with the "wrong"  callsign 
being used.  With reserve associate units without their own  aircraft, and last 
minute a/c swap outs due to maintenance, its pretty much  always a guess.  Im 
thinking we're right maybe 75% or more of the  time.
 
Chris
GJ CO US