How to read a PNR segment line, field by field

One dense line holds everything about a flight in a booking. Once you know where each field sits, you can read any segment in seconds — from any GDS.

A Passenger Name Record (PNR) stores each flight as a single line of tightly packed codes. It looks impenetrable the first time you see it, but the fields always appear in the same order, so it rewards a little decoding. Here is a representative segment:

 1  EK 185 K 20OCT 2 DXBBCN HK1  0815  1325  20OCT  E

Every field, left to right

1Segment number — the position of this flight within the itinerary.
EK 185Carrier and flight number — Emirates flight 185. The two-character code (EK) is the airline's IATA designator.
KBooking class (RBD) — a single letter that maps to a cabin and a fare bucket. It is airline-specific; see booking-class letters explained.
20OCTDeparture date, day then month. The year is deliberately not shown.
2Day-of-week digit, IATA numbering: 1 = Monday … 7 = Sunday. Here 2 means Tuesday.
DXBBCNOrigin and destination airport codes, run together with no space — Dubai (DXB) to Barcelona (BCN).
HK1Status code (HK = holding confirmed) plus the number of passengers on the segment (1).
0815Departure time, local to the origin airport, 24-hour clock.
1325Arrival time, local to the destination airport.
20OCTArrival date — only shown separately when it differs from the departure date (i.e. an overnight flight).
ETrailing flags vary by system — often an electronic-ticket indicator or equipment/meal code.

The two fields people misread most

The day-of-week digit

That lone digit after the date is easy to mistake for part of the date or the flight number. It is the day of the week, and it is genuinely useful: because the airline's own system generated it knowing the real booking year, it lets you infer the year that the PNR text never states outright. A 20OCT that falls on a Tuesday only lines up with specific years.

The run-together city pair

Origin and destination are printed with no separator — DXBBCN, not DXB BCN. Read it as two three-letter blocks. Occasionally OCR or a copy-paste introduces a stray space; if a tool rejects a line, a misplaced space in the city pair is a common culprit.

Local times, not elapsed time

Both times are local to their own airport, so the raw clock difference is not the flight duration whenever the route crosses time zones. Dubai (UTC+4) to Barcelona (UTC+1) shows 0815 → 1325, a five-hour-ten clock gap, but the real block time is closer to seven hours once you add back the three-hour zone change. Getting this right by hand is fiddly; getting it right automatically is one of the reasons to run a booking through a converter that carries airport time-zone data.

Want the surrounding codes too? The PNR & GDS codes guide covers status codes (HK, HL, KK…) and common terminology, and the booking-class article covers the cabin letters in depth.

Put it into practice

Reading one segment is the building block; a full itinerary is just several of them plus the passenger names and any special-service lines. Paste a whole PNR into PNRpro and it turns every segment into a plain, human-readable row — origin and destination spelled out, times formatted, durations computed — ready to price and send.

Open the converter →