37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1013065 |
Time | |
Date | 201205 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | IAH.Airport |
State Reference | TX |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
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 150 Flight Crew Total 14000 Flight Crew Type 4300 |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
When loading speed info into the climb page; we received a 'standby one' message in the FMC scratch pad that would not clear for several minutes. During that time the route disappeared from the map and the route and legs pages were empty of all but origination; destination and flight number. Any attempt to load a route caused the 'standby one' message to reappear. We were unable to locate guidance in the QRH or flight manual that addressed other than a temporary 'standby one.' attempts to communicate with dispatch and maintenance control through arinc via SELCAL took approximately 25 minutes to complete. In the meantime; we started troubleshooting on our own by first pressing the first officer's FMC switch to alternate. This caused the message to go away; but it returned as soon as we tried inputting route info. We returned the first officer's switch to normal then attempted same procedure with captain's switch and getting the same result. Once we eventually established communication with dispatch and maintenance they had us repeat that same process with the captain's side. This time the procedure seemed to work; however; it was very; very slow; taking several minutes before it would accept more than one waypoint and displays the route in map mode. Then it took several more minutes before we were able to load the climb; cruise or descent pages. When one page was able to load; it would take several minutes before we could load the next. I am concerned about the amount of time it took to get the communication established with dispatch and maintenance. Aren't we supposed to be able to quickly communicate with the company at all times during flight? Additionally; more info should be available in the flight manual regarding this FMC issue.
Original NASA ASRS Text
Title: When the FMC CDUs stopped functioning and the route pages and map display disappeared a B757-200 flight crew attempted to contact Dispatch and Maintenance Control for assistance. This attempt met with significant delay and the crew attempted unsuccessfully to resolve the problem without maintenance guidance. When; after 25 minutes; communication was established functional but very slow use of the FMS was restored.
Narrative: When loading speed info into the climb page; we received a 'standby one' message in the FMC scratch pad that would not clear for several minutes. During that time the route disappeared from the map and the route and legs pages were empty of all but origination; destination and flight number. Any attempt to load a route caused the 'standby one' message to reappear. We were unable to locate guidance in the QRH or Flight Manual that addressed other than a temporary 'standby one.' Attempts to communicate with Dispatch and Maintenance Control through ARINC via SELCAL took approximately 25 minutes to complete. In the meantime; we started troubleshooting on our own by first pressing the First Officer's FMC switch to alternate. This caused the message to go away; but it returned as soon as we tried inputting route info. We returned the First Officer's switch to normal then attempted same procedure with Captain's switch and getting the same result. Once we eventually established communication with Dispatch and Maintenance they had us repeat that same process with the Captain's side. This time the procedure seemed to work; however; it was very; very slow; taking several minutes before it would accept more than one waypoint and displays the route in map mode. Then it took several more minutes before we were able to load the climb; cruise or descent pages. When one page was able to load; it would take several minutes before we could load the next. I am concerned about the amount of time it took to get the communication established with Dispatch and Maintenance. Aren't we supposed to be able to quickly communicate with the company at all times during flight? Additionally; more info should be available in the Flight Manual regarding this FMC issue.
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.