B737 first officer reported dual FMC failure in cruise flight at FL350. The flight crew successfully...

Narrative:

We were cruising at FL350; proceeding direct to mqp VOR; in LNAV and VNAV path; and talking to fort worth center when both fmcs went blank. As the fmcs went blank; the autothrottles turned off and the lateral navigation mode reverted to control wheel steering. The captain responded by selecting; heading select and altitude hold; to maintain our course and altitude. I proceeded to call fort worth center; informed them that we had a system failure; and requested vectors to mqp VOR until we could get the fmcs back. Fort worth center told us to just maintain our present heading and inform them when we had the problem sorted out. After about 30 seconds; the FMC prompt at 1L returned on both cdus. As the pilot monitoring; I ran the QRH for FMC inflight restart. It took several minutes to re-input the data; verify the route; and verify our position. Both fmcs appeared to operating normally again so we informed fort worth that we could retake direct to mqp. They told us in the meantime that we had been rerouted and should proceed direct to diesl and join a different arrival. The remainder of the flight went normally. We entered a report of the failure into the electronic logbook. I should note that we checked route 2 during the preflight to ensure that it was empty per the pilot bulletin. There was no data entered in route 2.

Original NASA ASRS Text

Title: B737 First Officer reported dual FMC failure in cruise flight at FL350. The flight crew successfully reset both FMCs and the flight continued to destination.

Narrative: We were cruising at FL350; proceeding direct to MQP VOR; in LNAV and VNAV Path; and talking to Fort Worth Center when both FMCs went blank. As the FMCs went blank; the Autothrottles turned off and the lateral navigation mode reverted to control wheel steering. The Captain responded by selecting; Heading select and Altitude hold; to maintain our course and altitude. I proceeded to call Fort Worth Center; informed them that we had a system failure; and requested vectors to MQP VOR until we could get the FMCs back. Fort Worth Center told us to just maintain our present heading and inform them when we had the problem sorted out. After about 30 seconds; the FMC prompt at 1L returned on both CDUs. As the pilot monitoring; I ran the QRH for FMC Inflight Restart. It took several minutes to re-input the data; verify the route; and verify our position. Both FMCs appeared to operating normally again so we informed Fort Worth that we could retake direct to MQP. They told us in the meantime that we had been rerouted and should proceed direct to DIESL and join a different arrival. The remainder of the flight went normally. We entered a report of the failure into the Electronic Logbook. I should note that we checked Route 2 during the preflight to ensure that it was empty per the Pilot Bulletin. There was no data entered in Route 2.

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.

Attributes
ACN	1514291
Time
Date	201801
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Route In Use	Direct
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Pilot Not Flying First Officer
Experience	Flight Crew Type 1809
Events
Anomaly	Aircraft Equipment Problem Less Severe

B737 first officer reported dual FMC failure in cruise flight at FL350. The flight crew successfully reset both fmcs and the flight continued to destination.