22 Nov 2017: PIPER PA 12 NO SERIES

22 Nov 2017: PIPER PA 12 NO SERIES (N4040M) — Unknown operator

No fatalities • Dickinson, ND, United States

Probable cause

The pilot’s failure to attain adequate airspeed during the short field takeoff, which resulted in an exceedance of the airplane’s critical angle of attack and an aerodynamic stall.

— NTSB Determination

Accident narrative

On November 22, 2017, at 1253 mountain standard time, a Piper PA-12 airplane, N4040M, was substantially damaged during an in-flight collision with a truck trailer immediately after takeoff from an industrial truck yard near Dickinson, North Dakota. The pilot sustained serious injuries and the passenger sustained minor injuries. The airplane was registered to and operated by the pilot as a 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed. The flight was not operated on a flight plan. The flight was originating at the time of the accident. The intended destination was the Sloulin Field International Airport (ISN), Williston, North Dakota.The pilot stated that during the accident takeoff, when the airplane attempted to climb out of ground effect, it banked to the right and the right-wing tip contacted the ground. The airplane continued to roll and came to rest on a truck trailer. He commented that the airplane might have encountered a wind gust which contributed to a right wing stall. He did not perceive anomalies with respect to the airplane during the accident takeoff.

The pilot informed Federal Aviation Administration (FAA) inspectors that he did not feel that there was any hindrance to the airplane during the accident takeoff. The airplane was positioned at the east end of the truck yard to use all the available takeoff area. He set two notches of flaps and executed a short field takeoff procedure. The tail of the airplane lifted off the ground at about 30 knots, at which time he applied full flaps causing the airplane became airborne. Shortly afterward, the right wing dropped possibly due to a gust of wind. He responded by applying full left aileron and full left rudder to compensate. As he was recovering from the right bank, he retracted the flaps from full (third notch) to one-half (second notch) and confirmed throttle was full forward. At that time, the airplane tucked and turned sharply to the right.

According to the passenger, the airplane was gaining speed during the takeoff run until it neared the west end of the maintenance building located in the yard. About 10 or 15 feet above the ground, the airplane seemed to come to a "complete dead stop" and subsequently rolled to the right. The pilot was able to recover momentarily; however, the airplane banked to the right again and ultimately impacted a truck trailer.

A witness reported that the airplane became airborne about 400 feet into the takeoff run. Shortly afterward, when the airplane was about 6 feet above ground level, the right wing dipped to 35 or 40 degrees of bank. The pilot corrected, but the airplane remained in a 20-degree right bank. At that point, the airplane started a more abrupt climb, at which time the airplane "snap rolled" to the right and impacted a truck trailer inverted. He described the airplane attitude as "significantly nose up" and estimated the pitch angle as about 15-degrees angle of attack. The right-wing tip was about 6 feet off the ground when the airplane started the roll. The witness noted that the engine sounded as it if came to full power at the beginning of the takeoff and did not vary. He did not perceive and issues with respect to the engine.

One of the FAA inspectors that responded to the accident site reported that the truck yard consisted of dirt and gravel. The portion of the yard used for the accident takeoff was rough and uneven. The takeoff distance available was about 750 feet. A postaccident examination did not reveal any anomalies consistent with a preimpact failure or malfunction. Flight control continuity was confirmed, which included the wing flap control system. The cockpit flap handle appeared to be in the retracted (up) position at the time of the examination. The flaps were also in the retracted position; however, the exact position of the wing flaps at the time of impact could not be determined.

Contributing factors

  • cause Airspeed — Not attained/maintained
  • cause Angle of attack — Not attained/maintained
  • cause Pilot

Conditions

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