 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B767 pilot describes a strange pegasus FMC failure that the crew is eventually able to overcome; after much effort; and continue to destination.
| Attributes | |
| ACN | 1256678 |
| Time | |
| Date | 201504 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZMA.ARTCC |
| State Reference | FL |
| Environment | |
| Flight Conditions | Marginal |
| Aircraft 1 | |
| Make Model Name | B767-300 and 300 ER |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Pilot Not Flying |
| Experience | Flight Crew Type 100 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
I was the pilot monitoring on a pegasus 767-300 on departure; when five thousand feet from level off we lost VNAV. We detected the FMC had dropped the cruise altitude somehow; so we're entered cruise altitude of FL320. As we leveled off; we had been cleared to meagan intersection on the departure; but the magenta line was gone from the pfd. Looking at the FMC; we saw that now the route was gone. I selected the departure again; but when I tried to execute it; it gave me a scratch pad message 'stand by one'. As I tried to execute the route the FMC locked up and failed to work. We notified ATC who gave us a heading as we worked on the problem. We ran the QRH procedure and slowly gained some use of the FMC in a limited state. We were finally able to load a route using latitude/lon and execute it. This was done using route two; route one was non-functional at this time. As we loaded more points; ATC gave us a heading for remis and we put it in the FMC and it allowed us to execute and navigation. As we continued; more of the functions began to return on both FMC's. We were finally able to load the entire route and successfully navigate to destination without further complications. Dispatch; the company and ATC were advised during the event. No deviations occurred that we are aware of.
Original NASA ASRS Text
Title: B767 pilot describes a strange Pegasus FMC failure that the crew is eventually able to overcome; after much effort; and continue to destination.
Narrative: I was the pilot monitoring on a Pegasus 767-300 on departure; when five thousand feet from level off we lost VNAV. We detected the FMC had dropped the cruise altitude somehow; so we're entered cruise altitude of FL320. As we leveled off; we had been cleared to MEAGAN intersection on the departure; but the magenta line was gone from the PFD. Looking at the FMC; we saw that now the route was gone. I selected the departure again; but when I tried to execute it; it gave me a scratch pad message 'stand by one'. As I tried to execute the route the FMC locked up and failed to work. We notified ATC who gave us a heading as we worked on the problem. We ran the QRH procedure and slowly gained some use of the FMC in a limited state. We were finally able to load a route using LAT/LON and execute it. This was done using route two; route one was non-functional at this time. As we loaded more points; ATC gave us a heading for REMIS and we put it in the FMC and it allowed us to execute and NAV. As we continued; more of the functions began to return on both FMC's. We were finally able to load the entire route and successfully navigate to destination without further complications. Dispatch; the company and ATC were advised during the event. No deviations occurred that we are aware of.
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.