18 Jun 2016: GLAESER NIEUPORT 11 — Pilot

18 Jun 2016: GLAESER NIEUPORT 11 (N124TG) — Pilot

No fatalities • Gardner, KS, United States

Probable cause

The pilot's diverted attention during the approach for the precautionary landing, which resulted in low airspeed, an exceedance of the airplane’s critical angle of attack, and a subsequent aerodynamic stall. Contributing to the accident was the control system vibration and the airplane’s lack of a stall warning system.

— NTSB Determination

Accident narrative

On June 17, 2016, at 2040 central daylight time, an experimental amateur-built Nieuport 11, N124TG, experienced a hard landing and an impact with terrain during a precautionary landing at Gardner Municipal Airport (K34), Gardner City, Kansas. The pilot performed the precautionary landing after he felt a vibration from the horizontal stabilizer while in the airport traffic pattern. The airplane sustained substantial damage. The pilot was uninjured. The airplane was registered to and operated by the pilot under 14 Code of Federal Regulations Part 91 as a personal flight that was not operating on a flight plan. Visual meteorological conditions prevailed at the time of the accident. The local flight originated from K34 at 2015.

On June 16, 2016, the pilot trailered the airplane to K34 for an upcoming weekend event. On the day of the accident, the airplane was untrailered and reassembled mid-day. The pilot then preflighted the airplane and taxied it to a parking area at the airport for an evening flight.

The pilot stated that before takeoff he performed an engine run-up and checked the flight controls for a takeoff using runway 17. After takeoff, the pilot flew the airplane in a left-hand airport traffic pattern and completed two circuits over the airport with "no problems." He said that during the upwind leg, parallel to runway 17, he "noticed some vibration," and saw the horizontal stabilizer shaking/vibrating. He varied the engine throttle setting while the airplane was near the departure end of runway 17 to cease the vibration, but the vibration continued. The pilot then heard, but did not see, an inbound aircraft that made a radio transmission referencing runway 26. Due to the inbound aircraft, the pilot thought that it was "unsafe to land" on runway 26, so he flew a left base to runway 17 for landing. As the airplane neared the left side of runway 17, the pilot initiated a "shallow" left turn for a "modified" final over runway 17, and the airplane "quickly began to sink." The said that the airplane experienced an "aerodynamic stall." The pilot added full engine power, which induced a yaw and a roll. The airplane descended and impacted the ground coming to rest short and on the left side of runway 17.

The pilot stated that he did not lose elevator control authority during the flight and his attention to flying the airplane was "distracted" by a fear that parts/empennage may be separating from the airplane, which led to his stalling the airplane. He said that the airplane model was "super draggy" and "super light" and without engine power, the airplane slows down rapidly.

The pilot stated that the airplane was built from plans that were based upon a 100-year old airplane. The plans depicted and the airplane was manufactured without the left and right elevators connected to each other. A single control cable linked the two elevators via a Y-connection. The single control cable was not supported for "a number of feet" through guides/fairleads, which can make the elevators "flutter." The pilot said that following the accident several other airplane owners with the same model of airplane have modified the elevator control system by either installing a bellcrank in the elevator control system or by connecting the left and right elevators together.

The pilot said that neither the plans nor any subsequent modification to those plans in the building of the accident airplane resulted in the installation of a stall warning system in the airplane.

Contributing factors

  • cause Pilot
  • cause Capability exceeded
  • cause Airspeed — Not attained/maintained
  • factor Malfunction
  • factor Design
  • factor Not installed/available

Conditions

Weather
VMC

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.