ASN Wikibase Occurrence # 141735
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information
Narrative:According to the pilot, he performed a brake check and used the brakes numerous times while taxiing to the run-up area; however, as he approached the run-up area, the brakes failed, and the airplane continued to roll forward. He decided to steer the airplane off the taxiway surface and not risk an excursion onto the active runway. The airplane veered off the paved surface onto unprepared desert terrain, and the airplane continued to accelerate. The pilot attempted to shut down the engine with the ignition switch, but was unable to. He said that normal engine shut down is accomplished using two magneto switches on the instrument panel and not the ignition switch. The airplane then struck a boundary fence.
|Date:||Friday 6 January 2012|
Aerospool WT-9 Dynamic
|Total airframe hrs:||70 hours|
|Fatalities:||Fatalities: 0 / Occupants: 1|
|Aircraft damage:|| Substantial|
|Location:||Glendale Municipal Airport - KGEU, AZ -
United States of America
|Departure airport:||Glendale, AZ (KGEU)|
|Destination airport:||Glendale, AZ (KGEU)|
|Investigating agency: ||NTSB|
|Confidence Rating:|| Accident investigation report completed and information captured|
Postaccident examination revealed that the left wheel brake assembly was damaged by impact forces consistent with the airplane’s collision with the fence. The examination of the brake system for fluid leaks and functionality did not disclose any evidence of a preexisting mechanical malfunction that would have precluded normal operation. It is likely that, if the pilot had shut down the engine before the airplane departed the taxiway surface, he would have been able to stop in time to avoid colliding with the airport boundary fence.
Probable Cause: The pilot did not shut down the engine upon recognizing a brake malfunction. Contributing to the accident was the airplane's brake malfunction for undetermined reasons.
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=247DY
| || |
|Investigating agency: ||NTSB |
|Report number: ||WPR12LA074 |
|Status: ||Investigation completed|
|Duration: ||2 months|
|Download report: || Final report|
||Updated [Aircraft type, Registration, Cn, Operator, Source, Narrative]|
||Updated [Time, Aircraft type, Departure airport, Source, Narrative, Plane category, ]|
||ASN Update Bot
||Updated [Time, Damage, Category, Investigating agency]|
||ASN Update Bot
||Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative, Plane category]|
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2023 Flight Safety Foundation