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

Cessna 172N accident near Tarboro, North Carolina, August 25, 2002

On August 25, 2002 at about 2:05 pm local time, a Cessna 172N, registered N2291E, was substantially damaged in an accident near Tarboro, North Carolina (Tarboro-Edgecombe 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 failure of the solo student to maintain directional control of the airplane during the takeoff roll/run which resulted in the airplane veering off the runway and impacting trees, incurring substantial damage.

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

What the record shows

Date
August 25, 2002 · about 2:05 pm local time · cases in 2002
Place
Tarboro, North Carolina · Tarboro-Edgecombe · cases near this airport · 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
N2291E · registry record · serial 17271224
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The student stated that he was performing a short cross-country flight, and during his approach to land he felt that he was a little too high, so he elected to perform a go-around. He said he then made two subsequent approaches to land and performed go-arounds each time because he felt that he was too high, and on his final attempt he was lower, and landed the airplane about 1/3 of the distance down the runway from the approach end. He said that during the landing rollout he then turned the carburetor heat off, but forgot to raise the flaps, and after applying full power to take off, the airplane veered sharply to the left, exiting the runway and subsequently impacted trees incurring damage. Prior to the accident, there had been no mechanical failure or malfunction to the airplane or any of its systems.

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

Dual student

  • Certificate: student
  • Flight time: 22 hours in all; 22 in this make and model; 22 in the last 90 days; 5 in the last 30 days
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,277 hours
  • Last inspection: 100-hour inspection, August 13, 2002; 38 hours since
  • Maximum gross weight: 2,300 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Textron Lycoming O-320-H2AD (piston); 0 hours total
  • Operator: Wayne Aviation Inc.

The flight

  • Departed from: GWW Greensboro NC at 1:25 pm
  • Destination: ETC Tarboro NC
  • Flight plan: none
  • Runway 09, 4,000 ft by 50 ft

Weather at the time

  • Light: daylight
  • Wind: at 0 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 1,400 ft
  • Temperature: 81°F (27°C), dew point 75°F (24°C)
  • Altimeter: 30.11 inHg
  • Observation at 2:21 pm from RWI, 15 miles away

Injuries

FatalSeriousMinorNone
Crew1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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

2005-02-10CHI05LA070 · accident near Grafton, ND · substantial damage · no injuries

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/MIA02LA158.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.