← Plugin catalog
Travel

Airside Labs Aviation Tools

Airside Labs v1.3.0

Aviation facts and use cases

Create a free account to save this plugin.

From the developer

Not specified in the available declarations: capabilities, limitations, pricing & account requirements.

Onboarding example

Which airline used the designator BA on 1 January 1990, and what does the answer say about reused codes?
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 21, 2026.

View package source →

Description

From the marketplace listing

Aviation reference tools for analysts, researchers and product teams, with the source behind every answer. Resolve airports, airlines, aircraft types, registrations and flight identifiers with confidence, historical validity and per-field provenance, and check a set of identifiers against each other on a date. Look up what is true of an airport from the document that states it: network integration level as of a date, operator and ownership, operations status, nonstop connectivity and ACI passenger size band, plus the runways an aerodrome publishes in its state AIP with dimensions and declared distances per AIRAC cycle. See the scheduled capacity flown nonstop between two airports and the aircraft types that serve an airport, by carrier and type with seats and load factor, from BTS T-100. Ask which airframes have been heard operating a flight, or which flights an airframe has operated, from Airside Labs' own receiver and FAA flight plans. Explore a catalogue of 6,700+ aviation AI use cases by organisation and role, the data each needs and how fresh, its message lineage, where it sits in an operational workflow, an EASA AI-level and hazard screen, and real worked days with every event traced to its raw record. Twenty-nine tools in six groups; three work without an account. Reference, research and past observation only: not live operational, flight-status, booking or safety-control information. Users can also submit product feedback for human review and see what happened to it.

Language: English · Automatically detected from descriptions.

What changed

· 5 observations

Capabilities & instructions

Skill instructions changed from “regulator or a role inside one, what data it would need, or how a use case sits against EASA's AI framework. ## Steps 1. **Start with the landscape.** Call...” to “ground handler, regulator or a role inside one, what data it would need, how a use case sits against EASA's AI...

View comparison →
Capabilities & instructions

Skill instructions changed from “**Cite.** Every field in `best` has an entry in `provenance` with a source id and retrieval date. Quote the source when the answer will be relied on. ##...” to “**Go from identity to observation when the question is which aircraft.** `flight_airframes` says which airframes have been...

View comparison →
Capabilities & instructions

Is template instance added: “false”. Airside-aviation updated; open the comparison for details. App-6a99bd594da4819190de08daa2368989 updated; open the comparison for details. Full description changed from “teams. Resolve airports, airlines, aircraft types, registrations and flight identifiers with confidence,...

View comparison →
Capabilities & instructions

Is template instance added: “false”. Airside-aviation updated; open the comparison for details. App-6a99bd594da4819190de08daa2368989 updated; open the comparison for details. Full description changed from “teams. Resolve airports, airlines, aircraft types, registrations and flight identifiers with confidence,...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Files & skills

File archives

Plugin package8 files · 19.2 KBBrowse files →
Skill instructions
aviation-airport-facts4.13 KB

View saved version →

---
name: aviation-airport-facts
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.
---

# Airport and route facts: look up, cite, keep the scope

Use this workflow when a question asks what is true of a named airport, a city pair or an
airframe: who runs it, how it is integrated with the network, what runways it publishes, how
much capacity is flown on a route and with what, or which tails have operated a flight.

## Steps

1. **Resolve the airport first** with `resolve_airport` (pass `as_of` for a past date) and
   carry the ICAO code forward. The facts and runway tools take an airport identifier; the
   traffic tools take an ICAO code.
2. **Pick the tool that holds the fact.**
   - `airport_network_integration` for the EUROCONTROL Network Manager or FAA TFDM level, as of
     a date, citing the notice; `airport_operator` for operator and owner; 
     `airport_operations_status` for whether the airport is open for ordinary engagement;
     `airport_connectivity` for nonstop destinations; `airport_size_band` for the ACI passenger
     band with the figure and year.
   - `airport_runways` for what the state AIP publishes: designators, dimensions, surface,
     bearings, thresholds, approach slope indicators and the declared distances per direction,
     stamped with the AIRAC cycle. Coverage is the states whose exports permit reuse; a
     `not_covered` answer is the answer.
   - `route_capacity` for scheduled nonstop capacity between two airports from BTS T-100:
     departures, seats, passengers and load factor, by carrier and aircraft type. The pair is
     directional; ask both ways for a round trip. `airport_fleet_mix` for which types fly from
     or into an airport, how often and with how many seats.
   - `flight_airframes` for which airframes have been heard operating a flight, and
     `airframe_flights` for which flights an airframe has been heard or filed operating. Both
     are observation from Airside Labs' own receiver and FAA flight plans, within their
     footprint and window.
3. **Read the scope fields before the value.** `declared_distances` are full length and
   `from_intersections` are reduced; quote the one that matches the departure. A traffic
   answer names its window in months; a `not_heard` observation means not observed, not
   not flown.
4. **Cite.** Every field carries a `provenance` entry naming the document, dataset or
   instrument and the date. Quote it when the answer will be relied on, and give the AIRAC
   cycle or data window with any figure.

## Output requirements

- Name the airport by its ICAO and IATA codes and the date or cycle the answer applies to.
- Give the source for each fact in the same sentence as the fact.
- For capacity and fleet-mix figures, state the window, the direction and that the data is
  scheduled passenger service from BTS T-100, which covers US-reported segments.
- Say plainly when a tool answered `not_covered`, `unresolved` or `not_heard`.

## Do not

- Present an observed airframe as the aircraft that will operate a future flight; airlines
  swap tails without notice.
- Quote a load factor or seat count as live or as a forecast; the data is a monthly census.
- Use `airport_runways` for current operational status, closures or NOTAMs; it is the
  published AIP, not live state.
- Read connectivity, size band or runway data as a judgement about safety or capacity
  headroom.

## Example

User: "How much capacity flies Seattle to London Heathrow, on what aircraft, and what runways
does Heathrow publish?"

1. `resolve_airport` for SEA and LHR; carry KSEA and EGLL.
2. `route_capacity` with origin KSEA and dest EGLL: report the window, departures, seats,
   load factor, and the carrier and type breakdown.
3. `airport_runways` with EGLL: if

Preview of the first 4,000 characters. Read full instructions →

aviation-identity3.9 KB

View saved version →

---
name: aviation-identity
description: Resolve and cross-check aviation identifiers (airports, airlines, aircraft types, registrations, flight designators) with the Airside Labs Aviation Tools, on the right date, and report confidence and sources honestly.
---

# Aviation identity: resolve, date, cross-check

Use this workflow whenever a question names an airport, airline, aircraft type, registration or
flight number and the answer depends on which entity that identifier means.

## Steps

1. **Fix the date first.** If the question is about the past, pass `as_of` (YYYY-MM-DD) on every
   call. Airport codes move (ATH, HKG) and airline two-letter designators are reused (SN was
   Sabena, then Brussels Airlines). Without a date the tools answer for today, which is silently
   wrong for historical data.
2. **Resolve each identifier** with the matching tool: `resolve_airport`, `resolve_airline`,
   `resolve_aircraft_type`, `resolve_registration`, `parse_flight_identifier`. Prefer ICAO
   identifiers (four-letter airports, three-letter airlines) when carrying a result forward; they
   are not recycled the way IATA codes are.
3. **Read `status` and `confidence` before the value.** `resolved` at 1.0 is a unique match.
   0.7 to 0.99 came through an alias or a historical record; say so. 0.4 to 0.69 means
   `alternates` is populated: ask the user which one rather than choosing. `ambiguous` with a
   `country_hint` available: call again with the hint. `unresolved` is a real answer, not an
   error; do not invent one.
4. **Cross-check** when identifiers come from more than one source (a registration from a
   movement message and an address from a surveillance track, a flight number and an airline):
   call `validate_identifiers` with all of them and the date. `contradicted` means at least one
   check failed; never average it away. `consistent_where_checkable` with
   `unverifiable_count` above zero is partial coverage, not a pass: say which checks were silent.
5. **Go from identity to observation when the question is which aircraft.** `flight_airframes`
   says which airframes have been heard operating a flight (the tail decides the cabin and
   seat map, not the type); `airframe_flights` is the inverse for a registration or Mode-S
   address. Both are observation from Airside Labs' own receiver and FAA flight plans within
   their footprint and window: `not_heard` means not observed, not that the flight does not
   exist. A resolved aircraft type carries a `capacity` block (certified maximum, typical
   seating band, range, MTOW) for sizing questions.
6. **Cite.** Every field in `best` has an entry in `provenance` with a source id and retrieval
   date. Quote the source when the answer will be relied on.

## Output requirements

- State the date the answer applies to.
- Give the resolved entity with both code systems where the tool returns them.
- Name the confidence band in words (exact match, via alias, one of several candidates).
- If anything was unresolved, ambiguous or unverifiable, say so in the first sentence, not the last.

## Do not

- Use these tools for live status, schedules or slots; they answer identity questions and
  report past observations only.
- Present an observed airframe as the one that will fly next; airlines swap tails without
  notice, and the answer's confidence describes the observation.
- Present an unresolved result as a hint that the thing does not exist; coverage is not global.
- Drop the date from a follow-up question because the first call had one.

## Example

User: "Which airline was SN in 1995, and is BA117 a British Airways flight?"

1. `resolve_airline` with identifier `SN`, `as_of` `1995-06-01`: read `status`; if `ambiguous`,
   report the best candidate and the alternate with the tool's reason.
2. `validate_identifiers` with airline `BA`, flight `BA117`, `as_of` today: report the verdict
   and the checks.
3. Answer with the date, the entities, the confidence in words, and the sources.
aviation-use-cases3.77 KB

View saved version →

---
name: aviation-use-cases
description: Find and evidence AI use cases for an aviation organisation or role with the Airside Labs Aviation Tools, including the data each needs and the EASA AI-level screen, without overstating what the catalogue shows.
---

# Aviation AI use cases: landscape, search, fetch, screen

Use this workflow when someone asks what AI could do for an airline, airport, ANSP, MRO,
ground handler, regulator or a role inside one, what data it would need, how a use case sits
against EASA's AI framework, or for a real worked example behind it.

## Steps

1. **Start with the landscape.** Call `use_case_landscape` first, grouped by `org_type`, then
   narrow with `org_type` and `group_by=role` or `sector`. This tells you what the catalogue
   covers and the exact spellings the filters accept. Counts describe the catalogue, not the
   industry; never present a count as market evidence.
2. **Search with operational nouns.** `search_use_cases` works best on the things people do and
   the systems they touch (turnaround, stand allocation, NOTAM triage, engine health), not on
   abstractions. Take the top handful, not the whole list.
3. **Fetch the few records the argument needs** with `get_use_case`. Each record carries the
   role, the organisation type, every data requirement with its update cadence, the EASA screen
   where assessed, and nearest neighbours. Three well-chosen records beat thirty summaries.
4. **Go sideways when asked for alternatives:** `similar_use_cases` for the neighbours of one
   record; `data_requirements` for a role's or organisation type's aggregate data profile;
   `trace_data_lineage` to say where a data requirement's knowledge comes from;
   `trace_workflow` to place a use case in an operational sequence, with the steps before and
   after it and what hands off at each step.
5. **Screen with the framework, page-cited.** `easa_ai_framework` returns the AI-level, hazard
   class and technique-ceiling tables from the public EASA document with page references. The
   level and hazard on a use case are a title-level screen with a confidence, not a certification
   finding; say so.
6. **Ground the argument in real days when it needs one.** `get_use_case` records may carry
   `data_stories`: dated, sourced findings measured on Airside Labs' own receiver and approved
   public feeds. `scenarios` lists whole real days (one place, one UTC window, a timeline whose
   every event names its raw record) and `get_scenario` returns one with its lenses, each a use
   case's cut of the day with an evidence table and an implication. Quote a story or a scenario
   with its source and window and copy its `not_to_be_read_as`; never as live data or as a rate.
7. **File what you could not find.** If the user needed something the catalogue lacks, call
   `report_unmet_need` once with what was asked and what came back. If they have a correction or
   an addition, `submit_suggestion`. Both are read by a person; `feedback_status` says what
   happened later.

## Output requirements

- Name the organisation type and role the answer is scoped to.
- For each use case cited, give its ID, the data it needs with cadence, and the EASA screen if
  present, with the confidence stated.
- Separate what the catalogue records from what you infer.
- Carry the provenance note: the catalogue is Airside Labs' proprietary corpus for use inside
  the user's analysis, not for redistribution as a dataset; the EASA tables are public text that
  may be quoted with their page reference.

## Do not

- Quote landscape counts as adoption rates or market size.
- Describe a use case as certified, approved or compliant on the strength of the screen.
- Fetch dozens of full records when the question needs three.
- Extend a scenario past its window or read one airline's behaviour on one day as its policy.
Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Airside Labs

Package observed Nov 21, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 22, 2026 · 18:00 UTC
Latest observed change
Oct 24, 2026 · 13:07 UTC
Collection status
Collected

plugin_asdk_app_6a99bd594da4819190de08daa2368989

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.