Piper PA-28-235 accident near Shafter, California, February 9, 2025
On February 9, 2025 at about 7:15 pm local time, a 1959 Piper PA-28-235, registered N8535N, was substantially damaged in an accident during approach near Shafter, California (Shafter-Minter Fld airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 9, 2025 · about 7:15 pm local time
- Place
- Shafter, California · Shafter-Minter Fld · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28-235 D, built 1959 · all PA-28-235s on the register
- Registration
- N8535N · registry record · serial 28-11334
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On February 9, 2025, about 1115 Pacific standard time, a Piper PA-28-235, N8535N, was substantially damaged when it was involved in an accident near Shafter, California. The student and flight instructor were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. The student pilot reported that while on final approach to runway 30 at Shafter- Airport-Minter Field (MIT), Shafter, California, the engine lost power at about 400 ft above ground level. The flight instructor took control of the airplane, performed the power loss in flight checklist and attempted to restart the engine, but was unsuccessful. The flight instructor initiated a forced landing to an open field about 1 mile south of runway 30. During the landing roll, the airplane nosed over which resulted in substantial damage to the left wing and vertical stabilizer. The airplane was recovered to a secure location for further examination.
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
- Loss of engine power (total) during approach defining event
The aircraft
- Airframe total time: 1,275.6 hours
- Last inspection: annual inspection, August 2, 2024
- Maximum gross weight: 2,900 lb
- Seats: 4
- Landing gear: fixed
The flight
- Flight plan: none
- Runway 12/3, 4,501 ft by 100 ft
Weather at the time
- Light: daylight
- Visibility: 8 statute miles
- Sky: clear at 4,000 ft
- Temperature: 52°F (11°C), dew point 41°F (5°C)
- Altimeter: 30.21 inHg
- Observation at 10:54 am from KBFL, 8 miles away
Weather report (METAR): KBFL 091854Z 17004KT 8SM CLR 11/05 A3021 RMK AO2 SLP229 T01060050
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
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.