FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA17FA088 · Sharpe William L BUCCANEER II B

14 Jan 2017 · Mayo, FL, United States

Sharpe William L BUCCANEER II B · Accident: low altitude operation/event while maneuvering

From Mayo, FL to Mayo, FL

Report a problem

Event

NTSB case
ERA17FA088
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
Visual Meteorological Cond

Sharpe William L BUCCANEER II B

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
N696FT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mayo, FLTo Mayo, FL
Aircraft age
About 25 years (built 1992)
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
Maneuvering · low-altitude flying
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
Low altitude operation/event
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Environmental issues › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Psychological

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

NTSB narrative

The sport pilot of the experimental, amateur-built, amphibious airplane flew to meet a friend to camp for the night along a river. He landed on the river to the north, flying over power lines during the landing approach, and pulled the airplane onto the shore. The pilot offered to help his friend search for a life vest that had floated downstream after he finished unloading the gear from the airplane. Multiple witnesses watched as the pilot departed northbound on the river, made a 180° turn southbound, then flew over the river, beneath treetop level, and out of sight. They reported hearing a loud "boom" and the engine noise stop just before a power outage occurred. One witness reported seeing the airplane flying 30-40 ft above the river when it "suddenly flipped backwards and then hit the water." One witness reported that the sky was grey and overcast, and that the sun was setting about the time of the accident, making the power lines difficult to see. The powerlines directly overhead of the accident site displayed striations consistent with the airplane impacting the powerlines.

Examination of the wreckage revealed no evidence of a preexisting anomaly or malfunction that would have precluded normal operation. Toxicology testing on the pilot detected two medications, which were unlikely to have caused impairment, and the autopsy revealed an enlarged heart; however, there was no evidence of a heart attack or any other incapacitating event. It is likely that, while flying along the river at low altitude, the pilot failed to see the powerlines, which resulted in an in-flight collision with the powerlines and impact with the river.

Probable cause

The pilot's failure to see and avoid power lines while flying at low altitude.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA17FA088
Event ID
20170114X83817
Case number
ERA17FA088
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, coordinates. 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: 576f3f4ed9d46947c8400f5ae4df91362b3b680cfaca47382aaf977ec7c959ed; retrieved 2026-09-14T22:07:09.526Z.