FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16LA288 · Cessna 208B B

21 Jul 2016 · Baldwin, WI, United States

Cessna 208B B · Accident: runway excursion during landing

From Baldwin Airport (WI14) to Baldwin Airport (WI14)

Report a problem

Event

NTSB case
CEN16LA288
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 208B B

Aircraft type
Cessna 208
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N7581F
Onboard fatalities
Unknown
Route
From Baldwin Airport (WI14), Baldwin, WITo Baldwin Airport (WI14), Baldwin, WI
Aircraft age
About 22 years (built 1994)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Runway excursion
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16LA288
Event ID
20160727X44252
Case number
CEN16LA288
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 24da33e74622b24761a27ccc50cb0d9d9e4a2359160a417df386b1978e518d3f; retrieved 2026-09-16T03:42:38.737Z.