Narrative:

I set up my FMS with the departure procedure. All required checks of the FMS were completed according to FM1 and aom V1. Both FMS 1 and 2 were set correctly. During the taxi checklist both FMS's were checked and were set correctly for runway. After a normal takeoff; navigation was selected. I noticed that my FMS display showed us right of course and first officer's FMS displayed showed us left of course with no malfunction indication. The first officer was following the flight director bars until I notified him our FMS indications were not the same. At that time he rolled the wings level. Shortly after ATC asked for our heading and assigned us a new heading. We still had no malfunction indications. We wrote it up enroute and flight crew placarded both FMS's. Dispatch; maintenance control; and ATC were notified of the failures. We notified ATC that we were negative RNAV and that GPS's had failed. We conducted the remainder of the flight under conventional navigation.supplemental information from acn 748407: all indications showed the units functioning properly on preflight and taxi and there was no warning when the GPS's failed.callback conversation with reporter revealed the following information: the first officer stated that a power interruption at the gate prior to pushback may have initiated this event although he sees no reason why an FMC or EICAS alert message was not generated as it should have been. The EMB145 FMC automatically adjusts rnp for the phase of flight and type of departure/arrival/approach being flown. The rnp and GPS status is available in the FMC but the correct page must be selected to view it.

Google
 

Original NASA ASRS Text

Title: AN EMB 145 EXPERIENCED DUAL GPS FAILURES CAUSING AN FMS LNAV DIFFERENCE BETWEEN THE CAPT AND FO. THE EICAS DID NOT ALERT ABOUT THE GPS FAILURES.

Narrative: I SET UP MY FMS WITH THE DEP PROC. ALL REQUIRED CHECKS OF THE FMS WERE COMPLETED ACCORDING TO FM1 AND AOM V1. BOTH FMS 1 AND 2 WERE SET CORRECTLY. DURING THE TAXI CHECKLIST BOTH FMS'S WERE CHECKED AND WERE SET CORRECTLY FOR RWY. AFTER A NORMAL TAKEOFF; NAV WAS SELECTED. I NOTICED THAT MY FMS DISPLAY SHOWED US RIGHT OF COURSE AND FO'S FMS DISPLAYED SHOWED US LEFT OF COURSE WITH NO MALFUNCTION INDICATION. THE FO WAS FOLLOWING THE FLIGHT DIRECTOR BARS UNTIL I NOTIFIED HIM OUR FMS INDICATIONS WERE NOT THE SAME. AT THAT TIME HE ROLLED THE WINGS LEVEL. SHORTLY AFTER ATC ASKED FOR OUR HEADING AND ASSIGNED US A NEW HEADING. WE STILL HAD NO MALFUNCTION INDICATIONS. WE WROTE IT UP ENROUTE AND FLIGHT CREW PLACARDED BOTH FMS'S. DISPATCH; MAINT CTL; AND ATC WERE NOTIFIED OF THE FAILURES. WE NOTIFIED ATC THAT WE WERE NEGATIVE RNAV AND THAT GPS'S HAD FAILED. WE CONDUCTED THE REMAINDER OF THE FLIGHT UNDER CONVENTIONAL NAVIGATION.SUPPLEMENTAL INFO FROM ACN 748407: ALL INDICATIONS SHOWED THE UNITS FUNCTIONING PROPERLY ON PREFLIGHT AND TAXI AND THERE WAS NO WARNING WHEN THE GPS'S FAILED.CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE FO STATED THAT A POWER INTERRUPTION AT THE GATE PRIOR TO PUSHBACK MAY HAVE INITIATED THIS EVENT ALTHOUGH HE SEES NO REASON WHY AN FMC OR EICAS ALERT MESSAGE WAS NOT GENERATED AS IT SHOULD HAVE BEEN. THE EMB145 FMC AUTOMATICALLY ADJUSTS RNP FOR THE PHASE OF FLIGHT AND TYPE OF DEPARTURE/ARRIVAL/APPROACH BEING FLOWN. THE RNP AND GPS STATUS IS AVAILABLE IN THE FMC BUT THE CORRECT PAGE MUST BE SELECTED TO VIEW IT.

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