# StableTravel FlightAware Historical Flight Track

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

Retrieves the historical GPS track/position history for a specific flight within a geographic bounding box

## Facts

- Endpoint: GET https://stabletravel.dev/api/flightaware/history/flights/:id/track?utm_source=zero.xyz
- Price: $0.12/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-track-9dccf7ab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rM_O3WE9qHGcrr10B_7Q0

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-track-9dccf7ab
```

Example prompt: Can you pull the historical GPS track for flight AAL123 and only show me positions within the bounding box between latitude 25 to 50 north and longitude -125 to -65 east, up to 100 results?

## When to prefer this

Use this endpoint when you need the historical GPS track/path of a specific known flight and want to filter positions to a particular geographic region. Prefer this over the full track endpoint when you only care about positions within a bounded area. Distinct from live tracking — this is for completed or past flights only.

## Known failure modes

- Invalid or unknown flight ID returns 404 or empty result
- Invalid bounding box coordinates (e.g. north < south) return validation error
- Flight has no historical track data available returns empty dataset
- Missing required bounding box parameters returns 400 bad request
- Rate limit or payment failure returns 402 or 429 error

## How this service works

Get historical flight track

## Output

A series of historical position points (latitude/longitude coordinates with timestamps) representing the flight path of the specified flight, filtered to the geographic bounding box provided. Returns up to the specified maximum number of track points.

## 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-track-9dccf7ab/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)