ERA14LA268 · Piper Aircraft Inc PA-28-161
FIT Aviation Piper Aircraft Inc PA-28-161 · Accident: fire/smoke (non-impact) while standing
From Melbourne Orlando International Airport (MLB) to Melbourne Orlando International Airport (MLB)
Event
- NTSB case
- ERA14LA268
- 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
- Accident
- 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
- Unknown
- 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
Piper Aircraft Inc PA-28-161
- Aircraft type
- Piper PA-28
- 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
- N642FT
- Operator
- Fit Aviation
- Onboard fatalities
- Unknown
- Route
- From Melbourne Orlando International Airport (MLB), Melbourne, FLTo Melbourne Orlando International Airport (MLB), Melbourne, FL
- Aircraft age
- About 6 years (built 2008)
- 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 91: General Aviation
- 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
- Standing · engine(s) start-up
- Defining eventThe 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/smoke (non-impact)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that, while taxiing off the runway after landing and when the airplane was just before the hold short lines, the engine quit. The flight instructor contacted the tower air traffic controller and asked for permission to push the airplane completely off the runway, but the tower controller declined and instructed him to advise whether he could get the engine started. The flight instructor attempted to start the engine using procedures for a hot and cold engine and then noticed smoke coming from the engine cowling. The flight instructor secured the airplane, and, after evacuating it, noticed flames coming from the engine cowling, which he was unable to extinguish using the on-board fire extinguisher. Airport rescue and firefighting personnel responded and extinguished the fire.
Postaccident examination of the carburetor revealed that the loosening torque values of the screws that secure the throttle body to the carburetor bowl were lower than the tightening torque value specified for overhaul. However, repair station personnel reported that it was not uncommon for in-service units to exhibit no loosening torque value. The engine fire was likely caused by the flight instructor's overpriming of the engine during multiple unsuccessful engine start attempts, which likely resulted from his feeling rushed to get the engine started while the airplane was still on an active runway. The reason for the loss of engine power could not be determined.
Probable cause
The flight instructor’s overpriming of the engine during multiple unsuccessful engine start attempts on an active runway, which resulted in an engine compartment fire.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14LA268
- Event ID
- 20140530X42427
- Case number
- ERA14LA268
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 5655d5c8e6079b9699563af28c121fcf2d03c40f96f84d929dccd01c0541b83c; retrieved 2026-09-15T23:41:39.951Z.