What Is a PNR? Complete Beginner's Guide for Travel Agents

If you're new to the travel industry, you've probably already heard the term "PNR" thrown around constantly — by colleagues, by GDS training material, by airlines. But what is it, actually? This guide breaks it down in plain language, with real examples, so you walk away understanding exactly what a PNR is and why it matters.

What Does PNR Stand For?

PNR stands for Passenger Name Record. It's a record stored inside an airline's or GDS's computer system that contains all the details of a passenger's booking — names, flights, dates, contact information, and more.

Think of it as the digital file that represents one trip. Every time someone books a flight through a travel agent, a GDS (like Amadeus, Sabre, or Galileo), or sometimes directly with an airline, a PNR is created behind the scenes to hold all the booking details together.

Where Did PNRs Come From?

PNRs date back to the 1960s, when American Airlines and IBM built Sabre — the first computerized reservation system for airline tickets. Before that, bookings were tracked manually on paper. The PNR format was designed to store passenger and flight data as plain text, which is part of why it still looks cryptic today — it was built for computers in the 1960s, not for humans reading it on a screen in 2026.

What's Inside a PNR?

A typical PNR contains several categories of information:

• Passenger names — usually formatted as LASTNAME/FIRSTNAME with a title (MR, MRS, MS, CHD for child, INF for infant)
• Flight segments — airline code, flight number, date, route, departure/arrival times, booking class, and status
• Contact details — phone number or email used for the booking
• Ticketing information — ticket numbers, fare details, and payment status
• Special requests — meal preferences, seat assignments, frequent flyer numbers, or other remarks

What Does a Raw PNR Actually Look Like?

Here's a simplified example of what a real PNR might look like when pulled from a GDS:

RP/LON1A2345/LON1A2345
1.SMITH/JOHN MR
3 BA 284 H 15JUL 2*LHRJFK HK1 1120A 215P 15JUL E

To someone outside the industry, this looks like nonsense. But once you know the format, it reads clearly:

• 1.SMITH/JOHN MR — the passenger is John Smith, with the title Mr
• BA 284 — British Airways flight 284
• H — the booking class (a type of economy fare)
• 15JUL — the travel date, 15th of July
• LHRJFK — flying from London Heathrow (LHR) to New York JFK (JFK)
• HK1 — status confirmed, 1 seat
• 1120A 215P — departs 11:20 AM, arrives 2:15 PM (local times)

PNR vs. Booking Reference vs. Record Locator

These three terms often get used interchangeably, which causes confusion for beginners. Here's the distinction:

So technically, the 6-character code you see on a boarding pass is the record locator for the PNR — not the PNR itself. In everyday conversation, though, most agents just say "PNR" to mean the whole booking.

Why Multiple PNRs Sometimes Exist for One Trip

If a trip involves more than one airline — say, an outbound flight on Emirates and a return on British Airways — each airline may generate its own separate PNR for its segment of the journey. The GDS PNR (created by the booking agent) ties everything together, but each airline's internal system still keeps its own record. This is one of the more confusing parts of the system for newcomers, and it's worth knowing about before a client asks why their "reference number" looks different on two different airline apps.

Why This Matters for Your Day-to-Day Work

As a travel agent, you'll be reading and working with PNRs constantly — checking booking status, making changes, and communicating itinerary details to clients. Understanding the structure means you can:

• Spot booking errors before they become a problem for the client
• Quickly verify flight times, classes, and statuses without guessing
• Explain itinerary details confidently when a client calls with questions
• Convert raw PNR text into something a client can actually read

Reading Booking Status Codes Inside a PNR

Every flight segment in a PNR ends with a two-letter status code followed by the number of seats — that's the part of the line new agents tend to skim past, and it's often the most important two characters in the whole record. The status code tells you whether the seat is actually held, or whether the segment still needs action before you can consider the trip booked.

It's common for a single PNR to mix statuses across its segments — for example, an outbound flight sitting at HK1 while the return is still HL1 because the passenger requested a route with limited availability. Never assume a whole itinerary is confirmed just because the first segment is; scan every segment line individually before telling a client their trip is locked in.

How Long Does a PNR Stay Active?

A PNR isn't permanent the moment it's created. Most GDS bookings are subject to a ticketing time limit (TTL) — a deadline by which the booking must be ticketed or it risks being automatically cancelled by the airline. Depending on the fare rules, class of service, and how far in advance the booking was made, that window can range from a couple of hours to several days.

Behind the scenes, GDS platforms also use a queue system to route messages related to a PNR back to the agent who owns it — things like schedule changes, waitlist clearances, or ticketing reminders land on a queue that the agent (or their agency) checks and works through. A PNR that sits untouched, unticketed, and unqueued past its time limit is at real risk of being purged from the system or cancelled by the airline, which is why experienced agents build TTL checks into their daily workflow rather than trusting the booking to sit safely forever.

• Always confirm the ticketing deadline when a PNR is first created, especially for complex or multi-carrier itineraries
• Check agency queues regularly — a schedule change notice that sits unread can turn into a bigger problem by the time it's noticed
• A cancelled-for-non-ticketing PNR usually has to be rebuilt from scratch, and the original fare may no longer be available

OSI and SSR Lines: The Remarks You'll See Below the Segments

Below the flight segments, a PNR often includes remark lines that carry extra information the airline or agent needs but that doesn't belong in the segment itself. The two most common types are OSI and SSR:

4 OSI YY CTC 44 20 7946 0123
5 SSR WCHR EK HK1 SMITH/JOHN MR
6 SSR VGML EK HK1 SMITH/JOHN MR

• OSI (Other Service Information) — informational remarks passed to the airline that don't require action, such as a contact phone number or a note about the booking
• SSR (Special Service Request) — an actionable request tied to a specific passenger, such as wheelchair assistance (WCHR), a vegetarian meal (VGML), or a frequent flyer number

The distinction matters because SSRs typically need a status code of their own (again, HK, NN, and so on) confirming the airline actually accepted the request — an SSR sitting at NN hasn't necessarily been fulfilled, even though it's already written into the PNR.

Common Mistakes New Agents Make Reading a PNR

A few misreadings come up constantly with newcomers, and catching them early saves a lot of client-facing embarrassment:

• Missing the year on dates. PNR dates like 15JUL almost never include a year — the system infers it from context. If a booking spans a year boundary (booked in December for travel the following January), double-check which year is actually meant.
• Overlooking the day-change marker. An asterisk or number before the arrival city (like the 2* in LHRJFK examples) signals the flight arrives a different calendar day than it departed — easy to miss, and a common source of missed connections if overlooked.
• Assuming times are in one timezone. Both departure and arrival times in a PNR are local to their respective airports, not UTC and not the passenger's home timezone. A flight landing at "2:15 PM" means 2:15 PM at the destination, not 2:15 PM where the passenger started.
• Treating booking class as decoration. The single letter after the flight number (like the H in a British Airways segment) isn't just a seat map detail — it determines the fare rules, change fees, and mileage earned, and misreading it can lead to quoting the wrong change or cancellation cost to a client.