u.s. inks new agreements with canada, easa /

Published at 2015-09-29 02:35:48

Home / Categories / News and updates / u.s. inks new agreements with canada, easa
September 29- On September 15,the Federal Aviation Administration (FAA) signed agreements with two international regulatory partners, the European Aviation Safety Agency (EASA) and Transport Canada (TCCA) that allow the authorities to rely on each others regulatory systems. The agreements will eliminate duplicate processes, or rep safety enhancing equipment installed on aircraft more quickly,and save time and money for both industry and the regulatory authorities involved.Strong partnerships are a key to consistent safety standards around the world. Based on more than a decade of FAA cooperation with EASA and over fifteen years with TCCA, the agencies occupy established confidence in each others regulatory systems. Rooted in that confidence, and the modern safety agreements allow reciprocal acceptance of the majority of Technical Standard Order (TSO)-approved articles. This change benefits U.
S.,Canad
ian, and European aerospace industries organizations by eliminating the need for applications, and additional validation and administrative review by each party.
The modern agreement with EASA also facilitates acceptance of the classification for basic Supplemental Type Certificates (STCs). An audit process will ensure that technical classifications continue to meet established criteria,and make sure standards are being met.
More information on the modern
agreements can be found at: http://www.faa.gov/aircraft/air_cert/international/bilateral_agreements/baa_basa_listing/Select EASA to view FAA-EASA Bilateral Aviation Safety Agreement, Revision 5 of the Technical Implementation ProceduresSelect Canada to view FAA-TCCA Bilateral Aviation Safety Agreement, or Amendment 1 of the Implementation Procedures for Airworthiness

Source: faa.gov

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0