FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Airlines Airbus Industrie A-300B4-605R A300B4-605 incident

9 Jul 1998 · San Juan, PR, United States

Airbus Industrie A-300B4-605R A300B4-605 · Incident: fire/explosion en route

From Luis Munoz Marin International Airport (SJU) to Miami International Airport (MIA)

Report a problem

Event

NTSB case
MIA98IA195
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Airbus Industrie A-300B4-605R A300B4-605

Aircraft type
Airbus A-300
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N80057
Onboard fatalities
Unknown
Route
From Luis Munoz Marin International Airport (SJU)To Miami International Airport (MIA), Miami, FL
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · climb to cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Fire/explosion
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Flightcrew › Emergency procedure, delayed
  • Flightcrew › Emergency procedure, discontinued
  • Flightcrew › Fire extinguishing equipment, not used
  • Other maintenance personnel › Maintenance, overhaul, improper

Approximate · Estimated position: the centre of San Juan, the place the record names. Not the accident site.

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA98IA195
Event ID
20001211X10654
Case number
MIA98IA195
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 2c5975f6708625cab524d50dbf4715abf16df60db2b17f7f14533ada12bed9a2; retrieved 2026-09-18T17:07:17.129Z.