Piper PA28 accident near Venice, Florida, July 27, 2014
On July 27, 2014 at about 6:45 pm local time, a 1976 Piper PA28, registered N8826C, was substantially damaged in an accident during enroute near Venice, Florida. It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A total loss of engine power for reasons that could not be determined because postaccident examination of the engine revealed no mechanical malfunctions or failures that would have precluded normal operation. Contributing to the accident was the pilot’s failure to identify occupants on the ground near the shoreline in the airplane’s forced landing path.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 27, 2014 · about 6:45 pm local time
- Place
- Venice, Florida · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA28 181, built 1976 · all PA28s on the register
- Registration
- N8826C · no longer on the register · serial 28-7690168
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot was conducting a short flight from one airport to another airport to obtain fuel for the airplane. The pilot reported that the airplane had been kept in a hangar and had not been flown in the preceding 3 1/2 months. The pilot performed a preflight inspection of the airplane and noted the fuel quantity but he did not sump the fuel tanks. He subsequently performed an engine run-up and departed without incident. He climbed the airplane to about 1,000 ft and, after some maneuvering, eventually flew over the water and paralleled a shoreline toward another airport. The pilot reported that the engine then began to run roughly and that he heard a "missing, knocking, hitting sound" but that neither he nor the pilot-rated passenger noted a decrease in engine rpm. Although the pilot rotated the ignition switch through the various positions and changed fuel tanks, the engine lost power and the propeller began wind-milling. The pilot declared an emergency and angled the descending airplane toward the shoreline. He was concerned that, if he landed in deeper water, the fixed-landing-gear airplane would flip over. The pilot saw a group of people along the beach and attempted to navigate around them. He then aimed for a spot where he thought there were no people, and the airplane touched down in the water near the shoreline and then came to rest on the sand near the water's edge. The pilot exited the airplane and learned that he had struck two people in the water. Postaccident examination of the airframe and engine, which included a successful engine test run using fuel from the airplane's fuel system, did not reveal any evidence of water contamination or mechanical malfunctions or failures that would have precluded normal operation. Given this evidence, the loss of engine power was likely a transient condition. Although the condition could have resulted from pilot action, neither the pilot nor the passenger indicated that the pilot took any action that would have resulted in the loss of engine power. Although the airplane was operating in conditions that were conducive to the formation of carburetor ice without the carburetor heat on, the fixed-pitch propeller/engine combination did not gradually lose rpm, which would have occurred if carburetor ice had developed. Therefore, the reason for the loss of engine power could not be determined. The National Transportation Safety Board asked the Federal Aviation Administration (FAA) to provide information on any policy that addressed protecting people on the ground during a loss of engine power. The FAA responded, in part, "Because of the variety of possible emergency situations, it is impractical to apply a specific policy addressing risks involved between beach landings and ditching. The FAA relies on its requirements for pilot training on aeronautical decision making to compel pilots to pursue courses of action in an emergency which appear to be the safest and most appropriate under the circumstances." Once the engine failed, the pilot chose to land on a shoreline area that he incorrectly believed was unoccupied.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (total) during enroute defining event
- Off-field or emergency landing during emergency descent
- Miscellaneous/other during landing
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
- factor Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 203 hours in all; 74 in this make and model; 0 in the last 90 days; 172 as pilot in command
- Last flight review: February 11, 2013
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 1,902 hours
- Last inspection: annual inspection, February 17, 2014; 10 hours since
- Maximum gross weight: 2,550 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-360 SER (piston); 1,902 hours total
The flight
- Departed from: X36 Englewood FL at 6:30 pm
- Destination: VNC Venice FL
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 260° at 9 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 90°F (32°C), dew point 75°F (24°C)
- Altimeter: 30.10 inHg
- Observation at 6:55 pm from VNC, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
13 documents, released by the NTSB on February 27, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 13 pages | View Download |
| 2 | Excerpt, Sarasota County Sheriffs Office/faa Passenger Interview | PDF, 13 pages | View Download |
| 3 | Memorandum for Record - FAA Inspector Notes | PDF, 1 page | View Download |
| 4 | Memorandum for Record - FAA Inspector Conversation | PDF, 2 pages | View Download |
| 5 | Memorandum for Record - Preflight Inspection | PDF, 2 pages | View Download |
| 6 | Unicom Operator Statement | PDF, 1 page | View Download |
| 7 | FAA Policy Memorandum | PDF, 2 pages | View Download |
| 8 | Pilot's Operating Handbook Fuel Excerpt | PDF, 1 page | View Download |
| 9 | FAA Inspector's Interview of Victims' Family | PDF, 1 page | View Download |
| 10 | Memorandum for Record - Preliminary Information | PDF, 2 pages | View Download |
| 11 | Statement of Party Representatives to NTSB Investigation | PDF, 2 pages | View Download |
| 12 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
| 13 | Photo Array | PDF, 6 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
