Flight Itinerary Guide: How to Read and Plan an Air Trip

An itinerary is a description of a journey held in a reservation system. Learning to read one properly takes about ten minutes and saves a great deal of confusion at airports.

The shape of the document

Airline itineraries vary in styling but share a structure, because they are all rendering the same underlying record.

At the top: who is travelling and how the booking is identified. In the middle: one block per flight, in travel order. At the bottom: fare, baggage and the conditions attached to the ticket.

The middle section is where people misread things, because a single “flight” on an itinerary is not always a single aeroplane, and a single journey is often several flights.

Reading a segment

A segment is one takeoff and one landing. A typical line reads something like:

BA 112  LHR London Heathrow  T5   06 Oct  08:35
        JFK New York Kennedy  T7   06 Oct  11:35
        Economy (Q)  ·  Boeing 777-200  ·  1 checked bag

Six things are worth noticing.

The carrier code is the marketing carrier. BA 112 is the flight number British Airways sells under. The aircraft may be operated by another airline entirely on a codeshare. If your itinerary says “operated by”, that second name is who you actually check in with.

Both times are local. 08:35 is London time; 11:35 is New York time. The flight is not three hours long — it is about seven. This single convention causes more missed connections than any other feature of the document.

The terminal can change. T5 is scheduled information, valid when the itinerary was issued. Terminals get reassigned. Check on the day.

The fare class letter matters more than the cabin name. Economy (Q) — the Q determines what you paid, whether you can change the ticket, and how many miles you earn. Two people in adjacent economy seats can hold very different tickets. See fare class vs cabin class.

Aircraft type is indicative. Equipment swaps are routine and do not entitle you to anything.

Baggage shown is what the fare includes at the time of issue, and can differ between segments on a mixed-carrier journey.

Reading a connection

When two segments appear back to back, the gap between the arrival of the first and the departure of the second is your connection time. Two questions decide whether it is enough:

Is it one ticket or two? On a single ticket, the airline is responsible for rebooking you if the first flight is late. On two separate tickets — a “self-transfer” — you are responsible, and a missed connection means buying a new ticket. The itinerary tells you: separate tickets have separate booking references.

Does it clear the minimum connection time? Every airport publishes a minimum connection time, which varies by whether you change terminals, clear immigration or re-check bags. A connection sold on one ticket meets that minimum by construction. One you build yourself might not.

The difference between a layover, a stopover and a connection is worth getting straight, because it changes what you can do with the time and sometimes what you pay: layover vs stopover vs connection.

Reading the dates

The most common misreading of an itinerary is an arrival date. Long eastbound flights routinely land the next calendar day; long westbound flights across the Pacific can land the day before they departed.

The itinerary shows the correct dates. The trouble comes when you copy them into a hotel booking or a visa form from memory, having read the departure date and assumed the arrival matched.

If you are building a plan rather than reading one, the time zone planner computes the arrival date for you, and flight time zones explained covers why the date line behaves as it does.

Planning so the itinerary works

Reading is half of it. If you are constructing a trip:

Work in local time throughout. Write down every departure and arrival in the local time of the airport it happens at, exactly as the itinerary will show it.

Build the connections with slack. The published minimum is a floor, not a recommendation. On an international connection with a terminal change, two hours is comfortable; the published minimum might be 60 minutes.

Check the airports, not just the cities. London has six. New York has three. Flying into one and out of another is legitimate but means a surface transfer you have to plan and pay for. The airport code lookup shows which airports serve a city.

Sanity-check the total. Add up flying time plus connections. A routing that looks clever on paper occasionally turns out to take 31 hours.

The multi-city trip planner does the arithmetic for a chain of legs, and the travel itinerary checklist covers what to confirm once the plan is settled.

When the itinerary changes

Schedules change. Airlines move flights, retime them, and occasionally cancel them months ahead. When that happens you are notified, and the itinerary you were sent is superseded.

Two habits help: keep the booking reference somewhere retrievable rather than relying on a saved PDF, and re-check the itinerary in the airline’s own system a few days before departure. The document in your inbox is a snapshot; the reservation is the live record.