17 May 2010: SUPINSKI MARK R SUPINSKI MUSTANG II — MEADOW LAKE FLIERS LLC

17 May 2010: SUPINSKI MARK R SUPINSKI MUSTANG II (N512SR) — MEADOW LAKE FLIERS LLC

No fatalities • Peyton, CO, United States

Probable cause

The pilot’s failure to maintain control of the airplane during landing. Contributing to the accident was the pilot’s lack of experience flying tailwheel configured airplanes.

— NTSB Determination

Accident narrative

On May 17, 2010, about 1135 mountain daylight time, a Supinski Mustang II tailwheel configured experimental airplane, N512SR, was substantially damaged during landing at Meadow Lake Airport (00V), Colorado Springs, Colorado. The Airline Transport rated pilot received minor injuries. The local, personal flight was being conducted under the provisions of Title 14 Code of Federal Regulations Part 91 without a flight plan, and was terminating at 00V when the accident occurred. Visual meteorological conditions prevailed at the time of the accident.

The pilot stated he was conducting a Phase I test flight of the airplane. This was the airplane’s sixth flight and the pilot’s fifth flight in it. He had previously taken off, flown a flight profile to determine stall speeds, and performed a full stop landing. He took off again, performed one touch and go landing, and was on downwind in the traffic pattern when the engine started running rough. He switched from computer A to computer B (engine controllers for the Mazda 13B engine) and the engine began running normally. The pilot then elected to perform a full stop landing. The pilot stated he flew the final approach at 80 knots with the second notch of flaps. During landing the airplane touched down on the main landing gear, bounced, and immediately began a left turn/yaw. The pilot was able to correct back to centerline with right rudder and power. He then elected to keep the power in until the airplane became stabilized or became airborne. The airplane became airborne and began an uncontrollable left roll until the airplane contacted the ground. The airplane came to a rest and was on fire as the pilot exited the airplane. Witnesses observed the airplane touchdown, bounce, and start an immediate left turn with increasing pitch before hitting the ground. Several witnesses reported the engine was running normally during the final landing.

The pilot reported having 16,000 total hours, 2130 hours in airplane single-engine, and 10 hours in this make and model airplane. A review of the pilot’s logbook showed he had accumulated 6.6 hours in tailwheel configured airplanes beginning in March, 2010. The pilot stated he had additional tailwheel time logged in an earlier logbook, but he could not find it. He also said he preferred a three point landing in the airplane since the propeller was close to the ground during a main gear landing. The pilot said the airplane had a previous rudder control malfunction during taxi testing which caused a departure from the taxi surface. That excursion was attributed to incorrect installation of the rudder cables. This deficiency was identified in an airworthiness directive (AD) and was subsequently corrected by the airplane builder. The pilot did not report any additional problems with the rudder system after the cables were corrected.

Examination of the airplane wreckage showed the engine cowling, cockpit and fuselage were mostly consumed by fire. The empennage was separated from the fuselage. Both wooden propeller blades were fractured and separated near the propeller hub. The rudder cables were attached to the rudder pedals and rudder control continuity was verified to the rudder. Rudder movement was verified by moving the rudder back and forth between the rudder stops. Aileron control tube continuity was verified from each aileron to the control sticks. A section of the forward elevator control push-rod and a section of the aft elevator control push-rod were not located. The ends of the elevator control push-rod sections were fractured in a manner consistent with overload. No anomalies were found with the airplane during the examination.

Contributing factors

  • cause Performance/control parameters — Not attained/maintained
  • factor Pilot

Conditions

Weather
VMC, wind 170/11kt, 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.