Sabre PNR Converter: How to Decode Sabre PNRs

Sabre is one of the most widely used GDS platforms in North America, and its PNR format differs from Amadeus in some subtle but important ways. This guide walks through how to read a Sabre PNR and convert it into a clean, client-ready itinerary.

How Sabre PNRs Differ From Amadeus

Sabre PNRs are generally laid out similarly to Amadeus — numbered passenger lines followed by numbered flight segments — but the formatting of dates, status codes, and reference numbers can vary slightly depending on the specific Sabre interface (classic Sabre vs. Sabre Red 360, for example).

Anatomy of a Sabre PNR

1.AHMED/KARIM MR
1 PK 273 Y 20AUG 4 KHIDXB HK1 0930 1130 20AUG E
2 EK 201 Y 28AUG 4 DXBLHR HK1 0830 1230 28AUG E

Passenger Line

1.AHMED/KARIM MR — passenger Karim Ahmed, title Mr. Sabre formats names the same way as Amadeus: LASTNAME/FIRSTNAME.

Flight Segment Lines

Sabre's 24-Hour Time Format

One thing to watch for: Sabre often displays times in 24-hour format without an AM/PM suffix (0930 instead of 930A), whereas some Amadeus exports use a trailing A/P. Make sure whatever conversion method you use correctly handles both formats — misreading 0930 as 9:30 PM instead of 9:30 AM would throw off the entire itinerary.

Multi-Airline Segments

In the example above, the trip involves two different airlines — PK (Pakistan International Airlines) outbound and EK (Emirates) on the return. This is common for interline bookings. Each airline maintains its own internal record, but the Sabre PNR ties the full journey together in one place. For more on how this works, see our guide on interlining.

Converting a Sabre PNR Quickly

Rather than manually resolving airport codes and calculating durations by hand, paste the raw Sabre PNR into a tool like PNRGenius. It auto-detects the format, resolves airline and airport names, and calculates accurate flight durations — correctly accounting for the time zone difference between Karachi and Dubai in the example above, rather than just subtracting clock times.

Sabre-Specific Formatting Quirks Agents Run Into

Sabre agents work across two quite different interfaces — the classic "green screen" command-line terminal and the newer Sabre Red 360 graphical workspace — and the same PNR can look noticeably different depending on which one you're copying from. Sabre Red 360's itinerary view is a formatted, human-readable rendering of the booking, not the raw PNR text; copying from that view and pasting it into a converter built to parse raw GDS syntax usually produces poor or unusable results, because the underlying line structure (numbered segments, status codes in their expected position) isn't there anymore. Always pull from the raw PNR display — typically reached with a redisplay command like *R — rather than the graphical summary screen.

Sabre PNRs also carry free-text remarks lines (numbered lines beginning with RM) that sit visually close to the segment data. These aren't flight information — they're internal notes agents leave for each other — but on a busy PNR with several remarks interspersed between segments, it's easy to misread one as a flight line at a glance, especially if you're scanning quickly.

Sabre vs. Amadeus vs. Galileo: The Same Segment, Three Ways

The status code itself — HK1 — means exactly the same thing in all three: confirmed, one passenger. It's the surrounding punctuation and time formatting that changes, which is exactly why a converter needs to know which GDS it's looking at before it can reliably parse the rest of the line.

SSRs, OSI Lines, and Multi-Passenger Sabre PNRs

Add extra travelers and special service requests to a Sabre PNR and the passenger block grows into its own numbered list, with SSR and OSI lines following the segments they apply to:

1.AHMED/KARIM MR  2.AHMED/FARIDA MRS
1 PK 273 Y 20AUG 4 KHIDXB HK2 0930 1130 20AUG E
2 SSR WCHR PK HK1 20AUG KHIDXB/P2
3 OSI PK CTCT 923001234567/P1

As with the other GDS platforms, the segment status (HK2) reflects the whole party, while the SSR and OSI lines reference an individual passenger. If you're reading a family or group Sabre booking by hand, the safest approach is to work through the SSR/OSI lines one at a time and note which passenger number each one is tied to, rather than trying to hold the whole picture in your head.

Common Copy-Paste Mistakes When Pulling a PNR From Sabre

• Including the command line itself. It's easy to select from the top of the screen and accidentally capture the *R or IR command you typed, which ends up as a stray first line in the pasted text.
• Copying the Sabre Red 360 formatted itinerary instead of the raw PNR. As noted above, this produces a document that reads well for a human but isn't structured the way a converter expects.
• Missing the day-of-week digit. Sabre inserts a single numeric weekday marker right after the date — if it gets dropped during copying (common when a terminal window is narrow and text reflows), the remaining columns can shift and misalign.
• Only capturing one page of a multi-page PNR. On bookings with many segments or remarks, classic Sabre terminals paginate the display; copying only the visible screen leaves later segments out entirely.

Status Codes Beyond HK: What Else You Might See

Most Sabre PNRs you'll handle show a clean HK for a confirmed segment. Occasionally you'll run into other two-letter codes, which follow the same convention across every GDS:

Seeing anything other than a plain HK is usually a sign that something changed after the segment was first booked — a waitlist clearing, an airline-initiated schedule change, or a reconfirmation — and it's worth double-checking the booking before sending a client an itinerary built on it.

ARNK Segments and Split PNRs in Sabre

Sabre, like every GDS, uses an ARNK line to mark a gap between two flight segments that isn't a bookable flight — a surface transfer or an open-jaw gap the passenger covers independently. It carries no airline code, flight number, or status, and sits on its own line between two real segments.

1 PK 273 Y 20AUG 4 KHIDXB HK1 0930 1130 20AUG E
2 ARNK
3 EK 201 Y 28AUG 4 DXBLHR HK1 0830 1230 28AUG E

It's also worth knowing that Sabre PNRs can be split — when one passenger in a group cancels or is rebooked separately, Sabre creates a new record locator for that portion of the party, while the original PNR keeps the remaining passengers. If you're only handed one of the two record locators after a partial change, the itinerary you convert will legitimately be missing a passenger — that's not a conversion error, it's a sign you need the other half of the split booking.

Troubleshooting a Sabre PNR That Won't Convert Cleanly