FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18FA368 · Piper PA32RT 300T

31 Aug 2018 · St Ignace, MI, United States

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

From Mackinac County Airport (83D) to Burlington Municipal Airport (BUU)

Report a problem

Event

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

Piper PA32RT 300T

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
N500MJ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mackinac County Airport (83D), St Ignace, MITo Burlington Municipal Airport (BUU), Burlington, WI
Aircraft age
About 40 years (built 1978)
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

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

NTSB narrative

The instrument-rated pilot took off in dark night conditions over a lake that bordered the departure end of the runway. The airport manager witnessed the airplane depart and reported that the takeoff sounded normal. Two witnesses who were facing the lake reported that they observed an aircraft take off from the airport, and fly about 100 to 200 ft above the lake surface. It then banked to the right and disappeared from sight. About 10 to 15 seconds later, the witnesses heard what sounded like a crash into the water or an explosion. There were no distress radio calls from the pilot and there was no radar information for the flight. The airport manager and first responders reported that it was a very dark night and that there was no distinguishable horizon.

Examination of the airframe and engine did not reveal any preimpact anomalies that would have precluded normal operation, and evidence was consistent with a slight right wing down, nose low, high speed impact with the water. A right turn would have been necessary at some point after takeoff to fly towards the destination airport and evidence is consistent that a right turn had been initiated. Although the reason for the impact with the water could not be determined, the overwater departure in dark night conditions would not have provided adequate visual cues to assure a positive rate of climb during the departure and initial turnout on course as a pilot would be vulnerable to illusions if flight instruments were not used to conduct the takeoff and initial climb.

Probable cause

The pilot's failure to maintain sufficient altitude after takeoff in dark night conditions which resulted in a collision with the water.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18FA368
Event ID
20180904X04313
Case number
CEN18FA368
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 2018-09-01.
  • API snapshot SHA-256: b326ef9834fe7ed51bf4ae933a83f5622aeea6603f30682bd65ea4da35f1b9ed; retrieved 2026-09-15T06:47:32.444Z.