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
| Element | Example | Meaning |
|---|---|---|
| Airline + Flight | PK 302 | Pakistan International Airlines flight 302 |
| Class | Y | Standard economy fare |
| Date | 05SEP | 5th of September |
| Day-of-Week | 1 | Numbered weekday marker |
| Route | LHEDXB | Lahore to Dubai |
| Status | HK1 | Confirmed, 1 passenger |
| Times | 2200 0030 | Departs 22:00, arrives 00:30 (next day) |
| Arrival Date | 06SEP | Confirms the arrival is the next calendar day |
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.
If a converter doesn't correctly track the arrival date for overnight flights, it can calculate a wildly wrong layover time for the next connection — sometimes showing a 30+ hour "layover" when the real gap is just a few hours. Always verify layover calculations on any itinerary involving an overnight segment.
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.
Convert Worldspan PNRs Accurately
PNRGenius correctly tracks overnight flights and arrival dates, so layover times are always accurate — even on complex multi-segment trips.
Try the Free Converter →