ERA12LA157 · Cessna 210E
Cessna 210E · Accident: loss of engine power (total) on approach
From Spruce Creek Airport (7FL6) to Spruce Creek Airport (7FL6)
Event
- NTSB case
- ERA12LA157
- 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 210E
- 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
- N7130U
- Operator
- Clarry James S
- Onboard fatalities
- Unknown
- Route
- From Spruce Creek Airport (7FL6), Port Orange, FLTo Spruce Creek Airport (7FL6), Port Orange, FL
- Aircraft age
- About 47 years (built 1965)
- 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
- Approach · VFR pattern downwind
- 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)
- 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
- 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
According to the pilot, it was the first flight after the engine installation. Prior to departure, he conducted a preflight engine run-up and all systems were normal. The airplane then departed and climbed to the traffic pattern altitude. While on the downwind leg of the traffic pattern, the engine failed. The pilot attempted to return to the airport but was unsuccessful and made a forced landing short of the runway in a heavily wooded area. An examination of the fuel did not reveal any contamination. While examination of the induction tubes revealed that the right side intake induction tube was not connected properly (the clamp was found tight but the rubber connection hose was not sealed), it may have become disconnected when the engine was dragged out from the accident site during recovery. Further, the engine manufacturer indicated that a loose intake induction tube would disrupt air flow but would not necessarily cause an engine to stop. Examination of the ignition system revealed that sections of the wiring were not sealed. Uninsulated or unsealed areas of the ignition system wiring could have caused grounding/shorting of the ignition system; however, the investigation was unable to conclusively determine the reason for the total loss of engine power.
Probable cause
The total loss of engine power for reasons that could not be conclusively determined during postaccident examination.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12LA157
- Event ID
- 20120126X92124
- Case number
- ERA12LA157
- 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: f0ddead21bf6b8743bb158c0cf4bac866518dbfe339ac47b1a92dc52b9c69605; retrieved 2026-09-15T17:06:58.968Z.