# NTSB WPR11FA334: Piper PA-12, N7510H, Joshua Tree, CA, July 18, 2011 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Field investigation · Final report - Date: July 18, 2011, 08:46 local (15:46 UTC) - Place: Joshua Tree, CA - Coordinates: 34.044445, -116.302223 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.0444&lon=-116.3022&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Defining event: [Maneuvering-low-alt flying: Low altitude operation/event](https://openairdocs.org/ntsb-events/220) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed, report November 7, 2012 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 81144 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR11FA334 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/81144/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=81144 - Page: https://openairdocs.org/ntsb/WPR11FA334 ## 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Temp/humidity/pressure: high density altitude](https://openairdocs.org/ntsb-findings/03031020): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Piper PA-12, 2 cases](https://openairdocs.org/ntsb-findings/03031020/cases.md?model=7101202), [All aircraft, 278 cases](https://openairdocs.org/ntsb-findings/03031020/cases.md) - [Terrain: mountainous/hilly terrain](https://openairdocs.org/ntsb-findings/03021010): Environmental issues › Physical environment · Effect on operation; cases with it: [Piper PA-12, 5 cases](https://openairdocs.org/ntsb-findings/03021010/cases.md?model=7101202), [All aircraft, 329 cases](https://openairdocs.org/ntsb-findings/03021010/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-12, 18 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=7101202), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Aircraft capability: climb capability](https://openairdocs.org/ntsb-findings/01061010): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Piper PA-12, 4 cases](https://openairdocs.org/ntsb-findings/01061010/cases.md?model=7101202), [All aircraft, 183 cases](https://openairdocs.org/ntsb-findings/01061010/cases.md) - [Performance/control parameters: altitude](https://openairdocs.org/ntsb-findings/01062012): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-12, 6 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md?model=7101202), [All aircraft, 1,310 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Maneuvering-low-alt flying: Low altitude operation/event](https://openairdocs.org/ntsb-events/220) (defining event); cases with it: [Piper PA-12, 3 cases](https://openairdocs.org/ntsb-events/220/sequence.md?model=7101202), [All aircraft, 780 cases](https://openairdocs.org/ntsb-events/220/sequence.md) ## 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. ## Factual narrative On July 18, 2011, at 0846 Pacific daylight time, a Piper PA-12, N7510H, collided with mountainous terrain near Joshua Tree, California. The commercial pilot, the sole occupant onboard, was seriously injured. The airplane sustained substantial damage. Van Wagner Aerial Media LLC of Hollywood, Florida, was operating the airplane under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed for the cross-country repositioning flight. The flight departed from Lake Havasu City, Arizona, about 1 hour 30 minutes before the accident; its destination was Compton, California. No flight plan had been filed. According to the operator, the airplane had been at Lake Havasu conducting banner towing operations, and the purpose of the flight was to return the airplane to its home base in Compton. The pilot reported that the weather was clear along his planned route of flight. He was unable to recall any of the flight before the airplane impacted terrain. He recalled the airplane striking the ground, nosing over to the inverted position, and catching fire. He also recalled that the engine was generating power at impact. Although his right leg was broken, he was able to release his lap belt and shoulder harness and escape from the airplane by kicking out the left side window. An on scene examination of the wreckage was conducted by a National Transportation Safety Board (NTSB) investigator and a Federal Aviation Administration (FAA) inspector. The accident site was located in the Joshua Tree National Forest at an elevation of about 4,600 feet near the top of a ridgeline at the head of a box canyon. The airplane was lying inverted on a 20-degree slope about 50 feet upslope from an area with a 60-degree slope. The engine cowling, fabric fuselage skin, cabin area, and the inboard portions of both wings were consumed by fire. The steel tubing airframe and the control cables were exposed. Control continuity was confirmed from all control surfaces to the cockpit controls. The left wingtip, the right wingtip, and the right wing had leading edge crush damage. The rudder and vertical stabilizer had vertical crush damage. One propeller blade was twisted, bent after near the tip, and displayed trailing edge buckling. The other propeller blade was twisted and bent aft about midspan. No evidence of preimpact mechanical failure or malfunction was noted during the examination of the airframe and engine. A Garmin handheld Global Positioning System (GPS) device (Garmin GPSMAP 96) was recovered from the accident site, and data recorded during the flight was downloaded from the unit using NTSB laboratory equipment. The data parameters recorded included date, time, latitude, longitude, and GPS altitude. The data indicated that the airplane departed from Lake Havasu City Airport about 0715 and proceeded southwest over sparsely populated mountainous desert terrain with elevations ranging from about 500 to 5,500 feet. The airplane’s heightabove the ground was calculated at selected points. Time Altitude 0730 83 feet above ground level (agl) 0742 106 feet agl 0754 137 feet agl 0809 650 feet agl 0824 549 feet agl 0833 1,042 feet agl 0839 573 feet agl 0845 103 feet agl The last location recorded by the GPS device showed the airplane about 1 nautical mile northeast of the accident site, at an altitude of 4,016 feet mean sea level (103 feet agl). At 0856, the reported weather conditions at Twentynine Palms, California, located about 16 nautical miles northeast of the accident site, were wind 360 at 4 knots; visibility 7 miles; few clouds at 8,000 feet; temperature 28 degrees C; dew point 1 degree C; and altimeter setting 29.98 inches of mercury. The calculated density altitude at the accident site was about 7,300 feet. ## Aircraft - Registration: [N7510H](https://openairdocs.org/aircraft/N7510H), registered now, S/N 12-371, built 1946 (OpenAirDocs) - Reported make and model: PIPER PA-12 - Registry model: [Piper PA-12](https://openairdocs.org/model/piper-pa-12) (registry code 7101202) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 12-371 - Airframe hours: 20589 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Fire: On-Ground - Flight: Positioning, Part 91 - Operator: Van Wagner Aerial Media LLC - Registered owner: Van Wagner Aerial Media LLC - Airworthiness certificate: Special, Restricted (Special) - Last inspection: Annual, April 7, 2011 - Departed: HII, Lake Havasu, AZ - Destination: CPM, Compton, CA ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 24; injuries: serious; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review March 15, 2010; seat: left; flight hours: 1,600 total, 1,300 in this make and model, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 360° at 4 knots - Visibility: 7 statute miles - Lowest ceiling: none - Temperature: 82 °F, dew point 34 °F - Altimeter: 29.97 inHg - Observed at: NXP, 16 nm away ## 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 20110718017419A](https://openairdocs.org/incident/20110718017419A), Jul 18, 2011: Piper PA-12, Joshua Tree, CA, Destroyed. It was reported to the NTSB that the pilot was going through the canyon when he encountered a downdraft. Pilot was unable to manuever aircraft out of… ## Other investigations on N7510H (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 MIA90FA085](https://openairdocs.org/ntsb/MIA90FA085), Mar 9, 1990: Piper PA-12 (N7510H), Miramar, FL, destroyed, 3 fatal. Probable cause: THE FAILURE OF THE LOCAL CONTROLLER TO PROVIDE ADEQUATE TRAFFIC ADVISORIES TO N7510H, THE LOCAL CONTROLLER'S IMPROPER CLEARANCE TO N7510H TO DESCEND THROUGH THE TRAFFIC PATTERN, AND THE FAILURE OF… - [NTSB MIA84FA049](https://openairdocs.org/ntsb/MIA84FA049), Dec 22, 1983: Piper PA-12 (N7510H), Ft. Lauderdale, FL, destroyed, 1 fatal ## Docket (5 files) The files NTSB released with the investigation on August 24, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=81144. 4.8 MB in all. - Global Positioning System Device - Specialist's Factual Report (item 1, .PDF, 954 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40367733&FileExtension=.PDF&FileName=Global%20Positioning%20System%20Device%20-%20Specialist%27s%20Factual%20Report-Master.PDF - Global Positioning System Device - Specialist's Factual Report - Attachment 1 (item 2, .CSV, 2 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40367734&FileExtension=.csv&FileName=Global%20Positioning%20System%20Device%20-%20Specialist%27s%20Factual%20Report%20-%20Attachment%201-Master.csv - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 3, .PDF, 865 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40375234&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - NTSB On Site Examination Notes (item 4, .PDF, 2.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40374682&FileExtension=.PDF&FileName=NTSB%20On%20Site%20Examination%20Notes%20-Master.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 5, .PDF, 56 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40375236&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Redacted.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.