Great Lakes Air Piper PA-32-260 accident
Piper PA-32-260 · Accident: loss of control in flight while maneuvering
From Mackinac County Airport (83D) to Mackinac Island Airport (MCD)
Event
- NTSB case
- CEN12FA097
- 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
- 2 · 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
- Charter & commuter
- 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-32-260
- Aircraft type
- Piper PA-32
- 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
- N33315
- Operator
- Great Lakes Air
- Onboard fatalities
- Unknown
- Route
- From Mackinac County Airport (83D), St. Ignace, MITo Mackinac Island Airport (MCD), Mackinac Island, MI
- Aircraft age
- Not recorded
- 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 135: Air Taxi & Commuter
- 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
- 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
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed the mainland to drop a passenger off on an island located about 5 miles off shore. The pilot did not land on the island but was returning to the departure airport with the passenger still on board when the airplane contacted trees and terrain about 1.4 miles north of the departure airport. According to witnesses and weather observations, instrument meteorological conditions prevailed at both the departure and destination airports around the time of the accident, including rain and fog conditions. The flight was being operated under night visual flight rules. The accident site was located between a brightly lit casino/hotel resort and the airport. The pilot most likely located the casino/hotel and was following the shoreline back to the airport when the accident occurred. A witness reported hearing the airplane before the impact. No preaccident mechanical failures or malfunctions with the airplane were identified that would have precluded normal operation.
Probable cause
The pilot’s decision to initiate visual flight in instrument meteorological conditions and subsequent failure to maintain adequate altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12FA097
- Event ID
- 20111204X50348
- Case number
- CEN12FA097
- 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 2011-12-04.
- API snapshot SHA-256: 6d116bc2c88ac0db599fede3c496bac876186012eab6d77efb0e8befb08cc63b; retrieved 2026-09-13T22:02:38.760Z.