What Aircraft Is Operating My Flight? Type and Tail Number, Explained
Two different things answer 'what aircraft is this flight': the aircraft type (a Boeing 777, an Airbus A320) and the registration, or tail number, of the exact airframe. Here is what each means, when the API can tell you, and how to use them.
· 5 min read"What aircraft is operating my flight?" is two questions wearing one coat. One asks for the type — a Boeing 777-300ER, an Airbus A320 — which tells you the size, cabin and capability of the flight. The other asks for the registration, or tail number, of the specific airframe flying it today — a value like A6-EOA or N270QS that identifies one physical aircraft out of a fleet. They are populated at different stages and used for different jobs. This guide explains both, and how to read them from the API.
Type versus registration
The aircraft type is a property of the flight: a given flight number tends to be flown by the same family of aircraft day after day, because it is sized to the route. Knowing the type tells you roughly how many passengers to expect, whether it is a wide-body or narrow-body, and what class of service is likely. It is stable and known well in advance.
The registration is a property of the airframe: it names the exact tail flying the route on this date. It is only firmly known once a specific aircraft is assigned and airborne, because airlines swap airframes between routes routinely. The registration is what a spotter, an insurer, or a maintenance system cares about; the type is what a booking, a capacity plan, or a greeter cares about.
How the API answers
Every flight lookup returns an aircraft object. It carries the type as a short code and a human name — for example 388 and Airbus A380-800, or 77W and Boeing 777-300ER — and, when the flight is airborne and the airframe has been identified, a registration (the tail number). For a future or not-yet-flown flight, the type is provided from the aircraft that typically operates that flight, drawn from FlightNerve's accumulated observations, while the registration is left empty because the physical tail for a future date genuinely is not decided yet.
That split is deliberate and worth designing around: expect the type to be present whenever the flight is known, and expect the registration only for a flight that is happening now or has happened. A booking flow should read the type; an operations screen tracking a live arrival can read both.
Why the type matters operationally
- Capacity and load. A wide-body arrival means more passengers through the hall, more bags on the belt, and a different transfer plan than a regional jet.
- Ground handling. The type hints at stand size, whether a jet bridge or stairs, and how long turnaround and bag delivery tend to take.
- Cabin expectation. For a premium transfer or a duty-of-care check, knowing it is a long-haul wide-body versus a short-haul narrow-body sets the right expectation before the passenger lands.
- Equipment changes. When an airline swaps the usual type for a different one, that is a signal worth surfacing — it can change seat counts and timings.
Reading the tail number
The registration identifies one airframe. It is most useful when the flight is live: it lets you confirm the exact aircraft, follow it across a rotation, or match it against a record. Because airlines assign tails late and swap them freely, treat an empty registration on a future flight as normal rather than missing data — the type is the dependable field ahead of time, and the tail becomes available as the flight approaches and gets in the air.
Private and business aviation
For scheduled airlines, the type is the natural identifier and the tail is a bonus. For private and business aviation the emphasis flips: a private flight number is often reused across many unrelated trips, so the tail number is the meaningful identity of the aircraft. If you work with private movements — a meet-and-greet for a chartered arrival, for instance — anchor on the airport and the arrival window rather than treating a private flight number as a fixed route, and use the type and registration to confirm the aircraft on the day. Coverage of private movements is strongest over regions with dense live-signal reception and lighter elsewhere, so plan for the tail to be confirmed close to arrival.
Frequently asked questions
Why is the aircraft type present but the tail number empty? Because the type is known in advance from the aircraft that usually flies the route, while the specific airframe for a future date is not assigned yet. The tail fills in as the flight approaches and is airborne.
What do the code and name mean? The code is a short aircraft type code (for example 359 or B738) and the name is its full type name (Airbus A350-900, Boeing 737-800). Use the name for display and the code for matching.
Can the type change for a flight? Yes — airlines substitute aircraft. The value reflects the aircraft that typically operates the flight, so an occasional swap on the day is possible; for the live truth of an airborne flight, read the registration.
My flight shows no aircraft at all. Why? That happens for a brand-new airline or route we have not yet observed operating, where there is no established aircraft to report. As the flight accumulates a history, the type appears.
The aircraft type comes back on every flight lookup, no extra call. Get a free API key and see the documentation for the full response.