AviationStack Flight & Airport API

AviationStack Flight & Airport API is the agricultural products services catalog's movement-layer record: nine documented endpoint families spanning live flight tracking, historical flights, airline routes and six reference shelves - airports, airlines, airplanes, cities, countries and aviation taxes. One response returns one nested object per flight leg, with departure, arrival, aircraft, airline and status blocks carried inline rather than scattered across join tables.

The publisher cites reach of more than 10,000 airports, 13,000 airlines, 19,000 airframes, 9,000 cities, 250 countries and 500 aviation taxes - reference furniture deep enough to resolve nearly any code a logistics, travel or supply-chain table throws at it. Where most catalogs stop at traffic statistics, this record carries the leg itself: gates, terminals, four distinct clocks (scheduled, estimated, actual, runway) and a live position block with latitude, longitude, altitude, heading and both speed components. Datadory scores it 7/10 against a catalog mean of 7.81.

Two rows assembled from the documented field examples captured during the August 2026 research pass - one complete flight leg and one route pair, exactly as the fields arrive:

# Flight leg - American Airlines 1004, documented example values
departure : Los Angeles International (LAX / KLAX)   terminal B   gate B27
timezone  : America/Los_Angeles
sched     : 2019-12-11 23:30:00     estimated: 2019-12-11 23:30:00
actual    : 2019-12-11 23:34:00     runway   : 2019-12-11 23:42:00
arrival   : (JFK / KJFK)
status    : landed                  status_delay: 0
airline   : American Airlines       iata: AA   icao: AAL   flight: 1004
aircraft  : reg N160AN              icao24: A0F1BB
position  : 34.1234, -118.4567      alt: 32000   hdg: 65 deg
speed     : horizontal 480          vertical: 2.56
collected : 1576116000 (unix)

# Route row - code-indexed pair from the routes family
origin_code      : AA
destination_code : AA

Read the leg left to right and its discipline shows up. Four clocks run in sequence - scheduled 23:30, estimated 23:30, actual 23:34, runway 23:42 - so the journey decomposes into waiting, climb-out and an eight-minute taxi without any derived-column work on your side. The status pair closes the story: landed, zero delay. The position block holds still a moment mid-flight, altitude and both speed components attached, and the unix collection stamp dates the observation.

The route row is the wry one: the routes family documents its endpoints as bare codes, and the published example carries AA on both sides, which reads as airline-keyed rather than airport-keyed. Treat the pair as the carrier's own indexing and settle its exact scope when you sample.

Thirty-three documented fields carry the record, every definition checked against the publisher's own field listing during the August 2026 research pass rather than inferred. Twenty-seven are exemplified directly on the published flight-leg example. The departure block alone resolves five ways - name, IATA, ICAO, terminal, gate - with an IANA timezone beside it so local timestamps stay local. The four clocks follow. The arrival side carries its own IATA and ICAO pair. The status pair states where the leg stands and by how many minutes it missed its slot.

Identity travels three ways: the airline resolves to name, IATA and ICAO codes plus flight number; the airframe carries both its registration tail and its ICAO24 transponder hex, the stable identifier that stitches legs together across years. Six live-position fields round out the airborne picture, and a unix collection timestamp dates every row.

The full dictionary sits in the table below - nothing guessed, nothing padded.

Four arrival-side fields - the destination airport name and the three arrival timestamps - are defined in the dictionary above but carried no worked example in the research capture, so their observed values land with your first delivery. Beyond the flight leg, the reference families document more surface than one page should print: city attributes behind the airport shelf, country detail, airframe manufacture data and the aviation-tax records all ship under additional fields on request, along with the pagination envelope that wraps every list response. Name what your models need when you request the sample.

Geography - global, per the publisher's own counts: more than 10,000 airports, 13,000 airlines and 250 countries, with city, country and tax shelves layered underneath. Reference depth is the quiet strength here - a leg into a secondary airport still resolves to a named, coded place.

Temporal - live positions now, plus a historical-flights family for legs already flown, so a lane can be studied after it lands rather than only while it moves. Retention depth for the historical family is not published; it gets measured and reported with your sample rather than asserted here.

Granularity - one nested record per flight leg with departure, arrival, aircraft, airline and status blocks inline, plus one row per entity on each reference shelf and one code pair per routes-family row. No pre-aggregated roll-ups anywhere: aggregation stays yours, which is another way of saying the joins stay clean.

API, files, or your warehouse. Daily, weekly, or hourly.

Your cadence is your call regardless of how the underlying record moves - an hourly load keeps a status dashboard honest through the day, a daily file suits punctuality studies, and a monthly pull serves annual network research that never looks at yesterday. Name the carriers, airports, lanes or flight numbers when you request the sample and it arrives shaped to that scope as CSV or JSON, with the complete field dictionary attached. Nested leg structures flatten onto stable keys, so one leg stays one row however wide the delivery.

• Punctuality and delay analysis - the four-clock structure splits each journey into scheduled, estimated, actual and runway moments, giving delay studies a typed input instead of hand-copied notes.
• App and dashboard builders - one nested object per leg makes status-by-flight a lookup against an identifier, the fastest path from idea to shipping feature in this slice.
• Perishables and air-cargo exposure - for an agricultural products and services workflow, cut flowers, fresh fruit and temperature-sensitive produce move by air; lane-level legs tie cold-chain risk to physical flights rather than lagged statistics.
• Route network mapping - the routes family walks carrier pairs, making network comparisons a set difference rather than a scraping project avoided altogether: a mapping exercise, not a collection one.
• Master-data resolution - airports, airlines, airplanes, cities, countries and taxes turn bare codes anywhere in your stack into named, located entities.
• Citation-grade sourcing - journalists and academics anchor a claim to a dated, attributable leg record instead of recollection.

Developers and data-product builders get the shortest path to a live feature: one identifier, one nested object, every attribute inline - see developers builders use cases. Competitive intelligence and product teams read rivals' networks and punctuality as countable signals - see competitive intel product teams use cases. Investors and quant researchers get carrier-level movement detail ahead of official releases - see investors quants use cases. Market researchers and consultants resolve any aviation code set into client-ready named geography - see market researchers use cases. It is the pool's only record built for live queries at leg level, which is why the airport services ranking places it beside archives ten times its size.