 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A dc-10 on an RNAV departure climb lost both the autothrust and navigation capabilities for a short period time which caused a track deviation.
| Attributes | |
| ACN | 1022894 |
| Time | |
| Date | 201207 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | DC-10 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Navigational Equipment and Processing |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
On departure after contacting departure control and given climb to 14;000 ft; flying an RNAV departure in navigation we lost ats and navigation. First officer flying first noticed problem when he lost his course and pitch bars in his pfd. Concurrently I noticed the loss of the ats with N1 exceeding climb thrust limits on all three engines. Meanwhile first officer called for flaps retract while I continued to troubleshoot. Soon after retracting flaps ATC gave us a left turn to 090 and level off at 6;000 ft. We then realized we had gone past a waypoint on the departure; which was why ATC gave us the vector and level off. We then informed ATC that we had lost our navigation and was having issues with other systems. Within a short period we regained all systems; retracted the slats and returned to normal procedures to continue on our way uneventfully to our filed destination. Communicate the navigation problem right away and ask for vectors.
Original NASA ASRS Text
Title: A DC-10 on an RNAV departure climb lost both the autothrust and navigation capabilities for a short period time which caused a track deviation.
Narrative: On departure after contacting Departure Control and given climb to 14;000 FT; flying an RNAV Departure in NAV we lost ATS and NAV. First Officer flying first noticed problem when he lost his course and pitch bars in his PFD. Concurrently I noticed the loss of the ATS with N1 exceeding Climb Thrust Limits on all three engines. Meanwhile First Officer called for flaps retract while I continued to troubleshoot. Soon after retracting flaps ATC gave us a left turn to 090 and level off at 6;000 FT. We then realized we had gone past a waypoint on the departure; which was why ATC gave us the vector and level off. We then informed ATC that we had lost our NAV and was having issues with other systems. Within a short period we regained all systems; retracted the slats and returned to normal procedures to continue on our way uneventfully to our filed destination. Communicate the NAV problem right away and ask for vectors.
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.