ERA14LA117 · Piper PA-28-161
Fishe Flying Piper PA-28-161 · Accident: loss of control in flight en route
From Florida Keys Marathon International Airport (MTH) to Vero Beach Regional Airport (VRB)
Event
- NTSB case
- ERA14LA117
- 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
Piper PA-28-161
- Aircraft type
- Piper PA-28
- 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
- N2571U
- Operator
- Fishe Flying
- Onboard fatalities
- Unknown
- Route
- From Florida Keys Marathon International Airport (MTH), Marathon, FLTo Vero Beach Regional Airport (VRB), Vero Beach, FL
- Aircraft age
- About 35 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
- 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 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 › Action/decision
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the operator/owner, the noninstrument-rated pilot was visiting the United States on vacation and had rented the airplane for about 1 week. The pilot planned a day trip to an airport located about 2.5 hours from the airplane's home base, and the accident occurred on the return leg. After departing on the return leg, the pilot contacted air traffic control and requested flight-following services for the planned flight route, which was just offshore of the southeastern coast of Florida. About 1.5 hours into the flight and almost 1 hour after sunset, the accident pilot heard another pilot, who was operating on the same radio frequency, request an instrument flight rules clearance to an airport that was between the accident pilot's position and his intended destination. The accident pilot then requested an update of the current weather conditions at his destination, and an air traffic controller advised that an overcast ceiling of 600 ft prevailed. When the pilot requested the weather conditions for a slightly closer airport, the controller advised that there were scattered clouds at 700 ft and an overcast ceiling at 1,000 ft. The pilot subsequently advised the controller that he intended to divert the flight to the closer airport.
As the flight continued, the pilot discussed the weather conditions with an air traffic controller, noting that the cloud ceiling was "pretty low" and that he couldn't "get a real handle on the ceiling." The controller then asked the pilot what altitude he could maintain, and he responded "700 ft." After transitioning to an area without low-altitude radar coverage, the pilot advised that he was flying at an altitude of 450 ft. An air traffic controller then advised the pilot that flight-following services were not available at that altitude, and, after flight-following services were terminated, no further radio communications were received from the pilot.
The operator reported the airplane missing when it did not return later that evening as scheduled, and personal effects and airplane wreckage began washing ashore the following morning in the vicinity of the flight's last known position. No radar coverage was available in the area where the accident likely occurred; therefore, the exact sequence of events that resulted in the airplane's ultimate impact with water could not be determined. However, the condition of the recovered wreckage was consistent with water impact at a significant velocity.
The weather forecast at the pilot's original destination airport at the time of his departure indicated that marginal visual meteorological conditions (VMC) would prevail at the time of his anticipated arrival. As the flight progressed, the conditions en route and at the destination eventually deteriorated below VMC, and, as noted, the pilot discussed the deteriorating weather conditions with the air traffic controller several times. Although the reported visibilities in the area were favorable, the flight was conducted on a dark, moonless night under an overcast ceiling, over the ocean, and off a relatively sparsely populated area of the coast. These factors would have reduced the pilot's ability to perceive the natural horizon and increased his risk of losing airplane control due to spatial disorientation. The pilot might have reduced this risk by diverting the flight earlier to a destination with more favorable weather and lighting conditions. However, the pilot ultimately chose to divert to an airport that was only slightly closer than his original destination, which reported weather conditions at visual flight rules minimums. At the time of the actual diversion, the airplane was passing within 4 nautical miles of a large international airport, which at the time was reporting a cloud ceiling higher than 4,000 ft. Even after this point, the pilot could have chosen to turn around and return to this airport rather than continuing the flight into deteriorating conditions.
Probable cause
The noninstrument-rated pilot’s continued flight into dark night, instrument meteorological conditions, which resulted in a loss of control due to spatial disorientation and subsequent impact with water.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14LA117
- Event ID
- 20140211X72802
- Case number
- ERA14LA117
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2014-02-08.
- API snapshot SHA-256: c848d61758aa1f57f486eee657da61dbbbe4778c979b854d3de464aa45a9b7ce; retrieved 2026-09-14T16:10:27.958Z.