The U.S. aircraft register, updated daily
Accidents · NTSB CEN17LA265 · Final report

Cubcrafters INC CC11-160 accident near Milesville, South Dakota, July 9, 2017

On July 9, 2017 at about 7:09 pm local time, a 2015 Cubcrafters INC CC11-160, registered N111JW, was substantially damaged in an accident during enroute near Milesville, South Dakota (Philip airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

Fuel starvation and a subsequent loss of engine power for reasons that could not be determined because a postaccident examination and a test run of the engine did not reveal any anomalies. Contributing to the accident was the pilot’s failure to maintain airspeed after the loss of engine power, which resulted in an aerodynamic stall and a hard landing.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 9, 2017 · about 7:09 pm local time · cases in 2017
Place
Milesville, South Dakota · Philip · cases near this airport · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Cubcrafters INC CC11-160, built 2015 · all CC11-160s on the register
Registration
N111JW · registry record · serial CC11-00360
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The private pilot was conducting a personal flight and reported that the airplane had been "topped off" before takeoff. Due to a stronger-than-anticipated headwind en route, he decided to divert to an intermediate airport to add fuel so that the airplane would have an adequate fuel reserve. Shortly afterward, while the airplane was in cruise flight, the engine "abruptly stopped, [with] no coughing or sputtering." The pilot attempted to determine the cause of the problem. He noted that the fuel selector was set for both tanks and that each tank was about one-quarter full. The pilot also attempted to restart the engine but was not successful; as a result, he executed a forced landing to an open field. The pilot noted that the airplane's airspeed might have decayed on final approach to the field, resulting in an aerodynamic stall and hard landing. Data from the airplane's avionics system indicated that engine performance was normal until about 15 minutes before the accident. At that time, the fuel flow varied over a 4-minute period. Afterward, the fuel flow returned to normal, and the engine's performance appeared stable. However, about 5 minutes before the accident, the fuel flow began to vary again and ultimately decreased to zero. The corresponding engine parameters also decreased at that time, which was consistent with a loss of power. The engine data revealed that a loss of fuel flow to the engine precipitated the loss of power. However, a postaccident examination and a test run of the engine did not reveal any anomalies consistent with a loss of engine power. Specifically, the engine test run demonstrated operation of the engine, and no airframe fuel system obstructions or evidence of fuel leakage were observed. In addition, the fuel consumption for the accident flight was about one-half of the total usable fuel capacity, which excluded fuel exhaustion as a cause for the loss of engine power.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Fuel starvation during enroute defining event
  2. Off-field or emergency landing during emergency descent
  3. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Not specified other cases naming the fuel system
  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • factor Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • factor Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation

Pilot

  • Certificate: private
  • Ratings: single-engine land; single-engine sea
  • Flight time: 695 hours in all; 695 in this make and model; 55 in the last 90 days; 40 in the last 30 days; 586 as pilot in command
  • Last flight review: April 8, 2017
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: frt
  • Injury: minor injuries

The aircraft

  • Airframe total time: 642.1 hours
  • Last inspection: condition inspection, June 30, 2017; 20 hours since
  • Maximum gross weight: 1,320 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Titan OX-340CC-B3J3 (piston); 507 hours total

The flight

  • Departed from: ABR Aberdeen SD at 6:10 pm
  • Destination: RAP Rapid City SD
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 310° at 10 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 106°F (41°C), dew point 48°F (9°C)
  • Altimeter: 29.79 inHg
  • Observation at 6:55 pm from PHP, 25 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

13 documents, released by the NTSB on June 13, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN17LA265.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.