5 Aug 2017: BURKHART GROB FLUGZEUGBAU G102 CLUB ASTIR IIIB

5 Aug 2017: BURKHART GROB FLUGZEUGBAU G102 CLUB ASTIR IIIB (N102BK) — Unknown operator

No fatalities • Marion, OH, United States

Probable cause

The pilot’s failure to follow the before takeoff checklist, which resulted in an improper takeoff configuration and subsequent uncontrolled descent into terrain during a departure climb.

— NTSB Determination

Accident narrative

On August 5, 2017, about 1350 eastern daylight time, a Burkhart Grob Flugzeugbau G-102 Club Astir IIIB glider, N102BK, collided with a tree and terrain after releasing from the tow airplane at the Marion Municipal Airport (MNN), Marion, Ohio. The pilot received serious injuries, and the glider sustained substantial damage. The glider was owned by the Central Ohio Soaring Association, Inc., and operated by the pilot as a 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions existed near the accident site at the time of the flight, and a flight plan had not been filed. The flight was departing MNN on a local flight.

The pilot stated that he made a mistake during his before takeoff checks and forgot to latch the canopy. He stated that after climbing a "few hundred feet" the canopy came open. While he was trying to close the canopy, he lost sight of the Cessna 150 tow airplane, so he released the tow line and made a turn to the right. He attempted to land in a bean field, but the glider struck a tree and impacted the field.

A witness who observed the glider during the accident flight reported that the glider's left and right-wing spoilers were extended during the flight and were visible from the ground. He stated that the glider and tow airplane were unable to climb normally with the spoilers extended. He reported that the glider released from the tow airplane around 150 to 200 feet above ground level (agl) and tried to make a 180-degree turn back to the runway with the spoilers still extended. The glider's wing clipped a tree and crashed in a bean field.

The tow airplane pilot reported that shortly after takeoff, he felt the tow airplane being "jerked around" by the glider. He saw the glider in a high nose-up position, and then the tow line released about 150 feet agl. The tow airplane continued climbing straight ahead and then returned to MNN and landed. The tow pilot inspected the tow line after landing. The towline and tow ring were undamaged and attached to the tow airplane.

The Federal Aviation Administration (FAA) inspector reported that the examination of the glider at the accident site revealed that the spoilers were found in the open or deployed position. Maple leaves were found in the bottom of the spoiler wells. The right wing exhibited impact damage about mid-span. The flight controls were damaged consistent with impact forces. The canopy attachment pins and the surrounding composite material were torn from the fuselage at impact. The canopy attachment handle and bayonet pins showed proper operation. The damage to the canopy was consistent with it being in the latched position at impact.

In an interview with a FAA inspector, the pilot stated that he heard air noise in the cabin during takeoff and thought his canopy had become unlatched. He attempted to check the canopy handle during takeoff and climb out while still under tow.

In his report to the National Transportation Safety Board, the pilot stated, "We should not have let the need for a rapid departure overlook the need to make sure that the checklists are completed. And most important, fly the airplane." The pilot indicated that the glider had no mechanical malfunctions or failures.

At 1353, the surface weather observation at MNN was wind from 280 degrees at 9 knots; visibility 10 miles; sky clear; temperature 24 degrees C; dew point 12 degrees C; and altimeter 30.06 inches of mercury.

Contributing factors

  • cause Incorrect use/operation
  • cause Climb rate — Not attained/maintained
  • cause Pilot

Conditions

Weather
VMC, wind 280/09kt, 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.