37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 291830 |
Time | |
Date | 199412 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : pgy airport : san |
State Reference | CA |
Altitude | msl bound lower : 9000 msl bound upper : 11000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : san tower : ord |
Operator | common carrier : air carrier |
Make Model Name | Large Transport, Low Wing, 2 Turbojet Eng |
Navigation In Use | Other Other |
Flight Phase | climbout : intermediate altitude |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : flight engineer pilot : atp |
Experience | flight time last 90 days : 150 flight time total : 12000 flight time type : 1350 |
ASRS Report | 291830 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Events | |
Anomaly | aircraft equipment problem : critical non adherence : published procedure |
Independent Detector | aircraft equipment other aircraft equipment : unspecified |
Resolutory Action | aircraft : equipment problem dissipated other |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | Pilot Deviation |
Narrative:
Climbing through 9000 ft we received an engine 1 'B' loop detector fault on the ECAM. This lasted approximately 10 seconds then cleared itself. Less than a min later the engine 1 fire warning illuminated. We requested and were granted clearance to level off at 11000 ft. Once again the fault cleared itself as we prepared to execute the checklist. The warning was present for approximately 15 seconds. We checked the engine instruments and visually inspected the engine. The only discrepancy noted was a slightly higher nacelle temperature on #1 with bleed pressure 2 psi lower. Readings were: #1 nacelle 205 degrees C, bleed pressure 38 psi, and on #2 170 degrees C nacelle temperature, 40 psi bleed pressure. We continued on course and contacted dispatch and maintenance control to discuss the problem. Maintenance and control suspected a slight bleed leak on #1 but stated (with dispatch concurrence) that the problem did not warrant a diversion. We elected to continue to destination with no further incidents. Upon arrival we entered the discrepancy in the aircraft's logbook. After further reflection, it might have been more prudent to divert. It seems that with the level of computerization we now have, we may be less likely to treat a warning seriously because we receive so many false warnings, ie, warnings that appear for a short time and then clear themselves from the computer, and others that may be cleared by resetting the computer. Callback conversation with reporter revealed the following information: reporter returned call with the following information. The A-320 has been having a rash of fire warning loop faults. He stated that this particular aircraft was taken OTS after they arrived at the destination airport. The maintenance log indicated that maintenance changed both loops in the system. He isn't certain that this was the cause of the fire warning but the aircraft system is designed to give a fire warning when both loops develop a fault. He will investigate further and advise. He further indicated that he has seen more extreme nacelle temperatures than in this case. He felt there might have been a bleed air leak in this incident but to what extent he wasn't certain. He reiterated his feelings that he should have diverted back to lax for a maintenance check and correction. He agreed with the analyst's assessment that he may have been in continued flight towards destination airport without any fire warning sensing because of faulted loops. Reporter made a second call with the following information: he again stated that this particular aircraft had been taken OTS after they arrived at the destination airport. The aircraft log indicated that maintenance changed both loops in the system. He is now certain that this was the cause of the fire warning as the aircraft system is designed to give a fire warning when both loops develop a fault. He talked with other persons not idented, and found another crew that had experienced the same symptoms of faulted loops as he had on the previously stated date. This crew had the same aircraft 4 days later, after the maintenance had been performed on it.
Original NASA ASRS Text
Title: AN A-320 CREW EXPERIENCES A FAULTED B LOOP IN THE ACFT'S FIRE WARNING SYS AND THEN A FIRE WARNING WHICH SEEMS TO CLR ITSELF PRIOR TO CHKLIST EXECUTION.
Narrative: CLBING THROUGH 9000 FT WE RECEIVED AN ENG 1 'B' LOOP DETECTOR FAULT ON THE ECAM. THIS LASTED APPROX 10 SECONDS THEN CLRED ITSELF. LESS THAN A MIN LATER THE ENG 1 FIRE WARNING ILLUMINATED. WE REQUESTED AND WERE GRANTED CLRNC TO LEVEL OFF AT 11000 FT. ONCE AGAIN THE FAULT CLRED ITSELF AS WE PREPARED TO EXECUTE THE CHKLIST. THE WARNING WAS PRESENT FOR APPROX 15 SECONDS. WE CHKED THE ENG INSTS AND VISUALLY INSPECTED THE ENG. THE ONLY DISCREPANCY NOTED WAS A SLIGHTLY HIGHER NACELLE TEMP ON #1 WITH BLEED PRESSURE 2 PSI LOWER. READINGS WERE: #1 NACELLE 205 DEGS C, BLEED PRESSURE 38 PSI, AND ON #2 170 DEGS C NACELLE TEMP, 40 PSI BLEED PRESSURE. WE CONTINUED ON COURSE AND CONTACTED DISPATCH AND MAINT CTL TO DISCUSS THE PROB. MAINT AND CTL SUSPECTED A SLIGHT BLEED LEAK ON #1 BUT STATED (WITH DISPATCH CONCURRENCE) THAT THE PROB DID NOT WARRANT A DIVERSION. WE ELECTED TO CONTINUE TO DEST WITH NO FURTHER INCIDENTS. UPON ARR WE ENTERED THE DISCREPANCY IN THE ACFT'S LOGBOOK. AFTER FURTHER REFLECTION, IT MIGHT HAVE BEEN MORE PRUDENT TO DIVERT. IT SEEMS THAT WITH THE LEVEL OF COMPUTERIZATION WE NOW HAVE, WE MAY BE LESS LIKELY TO TREAT A WARNING SERIOUSLY BECAUSE WE RECEIVE SO MANY FALSE WARNINGS, IE, WARNINGS THAT APPEAR FOR A SHORT TIME AND THEN CLR THEMSELVES FROM THE COMPUTER, AND OTHERS THAT MAY BE CLRED BY RESETTING THE COMPUTER. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR RETURNED CALL WITH THE FOLLOWING INFO. THE A-320 HAS BEEN HAVING A RASH OF FIRE WARNING LOOP FAULTS. HE STATED THAT THIS PARTICULAR ACFT WAS TAKEN OTS AFTER THEY ARRIVED AT THE DEST ARPT. THE MAINT LOG INDICATED THAT MAINT CHANGED BOTH LOOPS IN THE SYS. HE ISN'T CERTAIN THAT THIS WAS THE CAUSE OF THE FIRE WARNING BUT THE ACFT SYS IS DESIGNED TO GIVE A FIRE WARNING WHEN BOTH LOOPS DEVELOP A FAULT. HE WILL INVESTIGATE FURTHER AND ADVISE. HE FURTHER INDICATED THAT HE HAS SEEN MORE EXTREME NACELLE TEMPS THAN IN THIS CASE. HE FELT THERE MIGHT HAVE BEEN A BLEED AIR LEAK IN THIS INCIDENT BUT TO WHAT EXTENT HE WASN'T CERTAIN. HE REITERATED HIS FEELINGS THAT HE SHOULD HAVE DIVERTED BACK TO LAX FOR A MAINT CHK AND CORRECTION. HE AGREED WITH THE ANALYST'S ASSESSMENT THAT HE MAY HAVE BEEN IN CONTINUED FLT TOWARDS DEST ARPT WITHOUT ANY FIRE WARNING SENSING BECAUSE OF FAULTED LOOPS. RPTR MADE A SECOND CALL WITH THE FOLLOWING INFO: HE AGAIN STATED THAT THIS PARTICULAR ACFT HAD BEEN TAKEN OTS AFTER THEY ARRIVED AT THE DEST ARPT. THE ACFT LOG INDICATED THAT MAINT CHANGED BOTH LOOPS IN THE SYS. HE IS NOW CERTAIN THAT THIS WAS THE CAUSE OF THE FIRE WARNING AS THE ACFT SYS IS DESIGNED TO GIVE A FIRE WARNING WHEN BOTH LOOPS DEVELOP A FAULT. HE TALKED WITH OTHER PERSONS NOT IDENTED, AND FOUND ANOTHER CREW THAT HAD EXPERIENCED THE SAME SYMPTOMS OF FAULTED LOOPS AS HE HAD ON THE PREVIOUSLY STATED DATE. THIS CREW HAD THE SAME ACFT 4 DAYS LATER, AFTER THE MAINT HAD BEEN PERFORMED ON IT.
Data retrieved from NASA's ASRS site as of July 2007 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.