37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 950690 |
Time | |
Date | 201105 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | TEB.Airport |
State Reference | NJ |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citation II S2/Bravo (C550) |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Commercial Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Multiengine Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 4500 Flight Crew Type 550 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
The reason for this report is because of an inadvertent altitude deviation on the RUUDY2 departure off of runway 24 from teb airport. I briefed the instrument departure to my co-pilot; with plenty of time available; prior to departure. The weather was IFR at teb. During the departure briefing to the co-pilot we discussed the RUUDY2 SID and the noise abatement procedures for runway 24. The takeoff was normal and unremarkable. Upon reaching 600 ft MSL the tis system sounded and stated 'traffic; traffic.' both pilots diverted attention to the tis system to see if we had a problem that we needed to avoid. The system showed an aircraft at the same altitude at our location. I believe the system malfunctioned causing the crew to divert our attention briefly. Upon looking back at the flight director; approximately 1;100 ft MSL; our aircraft was still climbing normally; with no other traffic advisories from the tis. The autopilot was off; however the flight director was engaged. The aircraft was being flown with reference to the flight director for the departure. Upon review; all correct information was inserted into the automation to ensure it should display proper information. Altitude selector was set on 1;500 ft MSL for the SID's first altitude requirement. The flight director failed to show a level off at the 1;500 ft MSL; however the asel [altitude select] did capture in the flight mode annunciator. I noticed the deviation at 1;700 ft MSL and was able to stop the ascent at 1;800 MSL and immediately proceeded back to 1;500 ft MSL. The air traffic controller on new york departure advised us to maintain 1;500 ft MSL. The rest of the flight was unremarkable. I believe the traffic alert caused us to divert our full attention from the altitude that was quickly approaching due to the quick climb out for noise abatement. Also; the automation was slow to respond causing the 300 ft inadvertent altitude deviation. To my knowledge we did not create a conflict for any other aircraft.
Original NASA ASRS Text
Title: CE550 Captain reports an altitude deviation during the RUUDY2 departure from TEB. The crew is distracted by a false TIS warning and the flight director is slow to capture the set altitude; resulting in an overshoot.
Narrative: The reason for this report is because of an inadvertent altitude deviation on the RUUDY2 departure off of Runway 24 from TEB airport. I briefed the instrument departure to my co-pilot; with plenty of time available; prior to departure. The weather was IFR at TEB. During the departure briefing to the co-pilot we discussed the RUUDY2 SID and the noise abatement procedures for Runway 24. The takeoff was normal and unremarkable. Upon reaching 600 FT MSL the TIS system sounded and stated 'TRAFFIC; TRAFFIC.' Both pilots diverted attention to the TIS system to see if we had a problem that we needed to avoid. The system showed an aircraft at the same altitude at our location. I believe the system malfunctioned causing the crew to divert our attention briefly. Upon looking back at the flight director; approximately 1;100 FT MSL; our aircraft was still climbing normally; with no other traffic advisories from the TIS. The autopilot was off; however the flight director was engaged. The aircraft was being flown with reference to the flight director for the departure. Upon review; all correct information was inserted into the automation to ensure it should display proper information. Altitude selector was set on 1;500 FT MSL for the SID's first altitude requirement. The flight director failed to show a level off at the 1;500 FT MSL; however the ASEL [Altitude select] did capture in the flight mode annunciator. I noticed the deviation at 1;700 FT MSL and was able to stop the ascent at 1;800 MSL and immediately proceeded back to 1;500 FT MSL. The Air Traffic Controller on New York Departure advised us to maintain 1;500 FT MSL. The rest of the flight was unremarkable. I believe the traffic alert caused us to divert our full attention from the altitude that was quickly approaching due to the quick climb out for noise abatement. Also; the automation was slow to respond causing the 300 FT inadvertent altitude deviation. To my knowledge we did not create a conflict for any other aircraft.
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.