airport_network_integration

shallow

com.airsidelabs/aviation-tools · Verify this server

What level of network integration does this airport have with the EUROCONTROL Network Manager, or with the FAA's TFDM programme, as of a date? Answers with one value: `ani` (Advanced Network Integrated: A-CDM with the higher level of integration), `acdm` (all DPI message types sent to the network, so a TOBT and TSAT stream exists), `adv_twr` (Advanced ATC TWR: E-DPI, C-DPI and A-DPI only, no TOBT or TSAT stream), `tfdm_a` or `tfdm_b` (FAA Terminal Flight Data Manager configurations), `standard` (removed from the Network Manager list by a notice), or `not_listed`. Each value carries its definition, the notice that establishes it, the date it has held since, and the history of changes across the notice chain. The source is the Network Manager's own Information Notice "Updated list of A-CDM, Advanced ATC TWR and ANI airports", parsed from each PDF in the chain from IN/25-001 (10 January 2025) to the current one. Pass `as_of` for a historical question: Berlin Brandenburg and Barcelona were `acdm` until 24 July 2025 and `ani` from 25 July; Edinburgh was removed on 4 December 2025 and back as `adv_twr` from 11 March 2026. Without a date you get today's list. Do NOT read `not_listed` as "no A-CDM": the list records integration with the network, and an airport can run a local A-CDM programme that never sends a DPI. Do NOT use this for the airport's live status, slots or runway data, and do not infer it from airport size or a vendor's press release; that inference is the confusion this tool exists to remove. The US part rests on the DOT OIG report of 17 July 2024, the only public site list; the FAA names no sites. `identifier` is an IATA or ICAO code, or an airport name; a name is resolved to its code first and the answer says so in its first note. Reading the answer: `status` is resolved, unresolved or not_covered. `confidence` is verified (named on an official list or read on the operator's own page), programmatic (derived from a public structured source and only as current as that source) or unknown. `provenance` names each source behind the answer; `source_url` and `as_of` are the citation. Unknown is never filled from the airport's country or size. `not_covered` means the airport is outside the public set rather than anything about the airport; report_unmet_need records which airport was wanted.

100.0/100

1 trials · measured 27 days ago

airport_network_integration scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.airsidelabs/aviation-tools, measured 11 Sept 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
gated
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-09-11100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: airport_network_integration
[![Vouch score](https://vouch.tools/api/tools/6cfa379d-aa80-4c6e-bc47-70225b8dc30b/badge.svg)](https://vouch.tools/tools/6cfa379d-aa80-4c6e-bc47-70225b8dc30b)
airport_network_integration — Vouch