# Airport Historical Departures

> Airport Historical Departures is a paid API for AI agents from StableTravel at stabletravel.dev, paid per call via MPP, $0.04/call, status unknown (last checked 2026-10-10).

Returns historical departure flights from an airport identified by bounding box coordinates via FlightAware data

## Facts

- Endpoint: GET https://stabletravel.dev/api/flightaware/history/airports/:id/flights/departures?utm_source=zero.xyz
- Price: $0.04/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Provider: StableTravel
- Docs: https://stabletravel.dev
- Website: https://stabletravel.dev
- Tags: amadeus, flightaware, flights, hotels, activities, transfers, travel, data, web
- Canonical page: https://www.zero.xyz/c/stabletravel-departures-696daa70
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_T5Brk8eQ7dUOuCR_S7SBO

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability stabletravel-departures-696daa70
```

Example prompt: Can you pull up the historical departure flights from the airport bounded by latitude 33.9 to 34.1 north and longitude -118.5 to -118.2 west using FlightAware — show me up to 100 results?

## When to prefer this

Use this endpoint when you need historical (past) departure data from a specific airport identified by geographic bounding box coordinates, especially when powered by FlightAware data quality. Prefer this over scheduled arrivals or real-time endpoints when analyzing past flight activity or auditing departure history.

## Known failure modes

- Missing required bounding box parameters (north, south, east, west) returns a 400 error
- Invalid coordinate values (out of range) may return no results or an error
- Airport ID not found returns empty or error response
- Exceeding max result limits may truncate data
- Network timeout if FlightAware upstream is slow

## How this service works

Get historical departures from airport

## Output

A list of historical departure flight records from the specified airport area, including flight details such as departure times, aircraft, operators, and destinations, sourced from FlightAware historical data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "north",
  "west",
  "south",
  "east"
 ],
 "properties": {
  "max": {
   "type": "number",
   "description": "Maximum number of results (default 50)"
  },
  "east": {
   "type": "number",
   "description": "Eastern longitude boundary"
  },
  "west": {
   "type": "number",
   "description": "Western longitude boundary"
  },
  "north": {
   "type": "number",
   "description": "Northern latitude boundary"
  },
  "south": {
   "type": "number",
   "description": "Southern latitude boundary"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stabletravel-departures-696daa70/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stabletravel.dev](https://www.zero.xyz/host/stabletravel.dev/llms.txt)