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

February 22, 2016 · Piper PA28 151 151 · N41618

St. Augustine, FL

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 22, 2016
Injury Outcomes
No injuries (2 uninjured)
Location
St. Augustine, FL
Aircraft
Piper PA28 151 151 (1974)
Tail Number
N41618
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA16LA119

According to the flight instructor, the airplane's engine stopped producing power during taxi immediately after landing. He attempted to restart the engine, but it caught fire. He stopped the airplane, and both the instructor and the student egressed, but they made no attempt to extinguish the fire because there was no fire extinguisher on board the airplane. Although the fire was eventually extinguished by first responders, it substantially damaged the airplane. Review of the Pilot's Operating Handbook (POH) revealed that engine fires during start were usually due to overpriming and that the first attempt to extinguish the fire should be to try to start the engine and draw the excess fuel back into the induction system. It is likely the flight instructor overprimed the engine, which resulted in an engine fire, and then failed to follow the POH procedure to extinguish the fire. Due to the instructor's failure to attempt to remediate the problem, the fire was not extinguished in a timely manner.

NTSB Probable Cause

The flight instructor's overpriming of the engine during start, which resulted in a carburetor fire. Contributing to the severity of accident was the flight instructor's failure to follow the Pilot Operating Handbook's engine fire during start emergency procedures.

Full Narrative

On February 21, 2016, about 2015 eastern standard time, a Piper PA-28-151, N41618, was substantially damaged by an engine fire after landing at Northeast Florida Regional Airport (SGJ), St. Augustine, Florida. The flight instructor and his pilot-rated student were not injured. Night visual meteorological conditions prevailed, and no flight plan was filed for the local instructional flight, which was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. According to the flight instructor, the airplane's engine stopped producing power during taxi immediately after landing. An engine restart was attempted, and the engine caught fire. The airplane was stopped, and both the instructor and the student egressed the airplane, but made no attempt to extinguish the fire, as there was no fire extinguisher on board the airplane. Instead, the instructor dialed 911 on his cellular telephone. The fire department on the airport was closed, and local police and fire responded to the call. The police arrived first, and were delayed at a perimeter gate, which was subsequently opened by airport personnel. The first police officer on scene suppressed the fire with a hand-held fire extinguisher from his cruiser until firefighters arrived and ensured the fire was fully extinguished shortly thereafter. The firefighters gained access through an entry point previously briefed and rehearsed with the airport authority. Examination of the airplane by a Federal Aviation Administration (FAA) aviation safety inspector revealed that both the engine firewall and mount required replacement due to fire damage. The inspector asked the operator why no fire extinguisher was installed in the accident airplane. He said the airplane was a late addition to the school's fleet, and that he and his staff "forgot" to install one. All other airplanes at the school were equipped with fire extinguishers. The instructor held a commercial pilot and flight instructor certificates with ratings for airplane single engine land, multiengine land and instrument airplane. His most recent third-class medical certificate was issued on January 18, 2016. The pilot reported 153 total hours of flight experience, of which 65 hours were in the accident airplane make and model. The pilot held a private pilot certificate with a rating for airplane single engine land. His most recent first-class medical certificate was issued on January 27, 2016. The instructor reported 895 total hours of flight experience, of which 20 hours were in the accident airplane make and model. The four-seat, single-engine, low-wing airplane was manufactured in 1974 and was equipped with a Lycoming O-320 series engine. A review of logbook entries by the FAA inspector revealed the airplane's most recent 100-hour inspection was completed July 27, 2015, at 7,717 total aircraft hours. Review of the Pilot's Operating Handbook, Section 3, Emergency Procedures revealed that engine fires during start were usually the result of overpriming, and that the first attempt to extinguish the fire should be to try to start the engine and draw the excess fuel back into the induction system.

Flight

Event TypeAccident
Event Time20:15 EST
Nearest AirportNortheast Florida Rgnl (0nm S)
Runway13
Runway Length8002 ft
Runway Width150 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireGrd
Aircraft ExplosionNo

Aircraft

AircraftPiper PA28 151 151
Tail NumberN41618
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 SERIES · Reciprocating · 150
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 22 · First Class · None
Crew 2Age 37 · Third Class · None

Conditions

ConditionsVMC
LightBright Night
Wind160° @ 7 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point64 F / 57
Altimeter30.12 inHg
Observation Time00:58

Appendix: Source Data