FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13LA082 · Piper PA-60-602P

2 Jan 2013 · North Las Vegas, NV, United States

Managed Aviation Piper PA-60-602P · Accident: hard landing

From North Las Vegas Airport (VGT) to North Las Vegas Airport (VGT)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
WPR13LA082
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-60-602P

Aircraft type
Piper PA-60
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N3AG
Onboard fatalities
Unknown
Route
From North Las Vegas Airport (VGT), North Las Vegas, NVTo North Las Vegas Airport (VGT), North Las Vegas, NV
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Hard landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial Possible conflict

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13LA082
Event ID
20130102X03247
Case number
WPR13LA082
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: a6dd570d41d818419c1245c5f9b0068e869175c1f853a3e2478d5faa03fd252f; retrieved 2026-09-15T20:41:32.452Z.