 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Challenger captain reported an FMS malfunction on departure; causing a deviation from their IFR clearance.
| Attributes | |
| ACN | 1681024 |
| Time | |
| Date | 201909 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | Challenger Jet Undifferentiated or Other Model |
| Operating Under FAR Part | Part 135 |
| Flight Phase | Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Seconds after departure; FMS number 1 lost position. Since this was an RNAV departure we were cleared RNAV zzzzz. As we had reviewed the departure before takeoff I knew there was a left turn coming up. This is when we were fully aware of the FMS position error. I started the left turn; but turned too far and ATC gave us a heading. We were told to review the departure by ATC. We advised ATC that we had lost FMS position and would need vectors until we could sort out the problem. I put the FMS into independent mode as FMS number 2 was meled. I then updated the number 1 FMS using [a nearby] VOR as a reference. This worked and we completed the trip using FMS number 1 and backup using VOR navigation. [We] asked ATC for vectors until we sorted out the position error.
Original NASA ASRS Text
Title: Challenger Captain reported an FMS malfunction on departure; causing a deviation from their IFR clearance.
Narrative: Seconds after departure; FMS Number 1 lost position. Since this was an RNAV departure we were cleared RNAV ZZZZZ. As we had reviewed the departure before takeoff I knew there was a left turn coming up. This is when we were fully aware of the FMS position error. I started the left turn; but turned too far and ATC gave us a heading. We were told to review the departure by ATC. We advised ATC that we had lost FMS position and would need vectors until we could sort out the problem. I put the FMS into independent mode as FMS Number 2 was MELed. I then updated the Number 1 FMS using [a nearby] VOR as a reference. This worked and we completed the trip using FMS Number 1 and backup using VOR NAV. [We] asked ATC for vectors until we sorted out the position error.
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.