Piper PA-12 N7510H accident near Joshua Tree, California

Jul 18, 2011 · NTSB number WPR11FA334 · Final report

Probable cause

The pilot's decision to conduct low altitude flight at a high density altitude and into a box canyon, which resulted in the airplane colliding with rising terrain when its climb capability was exceeded.

NTSB analysis

The pilot reported that, during the cross-country repositioning flight over mountainous desert terrain, the airplane impacted the terrain, nosed over to the inverted position, and caught fire. He recalled that the engine was generating power at impact, but he could not recall any details of the flight before the impact. Data recovered from a handheld global positioning system (GPS) device indicated that, during the flight, the pilot was flying at altitudes ranging from about 100 to 1,000 feet above ground level (agl). The last position recorded by the GPS device showed the airplane about 1 nautical mile from the accident site at an altitude of about 4,100 feet mean sea level (msl), which was about 100 feet agl. The accident site was at 4,600 feet msl near the top of a ridgeline at the head of a box canyon. Postaccident examination of the airframe and engine revealed no evidence of any preimpact mechanical failure or malfunction that would have prevented normal operation. The calculated density altitude at the accident site at the time of the accident was about 7,300 feet. It is likely that the pilot flew the airplane into the box canyon, and, given the high density altitude, the airplane did not have the climb capability to clear the rising terrain.

Text from the NTSB. Open the NTSB docket for WPR11FA334 for the full record.

Event

Date
Jul 18, 2011
Type
Accident
Place
Joshua Tree, California
Highest injury
Serious
Serious injuries
1
Weather
Visual (VMC)
Light
Day

Piper PA-12

N-number
N7510H
Category
Airplane
Damage
Substantial
Operating rule
Part 91 (general aviation)
Purpose of flight
Positioning

From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.