BEFORE THE

DEPARTMENT OF TRANSPORTATION WASHINGTON, DOC.

Agreements Adopted by the Traffic Conferences of the International Air Transport Association

Docket OST-2013-

APPLICATION FOR EXEMPTION FROM FILING AND APPROVAL OF AN AGREEMENT BY THE

INTERNATIONAL AIR TRANSPORT ASSOCIATION

22 May 2013 Communications with respect to this document should be sent to: Douglas Lavin Regional Vice President North America International Air Transport Association 1201 F Street, NW, Suite 650 Washington, D.C. 20004 (202) 628-9292

13455799.1

Summary DOCKET: OST-2013 DOT ORDER: pending Date: 22 May 2013 Filing fee/IATA Acct: $122 CAR003CH01 US/UST involved?: yes Intended effective date: 1 July 2013 Meeting date/time: CSC/35, Doha, Qatar, 10 March 2013 Agreement/Minutes: Recommended Practice 1630, Recommended Practice 1670 CSC/Meet/007/2013 dated 17 May 2013

APPLICATION FOR EXEMPTION FROM FILING AND APPROVAL (TIER 2 AGREEMENT FILING)

Pursuant to statements submitted by Member airlines of the International Air Transport

Association (IATA), the undersigned has been constituted to be their attorney-in-fact for filing with

the Department of Transportation copies of agreements adopted by the IATA Traffic Conferences.

On their behalf, and pursuant to the procedures specified in Order 2012-4-18

(13 April 2012), I am filling with the Department this application, the subject agreement and

supporting documentation. This agreement is a Tier 2 agreement, as specified in Appendix B to

Order 2012-4-18. The intended effective date of the agreement is 1 July 2013.

The subject agreement amends or establishes Resolutions and/or Recommended Practices

that are amongst subject areas which the Department has indicated it still chooses to review on a

case-by case basis.

The present Application requests an exemption from Condition #2 to the Departments

approval of the Provisions for the Conduct of the IATA Traffic Conferences, which condition

requires that an agreement be filed for review and appropriate action by the Department prior to

an agreements being implemented.

13455799.1

The text of the agreement and other conference documentation sent to airline Members of

IATA accompany this Notice. There is also a summary document that explains the amendment

or agreement regarding its nature and purpose.

In that context, granting the requested exemption would serve the public interest, and,

thus, meets the 49 USC 40109(c) standards for exemption from filing and approval

requirements.

Respectfully submitted: _________________________________ Douglas Lavin Regional Vice President North America International Air Transport Association Attorney-in-fact

13455799.1

CERTIFICATE OF SERVICE

A copy of this application has been served this day by first class or priority mail on the

following persons:

Chief, Transportation, Energy & Agriculture Section Antitrust Division Department of Justice Washington, DC 20530 A copy of this application has been sent this day by email to John Kiser (JohnKiser@dot.gov) and to Della Davis (Della.Davis@dot.gov) of the Department of Transportation. /s/ Douglas Lavin Douglas Lavin Date Served 22 May 2013

FINALLY ADOPTED RESOLUTIONS SUMMARY

The following Recommended Practices emanating from CSC/35 is requested for approval. The intended effective date is 1 July 2013.

RECOMMENDED PRACTICE 1630 Cargo Security

(Amending) Note: Recommended Practice 1630 was granted exemption from filing with the Department for prior approval under condition #2 imposed on the IATA bylaws through Order 2012-11-9, Issued by the Department of Transportation on the 9th day of November, 2012.

Amendment to align with the Consignment Security Declaration layout form proposed to be adopted by the International Civil Aviation Organization (ICAO) and to also add completion instructions

RECOMMENDED PRACTICE 1670 Carriage of Cargo Using Electronic Data Interchange (EDI)

(Amending) Note: Recommended Practice 1670 was granted exemption from filing with the Department for prior approval under condition #2 imposed on the IATA bylaws through Order 2012-11-9, Issued by the Department of Transportation on the 9th day of November, 2012.

Amendment to RP1670 Attachment 'A', Annex 'A' and RP1670 Attachment 'A', Annex 'C' to make reference to Resolution 600f and Resolution 600g respectively.

RECOMMENDED PRACTICE 1630 CARGO SECURITY

(AMENDNG)

CSC(35) 1630 Expiry: Indefinite

Type: A 3.12 Security Declaration 3.12.1 The appropriate authorities and/or air carriers may require for each shipment a security declaration to be provided in paper, electronic format, or any other means that may be allowed in the future. It is the responsibility of all Members and IATA Cargo Agents to be familiar and comply with any such security declaration requirements. 3.12.2 For paper security declarations, where not otherwise specified, it is recommended that the form to be used is the standard Consignment Security Declaration form shown in Attachment A. Completion instructions are shown as Attachment B. A completed form is shown in Attachment C. 3.12.3 Support of the electronic format can be provided through IATA CIMP messages (or IATA XML messages). This information can also be reproduced on the standard Consignment Security Declaration form. As an example, an indication of which fields from the Air Waybill Data (FWB) message can populate the form is shown in Attachment D.

EDITORIAL NOTE: IT HAS BEEN AGREED THAT THE FOLLOWING SECTIONS SHALL REPLACE THE CURRENT RECOMMENDED PRACTICE 1630 ATTACHMENT A, RECOMMENDED PRACTICE 1630 ATTACHMENT B, AND RECOMMENDED PRACTICE 1630 ATTACHMENT C. ALSO, A NEW SECTION SHALL BE INCLUDED FOR RECOMMENDED PRACTICE 1630, ATTACHMENT D.

R E C O M M E N D E D P R A T I C E 1 6 3 0 A t t a c h m e n t A

C o n s i g n m e n t S e c u r i t y D e c l a r a t i o n

R E C O M M E N D E D P R A T I C E 1 6 3 0 A t t a c h m e n t B

Comple t ion Ins t ruc t ions

Box Descr ip t ion

Regulated Party Category (KC, RA or AO) & Identifier The category (i.e. Known Consignor, Regulated Agent or Aircraft Operator) and its

unique identifier that originally issued the security status must be entered.

Unique Consignment Identifier The identification of the consignment itself must be entered. This may be an air waybill (format is nnn-nnnnnnnn), a house bill or a mail consignment identifier.

Content of the consignment The identification of the consignment details (e.g. goods description) must be entered in the case of a direct air waybill shipment or house waybill shipment. In case of a consolidation shipment, i.e. a master air waybill with associated house waybill(s), the consolidation box should be ticked in lieu of the goods description.

Origin The identification of the origin of the consignment must be entered. This would be the origin related to the appropriate transport document (air waybill or

house waybill) as identified in Box 2 (e.g. IATA three-letter airport or city code).

Destination The identification of the final destination of the consignment must be entered. This would be the destination related to the appropriate transport document (air waybill

or house waybill) as identified in Box 2(e.g. IATA three-letter airport or city code).

Transit/Transfer points The identification of an en-route stopping point where cargo may be transferred to

another aircraft or remain on board the same aircraft should be entered if known to the issuer, (e,g, IATA three-

letter airport or city code) otherwise this entry may be blank

Security Status The coded identification of the security status assigned to the consignment must be entered to indicate whether the consignment is secure for:

a) passenger, all-cargo and all-mail aircraft (some regions use the code SPX); b) all-cargo and all-mail aircraft only (some regions use the code SCO); or c) passenger, all-cargo and all-mail aircraft, in accordance with high-risk

requirements (some regions use the code SHR).

Received from The coded identification of the category (i.e. Known Consignor, Regulated Agent or Aircraft Operator) that tendered the consignment. If no other reason, i.e. Screening Method or Grounds for exemption is indicated and the consolidation box is not ticked then this entry cannot be blank.

Screening Method The coded identification of the screening methods (ICAO codes are still under

development) used by the Known Consignor, Regulated Agent or Aircraft Operator when securing the consignment could be entered as a reason that the security status was issued, e.g. Screening Method codes.

If no other reason, i.e. Received from or Grounds for exemptions is indicated and the consolidation box is not ticked then this entry cannot be blank.

In some cases a single screening method may not be sufficient to inspect all types of consignments, therefore more than one screening methods may be listed.

Grounds for exemptions The coded identification (ICAO codes are still under development) indicating why a

consignment is exempted from screening as defined in States NCASPs could be entered as a reason that the security status was issued, e.g. Screening Exemptions codes.

If no other reason, i.e. Received from or Screening Method is indicated and the consolidation box is not ticke