The U.S. aircraft register, updated daily
Accidents · NTSB CEN24LA342 · Final report

Piper PA-28R accident near Crystal, Minnesota, September 5, 2024

On September 5, 2024, a 1974 Piper PA-28R, registered N4081S, was substantially damaged in an accident during landing (flare/touchdown) near Crystal, Minnesota (Crystal airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 5, 2024
Place
Crystal, Minnesota · Crystal · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28R 200, built 1974 · all PA-28Rs on the register
Registration
N4081S · registry record · serial 28R-7435130
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Sys/Comp malf/fail (non-power) during landing (flare/touchdown) defining event

The NTSB's findings

  • Aircraft › Aircraft structures › Fuselage › Engine attach fitting (on fus) › Fatigue/wear/corrosion
  • Aircraft › Aircraft structures › Fuselage › Engine attach fitting (on fus) › Damaged/degraded

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 425 hours in all; 182 in this make and model; 20 in the last 90 days; 14 in the last 30 days; 334 as pilot in command
  • Last flight review: April 21, 2024
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,578.3 hours
  • Last inspection: annual inspection, November 8, 2023; 132.7 hours since
  • Maximum gross weight: 2,650 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming Engines IO-360-C1C (piston); 3,711 hours total

The flight

  • Departed from: MIC Crystal MN
  • Destination: MIC Crystal MN
  • Flight plan: none
  • Runway 14/3, 3,751 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 160° at 10 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 75°F (24°C), dew point 57°F (14°C)
  • Altimeter: 30.03 inHg
  • Observation at 7:53 pm from KMIC

Weather report (METAR): KMIC 050053Z 17009KT 10SM CLR 24/14 A3003 RMK AO2 SLP164 T02390144

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

10 documents, released by the NTSB on November 5, 2025. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.