37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 895184 |
Time | |
Date | 201006 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | TEB.Tower |
State Reference | NJ |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citationjet (C525/C526) - CJ I / II / III / IV |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | SID RUUDY 2 |
Flight Plan | IFR |
Component | |
Aircraft Component | Flight Director |
Person 1 | |
Function | Single Pilot Pilot Flying |
Qualification | Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 90 Flight Crew Total 16000 Flight Crew Type 3000 |
Events | |
Anomaly | Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Departed teb on the ruudy 2; thought I had engaged the VNAV flight director; and although the flight director was working properly; I did not have the VNAV engaged and as I went through the altitude; I didn't catch it quick enough to not upset some passengers in the cabin with a nose over. I did pull the power back and as I started to direct the aircraft back down to the proper altitude; the controller came on to remind me that I flew through the charted altitude. I've flown out of teb many times and I've flown the departure in the simulator at flight safety and this should not have happened except for my neglect. I did notice the restricted climb altitude in the FMS and on the pfd; but the VNAV mode was not engaged. In the future; I will be double checking my navigation modes set for the flight director.a contributing factor may have been the delay for takeoff clearance and not rechecking that all proper modes were set before the takeoff roll.
Original NASA ASRS Text
Title: CE525 Captain reports climbing through depicted altitude during the RUUDY 2 departure from TEB. VNAV function was thought to be engaged prior to departure but was not.
Narrative: Departed TEB on the RUUDY 2; thought I had engaged the VNAV flight director; and although the flight director was working properly; I did not have the VNAV engaged and as I went through the altitude; I didn't catch it quick enough to not upset some passengers in the cabin with a nose over. I did pull the power back and as I started to direct the aircraft back down to the proper altitude; the Controller came on to remind me that I flew through the charted altitude. I've flown out of TEB many times and I've flown the departure in the simulator at Flight Safety and this should not have happened except for my neglect. I did notice the restricted climb altitude in the FMS and on the PFD; but the VNAV mode was not engaged. In the future; I will be double checking my NAV modes set for the flight director.A contributing factor may have been the delay for takeoff clearance and not rechecking that all proper modes were set before the takeoff roll.
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.