5 Jan 2012: PIPER AEROSTAR 601P — IVANS NORMAN B

5 Jan 2012: PIPER AEROSTAR 601P (N104RM) — IVANS NORMAN B

No fatalities • Las Vegas, NV, United States

Probable cause

The pilot's failure to maintain directional control of the airplane during the landing roll.

— NTSB Determination

Accident narrative

On January 5, 2012, at 1539 Pacific standard time, a Piper Aerostar 601P, N104RM, sustained substantial damage during a landing at North Las Vegas Airport (VGT), Las Vegas, Nevada. The private pilot, the sole occupant of the airplane, was not injured. The owner/pilot was operating the airplane under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed for the personal local flight, which had originated approximately 39 minutes before the accident. A flight plan had not been filed.

The pilot stated that the purpose of the flight was to practice instrument landing approaches. On the third approach, he requested to side step from runway 12 left to 12 right for a full stop landing. The tower controller approved the side step and cleared him for landing. The pilot reported that almost immediately after touchdown, the airplane began “wavering” and moments later, veered to the left. He attempted to regain directional control with the application of “full right rudder” and subsequently the airplane departed the right side of the runway. The pilot attributed the loss of directional control to a main landing gear malfunction.

A witness said that the airplane’s landing touchdown was “firm” but not abnormal. Several witnesses observed the airplane to “fishtail” almost immediately after touchdown and drift towards the left side of the runway. As the airplane approached the left side of the runway, it “yawed” right and went “skidding” down the runway while facing right. The left engine propeller blades began contacting the runway. The witness said that as the airplane began moving to the right side of the runway, he heard the right engine increase to near full power. When the airplane entered the dirt on the right side of the runway, it spun to the left coming to rest facing the opposite direction from its approach to landing.

Postaccident inspection of the airplane by a Federal Aviation Administration (FAA) inspector revealed that both wings were bent up, the wing flaps were bent, the left wing’s fuel tank was compromised, and the fuselage had several holes in it. On January 25, 2012, the airplane was examined by the FAA inspector and a licensed mechanic. They found the left propeller assembly feathered, and the right propeller blades were bent forward. Examination of the cockpit revealed the both throttle leavers were in the aft/closed position, the propeller control leavers were full forward, and the mixture controls were full rich. The throttle levers in the cockpit exhibited normal operation and friction, but both propeller control levers exhibited little friction and could be moved with one finger’s pressure. The pilot had not reported any malfunctions with the airplane’s engines or their propeller assemblies.

A police video documented that moments after the accident, a police officer suggested that the pilot turn the airplane's electrical power off; the pilot was observed to reenter the accident airplane.

The mechanic suggested that the forward bending of the right propeller blades indicated that the right engine was at a high power setting when it contacted the ground and that the airplane was sliding backwards. Additional, the right wing flaps were bent forward indicating aft movement at the time of terrain contact. The airplane’s nose and main landing gears were examined, and no preimpact anomalies were identified.

Contributing factors

  • cause Pilot
  • cause Directional control — Not attained/maintained

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.