What Makes a Good Booking Reference? Airline PNR Codes Explained
Check in for almost any flight, anywhere in the world, on almost any airline, and you'll be asked for a six-character code, something like 4X7QK2. It's called a PNR, Passenger Name Record locator, and the fact that it's six characters on Ryanair and six characters on Singapore Airlines and six characters on an airline that didn't exist ten years ago isn't a coincidence. It's a convention that quietly works so well nobody's bothered to change it.
An airline booking reference, or PNR, is typically a 6-character alphanumeric code drawn from a roughly 32-character alphabet that excludes visually ambiguous letters like O and I. It identifies a whole reservation, potentially covering multiple passengers and flights, and is usually random rather than sequential so it can't be guessed or enumerated.
Why did six characters become the industry standard?
Six characters is long enough to give a busy airline reservation system a huge number of possible combinations, and short enough that a check-in agent, a kiosk, or a passenger reading it off a phone screen can communicate it without much friction. This convention traces back to early computerised airline reservation systems, and once major global distribution systems like Sabre and Amadeus settled on it, the format effectively became the industry default that every airline since has simply adopted rather than reinvented.
Why do PNR codes exclude certain letters?
Most airline booking references draw from an alphabet of around 32 characters rather than the full 36 letters and digits, deliberately excluding characters that are easy to misread: the letter O against the digit zero, the letter I against the digit one or a lowercase L. At the volume of check-ins a major airline processes daily, even a small percentage of misread codes translates into a meaningful number of frustrated passengers and support calls, so trimming the ambiguous characters pays for itself many times over.
What's the actual difference between a PNR and a ticket number?
A PNR identifies the reservation, which might include several passengers travelling together and several flight segments across a single trip. A ticket number is a separate, longer, purely numeric identifier issued underneath that PNR, one per passenger per ticket, used mainly for fare calculation, accounting and interline settlement between airlines. When you're checking in or looking up a booking online, you'll almost always use the PNR. The ticket number matters more behind the scenes, for refunds, reissues and revenue accounting.
Why is a booking reference usually random rather than sequential?
Unlike an invoice number, where a predictable sequence is often a feature, a booking reference frequently functions as a lightweight access credential. Combined with your surname, it's often enough to pull up and sometimes modify a reservation online. If bookings were numbered sequentially, anyone could try nearby codes and potentially stumble onto a stranger's reservation. Keeping the code effectively random, or random enough within its 32-character alphabet, makes that kind of casual guessing impractical.
Does this pattern apply outside airlines too?
The same underlying logic shows up wherever a business issues a reference that a customer needs to quote back later: hotel confirmation numbers, restaurant reservation codes, event ticket references, car rental confirmations. None of these industries share a single standard the way airlines loosely converged on six characters, but the same design goals apply everywhere: short enough to read aloud, unambiguous enough to type correctly, and unguessable enough that one customer can't stumble onto another customer's booking.
If you're building or testing a booking system of your own, the booking reference generator on this site produces properly formatted codes in the same style, entirely client-side, with ambiguous-character exclusion built in.
Frequently Asked Questions
Why are airline booking references always 6 characters?
It's a long-standing industry convention rather than a technical requirement, dating back to early airline reservation systems. Six characters from a roughly 32-character alphabet, avoiding visually ambiguous letters, gives enough combinations for a busy airline while staying short enough to read over the phone or type at a check-in kiosk.
Why do PNR codes avoid letters like O and I?
For the same reason many code systems avoid them: O looks like zero, I looks like one and sometimes like a lowercase L, and removing them cuts down on check-in errors and support calls without meaningfully shrinking the usable combination space.
Is a booking reference the same as a ticket number?
No. A booking reference, or PNR, identifies the reservation as a whole, which can include multiple passengers and multiple flight segments. A ticket number is a separate, longer numeric identifier issued per passenger per ticket, used mainly for fare and accounting purposes rather than day-to-day booking lookups.
Can two passengers have the same booking reference?
Yes, if they booked together as part of the same reservation, they share one PNR covering the whole party. Each passenger within that PNR still has their own individual ticket number underneath it.
Why do hotel and restaurant booking references look different from airline ones?
Because each industry and each individual platform designs its own format independently. There's no cross-industry standard the way there loosely is for airline PNRs, so a hotel confirmation code, a restaurant reservation number and a car rental reference can all follow completely different conventions even within the same booking aggregator.
Should a booking reference be sequential or random?
Almost always random or semi-random rather than sequential, specifically so a booking cannot be looked up or guessed by trying nearby numbers. This matters more for bookings than for something like an invoice number, since a booking reference often doubles as a lightweight access credential at check-in.