ERA11FA349 · Cessna T210N
Cessna T210N · Accident: loss of engine power (partial) during initial climb
From Westchester County Airport (HPN) to Montauk Airport (MTP)
Event
- NTSB case
- ERA11FA349
- 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
- 4 · 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 T210N
- Aircraft type
- Cessna 210
- 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
- N210KW
- Operator
- Keith Weiner
- Onboard fatalities
- Unknown
- Route
- From Westchester County Airport (HPN), White Plains, NYTo 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
- 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
- Loss of engine power (partial)
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
Witnesses observed the pilot perform multiple engine run-ups both on the parking ramp and at the end of the runway prior to departure. Both witnesses reported that the engine initially idled rough. Shortly after takeoff from runway 34, the pilot informed the air traffic controller that he needed to return to the airport and requested runway 16. The pilot declared an emergency but did not state the reason why. The airplane impacted trees and terrain about 1 mile from the approach end of runway 16. The cockpit and cabin sections were found inverted and mostly consumed by a post-crash fire. The wreckage path through the trees indicated that the airplane was established on a shallow glide angle when the impact occurred, with the landing gear and flaps retracted. A disassembly and examination of the engine revealed that the No. 2 cylinder piston head exhibited severe thermal deterioration consistent with a pre-ignition or detonation event. The electrodes of the No. 2 cylinder spark plugs were fully imbedded with aluminum and appeared incapable of producing a spark. The other five cylinders appeared to be functional and were undamaged. The left magneto was set to 30 degrees before top dead center (BTDC); the manufacturer's specification was 22 degrees BTDC. The right magneto was broken at its mount and its timing could not be verified. Examination of the engine maintenance records revealed that the magnetos were last retimed during an annual inspection about 27 months before the accident. The airplane was flown infrequently since the engine was installed in 2007.
The airport was equipped with noise abatement monitoring microphones that captured the airplane on the outbound and inbound (return) legs during the accident sequence. Although the engine appeared to be running just prior to impact, the engine sound pressure recorded on the outbound leg was significantly greater than on the inbound leg, suggesting that the pilot was approaching the airport at a reduced power setting. Although the amount of engine power available could not be determined, it is likely that additional power was available had the throttle been advanced.
Probable cause
The pilot's decision to depart on the flight with a suspected mechanical deficiency and his subsequent decision to fly the final approach at a reduced power setting. Contributing to the accident was the improper timing of the magneto(s) that resulted in a severe detonation event.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11FA349
- Event ID
- 20110618X55026
- Case number
- ERA11FA349
- 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, 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: 4c0054b99309a65117651355b37f57f5076555b449badf598e67a1cab307db89; retrieved 2026-09-13T21:28:17.484Z.