FTW89IA067 · Boeing 727-232
Boeing 727-232 · Incident: airframe, component or system failure en route
From Hartsfield Jackson Atlanta International Airport (ATL) to San Diego International Airport (SAN)
Event
- NTSB case
- FTW89IA067
- 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
Boeing 727-232
- Aircraft type
- Boeing 727
- 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
- N511DA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GATo San Diego International Airport (SAN), San Diego, CA
- 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 · 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Fire warning system, powerplant › Contamination
- Fire warning system, powerplant › False indication
- Fire warning system, powerplant › Shorted
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ACFT MADE A PRECAUTIONARY LANDING AFTER GETTING A FIRE WARNING INDICATION IN THE #2 ENG. INITIALLY THE INDICATIONS, BOTH THE FIRE WARNING LIGHT AND BELL, WERE INTERMITTENT; HOWEVER, THEY THEN WENT TO STEADY AND THE CREW SECURED THE ENG AND DISCHARGED BOTH FIRE BOTTLES WITH NO EFFECT. INVESTIGATION REVEALED THAT THERE HAD NOT BEEN A FIRE OR OVER TEMP CONDITION AND THAT THE ENGINE FIRE DETECTION LOOP WAS SHORTED OUT ON BOTH ELEMENTS. CONTAMINANTS WERE FOUND ON THE CONNECTORS AND PINS OF ONE END OF THE LOOP DURING INITIAL INSP. AFTER HANDLING AND SHIPMENT TO THE OPERATOR'S MAINTENANCE FACILITY, THE SHORT DISAPPEARED AND COULD NOT BE DUPLICATED. LOOP MET ALL MANUFACTURERING SPECIFICATIONS AND FUNCTIONED NORMALLY DURING ALL TESTING. CONTAMINANTS APPEARED TO BE ENGINE OIL AND HYDRAULIC FLUID. NO DETERMINATION WAS MADE ABOUT HOW OR WHEN THE CONTAMINANTS WERE INTRODUCED TO THE HERMETICALLY SEALED CONNECTORS.
Probable cause
FALSE FIRE WARNING, WHICH RESULTED FROM (1) CONTAMINANTS ON HARDWARE AT ONE END OF THE FIRE DETECTION LOOP; AND (2) AN ELECTRICAL SHORT ON BOTH ELEMENTS OF THE LOOP.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW89IA067
- Event ID
- 20001213X27892
- Case number
- FTW89IA067
- 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, damage. 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: 8f96571f46a1aa0213e66cccfbe76c1714d521009d2429217bf6c0f3e3107cee; retrieved 2026-09-18T19:13:24.826Z.