Tex Houston wrote:

"Guy Alcala" wrote in message
. ..
I'd like to point that they weren't, strictly speaking, generic callsigns.
Where Marshall didn't use the actual callsigns, it was because he was
working
from Red Baron event reports as opposed to other sources. Red Baron
doesn't
use the actual callsigns; rather it assigns callsigns by type of mission,
to
de-personalize the combats. So, all MiGCAP/escort flights are given names
of
U.S. cities (Ocala, Boulder, Tucson, etc.), strike flights receive metal
element or alloy callsigns (Copper, Iron, Bronze, etc.) and all support
flights, e.g. chaffers, weasels and H/K, jammers etc., receive fish names
(Tuna, Trout, Marlin etc.) These callsigns are used once only in Red
Baron,
so there's no duplication. Here's some typical Red Baron event listings
(picked out from the Red Baron III event summary) of otherwise well-known
combats:
snipped

For actual callsigns on the F-105 MiG kills see the table at:
http://www.geocities.com/Pentagon/7002/mig_kill.html . At least I think
they are the actual ones. Some were still in use when I was there later.

Yes, they are the actual callsigns (I've got the full list from "Aces and Aerial
Victories," which has all USAF kill claims). OTOH, Red Baron doesn't just list
US kills (from both services, unlike A&AV), it lists ALL A/A encounters whether
they resulted in kill claims for our side, the other side, both, or neither. So
you get listings such as the following:

"3. 15 Jan 1972/1630H
Denver: Two F-4Ds, Lead equipped with COMBAT TREE, were scrambled to attack a
single MiG-21; they fired a total of nine missiles with no damage observed."

"4. 17 Jan 1972/1735H
Phoenix: Two F-4Ds, Lead COMBAT TREE equipped, were scrambled to intercept two
MiGs in Barrel Roll (Laos). The MiGs fired three ATOLLS; no damage."

"13. 27 APR 1972/1736H
Norfolk: When GCI called 'merged plots,' two F-4Bs on MIGCAP turned to the
MIG's last known heading and were attacked from six o'clock; 02 was destroyed."

Guy