# Accident 20260623007739A: Piper PA-12, Dixie, ID, June 23, 2026

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 23, 2026, 09:30 local time
- Place: Dixie, ID
- Airport: Wilson Bar Usfs
- Damage: Substantial damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 45.3967° N, 115.4833° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=45.3967&lon=-115.4833&mi=10
- Aircraft: N3013M, registered now (https://openairdocs.org/aircraft/N3013M) (OpenAirDocs)
- Registry model: Piper PA-12 (registry code 7101202, https://openairdocs.org/model/piper-pa-12) (OpenAirDocs)
- Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs)
- Reported make and model: PIPER PA-12
- Reported engine: LYCOMING 0-235 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport, flight instructor
- Pilot flight hours: 24,284 total, 81 in this make and model, 33 in the last 90 days
- NTSB investigation: [NTSB WPR26LA234](https://openairdocs.org/ntsb/WPR26LA234) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20260623007739A

## Narrative

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

ACCORDING TO THE PILOT:

I DEPARTED FOR THE MCCALL, ID AIRPORT (KMYL) AROUND 7 AM FOR FUEL AND BREAKFAST. I DEPARTED MCCALL AROUND 9:00 AM WITH THE INTENTION OF LANDING AT WILSON BAR USFS STRIP (C48), STOPPING BRIEFLY, THEN RETURNING TO JOHNSON CREEK BEFORE THE TEMPERATURES INCREASED. AFTER CLIMBING TO 9,500 FT I JOINED A COURSE NORTHEAST BOUND ABOVE THE SOUTH FORK OF THE SALMON RIVER IN SMOOTH AIR AND CLEAR SKIES.

ONCE OVER THE RIVER, I DESCENDED TO 5,500FT AND TRANSITED TO WILSON BAR. I CROSSED OVER WILSON BAR AND MADE A LEFT 360 DEGREE TURN TO LOSE ALTITUDE AND JOIN A RIGHT BASE FOR RUNWAY 24. I REALIZED I WOULD NOT BE ABLE TO STOP ON THE RUNWAY SO I INITIATED A GO-AROUND. I BEGAN A CLIMBING RIGHT TURN IN AN EFFORT TO FLY BETWEEN THE TREES THAT LINED THE NORTH SIDE OF THE RUNWAY AND THE TERRAIN. UNFORTUNATELY, MY CLIMB PERFORMANCE WAS INSUFFICIENT AND IT BECAME CLEAR THAT I WOULD BE UNABLE TO SAFELY COMPLETE THE GO-AROUND AND EXECUTED A FORCED LANDING ON THE UPWARD SLOPE OF THE RISING TERRAIN AT ABOUT 40 MPH. THE TIRES AND LANDING GEAR ABSORBED MOST OF THE IMPACT THEN THE AIRCRAFT SUBSEQUENTLY ROLLED OVER. I QUICKLY EXITED THE AIRCRAFT WITH NO INJURIES.

END

## 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 WPR26LA234](https://openairdocs.org/ntsb/WPR26LA234), Jun 23, 2026: Piper PA-12 (N3013M), Dixie, ID, substantial damage. Probable cause: The pilot's delayed decision to initiate a go-around and subsequent failure to maintain clearance from rising terrain.

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.