NTSB · Safety Recommendation
Safety Recommendation A-04-040
Recommendation
TO THE NATIONAL FIRE PROTECTION ASSOCIATION AND THE INTERNATIONAL ASSOCIATION OF FIRE CHIEFS: In cooperation with Ballistic Recovery Systems, Inc., and Cirrus Design, develop and distribute a safety bulletin to your membership to raise awareness among non-airport fire/rescue organizations crews regarding the hazards associated with ballistic parachute devices during general aviation rescue and firefighting operations.
Safety Issue and Context
On June 16, 2001, about 1438 central daylight time, a Cirrus Design SR22, equipped with an undeployed ballistic parachute system, was destroyed while landing on runway 20 at the Springfield-Branson Regional Airport (SGF), in Springfield, Missouri. The airplane touched down 1,000 to 1,500 feet beyond the approach end of the runway, bounced several times, and veered off the left side of the runway. The airplane then crossed a sod area, a taxiway, and another sod area before impacting a disabled aircraft used for airport rescue and firefighting (ARFF) training.
The private pilot and the passenger in the rear seat received minor injuries; the passenger in the left front seat was seriously injured. Visual meteorological conditions prevailed at the time of the accident. The personal flight was operated under the provisions of 14 Code of Federal Regulations (CFR) Part 91.
Response History
January 31, 2005 · NTSB Correspondence · National Fire Protection Association
The Safety Board notes that the NFPA published two articles in summer and fall 2003 concerning the hazards associated with ballistic parachute devices during rescue and firefighting operations. The articles in ARFF News and the NFPA Online Journal provided the information to all airport rescue and firefighting (ARFF) working group and NFPA members. The NFPA also reported that Safety Recommendation A-04-41 is included in a proposal for the next revision of NFPA 402, Guide for Aircraft Rescue and Fire-Fighting Operations. The revision cycle for NFPA 402 is scheduled to commence no later than early spring 2006.
The Safety Board appreciates the NFPA's proaction in publishing the information last year once it became aware of the ballistic parachute device hazard. The early action not only informed non-airport fire/rescue personnel but also ARFF personnel. Accordingly, Safety Recommendation A-04-40 is classified "Closed--Reconsidered."
With regard to the revision to NFPA 402, including recommendation A-04-41 in the next revision cycle is a positive and logical step; however, it does not fully address the intent of the recommendation. The focus of this recommendation is to update training standards for recognizing and disabling ballistic parachute systems for all firefighting organizations, including fire stations other than those located on an airfield, specifically fire stations located near general aviation airfields that may potentially encounter the BRS device. The scope of NFPA 402 only includes ARFF operations.
The Safety Board encourages including this recommendation in the next revision cycle for NFPA 402, but would like to have the update of these training standards apply to all of your members.
Enclosed is a copy of the Federal Aviation Administration's (FAA's) response to the Safety Board's April 29, 2004, letter. The FAA states that it is developing training guidelines for ARFF personnel to assist in recognizing and disabling aircraft ballistic parachute systems. The agency is also working with the American Society for Testing and Materials (ASTM) to refine the Consensus Standard for ballistic recovery systems and to develop warning labels and exterior markings for any aircraft equipped with such a system. The Board urges NFPA to ensure that its technical committee coordinates with these efforts to encourage uniform guidance.
Pending the revision of NFPA 402 to include training standards on the recognition and disabling of ballistic parachute systems and development of a similar plan to address all members of NFPA, Safety Recommendation A-04-41 is classified
July 9, 2004 · Recipient Response · National Fire Protection Association
Letter Mail Controlled 7/16/2004 10:50:30 AM MC# 2040418 NFPA staff first became aware of the concerns of NTSB and others on this topic at least a year ago, and immediately took steps consistent with the spirit and intent of NTSB item # A-04-40. Specifically, an article authored by Mr. Mike Busch, Director of Air Safety at Cirrus Design, was published as the front page story in the July/August 2003 edition of ARFF News (see attached). ARFF News is a joint publication of the ARFF Working Group and NFPA, and it is published bimonthly to inform the membership of the ARFF Working Group and others about developments in aviation fire protection and ARFF Working Group activities.
Soon after this article was published in ARFF News, it was re-published in the October 2003 edition of NFPA Online Journal, which is the NFPA website publication available to all NFPA members (copy attached). This continues to be posted and available at the following Internet URL: http://www.nfpa.org/JournalArchive/Archives/archives.asp.
To further maintain direct consideration of this issue, and consistent with the intent of NTSB item # A-04-41, we have recently logged this particular NTSB recommendation in as a proposal for the upcoming revision of NFPA 402, Guide for Aircraft Rescue and Fire-Fighting Operations. NFPA 402 is in the A2007 revision cycle, and the Technical Committee on Aircraft Rescue and Fire Fighting is planning to address this overall subject at their ROP meeting currently scheduled no later than early spring 2006. Soon thereafter the action of the Technical Committee on this proposal will be published in the NFPA "A2007 ROP", and a copy will be automatically sent to you at that time.
In closing, the above information addresses the latest status of the two NTSB recommendations directed toward NFPA in your letter dated 29 April 2004. I trust that this adequately addresses the above referenced items at this time. We will be pleased to provide you with any additional updates in the future as needed.