FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD02FA086 · Cessna 172S

17 Aug 2002 · Plainville, CT, United States

Cessna 172S · Accident: fire during initial climb

From Robertson Field (4B8) to Montauk Airport (MTP)

Report a problem

Event

NTSB case
IAD02FA086
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
2 · 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

Cessna 172S

Aircraft type
Cessna 172
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
N35073
Operator
Unknown
Onboard fatalities
Unknown
Route
From Robertson Field (4B8), Plainville, CTTo Montauk Airport (MTP), Montauk, NY
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 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
Initial climb
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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Engine compartment › Fire
  • Pilot in command › Airspeed, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Several witnesses observed black smoke trailing the airplane immediately after takeoff, and one witness saw a "small orange ball" immediately behind the propeller. One witness also noticed that the engine noise had changed, as if the engine had experienced a power reduction, another heard the engine "cut-out," and a third heard the engine "sputter." About 400 feet, a nose-high, left turn was initiated back towards the airport, and the airplane subsequently "banked steeply downward" until it impacted the ground. The wreckage path was about 70 feet in length. Due to the severity of a post-impact fire, the origin of the in-flight fire and loss of engine power could not be determined.

Probable cause

An in-flight engine compartment fire of unknown origin, and a loss of engine power for undetermined reasons. Also causal, was the pilot's failure to maintain airspeed during a turn back to the airfield, which resulted in an inadvertent stall and subsequent impact with the ground.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD02FA086
Event ID
20020826X01459
Case number
IAD02FA086
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, coordinates. 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: 1dea3e7a8d0f2dd03e7006416b13f419d2ef560a2d245214818ab5c36aac2b99; retrieved 2026-09-20T19:54:18.264Z.