WPR13LA082

NTSB accident investigation · Piper PA-60-602P · North Las Vegas, NV · January 2, 2013

Accident · No injuriesLimited investigationFinal report
Date
January 2, 2013, 15:15 local (23:15 UTC)
Place
North Las Vegas, NV
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3AGPiper PA-60-602P
Defining event
Landing-flare/touchdown: Hard landing
Weather
Visual (VMC) · Day
Status
Completed · report November 5, 2015
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
FAA FSDO
FAA report
20130102000839A
Case key
85939

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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.

Findings · 4

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: descent/approach/glide pathAircraft › Aircraft oper/perf/capability · Not attained/maintainedPiper PA-60-602P: 1 caseAll aircraft: 809 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotPiper PA-60-602P: 2 casesAll aircraft: 9,295 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot receiving instruction conducted three full-stop landings without incident. After the fourth takeoff, the flight instructor simulated a prearranged left engine failure about 600 ft above ground level (agl). The pilot followed emergency procedures, used the checklist, and prepared to land. The pilot reported that, when the airplane was about 50 to 100 ft agl on final approach, he thought that it was a little too high, so he chose to initiate a go-around. He moved the throttle levers full forward, but neither engine responded. The flight instructor pushed the airplane's nose down, and the pilot continued the approach. On touchdown, the right main and nose landing gear collapsed. A postimpact fire ensued, which consumed most of the airplane. Postaccident examination of the landing gear revealed that it collapsed due to bending overload consistent with a hard landing. The reason for the failure of both engines to respond to power inputs could not be determined because of the postcrash fire damage.

Factual 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 bendingoverload 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.

Aircraft

Registration
N3AG
Reported as
Piper PA-60-602P
Category
Airplane
Serial number
60-8365018
Airframe hours
3,259
Engines
Lycoming IO-540-AA1A5, 350 horsepower, reciprocatingLycoming IO-540-AA1A5, 350 horsepower, reciprocating
Damage
Substantial damage
Fire
On-Ground
Flight
Instructional · Part 91
Operator
Managed Aviation Inc
Registered owner
Managed Aviation Inc
Airworthiness certificate
Standard, Normal
Last inspection
Annual · April 10, 2012
Departed
VGT · North Las Vegas, NV
Destination
VGT · North Las Vegas, NV
Airport
VGT · North Las Vegas, runway 12L, 4,202 × 75 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
72
Injuries
None
Certificate
Private
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Last flight review
August 29, 2012
Seat
Left
Restraint
3-point
Flight hours
3,900 total · 1,700 in this make and model · 3,900 as pilot in command · 21 in the last 90 days · 4 in the last 30 days · 1 in the last 24 hours
Role
Flight instructor
Age
64
Injuries
None
Certificates
Commercial, Flight instructor
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane, Helicopter
Medical
Class 2, With waivers/limitations
Last flight review
July 14, 2011
Seat
Right
Restraint
3-point
Flight hours
11,535 total · 60 in this make and model

Weather

Conditions
Visual (VMC) · Day
Wind
Calm
Visibility
10 statute miles
Lowest ceiling
None
Temperature
50 °F, dew point 10 °F
Altimeter
30.14 inHg
Observed at
KVGT

Docket · 4

The files NTSB released with the investigation on October 7, 2015, on NTSB’s docket system: statements, records, photos and specialists’ reports. 1.2 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.