Narrative:

During preflight in ZZZ1 we had a map shift between FMC generated position and raw data of at least 4 degrees deviation from ZZZ1 VOR sitting at gate at international terminal. Wrote it up also stating that air show map was reading wrong. Mechanic's action was to cycle air show circuit breaker. I complained that this was inadequate action because it did not address the issue in the cockpit with the navigation instruments. Subsequently maintenance recycled FMC circuit breakers which seemed to fix problem. Maintenance wanted to go without amending the mrd to reflect this maintenance action; but I told them we would require an amended mrd as required by the fom and far. We departed but returned to the gate due to antiskid failure. Deferral was issued and we departed again. On approach to ZZZ2 runway 34L ILS; being vectored; both FMC's failed with no EICAS message. This was very disconcerting to me as we were in turbulence and WX with IFR WX at ZZZ2. I directed the first officer's to reload the data and I advised ATC; requested delay vectors while first officer's reloaded all data into the CDU's. We lost route; landing altitude; performance data; everything; with no EICAS message. We accomplished this in about 4 mins and shot the approach. Landed normally. I see in the log that maintenance action was to recycle some circuit breakers and clear the item. I am concerned that we seem to be casually addressing these FMC type issues in light of the recent event at ZZZ1 involving aircraft Y; jan 08. Is this appropriate maintenance action? I have learned that this aircraft may have a history of this type of fault but I cannot say for sure with the limited resources that are at my disposal here in my room in ZZZ2.

Google
 

Original NASA ASRS Text

Title: B747-400 CAPTAIN QUESTIONS WHETHER MAINT ATTENTION TO FMC ANOMALIES IS ADEQUATE.

Narrative: DURING PREFLT IN ZZZ1 WE HAD A MAP SHIFT BTWN FMC GENERATED POS AND RAW DATA OF AT LEAST 4 DEGS DEV FROM ZZZ1 VOR SITTING AT GATE AT INTL TERMINAL. WROTE IT UP ALSO STATING THAT AIR SHOW MAP WAS READING WRONG. MECH'S ACTION WAS TO CYCLE AIR SHOW CIRCUIT BREAKER. I COMPLAINED THAT THIS WAS INADEQUATE ACTION BECAUSE IT DID NOT ADDRESS THE ISSUE IN THE COCKPIT WITH THE NAV INSTS. SUBSEQUENTLY MAINT RECYCLED FMC CIRCUIT BREAKERS WHICH SEEMED TO FIX PROB. MAINT WANTED TO GO WITHOUT AMENDING THE MRD TO REFLECT THIS MAINT ACTION; BUT I TOLD THEM WE WOULD REQUIRE AN AMENDED MRD AS REQUIRED BY THE FOM AND FAR. WE DEPARTED BUT RETURNED TO THE GATE DUE TO ANTISKID FAILURE. DEFERRAL WAS ISSUED AND WE DEPARTED AGAIN. ON APCH TO ZZZ2 RWY 34L ILS; BEING VECTORED; BOTH FMC'S FAILED WITH NO EICAS MESSAGE. THIS WAS VERY DISCONCERTING TO ME AS WE WERE IN TURB AND WX WITH IFR WX AT ZZZ2. I DIRECTED THE FO'S TO RELOAD THE DATA AND I ADVISED ATC; REQUESTED DELAY VECTORS WHILE FO'S RELOADED ALL DATA INTO THE CDU'S. WE LOST RTE; LNDG ALT; PERFORMANCE DATA; EVERYTHING; WITH NO EICAS MESSAGE. WE ACCOMPLISHED THIS IN ABOUT 4 MINS AND SHOT THE APCH. LANDED NORMALLY. I SEE IN THE LOG THAT MAINT ACTION WAS TO RECYCLE SOME CIRCUIT BREAKERS AND CLR THE ITEM. I AM CONCERNED THAT WE SEEM TO BE CASUALLY ADDRESSING THESE FMC TYPE ISSUES IN LIGHT OF THE RECENT EVENT AT ZZZ1 INVOLVING ACFT Y; JAN 08. IS THIS APPROPRIATE MAINT ACTION? I HAVE LEARNED THAT THIS ACFT MAY HAVE A HISTORY OF THIS TYPE OF FAULT BUT I CANNOT SAY FOR SURE WITH THE LIMITED RESOURCES THAT ARE AT MY DISPOSAL HERE IN MY ROOM IN ZZZ2.

Data retrieved from NASA's ASRS site as of May 2009 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.