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

Cessna 208B accident near Baldwin, Wisconsin, July 21, 2016

On July 21, 2016 at about 7:00 pm local time, a 1994 Cessna 208B, registered N7581F, was substantially damaged in an accident during landing (landing roll) near Baldwin, Wisconsin (Baldwin Airport). It was a skydiving flight under general aviation rules (Part 91). No one was hurt; 15 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's decision to land the fully loaded parachutist drop airplane on a wet grass runway that had insufficient length for the landing in high temperature conditions, which resulted in a runway overrun, when a more suitable longer runway was available at a nearby airport.

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

What the record shows

Date
July 21, 2016 · about 7:00 pm local time · cases in 2016
Place
Baldwin, Wisconsin · Baldwin Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 15 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 208B B, built 1994 · all 208Bs on the register
Registration
N7581F · registry record · serial 208B0389
Damage
Substantial damage
Flight
Skydiving flight · general aviation rules (Part 91)

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

Before the accident flight, the commercial pilot had conducted three flights, during which parachutists were successfully dropped. After each flight, he returned the empty airplane to a dry grass airstrip (1,950 ft long) and conducted full-stop landings. Because the temperature was over 90° with high humidity, the pilot requested that his manifests allow only up to 14 parachutists and a longer time between shutdowns to ensure sufficient time for adequate engine cooling before the next flight. The pilot reported that pop-up rain showers had been passing north and south of his base airport throughout the morning but that they never came closer than 10 to 15 miles. While preparing for the accident flight, the pilot noted that clouds were over the intended drop zone but that there was no rain and that the clouds were moving away from the northern edge of the drop zone, so the pilot decided that it was worth attempting the flight. While climbing through 4,000 ft, an air traffic controller advised the pilot that light-to-moderate precipitation was in the area. The pilot continued to climb toward the drop zone, and the flight encountered light rain. The pilot advised the 14 parachutists that they were returning to land because of the weather. The approach was a stabilized, power-on approach, which was much flatter than the previous approaches with an empty airplane. The pilot used flaps incrementally to 30° (full flaps), initiated a flare over the threshold, and touched down at 65 knots. He used full-reverse propeller and retracted the flaps during the landing roll. When the pilot started to apply the brakes, he discovered that the braking action was null. The grass runway was wet because of a recent rain shower. Because of the hot temperature, humidity, full load of parachutists, and trees at the end of the runway, the pilot decided not to attempt a go-around. The pilot held full aft on the control yoke for aerodynamic braking, stayed in full-reverse propeller, and braked as much as possible without locking the wheels up. Just before coming to a complete stop (about 5 to 10 mph), the airplane rolled into a ditch before a road beyond the departure end of the runway, which resulted in substantial damage to the empennage. According to the airplane manufacturer, the applicable Pilot's Operating Handbook (POH) tables did not provide distances for landing on wet grass runways. However, for landing on dry grass runways, 40% distance was added to the normal landing roll distance chart figures. The pilot reported that the airplane weighed 8,010 lbs, and the nearest weather reporting station to the accident site, located at an airport about 16 miles to the north, reported that the temperature was 30°C at the time of the accident. According to the POH chart, the minimum required landing distance would have been about 2,265 ft. The published length of the runway was 1,950 ft. The closest airport had an available runway that was 5,507 ft long, which would have been well within the safe stopping distance for the fully loaded airplane. The pilot's decision to land the fully loaded airplane on the wet grass runway that had insufficient length for the landing led to the runway overrun. If he had chosen to land at the nearby airport that had sufficient length for the landing, the accident may have been avoided.

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. Runway excursion during landing (landing roll) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Aircraft capability › Landing distance › Capability exceeded
  • Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › High temperature › Effect on equipment
  • Environmental issues › Physical environment › Runway/land/takeoff/taxi surface › Wet surface › Effect on operation

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 1,012 hours in all; 301 in this make and model
  • Last flight review: June 15, 2015
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 10,660 hours
  • Last inspection: 100-hour inspection, July 20, 2016; 1 hours since
  • Maximum gross weight: 9,062 lb
  • Seats: 19
  • Landing gear: fixed
  • Engine: Honeywell TPE331 (turboprop); 2,396 hours total

The flight

  • Departed from: WI14 Baldwin WI at 6:30 pm
  • Destination: WI14 Baldwin WI
  • Flight plan: none
  • Runway 18, 1,950 ft by 120 ft

Weather at the time

  • Light: daylight
  • Wind: from 280° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 86°F (30°C), dew point 72°F (22°C)
  • Altimeter: 29.95 inHg
  • Observation at 6:55 pm from RNH, 16 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers14

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

7 documents, released by the NTSB on June 29, 2017. 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.

Other NTSB records under N7581F the same tail number, which may have belonged to a different aircraft at the time

2022-06-03WPR22FA197 · accident near Oceanside, CA · substantial damage · fatal

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/CEN16LA288.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.