{"id":42898,"plugin_id":"plugin_asdk_app_6a99bd594da4819190de08daa2368989","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:07:43.692Z","digest":"6155117ef554df65b8a71f8f0e7609f47e1b1bc5409c3d4d4b59c4097011dba5","against":null,"payload":{"description":"Answer what is true of an airport or a route with the Airside Labs Aviation Tools (network integration, operator, status, connectivity, size band, published runways, scheduled capacity and fleet mix, observed airframes), cited to the document or dataset that states it.","included_files":[],"name":"aviation-airport-facts","skill_md_contents":"---\nname: aviation-airport-facts\ndescription: Answer what is true of an airport or a route with the Airside Labs Aviation Tools (network integration, operator, status, connectivity, size band, published runways, scheduled capacity and fleet mix, observed airframes), cited to the document or dataset that states it.\n---\n\n# Airport and route facts: look up, cite, keep the scope\n\nUse this workflow when a question asks what is true of a named airport, a city pair or an\nairframe: who runs it, how it is integrated with the network, what runways it publishes, how\nmuch capacity is flown on a route and with what, or which tails have operated a flight.\n\n## Steps\n\n1. **Resolve the airport first** with `resolve_airport` (pass `as_of` for a past date) and\n   carry the ICAO code forward. The facts and runway tools take an airport identifier; the\n   traffic tools take an ICAO code.\n2. **Pick the tool that holds the fact.**\n   - `airport_network_integration` for the EUROCONTROL Network Manager or FAA TFDM level, as of\n     a date, citing the notice; `airport_operator` for operator and owner; \n     `airport_operations_status` for whether the airport is open for ordinary engagement;\n     `airport_connectivity` for nonstop destinations; `airport_size_band` for the ACI passenger\n     band with the figure and year.\n   - `airport_runways` for what the state AIP publishes: designators, dimensions, surface,\n     bearings, thresholds, approach slope indicators and the declared distances per direction,\n     stamped with the AIRAC cycle. Coverage is the states whose exports permit reuse; a\n     `not_covered` answer is the answer.\n   - `route_capacity` for scheduled nonstop capacity between two airports from BTS T-100:\n     departures, seats, passengers and load factor, by carrier and aircraft type. The pair is\n     directional; ask both ways for a round trip. `airport_fleet_mix` for which types fly from\n     or into an airport, how often and with how many seats.\n   - `flight_airframes` for which airframes have been heard operating a flight, and\n     `airframe_flights` for which flights an airframe has been heard or filed operating. Both\n     are observation from Airside Labs' own receiver and FAA flight plans, within their\n     footprint and window.\n3. **Read the scope fields before the value.** `declared_distances` are full length and\n   `from_intersections` are reduced; quote the one that matches the departure. A traffic\n   answer names its window in months; a `not_heard` observation means not observed, not\n   not flown.\n4. **Cite.** Every field carries a `provenance` entry naming the document, dataset or\n   instrument and the date. Quote it when the answer will be relied on, and give the AIRAC\n   cycle or data window with any figure.\n\n## Output requirements\n\n- Name the airport by its ICAO and IATA codes and the date or cycle the answer applies to.\n- Give the source for each fact in the same sentence as the fact.\n- For capacity and fleet-mix figures, state the window, the direction and that the data is\n  scheduled passenger service from BTS T-100, which covers US-reported segments.\n- Say plainly when a tool answered `not_covered`, `unresolved` or `not_heard`.\n\n## Do not\n\n- Present an observed airframe as the aircraft that will operate a future flight; airlines\n  swap tails without notice.\n- Quote a load factor or seat count as live or as a forecast; the data is a monthly census.\n- Use `airport_runways` for current operational status, closures or NOTAMs; it is the\n  published AIP, not live state.\n- Read connectivity, size band or runway data as a judgement about safety or capacity\n  headroom.\n\n## Example\n\nUser: \"How much capacity flies Seattle to London Heathrow, on what aircraft, and what runways\ndoes Heathrow publish?\"\n\n1. `resolve_airport` for SEA and LHR; carry KSEA and EGLL.\n2. `route_capacity` with origin KSEA and dest EGLL: report the window, departures, seats,\n   load factor, and the carrier and type breakdown.\n3. `airport_runways` with EGLL: if covered, list the runways with their full-length declared\n   distances and the AIRAC cycle; if `not_covered`, say so and name the state coverage.\n4. Answer with the sources and the window in the same sentences as the figures.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}