37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 953072 |
Time | |
Date | 201106 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | TNP.VORTAC |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Stratolifter (C-135)/Stratotanker (KC-135) |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | IFR |
Component | |
Aircraft Component | Navigational Equipment and Processing |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Commercial Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 38 Flight Crew Total 2200 Flight Crew Type 1200 |
Events | |
Anomaly | Aircraft Equipment Problem Critical Airspace Violation All Types Deviation - Track / Heading All Types |
Narrative:
The autopilot was engaged in navigation/localizer with a closed random pattern depicted in the flight plan following the four points forming the air refueling track within R2501. We were approximately 5-10 miles from the western border of R2501; headed west; and all three mfd's in map mode displayed aircraft within R2501 on a westbound course with a turn southbound ahead.all systems remained normal with no faulty indications when we suddenly lost all three mfd map displays; which all went blank and displayed 'map fail' indications. I asked the boom [operator] to reference an independent laptop with GPS guidance; which displays a moving map of the aircraft purely for aircrew situational awareness. The boom [operator] pulled up the moving map display; which showed the aircraft outside of R2501 to the west. I immediately initiated a turn back towards the east by reference to a ground point we were familiar with from previous orbits and magnetic compass heading.after a short troubleshooting session; we were able to regain our heading; navigation system; and map displays on all three mfd's by proceeding direct to another point in the flight plan. We disengaged the navigation/localizer on the autopilot and navigated the rest of our mission off of the map displays while cross checking the separate laptop GPS moving map. There is no guidance within the kc-135 technical orders for a 'map fail' indication. There is; however; a safety supplement for the kc-135 block 40.1 navigation software for a frozen heading/navigation system failure. While we agree we had a frozen heading/navigation system failure; our indications within the cockpit did not match the safety supplement and the safety supplement did not mention any 'map fail' annunciation.there were no air traffic control conflicts which occurred during our 'spill-out' of R2501 and la center logged the event as a 'spill-out.' this was an extremely alarming event to the aircrew; especially based on the lack of before and after system failure reports. There was absolutely no warning other than the 'map fail' which only showed after the failure had already been occurring in the system; all while the auto-pilot remained coupled to the failed navigation system. Even after we were able to get the mfd's back there were no indications of any failure; no bit codes; no faults; etc. The only CDU annunciation was a 'check cp GPS;' which we did and found all navigation systems in the green with minimal drift. We have reported this malfunction to aircraft maintenance.
Original NASA ASRS Text
Title: A KC-135 flight crew suffered the loss of all three MFD map displays while performing a refueling mission. A temporary departure from the charted refueling airspace occurred while they reoriented themselves and regained use of the NAV displays.
Narrative: The autopilot was engaged in NAV/LOC with a closed random pattern depicted in the flight plan following the four points forming the air refueling track within R2501. We were approximately 5-10 miles from the western border of R2501; headed west; and all three MFD's in MAP mode displayed aircraft within R2501 on a westbound course with a turn southbound ahead.All systems remained normal with no faulty indications when we suddenly lost all three MFD map displays; which all went blank and displayed 'MAP FAIL' indications. I asked the Boom [Operator] to reference an independent laptop with GPS guidance; which displays a moving map of the aircraft purely for aircrew situational awareness. The Boom [Operator] pulled up the moving map display; which showed the aircraft outside of R2501 to the west. I immediately initiated a turn back towards the east by reference to a ground point we were familiar with from previous orbits and magnetic compass heading.After a short troubleshooting session; we were able to regain our HDG; NAV system; and map displays on all three MFD's by proceeding direct to another point in the flight plan. We disengaged the NAV/LOC on the autopilot and navigated the rest of our mission off of the map displays while cross checking the separate laptop GPS moving map. There is no guidance within the KC-135 technical orders for a 'MAP FAIL' indication. There is; however; a safety supplement for the KC-135 block 40.1 navigation software for a frozen HDG/NAV system failure. While we agree we had a frozen HDG/NAV system failure; our indications within the cockpit did not match the safety supplement and the safety supplement did not mention any 'MAP FAIL' annunciation.There were no air traffic control conflicts which occurred during our 'spill-out' of R2501 and LA Center logged the event as a 'spill-out.' This was an extremely alarming event to the aircrew; especially based on the lack of before and after system failure reports. There was absolutely no warning other than the 'MAP FAIL' which only showed after the failure had already been occurring in the system; all while the auto-pilot remained coupled to the failed NAV system. Even after we were able to get the MFD's back there were no indications of any failure; no BIT codes; no faults; etc. The only CDU annunciation was a 'check CP GPS;' which we did and found all NAV systems in the green with minimal drift. We have reported this malfunction to aircraft Maintenance.
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.