2 Jan 2013: PIPER PA-60-602P — Managed Aviation Inc

2 Jan 2013: PIPER PA-60-602P (N3AG) — Managed Aviation Inc

No fatalities • North Las Vegas, NV, United States

Probable cause

The pilot’s failure to maintain an adequate descent rate while on final approach, which resulted in a hard landing and landing gear collapse due to overload following the failure of both engines to respond to power inputs during an attempted go-around for reasons that could not be determined due to postcrash fire damage.

— NTSB Determination

Accident narrative

On January 2, 2013, about 1515 Pacific standard time, a Piper PA-60-602P, N3AG, veered off the runway during landing at North Las Vegas, Nevada. The pilot/owner was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The private pilot receiving instruction and the flight instructor were not injured; the airplane sustained substantial damage from a post-crash fire. The local instructional flight departed North Las Vegas about 1430. Visual meteorological (VMC) conditions prevailed, and no flight plan had been filed.

The pilot remained in the traffic pattern after departure, and completed three full-stop landings without incident; one was on runway 12R, and the other two were on runway 12L. As prearranged with the flight instructor prior to departure, the fourth takeoff was a simulated left engine failure about 600 feet above ground level (agl). The pilot followed emergency procedures, used the checklist, and prepared to land.

About 50-100 feet agl on final, the pilot felt that the airplane was a little too high, and elected to initiate a go-around. The propeller and mixture controls were already full forward. Movement of the throttle levers full forward resulted in neither engine increasing in power. The flight instructor pushed the nose down. The airplane shuddered about 15 feet agl, but did not stall. The pilot pulled the nose back before touchdown, and landed on the main landing gear. He stated that touchdown was not hard; it felt like a normal landing. The right wing went down immediately as if the right main landing gear had collapsed, and the airplane veered off the runway into a ditch in the infield.

The flight instructor noted that the airplane was on fire. The pilot shut down all power and the fuel mixture. It took three vigorous tries to open the upper clamshell door before the pilot and flight instructor could egress. Within a few moments of their exit, the airplane caught fire.

An airframe and powerplant (A&P) mechanic was working on the airport ramp. The A&P heard an airplane coming in for landing, and noted that the engine sounds were increasing and decreasing. He observed an airplane porpoising, and coming in fast. He thought that the airplane landed hard; the right main landing gear and nose landing gear collapsed on touchdown. The airplane caught fire within 40 to 50 feet after touchdown; it started sliding, and then it exited the runway surface.

The axle of the right main landing gear strut with the lower link still bolted to it was sent to the National Transportation Safety Board Office of Research and Engineering Materials Laboratory for examination.

A fractured piece of the piston was contained in the axle, and a portion of a fractured bolt was contained at the lower link connection to the upper link. Examination of the piston's fracture face revealed that it was oriented diagonally to the strut center line, and displayed a grainy surface with shear lips, consistent with a bending overload event. The fracture face on the lower link to upper link attachment bolt displayed grainy surfaces in a cup and cone formation with a distinct shear lip oriented in one direction, also consistent with a bending overload event.

Due to the postaccident fire damage, examination of the engines failed to reveal the reason why they did not respond to power input.

Contributing factors

  • cause Descent/approach/glide path — Not attained/maintained
  • Capability exceeded
  • cause Pilot
  • cause Pilot

Conditions

Weather
VMC, vis 10sm

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.