FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23FA181 · Piper PA32R 300

5 Apr 2023 · Venice, FL, United States

Piper PA32R 300 · Accident: loss of control in flight during initial climb

From Venice Municipal Airport (VNC) to Albert Whitted Airport (SPG)

Report a problem

Event

NTSB case
ERA23FA181
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

Piper PA32R 300

Aircraft type
Piper PA32
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
N635BD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Venice Municipal Airport (VNC), Venice, FLTo Albert Whitted Airport (SPG), St. Petersburg, FL
Aircraft age
About 47 years (built 1976)
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 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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

After flying into a coastal airport and having dinner, the instrument-rated commercial pilot conducted a night visual flight rules (VFR) departure over an oceanic basin. Witnesses reported seeing the airplane take off; shortly after takeoff, the airplane entered a right turn before it descended into the water. ADS-B track data indicated that the airplane took off and climbed on the runway heading to an altitude of about 300 ft as it maintained a ground speed of about 103 knots. The airplane then began to turn to the right and began to descend. The last data depicted the airplane at 100 ft, with a ground speed of about 136 knots and a vertical descent rate of 3,008 feet per minute. At the time of departure, dark night conditions prevailed, the winds were calm, and there was 10 miles of visibility with clear skies. Astronomical data indicated that, although the moon was full and moonrise had occurred, the moon was low on the eastern horizon, behind and to the left of the airplane, and there would not have been any visible horizon over the water. Examination of the wreckage revealed no evidence of preimpact mechanical malfunctions or failures with the airplane or instruments. The airplane was equipped with an autopilot with an attitude recovery function; however, the autopilot was limited to operations over 500 ft above ground level which was about 200 ft higher than the airplane’s peak altitude. The autopilot On/Off switch was found in the Off position. Due to the pilot’s heart disease, the pilot was at an increased risk of a sudden distracting, impairing, or incapacitating cardiac event, including angina, arrhythmia, or heart attack. However, there was no forensic evidence that such an event occurred. Ethanol was detected in the pilot’s cavity blood at a very low level and was not detected in vitreous fluid. Some or all of the detected ethanol may have been from postmortem production. It is unlikely that ethanol effects contributed to the accident. The pilot had diabetes and the postmortem vitreous level of glucose was elevated, as was the hemoglobin A1c (HbA1c). The pilot’s elevated HbA1c was consistent with uncontrolled diabetes over the previous several months. Short-term effects of high blood sugar may include decreased cognitive performance, including slower informational processing speed and decreased executive function and attention. Chronic high blood glucose levels can lead to vision complications and an increased risk of cardiovascular disease. Whether the pilot’s uncontrolled diabetes caused such symptoms or contributed to the accident could not be determined. Based upon track, meteorological, and astronomical data, the pilot initiated a VFR flight into known dark night conditions, without a visible horizon, which would have prevented reliable control of the airplane using only external visual cues. The turning and rapidly descending flight track were consistent with a pilot who was experiencing spatial disorientation, which resulted in a loss of control in flight and an impact with water. The pilot’s instrument and night currency could not be determined.

Probable cause

The pilot’s decision to initiate a visual flight rules flight into dark night conditions, which resulted in spatial disorientation during the initial climb and subsequent steep banking descent into water.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23FA181
Event ID
20230406107016
Case number
ERA23FA181
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2023-04-06.
  • API snapshot SHA-256: 8a61c80bb16e24469cf4f2608bd9478c96c760fcce90ab71b4f613f64fca1047; retrieved 2026-09-15T07:58:28.753Z.