# StableTravel FlightAware Airport Historical Arrivals

> StableTravel FlightAware Airport Historical Arrivals 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-13).

Retrieve historical arrival flights at an airport within a specified geographic bounding box

## Facts

- Endpoint: GET https://stabletravel.dev/api/flightaware/history/airports/:id/flights/arrivals?utm_source=zero.xyz
- Price: $0.04/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-13
- 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-arrivals-771fb57e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sxNqQFFgP9F5WHFKcZ59J

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-arrivals-771fb57e
```

Example prompt: Pull the historical arrivals for the airport at coordinates roughly between 33.5–34.5°N and -118.5–-117.5°W, and give me up to 100 results.

## When to prefer this

Use this endpoint when you need historical (past) arrival flight data for a specific airport identified by a geographic bounding box. Prefer this over live tracking endpoints when analyzing past traffic patterns, researching historical operations, or auditing arrivals after the fact. Choose this over departure endpoints when inbound flights specifically are needed.

## Known failure modes

- Missing required bounding box parameters (north, south, east, west) returns a 400 error
- Invalid or out-of-range latitude/longitude values may return no results or an error
- Airport ID not found returns an empty result set or 404
- Exceeding max result limits may truncate or error
- Upstream FlightAware data unavailability causes 503 or timeout

## How this service works

Get historical arrivals at airport

## Output

A list of historical arrival flight records for the airport(s) within the specified bounding box, including flight identifiers, operator details, and arrival timestamps, up to the requested maximum number of results.

## 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-arrivals-771fb57e/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)