37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 959037 |
Time | |
Date | 201107 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Embraer Legacy 450/500 |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Route In Use | Vectors |
Flight Plan | IFR |
Component | |
Aircraft Component | Hydraulic Main System |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 125 Flight Crew Total 5000 Flight Crew Type 400 |
Events | |
Anomaly | Aircraft Equipment Problem Critical Deviation - Procedural FAR |
Narrative:
After an emergency landing due to a complete hydraulic failure; I was escorted from the aircraft before noting the malfunction in the aircraft discrepancy log. Prior to the landing; I had been in direct contact with company maintenance personnel and they were informed of the nature of the malfunction. I also had a fairly strong level of certainty another crew wouldn't attempt to fly the aircraft before the malfunction was repaired; mostly because the aircraft was parked on a taxiway with its right main tire blown out. I was escorted from the aircraft to the FBO by airport authority personnel. Once there; I was instructed to duty off and leave the premises by dispatch. I didn't have any other contact with the aircraft after that. I made attempts to call my supervisors to inform them of the emergency situation. I received one email several hours later. If crews at my company had a series of clearly defined steps to follow in aftermath of an emergency; this oversight could have been prevented. In all of the confusion and rush following the event; I simply forgot to note the malfunction in the aircraft log; and no one in my company; including maintenance; noticed this until 6 days later.
Original NASA ASRS Text
Title: EMB 505 Captain reports an emergency landing due to hydraulic failure which results in a blown main tire. In the aftermath the aircraft log is completely overlooked and no discrepancy is entered. This oversight is not detected until six days later.
Narrative: After an emergency landing due to a complete hydraulic failure; I was escorted from the aircraft before noting the malfunction in the aircraft discrepancy log. Prior to the landing; I had been in direct contact with company maintenance personnel and they were informed of the nature of the malfunction. I also had a fairly strong level of certainty another crew wouldn't attempt to fly the aircraft before the malfunction was repaired; mostly because the aircraft was parked on a taxiway with its right main tire blown out. I was escorted from the aircraft to the FBO by Airport Authority Personnel. Once there; I was instructed to duty off and leave the premises by Dispatch. I didn't have any other contact with the aircraft after that. I made attempts to call my supervisors to inform them of the emergency situation. I received one email several hours later. If crews at my company had a series of clearly defined steps to follow in aftermath of an emergency; this oversight could have been prevented. In all of the confusion and rush following the event; I simply forgot to note the malfunction in the aircraft log; and no one in my company; including maintenance; noticed this until 6 days later.
Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.