SBAS Standards to Operations Evidence Ladder

Purpose

This note defines the evidence ladder required before a core SBAS statement can become an operational aviation statement.

It is a routing note, not an operational approval document.

The ladder

LayerQuestionPrimary owner in this KBEvidence family
1. Standards conceptWhat does the standards family define or constrain?SBAS Standards Source MatrixAnnex 10, DO-229, Doc 9849, procedure-design source notes
2. Service definitionWhat does the provider state it broadcasts or supports?Source - SBAS Service Providers and child notesofficial provider service definitions/status/performance publications
3. Receiver capabilityWhat can the approved receiver process and present?SBAS Receiver Modes and AnnunciationMOPS and article-approval source families
4. Procedure designWhat type of procedure can be designed?procedure-design source notes and aviation pagesPANS-OPS/PBN and state design material
5. Procedure publicationIs a procedure published for a specific runway and cycle?SBAS Operational Validation DashboardAIP/AIS/procedure database evidence
6. Aircraft/operator authorizationMay this aircraft/operator fly it?SBAS Operational Validation Dashboardaircraft, avionics, operator, and regulator evidence
7. Current operational useIs it usable now under current status and contingencies?operational validation dashboard and source-specific notescurrent service, NOTAM/status, AIP, operator, and procedure evidence

Rule

A claim can move upward only when the next evidence layer is explicitly sourced. Lower layers do not automatically prove higher layers.

Common failure modes

  • Treating Annex 10 or DO-229 as proof that a state has published procedures.
  • Treating a service-provider page as proof that aircraft and operators are approved.
  • Treating an AIP procedure as proof that all SBAS-capable aircraft may fly it.
  • Treating a receiver capability label as a service-performance claim.

Relationship to existing routing notes

Source anchors

See also