airport_runways
shallowcom.airsidelabs/aviation-tools · Verify this server
What runways does this aerodrome publish in its state AIP, with what dimensions, surface, bearings, thresholds and declared distances, and for which AIRAC cycle? Returns every runway the state's export lists for the aerodrome: designator, length and width, surface and PCN, the runway strip, and per direction the threshold coordinates, true and magnetic bearing, the approach slope indicator (PAPI or VASIS type, slope and MEHT) and the four declared distances TORA, TODA, ASDA and LDA. Every length is `{"m": ...}`; where the publisher states feet it is `{"m": ..., "published": {"value": ..., "uom": "FT"}}` and the published figure is the one to quote. `as_of` is the cycle the figures are true for and `provenance` names the export. Read `declared_distances` and `from_intersections` as two different things. The top-level figures are the FULL-LENGTH declared distances. `from_intersections` lists the reduced distances available to a departure that starts at a taxiway intersection: Paris CDG 09R publishes a TORA of 4200 m at full length and 2962 m from D6, and both are true. Quoting an intersection figure as "the" TORA understates the runway; quoting the full length for an intersection departure overstates it. LDA is measured from a different datum and may be shorter than TORA at full length while longer from an intersection; that is the publisher's figure, not an error. `remarks` carry the publisher's own qualifications (PPR, reduced distances) and must travel with the number. `identifier` is an ICAO location indicator, an IATA code or an aerodrome name; a name or IATA code is resolved to its ICAO code first and the answer says so in its first note. Coverage is by state export: France and its overseas territories (SIA AIXM export, Licence Ouverte, every aerodrome) and the United States (FAA NASR 28-day airport files, public domain, the aerodromes with an ICAO location indicator). FAA runway-end coordinates are the displaced threshold where there is one, else the physical end, and the FAA publishes no intersection-qualified distances. `not_covered` means the aerodrome is outside the exports held, not that it has no runways; `coverage` in that answer says what is held, and report_unmet_need records which aerodrome was wanted. An aerodrome that resolves with zero runways is a heliport, a water aerodrome or a publisher gap, and the note says which. Do NOT use this for the runway in use, closures, NOTAMs, work in progress, or anything that changes inside a cycle: it is the published infrastructure for a cycle, accurate to that publication and not live. Do not convert units silently: the elevation and MEHT carry a `uom`, and a length stated in feet carries the published figure beside the metre conversion, because the exports mix feet and metres.
1 trials · measured 1 day ago
airport_runways scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.airsidelabs/aviation-tools, measured 6 Oct 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- gated
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-10-06 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 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.
[](https://vouch.tools/tools/2bd69e44-e0d7-4bef-a9a9-44c59398222b)