ERA09LA269 · Cessna 208
Greystoke Engineering Cessna 208 · Accident: powerplant system/component malfunction/failure while taxiing
From Winchester Regional Airport (OKV) to Frederick Municipal Airport (FDK)
Event
- NTSB case
- ERA09LA269
- 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
Cessna 208
- Aircraft type
- Cessna 208
- 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
- N208JW
- Operator
- Greystoke Engineering
- Onboard fatalities
- Unknown
- Route
- From Winchester Regional Airport (OKV), Winchester, VATo Frederick Municipal Airport (FDK), Frederick, MD
- 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
- Taxi · from runway
- 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
- Powerplant system/component malfunction/failure
- 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 power plant
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the landing roll, with the power lever at idle, the pilot heard a “pop,” followed by indications of the engine “spooling down.” He exited the runway and observed smoke coming from the engine compartment. Thinking this was residual fuel, he “spooled the engine.” Realizing there was a fire, he called for assistance and shut off the fuel selectors and firewall shutoff valve. After the accident, a FAA inspector examined the airplane and reported extensive thermal damage to the fuselage sub-frame and evidence of an engine fire. Numerous engine turbine blades were found on the pavement adjacent to where the fire occurred. A disassembly and inspection of the engine revealed that one or more of the compressor turbine (CT) blades failed. The engine was overhauled about 6 hours prior to the accident. The CT blades were manufactured under the FAA Parts Manufacture Approval (PMA) program. Extreme heat damage obliterated the fracture surfaces of the blades, therefore the reason for the blade failure(s) could not be determined. A functional test of the fuel control unit (FCU) revealed the Sg (specific gravity) dome, high idle stop screw, and minimum flow stop were set above the recommended range, which would result in higher than normal fuel flow. The FCU adjustments appeared to be made after the overhaul, however it could not be determined when the adjustments occurred. Although the higher than normal fuel flow setting probably did not result in the CT blade failures, it could have exacerbated the thermal damage and fire.
Probable cause
A loss of engine power due to the failure of one or more compressor turbine blades for an undetermined reason.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09LA269
- Event ID
- 20090427X62717
- Case number
- ERA09LA269
- 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: 22093e17a71bf45784117d24b3a07e3f4211ab77ce9ef881e5a6128bcfe10f88; retrieved 2026-09-15T10:59:26.733Z.