Airbus A-300B4-605R N80057
9 July 1998 · San Juan · Minor injuries
Summary
On 9 July 1998 at about 14:07 local time, a Airbus A-300B4-605R registered N80057, operated by American Airlines, Inc., was involved in an incident near San Juan. 252 people were on board and 28 had minor injuries. The aircraft was slightly damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 14:07
- Classification
- Incident
- Location
- San Juan
- Nearest airport
- Luiz Munoz Marin Int'l (SJU)
- Coordinates
- Not recorded
- Aircraft
- Airbus A-300B4-605R
- Registration
- N80057
- Category
- Airplane
- Engines
- 2
- Operator
- American Airlines, Inc.
- Operating rule
- Part 121: Air Carrier
- Purpose of flight
- Unknown
- Phase of flight
- Not recorded
- Route
- Unknown → Miami
- Aircraft damage
- Minor
- Weather
- VMC
- Light
- Day
- NTSB number
- MIA98IA195
People
28 people had minor injuries.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 252 | 0 | 0 | 28 | 224 |
Probable cause
An in-flight engine fire resulting from (1) the failure of the engine overhaul facility to install, and the failure of American Airlines to ensure installation of, the proper adapter bolt inserts to preclude fuel leakage and the failure of the engine overhaul facility to notify the aircraft operator and the engine manufacturer, and request correction, of an error in Service Bulletin (SB) 72-743; and (2) and the failure of General Electric Aircraft Engines to specify the proper adapter bolt insert and to correct SB 72-743 after notification of the error. Contributing to the severity of the incident were (1) the flight crew's failure immediately to complete the in-flight engine fire procedures and (2) the failure of Airbus Industrie and American Airlines to provide all necessary information in the in-flight engine fire procedures.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
Shortly after takeoff, as the flight climbed through 3,100 feet, the No. 1 engine fire warning activated. About 20 seconds later, the captain, who was the pilot flying, moved the No. 1 throttle to idle and asked the first officer to declare an emergency with air traffic control. About 47 seconds after the first officer identified the No. 1 engine fire warning, the captain asked the first officer to perform the engine fire emergency procedures checklist. The engine fire warning system deactivated because of fire damage to one of the fire loops, about 88 seconds after the fire warning activated and 2 seconds before the first officer moved the No. 1 fuel lever to the off position, shutting down the No. 1 engine. The flight crew did not notice the warning that the No. 1 fire loop system was inoperative. The engine fire warning system uses two loops. If one loop should no longer sense a fire or become inoperative because of fire damage, the engine fire warning will deactivate and a fire loop warning will be displayed to the flight crew. The flight crew must deactivate the faulty loop to regain the engine fire warning. The crew elected to stop the procedure after shutting down the No.1 engine because the fire light went out, and therefore did not activate the No.1 fire handle. Pressurized fuel continued to be supplied to the engine and feed the engine fire. The flight crew turned back to the departure airport. At 2,000 feet, about 3 minutes from landing, a flight attendant reported that a mechanic in the back had stated that the No. 1 engine was still smoking or on fire. The flight crew did not take any action and landed. About 1 minute after stopping, the captain ordered an emergency evacuation of the airplane, with instructions not to use the left overwing exits. About 1 minute 55 seconds after landing, the flight crew pulled the engine and auxiliary power unit fire handles and discharged the fire bottles into the No. 1 engine. In 1995, Airbus changed the engine fire procedure to allow for discontinuing the fire procedure and keeping an engine running at idle after an engine fire warning once the fire warning has gone out and after the throttle has been moved to idle. This change was made because of the high number of bleed air leak activated fire warnings. Postincident examination of the No. 1 engine showed that all the accessory gearbox idler adapter attachment bolt inserts had backed out, allowing fuel lines to unseat and spray pressurized fuel onto hot engine parts and ignite. On September 26, 1995, the accessory gear box idler adapter had been reworked per General Electric Aircraft Engine Service Bulletin 72-743 during engine overhaul at a vendor's facility. Smaller-than-required adapter bolt inserts had been installed.
Quoted verbatim from the NTSB record.
Other Airbus A-300B4 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 7 Jan 1997 | Airbus A-300B4-605R | Atlantic Ocean | - | Serious injuries | - |
| 20 Feb 1996 | Airbus A-300B4-605R | Jamaica, New York, United States | - | Serious injuries | - |
| 17 Jan 1996 | Airbus A-300B4-605R | Atlantic Ocean | - | Serious injuries | - |
| 15 Nov 1988 | Airbus A-300B4-203 | Panama City, Panama | Pan American World Airways | Serious injuries | - |
| 28 May 1985 | Airbus A-300B4-2C | Atlantic Ocean | - | Serious injuries | - |
| 7 Nov 1983 | Airbus A-300B4-2C | Miami, Florida, United States | Eastern Airlines Inc. | No injuries | - |