Detailed reference for the Global Aeronautical Distress and Safety System (GADSS). This folder expands the summary in topics/gadss.md into per-aspect files so each can be read independently.

Files in this folder#

• overview.md — what GADSS is, how it arose from MH370, and how it sits in the ICAO/ATM/SAR framework.
• components.md — the building blocks: normal tracking technology, ADT triggering logic, ELT(DT), ADFR, LADR, OPS Control Directory, flight recorders, and the RCC/ATSU interface.
• blocks.md — the three functional pillars (Aircraft Tracking, ADT, Post-Flight Localization and Recovery) as maturity stages with applicability dates; mermaid of the distress-detection-to-recovery flow.
• threads.md — the six functional axes that together constitute GADSS: normal tracking, autonomous distress tracking, post-flight localization, flight recorder evolution, SAR alerting integration, and avionics and equipage.
• modules.md — anatomy of one complete GADSS activation: ADT triggers, 1-minute position stream, LADR upload, ATSU alert, RCC notification, and SAR response; worked end-to-end example.
• enablers.md — CNS infrastructure, avionics certification, COSPAS- SARSAT, training, regulation, oversight, and institutional bodies.
• performance_objectives.md — KPA matrix and KPIs for measuring GADSS effectiveness: safety, SAR response time, data recovery.
• timeline.md — year-keyed history from MH370 (2014) to normal tracking (2018), ADT applicability (2025), and Doc 10165 (2025).
• references.md — consolidated ICAO and authoritative external references for all content in this folder.

Reading order#

Start with overview.md to understand the concept and its origins, then components.md for the structural building blocks. Read blocks.md for the three functional pillars and maturity stages, threads.md for the functional axes, and modules.md for a concrete worked example. Use enablers.md for planning and compliance checklists, performance_objectives.md for KPA mapping, and timeline.md for date context. references.md is the citation master list.

Source basis#

Content is grounded in:

• ICAO Annex 6, Part I (Operation of Aircraft — International Commercial Air Transport), 12th Edition with amendments through Amendment 50; particularly §3.5, §6.3.2, §6.3.6, §6.17, §6.18, Appendix 8, Appendix 9, and Attachment H.
• ICAO Annex 11 (Air Traffic Services), Chapter 5, §5.1.3.
• ICAO Annex 12 (Search and Rescue).
• ICAO Doc 10165 (Manual on Global Aeronautical Distress and Safety System), First Edition, 2025.
• ICAO Doc 10150 (Functional Specifications for the LADR).
• ICAO Circular 347-AN/205 (Aircraft Tracking Implementation Guidelines).
• ICAO Doc 10065 and Doc 10073 (Council session records documenting the MH370-driven GADSS deliberations).

What GADSS is#

The Global Aeronautical Distress and Safety System (GADSS) is the overarching ICAO construct for a set of Standards and Recommended Practices (SARPs) and associated provisions that collectively ensure an aircraft's location is always known and that effective search and rescue (SAR) operations can be initiated whenever an aircraft enters a distress condition or an accident occurs.

GADSS is not a single technology or a single system. It is a performance-based framework: it defines what must be achieved and to what accuracy — locating an accident site to within a 6 NM radius is the stated objective of the autonomous distress tracking function — and it leaves industry free to choose the technology that meets those performance requirements.

Doc 10165 (Manual on Global Aeronautical Distress and Safety System, First Edition, 2025) is the authoritative guidance document. It defines GADSS at §1.1.1 as having four objectives:

• assist in timely detection and subsequent tracking of aircraft in distress;
• assist in the timely identification of the accurate location of end of flight;
• assist in timely retrieval of flight recorder data (FRD); and
• enable timely and effective SAR operations and accident investigation.

Where GADSS came from — the MH370 catalyst#

On 8 March 2014, Malaysian Airlines flight MH370 disappeared with 239 people on board. The last ATC contact and the last radar return were over the South China Sea. Despite an unprecedented multi-nation search, the aircraft was not located for many months and the wreckage was never fully recovered.

The key operational lesson was that the global air traffic system had no means to locate an aircraft beyond radar coverage, no automatic position broadcast triggered by distress, and no mechanism to ensure flight recorder data could be recovered promptly.

Within weeks of the disappearance, ICAO convened a special multidisciplinary meeting on global flight tracking (MMGFT) at ICAO Headquarters on 12 and 13 May 2014. That meeting established the GADSS framework and agreed on near-term, medium-term, and long-term action. The Second ICAO High-level Safety Conference (HLSC 2015, February 2015) endorsed the GADSS Concept of Operations and directed expeditious SARPs adoption. The Normal Aircraft Tracking Implementation Initiative (NATII) was formed on 19 February 2015 to lead the near-term work.

The earlier disappearance of Air France flight AF447 in June 2009 over the South Atlantic — where the Flight Data Recorder and Cockpit Voice Recorder were not recovered for nearly two years — had already underscored the need for deployable flight recorders and faster data recovery. GADSS absorbed and codified the lessons from both accidents.

Where GADSS sits in the ICAO/ATM/SAR framework#

GADSS is anchored in Annex 6 (Operation of Aircraft), Part I. It involves four ICAO Annexes and several PANS and manuals:

• Annex 6, Part I — the primary SARPs instrument for aircraft tracking (§3.5), location of an aeroplane in distress (§6.18), flight recorder requirements (§6.3), ELT carriage (§6.17), and the ADFR standard (Appendix 8). This is the operator's primary compliance reference.
• Annex 11 (Air Traffic Services) — requires ATS authorities to maintain contact details in the OPS Control Directory (§5.1.3) and references LADR as a source of distress position information.
• Annex 12 (Search and Rescue) — addresses SAR responsiveness, coordination between RCCs and ATSUs on receipt of ADT information, and SAR personnel safety at accident sites.
• Annex 13 (Aircraft Accident and Incident Investigation) — references GADSS data and information in the context of investigations.
• PANS-OPS (Doc 8168), Volume III, Section 10 — operational procedures for monitoring aircraft tracking information and for making distress position information available; directly supports ATSUs in using GADSS data.
• Doc 10165 (First Edition, 2025) — implementation guidance; supersedes Circular 347 and Doc 10054.
• Doc 10150 — functional specifications for the LADR.

GADSS connects to SAR through the RCC (Rescue Coordination Centre) interface: when ADT data flows into the LADR, the RCC can retrieve the last known position of the aircraft in distress and cue SAR assets to a 6 NM radius around that position. The GADSS framework therefore bridges the civil aviation operator/ANSP world and the SAR community, using information management (LADR, OPS Control Directory) as the connective tissue.

Scope: who must comply#

The GADSS obligations under Annex 6, Part I apply to operators of aeroplanes engaged in international commercial air transport as defined in Annex 6. The scope is determined by aircraft mass thresholds and certificate of airworthiness dates:

• Normal aircraft tracking (§3.5.3): aeroplanes with maximum certificated take-off mass over 45,500 kg and seating capacity greater than 19, in oceanic areas — Standard applicable from 8 November 2018. Aeroplanes over 27,000 kg with seating greater than 19 — Recommended Practice for all areas.
• Autonomous distress tracking (§6.18.1): aeroplanes over 27,000 kg with first certificate of airworthiness on or after 1 January 2024 — Standard applicable from 1 January 2025.
• ADT Recommended Practice (§6.18.2): aeroplanes over 5,700 kg with first certificate on or after 1 January 2023.
• Flight recorder data recovery (§6.3.6): aeroplanes over 27,000 kg with more than 19 passengers, where type certification application was submitted on or after 1 January 2021.

References#

• Doc 10165 (Manual on Global Aeronautical Distress and Safety System), First Edition, 2025, Chapter 1, §1.1.1 — GADSS objectives.
• Doc 10165, Chapter 1, §1.2.1 — GADSS four functions and normative references.
• Annex 6 (Operation of Aircraft), Part I, Chapter 3, §3.5 — Aircraft tracking SARPs; applicability 8 November 2018.
• Annex 6, Part I, Chapter 6, §6.18 and Appendix 9 — Location of aeroplane in distress; ADT applicability 1 January 2025.
• Circular 347-AN/205, Chapter 1, §1.1.1-1.1.2 — MH370 catalyst and MMGFT meeting of 12-13 May 2014.
• Annex 11 (Air Traffic Services), Chapter 5, §5.1.3 — OPS Control Directory requirement.
• Annex 12 (Search and Rescue) — SAR responsiveness in relation to GADSS (authoritative source — not in local library; see current edition).
• Annex 13 (Aircraft Accident and Incident Investigation) — GADSS data use in investigations (authoritative source — not in local library; see current edition).

The building blocks of GADSS#

GADSS is a system of systems. No single component delivers GADSS capability in isolation. The following are the principal building blocks, each mapped to its normative reference in ICAO SARPs.

1. Aircraft tracking capability (operator-level)#

What it is. The operator-maintained, ground-based process that records and updates the 4D position (latitude, longitude, altitude, time) of each aircraft in the operator's fleet throughout its area of operations at intervals not exceeding 15 minutes.

SARPs reference. Annex 6, Part I, §3.5. Standard 3.5.3 (oceanic) and Recommended Practice 3.5.2 (all areas).

Technologies used. Any combination of:

• ADS-B (Automatic Dependent Surveillance-Broadcast): aircraft broadcasts GNSS-derived position; ground stations or other aircraft receive and relay it.
• ADS-C (Automatic Dependent Surveillance-Contract): aircraft reports position periodically under a FANS/CPDLC contract; used in oceanic areas where ADS-B ground coverage is absent.
• ACARS/SATCOM position reports: FMS-generated messages sent via VHF data link (VDL) or satellite communications.
• Waypoint position reporting (WPR): position report transmitted at each waypoint.
• SSR Mode S extended squitter where coverage allows.

Key rule. The operator is responsible even when using third-party services; responsibility cannot be delegated (Annex 6, Part I, §4.2.1.3.1).

2. Autonomous Distress Tracking (ADT) system#

What it is. The on-board capability that automatically broadcasts aircraft position at least once every minute when the aircraft enters a distress condition, without requiring flight crew action. The system must continue operating even with aircraft electrical power loss, for the expected duration of the entire flight. Deactivation is only possible via the same mechanism that triggered activation.

SARPs reference. Annex 6, Part I, §6.18 and Appendix 9.

Distress condition defined. Appendix 9, §2.2: a state that, if the aircraft behaviour event is left uncorrected, can result in an accident. Examples include unusual attitudes, unusual speed conditions, collision with terrain, total loss of thrust on all engines, and ground proximity warnings.

Performance objective. Locate the accident site to within a 6 NM (11 km) radius.

Trigger logic. A triggered system must commence position transmission within five seconds of detecting the activation event (Appendix 9, §2.2 Note 2). EUROCAE ED-237 provides the Minimum Aviation System Performance Specification (MASPS) for in-flight event detection criteria.

Position accuracy. Must at minimum meet the position accuracy requirements established for ELTs (Appendix 9, §2.6).

2.1 ELT(DT) — Emergency Locator Transmitter (Distress Tracking)#

The ELT(DT) is the COSPAS-SARSAT satellite-based ADT device. It broadcasts on the 406 MHz distress frequency via the COSPAS-SARSAT Low-Earth Orbit Satellite System (LEOSS) and Medium-Earth Orbit Satellite System (MEOSS). ELT(DT) messages carry a clear indicator that the source is a distress tracking alert, distinguishing them from traditional ELT crash signals. An ELT(DT) can optionally be configured to act as a post-crash ELT(AF), continuing to transmit a homing signal on 121.5 MHz after impact. An ELT(DT) alone does not satisfy the ELT carriage requirement under §6.17 — the two obligations are separate.

2.2 Automatic Deployable Flight Recorder (ADFR)#

The ADFR is a combined flight recorder (FDR + CVR data) that ejects automatically from the aircraft before or at impact, activates its integrated ELT, and floats. It satisfies both the ADT/PFL functions (because the integrated ELT transmits position) and the flight data recovery function (because the recorder is physically separated from the wreckage). Annex 6, Part I, Appendix 8, §4, and Attachment H govern ADFR technical requirements.

3. Post-Flight Localization (PFL) equipment#

What it is. Equipment that guides SAR assets to the accident site after the end of flight.

Principal components:

• ELT (any type satisfying Annex 6, Part I, §6.17) — mandatory carriage on commercial air transport aeroplanes.
• Underwater Locating Device (ULD) on the FDR and CVR — required under Annex 6, Part I for aeroplanes operating over water; enables sonar location of sunken recorders.
• ELT(AD) (Automatic Deployable ELT) — rigidly attached, deploys and activates automatically on impact.

4. Flight Recorder systems#

FDR (Flight Data Recorder). Records mandatory flight parameters. Annex 6, Part I, §6.3.1 requires FDRs to retain at least the last 25 hours of operation for qualifying aircraft.

CVR (Cockpit Voice Recorder). Records cockpit audio. Annex 6, Part I, §6.3.2.3.2 requires 25-hour CVR recording duration for aeroplanes over 27,000 kg with first certificate of airworthiness on or after 1 January 2022 (Amendment 46, applicable 25 March 2021).

Flight Recorder Data Recovery (FRDR). Annex 6, Part I, §6.3.6 requires qualifying aeroplanes (type certification applied from 1 January 2021) to carry a State-approved means to make FDR/CVR data available in a timely manner, without waiting for physical recovery of the underwater recorder. Doc 10054 provides guidance.

5. LADR — Location of an Aircraft in Distress Repository#

What it is. A centralised, SWIM-compatible repository that collects and stores ADT position data from all approved distress tracking systems, regardless of manufacturer or operator.

Why it matters. Because operators install different ADT technologies (ELT(DT), SATCOM-based, ADFR-integrated), an RCC responding to a distress event would otherwise need to contact each system operator separately. The LADR provides a single query point: any authorised ATSU or RCC can retrieve the last known position of any aircraft with an active ADT event.

Governance. Doc 10150 (Functional Specifications for the LADR) specifies the minimum dataset (aircraft identification, latitude, longitude, time-stamp), data access rules, quality assurance, and privacy protections. The LADR host organisation operates under ICAO oversight. States and operators wishing to use novel ADT systems must coordinate with ICAO and the LADR host to establish a data feed (Doc 10165, §3.6.1.5).

6. OPS Control Directory#

What it is. A centrally maintained directory of current contact details for air traffic service units (ATSUs) — specifically flight information centres and area control centres — to enable operators to reach the appropriate ATSU quickly during an aircraft status event.

SARPs reference. Annex 11, §5.1.3 requires each ATS authority to maintain and keep current its entries in the OPS Control Directory.

7. RCC/ATSU interface#

The ATSU is the first contact point in the ATS system when an aircraft status event occurs. The ATSU uses the OPS Control Directory to contact the operator and uses the LADR to obtain distress position data. Annex 11 (Note at §5.1.3) and Annex 12 define the coordination processes between ATSUs and RCCs.

How the components connect#

Normal aircraft tracking (Annex 6, §3.5)
  +--> Operator tracks every 15 min max
  +--> ATSU receives position reports
  +--> OPS Control Directory (ATSU contacts operator)

Distress event triggers ADT (Annex 6, §6.18 + App 9)
  +--> ADT system activates (automatic, 1-min position)
  +--> ELT(DT) / SATCOM / ADFR transmits position
  +--> LADR receives and stores ADT data
  +--> Operator alerts ATSU and RCC
  +--> RCC queries LADR for last known position
  +--> SAR assets cued to 6 NM radius

Post-flight
  +--> ELT homing signal guides SAR to site (PFL)
  +--> ADFR floats, continues ELT transmission
  +--> FDR/CVR data recovered (FRDR)

References#

• Annex 6 (Operation of Aircraft), Part I, Chapter 3, §3.5 — Aircraft tracking: automated 4D position reporting standard.
• Annex 6, Part I, Chapter 6, §6.18 and Appendix 9 — Location of an aeroplane in distress; ADT requirements and distress condition definition.
• Annex 6, Part I, Chapter 6, §6.3.2.3.2 — CVR 25-hour recording duration.
• Annex 6, Part I, Chapter 6, §6.3.6 — Flight recorder data recovery requirement.
• Annex 6, Part I, Chapter 6, §6.17 — ELT carriage requirements.
• Annex 6, Part I, Appendix 8, §4 — ADFR technical requirements.
• Annex 11 (Air Traffic Services), Chapter 5, §5.1.3 — OPS Control Directory maintenance obligation.
• Doc 10165 (Manual on GADSS), First Edition, 2025, Chapter 1, §1.2 — GADSS architecture and component overview.
• Doc 10165, Chapter 3, §3.3.3 — ADT system overview; ELT(DT) and SATCOM technology options.
• Doc 10165, Chapter 4 — Post flight localization equipment and procedures.
• Doc 10165, Chapter 5 — Flight data recovery; ADFR and FRDR.
• Doc 10165, Chapter 6, §6.1-6.4 — GADSS information management; LADR and OPS Control Directory.
• Doc 10150 (Functional Specifications for the LADR) — Minimum dataset, access rules, and SWIM interface for the LADR (authoritative source — not in local library).

The three GADSS pillars#

GADSS is structured around three functional pillars, each targeting a distinct phase of an aircraft emergency and each governed by its own set of Annex 6 SARPs. The blocks below use the term "pillar" to match the GADSS architecture; they are not ASBU blocks but are presented as maturity stages because each was implemented at a different time and each has distinct applicability conditions.

Pillar 1 — Normal Aircraft Tracking (applicable 8 November 2018)#

Purpose. Maintain a continuous ground-based 4D record of every aircraft's position at no more than 15-minute intervals so that when normal surveillance is unavailable, the search area for a missing aircraft is constrained.

Key SARPs (Annex 6, Part I, §3.5):

• §3.5.1 (Standard): operator shall establish an aircraft tracking capability throughout its area of operations.
• §3.5.3 (Standard, oceanic): operator shall track at no more than 15-minute intervals in oceanic areas for aeroplanes over 45,500 kg with seating greater than 19 where ATS obtains position at intervals greater than 15 minutes.
• §3.5.2 (Recommended Practice): same 15-minute standard recommended for aeroplanes over 27,000 kg in all areas of operation.
• §3.5.4: State of Operator may permit risk-assessed variations to the automated reporting interval.
• §3.5.5: operator shall retain tracking data to assist SAR in determining last known position.

Technology-neutral. ADS-B, ADS-C, ACARS, SATCOM WPR, or any automated means satisfying the standard. No new procedures imposed on ATSUs.

Pillar 2 — Autonomous Distress Tracking / Location of Aircraft#

in Distress (applicable 1 January 2025)#

Purpose. Automatically broadcast aircraft position at 1-minute intervals when the aircraft enters a distress condition, so that the accident site can be located to within a 6 NM radius. This function operates independently of the flight crew and continues even with electrical power loss.

Key SARPs (Annex 6, Part I, §6.18 and Appendix 9):

• §6.18.1 (Standard): as of 1 January 2025, aeroplanes over 27,000 kg with first certificate of airworthiness on or after 1 January 2024 shall autonomously transmit position at least once per minute when in distress.
• §6.18.2 (Recommended Practice): aeroplanes over 5,700 kg with first certificate on or after 1 January 2023 should comply.
• §6.18.3: operator shall make distress position information available to appropriate organisations as established by the State of the Operator.
• Appendix 9, §2.1: aeroplane in distress shall automatically activate position transmission; manual activation shall also be possible.
• Appendix 9, §2.2: distress condition definition; triggering events; initial transmission within five seconds; autonomous operation under power loss.
• Appendix 9, §2.4: notification to ATSUs and RCCs as minimum.

History of the applicability date:

• Amendment 40-A adopted 2 March 2016; original applicability: 1 January 2021.
• Industry supply-chain and certification constraints identified in 2020-21 caused deferral.
• Amendment 48 adopted 18 July 2022; revised applicability to 1 January 2025 for aeroplanes with first certificate on or after 1 January 2024.

Pillar 3 — Post-Flight Localisation and Data Recovery#

Purpose. Once an accident occurs, guide SAR services to the site via ELT signals and ensure flight recorder data is available to accident investigators within hours rather than months.

Key SARPs:

• Annex 6, Part I, §6.17: ELT carriage requirements (20+ pax aeroplanes in international CAT must carry at least one automatic ELT).
• Annex 6, Part I, Appendix 8, §4: ADFR requirements — ejects before impact, floats, integrated ELT activates automatically.
• Annex 6, Part I, §6.3.6 (FRDR): aeroplanes over 27,000 kg with more than 19 passengers, where type certification was applied on or after 1 January 2021, shall carry a State-approved means to make FDR/CVR data available in a timely manner.
• Annex 6, Part I, §6.3.2.3.2 (CVR 25-hour): aeroplanes over 27,000 kg with first certificate on or after 1 January 2022 shall have 25-hour CVR recording duration (Amendment 46, applicable 25 March 2021).
• Annex 6, Part I, §6.3.1 (FDR 25-hour): all FDRs on qualifying aeroplanes shall retain at least 25 hours of operation.

Mermaid: Distress-detection-to-recovery flow#

Applicability summary#

References#

• Annex 6 (Operation of Aircraft), Part I, Chapter 3, §3.5 — Normal aircraft tracking SARPs; Amendment 39 applicable 8 November 2018.
• Annex 6, Part I, Chapter 6, §6.18 — Location of aeroplane in distress; Amendment 48; applicability 1 January 2025.
• Annex 6, Part I, Appendix 9 — Distress condition definition; 1-minute transmission; 6 NM accuracy objective; ATSU/RCC notification.
• Annex 6, Part I, Chapter 6, §6.3.6 — FRDR requirement; type certification threshold of 1 January 2021.
• Annex 6, Part I, Chapter 6, §6.3.2.3.2 — CVR 25-hour duration; Amendment 46; applicable 25 March 2021.
• Annex 6, Part I, Appendix 8, §4 — ADFR technical requirements.
• Doc 10165 (Manual on GADSS), First Edition, 2025, Chapter 1, §1.2 — Four GADSS functions and their normative references.
• Doc 10192 (ICAO Council session records) — Records of Council deliberations leading to Amendment 48 and the COVID-19 pandemic deferral of the ADT applicability date from 2023 to 2025.

The six GADSS threads#

GADSS capability is delivered through six functional threads — distinct subject axes that each contribute to the overall objective of ensuring an aircraft can always be located and that SAR operations can be mounted effectively.

The threads are interdependent: Thread 1 (normal tracking) establishes the baseline position awareness from which a distress event is detected. Thread 2 (ADT) activates when Thread 1 fails to explain the aircraft status. Threads 3 and 4 complete the post-accident coverage.

Thread 1 — Normal Aircraft Tracking#

Axis. Continuous ground-based 4D position record at no more than 15-minute intervals under normal operating conditions.

Core provisions. Annex 6, Part I, §3.5 (Amendment 39, applicable 8 November 2018).

Key characteristics:

• Technology-neutral: ADS-B, ADS-C, ACARS, SATCOM WPR all qualify.
• Operator-held data; no mandatory sharing with ATSUs during normal ops, but data must be available to SAR on request (§3.5.5).
• Standard in oceanic areas (>45,500 kg, >19 seats); Recommended Practice in all areas (>27,000 kg, >19 seats).
• Variations to the reporting interval are permitted with a State- approved risk assessment (§3.5.4).

Thread 1 to Thread 2 transition. When normal tracking data becomes unavailable or when the position shows a distress event, the ADT system takes over.

Thread 2 — Autonomous Distress Tracking (ADT)#

Axis. Automatic, unsolicited 1-minute position broadcasting that activates when the aircraft enters a distress condition, without requiring flight crew action.

Core provisions. Annex 6, Part I, §6.18 and Appendix 9 (Amendment 48, applicable 1 January 2025).

Key characteristics:

• Performance-based: operators may use any technology that meets the standard (ELT(DT), SATCOM-based, ADFR-integrated ELT).
• Must operate independently of aircraft electrical power.
• Must achieve 6 NM position accuracy at 1-minute intervals.
• Triggering criteria include unusual attitudes, unusual speed, GPWS activation, and total loss of thrust.
• Position data must reach the LADR and be made available to designated ATSUs and RCCs.
• The LADR provides the global interoperability layer that unifies data from different ADT technology vendors.

Relationship to COSPAS-SARSAT. ELT(DT) uses the existing 406 MHz COSPAS-SARSAT satellite infrastructure, giving ADT global coverage including oceanic and polar areas where ADS-B ground coverage is absent.

Thread 3 — Post-Flight Localisation#

Axis. Hardware that guides SAR services to the accident site after end of flight.

Core provisions. Annex 6, Part I, §6.17 (ELT carriage); Appendix 8, §4 (ADFR); §6.5.3 (ULD for underwater location).

Key characteristics:

• ELT(AF), ELT(AP), or ELT(AD) as a minimum on qualifying aeroplanes.
• ELT transmits on 406 MHz (COSPAS-SARSAT) and 121.5 MHz (homing).
• ADFR ejects before impact, floats, and activates integrated ELT.
• Underwater Locating Device (ULD) on FDR and CVR containers enables sonar location of sunken recorders.

Thread 4 — Flight Recorder Evolution#

Axis. Improvements to what is recorded, for how long, and how the data can be recovered in a timely manner.

Core provisions. Annex 6, Part I, §6.3 (FDR, CVR, ADFR); §6.3.2.3.2 (25-hour CVR); §6.3.6 (FRDR).

Key characteristics:

• FDRs retain at least 25 hours of data on qualifying aircraft.
• CVR 25-hour duration required for aeroplanes >27,000 kg with first certificate on or after 1 January 2022.
• FRDR (flight recorder data recovery): a State-approved means to make FDR/CVR data available in a timely manner, required for new aircraft types with type certification applied from 1 January 2021.
• ADFR satisfies both PFL (Thread 3) and FRDR (Thread 4) objectives.
• Cockpit Area Microphone (CAM) and Airborne Image Recorder (AIR) are additional recording systems where required.

Thread 5 — SAR Alerting Integration#

Axis. Ensuring that distress information flows rapidly and reliably from the aviation system to the SAR response chain (ATSUs and RCCs).

Core provisions. Annex 6, Part I, §6.18.3 (operator to provide distress position to appropriate organisations); Appendix 9, §2.3-2.4 (ATSU/operator coordination; ATSU and RCC notification); Annex 11, §5.1.3 (OPS Control Directory); Annex 12.

Key characteristics:

• When ADT activates, the operator is alerted and must forward position to the designated ATSU and RCC.
• ATSUs use the OPS Control Directory to contact operators quickly.
• RCCs query the LADR for last known position.
• PANS-OPS, Doc 8168, Volume III, Section 10 provides the operational procedures for ATSUs monitoring aircraft tracking and distress position data.
• Annex 11 and Annex 12 procedures remain applicable; ADT data supplements rather than replaces existing alerting processes.

Thread 6 — Avionics and Equipage#

Axis. The certification, installation, and on-board integration of GADSS equipment — the hardware-enabling thread that determines when states and operators can practically comply.

Key characteristics:

• ADT compliance requires State airworthiness certification of the chosen system before acceptance on the national register.
• EUROCAE ED-237 provides the MASPS for ADT distress event detection criteria.
• ELT(DT) requires alignment with COSPAS-SARSAT second-generation system specifications.
• ADFR requires certification as a combined flight recorder under Appendix 8 requirements.
• The pandemic-driven deferral of ADT applicability (from 2021 to 2025) was partly caused by supply-chain disruption in the avionics certification process.
• States intending to approve novel ADT systems must coordinate with ICAO and the LADR host before granting certification (Doc 10165, §3.6.1.5).

Thread interdependency map#

• Thread 1 (normal tracking) establishes the baseline; its failure or anomaly may trigger Thread 2.
• Thread 2 (ADT) activates automatically and feeds data into the LADR (Thread 5 information layer).
• Thread 5 (SAR alerting) uses LADR data and OPS Control Directory to alert ATSUs and RCCs.
• Thread 3 (PFL) takes over once the aircraft has ended flight and directs SAR assets cued by Thread 5.
• Thread 4 (flight recorders) provides the investigation evidence recovered alongside Thread 3 hardware.
• Thread 6 (avionics) is the prerequisite: no other thread operates without certified equipment.

References#

• Annex 6 (Operation of Aircraft), Part I, Chapter 3, §3.5 — Thread 1: normal aircraft tracking.
• Annex 6, Part I, Chapter 6, §6.18 and Appendix 9 — Thread 2: ADT; 1-minute position; distress condition.
• Annex 6, Part I, Chapter 6, §6.17; Appendix 8, §4 — Thread 3: ELT carriage and ADFR.
• Annex 6, Part I, Chapter 6, §6.3.2.3.2, §6.3.6 — Thread 4: CVR 25-hour and FRDR.
• Annex 6, Part I, Appendix 9, §2.3-2.4; Annex 11, §5.1.3 — Thread 5: SAR alerting and OPS Control Directory.
• Doc 10165 (Manual on GADSS), First Edition, 2025 — Thread architecture and interdependencies.
• PANS-OPS (Doc 8168), Volume III, Section 10 — Thread 5: ATSU procedures for monitoring tracking and distress position data (authoritative source — not in local library).

Purpose of this file#

This file dissects a single GADSS capability — Autonomous Distress Tracking (ADT) activation — as a worked end-to-end example. It traces the event from the first on-board distress detection signal through the data flow to the RCC, and maps each step to its normative ICAO reference.

The ADT event is the central intersection in GADSS: Thread 2 (autonomous distress tracking) at Pillar 2 (location of aircraft in distress). All other threads either precede it (normal tracking) or follow from it (SAR alerting, PFL).

The ADT module — step-by-step#

Step 1. Normal flight — Thread 1 active#

The aircraft is in flight. The operator's tracking system is receiving automated 4D position reports at intervals not exceeding 15 minutes (Annex 6, Part I, §3.5.3). Typical means: ADS-C contracts over the oceanic FIR, or ACARS/SATCOM WPR when beyond radar coverage.

The ATSU may also have radar or ADS-B surveillance. The OPS Control Directory has the operator's current emergency contact details.

Step 2. Distress condition detected on board#

An on-board parameter crosses a threshold defined as a distress condition (Appendix 9, §2.2): for example, the aircraft enters an unusual attitude, a GPWS/TAWS alert fires, or all engines flame out.

The detection logic is not prescribed by ICAO in detail; EUROCAE ED-237 (MASPS for Criteria to Detect In-Flight Aircraft Distress Events) provides the minimum performance specification. The on-board system processes the event autonomously.

Step 3. ADT activates — no crew action required#

Within five seconds of detecting the distress event (Appendix 9, §2.2 Note 2), the ADT system begins transmitting position information. No flight crew input is required or expected. The system must continue even if aircraft electrical power is lost; it must carry its own power source for the expected duration of the entire flight.

Position information is transmitted at least once per minute (§6.18.1). The information includes latitude, longitude, and time stamp. Position accuracy must meet or exceed the ELT position accuracy standard (Appendix 9, §2.6).

Step 4. ELT(DT) transmits on 406 MHz (if ELT(DT) equipped)#

If the ADT system is an ELT(DT), the 406 MHz signal is uplinked by COSPAS-SARSAT satellites. The message type clearly identifies the source as a distress tracking alert, distinguishing it from a post- crash ELT activation (Doc 10165, §4.4.1). COSPAS-SARSAT processes and forwards the alert to the relevant LEUT (Local User Terminal) and hence to the Mission Control Centre (MCC).

COSPAS-SARSAT 2nd-generation satellites (Medium-Earth Orbit) provide near-real-time detection globally, including oceanic and polar areas. First-generation LEO satellites may introduce a delay of up to 90 minutes; MEOSS reduces this to minutes.

Step 5. ADT data flows to LADR#

The ADT position messages (from ELT(DT) via COSPAS-SARSAT, or from a SATCOM-based ADT system via its own data path) are delivered to the LADR (Location of an Aircraft in Distress Repository, Doc 10150).

The LADR stores the time-stamped position records for the flight, associating them with the aircraft identification. Access is restricted to authorised entities: operators, ATSUs, and RCCs as established by the State of the Operator (§6.18.3). The LADR interface is SWIM- compatible, facilitating automated data distribution.

Step 6. Operator alerted; notification to ATSU and RCC#

The operator is alerted — either by the ADT system or by COSPAS-SARSAT MCC notification (Doc 10165, §3.5.1). The operator validates the distress event (false alert checks) and then contacts the responsible ATSU using the OPS Control Directory contact details (Annex 11, §5.1.3) and notifies the RCC.

Appendix 9, §2.3 requires that when an operator or ATSU has reason to believe an aircraft is in distress, coordination shall be established between the ATSU and the operator. Appendix 9, §2.4 requires notification to ATSUs and RCCs as a minimum.

Annex 11 existing alerting phase procedures (INCERFA, ALERFA, DETRESFA) remain applicable. ADT data provides additional position evidence but does not change the existing alerting structure (Doc 10165, §3.5.2.1).

Step 7. RCC cues SAR assets using LADR data#

The RCC queries the LADR for the last known position of the aircraft. The LADR returns the most recent ADT position, giving the RCC a 1- minute-resolution track of the distress flight. The SAR initial search area is defined as a 6 NM radius around the last LADR position (Annex 6, Appendix 9, §1).

This is the transformational improvement GADSS delivers versus the pre-MH370 situation: before ADT, the RCC had only radar returns (if any), flight plan waypoints, or discrete position reports. ADT narrows the search area from thousands of square nautical miles to a circle of approximately 110 NM squared.

Step 8. Post-flight localization and data recovery#

If the aircraft has impacted, the ELT (§6.17) begins its post-crash function, transmitting on 121.5 MHz for homing and on 406 MHz for COSPAS-SARSAT. If an ADFR is installed, it has ejected and deployed, floating on the surface and transmitting independently.

SAR assets arrive, survivors are rescued, the wreckage is located. The ADFR and/or the sunken recorder (ULD-equipped) are recovered. The State-approved FRDR means (§6.3.6) ensures FDR and CVR data are made available in hours rather than months.

Key numeric parameters#

References#

• Annex 6 (Operation of Aircraft), Part I, Chapter 3, §3.5 — Normal tracking: automated 4D position at 15-minute intervals.
• Annex 6, Part I, Chapter 6, §6.18.1 — ADT standard: 1-minute autonomous position; applicable 1 January 2025.
• Annex 6, Part I, Appendix 9, §2.1-2.6 — ADT operation: automatic activation, distress condition, 5-second trigger, power independence, deactivation, ATSU/RCC notification.
• Annex 6, Part I, Appendix 9, §1 — 6 NM accuracy objective for accident site location.
• Annex 6, Part I, §6.3.2.3.2 — CVR 25-hour duration.
• Annex 6, Part I, §6.3.6 — FRDR requirement for timely data availability.
• Annex 11 (Air Traffic Services), Chapter 5, §5.1.3 — OPS Control Directory for operator contact.
• Doc 10165 (Manual on GADSS), First Edition, 2025, Chapter 3, §3.4 — ADT operation procedures.
• Doc 10165, Chapter 3, §3.5 — ATSU and RCC response to ADT activation.
• Doc 10165, Chapter 3, §3.6 — LADR data flow and access for ADT events.
• Doc 10150 (Functional Specifications for the LADR) — LADR dataset, access and SWIM interface (authoritative source — not in local library).

Overview#

GADSS capability depends on a wide range of enablers beyond the SARPs themselves. This file maps the key dependencies across CNS infrastructure, avionics, operational procedures, training, regulation, and institutional arrangements.

1. Communications infrastructure#

1.1 SATCOM and ACARS data links#

Normal aircraft tracking (Thread 1) requires that operators obtain automated position reports at 15-minute intervals in oceanic areas. In areas beyond ADS-B ground coverage, this requires either ADS-C contracts (which in turn require FANS/CPDLC data link) or SATCOM- based ACARS or waypoint reporting. Without SATCOM data link, operators in oceanic areas cannot meet §3.5.3.

Key SATCOM providers: Inmarsat Classic Aero (L-band), Iridium, and newer high-throughput SATCOM (HTS) in Ka/Ku band. The standards for SATCOM ACARS messaging are published by AEEC and ARINC.

1.2 COSPAS-SARSAT system#

ELT(DT) operation requires the COSPAS-SARSAT satellite infrastructure. The programme operates two satellite layers:

• LEOSS (Low-Earth Orbit Satellite System): proven reliability for 406 MHz alerts; initial detection time up to 90 minutes.
• MEOSS (Medium-Earth Orbit Satellite System): near-real-time detection using GPS and GLONASS search and rescue payloads; eliminates the detection delay.

COSPAS-SARSAT is governed by an international agreement between Canada, France, Russia, and the United States, with over 45 provider states and hundreds of ground receiving stations (LUTs).

For ADT purposes, ELT(DT) messages must be relayed from the MCC to the LADR in near real time. The interface between COSPAS-SARSAT MCC outputs and the LADR data submission process is governed by Doc 10150 and ICAO/COSPAS-SARSAT coordination arrangements.

2. Avionics and certification#

2.1 ADT system certification#

No ADT system may be used for compliance unless it is certified by the State of the Operator and approved for installation on the specific aircraft type. The certification process must verify:

• compliance with the position accuracy requirements (Appendix 9, §2.6);
• independent power supply for the expected flight duration;
• distress event detection criteria meeting EUROCAE ED-237 MASPS;
• automatic activation and prohibition of inadvertent deactivation.

States intending to approve novel ADT systems not yet connected to the LADR must do so in coordination with ICAO and the LADR host organisation (Doc 10165, §3.6.1.5).

2.2 ADFR certification#

The Automatic Deployable Flight Recorder must be certified as a combined flight recorder under Annex 6, Part I, Appendix 8, §4. The ADFR container must be painted a distinctive orange colour (Appendix 8, §1.1), withstand impact and fire, and float. The integrated ELT must activate automatically on deployment.

2.3 CVR and FDR#

25-hour CVR requires new recording hardware that may not be available on older aircraft as a retrofit. New aircraft deliveries from 2022 onwards (for the applicable mass category) must be factory-configured with 25-hour CVR. Similarly, FDR parameters and recording rates must meet current Annex 6, Part I, Appendix 8, §2 requirements.

2.4 EUROCAE standards#

EUROCAE (European Organisation for Civil Aviation Equipment) publishes the minimum performance standards (MASPS and MOPS) that avionics manufacturers must meet for GADSS equipment:

• ED-237: MASPS for in-flight distress event detection criteria.
• Related ED documents cover ELT(DT) performance, ADFR containers, and ULD specifications.

3. Operational procedures#

3.1 Operator tracking procedures#

Operators must establish and publish procedures for aircraft tracking, approved by the State of the Operator (§3.5.4 risk assessment; §3.5.5 data retention). These procedures must address:

• which automated means are used in which phase of flight;
• notification procedures when tracking contact is lost;
• coordination with ATSUs when position cannot be determined (§2.8f);
• third-party tracking service agreements and accountability.

3.2 ATSU alerting procedures#

ATSUs use PANS-OPS (Doc 8168), Volume III, Section 10 for procedures on monitoring aircraft tracking and distress position data. ATSUs must access the OPS Control Directory (Annex 11, §5.1.3) to contact operators quickly. Existing Annex 11 alerting phase procedures remain applicable; ADT data supplements existing processes.

3.3 SAR coordination#

Annex 12 and the IAMSAR Manual govern SAR coordination. RCCs must be designated by States as recipients of operator distress position notifications (Appendix 9, §2.4). RCCs must have access to the LADR to query last known position. SAR exercises (table-top and live) are recommended to validate GADSS end-to-end data flows.

4. Training#

4.1 Operator personnel training#

PANS-OPS, Doc 8168, Volume III, Section 10 requires operators to include in their training programmes for flight operations officers and other nominated personnel:

• use of ADT services and functionalities;
• LADR access procedures;
• distress event validation processes to reduce false alerts.

Flight crew do not activate ADT; however, they should understand that the ADT system is active and that manual activation is also possible.

4.2 ATSU controller training#

Controllers must understand that ADT position data may appear in the LADR during a declared emergency phase, even without a discrete radio call or radar return. Training must cover LADR query procedures, OPS Control Directory use, and coordination with RCCs.

5. Regulation and oversight#

5.1 State of the Operator responsibilities#

The State of the Operator must approve the operator's aircraft tracking procedures (§3.5.4), certify ADT systems for use on the national register, and designate the organisations (ATSUs, RCCs) to receive distress position information (§6.18.3). Oversight of compliance is part of the State safety oversight function under Annex 19 and the USOAP.

5.2 State of Registry obligations#

Aircraft type certification, including ADT system approval, falls to the State of Design. The State of Registry must ensure that aircraft on its register comply with the applicable SARPs, including the mass and certificate date thresholds.

6. Institutional bodies and governance#

ICAO Flight Operations Panel (FLTOPSP). The panel that developed the GADSS SARPs through Amendments 39, 40-A, 44, 46, and 48. Ongoing review of implementation issues.

ICAO GADSS Advisory Group (GADSS-AG). An advisory body providing guidance to ICAO on GADSS implementation, reviewing operational experience, and recommending updates to Doc 10165 and related documents.

COSPAS-SARSAT. The international satellite SAR programme that provides the ground segment for ELT(DT) alerting. Close coordination with ICAO is required for the LADR interface.

EUROCAE. Develops the avionics performance standards (MASPS/MOPS) that industry uses for ADT system certification.

IAMSAR (International Aeronautical and Maritime Search and Rescue) Manual. Published jointly by ICAO and IMO; contains operational SAR procedures used by RCCs in response to GADSS distress alerts.

References#

• Annex 6 (Operation of Aircraft), Part I, §3.5.4 — Risk assessment for tracking interval variations; State of Operator approval.
• Annex 6, Part I, Appendix 9, §2.4 — State obligation to designate ATSU and RCC recipients of distress position information.
• Annex 6, Part I, §6.18.3 — Operator obligation to forward distress position to appropriate organisations.
• Annex 11 (Air Traffic Services), Chapter 5, §5.1.3 — OPS Control Directory: State obligation.
• Doc 10165 (Manual on GADSS), First Edition, 2025, Chapter 3, §3.3.3.2 — ADT system performance validation.
• Doc 10165, Chapter 3, §3.6.1.5 — Novel ADT system coordination with ICAO and LADR host.
• Doc 10165, Chapter 3, §3.3 — ADT technology options: ELT(DT), SATCOM-based, ADFR-integrated.
• PANS-OPS (Doc 8168), Volume III, Section 10 — ATSU and operator procedures for aircraft tracking and distress position monitoring (authoritative source — not in local library).
• IAMSAR Manual (ICAO/IMO) — SAR coordination procedures for RCCs responding to GADSS distress alerts (authoritative source — not in local library).

The performance lens of GADSS#

GADSS is a safety-driven, performance-based framework. Each GADSS function is justified by the improvement it delivers to a Key Performance Area (KPA) defined in Doc 9854 (Global ATM Operational Concept) and Doc 9883 (Manual on Global Performance of the Air Navigation System).

The chain is:

KPA  --(measured by)-->  KPI  <--(achieved by)-->  GADSS function

Primary KPA is Safety. Secondary KPAs include Participation (global coverage of tracking and SAR), Efficiency (speed of SAR response), and Interoperability (LADR as a common information platform).

Key Performance Areas relevant to GADSS#

KPA contribution by GADSS function#

Scoring: 1 = some benefit; 2 = clear benefit; 3 = primary driver.

Performance objectives#

PO 1 — Reduce the time to determine the operational status of an#

aircraft and initiate SAR#

KPA. Safety, Efficiency.

Baseline problem. Before GADSS, an aircraft beyond radar coverage could be unreported for hours. The last known position was the last filed flight plan waypoint. SAR search areas could exceed tens of thousands of square nautical miles.

How GADSS addresses it:

• Normal tracking (15 minutes) constrains the initial search area to a circle consistent with the aircraft's speed in 15 minutes (roughly 50-60 NM radius for a typical jet).
• ADT (1 minute) further constrains the search to a 6 NM radius around the last transmitted position.

KPI. Time from last known contact to SAR initial search area definition.

PO 2 — Locate the accident site within a 6 NM radius#

KPA. Safety.

How GADSS addresses it. Annex 6, Part I, Appendix 9, §1 states explicitly: "Location of an aeroplane in distress aims at establishing, to a reasonable extent, the location of an accident site within a 6 NM radius." ADT at 1-minute intervals with ELT(DT) or SATCOM position accuracy meets this objective.

KPI. Actual search area radius vs. 6 NM standard.

PO 3 — Enable timely recovery of flight recorder data#

KPA. Safety (accident investigation effectiveness).

How GADSS addresses it. FRDR requirement (§6.3.6) for new aircraft types; ADFR floats and is recovered quickly. CVR 25-hour duration (§6.3.2.3.2) ensures adequate coverage of the hours preceding the accident.

KPI. Time from accident to FDR/CVR data availability to investigators.

PO 4 — Ensure global SAR coverage through interoperable#

information sharing#

KPA. Interoperability, Participation.

How GADSS addresses it. LADR as the universal ADT data hub: regardless of ADT technology, all position data is collected in one repository accessible to any authorised RCC worldwide.

KPI. LADR availability; number of ADT systems feeding data to LADR; percentage of qualifying aircraft with LADR-connected ADT.

KPI catalogue#

Performance monitoring#

GADSS performance is monitored through several channels:

ICAO Secretariat and Safety Section. Tracks State implementation of GADSS SARPs through the USOAP (Universal Safety Oversight Audit Programme) and through the GADSS Advisory Group (GADSS-AG).

COSPAS-SARSAT. Reports on ELT performance, false alert rates (including inadvertent ELT(DT) activations), and MEOSS coverage metrics. The 42nd ICAO Assembly noted the potential burden from inadvertent ELT(DT) activations and urged coordinated mitigation.

Regional SAR bodies. Regional RCC networks monitor SAR response times and coordinate exercises to validate end-to-end GADSS data flows.

Accident investigation reports. Each accident involving GADSS- equipped aircraft provides data on whether the system performed as intended, feeding SARPs improvements through the FLTOPSP review cycle.

References#

• Annex 6 (Operation of Aircraft), Part I, Appendix 9, §1 — 6 NM radius location accuracy objective.
• Annex 6, Part I, Appendix 9, §2.2 — 5-second ADT activation delay limit; distress condition definition.
• Annex 6, Part I, Chapter 6, §6.18.1 — 1-minute ADT position interval.
• Annex 6, Part I, Chapter 3, §3.5.3 — 15-minute normal tracking interval.
• Annex 6, Part I, §6.3.2.3.2 — 25-hour CVR duration.
• Annex 6, Part I, §6.3.1 — 25-hour FDR duration.
• Doc 9854 (Global ATM Operational Concept), Chapter 2 — KPA framework; safety as primary ATM performance dimension.
• Doc 9883 (Manual on Global Performance of the Air Navigation System) — KPI definitions and measurement methodology (authoritative source — not in local library).
• Doc 10222 (ICAO 42nd Assembly Working Papers) — Assembly note on inadvertent ELT(DT) activations and mitigation.

Two timelines to keep distinct#

When working with GADSS dates, separate two things:

1. Development timeline — when events, conferences, amendments, and publications occurred.
2. Applicability timeline — when SARPs became operative for operators and states.

A state's compliance plan is a third, national timeline that must align with the applicability dates below.

Key event and applicability dates#

Applicability date history for ADT — why the date changed#

The original ADT applicability was 1 January 2021 (Amendment 40-A, adopted 2016). In 2020-21, industry reported that supply-chain disruption caused by the COVID-19 pandemic meant aeroplanes could not complete the national airworthiness certification process needed before being accepted onto the register. Certification is not complete simply by installing equipment; each country must complete its own process.

Amendment 48 (adopted 18 July 2022) addressed this by establishing a new standard: applicable from 1 January 2025, for aeroplanes whose individual certificate of airworthiness is first issued on or after 1 January 2024. This provided a one-year lead time between the eligibility date and the applicability date.

Where GADSS fits in the ICAO safety work programme#

1944   Chicago Convention — foundation
...
2005   Doc 9854 Global ATM Operational Concept (mentions distress)
2009   AF447 — deployable recorder lesson
2014   MH370 — GADSS catalyst
2015   HLSC 2015 / NATII / CONOPS
2016   Amdt 39, 40-A — normal tracking + ADT SARPs adopted
2018   Normal tracking applicable
2021   CVR 25-hr + FRDR enter force
2025   ADT Standard applicable (new large aeroplanes)
2025   Doc 10165 published
2026   Annex 11/12/13 GADSS alignment applicable

References#

• Annex 6 (Operation of Aircraft), Part I, Foreword amendment table — full history of Amendments 39 through 50 with adopted/effective/applicable dates.
• Annex 6, Part I, Chapter 6, §6.18.1 — ADT applicability 1 January 2025.
• Annex 6, Part I, §6.3.2.3.2 — CVR 25-hour: applicable from certificates issued after 1 January 2022.
• Annex 6, Part I, §6.3.6 — FRDR: type certification from 1 January 2021.
• Circular 347-AN/205, Chapter 1, §1.1.1 — MH370 disappearance 8 March 2014; MMGFT 12-13 May 2014.
• Doc 10150 (LADR Functional Specifications) — Version history tracing ADTR-TF (2016) through version 4.0 (2020) and publication as ICAO doc.
• Doc 10165 (Manual on GADSS), First Edition, 2025 — Foreword tracing GADSS development timeline.
• Doc 10192 (ICAO Council session records) — Record of Council decision to defer ADT applicability from 1 January 2023 to 1 January 2025 due to COVID-19 supply chain impact.
• Annex 12 (Search and Rescue) — Amendment 9 (effective March 2024; applicable November 2026) incorporating GADSS responsiveness provisions.
• Annex 11 (Air Traffic Services) — Amendment 53 (effective March 2024; applicable November 2026) incorporating GADSS and LADR references.

Primary ICAO SARPs instruments#

• Annex 6 (Operation of Aircraft), Part I (International Commercial Air Transport — Aeroplanes), 12th Edition with amendments through Amendment 50 — primary SARPs vehicle for all GADSS functions; §3.5 (normal tracking), §6.3 (flight recorders), §6.17 (ELT carriage), §6.18 (location of aeroplane in distress / ADT), Appendix 8 (flight recorders), Appendix 9 (location of aeroplane in distress), Attachment H (guidance on location of aeroplane in distress).
• Annex 6, Part I, Chapter 3, §3.5 — Normal aircraft tracking: automated 4D position at 15-minute intervals; Amendment 39, applicable 8 November 2018.
• Annex 6, Part I, Chapter 6, §6.18 and Appendix 9 — Location of aeroplane in distress (ADT): 1-minute autonomous position; distress condition; 6 NM accuracy; ATSU/RCC notification; Amendment 48, applicable 1 January 2025.
• Annex 6, Part I, Chapter 6, §6.3.2.3.2 — CVR 25-hour recording duration; Amendment 46, applicable 25 March 2021; for aeroplanes >27,000 kg with first certificate from 1 January 2022.
• Annex 6, Part I, Chapter 6, §6.3.6 — Flight recorder data recovery (FRDR); for new aircraft types with type certification applied from 1 January 2021.
• Annex 6, Part I, Appendix 8, §4 — Automatic deployable flight recorder (ADFR) requirements.
• Annex 11 (Air Traffic Services), Chapter 5, §5.1.3 — OPS Control Directory: requirement for ATS authorities to maintain current ATSU contact details for GADSS emergency coordination.
• Annex 12 (Search and Rescue) — SAR responsiveness to GADSS distress events; ATSU/RCC coordination; SAR personnel safety at accident sites; GADSS-AG Amendment 9 provisions (applicable 26 November 2026) (authoritative source — not in local library).
• Annex 13 (Aircraft Accident and Incident Investigation) — GADSS data use in investigations; GADSS-AG provisions in Amendment (applicable 26 November 2026) (authoritative source — not in local library).

ICAO documentation and guidance#

• Doc 10165 (Manual on Global Aeronautical Distress and Safety System), First Edition, 2025 — authoritative implementation guidance for all GADSS functions; supersedes Circular 347 and Doc 10054; covers aircraft tracking, ADT, post-flight localization, FRDR, and GADSS information management.
• Doc 10150 (Functional Specifications for the Location of an Aircraft in Distress Repository — LADR) — minimum dataset, access rules, SWIM interface, and privacy protections for the LADR (authoritative source — not in local library).
• Doc 10054 (Manual on Location of Aircraft in Distress and Flight Recorder Data Recovery) — superseded by Doc 10165 (2025); contains legacy guidance on ADT and FRDR referenced in earlier SARPs.
• Circular 347-AN/205 (Aircraft Tracking Implementation Guidelines) — implementation guidance for normal tracking SARPs (applicable 8 November 2018); superseded as overall GADSS guidance by Doc 10165 (2025).
• PANS-OPS (Doc 8168), Volume III, Section 10 — operational procedures for ATSUs monitoring aircraft tracking data and making distress position information available; referenced in Annex 6 Notes at §3.5.3 and §6.18.3 (authoritative source — not in local library).

ICAO policy and conference records#

• Doc 10041 (ICAO Council 202nd Session, 2014, C-DEC 202/16) — Council discussions on MH370 disappearance and GADSS development; near-term tracking strategy; COSPAS-SARSAT ELT work.
• Doc 10065 (ICAO Council adoption of Amendment 39 record) — Council deliberations on normal aircraft tracking; Australia's reservation on staged SARPs.
• Doc 10073 (ICAO Council record, 2015) — Council review of ADT distress tracking SARPs; ANC role in developing GADSS provisions.
• Doc 10192 (ICAO Council session record) — Council decision on Amendment 48 deferring ADT applicability to 1 January 2025; COVID-19 supply-chain rationale.
• Doc 10222 (42nd ICAO Assembly Working Papers and Decisions) — Assembly note on ELT(DT) inadvertent activations and coordinated mitigation; agenda item A42-WP/331.
• Doc 10115 (AN-Conf/13 Report, 2018) — Conference discussion on GADSS improving SAR effectiveness; call for additional ICAO provisions for distress tracking information exchange.
• Doc 10046 (ICAO Assembly Resolution / ICAO safety outcomes) — §1847c: prompt implementation of GADSS normal tracking (every 15 minutes) and distress tracking (every minute).

EUROCAE standards#

• EUROCAE ED-237 (Minimum Aviation System Performance Specification for Criteria to Detect In-Flight Aircraft Distress Events to Trigger Transmission of Flight Information) — referenced in Annex 6, Part I, Appendix 9, Note 2; provides triggering criteria for ADT systems (authoritative source — not in local library).

External and institutional references#

• https://www.icao.int/safety/OPS/OPS-Section/Pages/Understanding-GADSS.aspx - ICAO GADSS overview page; official entry point
• https://www.icao.int/safety/OPS/OPS-Section/Pages/Location-aircraft-in-distress.aspx - ICAO page on location of aircraft in distress; links to LADR and GADSS-AG
• https://www.cospas-sarsat.int/ - COSPAS-SARSAT programme; satellite infrastructure for ELT(DT) alerts in GADSS
• https://store.icao.int/en/manual-on-global-aeronautical-distress-and-safety-system-doc-10165 - Doc 10165 First Edition (2025) on ICAO store