ATL83IA028 · Convair 340
Florida Aircraft Leasing Convair 340 · Incident: fire en route
From Baltimore, MD to Greensboro, NC
Event
- NTSB case
- ATL83IA028
- 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
- General aviation
- 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
Convair 340
- Aircraft type
- Convair 340
- 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
- N4814C
- Operator
- Florida Aircraft Leasing
- Onboard fatalities
- Unknown
- Route
- From Baltimore, MDTo Greensboro, NC
- 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 125: 20+ Pax,6000+ lbs
- 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
- Fire
- 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
- Engine assembly, master rod › Failure, total
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
THE PILOT STATED THAT WHILE AT CRUISE AT 4000 FEET THAT THERE WAS A SHARP JOLT IN THE AIRFRAME AND ON FURTHER INVESTIGATION DISCOVERED THAT THE LEFT ENGINE WAS ON FIRE. THE PROPELLER STOPPED TURNING SHORTLY THEREAFTER. IMMEDIATELY THE PILOT PULLED THE FIREWALL SHUTOFF VALVE AND COMPLETED THE EMERGENCY CHECKLIST. THE FLIGHT CONTINUED TO ITS INTENDED DESTINATION AND LANDED UNEVENFULLY. GROUND EXAMINATION OF THE AIRCRAFT REVEALED THAT THE ENGINE FORWARD BANK MASTER ROD HAD FAILED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83IA028
- Event ID
- 20020917X04336
- Case number
- ATL83IA028
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1982-11-11.
- API snapshot SHA-256: a0480e3d5e4bdac33b0a2bc50a3b93bcb006d751d1b840e0f0424283760a3133; retrieved 2026-09-24T00:07:29.893Z.