37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 807588 |
Time | |
Date | 200810 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : san.airport |
State Reference | CA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : san.tower |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : takeoff ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 220 flight time total : 9200 flight time type : 2200 |
ASRS Report | 807588 |
Events | |
Anomaly | aircraft equipment problem : less severe |
Independent Detector | aircraft equipment other aircraft equipment : ecam other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | Aircraft Flight Crew Human Performance |
Primary Problem | Aircraft |
Narrative:
While taxiing out at san we got repeated 'navigation FMS/GPS position disagree' warnings from ECAM. This is a well known problem that happens every time we fly the airbus into san diego (I do not know the cause). We cancelled the warning repeatedly and continued with the takeoff. After takeoff we had indications that one of our 'flight management guidance computers' (FMGC's) had failed. I'm not positive; but I believe it may have been failed before we took off; we may have disregarded the 'warning signs' when we were disregarding the navigation position failures. There are 2 problems here: 1) the GPS accuracy anomaly at san needs to be addressed so crews are not 'trained' by habit to just 'ignore' an ECAM warning. 2) the FMGC's are not monitored by the ECAM system on the airbus. Loss of an FMGC is a very serious matter; it should have a separate crew warning rather than just leaving hard to interpret 'clues' for the crew to attempt to decipher.callback conversation with reporter revealed the following information: the reporter believes that there may be interference at san that affects the GPS receiver causing the ECAM warnings. However; the real problem is the fact that flight crews are ignoring the warnings and use the ECAM emergency cancel to prevent them from repeating. The fact that an FMGC failure can be subtle and should produce an ECAM warning needs to be addressed.
Original NASA ASRS Text
Title: A320 FO REPORTS NAV/GPS POSITION DISAGREE ECAMS DURING TAXI AT SAN; WHICH ARE COMMON AND ROUTINELY DISREGARDED. AFTER TKOF AN FMGC IS DISCOVERED TO HAVE FAILED.
Narrative: WHILE TAXIING OUT AT SAN WE GOT REPEATED 'NAV FMS/GPS POSITION DISAGREE' WARNINGS FROM ECAM. THIS IS A WELL KNOWN PROBLEM THAT HAPPENS EVERY TIME WE FLY THE AIRBUS INTO SAN DIEGO (I DO NOT KNOW THE CAUSE). WE CANCELLED THE WARNING REPEATEDLY AND CONTINUED WITH THE TAKEOFF. AFTER TAKEOFF WE HAD INDICATIONS THAT ONE OF OUR 'FLIGHT MANAGEMENT GUIDANCE COMPUTERS' (FMGC'S) HAD FAILED. I'M NOT POSITIVE; BUT I BELIEVE IT MAY HAVE BEEN FAILED BEFORE WE TOOK OFF; WE MAY HAVE DISREGARDED THE 'WARNING SIGNS' WHEN WE WERE DISREGARDING THE NAV POSITION FAILURES. THERE ARE 2 PROBLEMS HERE: 1) THE GPS ACCURACY ANOMALY AT SAN NEEDS TO BE ADDRESSED SO CREWS ARE NOT 'TRAINED' BY HABIT TO JUST 'IGNORE' AN ECAM WARNING. 2) THE FMGC'S ARE NOT MONITORED BY THE ECAM SYSTEM ON THE AIRBUS. LOSS OF AN FMGC IS A VERY SERIOUS MATTER; IT SHOULD HAVE A SEPARATE CREW WARNING RATHER THAN JUST LEAVING HARD TO INTERPRET 'CLUES' FOR THE CREW TO ATTEMPT TO DECIPHER.CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE REPORTER BELIEVES THAT THERE MAY BE INTERFERENCE AT SAN THAT AFFECTS THE GPS RECEIVER CAUSING THE ECAM WARNINGS. HOWEVER; THE REAL PROBLEM IS THE FACT THAT FLT CREWS ARE IGNORING THE WARNINGS AND USE THE ECAM EMERGENCY CANCEL TO PREVENT THEM FROM REPEATING. THE FACT THAT AN FMGC FAILURE CAN BE SUBTLE AND SHOULD PRODUCE AN ECAM WARNING NEEDS TO BE ADDRESSED.
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.