7 Jun 2017: MCKENNA SD-1A

7 Jun 2017: MCKENNA SD-1A (N31313) — Unknown operator

No fatalities • Juneau, WI, United States

Probable cause

The pilot’s difficulty controlling the airplane due to his incorrect reinstallation of the wings, which led to a bounced precautionary landing. Contributing to the accident was the failure of the pilot and the mechanic to verify the wings’ angle of incidence.

— NTSB Determination

Accident narrative

On June 7, 2017, about 0930 central daylight time, an experimental amateur-built SD-1A airplane, N31313, was substantially damaged during a precautionary landing at Dodge County Airport (KUNU), Juneau, Wisconsin. The private-rated pilot was not injured. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed and no Federal Aviation Administration (FAA) flight plan had been filed for the flight. The local flight had departed about 0900.

According to the pilot, immediately after takeoff the left wing felt "extremely heavy" and required an "exceptional amount of right aileron" to maintain level flight. The pilot was able to fly the airplane around the traffic pattern and perform a precautionary landing on runway 20. During the landing, the airplane bounced, and turned to the right. The left main landing gear collapsed, and the engine mount was substantially damaged.

According to the FAA inspector who responded to the accident, the wings had been taken off the airplane prior to its purchase. The pilot purchased the airplane in April of 2016. During the reinstallation of the wings, in April of 2017, the pilot installed the wing bolts where he thought they should go. He did not perform any measurements during this reinstallation. The Airframe and Powerplant Mechanic who signed off on the condition inspection did not confirm the position of the wings and more specifically, the angle of incidence.

The accident flight was the first flight after the reinstallation of the wings. Postaccident examination of the airplane revealed that the flight controls were continuous and correct; however, the angle of incidence, on the wings, was incorrect. No other anomalies were noted that would have precluded normal operation.

Contributing factors

  • cause Incorrect service/maintenance
  • cause Pilot
  • cause Incorrect service/maintenance
  • factor Pilot
  • factor Maintenance personnel

Conditions

Weather
VMC, 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.