14 Jun 2015: PIPER PA28 140

14 Jun 2015: PIPER PA28 140 (N43078) — Unknown operator

No fatalities • Hampton, NH, United States

Probable cause

The pilot’s failure to properly set the stabilator trim prior to takeoff, which resulted in an exceedance of the airplane’s critical angle of attack and an aerodynamic stall during takeoff.

— NTSB Determination

Accident narrative

On June 14, 2015, about 0930 eastern daylight time, a Piper PA-28-140, N43078, impacted trees and terrain shortly after takeoff from Hampton Airfield (7B3), Hampton, New Hampshire. The private pilot and one passenger received serious injuries. The airplane was substantially damaged by impact forces and a postcrash fire. Visual meteorological conditions prevailed and no flight plan was filed for the planned flight to Biddeford Airport (B19), Biddeford, Maine. The airplane was owned and operated by the private pilot under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight.According to the pilot, on the morning of the accident he had fueled the airplane at B19, and performed a "full run-up and normal takeoff" for the flight to 7B3. The takeoff, all systems, and flight characteristics appeared normal. After landing at 7B3, he taxied to the ramp and shut the airplane down. He did not refuel at 7B3, and a short time later he and his passenger embarked and taxied to runway 02, where he performed another engine run-up, with no anomalies noted. He indicated that the takeoff, and all systems including the airspeed, appeared normal. He said that the airplane lifted off at 65 knots, but it would not climb. He asked the passenger to read the emergency checklist, and verified that the mixture was rich, the throttle was full, the fuel selector was on the fullest tank, the fuel pump was on, and the carburetor heat was off. He attempted to keep the airplane level; however, he raised the nose at the last minute as they approached a tree line. The airplane cleared the initial tree line; however, subsequently descended into the wooded area.

According to a witness, as the airplane lifted off from the runway, it appeared to have a "high angle of attack," and it looked as though it was "mushing through the air" after takeoff. During the initial climb the pitch attitude decreased briefly, and then increased before the airplane reached a tree line. After clearing the trees, the nose lowered and the airplane disappeared out of sight. The witness further stated that he did not hear a loss of engine power at any time. Another witness stated that when the airplane lifted off the ground, its "nose was too vertical." The witness thought the airplane would not climb above the trees in the nose-up position; however, it cleared the tree tops and was "nearly vertical" when it began to lose altitude.

Review of airport surveillance video also revealed that the airplane lifted off and remained in a nose-up attitude.

Examination of the wreckage, at the scene, by a Federal Aviation Administration (FAA) inspector revealed that the airplane impacted a wooded area about 2,000 feet from the departure end of the runway and slightly right of the extended runway centerline. The fuselage came to rest upright in a nose down attitude with the engine and nose section embedded in soil. Both wings were separated from the fuselage.

A postaccident examination of the airplane and engine was conducted by an FAA inspector and representative from the engine manufacturer. One propeller blade exhibited chordwise scratching and leading-edge gouging. When the engine crankshaft was rotated by hand, continuity was confirmed on all cylinders, valves, and accessory gears. Thumb compression and suction was verified on each cylinder. The spark plugs were removed and examined; each displayed little or no wear and were light gray/black/oily in color. The carburetor bowl was removed and was found to be free of debris.

Control cable continuity was established from each aileron though fractures, consistent with tensile overload, to the cockpit area. The stabilator and rudder were removed during salvage recovery efforts, and the flight control cables were cut by recovery personnel. However, cable continuity was confirmed from the cockpit area to the rudder and stabilator.

Examination of the stabilator trim indicator in the cockpit revealed that the trim was in the full nose up position. Examination of the stabilator trim jackscrew revealed 16 exposed threads, which equated to a full nose-up position. Review of a takeoff checklist from a make and model pilot operating manual revealed "Trim tab – set."

Contributing factors

  • cause Incorrect use/operation
  • cause Pilot
  • cause Capability exceeded
  • cause Pilot

Conditions

Weather
VMC, wind 060/08kt, 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.