B767 flight crew experienceds a dual FMC failure shortly after departure while attempting to go dire...

Narrative:

At gate; both pilots checked the entire route reading from both the route page as well as fix-by-fix on the plan/legs page. Everything checked normal and as filed. After takeoff from runway 09 and a 120 degree heading initial turn by the tower; received an ATC clearance from departure to proceed direct to skips. I was the pilot flying; so the first officer made the FMC entry to proceed direct to skips. As the first officer was querying me on 'how does that look?' both FMC scratch pads displayed 'standby one.' in addition; the entire route was now gone… nothing showed on any route page after page 1 and nothing existed on any legs page. That scratch pad item would never go away until later in the flight when the FMS computers were reset. Told ATC about the FMC problem and they gave us an initial vector to skips while I switched to VOR raw data and navigated on our own. We told ATC that we had lost RNAV capability and would need to be rerouted on an airway. We got A315 and navigated there on our own towards zin using VOR raw data and heading select. Contacted dispatch followed by a phone patch to maintenance. Maintenance suggested an FMC reset by pulling both FMC circuit breakers and resetting them. We did that; reloaded the route to the next down line fix after zin; and informed ATC that we were normal and RNAV capable again. The remainder of the flight was normal. In addition; after the problem started; we advised ATC the suffixes that no longer applied to our flight/aircraft after loss of RNAV capability. We were prepared to return to mia or divert to an appropriate field considering our equipment problem and weather. Since the problem was solved before leaving mia ARTCC airspace; we felt that we chose the correct alternative given the evolving issue and eventual resolution.

Original NASA ASRS Text

Title: B767 Flight Crew experienceds a dual FMC failure shortly after departure while attempting to go direct to a fix. Both FMC's were successfully reset and flight continued to destination.

Narrative: At gate; both pilots checked the entire route reading from both the route page as well as fix-by-fix on the plan/legs page. Everything checked normal and as filed. After takeoff from Runway 09 and a 120 degree heading initial turn by the Tower; received an ATC clearance from departure to proceed direct to SKIPS. I was the pilot flying; so the First Officer made the FMC entry to proceed direct to SKIPS. As the First Officer was querying me on 'How does that look?' both FMC scratch pads displayed 'Standby One.' In addition; the entire route was now gone… nothing showed on any route page after page 1 and nothing existed on any legs page. That scratch pad item would never go away until later in the flight when the FMS computers were reset. Told ATC about the FMC problem and they gave us an initial vector to SKIPS while I switched to VOR raw data and navigated on our own. We told ATC that we had lost RNAV capability and would need to be rerouted on an airway. We got A315 and navigated there on our own towards ZIN using VOR raw data and heading select. Contacted Dispatch followed by a phone patch to Maintenance. Maintenance suggested an FMC reset by pulling both FMC circuit breakers and resetting them. We did that; reloaded the route to the next down line fix after ZIN; and informed ATC that we were normal and RNAV capable again. The remainder of the flight was normal. In addition; after the problem started; we advised ATC the suffixes that no longer applied to our flight/aircraft after loss of RNAV capability. We were prepared to return to MIA or divert to an appropriate field considering our equipment problem and weather. Since the problem was solved before leaving MIA ARTCC airspace; we felt that we chose the correct alternative given the evolving issue and eventual resolution.

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.

Attributes
ACN	884422
Time
Date	201004
Local Time Of Day	0601-1200
Place
Locale Reference	MIA.Airport
State Reference	FL
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Component
Aircraft Component	FMS/FMC
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Person 2
Function	Pilot Not Flying First Officer
Events
Anomaly	Aircraft Equipment Problem Less Severe

B767 flight crew experienceds a dual FMC failure shortly after departure while attempting to go direct to a fix. Both FMC's were successfully reset and flight continued to destination.