Sample Flight Itinerary: Format, Fields & Travel-Planning Uses

A sample flight itinerary borrows the layout of a real one. Understanding which parts of that layout carry real information — and which parts are structurally empty on a sample — tells you most of what you need to know about when the document is useful.

The anatomy of an itinerary

A real airline itinerary is a printout of a reservation. It has four layers, and they are not equally substantial.

Identity layer. Passenger names, in SURNAME/GIVEN NAME TITLE format. This is not a stylistic choice: it mirrors how names are stored in the reservation system, and it is why your itinerary looks like it was typed by a machine in 1978.

Reference layer. The booking reference (PNR / record locator) and the e-ticket number. These are the only fields that make an itinerary checkable. Everything else is descriptive; these two are keys into a database.

Journey layer. One block per flight segment: carrier and flight number, origin and destination airports, departure and arrival dates and local times, and often aircraft type, cabin and fare class.

Commercial layer. Fare, taxes, total, baggage allowance, fare rules, and the issuing agency.

A sample itinerary can reproduce the identity and journey layers faithfully. It cannot reproduce the reference layer at all, because those values are issued by a reservation system in response to an actual booking. The commercial layer can be illustrated but not quoted — no fare on a sample is a price anyone has offered you.

Field by field

Field	On a real itinerary	On a sample
Passenger name	From the booking, matched to the passport	Whatever you type
Booking reference / PNR	6 characters, issued by the airline or GDS	Not issued — cannot exist
E-ticket number	13 digits, starts with the airline’s 3-digit code	Not issued — cannot exist
Flight number	Carrier code plus 1–4 digits	Illustrative only
Airports	IATA codes, real	Real — from the airport database
Dates and times	Scheduled, local at each airport	As entered; arrival calculated
Aircraft type	From the schedule, subject to change	Not shown
Cabin / fare class	From the fare purchased	Display choice
Baggage allowance	From the fare rules	A note you write
Fare and taxes	What was actually charged	Illustrative figure or blank
Issuing agency	The agency or airline that issued the ticket	Not applicable

The pattern is consistent: everything that describes a plan can be genuine, and everything that describes a transaction cannot.

Why the reference fields matter more than the rest

People often assume the booking reference is a formality — a serial number. It is the opposite. It is the entire document.

Given a record locator and a surname, an airline agent, a consular officer or an automated system can retrieve the actual reservation: whether it exists, whether it is ticketed, what fare was paid, and whether it has been cancelled. Everything else on the printout is a rendering of that record. The record is the fact; the printout is a description of it.

This is why a sample itinerary with an invented six-character code is worse than one with the field left blank. A blank field is honest about what the document is. An invented code makes a claim that takes one query to disprove, and the person querying is now looking at someone who tried.

The generator on this site prints SAMPLE — NOT ISSUED in both reference fields for that reason. See PNR and booking reference explained and e-ticket numbers for what those values actually encode.

What a sample gets genuinely right

Three things on a well-built sample are as accurate as on a real itinerary, and they are the three that matter for planning:

Airports. IATA and ICAO codes, city, country and coordinates come from a real airport database. If the sample says LHR, that is London Heathrow, at the coordinates London Heathrow occupies.

Distances. Great-circle distance between two coordinate pairs is a geometric fact, not an airline claim. JFK–LHR is about 5,555 km whoever flies it. See the flight distance calculator.

Time-zone arithmetic. Given a departure time, a flying time and two IANA time zones, the local arrival time and any date change are computable. This is where most hand-built itineraries go wrong, and it is the part a tool is genuinely better at. See flight time zones explained.

Reading the layout before you use it

A useful exercise: open a real itinerary you have received and find each of the four layers. Once you can see which parts of the page are keys into a system and which parts are just formatting, the question “will this sample pass?” answers itself. The parts that would be checked are the parts a sample does not have.

Every field on a flight itinerary explained — the long version of the table above
Itinerary vs boarding pass vs e-ticket — three documents, three jobs
What is a dummy ticket? — the terminology problem