# NTSB MIA02LA158: Cessna 172N, N2291E, Tarboro, NC, August 25, 2002 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: August 25, 2002, 10:05 local (14:05 UTC) - Place: Tarboro, NC - Coordinates: 35.939445, -77.546669 - Nearby events: https://openairdocs.org/map.md?lat=35.9394&lon=-77.5467&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report December 6, 2002 - Report: Approved by Office Director - Parties: FAA FSDO - NTSB case key (mKey): 55594 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=MIA02LA158 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/55594/pdf - Page: https://openairdocs.org/ntsb/MIA02LA158 ## Probable cause 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. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, takeoff - roll/run - aircraft control - not maintained, pilot in command (cause) - On ground/water collision with object, takeoff - roll/run - object - tree(s) ## Analysis 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. ## Factual narrative On August 25, 2002, about 1005, eastern daylight time, a Cessna 172N, N2291E, registered to Aviation Consultants and Sales Inc., and operated by Wayne Aviation, as a Title 14 CFR Part 91 instructional flight, veered off the runway during takeoff at Tarboro, North Carolina. Visual meteorological conditions prevailed, and no flight plan was filed. The student-rated pilot was not injured, and the airplane incurred substantial damage. The flight originated from Greensboro, North Carolina, the same day, about 0925. The student stated that he was performing a short cross-country training 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 on to the grass. He said he attempted to use rudder control input to guide the airplane back on to the runway, but it responded slowly, and the airplane impacted some small trees, entered a small ditch, and flipped over incurring damage to the wings. Prior to the accident, there had been no mechanical failure or malfunction to the airplane or any of its systems. ## Aircraft - Registration: [N2291E](https://openairdocs.org/aircraft/N2291E), registered now, S/N 17271224, built 1978 (OpenAirDocs) - Reported make and model: Cessna 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17271224 - Airframe hours: 4277 - Engines: Textron Lycoming O-320-H2AD 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Wayne Aviation Inc. - Registered owner: Aviation Consultants and Sales Inc. - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, August 13, 2002, 38 hours before - Departed: GWW, Greensboro, NC - Destination: ETC, Tarboro, NC - Airport: ETC, Tarboro-Edgecombe, runway 09, 4,000 × 50 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 36; injuries: none; student; medical: class 3, valid medical--no waivers/lim.; seat: left; flight hours: 22 total, 22 in this make and model, 22 in the last 90 days, 5 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 0° at 0 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 81 °F, dew point 75 °F - Altimeter: 30.11 inHg - Observed at: RWI, 15 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20020825026429A](https://openairdocs.org/incident/20020825026429A), Aug 25, 2002: Cessna 172N, Tarboro, NC, Substantial damage. (-23) Student pilot was on cross country solo and was attempting touch and go landing at airport. After touchdown student pilot attempted to take off. Student… ## Other investigations on N2291E (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB CHI05LA070](https://openairdocs.org/ntsb/CHI05LA070), Feb 10, 2005: Cessna 172N (N2291E), Grafton, ND, substantial damage. Probable cause: The pilot's inadequate compensation for the wind conditions which resulted in a loss of directional control during the landing. Factors associated with the accident were the crosswind condition and… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.