ERA10LA335 · Cessna 210D
Cessna 210D · Accident: loss of engine power (total) en route
From Easton Airport / Newnam Field (ESN) to Francis S Gabreski Airport (FOK)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA10LA335
- 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 210D
- 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
- N3973Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Easton Airport / Newnam Field (ESN), Easton, MDTo Francis S Gabreski Airport (FOK), Westhampton, 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
- En route · cruise
- 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 (total)
- 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
- Aircraft › Fluids/miscellaneous hardware
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, the engine began running rough approximately 1 hour into the flight. Shortly thereafter, all engine power was lost, and the pilot executed a forced landing to a field. During the landing, the airplane collided with a walkway railing, substantially damaging the left wing. Examination of the engine revealed that it lost power due to oil starvation. Signatures within the internal components were consistent with engine operation after a depleted oil supply. Further examination revealed that the gasket between the oil filter adapter and the pump was torn, likely allowing oil to leak from this junction. Oil leak signatures including oil staining on the bottom of the engine were identified during the postaccident investigation. No determination could be made regarding how long the gasket had been in place.
Probable cause
The loss of engine power due to the failure of the oil filter gasket and the subsequent engine oil depletion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10LA335
- Event ID
- 20100627X42646
- Case number
- ERA10LA335
- 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: e7741bf72b18ed175342fb35de61e0e60012f4df877b0305c6520f2f25e29dba; retrieved 2026-09-15T14:30:31.438Z.