Service Difficulty Report (SDR)

The Service Difficulty Report is the mandatory upward-reporting mechanism that routes field-discovered product failures, malfunctions, and defects from the organizations that discover them to the FAA for safety analysis and potential regulatory action. The statutory basis is 14 CFR §21.3, which imposes reporting obligations on holders of type certificates (TCs), supplemental type certificates (STCs), Parts Manufacturer Approvals (PMAs), Technical Standard Order Authorisations (TSOAs), and on FAA-approved production organizations and repair stations. The regulatory trigger under §21.3(c) — the specific list of defects that require reporting — includes: failures, malfunctions, or defects in any aircraft, aircraft engine, propeller, or appliance that has resulted in or may result in fire; structural failure; damage to structure; breakdown of primary structure; or any failure or malfunction that prevents the continued safe flight and landing of the aircraft.

For FAA Part 145 repair stations, the mandatory reporting obligation is restated in §145.221: a certificated repair station that discovers a reportable occurrence under §21.3 must report it in accordance with §21.3. The practical effect is that any A&P mechanic working in an FAA certificated repair station who discovers a qualifying defect during maintenance has an obligation that flows through the station to the FAA. For Part 121 air carriers, §121.703 provides a parallel SDR requirement (Mechanical Reliability Reports) with a 96-hour reporting timeframe for initial reports and a streamlined form structure, essentially duplicating the §21.3 obligation in the air carrier context. Part 135 operators have equivalent reporting requirements under §135.415.

The reporting mechanism is the FAA's online SDR submission system (currently the Aviation Safety Hotline / MedWatch SDR portal at the FAA SDR program site) or paper Form 8010-4. Reports include: the aircraft registration and serial number, the aircraft's total time and cycles, the defect description, the part number and serial number of the defective component, the ATA chapter reference, the circumstances of discovery, and the action taken. The FAA assigns each report an SDR accession number and routes it for analysis.

The SDR database is maintained as part of the FAA Aviation Safety Information Analysis and Sharing (ASIAS) program. ASIAS integrates SDR data with Accident and Incident Data System (AIDS) records, Aviation Safety Hotline data, and other sources to identify systemic safety issues — specific part numbers generating repeated defect reports, ATA chapters with anomalous failure rates, or in-service events that match an emerging failure mode not previously captured in type-design safety analysis. This trend analysis is one of the FAA's primary triggers for initiating Airworthiness Directive rulemaking. An AD addressing a specific part number failure may trace directly to an SDR trend identified years before the AD was issued.

EASA's equivalent system is qualitatively broader in scope. Regulation (EU) 376/2014 on the reporting, analysis, and follow-up of occurrences in civil aviation establishes mandatory occurrence reporting for a defined list of occurrence types (in the Annex to the Regulation), voluntary reporting for lower-severity events, and just-culture protections for reporters. Reports are entered into ECCAIRS (European Co-ordination Center for Accident and Incident Reporting Systems), the EU-wide database managed through the European Aviation Safety Agency's Safety Analysis and Research Department. Where the FAA SDR system focuses specifically on product defects from approved organizations, EU 376/2014 is broader — covering operational occurrences (runway incursions, AIRPROX, TCAS RAs), meteorological hazards, ATC incidents, and maintenance occurrences in a unified reporting framework. The reporting obligation under EU 376/2014 falls on organizations (approved training organizations, maintenance organizations, AOC holders) rather than on individual certificate holders.

The common failure mode in both systems is under-reporting by technicians who either do not recognize the discovered defect as reportable under §21.3(c) or EU 376/2014 Annex, or are concerned that filing a report will trigger an investigation into their own maintenance practice. The just-culture protections under EU 376/2014 Article 16 are explicit: information from occurrence reports must not be used to attribute blame or liability, and Member States may not use SDR or occurrence report data in administrative or judicial proceedings against the reporter except in specified exceptional circumstances. FAA parallel protections are less codified but are present through the Aviation Safety Reporting System (ASRS) immunity provisions, which provide protection for voluntary self-disclosures under AC 00-46.

For flight schools and ATOs with in-house maintenance, SDR reporting is a discipline that requires active management because the link between a technician's field discovery and the FAA's regulatory pipeline is not obvious from the bench level. A Part 145 repair station that services a training fleet and discovers a cracked spar cap, a failed primary control cable, or a corrosion-compromised firewall during a scheduled inspection has an obligation under §21.3 and §145.221 to report within 96 hours of discovery. If the maintenance director is unaware of or does not have a process to identify reportable defects, the report will not be filed — not out of bad intent but out of process gap. This is the same failure mode that EASA NPA 2019-05 identified as a systemic weakness in Part-145 organizations: absence of structured defect review against reporting triggers.

The strategic value of the SDR database for flight school operators is underused. ASIAS's publicly searchable SDR database allows any operator to query all filed SDRs for a specific aircraft type, engine model, or part number — effectively a free fleet intelligence tool. An operator planning to purchase a used Piper PA-28 for training can query the SDR database for all PA-28 structural and engine reports over the past five years and gain industry-wide field experience data that no pre-purchase inspection can replicate.

Aviatize's maintenance execution module includes an SDR reporting trigger workflow. When a work order is closed and the defect description is finalized, the system presents a mandatory check: does this defect fall within the §21.3(c) or EU 376/2014 Annex reporting categories? If yes, the platform opens an SDR/occurrence report draft, pre-populated with the aircraft data, ATA chapter, part number, serial number, and defect description from the work order, and queues it for submission review by the maintenance director. The submission deadline (96 hours for FAA, or the applicable EU 376/2014 timeframe) is tracked against the discovery timestamp in the work order.

For organizations seeking to use SDR data proactively, the compliance and auditing module enables import of FAA ASIAS SDR query results for their fleet types, presenting the historical industry-wide failure data alongside the organization's own maintenance history. When a work order is being written for a component that has a history of SDR-reported defects in the ASIAS database, the system can surface the relevant SDR summary — giving the certifying staff member the benefit of industry-wide field experience during task planning rather than after the work is complete.