18 Jul 2011: PIPER PA-12 — VAN WAGNER AERIAL MEDIA LLC

18 Jul 2011: PIPER PA-12 (N7510H) — VAN WAGNER AERIAL MEDIA LLC

No fatalities • Joshua Tree, CA, United States

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 Determination

Accident 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 height above 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.

Contributing factors

  • Effect on operation
  • Effect on operation
  • cause Pilot
  • cause Capability exceeded
  • cause Altitude — Not attained/maintained

Conditions

Weather
VMC, wind 360/04kt, vis 7sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.