Aviationstack pitches live airport data for travel apps

Aviationstack says travel apps can replace hard-coded airport tables with live API data that includes airport codes, coordinates and time zones. The move is aimed at avoiding stale records, wrong local times and outdated airport entries as aviation networks change.

Why it matters: - Travel apps that rely on hand-kept airport tables risk stale codes, missing new airports and incorrect local times. - Aviationstack says live airport data can help booking tools and flight apps stay aligned with current aviation records. - The pitch matters for AI-written code too, since assistants can otherwise generate airport lists from training data that look complete but drift over time.

What happened: - Aviationstack said its API provides updated airport codes, coordinates and time zones for travel platforms, booking systems and flight applications. - The company said its airport catalog covers more than 10,000 airports. - The catalog includes the airport name, IATA and ICAO codes, city code, country, latitude, longitude and phone number for each record. - The API also includes the airport time zone, which date libraries can turn into local time for any date. - Companion catalogs cover more than 13,000 airlines, 9,000 cities, 250 countries and aircraft types.

The details: - Aviationstack said the catalogs are available on every plan, including Free. - Airport lookup on plans from Basic up accepts a search term, which can power type-ahead airport suggestions in booking forms. - Each request returns up to 100 airports below the Professional plan and up to 1,000 airports on Professional and above. - A full copy of the airport dataset takes at least 100 requests on the smaller plans and at least 10 requests on the larger plans. - The free plan includes 100 requests per month for testing. - The Basic plan includes 10,000 requests, which is enough to fit a full airport copy. - A refreshed local copy can carry its own source and date while staying aligned with Aviationstack data.

Between the lines: - The core problem is not just missing data. It is data that becomes wrong as airports open, close or change names. - Berlin is a clear example: in 2020, flights moved to BER, and the older TXL and SXF codes went out of use. - Time zone handling is another weak point in static tables, because one offset per airport can be wrong for part of the year where daylight saving changes. - Aviationstack is positioning itself as infrastructure for both conventional app development and AI-assisted coding workflows.

What's next: - Developers can test Aviationstack on the free plan at Aviationstack. - APILayer said more MCP servers across its suite are coming. - Weatherstack can already use airport latitude and longitude to return local conditions, and IPstack already ships an MCP server for AI assistants to call directly.

The bottom line: - Aviationstack is betting that travel apps will prefer live aviation data over static airport tables to reduce maintenance and avoid outdated results.