FAA Issues Airworthiness Directive for Airbus Helicopters

The U.S. Federal Aviation Administration has issued a new airworthiness directive for specific Airbus Helicopters models. The action underscores ongoing regulatory focus on rigorous verification and traceability in both hardware and software. While not introducing new language for DO-178C or ARP4754A, the directive signals continued scrutiny of embedded software and systems engineering practices as avionics grow more complex.

- The specific directive for the Airbus Helicopters Model SA330J addresses a hardware issue where the resistance value of the engine fire extinguisher's pyrotechnic cartridge was found to be out of tolerance, requiring repetitive inspections. - Broader regulatory scrutiny on software is exemplified by a recent EASA emergency airworthiness directive for the Airbus A320 family, which mandated a software fix after a malfunction in an Elevator Aileron Computer (ELAC) led to an uncommanded pitch-down event. The cause was linked to intense solar radiation potentially corrupting critical flight control data. - The certification of new-generation helicopters, such as the Airbus H160 with its Helionix avionics suite, highlights the challenges posed by increasing complexity. The H160's FAA certification process was extended due to novel design features that fell outside the existing parameters of FAR Part 29 regulations. - Adherence to DO-178C is critical for flight-control software and systems with the highest Design Assurance Level (DAL A), where a failure could be catastrophic. This standard mandates a verifiable and traceable link from system-level requirements (defined under ARP4754A) down to the software architecture and source code. - A core challenge in meeting these standards is maintaining end-to-end traceability, proving that every software requirement links to a system safety objective and is verified by a specific test. Any break in this traceability chain can invalidate the airworthiness argument, regardless of the volume of testing performed. - The process of qualifying software development and verification tools, as outlined in the DO-330 supplement to DO-178C, is also under scrutiny. If a tool is used to automate or verify critical aspects of a DAL A system, the tool itself must be qualified to ensure it does not introduce errors.

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.