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

Cessna 172N accident near Appleton, Wisconsin, March 31, 2011

On March 31, 2011 at about 8:25 pm local time, a Cessna 172N, registered N73836, was substantially damaged in an accident during takeoff near Appleton, Wisconsin (Outagamie County Regional Arpt airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The student pilot's failure to maintain directional control of the airplane during takeoff.

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

What the record shows

Date
March 31, 2011 · about 8:25 pm local time
Place
Appleton, Wisconsin · Outagamie County Regional Arpt · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172N · all 172Ns on the register
Registration
N73836 · no longer on the register · serial 17267710
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The student pilot stated that he performed a short field takeoff. He said he accelerated the airplane to about 58 knots indicated airspeed and the airplane veered left. He reduced the power and applied right rudder to keep the airplane on the runway, but the airplane exited the runway and cartwheeled on its nose. The airplane sustained substantial damage to its fuselage and wings. The pilot reported that there were no mechanical malfunctions with the airplane. He said that he may have inadvertently applied left toe brake during the takeoff.

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. Loss of control on ground during takeoff defining event
  2. Runway excursion during takeoff
  3. Nose over/nose down during takeoff

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • cause Personnel issues › Task performance › (general) › (general) › Pilot

Pilot

  • Certificate: student
  • Flight time: 47 hours in all; 41 in this make and model; 8 in the last 90 days; 7 in the last 30 days
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 7,451 hours
  • Last inspection: annual inspection, January 24, 2011
  • Maximum gross weight: 2,300 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320-H2AD (piston); 0 hours total

The flight

  • Departed from: ATW Appleton WI at 8:30 pm
  • Destination: ATW Appleton WI
  • Flight plan: none
  • Runway 30, 6,501 ft by 150 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: scat at 12,000 ft
  • Temperature: 45°F (7°C), dew point 14°F (-10°C)
  • Altimeter: 29.73 inHg
  • Observation at 8:31 pm from ATW

Injuries

FatalSeriousMinorNone
Flight crew1

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

1 document, released by the NTSB on May 2, 2011. 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.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.