Six Characters

Behind the simple six-character PNR lies a complex 60-year-old infrastructure. This article decodes how aviation data works, from GDS locators to the mysterious fare calculation strings.
Six Characters
Part 2 of 6 in the Iron Core series: the 60-year-old infrastructure that flies 4.5 billion people a year.
My Air India e-ticket has a line on it that looks like a typographical error:
It is not a typographical error. It is a fare calculation: expressed in a notation system designed in the 1970s, referencing a currency that does not exist (NUC), and priced to a city code (LON) rather than an airport. Every field in that string is meaningful. By the end of this piece, you will be able to read it.
But first: the six characters at the top of the ticket.
DDTCIV.
This is my PNR: Passenger Name Record. The booking reference. The confirmation code. The six characters that identify me to Air India, to the airport check-in system, and to the departure gate scanner in London. They appear on every document related to my flight: the e-ticket, the myBiz confirmation, the boarding pass, the baggage tag.
Here is what most people, and many engineers who build systems that interact with aviation, do not know about those six characters.
They are not globally unique.
What a PNR Actually Is
A Passenger Name Record is the canonical data structure of commercial air travel. Essentially every IATA-scheduled passenger booking has one. The concept was defined by IATA (International Air Professional Association) in the 1960s, formalised as Recommended Practice 1830, and has remained structurally consistent since.
The PNR is not a database record in the conventional sense. It is a structured document, closer to an append-only log, held inside the GDS that created it. In my case, that is Amadeus. The PNR is associated with a locator: a short identifier generated by the GDS at the moment the booking is saved.
That locator, DDTCIV, is six characters long. It is unique within Amadeus's system. It is not guaranteed to be unique across all GDS systems globally. A Sabre PNR and an Amadeus PNR can both carry the locator DDTCIV, belonging to completely different passengers on completely different airlines.
This is why airlines maintain their own Record Locator: a separate identifier in their own PSS, cross-referenced to the GDS locator. When you check in directly with Air India, they may show you a different reference. The GDS locator is what your travel agent sees. The airline locator is what the airline's own system calls your booking. They point to the same journey. They are not the same code.
The Five Mandatory Elements
IATA Recommended Practice 1830 specifies five mandatory elements that must be present before a PNR can be "ended": saved and assigned a locator. Without all five, the booking does not exist.
These five elements are the contract between the booking system and the airline. They exist because in 1964, American Airlines needed a minimum viable data structure that could be transmitted across a teletype network, processed in milliseconds, and stored in a fixed-size memory cell.
What is notably absent from the mandatory set: passport number, payment details, seat preference, meal request, frequent flyer number. All of these are optional enrichments. The bare minimum is name, flight, contact, ticketing status, and an audit trail of who made the booking.
My PNR, Decoded
Field by field, the status codes like HK (Holding Confirmed) are load-bearing. Other statuses include HL (Waitlisted), XX (Cancelled), and TK (Schedule change).
The E-Ticket Number
Every airline has a 3-digit IATA numeric code. 098 = Air India. The e-ticket number, not the PNR locator, is the true primary key of your booking. The PNR can change status, but the e-ticket number, once issued, is permanent. It lives in the airline's Electronic Ticket Database (ETD). When you board, the gate scanner validates your ticket number against the ETD.
The Fare Calculation Line
This is IATA fare construction notation: a domain-specific language for expressing how a fare is built. The NUC (Neutral Unit of Construction) system exists because airlines price internationally but currencies fluctuate. By pricing in a currency-neutral unit and applying the exchange rate (ROE) at the point of ticketing, IATA allows a fare to be quoted consistently across markets. The Q surcharges are fare construction surcharges required by IATA's pricing rules.
Source: Hacker News















