[MilCom] Airport Codes

MJ Cleary mjcleary at bellsouth.net
Tue May 23 20:02:24 EDT 2006


----- Original Message ----- 
From: "Mike Consalvo" <mhcon at juno.com>
Subject: [MilCom] Airport Codes


> Great, another one. Didn't someone just mention this a few days ago?
>
> Why is so hard to put a name on a location? Why does everyone on the list
> have to look up the location code (Kxxx) because the person who posted it
> didn't name the location?
>
> There are people on this list from all over the country. We don't have a
> list of every airport in America, and most of us don't have to time to
> look up every code that's used.
>
> Please people, either put the airport name, or your monitoring location,
> so we know where the posted freqs are being used. That's the whole idea
> of this list, isn't it????


Here's a helpful hint I've found useful and necessary over the years; put a 
text file of all the ICAOs eitherreference. Here is one from Hugh's site: 
http://www.ominous-valve.com/airports.txt
Stations often rattle off 5 or 6 ICAOs in quick succession and frankly, 
especially for foreign airports, it's much easier to type up the code rather 
than the whole airport name.

Apologies for not including the ICAO name in the heat of a breaking 
situation with a dozen radios going. An alternative would be to simply not 
post anything at all.

BTW - Aircraft landed and runway was closed until EOD came out and disposed 
of the flare. Local news mentioned it tonight.



Mark
====================================
Monitoring Milcom from Charleston, SC

ICOM R8500, ICOM R75 (x3), DX-398, ATS-505,
BC 895XLT (x2), BC 245XLT, PRO-37, PRO-60,
PRO-2052 (x2), BC 780XLT, DX-302, DX-390
BC 898T, YB400, 45 foot PAR EF-SWL (x3)
====================================





More information about the MilCom mailing list