airframe_flights

com.airsidelabs/aviation-tools · Verify this server

Which flights has this airframe been heard or filed operating, how often and when -- the inverse of flight_airframes, from Airside Labs' own ADS-B receiver and the FAA flight-plan feed? Accepts a registration in any common form (G-XWBA, N101DU, PH-BHA) or a Mode-S address (406a3d). A registration is resolved first, so `as_of` matters for a re-issued mark: the answer names the airframe it resolved to and the Mode-S address(es) it looked up. Returns each Flight ID the airframe was heard broadcasting within the receiver's footprint, or was filed under in FAA flight plans, with sightings (receiver poll cycles in view), distinct days seen, first and last seen, and which instrument observed it. `most_seen` and `most_recent` name the services it is usually on; `flight_count` how many distinct Flight IDs it carried in the window. Why this matters: movement history for a tail. A fleet-watching, lessor or MRO agent that has resolved a registration wants to know what it has been doing; this answer comes from what the receiver heard and what was filed, within the footprint below, not from a schedule. Coverage is the station's footprint (about 180 nm, taking in Heathrow and Gatwick traffic and the westbound Heathrow departure flow) plus departures filed from JFK, Newark and Seattle. `not_heard` means the airframe was not observed in the window and says nothing about whether it flew. A Flight ID identifies the service, not the route or the position: this is not a track log and never a current location. Do NOT use it to assert where an aircraft is or will be; say what it has been heard operating.