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

Cessna R182 accident near Mooresville, North Carolina, March 29, 2017

On March 29, 2017 at about 5:25 pm local time, a 1978 Cessna R182, registered N2383C, was substantially damaged in an accident during takeoff near Mooresville, North Carolina (Atwell airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to properly configure the airplane's flaps for takeoff, which resulted in a longer ground roll and subsequent runway excursion.

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

What the record shows

Date
March 29, 2017 · about 5:25 pm local time
Place
Mooresville, North Carolina · Atwell · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna R182 NO SERIES, built 1978 · all R182s on the register
Registration
N2383C · no longer on the register · serial R18200171
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

After an uneventful preflight inspection and engine runup, the private pilot attempted to take off from a 1,700-ft-long turf runway for the personal flight. During the takeoff roll, as the airplane reached a point on the runway where it would normally lift off (about 1,200 ft down the runway), the pilot pulled back on the yoke, but the airplane did not climb. The pilot recalled that the airspeed was close to 60 knots; he did not recall any engine instrument indications and noted that the engine sounded normal. When he realized that the airplane was not going to take off and a collision appeared imminent, he advised his passenger to prepare for impact. As the airplane approached a fence just beyond the departure end of the runway, he pulled back on the yoke and the airplane lifted off, flew over the fence, then descended and struck another fence before coming to rest in the driveway of his residence. Examination of the airframe and engine did not reveal any evidence of preimpact mechanical malfunctions or anomalies that would have precluded normal operation. Given this and the pilot's description that the engine appeared to be operating normally during the takeoff, it is unlikely that a partial loss of engine power contributed to the accident. Review of takeoff performance data in the pilot operating handbook for the airplane make and model revealed that, given the airplane's weight and approximate weather conditions around the time of the accident, the airplane should have been able to become airborne with the runway available; however, the data assumed the flaps were set to 20° extension. Although the pilot believed the flaps were "down" when he started the takeoff roll, he noticed that they were "up" after the accident, which suggests that he may not have actually set them to 20° before initiating the takeoff. This fully retracted flap setting may have reduced the airplane's takeoff performance and resulted in a longer ground roll than expected.

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. Miscellaneous/other during takeoff defining event
  2. Runway excursion during takeoff
  3. Collision with terrain or object (not controlled flight into terrain) during emergency descent

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Forgotten action/omission › Pilot
  • cause Aircraft › Aircraft structures › Wing structure › Trailing edge flaps › Incorrect use/operation
  • Environmental issues › Physical environment › Object/animal/substance › Fence/fence post › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 986 hours in all; 90 in this make and model; 6 in the last 90 days; 0 in the last 30 days; 924 as pilot in command
  • Last flight review: March 10, 2015
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 1,822 hours
  • Last inspection: annual inspection, September 10, 2016; 19 hours since
  • Maximum gross weight: 3,100 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming O-540 (piston); 1,822 hours total
  • Operator: Scott Atwell Insurance Services INC

The flight

  • Departed from: 1NC2 Mooresville NC at 6:25 pm
  • Destination: 12TN Kingston TN
  • Flight plan: none
  • Runway 36, 1,700 ft by 60 ft

Weather at the time

  • Light: daylight
  • Wind: from 080° at 5 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 4,700 ft
  • Temperature: 72°F (22°C), dew point 52°F (11°C)
  • Altimeter: 30.06 inHg
  • Observation at 5:20 pm from KSVH, 10 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

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