6 Jun 2015: FLIGHT DESIGN GMBH CTSW

6 Jun 2015: FLIGHT DESIGN GMBH CTSW (N535CT) — Unknown operator

No fatalities • Haskell, OK, United States

Probable cause

The loss of engine power for reasons that could not be determined because a postaccident engine examination and test run did not reveal any evidence of preimpact malfunctions or failures that would have precluded normal operation.

— NTSB Determination

Accident narrative

On June 6, 2015, about 1258 central daylight time, a Flight Design CTSW, light-sport airplane, N535CT, performed a forced landing shortly after departing the Haskell Airport (2K9), Haskell, Oklahoma. The pilot and a passenger received minor injuries, and the airplane was substantially damaged during the off-airport landing. The airplane was registered to KT Aviation LLC, of Wagoner, Oklahoma, and was operated by a private individual as a 14 Code of Federal Regulations Part 91 personal flight. Day visual meteorological conditions prevailed and a flight plan had not been filed. The flight originated from 2K9 and was destined for Hefner-Easley Airport (H68), Wagoner, Oklahoma, at the time of the accident.

The pilot reported that they had flown from H68 to 2K9 earlier in the day. Prior to departing H68, he did a normal preflight inspection, with no discrepancies noted and about 28 gallons of automotive fuel.

After starting engine at 2K9, the pilot noticed the engine gauges were normal, but the charging system had an inadequate output, so he shut down the engine. After consulting a mechanic, he restarted the engine about 1245, with normal engine and charging indications.

During the initial climb from 2K9 about 500 to 600 feet above ground level, the engine starting "sputtering". The engine continued to run but not enough to maintain altitude. The pilot selected a field for the forced landing; various throttle settings failed to restore engine power and the choke was off. The airplane touched down in a muddy field and came to rest inverted.

An on-scene wreckage examination found substantial damage to the airplane's fuselage and damage to the airplane's landing gear. Fuel quality checks of the on-board fuel and the fuel facility were satisfactory. The wreckage was moved to a different location and a post-accident examination of the engine was conducted. Further examination revealed no water or debris were noted in the gascolator, the engine's left and right carburetor float bowls contained clean fuel, the sparkplugs appeared normal, and ignition spark was verified. A test run of the engine was conducted. The engine was started and run at idle before running up to power; no problems were noted during the engine examination or test run.

The airplane's EFIS (Electronic Fight Information System) and EMS (Engine Monitoring System), were removed for extraction of volatile memory (NVM). The memory in the EFIS was corrupted and no useful information could be obtained. The EMS contained an eight-minute recording of engine parameters for the accident flight. A review of the EMS data revealed the engine acceleration to high power, followed by fluctuations and a reduction in the engine rpms.

The NTSB's Vehicle Recorder Division's full factual report is located in the public docket for this case.

The closest weather reporting station was located at the Okmulgee Regional Airport Okmulgee, Oklahoma, about 17 miles southwest from the accident site. At 1255, the station recorded wind from 150 degrees at 3 knots, visibility 10 miles, scattered clouds at 4,700 ft agl, temperature 88° F, dew point 70° F, and an altimeter setting of 30.00 inches of mercury.

The carburetor icing probability chart included in Federal Aviation Administration Special Airworthiness Information Bulletin No. CE-09-35, Carburetor Icing Prevention, indicated that the airplane was operating in an area that was associated with a serious risk of carburetor ice formation at glide power settings.

Conditions

Weather
VMC, wind 150/03kt, 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.