![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 912729 |
| Time | |
| Date | 201010 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | TEB.Airport |
| State Reference | NJ |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Embraer Phenom 100 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Route In Use | SID RUDDY TWO |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | AHRS/ND |
| Person 1 | |
| Function | Captain Single Pilot |
| Qualification | Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine |
| Experience | Flight Crew Last 90 Days 120 Flight Crew Total 4000 Flight Crew Type 50 |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Upon reaching runway 24; AHRS2 (altitude heading reference system) had failed for 2 seconds; then corrected itself. After departure; I flew the 240 degree heading leg of the ruddy two departure. I turned to wentz on a heading of 260 and engaged the autopilot at approximately 500 ft AGL. There was a distraction in the cabin; (spilled drink and small commotion) and then the autopilot failed; and I got a indication of a AHRS2 failure. During the autopilot failure; I did not hear the altitude alerter. Three seconds later; I called approach and checked on with '[flight number] 2;000 climbing' after looking down at my altimeter. The controller immediately asked what I was climbing to and I realized that I was high; I replied back with 'descending 2;000' and the controller asked what altitude I was assigned in a stern voice; I replied 2;000; and he asked again; I was honestly confused on which segment of the departure I was on. I was pulling the power back at this time; hand flying and attempting to re-establish situation awareness. I realized that I hadn't yet reached tasca and that I had not only missed the 1;500 ft level off; but in the confusion; I had climbed to 2;300 ft MSL. The ahrs again correct itself and I was able to re-engage the autopilot/yaw damper. A second controller then took over for the first controller; and gave me a stern warning about 'blowing a SID' and the flight continued on with no further issue.
Original NASA ASRS Text
Title: A single pilot corporate jet failed to comply with the altitude restrictions on the RUUDY SID from TEB. An autopilot disconnect due to a failed AHRS system at a critical point contributed to the reporter's loss of situational awareness.
Narrative: Upon reaching Runway 24; AHRS2 (Altitude Heading Reference System) had failed for 2 seconds; then corrected itself. After departure; I flew the 240 degree heading leg of the Ruddy Two departure. I turned to WENTZ on a heading of 260 and engaged the autopilot at approximately 500 FT AGL. There was a distraction in the cabin; (spilled drink and small commotion) and then the autopilot failed; and I got a indication of a AHRS2 failure. During the autopilot failure; I did not hear the altitude alerter. Three seconds later; I called Approach and checked on with '[Flight number] 2;000 climbing' after looking down at my altimeter. The Controller immediately asked what I was climbing to and I realized that I was high; I replied back with 'descending 2;000' and the Controller asked what altitude I was assigned in a stern voice; I replied 2;000; and he asked again; I was honestly confused on which segment of the departure I was on. I was pulling the power back at this time; hand flying and attempting to re-establish situation awareness. I realized that I hadn't yet reached TASCA and that I had not only missed the 1;500 FT level off; but in the confusion; I had climbed to 2;300 FT MSL. The AHRS again correct itself and I was able to re-engage the autopilot/yaw damper. A second Controller then took over for the first Controller; and gave me a stern warning about 'blowing a SID' and the flight continued on with no further issue.
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.