# Accident 20250307005209A: Piper PA-32-300, Redding, CA, March 7, 2025

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 7, 2025, 19:10 local time
- Place: Redding, CA
- Airport: Redding Municipal
- Damage: Substantial damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 40.5073° N, 122.2989° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.5073&lon=-122.2989&mi=10
- Aircraft: N32371, a cancelled registration (https://openairdocs.org/deregistered/N32371-2025-12-03) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA-32-300
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 603 total, 134 in this make and model, 61 in the last 90 days
- NTSB investigation: [NTSB ANC25LA032](https://openairdocs.org/ntsb/ANC25LA032) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20250307005209A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON 03/07/2025 @ 19:10 LOCAL TIME THE AIRCRAFT SUFFERED A HARD LANDING ON RUNWAY 34 AT REDDING AIRPORT (RDD). FROM EXAMINATION OF THE ACCIDENT SCENE ON 03/25/25, THE AIRCRAFT MADE INITIAL CONTACT WITH RUNWAY 34 APPROXIMATLEY 35FT TO THE LEFT SIDE OF THE CENTERLINE AND DOWN THE RUNWAY APPROXIMATLEY 1250FT FROM THE END OF THE THRESHOLD LINES. THE AIRCRAFT THEN REBOUNDED FOR APPROXIMATLEY 150FT AND STRUCK THE RUNWAY A SECOND TIME AT THE END OF THE FIRST 500 FT MARKER SKIDDING APPROXIMATELY 350FT TO REST ON THE LEFT SIDE OF THE RUNWAY. MARKS LEFT ON THE RUNWAY INDICATE THAT THE NOSEWHEEL PARTIALLY COLLAPSED ON INITIAL IMPACT AND COMPLETELY COLLAPSED ON SECONDARY IMPACT LEADING TO THE PROPELLER STRIKING THE GROUND. THE PILOT STATED THAT HE MAINTAINED A STABILIZED APPROACH, BUT AT ABOUT 200 FEET ABOVE THE RUNWAY HE EXPERIENCED WINDSHEAR CAUSING A LOSS OF CONTROL OF THE AIRCRAFT.

## The NTSB's investigation of this event (1)

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 ANC25LA032](https://openairdocs.org/ntsb/ANC25LA032), Mar 8, 2025: Piper PA-32-300 (N32371), Redding, CA, substantial damage. Probable cause: The pilot's failure to maintain a stabilized approach and his delayed action to perform a go-around, resulting in a collision with the runway surface.

## Other reports on N32371 (1)

Matched to the same aircraft by N-number and date.

- [Incident 19930126003249I](https://openairdocs.org/incident/19930126003249I), Jan 26, 1993: Piper PA32300 (N32371), Oakland, CA. Loss of engine power in traffic pattern. Landed safely. Found loose pipe plug fitting in fuel tank. Block fuel.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.