resolve_registration

shallow

com.airsidelabs/aviation-tools · Verify this server

Which airframe wore this registration on a given date? Accepts a tail number in any common form: VH-OQA, VHOQA, lowercase, padded with whitespace. Returns the aircraft with its country of registry, ICAO type designator, an embedded resolved aircraft type, operator, owner, serial number and Mode-S hex address. A registration is a slot rather than a permanent name: marks are surrendered and reissued. VP-BRZ was an Aeroflot A320 until 2017 and a different airframe entirely from 2019, with a different Mode-S address. Pass `as_of` for any historical question. Where the date falls between two holders the tool returns `unresolved`, reports the country from the nationality mark, and offers both airframes as alternates. When the tail is unknown but the nationality mark is recognised, the response carries a `partial` object with the country of registry at confidence around 0.5. That is a partial answer, not a resolution: the aircraft is still unidentified. Coverage is not global. An unresolved registration means this dataset does not hold it, NOT that the aircraft does not exist. Do NOT infer that an aircraft is fictitious from an unresolved result, and do NOT use this for airworthiness, lease status or current position. Reading `confidence`: 1.0 means an exact unique match on an unambiguous identifier for the as_of date. 0.7-0.99 means a unique match reached through normalisation, an alias or a historical record. 0.4-0.69 means the best of several plausible candidates and `alternates` is populated -- prefer asking the user over picking one. Below 0.4 is speculative: do not act on it. `status` is resolved, ambiguous or unresolved. An unresolved answer is a real result, not an error: it means this dataset cannot identify the thing, and inventing one would be worse. Every field in `best` has a citation in `provenance`. When the thing exists and this dataset could not identify it, report_unmet_need with gap_kind `unresolved` is how that gap gets prioritised -- report it, then tell the user you could not find it.

100.0/100

1 trials · measured 27 days ago

resolve_registration 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: resolve_registration
[![Vouch score](https://vouch.tools/api/tools/54abcf97-65c7-43ce-9135-25de59d77a50/badge.svg)](https://vouch.tools/tools/54abcf97-65c7-43ce-9135-25de59d77a50)
resolve_registration — Vouch