Code Names for U.S. Military Projects and Operations
HTML formatting Copyright © 2003-2005 Andreas Parsch
Sections 1 "Names — Another Form of Designation" (except section 1.5) Copyright © 2003 Andreas Gehrs-Pahl
(The sign indicates incomplete areas.)
1 Names — Another Form of Designation
2 List of Names
Project Names and Code Words were used by military and intelligence organizations around the world for many years. They came into their own during World War I, and were virtually everywhere in World War II. The Cold War left a legacy of secrecy and a huge bureaucracy, that contributed a lot to the prevalence of Code Words and classifications, a bureaucracy which continues to dominate the US intelligence community and military to this day. There is probably only one other thing that this bureaucracy likes more than codes and classifications, and that is using abbreviations and acronyms :-). The rest of this article will deal specifically with US DoD and related Code Words, Nicknames, etc., and not with Names and Codes of any other country.
There are several different types of Names used in the US military, mostly for the purpose of designation but some simply for concealment. Most of those Names are public but deal with or describe secret things, but some Names or Code Words are actually secret by themselves.
Some of the different kinds of "Names" used are:
Of those, "Code Words" are classified, but only while they are "Active" or "Cancelled". "NATO Reporting Names" and "Call Signs" are sometimes also classified, but not always. All others, like "Nicknames", "Exercise Terms", and "Popular Names" are usually unclassified, as are "Available" (or unassigned) Code Words.
A list of all US DoD "Code Words", "Nicknames", and "Exercise Terms", as well as US and Allied "Call Signs", their meaning, and rules and regulations on how to assign and use them, can be found in the following documents. Most of those documents are classified and are prepared for the Joint Chiefs of Staff (JCS) or other agencies on a regular basis. For additional details see also "CJCSM 3150.01A", which is available at http://www.dtic.mil/doctrine/jel/cjcsd/cjcsm/m315001a.pdf.
Those documents describe how Nicknames and Code Words are assigned, and which Code Words, Nicknames, Call Signs, Exercise Terms, and alphabetical blocks for Nicknames, have been assigned to which agency. Nicknames and Code Words are usually assigned in blocks, by the Director of Operations, Joint Staff (JCS-J3), and assigned to specific DoD components.
Code Words are always classified (CONFIDENTIAL, SECRET, or higher) and always consist of a single word. The assignment of TOP SECRET Code Words requires Director, Special Programs, ODTUSD(P), approval. Code Words or blocks of Code Words are assigned to DoD components by the Joint Staff (JS). If a Code Word has been assigned, it is considered ACTIVE. Active Code Words always need to be shown with their classification, like (S) for SECRET or (TS) for TOP SECRET, and can not be discussed on unclassified networks or lines. Normally, Code Words are printed using all capital letters. [Note: In this document, Code Words are written in Small Caps to enhance readability.]
If a Code Word becomes compromised (or is suspected of being compromised), a new Code Word is assigned and the old Code Word is CANCELLED. Code Words are also cancelled, if the project, program, operation, or mission they were assigned to, was either completed or disbanded. All cancelled Code Words are still classified (at least) CONFIDENTIAL for (at least) another two years, before they become AVAILABLE (and Unclassified) again. Available Code Words can be re-used and assigned again for a different purpose. Because of this, the only Code Words that we (the general public) know about and that we discuss here, are usually Code Words that have been cancelled at one time or another. It is highly unlikely that such well-known and publicized Code Words as Oxcart or Tagboard are ever re-used, but it is possible. It may even be beneficial to re-use previously cancelled Code Words for the very same reason, as this "game" is all about deception.
Code Words should not describe or suggest the nature of what is classified. Follow-on projects or phases of a program must receive different Code Words. For example, follow-on phases of Project "Gusto" can't be assigned Code Words like "Gusto II" or "Gusto III".
Code Words can be assigned to virtually everything that might be classified, including Programs, Projects, Geographical Areas or Locations, Operations, Objectives, Missions, Plans, Tasks, Information types, etc. So called "Special Access (required) Programs" (SAP), also known as "black" programs, may have a classified Code Word assigned to them, but this is optional. Code Words are usually not assigned to Tests, Drills, Exercises, or Budget Identifiers, but many Special (Nuclear) Weapons Tests have received Code Words. Those Code Words might have originated from the DoE rather than the DoD, though.
The DoD only assigns single-word Code Words, but also sometimes uses Code Words that originate from other agencies (CIA, DoE, etc.), commercial companies, or foreign countries, which might not follow DoD directives for assignments of Code Words. Any and all Code Words that are used must be registered, to prevent double assignments or confusion. All Code Words and Nicknames are stored in the "Code Word, Nickname, and Exercise Term System" database, also known as NICKA, which was available through the military's Worldwide Military Command and Control System (WWMCCS) network, but is now only available through the JS LAN (Joint Staff Local Area Network).
Code Words are not really used to conceal the classified object itself, as the Code Words themselves are classified, too, but are used instead to implement a Need-To-Know system for Sensitive Compartmented Information (SCI), which is designed to keep individuals or groups from knowing too much about a specific system or topic, and to limit their access to only the information needed to do their specific job. There are several different SCI categories used in the DoD, and Code Words are assigned within those categories. For example, photos or tapes created by SIGINT (Signals Intelligence) or PHOTINT (Photographic Intelligence) can be viewed and analyzed by interpreters that have Special Intelligence (SI) and/or Talent-Keyhole (TK) clearances. SI covers all sorts of signals and overhead reconnaissance data, while TK covers overhead reconnaissance (both, aerial and satellite). The collecting systems (or Assets) of the NRO are covered under Byeman clearances, and receive separate Code Words. Even the individual systems and missions, like a particular satellite or launch, or a particular reconnaissance mission or flight, receive one or more numerical Codes. Those numerical codes are not covered in this article, though.
Specific types of information may also receive specific Code Words, for example Umbra, which covers particularly sensitive communications intelligence (COMINT) or Ruff, which covers specific intelligence based on satellite imagery. Some of those Code Words (like Cosmic, Gamma, Umbra, Byeman, Talent, and Keyhole) are still used, even though they are publicly known for a long time.
Nicknames are always unclassified, and (usually) consist of two separate words. The first word must start with two letters selected from a range of alphabetical blocks that are assigned to different agencies by the Joint Staff (JS) (see section 1.4). Often, specific First Words from those alphabetical blocks are reserved for specific types of users, projects, or operations (see section 1.5). This practice exists since at least the early 1970s, but I don't know how any earlier Nicknames were assigned, and if similar rules were followed.
Nicknames should not contain the words "Project", "Operation", "Exercise", or consist of two separate words that also exist as a single word, like "Moon Light". Sometimes, three words are used, and the first or second word is sometimes an acronym. Follow-on projects or additional phases of a program often receive Roman Numeral suffixes, like "Peace Vector II" and "Peace Vector III", etc. In case of such multi-phase programs, the first, original project often receives a Roman Numerical "I" suffix, even if it originally did not have that extra "I" assigned to it. In the above example, "Peace Vector" and "Peace Vector I" would be equivalent and would address the same program. Nicknames are most often printed using all capital letters, but this does not seem to be a fixed rule. [Note: In this document, nicknames are written in Small Caps to enhance readability.] Nicknames should not be "exotic words, trite expressions, or well-known commercial trademarks". They should also "not express a bias inconsistent with traditional American ideals or foreign policy. Convey connotations offensive to good taste or derogatory to a particular group, sect, or creed, or convey connotations offensive to our allies or other nations."
All departments and agencies usually place additional restrictions on the assignment of Nicknames, such as that they should not contain words that are "close in spelling or pronunciation to a code word" or "any two-word combination voice call sign found in either JANAP-119 or ACP-119." In addition, sometimes First Words are assigned to specific departments, units, or project types.
Nicknames can be assigned to virtually the same things as Code Words, like Programs, Projects, Events, Geographical Areas and Locations, Operations, Objectives, Missions, Plans, Tasks, and Tests, etc. So called "Special Access Programs" (SAP), also known as "black" programs, must have an unclassified Nickname assigned to them. Even though Nicknames are always unclassified, they should not be discussed or mentioned on unclassified networks or telephone lines, unless all aspects, including organizational associations, are completely unclassified. SAPs usually also receive a trigraph or digraph (three or two-letter codes), which in case of digraphs, are usually the first two letters of the two unclassified words of the Nickname, like "TK" for "Talent-Keyhole" -- even though "Talent" and "Keyhole" are two separate Code Words, rather than a Nickname, in this example. An example for a trigraph might be "ONW" for "Operation Northern Watch" (even though ONW is not a SAP, of course).
Sometimes, whole groups of projects or programs are grouped under a single Nickname, like the NRO Nicknames Senior Keyhole or Senior Year, which (apparently) cover all overhead (photo) reconnaissance satellites and all overhead (photo) reconnaissance aircraft, respectively.
Many projects also receive a Project Number for logistical purposes. This "Number" actually consists of a three-character alphanumeric code. Where known, this code is also given in the accompanying list of Nicknames.
Exercise Terms should be considered a special form of Nickname, as they are always unclassified and for public use, and because they often consist of two words, and because they should be based on the same alphabetical blocks of possible words. Because exercises are often repeated on a regular basis, either quarterly, annually or bi-annually, specific exercises are often indicated by added numerical postfixes, like "Roving Sands '99", or "Red Flag 2/03", or "Balikatan 2000".
There is also usually no constraint on the meaning of Exercise Terms, and it is perfectly fine if the name used describes the exercise or any aspect of it. Some DoD components assign specific meanings to either the first or both words. As an example, all NORAD exercise terms use the first word to describe the organization or agency responsible, while the second word describes the type of exercise, test, or experiment that will be conducted.
The following alphabetical blocks are assigned to the listed DoD components, agencies, and unified or specified commands, of which 24 different ones exist, as far as I know. Except for 'X', all initial letters are divided into four blocks, resulting in a total of 101 blocks (numbered alphabetically except for 'X', which appears to be regarded as a "special" letter). A few blocks are still unassigned. The table is from CJCSM 3150.29A, but it is not known if edition 3150.29B has changed any block assignments.
|First Letters||Command / DOD Component / Agency|
|1||AA - AF||USSOCOM (US Special Operations Command)|
|2||AG - AL||USACOM (US Atlantic Command)|
|3||AM - AR||USSPACECOM (US Space Command)|
|4||AS - AZ||USEUCOM (US European Command)|
|5||BA - BF||USPACOM (US Pacific Command)|
|6||BG - BL||USSOUTHCOM (US Southern Command)|
|7||BM - BR||USSOCOM (US Special Operations Command)|
|8||BS - BZ||USSTRATCOM (US Strategic Command)|
|9||CA - CF||US Army|
|10||CG - CL||US Navy|
|11||CM - CR||US Air Force|
|12||CS - CZ||US Marine Corps|
|13||DA - DF||NSA (National Security Agency)|
|14||DG - DL||DNA (Defense Nuclear Agency)|
|15||DM - DR||DIA (Defense Intelligence Agency)|
|16||DS - DZ||DCA (Defense Communications Agency) (note 1)|
|17||EA - EF||USCENTCOM (US Central Command)|
|18||EG - EL||JCS (Joint Chiefs of Staff)|
|19||EM - ER||USSOCOM (US Special Operations Command)|
|20||ES - EZ||USACOM (US Atlantic Command)|
|21||FA - FF||USSPACECOM (US Space Command)|
|22||FG - FL||USEUCOM (US European Command)|
|23||FM - FR||USPACOM (US Pacific Command)|
|24||FS - FZ||USSOUTHCOM (US Southern Command)|
|25||GA - GF||USSOCOM (US Special Operations Command)|
|26||GG - GL||USSTRATCOM (US Strategic Command)|
|27||GM - GR||US Army|
|28||GS - GZ||US Navy|
|29||HA - HF||US Air Force|
|30||HG - HL||US Marine Corps|
|31||HM - HR||NSA (National Security Agency)|
|32||HS - HZ||DNA (Defense Nuclear Agency)|
|33||IA - IF||DIA (Defense Intelligence Agency)|
|34||IG - IL||DCA (Defense Communications Agency) (note 1)|
|35||IM - IR||USCENTCOM (US Central Command)|
|36||IS - IZ||JCS (Joint Chiefs of Staff)|
|37||JA - JF||USSOCOM (US Special Operations Command)|
|38||JG - JL||USACOM (US Atlantic Command)|
|39||JM - JR||USSPACECOM (US Space Command)|
|40||JS - JZ||USEUCOM (US European Command)|
|41||KA - KF||USPACOM (US Pacific Command)|
|42||KG - KL||USSOUTHCOM (US Southern Command)|
|43||KM - KR||USSOCOM (US Special Operations Command)|
|44||KS - KZ||USSTRATCOM (US Strategic Command)|
|45||LA - LF||US Army|
|46||LG - LL||US Navy|
|47||LM - LR||US Air Force|
|48||LS - LZ||US Marine Corps|
|49||MA - MF||NSA (National Security Agency)|
|50||MG - ML||DNA (Defense Nuclear Agency)|
|51||MM - MR||DIA (Defense Intelligence Agency)|
|52||MS - MZ||DCA (Defense Communications Agency) (note 1)|
|53||NA - NF||USCENTCOM (US Central Command)|
|54||NG - NL||JCS (Joint Chiefs of Staff)|
|55||NM - NR||USEUCOM (US European Command)|
|56||NS - NZ||USPACOM (US Pacific Command)|
|57||OA - OF||USSOCOM (US Special Operations Command)|
|58||OG - OL||USSTRATCOM (US Strategic Command)|
|59||OM - OR||US Army|
|60||OS - OZ||US Navy|
|61||PA - PF||US Air Force|
|62||PG - PL||US Marine Corps|
|63||PM - PR||JCS (Joint Chiefs of Staff)|
|64||PS - PZ||USTRANSCOM (US Transportation Command)|
|65||QA - QF||USACOM (US Atlantic Command)|
|66||QG - QL||-|
|67||QM - QR||USSOUTHCOM (US Southern Command)|
|68||QS - QZ||US Army|
|69||RA - RF||US Navy|
|70||RG - RL||US Air Force|
|71||RM - RR||US Army|
|72||RS - RZ||US Navy|
|73||SA - SF||US Air Force|
|74||SG - SL||USEUCOM (US European Command)|
|75||SM - SR||USACOM (US Atlantic Command)|
|76||SS - SZ||DIA (Defense Intelligence Agency)|
|77||TA - TF||USPACOM (US Pacific Command)|
|78||TG - TL||OSD (Office of the Secretary of Defense)|
|79||TM - TR||US Army|
|80||TS - TZ||USTRANSCOM (US Transportation Command)|
|81||UA - UF||US Army|
|82||UG - UL||USTRANSCOM (US Transportation Command)|
|83||UM - UR||USACOM (US Atlantic Command)|
|84||US - UZ||US Army|
|85||VA - VF||USPACOM (US Pacific Command)|
|86||VG - VL||USSPACECOM (US Space Command)|
|87||VM - VR||USTRANSCOM (US Transportation Command)|
|88||VS - VZ||-|
|89||WA - WF||DMA (Defense Mapping Agency) (note 2)|
|90||WG - WL||US Army|
|91||WM - WR||USTRANSCOM (US Transportation Command)|
|92||WS - WZ||-|
|93||YA - YF||DIS (Defense Investigative Service) (note 3)|
|94||YG - YL||USTRANSCOM (US Transportation Command)|
|95||YM - YR||USSTRATCOM (US Strategic Command)|
|96||YS - YZ||-|
|97||ZA - ZF||OSD (Office of the Secretary of Defense)|
|98||ZG - ZL||-|
|99||ZM - ZR||-|
|100||ZS - ZZ||-|
|101||XA - XZ||White House Military Office|
Those assignments could very well change over time, especially when new organizations and commands are created or deactivated.
Recently, many of the US-led Operations and Exercises received more often Nicknames that are not in line with the assigned blocks, but instead are supposed to sound "patriotic" or maybe "inspiring". For some insight on how some of the more popular operations' names were assigned, see the following interesting article at http://carlisle-www.army.mil/usawc/Parameters/1995/sieminsk.htm.
The following words were at one time or another permanently assigned to a specific department or user for use as first word in two-word nicknames. It includes only those words explicitly listed as "permanently assigned first words" in one of our primary sources, and is certainly incomplete. If a using agency no longer exists, the name assignment may have been cancelled, inherited by its successor, or reassigned to another user. Also, nicknames older than the permanent assignment may start with the word although they did not originate from the listed user.
|So far, primarily U.S. Air Force names are listed. Source  includes also many non-USAF first words, which will be added to the list as well.|
|First Word||Assigned To|
|Amazon||NORAD Cheyenne Mountain|
|Badger||USN Pacific Fleet|
|Balance||USPACOM; joint exercises|
|Ballistic||USN Pacific Fleet|
|Beach||USN Pacific Fleet|
|Bean||USN Pacific Fleet|
|Bear||USN Pacific Fleet|
|Beard||USN Pacific Fleet|
|Bearer||USN Pacific Fleet|
|Bearing||USN Pacific Fleet|
|Beauty||USN Pacific Fleet|
|Beaver||USN Pacific Fleet|
|Beige||USN Pacific Fleet|
|Belfry||USN Pacific Fleet|
|Bell||USN Pacific Fleet|
|Belt||USN Pacific Fleet|
|Bench||PACAF (Pacific Air Forces)|
|Bend||PACAF (Pacific Air Forces)|
|Bendix||PACAF (Pacific Air Forces)|
|Beret||PACAF (Pacific Air Forces)|
|Berry||PACAF (Pacific Air Forces)|
|Best||PACAF (Pacific Air Forces)|
|Bevel||PACAF (Pacific Air Forces)|
|Buggy||USAF SAC (Strategic Air Command)|
|Burning||USSTRATCOM (formerly USAF SAC); RC-135 missions|
|Busy||USSTRATCOM (formerly USAF SAC)|
|Chair||ONR (Office of Naval Research)|
|Chalk||USN (N89/N7SP); Special Access Programs|
|Challenge||USN Chief of Naval Operations (N6)|
|Channel||USN (N89/N7SP); Special Access Programs|
|Charade||USN Chief of Naval Operations (N2)|
|Check||USN Naval Criminal Investigative Service|
|Cheese||USN Chief of Naval Operations|
|Cherry||USN Chief of Naval Operations (N2)|
|Chipped||USN Chief of Naval Operations (N2)|
|Chocolate||USN Chief of Naval Operations (N2)|
|Church||USN Chief of Naval Operations (N095)|
|Cinnamon||USN Chief of Naval Operations (N2)|
|Circuit||USN Chief of Naval Operations (N6)|
|Clamp||USN Naval Criminal Investigative Service|
|Clarinet||USN Chief of Naval Operations (N61)|
|Classic||USN Naval Security Group|
|Claymore||USN Chief of Naval Operations (N87)|
|Clipper||USN Chief of Naval Operations (N3)|
|Cluster||USN Naval Intelligence|
|Cobbler||USAF AAC (Alaskan Air Command)|
|Cobra||USAF Headquarters (Air Force Intelligence)|
|Cold||USAF MAC (Military Airlift Command)|
|College||USAF ADC (Air Defense Command)|
|Colony||USAF Headquarters (AFCOR)|
|Colt||USAFE (U.S. Air Forces in Europe)|
|Columbine||USAF AFAFC (Air Force Accounting & Finance Center)|
|Comet||USAF Headquarters (AFRDSC)|
|Comfort||AFRES (Air Force Reserve) Headquarters|
|Comfy||USAFSS (USAF Security Service), Air Intelligence Agency|
|Commando||PACAF (Pacific Air Forces)|
|Compass||USAF Headquarters (AFRDR)|
|Competent||USAF TAC (Tactical Air Command)|
|Comply||PACAF (Pacific Air Forces)|
|Concrete||USAF Headquarters (AFOCE)|
|Contract||USAF Headquarters (AFSLP)|
|Control||USAF Headquarters (AFIGO)|
|Cool||USAF AAC (Alaskan Air Command)|
|Cope||PACAF (Pacific Air Forces); exercises|
|Copper||USAF Headquarters (AFSPP)|
|Coral||USAF AFMC (Air Force Material Command)|
|Corona||USAF Headquarters (AFCCS)|
|Coronet||USAF ACC (Air Combat Command); formerly TAC (Tactical Air Command); fighter or bomber deployments|
|Cosy||USAF AFLC (Air Force Logistics Command)|
|Cougar||USAF AFAFC (Air Force Accounting & Finance Center)|
|Council||USAF Headquarters (AFBSA)|
|Counter||USAF AFAFC (Air Force Accounting & Finance Center)|
|Country||USAF Communications Command|
|Credible||USAF AFMC (Air Force Material Command)|
|Creek||USAFE (U.S. Air Forces in Europe)|
|Crested||USAF Headquarters (AFOAP)|
|Crew||USAF AFTAC (Air Force Technical Applications Center)|
|Crispy||USAF MAC (Military Airlift Command)|
|Crowfoot||AFRES (Air Force Reserve) Headquarters|
|Crown||USAF ACC (Air Combat Command); formerly TAC (Tactical Air Command)|
|Crystal||USAF AAC (Alaskan Air Command)|
|Hacienda||USAF OAR (Office of Aerospace Research)|
|Hallmark||AFRES (Air Force Reserve) Headquarters|
|Hammer||USAF AFCS (Air Force Communications Service)|
|Handy||USAF ACIC (Aeronautical Chart and Information Center)|
|Hardy||USAF AFLC (Air Force Logistics Command)|
|Harvest||USAF Headquarters (AFSDC)|
|Hasty||USAF ATC (Air Training Command)|
|Have||USAF AFSC (Air Force Systems Command)|
|Haven||USAF OAR (Office of Aerospace Research)|
|Hazy||USAF ACIC (Aeronautical Chart and Information Center)|
|Heavy||USAF Headquarters (AFXPD)|
|Hectic||USAF ACIC (Aeronautical Chart and Information Center)|
|Heroic||USAFA (U.S. Air Force Academy)|
|Lock||USAF AFCS (Air Force Communications Service)|
|Lofty||USAFA (U.S. Air Force Academy)|
|Look||USAF Headquarters (AFIDI, AFISA, AFIIN) Norton AFB|
|Low||USAF ATC (Air Training Command)|
|Loyal||USAF AU (Air University)|
|Pacer||USAF AFLC (Air Force Logistics Command); Conversion/Modification/Update programs|
|Panda||USAF AFCS (Air Force Communications Service)|
|Papa||USAF AAC (Alaskan Air Command)|
|Party||USAF ATC (Air Training Command)|
|Peace||USAF Headquarters; FMS/MDAP programs|
|Perky||USAF Southern Command|
|Pet||USAFE (U.S. Air Forces in Europe)|
|Rich||USAF ADC (Air Defense Command)|
|Riding||USAF Security Service|
|Ritzy||Secretary of the Air Force (SAFOS)|
|Rivet||USAF Headquarters; ELINT/ECM programs|
|Sage||USAF Security Service|
|Salty||USAF MAC (Military Airlift Command)|
|Sandy||USAF AU (Air University)|
|Savage||USAF Southern Command|
|Scarlet||USAF ADC (Air Defense Command)|
|Scenic||USAFA (U.S. Air Force Academy)|
|Science||USAF Headquarters (AFRDC)|
|Search||USAF Headquarters (AFRRP)|
|Secure||USAF Headquarters, Kirtland AFB|
|Seed||USAF Headquarters (AFRPD)|
|Serious||USAF AFSC (Air Force Systems Command)|
 Department of Defense Regulation DoD 5200.1-R
"DoD Information Security Program"
 HQ NORAD Regulation 11-3 "Administrative Practices - Code Words, Nicknames, and Exercise Terms"
 OPNAV Instruction OPNAVINST 5511.37C "Nicknames, Exercise Terms and Code Words"
 Marine Corps Order MCO 5030.2C "Policies and Procedures Concerning the Use of Code Words, Nicknames, and Exercise Terms"
 Air Force Manual AFMAN 23-110, Volume 1, Part 4 "Standard Supply Codes"
 Chairman of the Joint Chiefs of Staff Manual CJCSM 3150.29A "Codename, Nichname, and Exercise Term Report (NICKA)"
 William M. Arkin: "Code Names: Deciphering U.S. Military Plans, Programs And Operations In The 9/11 World", Random House, 2005
The listing includes mainly two-word nicknames for U.S. military aviation-related projects, operations, exercises and foreign aid programs from around the 1960s and later. A few names (e.g. single-word CIA codes), which would fall outside that scope are included nevertheless, when one of our authors happened to come across it ;-).
(1) The initial name list was provided by Andreas Gehrs-Pahl, who collected the information over a long time from numerous public sources.
(2) A large number of names was grabbed from the "Code Names Handbook", published by Defense Marketing Services (D.M.S.) in 1983. The two-word names from the D.M.S. listing can be downloaded as a ZIP'ed PDF file (323 KB). Many thanks go to Per Nyström, who has done a fantastic job in scanning and OCR'ing the printed publication!
Notes: All names in our tables, whose entries were copied verbatim from the D.M.S. handbook are shown in blue. This indicates that the information is taken directly from a 1983 publication, and may therefore be completely outdated. A few entries, which were definitely incorrect, have not been ported from the D.M.S. handbook. Also, the term "cancelled" in a D.M.S. description apparently does not mean that the program never actually started. It probably can also indicate that the program had already been terminated at the time when D.M.S. compiled their handbook.
Copyright Note: The D.M.S. data is made available with the permission of
Forecast International Inc.
(http://www.forecastinternational.com). Forecast International
is the current owner of all former D.M.S. assets, and holds the copyright to all D.M.S. publications. Regarding the publication
of parts of the 1983 "Code Name Handbook" on the
Forecast International issues the following disclaimer:|
(3) William M. Arkin: "Code Names: Deciphering U.S. Military Plans, Programs And Operations In The 9/11 World", Random House, 2005
This source lists several thousand code names and nicknames for post-Cold War projects, programs, exercises, etc.. A subset of these names has been added to the tables on this web site.
|The copying of names from the book to the tables has not yet been started.|
|Entries, which only have "[...]" in the description column, are preliminary and will eventually be either edited or removed.|
Comments and corrections to: Andreas Parsch
Back to Home page