Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

April 4, 2014 · Piper Aircraft PA-28-161 · N642FT

Melbourne, FL

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
April 4, 2014
Injury Outcomes
No injuries (2 uninjured)
Location
Melbourne, FL
Aircraft
Piper Aircraft PA-28-161 (2008)
Tail Number
N642FT
Operator
Fit Aviation
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA14LA268

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.

NTSB 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.

Full Narrative

On April 4, 2014, about 1014 eastern daylight time, a Piper PA-28-161, N642FT, experienced an engine compartment fire after landing at Melbourne International Airport (MLB), Melbourne, Florida. The certified flight instructor (CFI) and pilot-rate student were not injured. The airplane was substantially damaged. The airplane was registered to and operated by FIT Aviation, LLC, under the provisions of 14 Code of Federal Regulations (CFR) Part 91 as an instructional flight. Visual meteorological conditions prevailed at the time and no flight plan was filed for the local flight, which originated about 1 hour 4 minutes earlier. The CFI stated that after landing on runway 27R, while taxiing off the runway onto taxiway "Q" just prior to the hold short lines, the engine quit. He contacted the tower and asked for permission to push the airplane completely off the runway to give himself, "…time to think", but the tower controller declined and instructed them to advise whether they could start the engine. They used the procedures for a hot and cold engine, but was unable to start the engine. They began to notice smoke coming from the engine cowling, and secured the airplane. After evacuating it, they noticed flames from the engine cowling. The CFI attempted to extinguish the fire using the on-board hand held fire extinguisher, but was unable. Airport fire rescue responded and extinguished the fire. During repairs of the airplane to return it to service, the engine mount was inspected and overhauled; however, the firewall required replacement. The carburetor, a MA4-SPA, part number 10-5217, serial number CK47312 was removed, and taken to a FAA certified repair station for inspection and testing with FAA oversight. According to the report, the examination of the carburetor revealed the unit exhibited charring on the exterior and also inside the carburetor throat or venture. Bench testing revealed no issues related to the float shut off and accelerator pump discharge. The removal torque forces of the throttle body to bowl screws were checked and all were reported to be greater than 10 inch pounds, although the technician recalled the values were between 25 and 35 inch pounds (tightening torque specification is 35 to 45 inch pounds). Personnel of the repair station indicate it is not unusual for units in service returned to them for overhaul to exhibit no loosening torque values of the screws that secure the throttle body to the carburetor bowl. Review of the maintenance records revealed the carburetor was overhauled last on December 13, 2013, and installed on the accident airplane on March 21, 2014, where it remained installed until removed postaccident. The carburetor had accrued approximately 37 hours since overhaul at the time of the engine fire. Review of the Pilot's Operating Handbook and FAA Approved Airplane Flight Manual revealed that it specifies that engine fires during start are usually the result of overpriming.

Flight

Event TypeAccident
Event Time10:14 EDT
Nearest AirportMelbourne International Arpt (0nm)
Runway27R
Runway Length6000 ft
Runway Width150 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireGrd
Aircraft ExplosionNo

Aircraft

AircraftPiper Aircraft PA-28-161
Tail NumberN642FT
Aircraft CategoryAir
DamageSubstantial
OperatorFit Aviation
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-D3G · Reciprocating · 160
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 20 · First Class · None
Crew 2Age 29 · First Class · None

Conditions

ConditionsVMC
LightDaylight
Wind200° @ 9 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point63 F
Altimeter30.06 inHg
Observation Time13:53
Weather SourceWFAC

Appendix: Source Data