Piper PA-46 (Malibu/Meridian/Mirage/Matrix/M-Class)

The single engine airplane departed Lincoln on a flight to North Platte, Nebraska. While approaching North Platte-Lee Bird Airport Runway 30 in poor weather conditions, the aircraft went out of control and crashed on the shore of a small lake, bursting into flames. The aircraft was destroyed by impact forces and a post crash fire and the wreckage was found 6 km from the runway threshold. Both occupants were killed. At the time of the accident, visibility was limited due to freezing rain.

The single engine airplane departed Albuquerque-Double Eagle II Airport on a private flight. It crashed in unknown circumstances north of Seligman shortly before noon. Both occupants were killed.

The single engine airplane was on final approach to North Las Vegas Airport when it collided with a Cessna 172 Skyhawk owned by Binner Enterprises. Registered N160RA, the Skyhawk was carrying two pilots who were completing touch and go manoeuvres. Following the collision, both aircraft dove into the ground and crashed on the airport perimeter. Both aircraft were destroyed and all four occupants were killed.

The airplane had recently undergone an annual inspection, and the pilot planned to fly the airplane back to his home base. After receiving clearance from air traffic control, the pilot proceeded to take off. The airplane accelerated and reached a peak groundspeed of 81 kts about 2,075 ft down the 4,097-ft runway. Once airborne, the airplane drifted slightly to the right and the pilot radioed an urgent need to return to the airport. The controller cleared the airplane to land and no further transmissions were received from the accident airplane. The airplane’s flight path showed that it slowed before turning back toward the left and the airplane’s speed continued to decrease throughout the remainder of the data. The final data point recorded the airplane at a groundspeed of 45 kts. The groundspeed would equate to 60 kts airspeed when considering the 15-kt headwind. The stall speed chart for the airplane listed the minimum stall speed for any configuration as 64 kts. Postaccident examinations of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. External and internal engine damage indicated that the engine was producing power at the time of impact, but the amount of power output could not be determined. Based on the available information, the pilot perceived an urgent need to return the airplane to the airport; however, due to the amount of damage from the impact and postimpact fire, the reason that the pilot was returning to the airport could not be determined. Stall speed information for the airplane, the recorded winds, and flight track data, indicated that the airplane encountered an aerodynamic stall before impacting the ground near the departure end of the runway. Since the airplane stalled and impacted the ground before reaching the perimeter of the airport, the pilot may not have had sufficient altitude to execute a forced landing to the empty field off the departure end of the runway.

En route, the pilot encountered engine problems and elected to make an emergency landing on a motorway. Upon landing, the aircraft impacted the road bank, lost its left wing and came to rest. All six occupants evacuated with minor injuries and the aircraft was damaged beyond repair.

The pilot was conducting a solo night cross-country flight in low visibility through mountainous terrain. The pilot was then cleared by an air traffic controller to conduct a RNAV (GPS)-E instrument approach into the destination airport. After passing the final approach fix and before the missed approach point, the pilot, for an unknown reason, executed a left turn, consistent with the missed approach procedure. During the turn toward the holding waypoint, the airplane did not climb. Shortly thereafter, the airplane impacted steep rising terrain The local weather at the time of the accident indicated a cloud ceiling of 1,200 ft above ground level and 1 statute mile visibility, which was below the weather minimums for the approach. Data retrieved from the onboard avionics revealed that although the pilot flew the published route in accordance with the instrument approach procedure, the minimum required altitudes were not adhered to. A review of the ForeFlight weather briefing data indicated that a route weather briefing had been generated by the pilot with the filing of the instrument flight rules (IFR) flight plan. While no weather imagery was reviewed during the period, the pilot had checked METARs for the destination and another nearby airport before departure and viewed the RNAV (GPS)-E approach procedure at the destination airport. A review of the data that was presented to the pilot indicated that visual flight rules conditions prevailed at the destination with light snow in the vicinity at the time it was generated. Based on the preflight weather briefing the pilot obtained, he was likely unaware of the IFR conditions and below minimum weather conditions at the destination until he descended into the area and obtained the current local weather during the flight. It is probable that, based upon the weather and flight track information, as the pilot was on the instrument approach, he became aware of the below minimum weather conditions and elected to initiate the missed approach, as evident by the turn away from the airport similar to the missed approach procedure and the flaps and landing gear being in transition. This investigation was unable to determine why the missed approach procedure was prematurely initiated and why the airplane failed to climb. Additionally, there were no preimpact mechanical malfunctions or anomalies found during a postaccident examination that would have precluded normal operation.