NYC00FA239 · Cessna 206H
Dunkirk Aviation Cessna 206H · Accident: fire/explosion en route
From Chautauqua County-Dunkirk Airport (DKK) to Port Meadville Airport (GKJ)
Event
- NTSB case
- NYC00FA239
- 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
- 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
Cessna 206H
- Aircraft type
- Cessna 206
- 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
- N7269S
- Operator
- Dunkirk Aviation
- Onboard fatalities
- Unknown
- Route
- From Chautauqua County-Dunkirk Airport (DKK), Dunkirk, NYTo Port Meadville Airport (GKJ), Meadville, PA
- 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
- 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/explosion
- 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
- Tree(s)
- 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
- Fluid, fuel › Exploded
- Fluid, fuel › Leak
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane climbed to 4,000 feet. After level-off, the pilot checked that the gauges were 'in the green,' set the power to 2,400 rpm and 24 inches of manifold pressure, and engaged the autopilot. The engine was running smoothly, with no vibrations. About 35 to 40 seconds later, there was a loud explosion, and blue and yellow flames emanated from both sides of the engine compartment. The pilot turned the airplane towards a field he had seen earlier. During the turn, there was a second explosion. The engine, which had continued to run smoothly after the first explosion, quit. The cabin became engulfed in black smoke, and forward visibility was nil. The pilot then made a forced landing, but due to limited visibility out the side window, the airplane struck trees during the approach, stalled, and hit the ground. Post-accident investigation revealed fire damage to the accessory section of the engine, the firewall, and the interior surface of the left engine cowling. Unburned oil residue was found on the interior surface of the right engine cowling. Oil was also found on the undersides of the fuselage and wings. The oil filler tube, on the right side of the engine, was burned away; however, the majority of the oil dipstick was still in place, in the engine. The interior surface of the left cowling was sooted and scorched. The bottom plate of the engine driven fuel pump was burned away, and the fuel boost pump was sooted. There was a breach in the engine casing, in the vicinity of the number 6 connecting rod. All of the connecting rod ends exhibited heat damage, consistent with a loss of lubrication, with the most severely damaged being the number 6 rod end. The oil pump housing and impellers exhibited light scoring. The main bearings were undamaged. The pilot stated that during his preflight inspection, he checked three times that the oil cap was secure. Additionally, no oil leaks were found on the ramp. Another pilot, with the same airframe/engine configuration as the accident airplane, reported that his oil cap had come loose during flight on several occasions. However, even though it came loose, there was no oil leakage.
Probable cause
An engine compartment explosion due to a fuel/fuel vapor leak of undetermined origin. A secondary explosion resulted from a lack of lubrication to the number 6 connecting rod bearing. Contributing to the pilot's injuries was his reduced visibility during the forced landing, resulting from a heavy concentration of smoke in the cockpit.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00FA239
- Event ID
- 20001212X21847
- Case number
- NYC00FA239
- 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. 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: f05b926b5b90716efd84f3de5c46a3c570fe4cc1ba079c27a1b26f5b0b3fc989; retrieved 2026-09-21T10:28:23.237Z.