FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24LA342 · Piper PA-28R 200

4 Sept 2024 · Crystal, MN, United States

Piper PA-28R 200 · Accident: system/component malfunction/failure (non-power) during landing

From Crystal Airport (MIC) to Crystal Airport (MIC)

Report a problem

Event

NTSB case
CEN24LA342
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
0
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 PA-28R 200

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
N4081S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Crystal Airport (MIC), Crystal, MNTo Crystal Airport (MIC), Crystal, MN
Aircraft age
About 50 years (built 1974)
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
Landing · flare/touchdown
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
System/component malfunction/failure (non-power)
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 structures

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

NTSB narrative

During the landing flare, the airplane encountered a gust of wind, climbed about 3 ft, and landed on the runway centerline. The pilot described the landing as firm, but not hard. The airplane was refueled and returned to the hangar with no issues. The next day, the pilot’s son flew the airplane. The pilot’s son performed a preflight inspection with no anomalies noted. After the takeoff, he retracted the landing gear, and he noticed that the “gear in transit” light stayed illuminated. He extended the landing gear, and all three green landing gear lights were illuminated. The pilot’s son landed back at the airport and taxied back to the hangar with no issues. The following day, the pilot’s son flew the airplane to another airport to have a mechanic inspect it. A postflight inspection by the mechanic revealed that the engine mount had fractured at the nose gear attachment point. The airplane’s engine mount sustained substantial damage. Postaccident examination revealed that the engine mount likely failed under normal operating loads due to the fracture of a vertical tube that was weakened by corrosion and fatigue cracks. The corrosion occurred on the interior surface of the vertical tube, likely due to the presence of water and greasy deposits at the lower end of the tube. Although the corrosion damage had likely been developing for an extended time, it would not have been detectable by visual inspection. The corrosion damage included a loss of wall thickness that increased the average stress in the remaining cross-section, and local stresses were further increased by rough surfaces and pits that formed during the corrosion process. As a result, fatigue cracks initiated and grew from multiple origins at the corroded surface. Although the total extent of fatigue cracking could not be determined due to post-fracture damage, it is likely that the tube was weakened sufficiently from the combination of wall thickness loss and fatigue crack growth to cause failure under normal loading conditions. The corrosion and fatigue cracks at the lower end of the tube were secondary to another failure that could not be determined from the examined pieces. Although an incomplete weld or service damage such as a crack or hole in the tube could have allowed water to seep into the tube bore, causing the tube to corrode from the inside out, no such anomalies or cracks were observed below the cut location.

Probable cause

The failure of the engine mount under normal operating loads due to the fracture of a vertical tube that was weakened by corrosion and fatigue of the internal surfaces.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24LA342
Event ID
20240907195075
Case number
CEN24LA342
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, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2024-09-05.
  • API snapshot SHA-256: c85909fcd1192cf0d7901a46b7b93165dcedf2ce5a13fae0da3e3a2aa90b6820; retrieved 2026-09-16T19:14:34.714Z.