The Service Difficulty Reporting System (SDRS) is undergoing upgrades to enhance system stability and expand functionality. These improvements include the introduction of required fields, strengthened data validation, updated processes for supplemental records, refinements to batch file handling, and the creation of a new oversight role.
These changes are targeted for deployment on Jan 22, 2027.
We encourage all to review the artifacts provided in the table which provide more details on the upcoming changes: The SDRS user manual, Required Fields Map, Batch Submission Instructions, and Look-up Tables zip file.
To ensure a seamless transition, some preparation might be necessary - some of your internal systems may require modification, specifically those systems and processes that produce the batch files you submit. While the basic batch file structure is not changing, Version 2.14 introduces automated, real-time data validation and distinct workflows for new versus supplemental records, and an increased level of data precision.
To support a seamless transition, we can help with testing of batch files. Please contact us at 9-AMC-SDR-ProgMgr@faa.gov for assistance.
1. Standardized Formatting and Table Values
Formats: Fields, such as the Difficulty Date, need to be formatted exactly as MM/DD/YYYY. Control Numbers must follow a set formula: the Operator Designator + the Date of Submission (formatted as YYYYMMDD) + 5 chosen digits.
Several fields—including SDR Type, JASC Code, Stage of Operation, and How Discovered—must be selected directly from the approved system tables rather than using free-text entries. For example, the Aircraft Make must match the standard table values (such as "EMB" rather than "EMBRA") to process successfully.
2. Context-Driven Logic
The system applies intelligent, context-driven logic where certain fields automatically become necessary based on other data provided. For example:
JASC Code Dependencies: Engine Make and Model are required if the JASC Code falls between 7000 and 9000. Similarly, Propeller Make and Model are required for JASC Codes between 6100 and 6199.
Submitter Type Exemptions: Aircraft Make and Model are required unless the submitter is a Part 145 Repair Station. The Operator Designator is also required, unless the submitter is a Non-Cert International organization or is filing a General Aviation report.
3. Field Interdependencies
Providing certain optional information will prompt the system to require corresponding data to ensure completeness. For example:
If a Part Time Since or Component Time Since value is entered, the corresponding Since Code (O for Overhaul, R for Repair, or I for Inspection) must also be provided.
If a Component Part Number is entered, either the Component Make or Component Name becomes required.
4. Core Fields and File Structure
File Layout: Batch submissions remain as pipe-delimited files containing exactly 77 values, using blank positions ( || ) to mark non-applicable data.
Essential Data: Core fields like the Submitter Designator, Submitter Type Code, JASC Code (0000 is allowed if the exact code is unknown), and the final Discrepancy narrative must be populated.
Data Limits: Character limits are enforced across the file, such as the Discrepancy field which accommodates up to 1500 characters.