17 Nov 2018: Piper PA28 180

17 Nov 2018: Piper PA28 180 (N111TA) — Unknown operator

No fatalities • Barnesville, GA, United States

Probable cause

The student pilot’s failure to maintain airplane control during takeoff and the flight instructor’s delayed remedial action, which resulted in an off-runway landing and subsequent collision with trees.

— NTSB Determination

Accident narrative

On November 17, 2018, about 1112 eastern standard time, a Piper PA-28-180, N111TA, was substantially damaged after a collision with trees and terrain at Little Tobesofkee Creek Ranch Airport (GA86), Barnesville, Georgia. The flight instructor and student pilot incurred minor injuries, and two passengers were not injured. The airplane was operated by Clear Blue Sky Aviation LLC under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no flight plan was filed for the flight to Macon Downtown Airport (MCN), Macon, Georgia. The instructional flight that originating at the time of the accident.The flight instructor reported that runway 35 was selected for the takeoff due to the prevailing wind out of the north at 7 to 8 kts. The student was at the controls for the takeoff. The takeoff was initiated and acceleration seemed normal, considering the runway upslope and 3,000 ft-long turf surface. The airspeed reached 65 kts and was increasing at the predesignated decision point, which was about 60% of the runway length. After takeoff, the airplane banked to the left unexpectedly. The instructor did not recall the stall warning light illuminating. The student called out a lack of responsiveness from the flight controls and the flight instructor simultaneously took the controls. The pilots realized that the airplane would not clear trees at the departure end of the runway, so the flight instructor elected to land the airplane straight ahead and aim it between the trees. The airplane touched down about 200 ft from the trees and continued until it struck several small trees and one large tree. The airplane came to a stop, the engine was secured, and the pilots and passengers egressed the airplane and were met by first responders.

An inspector with the Federal Aviation Administration responded to the accident site and examined the wreckage. The airplane crashed in a wooded area to the north of the airport boundary. Structural damage occurred to the wings and fuselage. There was no fire.

The wreckage was recovered to a salvage facility where a more detailed examination was performed. The fuselage was generally intact. Both wings were cut off near the wing roots by recovery personnel. The right wing exhibited leading edge crushing signatures from contact with trees. The aileron cables were cut by recovery personnel. The aileron cables were otherwise connected to the ailerons and the ailerons were connected to the attachment points on the wings. Aileron cable continuity was established from the cut ends at the wing roots to the control yokes. Elevator and rudder continuity were confirmed from the control surfaces to the cockpit controls. The vertical stabilizer, rudder, and stabilator were undamaged.

The engine remained attached to the firewall. The metal, fixed pitch propeller remained attached to the crankshaft. The engine crankshaft was turned through manually by turning the propeller. Internal engine continuity was confirmed. Compression and suction were observed on all cylinders. Valve action was normal on all cylinders. The engine contained oil. Both spark plugs were removed from each cylinder. They were normal in color and wear when compared to a Champion inspection chart. The carburetor was intact. The venturi and floats were in place and undamaged. The gascolator was drained and it contained about 1 oz of clean, blue-colored fuel. Both magnetos produced a visible spark at all leads when rotated.

The stall warning light operated normally when tested. The airplane was not equipped with a stall warning horn.

Contributing factors

  • cause Student/instructed pilot
  • cause Performance/control parameters — Not attained/maintained
  • cause Instructor/check pilot
  • cause Effect on operation

Conditions

Weather
VMC, wind 010/04kt, 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.