FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13FA275 · Cessna 340A

8 Jun 2013 · Boynton Beach, FL, United States

Paul S. Soule Enterprises Cessna 340A · Accident: loss of control in flight en route

From Fort Lauderdale Executive Airport (FXE) to Leesburg International Airport (LEE)

Report a problem

Event

NTSB case
ERA13FA275
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
1 · 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
Instrument Meteorological Cond

Cessna 340A

Aircraft type
Cessna 340
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
N217JP
Onboard fatalities
Unknown
Route
From Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, FLTo Leesburg International Airport (LEE), Leesburg, FL
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 · climb to 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 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
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Four minutes after taking off on an instrument flight rules flight, during an assigned climb to 4,000 feet, the pilot advised the departure air traffic controller that the airplane was having "instrument problems" and that he wanted to "stay VFR" (visual flight rules), which the controller acknowledged. As directed, the pilot subsequently contacted the next sector departure controller, who instructed him to climb to 8,000 feet. The pilot stated that he would climb the airplane after clearing a cloud and reiterated that the airplane was having "instrument problems." The controller told the pilot to advise when he could climb the airplane. About 30 seconds later, the pilot told the controller that he was climbing the airplane to 8,000 feet, and, shortly thereafter, the controller cleared the airplane to 11,000 feet, which the pilot acknowledged. Per instruction, the pilot later contacted a center controller, who advised him of moderate-to-heavy precipitation along his (northbound) route for the next 10 miles and told him that he could deviate either left or right and, when able, proceed direct to an intersection near his destination. The pilot acknowledged the direct-to-intersection instruction, and the controller told the pilot to climb the airplane to 13,000 feet, which the pilot acknowledged. The pilot did not advise the center controller about the instrument problems.

The airplane subsequently began turning east, eventually completing about an 80-degree turn toward heavier precipitation, and the controller told the pilot to climb to 15,000 feet, but the pilot did not respond. After two more queries, the pilot stated that he was trying to maintain "VFR" and that "I have an instrument failure here." The controller then stated that he was showing the airplane turning east, which "looks like a very bad idea." He subsequently advised the pilot to turn to the west but received no further transmissions from the airplane.

Radar indicated that, while the airplane was turning east, it climbed to 9,500 feet but that, during the next 24 seconds, it descended to 7,500 feet and, within the following 5 seconds, it descended to just above ground level (the ground-based radar altitude readout was 0 feet). The pilot recovered the airplane and climbed it northeast-bound to 1,500 feet during the next 20 seconds. It then likely stalled and descended northwest-bound into shallow waters of a wildlife refuge. Weather radar returns indicated that the airplane's first descent occurred in an area of moderate-to-heavy rain but that the second descent occurred in light rain. The ceiling at the nearest recording airport, located about 20 nautical miles from the accident site, was 1,500 feet, indicating that the pilot likely climbed the airplane back into instrument meteorological conditions (IMC)before finally losing control.

The investigation could not determine the extent to which the pilot had planned the flight. Although a flight plan was on file, the pilot did not receive a formal weather briefing but could have self-briefed via alternative means. The investigation also could not determine when the pilot first lost situational awareness, although the excessive turn to the east toward heavier precipitation raises the possibility that the turn likely wasn't intentional and that the pilot had already lost situational awareness.

Earlier in the flight, when the pilot reported an instrument problem, the two departure controllers coordinated between their sectors in accordance with air traffic control procedures, allowing him to remain low and out of IMC. Although the second controller told the pilot to advise when he was able to climb, the pilot commenced a climb without further comment. The controller was likely under the impression that the instrument problem had been corrected; therefore, he communicated no information about a potential instrument problem to the center controller. The center controller then complied with the level of service required by advising the pilot of the weather conditions ahead and by approving deviations. The extent and nature of the deviation was up to the pilot with controller assistance upon pilot request. The pilot did not request further weather information or assistance with deviations and only told the center controller that the airplane was having an instrument problem after the controller pointed out that the airplane was heading into worsening weather.

Due to impact forces, only minimal autopsy results could be determined. Federal Aviation Administration medical records indicated that the 16,560-hour former military pilot did not have any significant health issues, and the pilot's wife was unaware of any preexisting significant medical conditions.

The wreckage was extremely fractured, which precluded thorough examination. However, evidence indicated that all flight control surfaces were accounted for at the accident scene and that the engines were under power at the time of impact.

The airplane was equipped with redundant pilot and copilot flight instruments, redundant instrument air sources, onboard weather radar, and a storm scope. The pilot did not advise any of the air traffic controllers about the extent or type of instrument problem, and the investigation could not determine which instrument(s) might have failed or how redundant systems could have been failed at the same time. Although the pilot stated on several occasions that the airplane was having instrument problems, he opted to continue flight into IMC. By doing so, he eventually lost situational awareness and then control of airplane but regained both when he acquired visual ground contact. Then, for unknown reasons, he climbed the airplane back into IMC where he again lost situational awareness and airplane control but was then unable to regain them before the airplane impacted the water.

Probable cause

The pilot’s loss of situational awareness, which resulted in an inadvertent aerodynamic stall/spin after he climbed the airplane back into instrument meteorological conditions (IMC). Contributing to the accident was the pilot’s improper decision to continue flight into IMC with malfunctioning flight instrument(s).

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13FA275
Event ID
20130608X41116
Case number
ERA13FA275
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: 9d422f617752785dc49297adbe0e58ecbdee103fe6afdfe8f4ed231da9df6de5; retrieved 2026-09-14T15:58:18.763Z.