Jitu Thaker Technical Officer — Facilitation

Advance Passenger Information (API) &

Passenger Name Record Data (PNR) —

ICAO’s Regulatory Role

Overview

• API & PNR: What are they?

• ICAO’s interest in API and PNR

• Regulatory Framework

2

Advance Passenger Information (API) . . . the collection of passenger’s and/or crew member’s biographic data

and flight details by the aircraft operator before departure of flight . . . its electronic transmission to border control agencies prior to flight departure or arrival

Collection of data in DCS: flight “open” for check-in (48hrs)

3

API Biographic Data Elements in MRZ

4

• 1. Travel Document Number • 2. Issuing State or Organization • 3. Travel Document Type • 4. Expiration Date of Document • 5. Surname/Given names(s) of holder • 6. Nationality • 7. Date of Birth • 8. Gender

API Flight Information

5

• 1. IATA Airline code & Flight number • 2. Departure Date and Time • 3. Arrival Date and Time • 4. Last place of call of aircraft • 5. Subsequent place of call of aircraft • 6. Total number of passengers on flight

Passenger Name Record (PNR) Data

The record created for each journey booked by a passenger. Contains all information used by aircraft operators for their own commercial and operational purposes in providing air transportation services.

Captured months/ weeks/days in advance of flight

6

Passenger Name Record (PNR) Data

1. API details 2. Other details of passenger and flight(s)

─ record locator ─ payment information (credit card, cash . . .) ─ contact information ─ frequent flyer number ─ seating information ─ baggage information (checked bags; excess baggage) ─ free text

7

ICAO’s Interest in API & PNR ●Art. 13 [Chicago Convention]: Entry & clearance regulations

→Passengers, crew required to comply with a State’s clearance, immigration, customs regulations on entry/departure . . .

● Art. 22: Facilitation of formalities

→States agree to prevent unnecessary delays to aircraft, passengers, crew: Administration of immigration, customs, clearance laws

● Art. 23: Customs & Immigration

→States undertake to establish customs/immigration procedures recommended pursuant to Convention

8

Annex 9 developed:

→ elaborate States’ obligations under Articles 22, 23, 24 of the Chicago Convention

→ standardize procedures for meeting legal requirements under Articles 10, 13, 14, 29, 35 of the Convention

9

API & PNR: Regulatory framework

→ Annex 9 — Facilitation

→ Assembly Resolutions

10

S

T

A

N

D

A

R

D

I

Z

A

T

I

O

N

Annex 9 (14th Edition, 2015)

States’ obligation to standardize API requirements

1. Standard 3.48

2. Standard 3.48.1

3. Standard 3.48.2

4. Standard 3.48.5

5. Standard 3.48.7

*All Mandatory (binding)*

11

Standard 3.48

Each Contracting State that introduces an Advance Passenger Information (API) system under its national legislation shall adhere to international recognized standards for the transmission of Advance Passenger Information.

►Note 1: Brief description of API ►Note 2: Information on UN/EDIFACT

PAXLST (electronic) Message ►Note 3: Non-applicability of Paxlst to

general aviation 12

Standard 3.48.1

Contracting States shall require only biographical data elements from travel documents that are machine readable per Doc 9303. All information to conform to specifications for UN/EDIFACT PAXLST messages found in the WCO/IATA/ICAO API Guidelines.

13

14

Standard 3.48.2

►If more information required ►Then request change [►WCO/ICAO/IATA:

API/PNR Contact Committee, WCO, Brussels]

[Data Maintenance Request: DMR]

15

Interactive API (iAPI)

Electronic system that transmits, during check-in,

API data elements collected by the aircraft operator to

public authorities who, within existing business

processing times for passenger check-in, return to the

operator a response message for each passenger and/or

crew member.

→BOARD / NO BOARD Message

16

RP3.48.8

States seeking to implement iAPI system:

. . . . . . conform to WCO/ICAO/IATA Guidelines.

17

Regulatory framework for PNR RP 3.49

Contracting States requiring PNR access to align their data requirements and their handling of such data with: −the guidelines contained in ICAO Doc 9944 and −in PNRGOV message implementation guidance materials published by the WCO and endorsed by ICAO & IATA

+ 2 other RPs

18

GUIDELINES: DOC 9944 Examples of issues covered:

►Meaning of PNR; Why States want access

►Data elements;

►Storage of PNR data

►Data protection; security and integrity of data

►What PNRs should NOT contain

►Sensitive data

►Methods of PNR data transfer

►Transparency & Passenger Redress

►Conflict of laws between States

19

API Guidelines & PNR Reporting Standards:

http://www.icao.int/Security/FAL/ANNEX9/Pages/Publications.aspx

20

Assembly Resolutions • A39-WP/41 (Consolidated FAL Statement)

– (new) Appendix D: Passenger Data Exchange Systems

• A39-WP/16 (Consolidated AVSEC Statement)

– Appendix C, para. 8: States . . . enhance use of API

21

ICAO action following UNSC Res. 2178 (2014)

• FALP/9 (4-7 April 2016) – Additional provisions to enhance existing API SARPs:

http://www.icao.int/Meetings/FALP/Pages/FALP9-2016.aspx

22

Recommendations of FALP/9 [A39-WP/42, Appendix]:

→ a new Standard obliging each Contracting State to establish an Advance Passenger Information (API) system.

→ a new Recommended Practice on a “passenger data single window”

→Council, Feb/March 2017

23

WHY Standardization? •Data to 3 agencies

•Data sets (possibly) different

•Separate systems: both airline & State

24

Airline

Agency A

Agency B

Agency C

WHY Standardization? • 1 set of data to 1 central system

25

Airline Agency A

(Single Window)

Agency B

Agency C

Agency D . . . . Etc.

1. Less expensive for both airline and

State 2. More efficient

jthaker@icao.int

THANK YOU! Advance Passenger Information (API) &

Passenger Name Record Data (PNR) —

ICAO’s Regulatory Role