PNR

A PNR, or Passenger Name Record, is a unique alphanumeric code — typically six characters — that serves as the master reference for a traveler's booking in an airline's or Global Distribution System's reservation database. Every commercial flight booking ever made generates a PNR, and that single code links together the passenger's identity, complete itinerary, contact information, seat assignment, issued ticket numbers, payment details, meal preferences, wheelchair requests, and any other special service needs. The PNR is the foundational data structure of modern commercial aviation.

What Is a PNR?

PNR stands for Passenger Name Record. It is the core data record that makes the modern travel industry function, originally standardized by IATA to enable interoperability between airlines and travel agents using different and otherwise incompatible computer reservation systems. A PNR is not merely a confirmation number: it is a structured database record containing dozens of mandatory and optional data elements. The standard PNR contains at minimum a passenger name element (the traveler's name exactly as it appears on their travel document), at least one itinerary segment (flight number, date, and booking class), a contact element (phone number or email address for irregular operations notifications), and a ticketing element (either a future ticketing deadline or an already-issued ticket number).

In GDS environments like Amadeus and Sabre, PNRs are stored on massive central servers and can be accessed by any authorized airline check-in agent or travel agent worldwide using just the six-character alphanumeric code and the passenger's surname. The six-character format — mixing letters and sometimes numbers — was designed to balance brevity with sufficient combinatorial space to avoid collisions across billions of concurrent bookings globally.

How It Works in Practice

When a passenger books a flight through United.com, through a corporate booking tool, or through a travel agency using Sabre, the reservation system creates a PNR and assigns a random-appearing six-character alphanumeric code such as "XKPL9F." This code appears on the e-ticket confirmation email and the boarding pass under labels like "booking reference," "confirmation number," or "record locator." The PNR is also where the airline stores the issued ticket number — a separate 13-digit identifier — linking the payment record to the itinerary.

Airlines share PNR data with partner carriers on interline and codeshare itineraries through an industry-standard messaging protocol, ensuring that both the operating and marketing carrier can access the booking record. PNR data is also shared with immigration and customs authorities through government-mandated programs. The US Department of Homeland Security receives PNR data on all inbound international flights at least 72 hours before departure as part of the Advance Passenger Information System (APIS). The EU's PNR Directive (2016/681) requires airlines to transmit PNR data to EU member states' Passenger Information Units for all flights into or out of the EU. Amadeus alone hosts approximately 400 million active PNRs at any given time across its global platform.

Why It Matters

The PNR is the single source of truth for every aspect of a traveler's journey from booking to boarding. Airlines use it to manage check-in eligibility, seat assignment, baggage tagging and tracking, meal preorders, wheelchair and medical assistance requests, unaccompanied minor supervision, and lounge access. Border security agencies use it for advance risk assessment before passengers board. Frequent flyer programs use it to post mileage credits. Travel management companies use it to track, report, and reconcile employee travel spending against corporate policies. For travelers, keeping the PNR code accessible at all times — saved in an email, a travel app, or written down — is essential. Mid-trip flight changes, rebooking during irregular operations, and baggage claims all require the PNR as the primary lookup key.

Key Facts and Figures

• PNR format was standardized by IATA in the 1960s to enable cross-system interoperability between airlines and the first computer reservation systems (originally SABRE, Galileo, and Amadeus predecessors).
• A standard PNR contains approximately 20 mandatory data fields and can include hundreds of optional elements including OSI (Other Service Information), SSR (Special Service Request), and free-text remarks.
• Amadeus processes over 2.5 billion PNR transactions annually across its global distribution platform.
• EU PNR Directive (2016/681) requires airlines to transmit PNR data to EU member states' authorities for all flights entering or leaving the EU, enabling advance law enforcement screening before passengers board.
• PNR codes are designed to avoid visually ambiguous characters: some systems omit 0 and O, and 1 and I, to reduce misreading errors during verbal communication at check-in counters and call centers.
• Airlines retain archived PNR data for varying periods: Sabre archives completed PNRs for up to 10 years for legal, regulatory, and analytics purposes.
• A single complex group booking itinerary — such as a corporate event with hotel, transfers, and multiple flight options — can generate a PNR containing hundreds of data elements across all standard categories.
• The six-character PNR format theoretically supports over 36^6 (approximately 2.18 billion) unique combinations, providing sufficient capacity for global simultaneous booking volumes even at peak travel periods.

Related Concepts

E-Ticket, GDS, Booking Class, NDC, Fare Rules