# NTSB CEN24LA342: Piper PA-28R, N4081S, Crystal, MN, September 5, 2024 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 3 · Limited · Final report - Date: September 4, 2024, 19:50 local (Sep 5, 2024, 00:50 UTC) - Place: Crystal, MN - Coordinates: 45.064699, -93.356552 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=45.0647&lon=-93.3566&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report November 5, 2025 - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Central Region - Parties: Piper Aircraft, FAA Minneapolis FSDO - NTSB case key (mKey): 195075 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN24LA342 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/195075/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=195075 - Page: https://openairdocs.org/ntsb/CEN24LA342 ## 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Fuselage: engine attach fitting (on fus)](https://openairdocs.org/ntsb-findings/01035346): Aircraft › Aircraft structures · Fatigue/wear/corrosion (probable cause); cases with it: [Piper PA-28R-200, 1 case](https://openairdocs.org/ntsb-findings/01035346/cases.md?model=7102811), [All aircraft, 2 cases](https://openairdocs.org/ntsb-findings/01035346/cases.md) - [Fuselage: engine attach fitting (on fus)](https://openairdocs.org/ntsb-findings/01035346): Aircraft › Aircraft structures · Damaged/degraded (probable cause); cases with it: [Piper PA-28R-200, 1 case](https://openairdocs.org/ntsb-findings/01035346/cases.md?model=7102811), [All aircraft, 2 cases](https://openairdocs.org/ntsb-findings/01035346/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330) (defining event); cases with it: [Piper PA-28R-200, 5 cases](https://openairdocs.org/ntsb-events/330/sequence.md?model=7102811), [All aircraft, 994 cases](https://openairdocs.org/ntsb-events/330/sequence.md) ## Analysis 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. ## Factual narrative On September 4, 2024, about 1950 central daylight time, a Piper PA-28R-200 airplane, N4081S, sustained substantial damage when it was involved in an accident near Crystal, Minnesota. The pilot was uninjured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot performed a preflight inspection on the airplane with no anomalies noted. The airplane departed from the Crystal Airport (MIC), Crystal, Minnesota, for a local area flight. As the pilot returned to MIC, he completed the before-landing checklist and was cleared to land by air traffic control. 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. He performed a preflight inspection with no anomalies noted. After takeoff, he retracted the landing gear and 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 to MIC and taxied back to the hangar with no issues. The following day, the pilot’s son flew the airplane from MIC to the Rochester International Airport (RST), Rochester, Minnesota, to have a mechanic inspect it. The pilot’s son flew the airplane from MIC to RST with the landing gear extended the whole flight and landed and taxied at RST without incident. A post-flight inspection by the mechanic revealed a fractured engine mount at the nose gear attachment point. The airplane’s engine mount, Piper part number 67119-57, sustained substantial damage. The engine mount was not serialized. Postaccident examination of the engine mount revealed that the fracture surface generally showed substantial damage from oxidation and post-fracture contact. Greasy deposits were observed covering the black painted surfaces over most of the fractured tube’s exterior surface. On the interior of the fractured tube, an accumulation of greasy, mostly black deposits of corrosion products and other debris was observed inside the tube piece. Areas with relatively flat features in planes perpendicular to the tube axis were observed in several locations, mostly on the left half of the fracture. Additional features including radial lines and ratchet marks were also observed in these areas emanating from the interior edge of the fracture. These fracture features were consistent with fatigue initiating from corrosion pits at the interior surface of the tube. Each fatigue region had multiple origins. The fatigue regions appeared to extend through the wall thickness on the aft left and forward left portions of the fracture. At the forward right side of the fracture, the fatigue region extended part way through the thickness. An area on the left side of the fracture was smeared from post-fracture damage, so thefracture mechanism was undetermined in that area. The remainder of the fracture surface outside of the fatigue boundary and to the right of the fatigue regions had rough features on slant angles consistent with ductile overstress fracture. At the time of the accident, the airframe, which was manufactured in 1974, had accumulated 3,711 hours. The most recent annual inspection on the airframe was completed on November 8, 2023. ## Aircraft - Registration: [N4081S](https://openairdocs.org/aircraft/N4081S), registered now, S/N 28R-7435130, built 1974 (OpenAirDocs) - Reported make and model: PIPER PA-28R (200) - Registry model: [Piper PA-28R-200](https://openairdocs.org/model/piper-pa-28r-200) (registry code 7102811) (OpenAirDocs) - Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28R-7435130 - Year built: 1974 - Airframe hours: 3578.29 - Engines: Lycoming Engines IO-360-C1C 200 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, November 8, 2023, 132.71 hours before - Departed: MIC, Crystal, MN - Destination: MIC, Crystal, MN - Airport: MIC, Crystal, runway 14/32, 3,751 × 75 ft, asphalt - Equipment: ADS-B, Auto-pilot, Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 63; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review April 21, 2024; seat: left; restraint: 3-point; flight hours: 425 total, 182 in this make and model, 334 as pilot in command, 20 in the last 90 days, 14 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 160° at 10 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 75 °F, dew point 57 °F - Altimeter: 30.03 inHg - Observed at: KMIC - METAR: KMIC 050053Z 17009KT 10SM CLR 24/14 A3003 RMK AO2 SLP164 T02390144 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20240904014229A](https://openairdocs.org/incident/20240904014229A), Sep 4, 2024: Piper PA-28R-200, Crystal, MN, Substantial damage. While landing at the pic’s home airport after a 50-minute flight a wind gust caught the aircraft resulting in a 3–4-foot rise. The PIC continued to land and… ## Other investigations on N4081S (2) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB ANC81DAG07](https://openairdocs.org/ntsb/ANC81DAG07), Oct 17, 1980: Piper PA-32 (N4081S), Simeonof Is, AK, substantial damage - [NTSB NYC78DHA13](https://openairdocs.org/ntsb/NYC78DHA13), Jan 30, 1978: Piper PA-28R (N4081S), E. Stroudsburg, PA, substantial damage ## Docket (10 files) The files NTSB released with the investigation on November 5, 2025, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=195075. 26.1 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 9 pages, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19105611&FileExtension=pdf&FileName=NTSB%20Form%206120_1_Redacted-Rel.pdf - Investigation photographs (item 2, PDF, 4 pages, 538 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19119435&FileExtension=pdf&FileName=Investigation%20Photographs-Rel.pdf - Materials laboratory factual report 25-004 (item 3, PDF, 10 pages, 11 photos, 2.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18319302&FileExtension=pdf&FileName=25-004-Rel.pdf - N4081S - engine mount information (item 4, PDF, 1 page, 65 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19273158&FileExtension=pdf&FileName=CEN24LA342%20Engine%20Mount%20Information-Rel.pdf - N4081S - recent airframe maintenance records (item 5, PDF, 5 pages, 10.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19124290&FileExtension=pdf&FileName=Airframe%20Maintenance%20Records_Redacted-Rel.pdf - N4081S - recent engine maintenance records (item 6, PDF, 2 pages, 4.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19124366&FileExtension=pdf&FileName=Engine%20Maintenance%20Records_Redacted-Rel.pdf - N4081S - recent propeller maintenance records (item 7, PDF, 2 pages, 5.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19124300&FileExtension=pdf&FileName=Propeller%20Maintenace%20Records_Redacted-Rel.pdf - Piper aircraft - service manual excerpt (item 8, PDF, 6 pages, 632 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19120179&FileExtension=pdf&FileName=753-586%20Cherokee%20Service%20Manual%20-%20Engine%20Mount-Rel.pdf - Piper aircraft - airplane parts catalog excerpt (item 9, PDF, 9 pages, 133 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19119932&FileExtension=pdf&FileName=753-582%20Cherokee%20IPC%20-%20Engine%20Mount-Rel.pdf - Statement of party representatives to NTSB investigation (item 10, PDF, 1 page, 192 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19105964&FileExtension=pdf&FileName=CEN24LA342%20Party%20Member%20Form%20-%20Piper%20Aircraft_Redacted-Rel.pdf From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.