2 Sep 2015: PIPER PA 28-140 — LUIS M. JARA

2 Sep 2015: PIPER PA 28-140 (N7494R) — LUIS M. JARA

No fatalities • North Pole, AK, United States

Probable cause

The student pilot’s loss of directional control during landing with a tailwind, which resulted in a runway excursion and collision with trees.

— NTSB Determination

Accident narrative

On September 2, 2015, about 1500 Alaska daylight time, a Piper PA-28 airplane, N7494R, sustained substantial damage following a loss of control while landing at Lakloey Air Park, North Pole, Alaska. The airplane was being operated by the student pilot as a visual flight rules (VFR) flight under the provisions of Title 14, Code of Federal Regulations (CFR) Part 91, when the accident occurred. The student pilot sustained minor injuries and the sole passenger was not injured. Visual meteorological conditions prevailed and no flight plan had been filed.

During a telephone conversation with the National Transportation Safety Board (NTSB) investigator-in-charge (IIC) on September 2, the passenger stated that they had overflown a moose hunting area and were returning for landing. After touchdown, during the landing roll, the airplane veered to the left, then to the right, then back to the left before departing the runway and impacting a stand of birch trees. He stated that the airplane seemed to fly great, and he was not aware of, nor did the pilot discuss, any mechanical anomalies or malfunctions during the course of the flight.

During an interview with the NTSB, IIC on September 3 the pilot stated that the only thing he remembered from the accident flight was being on short final for runway 24 at Lakloey Air Park.

At the time of the accident, a pilot rated witness on the northeast corner of Lakloey Air Park reported light wind conditions out of the east at 8 to 10 knots. He observed the accident airplane on final approach for runway 24; a downwind landing. He noted that the airplane appeared to be a "little fast", and estimated the groundspeed to be about 60 miles per hour. He said that after touchdown, the airplane veered to the left, then to the right, then back sharply to the left before exiting the runway.

The NTSB IIC reached the accident site on the morning of September 3. The airplane came to rest upright in a densely populated stand of birch trees about midfield and adjacent to runway 24, on a heading of about 250 degrees. All the primary flight controls were identified at the accident site. Stabilator control continuity was established from the control column to the stabilator balance arm. Rudder control continuity was established from the rudder torque tube to the rudder horn. Aileron control continuity was established in the direct cables, from the control column to the point where the right cable fractured with features consistent with tension overload, to the left and right aileron bellcranks, and in the balance cable to the point where the cable fractured with features consistent with tension overload, to the left and right aileron bellcranks.

The airplane sustained substantial damage to the wings and fuselage. The examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.

The closest weather reporting facility is Ladd Army Airfield, Fort Wainwright, AK approximately 3 miles west of the accident site. At 1458, an aviation routine weather report (METAR) at Fort Wainwright, Alaska, reported in part: wind 090 degrees at 7 knots, visibility, 10 statute miles, clear skies; 67 degrees F; dew point 37 degrees F; altimeter, 29.87 inHG.

Title 14, Code of Federal Regulation (CFR) Part 61 prescribes in part: The requirements for issuing pilot certificates and ratings, and the privileges and limitations of these certificates and ratings. The student pilot was subject to the part's applicable rules. Section 61.89, states, in part: A student pilot may not act as pilot in command of an aircraft: That is carrying a passenger.

Contributing factors

  • cause Directional control — Not attained/maintained
  • cause Student/instructed pilot
  • cause Effect on operation

Conditions

Weather
VMC, wind 070/05kt, 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.