37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 873763 |
Time | |
Date | 201002 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | TEB.Airport |
State Reference | NJ |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Learjet 40 |
Operating Under FAR Part | Part 135 |
Flight Phase | Initial Climb Climb |
Route In Use | SID RUUDY |
Flight Plan | IFR |
Component | |
Aircraft Component | Flight Director |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Upon departing teterboro we commenced the assigned ruudy 2 departure procedure. The FMS was set up for the departure off runway 24 in FMS/navigation mode for the RNAV departure procedure. The departure called for the runway heading to intercept the 260 course to wentz; the first intersection on the departure and to cross wentz at 1;500 ft. As we climbed out on the runway heading (I was flying as sic from the right seat) I noted the FMS course needle turned to intercept the 260 course to wentz. However the flight director continued a command straight ahead. I noted it and commented to the captain who simply confirmed we were beginning to cross the course on the supplemental mfd display. Simultaneously; I turned to re-intercept the course needle to intercept and fly to wentz. While we did overfly the course by the time I realized what was happening the needle did not deviate more than 3/4 of a dot and I did level at 1;500 ft cross what was slightly abeam of wentz. I just then followed the course needle manually to remain on the departure. New york departure said nothing except to give us a climb to 8;000 ft. The captain noted that on one previous occasion; when there was a moderate or greater crosswind and the commanding flight director was on the right side; the flight director did not capture the course on an approach. However; it only happened on one day before I arrived on the airplane and he noted it never re-occurred. Therefore; no comment was made of that irregularity. When we arrived at our destination; the current captain listed the irregularity as a discrepancy and reported it to maintenance. When we arrived at the airplane on the following day; we noted that maintenance had 'ops checked' the autopilot with no discrepancies noted and returned the aircraft to service. We did fly the aircraft on the next leg and the automation performed flawlessly.
Original NASA ASRS Text
Title: A LR40 pilot departed TEB on the RUUDY2 RNAV and noted that the aircraft's Flight Director did not capture the 260 degree course to WENTZ. The reporter flew the procedure manually. Maintenance replied to the discrepancy and reported 'OPS CHECK.'
Narrative: Upon departing Teterboro we commenced the assigned Ruudy 2 Departure procedure. The FMS was set up for the departure off Runway 24 in FMS/NAV mode for the RNAV departure procedure. The departure called for the runway heading to intercept the 260 course to Wentz; the first intersection on the departure and to cross Wentz at 1;500 FT. As we climbed out on the runway heading (I was flying as SIC from the right seat) I noted the FMS course needle turned to intercept the 260 course to Wentz. However the flight director continued a command straight ahead. I noted it and commented to the Captain who simply confirmed we were beginning to cross the course on the supplemental MFD display. Simultaneously; I turned to re-intercept the course needle to intercept and fly to Wentz. While we did overfly the course by the time I realized what was happening the needle did not deviate more than 3/4 of a dot and I did level at 1;500 FT cross what was slightly abeam of Wentz. I just then followed the course needle manually to remain on the departure. New York departure said nothing except to give us a climb to 8;000 FT. The Captain noted that on one previous occasion; when there was a moderate or greater crosswind and the commanding flight director was on the right side; the Flight Director did not capture the course on an approach. However; it only happened on one day before I arrived on the airplane and he noted it never re-occurred. Therefore; no comment was made of that irregularity. When we arrived at our destination; the current Captain listed the irregularity as a discrepancy and reported it to maintenance. When we arrived at the airplane on the following day; we noted that maintenance had 'ops checked' the autopilot with no discrepancies noted and returned the aircraft to service. We did fly the aircraft on the next leg and the automation performed flawlessly.
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.