Worldspan PNR Converter Guide

Worldspan, now part of the Travelport family alongside Galileo, has its own PNR formatting conventions that trip up agents used to Amadeus or Sabre. This guide explains how to read a Worldspan-style PNR and convert it into a clean itinerary.

Worldspan's Place in the GDS Landscape

Worldspan was historically one of the four major GDS platforms (alongside Amadeus, Sabre, and Galileo) before merging into the Travelport group. Many agencies that were originally trained on Worldspan still use formatting conventions and terminology rooted in that system, even as the underlying platform has evolved.

Reading a Worldspan-Style PNR

The core structure is similar to other GDS systems — numbered passenger lines followed by numbered flight segments — but formatting details like day-of-week markers and status code placement can differ slightly:

1.KHAN/ALIA MR
2 PK 302 Y 05SEP 1 LHEDXB HK1 2200 0030 06SEP E
3 EK 001 Y 06SEP 2 DXBLHR HK1 0830 1300 06SEP E

Breaking Down the Segment Line

Watch for Overnight Flights

Notice the segment above departs at 22:00 and arrives at 00:30 — crossing midnight. The PNR includes an explicit arrival date (06SEP) to clarify the flight lands the next day. This detail is easy to miss when reading quickly, and missing it can throw off any layover calculation for the next connecting flight.

Multi-Segment Worldspan Itineraries

Worldspan-formatted PNRs commonly include multi-city or connecting itineraries, similar to the Amadeus and Sabre examples in our other guides. The same general principles apply: track each segment's actual arrival date (not just departure date) when calculating connection times between flights.

Converting Worldspan PNRs Without Manual Decoding

Because Worldspan's formatting quirks (like the explicit arrival date for overnight segments) require careful handling, a converter that's only built for one GDS format can produce inaccurate layover times on Worldspan-style PNRs. A tool that correctly tracks arrival dates per segment — not just departure dates — avoids this issue entirely.

Worldspan's Legacy Terminal Quirks

Worldspan's architecture predates a lot of the more standardized formatting conventions used across today's GDS platforms, and agencies that were trained on it — or that still run Worldspan-derived terminal emulators inside the Travelport ecosystem — tend to encounter a few formatting habits that don't show up the same way in Amadeus or Sabre. Special service request and remarks lines, in particular, are more likely to use slash-delimited punctuation rather than the space-separated layout common elsewhere, a holdover from the system's original command syntax.

Worldspan also tends to be stricter about showing an explicit arrival date on every segment, even when the flight departs and lands on the same calendar day — where Amadeus or Galileo might omit a same-day arrival date entirely, a Worldspan-style PNR will often repeat it. That's a minor redundancy for a human reader, but it matters for any parser that assumes a missing arrival date always means "same day as departure," since a Worldspan PNR won't rely on that assumption.

Worldspan vs. Amadeus vs. Sabre vs. Galileo: The Same Segment, Four Ways

SSRs, OSI Lines, and Multiple Passengers in Worldspan PNRs

A multi-passenger Worldspan booking with special service requests follows the same overall pattern as other GDS platforms, just with the punctuation habits described above:

1.KHAN/ALIA MR  2.KHAN/ZARA MISS
2 PK 302 Y 05SEP 1 LHEDXB HK2 2200 0030 06SEP E
3.SSR/WCHR/PK/HK1/06SEP/DXBLHR/P2
4.OSI/PK/CTCT/923001234567/P1

The status code and passenger-reference logic mean exactly the same thing they do everywhere else — HK2 covers both travelers on the segment, and the /P2 or /P1 reference ties a special request to a specific person. It's only the slash-heavy punctuation style that marks this as a Worldspan-flavored display rather than Amadeus or Sabre.

Common Copy-Paste Mistakes From the Worldspan Terminal

• Misreading slash-delimited SSR lines as broken formatting rather than recognizing them as a normal Worldspan convention, and manually "cleaning up" the text in a way that actually removes meaningful structure.
• Treating a repeated arrival date as an error and deleting what looks like a duplicate, when it's simply how Worldspan confirms the flight lands on the same day it departed.
• Losing the day-of-week digit during copying from a narrow terminal window, which shifts every column after it out of alignment.
• Pasting from a legacy terminal emulator with a fixed character-per-line limit, which can hard-wrap a long segment line in the middle of a field rather than at a natural break point.
• Assuming a queue placement line is part of the itinerary. Worldspan PNRs are frequently displayed alongside queue-count or placement notes used for internal agency workflow — these sit near the segment data but describe where the booking sits in an agent's queue, not anything about the flights themselves, and including them in a paste can confuse a converter that isn't expecting non-itinerary text mixed in.

Status Codes Beyond HK: What Else You Might See

Most Worldspan 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 Worldspan

Worldspan follows the same industry-standard ARNK convention for a surface gap between two flight segments — though, consistent with its slash-heavy formatting elsewhere, the line may appear with less surrounding punctuation than the flight segments around it, making it easy to mistake for a formatting error rather than deliberate data.

2 PK 302 Y 05SEP 1 LHEDXB HK1 2200 0030 06SEP E
3 ARNK
4 EK 001 Y 10SEP 3 DXBLHR HK1 0830 1300 10SEP E

Worldspan bookings can also be split into separate record locators when part of a group's itinerary changes independently of the rest — the same behavior found across every GDS. If a converted itinerary looks like it's missing a passenger from what you remember booking, check whether a split occurred before assuming something went wrong in conversion.

Troubleshooting a Worldspan PNR That Won't Convert Cleanly