37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1176380 |
Time | |
Date | 201405 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | TEB.Airport |
State Reference | NJ |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Challenger Jet Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | SID RUDDY4 |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 92.8 Flight Crew Total 8000 Flight Crew Type 96 |
Person 2 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 150 Flight Crew Total 6500 Flight Crew Type 100 |
Events | |
Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
[We were] departing teb runway 24 via the RUUDY4 departure on the initial climb and course. We were set up for; and had briefed that we would engage the autopilot to fly the RNAV SID. After takeoff and gear up we engaged the autopilot with navigation and VNAV selected and turned the autothrottle system on. At the first fix where we were to make a 20 degree turn to the right to intercept the 260 degree course to the next intersection (wentz) at 1;500 ft. It was at the unnamed point where we were to turn from 240 to 260 that we recognized that the autopilot was not initiating the turn or level off. The pilot flying disconnected the autopilot and immediately turned the airplane toward the wentz intersection and arrested the climb. At that point we were above 1;500 and near 2;000 ft so he continued to nose over and bank the airplane to get back down to 1;500 ft. At this point ATC was talking to us and giving us instructions to descend to 1;500 [ft] and take up a heading of 280 which we did as promptly and safely as possible.the contributing factors leading up to the event was primarily the failure of both of us to recognize that the FMS was not selected to the right mode of navigation. Thus the autopilot did not fly the prescribed and expected course. The deviation from the departure profile; though caught by both of us relatively quickly; was not easily remedied due to the nature of that section of the departure and the performance of the airplane. To correct the causation of this situation the crew will need to adopt a departure briefing that includes the navigation mode of the FMS.
Original NASA ASRS Text
Title: A CL60 departed on the TEB Runway 24 RUUDY 4 SID but because an incorrect FMS Mode as selected the aircraft did not level at 1;500 FT nor turn to the 260 heading. The pilot flying was correcting as ATC called with a track and descent clearance.
Narrative: [We were] departing TEB Runway 24 via the RUUDY4 departure on the initial climb and course. We were set up for; and had briefed that we would engage the autopilot to fly the RNAV SID. After takeoff and gear up we engaged the autopilot with NAV and VNAV selected and turned the Autothrottle System ON. At the first fix where we were to make a 20 degree turn to the right to intercept the 260 degree course to the next intersection (WENTZ) at 1;500 FT. It was at the unnamed point where we were to turn from 240 to 260 that we recognized that the autopilot was not initiating the turn or level off. The pilot flying disconnected the autopilot and immediately turned the airplane toward the WENTZ Intersection and arrested the climb. At that point we were above 1;500 and near 2;000 FT so he continued to nose over and bank the airplane to get back down to 1;500 FT. At this point ATC was talking to us and giving us instructions to descend to 1;500 [FT] and take up a heading of 280 which we did as promptly and safely as possible.The contributing factors leading up to the event was primarily the failure of both of us to recognize that the FMS was not selected to the right mode of navigation. Thus the autopilot did not fly the prescribed and expected course. The deviation from the departure profile; though caught by both of us relatively quickly; was not easily remedied due to the nature of that section of the departure and the performance of the airplane. To correct the causation of this situation the crew will need to adopt a departure briefing that includes the Navigation Mode of the FMS.
Data retrieved from NASA's ASRS site 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.