Section 38: LEO Flying Armed Transactions

From Nlets Wiki
Jump to: navigation, search

LEO Flying Armed

Important Message for Law Enforcement Officers Flying Armed (LEOFA)

The LEOFA Program has undergone several recent (May 17, 2016_2000 ET) enhancements to maintain the program's integrity and to improve service and support to Law Enforcement Officers (LEOs), who meet the requirements to fly armed on commercial aircraft nationwide. Therefore, review all content, while paying particular attention to changes to the EIT, FLN, and CAP fields (Note: Another update to the EIT explanations took effect July 20, 2016 at 2000 ET).

Since November 15 2008, for state or local LEO to fly armed the employing agency must send an AM message to the Federal Air Marshal Service. A receipt with a unique alphanumeric identifier will be returned from TSA's system to the employing agency. Requesting agencies or departments should expect a delay in response up to two hours. This identifier shall then be verified at the airport on the day of travel. In addition to the unique alphanumeric identifier, the officer must present the Nlets message to the TSA agent.

Failure to provide the unique alphanumeric identifier may result in delays due to the additional verification requirements. Please visit the program website at www.tsa.gov/travel/law-enforcement to learn more.

Detailed Flying Armed Specifications

Fields marked with ### went into effect on May 17, 2016 (2000 ET).


Entry # Char. Explanation
LEOFA N/A

Indicates to TSA that this is a LEO flying armed
request message. All messages without this will be ignored.

NAM/ N/A

Full name of flying armed LEO. Must be in the
format of last name, first name.
Example: NAM/SMITH, JOHN.
The period at the end of the line is required.

AGY/ N/A

Agency or department name of the flying armed LEO.
Example: AGY/ARLINGTON POLICE DEPARTMENT.
The period at the end of the line is required.

BCN/ N/A

Badge or credential number of the flying armed LEO.
Example: BCN/ABC123456.
The period at the end of the line is required.

OFC/ 4 or 5

Officer type. Must be either state
or local.
Example: OFC/LOCAL.
The period at the end of the line is required.

### NAO/ N/A

Name of authorizing official.
The Authorizing Official will be the Chief, Sheriff, or Law Enforcement Agency Administrator whom endorses and approves the submission of a LEO Flying Armed NLETS message and will ensure that all program requirements have been fully met prior to submission.
Must be in format last name, first name.
Example: NAO/SMITH, JOHN.
The period at the end of the line is required.

CRT/ 3 or 2

Completed required training. Must be either yes or no. A no in this field will result in a denied reply message because all LEO flying armed must have completed required training.
Example: CRT/YES.
The period at the end of the line is required.

CPN/ 10

Cell phone number of LEO flying armed. Must not contain dashes and must be exactly 10 digits.
Example: CPN/1234567890.
The period at the end of the line is required.

APN/ 10

Agency or department number of flying armed LEO. Must not contain dashes and must be exactly 10 digits.
Example: APN/1234567890.
The period at the end of the line is required.

### EIT/ One word only

Explanation of Individual's Travel (previously Escorted Individual Type).
This is a required field.
Explanations must be exactly one word long with no added spaces or punctuation.
Explanations are: PROTECTIVEDETAIL, SURVEILLANCE, ENFORCEMENT, INVESTIGATION, PRISONER.
The officer must be assigned to a protective duty or on travel required to be prepared to engage in a protective function (PROTECTIVEDETAIL).
Hazardous surveillance activity, from the time the officer would otherwise check their weapon until the time the weapon would be claimed after deplaning (SURVEILLANCE).
Official police activity that requires the officer to be "Armed and Prepared For Duty". The armed LEO must have an operational need to have the weapon accessible on the aircraft (ENFORCEMENT or INVESTIGATION).
The primary purpose of travel for the officer must be escorting or picking up a prisoner (PRISONER).
Example: EIT/PRISONER.
Enter PRISONER in EIT 'to' and 'from'.
The period at the end of the line is required.

### EIN/ N/A

Escorted individual's name. Must be in the format of last name, first name.
Example: EIN/SMITH, JOHN.
If the LEO will not be escorting an individual, the field must be formatted as follows: EIN/. or EIN/NA.
The period at the end of the line is required.

NOA/ N/A

Name of airline
Example: NOA/AMERICAN AIRLINES.
The period at the end of the line is required.

### FLN/ N/A

Flight number. Multiple flight numbers should be separated by a comma',' and a space.
Example: FLN/AA1234, AA2345.
The period at the end of the line is required.

DOF/ 6

Date of flight. Must be in the format of MMDDYY.
Example: DOF/122508.
The period at the end of the line is required.

DAP/ 3

Departing airport. Must be a known and federalized United States airport three letter code.
Must not be more than 3 characters long.
Example: DAP/DCA.
Use DAP/TSA for all Test queries.
The period at the end of the line is required.

### CAP/ 3

Connecting airport. Must be a known and federalized United States airport.
This field is not required if no connections are scheduled.
Must not be more than 3 characters long.
Example: CAP/DEN. When more than one airport connection exists, all connecting airport codes should be entered separated by a comma ',' and a space.
Example: CAP/DEN, TUC.
Use CAP/TSA for all Test queries.
The period at the end of the line is required.

FDA/ 3

Final destination airport. Must be a known and federalized United States airport.
Must not be more than 3 characters long.
Example: FDA/BOS.
Use FDA/TSA for all Test queries.
The period at the end of the line is required.

If you have questions or comments regarding the LEOFA Program or experience difficulties with submission of LEOFA identifier request messages via NLETSs, please contact the Federal Air Marshal Service, Flight Operations Division, Liaison Section at LEOFA@OLE.TSA.DHS.GOV or by calling 1-855-FLY-LEOS and follow the prompts. Please refer to our Frequently Asked Questions and Sample NLETS Messages below as a reference tool.

Roderick Allison.
Assistant Administrator, Office of Law Enforcement.
Director, Federal Air Marshal Service

Help Files

To obtain a copy of the Leo Flying Armed help file, an Administrative Message should be sent to destination "NLFLYHELP".

Top

GJXDM (DEPRECATED)

GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.

Top

NIEM

LEO Flying Armed NIEM Specifications

This section describes NIEM format specifications and provides NIEM examples of LEO Flying Armed Messages that are sent as Administrative Messages (AM) to Nlets.

All Nlets NIEM messages must be based on the Nlets NIEM Message Structure and include the standard Nlets XML Header as detailed in Message Structure. The NIEM header and hierarchy of the elements in this section have been omitted to avoid redundancy. The associated schemas and instances should be consulted to determine the correct XPaths of the elements.

Element Dictionary

Transaction types detailed below include: Administrative Message (AM).

Query Formats

Administrative Message (AM)

Mail Data (n2:NLETSMailData)
This element will contain all elements specific to this transaction.

  Mail Text (n2:MailMessageText)
  This element will contain the free text administrative message including the tags identified in the legacy section.


  Nlets recommends the use of

<!&#91;CDATA&#91;&#93;&#93;>

tags to ensure that the response does not contain any characters


  illegal in XML.

LEO Flying Armed NIEM Example

Example 1: Sample agency message to TSA

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>VAFAM0199</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="AM">
    <n2:MailMessageText>
          LEOFA
          NAM/SMITH, JOE.
          AGY/ARIZONA POLICE DEPARTMENT.
          BCN/BSO123456.
          OFC/STATE.
          NAO/WASHINGTON, GEORGE.
          CRT/YES.
          CPN/7031234989.
          APN/2023456789.
          EIT/PRISONER.
          EIN/SMITH, JOHN.
          NOA/AMERICAN AIRLINES.
          FLN/AA1234.
          DOF/122508.
          DAP/TSA.
          CAP/TSA.
          FDA/TSA.
    </n2:MailMessageText>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 2: TSA response message.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>AM</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>VAFAM0199</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[0123456789]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>07/28/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>11:34</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>07/28/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>11:34</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00006</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00018</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSMailData n2:key="AM">
     <n2:MailMessageText>
       FLYING ARMED LEO REQUEST APPROVED.
       YOUR UNIQUE LEOLANE IDENTIFIER IS: AAA11111
       NAME: JOE SMITH
       AGENCY: ARIZONA POLICE DEPARTMENT
       BADGE/CREDENTIAL: BSO123456
       NAME OF AUTHORIZING OFFICIAL: WASHINGTON, GEORGE
       COMPLETED TRAINING: YES
       CELL PHONE: 7031234989
       ESCORTED INDIVIDUAL: SMITH, JOHN
       DEPARTING AIRPORT: TSA
       CONNECTING AIRPORT: TSA
       FINAL DESTINATION AIRPORT: TSA
       AIRLINE: AMERICAN AIRLINES
       FLIGHT NUMBER: AA1234
       FLIGHT DATE: 122508
       PRINT OUT THIS REPLY AND PRESENT IT AT THE AIRPORT'S LEO LANE
     </n2:MailMessageText>
  </n2:NLETSMailData>
</n2:NLETS>

Top

Legacy (DEPRECATED)

LEO Flying Armed Legacy Specifications

Fields marked with ### went into effect on May 17, 2016 (2000 ET).

This section provides the Legacy format and an example of the Officer Flying Armed transaction.

Query Formats

Entry # Char. Explanation
LEOFA N/A

Indicates to TSA that this is a LEO flying armed
request message. All messages without this will be ignored.

NAM/ N/A

Full name of flying armed LEO.
Must be in the format of last name, first name.
Example: NAM/SMITH, JOHN.
The period at the end of the line is required.

AGY/ N/A

Agency or department name of the flying armed LEO.
Example: AGY/ARLINGTON POLICE DEPARTMENT.
The period at the end of the line is required.

BCN/ N/A

Badge or credential number of the flying armed LEO.
Example: BCN/ABC123456.
The period at the end of the line is required.

OFC/ 4 or 5

Officer type.
Must be either state or local.
Example: OFC/LOCAL.
The period at the end of the line is required.

### NAO/ N/A

Name of authorizing official.
The Authorizing Official will be the Chief, Sheriff, or Law Enforcement Agency Administrator whom endorses and approves the submission a LEO Flying Armed NLETS message and will ensure that all program requirements have been fully net prior to submission.
Must be in format last name, first name.
Example: NAO/SMITH, JOHN.
The period at the end of the line is required.

CRT/ 3 or 2

Completed required training.
Must be either yes or no.
A no in this field will result in a denied reply message because
all LEO flying armed must have completed required training.
Example: CRT/YES.
The period at the end of the line is required.

CPN/ 10

Cell phone number of LEO flying armed.
Must not contain dashes and must be exactly 10 digits.
Example: CPN/1234567890.
The period at the end of the line is required.

APN/ 10

Agency or Department Number of flying armed LEO.
Must not contain dashes and must be exactly 10 digits.
Example: APN/1234567890.
The period at the end of the line is required.

### EIT/ One word only

Explanation of Individual's Travel (previously Escorted Individual Type).
This is a required field.
Explanations must be exactly one word long with no added spaces or punctuation.
Explanations are: PROTECTIVEDETAIL, SURVEILLANCE, ENFORCEMENT, INVESTIGATION, PRISONER.
The officer must be assigned to a protective duty or on travel required to be prepared to engage in a protective function (PROTECTIVEDETAIL).
Hazardous surveillance activity, from the time the officer would otherwise check their weapon until the time the weapon would be claimed after deplaning (SURVEILLANCE).
Official police activity that requires the officer to be "Armed and Prepared For Duty". The armed LEO must have an operational need to have the weapon accessible on the aircraft (ENFORCEMENT or INVESTIGATION).
The primary purpose of travel for the officer must be escorting or picking up a prisoner (PRISONER).
Example: EIT/PRISONER.
Enter PRISONER in EIT 'to' and 'from'.
The period at the end of the line is required.

### EIN/ N/A

Escorted Individual's Name.
Must be in the format of last name, first name.
Example: EIN/SMITH, JOHN.
If the LEO will not be escorting an individual, the field must be formatted as follows;
EIN/. or EIN/NA.
The period at the end of the line is required.

NOA/ N/A

Name of Airline.
Example: NOA/AMERICAN AIRLINES.
The period at the end of the line is required.

### FLN/ N/A

Flight number.
Multiple flight numbers should be separated by a comma ',' and a space.
Example: FLN/AA1234, AA2345.
The period at the end of the line is required.

DOF/ 6

Date of flight.
Must be in the format of MMDDYY.
Example: DOF/122508.
The period at the end of the line is required.

### DAP/ 3

Departing airport.
Must be a known and federalized United States airport three letter code.
Must not be more than 3 characters long.
Example: DAP/DCA.
Use DAP/TSA for all Test queries.
The period at the end of the line is required.

### CAP/ 3

Connecting airport.
Must be a known and federalized United States airport.
Must not be more than 3 characters long.
Example: CAP/DEN. When more than one airport connection exists, all connecting airport codes should be entered separated by a come ',' and a space.
Example: CAP/DEN, TUC.
Use CAP/TSA for all Test queries.
The period at the end of the line is required.

FDA/ 3

Final destination airport.
Must be a known and federalized United States airport.
Must not be more than 3 characters long.
Example: FDA/BOS.
Use FDA/TSA for all Test queries.
The period at the end of the line is required.

LEO Flying Armed Legacy Example

Example 1: Sample agency message to TSA

AM.PASO12345.VAFAM0199.*0008000001.TXT
LEOFA
NAM/SMITH, JOE.
AGY/ARIZONA POLICE DEPARTMENT.
BCN/BSO123456.
OFC/STATE.
NAO/WASHINGTON, GEORGE.
CRT/YES.
CPN/7031234989.
APN/2023456789.
EIT/PRISONER.
EIN/SMITH, JOHN.
NOA/AMERICAN AIRLINES.
FLN/AA1234.
DOF/122508.
DAP/TSA.
CAP/TSA.
FDA/TSA.

Example 2: TSA response message.

AM.VAFAM0199
07:41 01/03/2011 05854
07:41 01/03/2011 01488 AZNLETS20
TXT
FLYING ARMED LEO REQUEST APPROVED.
YOUR UNIQUE LEOLANE IDENTIFIER IS: AAA11111
NAME: SMITH, JOE
AGENCY: ARIZONA POLICE DEPARTMENT
BADGE/CREDENTIAL: BS0123456
NAME OF AUTHORIZING OFFICIAL: WASHINGTON, GEORGE
COMPLETED TRAINING: YES
CELL PHONE: 7031234989
ESCORTED INDIVIDUAL: SMITH, JOE
DEPARTING AIRPORT: TSA
CONNECTING AIRPORT: TSA
FINAL DESTINATION AIRPORT: TSA
AIRLINE: AMERICAN AIRLINES
FLIGHT NUMBER: AA1234
FLIGHT DATE: 122508
PRINT OUT THIS REPLY AND PRESENT IT AT THE AIRPORT'S LEO LANE

Top