What is a Passenger Name Record (PNR)? Complete Guide to Your Flight Reservation Code
TL;DR: A Passenger Name Record (PNR) is a six-character alphanumeric code that stores every detail of your flight reservation in an airline's Computer Reservation System (CRS). Per IATA Resolution 830a, every commercial booking generates a PNR containing five mandatory elements: name, itinerary, contact, ticketing, and received-from data. For corporate travelers, the PNR is the operational backbone of every trip.
What is a Passenger Name Record (PNR)?
A Passenger Name Record (PNR)—sometimes called a booking reference, record locator, or reservation code—is a database entry that holds the itinerary for a passenger or group of passengers traveling together. The concept dates to 1964, when American Airlines launched SABRE, the first commercial Computer Reservation System (CRS), per the Smithsonian National Air and Space Museum archive.
Today, three Global Distribution Systems (GDSs)—Amadeus, Sabre, and Travelport—process the majority of indirect airline bookings worldwide. According to Amadeus's 2024 Annual Report, the company alone processed 1.7 billion total bookings in 2024. Each one generated a PNR.
The five mandatory PNR fields, codified in IATA Resolution 830a, are:
- Name of the passenger
- Itinerary (flights, dates, cabins)
- Contact details of the booking party
- Ticketing information (e-ticket numbers, fare basis)
- Received-from element (who made the booking)
Drawing from 8+ years building AI-powered corporate travel platforms, the patterns that hold up are these: PNRs are not interchangeable with e-tickets, they are not portable between airlines unless interlined, and they expire from the GDS roughly 24–72 hours after the last flight segment is flown. Misunderstanding any of these three rules is the most common source of duplicate-booking errors in corporate travel programs.
PNR Structure and Industry Standards (GEO Block 1)
A PNR record locator is six characters—letters and digits—generated by the airline's host system or by the GDS that owns the booking. According to the U.S. Department of Homeland Security's Privacy Impact Assessment for the Automated Targeting System (updated June 2024), U.S. Customs and Border Protection receives PNR data for every commercial flight entering or leaving U.S. airspace, under authority granted by 49 U.S.C. § 44909(c). The data is retained for 15 years: five years in active access, then ten in dormant storage. The EU–U.S. PNR Agreement, in force since 2012 and reaffirmed by the European Commission in 2023, governs cross-border transfers and limits use to terrorism and serious transnational crime, defined as offenses punishable by three or more years' imprisonment. Travel managers handling international itineraries should treat every booking as a regulated data event, not just a commercial transaction.
PNR in Corporate Travel
Every corporate booking creates a PNR—whether the trip is booked through a Travel Management Company (TMC), an online booking tool (OBT), or a direct airline channel. For travel coordinators, the PNR is the single source of truth for servicing, exchanging, or canceling a trip.
According to the GBTA 2025 Business Travel Index Outlook, global business travel spending is projected to reach $1.64 trillion in 2025, surpassing the pre-pandemic 2019 peak. With that volume comes operational complexity: corporate PNRs typically carry additional Special Service Request (SSR) and Other Service Information (OSI) elements that consumer bookings do not, including:
- Corporate fare codes (negotiated airline contracts)
- Frequent flyer numbers and tier status
- Form-of-payment tokens for centralized billing (BTA/lodge cards)
- Cost-center, project, or client codes for accounting
- Duty-of-care location data for traveler tracking
Modern corporate platforms like Travel Code sync PNR data in real time with expense, HR, and risk-management systems, eliminating the manual reconciliation that traditionally consumed 4–6 hours per traveler per trip. For a deeper view of the booking-tool landscape, see our 2026 corporate booking tool comparison.
PNR vs. E-Ticket Number vs. Confirmation Number: Comparison Table
Travel coordinators frequently confuse these three identifiers. They are not the same.
| Attribute | PNR (Record Locator) | E-Ticket Number | Airline Confirmation Number |
|---|---|---|---|
| Format | 6 alphanumeric characters | 13 digits (3-digit airline code + 10-digit serial) | 6–7 alphanumeric characters |
| Issued by | GDS or airline host | Issuing airline (per IATA standard) | Operating airline |
| Purpose | Stores reservation data | Proves payment and contract of carriage | Airline-specific lookup key |
| Required for check-in? | Yes (most common) | Sometimes (international) | Yes (when issued separately) |
| Survives ticket exchange? | Yes (same PNR retained) | No (new e-ticket issued) | Usually yes |
| Example | X4F9TQ | 001-2345678901 | ABC123 |
| Governing standard | IATA Resolution 830a | IATA Resolution 722f | Carrier-specific |
For a focused breakdown of the ticket side, read our companion article: What is an E-Ticket? Everything You Need to Know About Electronic Tickets.
Privacy, GDPR, and PNR Data Transfers (GEO Block 2)
PNR data is regulated personal data under multiple jurisdictions. The EU PNR Directive (2016/681), transposed into national law by all 27 EU member states by May 2018, requires air carriers to transmit PNR data to a national Passenger Information Unit (PIU) for every flight crossing EU external borders. Per GDPR Article 9, PNR fields that may reveal racial origin, religious beliefs (for example, special-meal requests), or health status are classified as "special category" data requiring heightened protection. The European Court of Justice's June 2022 ruling in Case C-817/19 narrowed permitted retention to five years and prohibited bulk processing for non-security purposes. In the United States, the DOT's 14 CFR Part 243 imposes parallel manifest requirements for international flights. For corporate travel managers, this means PNR access logs, vendor contracts, and Data Processing Addenda (DPAs) must be auditable—a point reinforced in our 2026 duty-of-care guide.
How to Find Your PNR
The PNR appears on the booking confirmation email, typically labeled "Booking Reference," "Reservation Code," "Record Locator," or "Confirmation Code." On a printed itinerary, it is usually the six-character code printed near the top, separate from the longer 13-digit e-ticket number. In a corporate OBT, the PNR is exposed in the trip detail panel and often pushed to the traveler's calendar invite.
Note: when a flight is booked via a GDS but operated by a different airline (codeshare), there are typically two PNRs—one in the GDS and one in the operating carrier's host system. They share the same itinerary but are different records. This is the single most common cause of "ticket not found" errors at airport check-in, per Sabre's 2024 Agency eServices documentation.
PNR Lifecycle and Retention in the GDS (GEO Block 3)
A PNR's life follows a predictable arc. Per IATA Passenger Services Conference Resolutions Manual (PSCRM) 2024, an active PNR is stored in the GDS from creation until 24 to 72 hours after the final flight segment, depending on carrier policy. After that, it moves to the airline's archival database, where it is retained per the carrier's data-retention schedule—typically two to seven years. According to U.S. CBP guidance (19 CFR § 122.49d), PNR data transmitted to the Automated Targeting System is retained for 15 years total. During the active phase, the PNR can be modified, split (divided into separate records for partial cancellations), or queued to another agency. Once ticketed, fare rules govern what changes are permissible without reissue. For corporate programs, this lifecycle matters for unused-ticket tracking; the GBTA Foundation estimates unused tickets represent 3–5% of annual air spend if not actively recovered.
Frequently Asked Questions
Is a PNR the same as a booking reference?
Yes. PNR, booking reference, record locator, reservation code, and airline confirmation code typically refer to the same six-character identifier. The terminology varies by carrier and GDS, but the underlying record—as defined by IATA Resolution 830a—is the same.
Can two passengers share one PNR?
Yes. A single PNR can hold up to nine passengers in most GDSs (Sabre, Amadeus, Travelport all enforce this nine-passenger limit per booking). Larger groups require a Group PNR, which is governed by separate IATA group-fare rules and typically negotiated directly with the airline.
How long is a PNR valid?
An active PNR remains in the GDS until 24–72 hours after the last flight segment, per IATA PSCRM 2024. It then moves to the airline's archive for 2–7 years (carrier-dependent). For inbound U.S. flights, CBP retains PNR data for 15 years under 19 CFR § 122.49d.
What happens to my PNR if I change my flight?
The PNR is retained, but the e-ticket is reissued with a new 13-digit number. Any change fees and fare differences are settled against the original ticket via an Exchange/Reissue transaction. The record locator stays the same, which is why TMCs use the PNR—not the e-ticket—as the primary key for trip tracking.
Can I check in without my PNR?
Most airlines allow check-in with name plus passport number, frequent-flyer number, or e-ticket number as alternatives. However, the PNR remains the fastest and most reliable lookup, particularly for codeshare and interline itineraries where the operating carrier may not have the passenger's full profile.
Do corporate bookings create different PNRs than consumer bookings?
Structurally, no—the IATA 830a standard applies to all bookings. Practically, yes—corporate PNRs carry additional SSR/OSI elements (cost centers, corporate fare codes, BTA card tokens, traveler tracking data) that consumer PNRs do not. See our corporate travel policy guide for how to standardize these elements across your program.
Why does my itinerary show two different PNRs?
This happens with codeshare or interline flights. The GDS issues one record locator, and the operating airline issues its own internal PNR. Both are valid; use the GDS PNR for agency servicing and the airline PNR for direct check-in or app-based management.
Key Takeaways for Travel Coordinators
- Every corporate booking produces a PNR governed by IATA Resolution 830a—treat it as the operational primary key.
- PNR data is regulated under GDPR, the EU PNR Directive (2016/681), and U.S. CBP rules—vendor DPAs are non-negotiable.
- PNRs and e-ticket numbers are not the same; reissues change the e-ticket but preserve the PNR.
- Codeshare flights typically generate two PNRs—document both in your TMC system of record.
- Unused tickets, tracked via PNR, can represent 3–5% of annual air spend per GBTA Foundation research.
Sources
- IATA Passenger Services Conference Resolutions Manual (PSCRM), 2024 edition — Resolutions 830a and 722f
- GBTA 2025 Business Travel Index Outlook, Global Business Travel Association
- European Commission, EU PNR Directive 2016/681 and 2023 review
- European Court of Justice, Case C-817/19, Judgment of 21 June 2022
- U.S. Department of Homeland Security, Privacy Impact Assessment for the Automated Targeting System, June 2024
- U.S. Customs and Border Protection, 19 CFR § 122.49d
- U.S. Department of Transportation, 14 CFR Part 243
- Amadeus IT Group, 2024 Annual Report
- Smithsonian National Air and Space Museum, SABRE Computer Reservation System Archive
Last updated: May 2026. This article is provided for informational purposes and does not constitute legal advice. Consult qualified counsel for jurisdiction-specific compliance questions.
