ERA18FA244 · Cessna 335
Cessna 335 · Accident: loss of control in flight on approach
From Key West International Airport (EYW) to Palm Beach County Park Airport (LNA)
Event
- NTSB case
- ERA18FA244
- 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
- 2 · 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 335
- Aircraft type
- Cessna 335
- 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
- N2707J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Key West International Airport (EYW), Key West, FLTo Palm Beach County Park Airport (LNA), Lake Worth, FL
- Aircraft age
- About 39 years (built 1979)
- 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 base
- 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 control in flight
- 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft power plant
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot, who was the owner of the airplane, was conducting a personal cross-country flight with one passenger. Recorded engine data indicated that, about 9 miles from the destination airport, the left engine lost all power for about 2 minutes. Power was restored for about 2 minutes before it was lost again as the airplane was on a left downwind leg abeam the approach end of the runway. The right engine's power output remained relatively constant for the remainder of the flight. The airplane continued the downwind leg for about 20 seconds, then began a left descending 180° turn. Data recovered from the primary flight display indicated that, at the end of this turn, the airspeed decreased to 73 knots (kts), below the airplane's published minimum control speed of 83 kts, and the airplane rolled inverted and descended into the ground.
The pilot did not hold a valid pilot certificate at the time of the accident, as his certificate had been revoked about 21 years earlier. Although the pilot had owned the airplane for about 7 years, he had logged only 1.8 hours in the preceding eight months, and 6.4 hours during the prior calendar year. The most recent documented practice of one engine inoperative (OEI) procedures was over 6 years before the accident, and there was no record of any flight reviews in his logbook; therefore, it is unlikely that the pilot was proficient in the procedures associated with OEI at the time of the accident, which included the criticality of maintaining minimum control speed (Vmc) and not turning into the nonoperational engine.
Examination of both engines revealed no anomalies that would have precluded normal operation and the right engine's recorded data parameters and propeller exhibited signatures consistent with the engine operating until impact. Although the engine monitor's recorded parameters indicated the left engine lost power immediately before the accident, it lacked sufficient parameters to determine why the loss of engine power occurred. Given the available fuel onboard, the airplane had adequate fuel to complete the accident flight; however, the pilot's management of the fuel during the flight and whether it contributed to the loss of left engine power could not be determined.
Although autopsy of the pilot revealed evidence of severe coronary artery disease, the recorded flight data indicated that he continued to fly the airplane after both losses of power in the left engine; therefore, it is unlikely that sudden impairment or incapacitation from an acute cardiac event contributed to the loss of control. The pilot may have been experiencing effects from his use of diphenhydramine, such as psychomotor slowing and impaired judgment. However, based on the available information, whether effects from his use of diphenhydramine contributed to this accident could not be determined.
Probable cause
The pilot's loss of control during approach for landing following a total loss of left engine power for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA18FA244
- Event ID
- 20180909X20438
- Case number
- ERA18FA244
- 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: 015cebb6f21782fe6124f7f875551b70b4087fa4e5ce9bbaa7a37a538650f677; retrieved 2026-09-15T06:47:44.590Z.