FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Great Lakes Air Piper PA 28 140 accident

26 Feb 2018 · Mackinac Island, MI, United States

Piper PA 28 140 · Accident: part(s) separation from aircraft on approach

From Mackinac County Airport (83D) to Mackinac Island Airport (KMCD)

Report a problem

Event

NTSB case
CEN18LA112
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
0 · 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
Visual Meteorological Cond

Piper PA 28 140

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
N1722J
Onboard fatalities
Unknown
Route
From Mackinac County Airport (83D), Saint Ignace, MITo Mackinac Island Airport (KMCD), Mackinac Island, MI
Aircraft age
About 50 years (built 1968)
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
Approach · VFR pattern final
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
Part(s) separation from aircraft
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 systems
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During the final approach for the short cross country flight, the pilot heard a "thud." During the landing flare the pilot suspected a landing gear issue and landed as gently as possible. However, the right wing settled onto the runway and was substantially damaged. A postaccident examination revealed that the landing gear had not been reinstalled correctly during maintenance performed in 2013. Only one of the 8 fasteners required for installation was recovered and it was sheered. The damage to the wing and landing gear was consistent with the improper installation of the fasteners and was not impact related. It is likely that the fasteners were either not installed or not torqued properly during the previous maintenance. Subsequent annual and 100-hour inspections did not detect this discrepancy.

Probable cause

The improper reinstallation of the right main landing gear by maintenance personnel which resulted in the separation of the landing gear and the subsequent abnormal runway contact during the landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18LA112
Event ID
20180301X65123
Case number
CEN18LA112
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. 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: 59135cd195e59ee35bb6ab9ba2f2a32e1c20417e202fe976881477a2f0478f62; retrieved 2026-09-16T06:33:28.915Z.