16 Feb 2014: PIPER PA-30 — Gateway Aviation, Ltd.

16 Feb 2014: PIPER PA-30 (N931JS) — Gateway Aviation, Ltd.

No fatalities • Allentown, PA, United States

Probable cause

The flight instructor’s failure to maintain directional control during the landing.

— NTSB Determination

Accident narrative

On February 16, 2014, about 1440 eastern standard time, a Piper PA-30, N931JS, experienced a loss of directional control during landing and collided with a snowbank at Allentown Queen City Municipal Airport (XLL), Allentown, Pennsylvania. The certified flight instructor (CFI) and commercial rated student were not injured. The airplane was substantially damaged. The airplane was registered to Hamilton Services Group, Inc., and was operated by Gateway Aviation, Ltd., under the provisions of 14 Code of Federal Regulations (CFR) Part 91 as an instructional flight. Visual meteorological conditions prevailed at the time and no flight plan was filed. The flight originated about 5 minutes earlier from Lehigh Valley International Airport (ABE), Allentown, Pennsylvania.

The CFI stated that the purpose of the flight was for the student to practice simulated single engine failures during various phases of flight. The flight departed from XLL about 1330, and flew to the practice area where the student performed airwork. The flight then proceeded to ABE, where the student successfully performed a simulated single engine full-stop landing. While taxiing for takeoff, the airplane encountered slush. The flight departed ABE returning to XLL where the flight joined the upwind leg for runway 25. The CFI reported that the wind at the time was approximately 5 knots within 20 degrees of runway heading, while a surface aviation observation from XLL about 5 minutes before the accident indicates in part the wind was from 290 degrees at 7 knots.

The CFI simulated a failure of the right engine by bringing the right throttle to idle, which prompted the student to correct for and secure the 'failed' engine. He did perform the procedure correctly, and before turning onto crosswind, the CFI advanced the right throttle to 13 inches of manifold pressure (per the manufacturer's recommendation), and the flight continued in the traffic pattern for runway 25. The student applied the necessary aileron and rudder corrections to account for the 'failed' right engine, and turned onto final approach to runway 25.

While on final approach with flaps fully extended to the landing position, the student kept the longitudinal axis of the airplane aligned with centerline, and maintained 'blue line' indicated airspeed plus ten knots. As the flight approached the runway the student flared a little high or early, with a resulting "solid touchdown" on the dry runway on the main landing gears. Though the CFI could tell the touchdown was going to be firm or harder than average, he didn't feel the need to take over the controls or initiate a go-around since the landing was no worse than others he has had in this aircraft in the past. While guarding the rudder pedals with his feet, shortly, if not immediately after touchdown, the aircraft pulled heavily to the left, which he (CFI) attempted to correct with full right rudder and right brake application. Having no affect the airplane continued to veer to the left and collided with a snowbank off the left side of the runway at about 25 knots. The airplane was removed from the site for further examination.

Postaccident inspection of the airplane following recovery by a FAA airworthiness inspector revealed no evidence of preimpact failure or malfunction of the nose landing gear steering system, or of the left main landing gear trunnion, which exhibited evidence of overload fracture. The FAA inspector also reported observing skid marks on the runway from all three landing gear tires; the skid mark from the nose landing gear tire was very close to the skid mark made by the left main landing gear tire, consistent with the airplane yawing to the left.

Contributing factors

  • cause Directional control — Not attained/maintained
  • cause Instructor/check pilot

Conditions

Weather
VMC, wind 290/07kt, 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.