Look up the last flight for any aircraft by registration via FlightAware, pay-per-request at $0.40.
What it does
This endpoint returns the most recent flight record for a specific aircraft identified by its tail registration number (e.g., N12345). It is part of StableTravel's FlightAware history API suite, which proxies FlightAware AeroAPI data through a pay-per-request micropayment model. The response includes origin/destination airports (with ICAO/IATA codes, city, timezone), scheduled and actual gate/runway times, delays, aircraft type, route distance, filed altitude/airspeed, baggage claim, gate/terminal info, and flight status.
The endpoint costs $0.40 per request, settled via MPP (Tempo method on chain 4217) or x402 using USDC. No API keys or subscriptions are required — payment serves as authentication. The registration is passed as a path parameter (e.g., `/api/flightaware/history/aircraft/N12345/last-flight`). The endpoint accepts GET requests and returns a single flight object (not an array). This is one of the more expensive endpoints in the StableTravel suite, reflecting the underlying FlightAware AeroAPI cost for aircraft-level historical lookups.
StableTravel is operated by Merit Systems and provides a full OpenAPI 3.1 spec at `/openapi.json`. The MPP challenge was confirmed live, returning a 402 with a valid payment challenge.
Capabilities
Use cases
- —Determine where a specific aircraft last flew and when it landed
- —Verify aircraft utilization for fleet management or leasing due diligence
- —Check if a charter or private jet has recently been active
- —Feed aircraft movement data into logistics or scheduling systems
- —Audit aircraft operational history by registration number
Fit
Best for
- —Agents that need to look up the most recent flight of a specific aircraft by tail number
- —Fleet management tools tracking aircraft utilization
- —Aviation data pipelines requiring per-aircraft historical lookups
Not for
- —Bulk historical flight data retrieval across many aircraft (use operator/flights endpoint instead)
- —Real-time live flight tracking (use the /flightaware/flights/{ident} endpoints)
- —Price-sensitive use cases where $0.40 per lookup is too expensive
Quick start
npx agentcash fetch "https://stabletravel.dev/api/flightaware/history/aircraft/N12345/last-flight"Example
Response
{
"ident": "UAL123",
"origin": {
"city": "Chicago",
"code": "KORD",
"name": "Chicago O'Hare Intl",
"code_iata": "ORD",
"code_icao": "KORD"
},
"status": "Arrived",
"operator": "UAL",
"actual_in": "2025-07-10T16:45:00Z",
"actual_out": "2025-07-10T14:12:00Z",
"ident_iata": "UA123",
"ident_icao": "UAL123",
"destination": {
"city": "Los Angeles",
"code": "KLAX",
"name": "Los Angeles Intl",
"code_iata": "LAX",
"code_icao": "KLAX"
},
"fa_flight_id": "UAL123-1718000000-schedule-0001",
"registration": "N12345",
"aircraft_type": "B738",
"arrival_delay": 300,
"operator_iata": "UA",
"operator_icao": "UAL",
"scheduled_out": "2025-07-10T14:00:00Z",
"route_distance": 1745,
"departure_delay": 720
}Endpoint
Quality
Full OpenAPI 3.1 schema with detailed response types, clear pricing ($0.40/request), live MPP 402 challenge confirmed, and comprehensive documentation. Slightly below 0.9 because no real example response was captured from a paid call, and the response schema uses additionalProperties liberally.
Warnings
- —Example response is synthetic — no actual paid response was captured in the probe
- —This is one of the more expensive endpoints at $0.40 per call
Citations
- —Endpoint price is $0.40 per requesthttps://stabletravel.dev/openapi.json
- —Payment via USDC on Tempo (chain 4217) or x402, no API keys neededhttps://stabletravel.dev
- —MPP challenge confirmed live with 402 status and valid payment parametershttps://stabletravel.dev/api/flightaware/history/aircraft/:registration/last-flight
- —Operated by Merit Systemshttps://stabletravel.dev/docs
- —Response includes origin, destination, times, delays, aircraft type, route distance, and status fieldshttps://stabletravel.dev/openapi.json