SBAS Knowledge Base

SBAS Receiver Modes and Annunciation

2 min read

SBAS Receiver Modes and Annunciation

Purpose

This note explains where receiver-mode and annunciation claims belong in the knowledge base.

It does not publish cockpit procedures, detailed alerting logic, message validity rules, receiver algorithms, equipment classes, or pilot operating instructions. Those require direct standards, avionics, aircraft, and operator sources.

Receiver concept boundaries

TopicSafe concept-level statementRequired evidence before detail
Receiver modeA receiver may present or use modes according to its design and approval basisMOPS, article approval, aircraft/avionics manuals
AnnunciationThe receiver/flight deck must communicate relevant mode or alert status to the crew according to approved designavionics and aircraft documentation
Integrity alertingReceiver behavior is part of the integrity chainDO-229 and operational sources before detailed timing/logic claims
Procedure useReceiver mode must match procedure and operation requirementsprocedure chart/AIP, aircraft, operator, and regulator evidence

What this note blocks

Do not infer:

  • a cockpit annunciation from a service-provider source;
  • a receiver mode from SBAS coverage;
  • aircraft eligibility from a generic equipment standard;
  • procedure authorization from receiver capability alone;
  • pilot action from a concept page.

Relationship to integrity

Receiver behavior is where the broadcast and airborne approval layers meet operational use. It must be routed through:

  1. SBAS Signal and Message Flow for message path;
  2. SBAS Corrections and Integrity Separation for correction/integrity distinction;
  3. Protection Levels and Alert Limits for usability concepts;
  4. SBAS Standards to Operations Evidence Ladder for escalation into operations.

Source anchors

See also

Graph View

Backlinks