37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1065464 |
Time | |
Date | 201202 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | TEB.Airport |
State Reference | NJ |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citation II S2/Bravo (C550) |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | SID RUUDY FOUR |
Flight Plan | IFR |
Component | |
Aircraft Component | Altitude Hold/Capture |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 150 Flight Crew Total 1100 Flight Crew Type 300 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
The captain and I took off runway 24 at teb via the ruudy four departure. On departure; we were having trouble with our FMS and getting our flight director to sync up. Our altitude was set to level off at 1;500 ft. At 500 ft I called the '500 ft for 1;500 ft' callout and verified the 'alt select' button was armed. Shortly after; I put my head down to verify the FMS was flying the correct course to intercept the 260 degree course to wentz. While working the FMS; we received a call from ATC to verify our altitude. This was the point that I had realized the altitude did not capture upon reaching 1;500 ft. We deviated above our assigned altitude approximately 600-700 ft prior to immediately taking corrective action (reduced power and pitched down) to return the 1;500 ft. The captain was under the impression he had engaged the autopilot and the altitude select was armed; however; when attempting to get the flight director to sync up; it inadvertently disengaged the 'alt select arm' button. Due to our flight director issue; I took my eyes of the instruments to attend the FMS and verify we were flying the correct departure routing. In the future; I will back up the flying pilot and personally watch the instruments to ensure we are leveling of at the assigned altitudes.
Original NASA ASRS Text
Title: A CE550 Flight Director failed to sync with the FMS after departing on the TEB Runway 24 RUUDY FOUR and so a distracted crew did not detect the 1;500 FT altitude overshoot until ATC requested an altitude check.
Narrative: The Captain and I took off Runway 24 at TEB via the RUUDY FOUR Departure. On departure; we were having trouble with our FMS and getting our flight director to sync up. Our altitude was set to level off at 1;500 FT. At 500 FT I called the '500 FT for 1;500 FT' callout and verified the 'Alt Select' button was Armed. Shortly after; I put my head down to verify the FMS was flying the correct course to intercept the 260 degree course to WENTZ. While working the FMS; we received a call from ATC to verify our altitude. This was the point that I had realized the altitude did not capture upon reaching 1;500 FT. We deviated above our assigned altitude approximately 600-700 FT prior to immediately taking corrective action (reduced power and pitched down) to return the 1;500 FT. The Captain was under the impression he had engaged the autopilot and the altitude select was armed; however; when attempting to get the flight director to sync up; it inadvertently disengaged the 'alt select arm' button. Due to our flight director issue; I took my eyes of the instruments to attend the FMS and verify we were flying the correct departure routing. In the future; I will back up the flying pilot and personally watch the instruments to ensure we are leveling of at the assigned altitudes.
Data retrieved from NASA's ASRS site as of July 2013 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.