File:MTTP-Codes.pdf

From Wikispooks
Jump to navigation Jump to search

MTTP-Codes.pdf(file size: 365 KB, MIME type: application/pdf)

File Provenance

  • The file was uploaded anonymously with the following message:

If you have a ham radio or jail-broke a scanner that miraculously receives military frequency's and have not a clue what is being talked about. Or are just curious what PigAway or Snooper means you will enjoy this code book.

  • It appears to be a compendium of standard verbal/written abbreviations/acronyms for use by the US Military to compress communications.
  • It appears to have the same contents as a similar pdf posted on Public Intelligence on 28 May 2011. The cover is different and should be treated with caution.
  • It is Dated June 2003 and claims to be an update of previous versions. It has the following Heading and document references:

Disclaimer (#3)

MULTI-SERVICE BREVITY CODES

FM 3-54.10(FM 3-97.18); MCRP 3-25B; NTTP 6-02.1; AFTTP(I) 3-2.5

PREFACE

1. Purpose

This publication will ease coordination and improve understanding during multi-Service operations. A Brevity code is a code which provides no security but which has as its sole purpose the shortening of messages rather than the concealment of their content (Joint Publication 1-02).

2. Scope

This publication standardizes air-to-air, air-to-surface, surface-to-air, and surface-tosurface brevity codes. The scope is limited to those [voice] brevity codes used in multi-Service operations and does not include words unique to single-service operations. While not authoritative in nature, all services agree to these brevity code meanings. The brevity codes have been forwarded for inclusion or modification of current North Atlantic Treaty Organization (NATO) joint brevity words.

3. Applicability

This publication is intended for air and ground operations personnel at the tactical level.

4. Implementation Plan

Participating service command offices of primary responsibility (OPRs) will review this publication, validate the information, and reference and incorporate it in service and command manuals, regulations, and curricula as follows:

  • Army The Army will incorporate the TTP in this publication in U.S. Army training and doctrine publications as directed by the Commander, U.S. Army Training and Doctrine Command (TRADOC). Distribution is in accordance with initial distribution number (IDN) XXXXXXX.
  • Marine Corps. The Marine Corps will incorporate the procedures in this publication in U.S. Marine Corps training and doctrine publications as directed by the Commanding General, U.S. Marine Corps Combat Development Command (MCCDC). Distribution is in accordance with the Marine Corps Publication Distribution System (MCPDS).
  • Navy. The Navy will incorporate these procedures in U.S. Navy training and doctrine publications as directed by the Commander, Navy Warfare Development Command (NWDC)[I5]. Distribution is in accordance with Military Standard Requisition and Issue Procedure Desk Guide (MILSTRIP Desk Guide) and Navy Standing Operating Procedure Publication 409 (NAV SOP Pub 409).
  • Air Force. The Air Force will validate and incorporate appropriate portions of this publication’s multi-Service tactics, techniques, and procedures (MTTP) into Air Force doctrine documents as directed by the Commander, Air Force Doctrine Center (AFDC). Distribution is in accordance with Air Force Instruction (AFI) 33-360.

5. User Information

  • a. TRADOC, MCCDC, NWDC, Headquarters AFDC, and the Air Land Sea Application (ALSA) Center developed this publication with the joint participation of the approving Service commands. ALSA will review and update this publication as necessary.
  • b. This publication reflects current joint and Service doctrine, command and control organizations, facilities, personnel, responsibilities, and procedures. Changes in Service protocol, appropriately reflected in joint and Service publications, will likewise be incorporated in revisions to this document.

Continues....

File history

Click on a date/time to view the file as it appeared at that time.

Date/TimeDimensionsUserComment
current06:54, 30 May 2011 (365 KB)Peter (talk | contribs)
  • You cannot overwrite this file.

There are no pages that use this file.