What AeroDataBox is and who should use it
AeroDataBox covers the full breadth of commercial aviation data that a developer typically needs: real-time and historical flight status, airport FIDS (flight information display system) data, aircraft registrations, airport infrastructure details, delay statistics, and push-based flight alerts. All of this is exposed through a REST API returning JSON (default) or XML, plus a webhook mechanism for event-driven architectures.
The explicit target market is small and medium businesses, solo developers, students, and researchers — not airline operations centers. The pricing reflects that: the free tier is genuinely usable for prototyping, and even the highest self-serve plan tops out at $160/month. If you have ever tried to source aviation data from traditional providers, that context matters.
With 83 documented endpoints across six functional groups and more than 20,800 marketplace subscribers, AeroDataBox is one of the more comprehensive flight data APIs available through public API marketplaces.
Endpoint groups and what each covers
Flights API
This is the core of AeroDataBox. You can look up a flight by IATA/ICAO flight number, ATC callsign, aircraft registration, or 24-bit ICAO Mode-S address — a level of flexibility that accommodates both consumer-facing and operational use cases.
- Flight status (single day) returns current, future, or historical data for a specific flight on a specific or nearest date. An optional add-on includes the filed flight plan, though this is currently limited to mainland U.S. airspace. Real-time position is another optional extra.
- FIDS / Schedules gives you the full list of arrivals and departures at an airport, queryable by relative time window or an explicit local time range.
- Flight history & schedule (date range) extends status lookups across a span of dates rather than a single day.
- Flight departure dates answers the simpler question: on which days does a given flight actually operate?
- Search flight numbers by term supports autocomplete UX patterns.
Flight Alert API (webhooks)
Instead of polling for flight updates, you can POST a webhook subscription tied to a flight number or airport code. AeroDataBox will call your HTTP endpoint whenever the flight data changes. Webhook subscription management (create, list, get, delete) is on the free tier; refilling the webhook credit balance consumes Tier 1 quota. This makes the alert system accessible even on the BASIC plan, though sustained use will draw down credits.
Aircraft API
Lookups by tail number or Mode-S address return aircraft metadata, full registration history (useful for tracking re-registrations across jurisdictions), and — in beta — a photo sourced from Flickr under commercially permissible licenses. The airline fleet endpoint (also beta) returns all active aircraft for a given airline code.
Airport API
Beyond basic airport metadata (name, location, elevation, IATA/ICAO codes), this group includes runway details (threshold coordinates, dimensions, surface type, lighting, heading), proximity search by lat/lon radius, IP-geolocation-based nearest-airport lookup, and free-text search for autocomplete. The IP-based lookup is a practical shortcut for apps that want to surface relevant airports without asking users to type.
Statistical API
Three endpoints cover delay intelligence: current airport delays, historical delays by date or date range, and global delays across all covered airports. A fourth endpoint returns daily route statistics — how many flights operate between an airport and each destination. A fifth provides per-flight delay statistics broken down by departure/arrival airport, hour of day, and delay brackets including percentiles.
Miscellaneous and industry endpoints
The miscellaneous group is small but occasionally indispensable: local time at an airport (no timezone table maintenance required), solar times (sunrise, sunset, civil/nautical/astronomical dusk and dawn, golden hour, sun elevation and azimuth), great-circle distance between airports, and an ML-based realistic flight time estimate. The industry group provides access to FAA LADD (Limiting Aircraft Displayed) status, useful for U.S.-focused aviation compliance tools.
Understanding the pricing model
AeroDataBox uses two parallel counters: Requests (raw HTTP calls) and API Units (a weighted cost that varies by endpoint tier). Not all calls cost the same number of units — a Tier 3 endpoint consumes more units than a Tier 1 call. Consult the pricing page before designing your call patterns, because the unit cost per endpoint tier can significantly affect how far your monthly allocation stretches.
| Plan | Price/month | API Units/month | Requests/month | Rate limit |
|---|---|---|---|---|
| BASIC | $0 | 600 | 2,400 | 1 req/sec |
| PRO | $5.35 | 6,000 | 24,000 | 1 req/sec |
| ULTRA | $32 | 60,000 | 240,000 | 2 req/sec |
| MEGA | $160 | 600,000 | 2,400,000 | 3 req/sec |
Overage is only available on MEGA, at $0.0003 per additional API unit.
The BASIC plan's 600 API units is genuinely small. If you mix in Tier 2 and Tier 3 endpoint calls, those units can evaporate well before you reach the 2,400-request ceiling. BASIC is best suited for proof-of-concept work or very low-frequency production use cases (think: a personal project that checks a handful of flight statuses per day). PRO at $5.35/month is a reasonable starting point for a hobby app with real users. ULTRA is flagged as the recommended tier and makes sense for small commercial products. MEGA is the right choice for data-intensive pipelines, with overage as a safety net.
Practical use cases
- Flight tracker apps: Combine FIDS, real-time flight status with live position, and the webhook alert system to build a complete flight-monitoring experience without polling loops.
- Travel apps and booking tools: Airport autocomplete, nearest-airport-by-IP, local time, and solar times round out UX features that would otherwise require separate geocoding and timezone APIs.
- Research and analysis: Historical flight data, delay statistics, and route frequency data are directly useful for academic research, journalism, or business intelligence on airline operations.
- Operational tools: Aircraft registration history and FAA LADD status serve compliance and due-diligence workflows in aviation services.
- Autocomplete interfaces: Dedicated search endpoints for airport names and aircraft tail numbers are specifically designed for low-latency typeahead inputs.
Limitations and things to verify before integrating
Data coverage is not universal. AeroDataBox publishes a dedicated data coverage page that documents which airports and regions are supported for which services. Not every airport has live flight update feeds, and not every region has the same depth of historical data. Check coverage for your target airports before committing to an integration.
Flight plans are U.S.-only (for now). The filed flight plan feature on the flight status endpoint only covers mainland U.S. airspace. If your use case requires flight plans for other regions, this limitation is material.
Webhook balance is separate from your API quota. The Flight Alert API uses a distinct credit balance that must be refilled explicitly. Burning through that balance will stop alert delivery independently of your remaining API unit quota.
Rate limits are low on the entry tiers. One request per second on BASIC and PRO means any burst behavior — say, initializing a dashboard that fetches data for ten flights at once — needs to be serialized or will hit limits. Plan your request queuing accordingly.
Airline fleet and aircraft photos are in beta. Treat those endpoints as potentially unstable; they may change without the same notice that stable endpoints receive.
Scam alert. AeroDataBox explicitly warns about unauthorized APIs impersonating their service. Subscribe through their official marketplace listings and verify the source before integrating.
Getting started
AeroDataBox is available through major API marketplaces. The BASIC plan requires no payment information and provides enough quota to explore most endpoint groups meaningfully. The OpenAPI specification is the authoritative reference for request parameters and response schemas. A flight search portal lets you browse live data before writing a single line of code — a useful way to verify coverage for your target airports and routes. Subscribe to the newsletter for breaking change notifications, since aviation data APIs tend to evolve with regulatory and data-source changes.
