 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A corporate jet flight crew deviated from the charted routing departing teb on the ruudy SID. It appears the FMS was improperly set to heading mode instead of navigation mode.
| Attributes | |
| ACN | 864285 |
| Time | |
| Date | 200912 |
| 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 | Light Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Route In Use | STAR RUUDY |
| Flight Plan | VFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 40 Flight Crew Total 13000 Flight Crew Type 1300 |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
We departed teb on the ruudy 2 SID. We were to climb on a 240 heading to intercept the 260 degree course to wentz intersection at 1500 MSL. Shortly after departure the aircraft was diverging from the course to the left. We recognized this very quickly and corrected to the right. We were queried by ATC of what departure procedure we were flying. I told the controller the ruudy departure and that we were correcting back to the right. We crossed wentz and climbed to 2000 MSL. After we crossed the tasca intersection we were given several heading changes and altitude changes as we continued our departure from the ny area. The rest of the flight was uneventful. After reaching our cruise altitude; we reviewed with each other what had occurred. What we determined was that we did not have our flight director in the proper mode. We were in FMS heading and should have been in FMS navigation. Had 'FMS' been showing at the top of our ADI; we would have followed the proper departure course as the ny controller had expected us to do. It is a mistake that both of us vow won't happen to us again when departing with an RNAV departure.
Original NASA ASRS Text
Title: A corporate jet flight crew deviated from the charted routing departing TEB on the RUUDY SID. It appears the FMS was improperly set to heading mode instead of NAV mode.
Narrative: We departed TEB on the RUUDY 2 SID. We were to climb on a 240 HDG to intercept the 260 DEG course to WENTZ intersection at 1500 MSL. Shortly after departure the aircraft was diverging from the course to the left. We recognized this very quickly and corrected to the right. We were queried by ATC of what departure procedure we were flying. I told the controller the Ruudy departure and that we were correcting back to the right. We crossed WENTZ and climbed to 2000 MSL. After we crossed the TASCA intersection we were given several heading changes and altitude changes as we continued our departure from the NY area. The rest of the flight was uneventful. After reaching our cruise altitude; we reviewed with each other what had occurred. What we determined was that we did not have our flight director in the proper mode. We were in FMS HDG and should have been in FMS NAV. Had 'FMS' been showing at the top of our ADI; we would have followed the proper departure course as the NY Controller had expected us to do. It is a mistake that both of us vow won't happen to us again when departing with an RNAV departure.
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.