# Accident 20001022016219A: Cessna 172P, Knoxville, TN, October 22, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 22, 2000, 13:44 local time
- Place: Knoxville, TN
- Airport: Powell Stol
- Damage: Substantial damage
- Phase of flight: Climb
- Operating rules: General operating rules (Part 91)
- Location: 35.7901° N, 83.9690° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=35.7901&lon=-83.9690&mi=10
- Aircraft: N53512, a cancelled registration (https://openairdocs.org/deregistered/N53512-2001-03-05) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYC O320D2J
- Fatal injuries: 0
- Pilot flight hours: 91 total, 17 in this make and model, 23 in the last 90 days
- NTSB investigation: [NTSB MIA01LA013](https://openairdocs.org/ntsb/MIA01LA013) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20001022016219A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) A/C DEPARTED POWELL STOLPORT (9A2), VFR. PILOT ROTATED PREMATURELY AND WAS NOT ABLE TO GAIN FLYING SPEED DUE TO RISING TERRAIN. A/C STALLED AND CRASHED. (.4) THE PILOT STATED THAT HE ENGAGED 10 DEGREES OF FLAPS, HELD THE BRAKES AND APPLIED FULL POWER, BUT THE TAKEOFF ROLL WAS EXTREMELY BUMPY, AND THE AIRPLANE WAS NOT ACCELERATING AS IT SHOULD, AND THE REMAINING AVAILABLE RUNWAY WAS DECREASING. HE SAID THERE WERE TREES AT THE END OF THE RUNWAY, BUT HE DID NOT FEEL THAT HE COULD HAVE APPLIED THE BRAKES AND STOP THE TAKEOFF ROLL WITHOUT RUNNING INTO THEM, SO HE CONTINUED THE TAKEOFF. THE PILOT FURTHER STATED THAT HE FELT THAT THE AIRPLANE'S ACCELERATION WAS BEING IMPEDED BY THE CRACKS ON THE RUNWAY WHICH HAD GRASS GROWING IN THEM, SO HE DECIDED TO TRANSITION TO A SOFT FIELD TAKEOFF. HE SAID THAT INITIALLY THE CLIMBOUT WAS "OKAY", BUT THE PROXIMITY AND HEIGHT OF THE TREES REQUIRED THAT HE MAINTAIN APPROXIMATELY 60 KNOTS, AND AT THAT AIRSPEED THE AIRCRAFT SEEMED LESS AND LESS RESPONSIVE. HE SAID HE ATTEMPTED TO LOWER THE PITCH TO INCREASE THE AIRSPEED A COUPLE OF TIMES DURING THE CLIMBOUT, BUT THE AIRCRAFT SEEMED LE                                                                  SS AND LESS RESPONSIVE. ACCORDING TO THE PILOT, THE "PLANE FAILED TO PROVIDE THE NECESSARY LIFT IN ORDER TO CONTINUE THE CLIMBOUT, AND NOSE-DIVED TO THE GROUND." A WITNESS STATED THAT HE SAW THE ACCIDENT AIRCRAFT ROTATE AT THE MIDFIELD POINT, AND IT REMAINED IN AN EXTREME NOSE-UP ATTITUDE DURING CLIMBOUT. HE SAID HE THEN SAW THE AIRCRAFT "MUSH", AFTER WHICH THE LEFT WING ROSE BRIEFLY, AND THE AIRCRAFT TURNED TO THE LEFT, AND DESCENDED, IMPACTING THE GROUND. AN FAA INSPECTOR, ALONG WITH REPRESENTATIVES FROM CESSNA AIRCRAFT COMPANY, AND TEXTRON LYCOMING COMPANY, CONDUCTED POSTCRASH EXAMINATIONS OF THE ACCIDENT AIRCRAFT, AND NO PREACCIDENT FAILURES OR MALFUNCTIONS WERE FOUND WITH THE AIRCRAFT STRUCTURE, THE FLIGHT CONTROL SYSTEM, OR THE ENGINE.THE INSPECTOR FURTHER STATED THAT THE PILOT HAD ELECTED TO TAKE OFF USING AN UPSLOPING RUNWAY, TOWARDS RISING TERRAIN, WITH TREES AT THE END OF THE RUNWAY. THE WIND VELOCITY WAS ABOUT 4 KNOTS AT THE TIME OF THE ACCIDENT.

## The NTSB's investigation of this event (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 MIA01LA013](https://openairdocs.org/ntsb/MIA01LA013), Oct 22, 2000: Cessna 172P (N53512), Knoxville, TN, substantial damage. Probable cause: The pilot's failure to maintain Vs during takeoff/initial climb, which resulted in an inadvertent stall/mush, an uncontrolled descent, and an impact with the ground. Factors in the accident were the…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

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