# Accident 20000815014269A: Cessna 152, Gainesville, FL, August 15, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 15, 2000, 10:55 local time
- Place: Gainesville, FL
- Airport: Gainesville Regional Airport
- Damage: Substantial damage
- Phase of flight: Forced/Precautionary Landing
- Operating rules: General operating rules (Part 91)
- Location: 29.6701° N, 82.3305° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=29.6701&lon=-82.3305&mi=10
- Aircraft: N93589, a cancelled registration (https://openairdocs.org/deregistered/N93589-2018-01-30) (OpenAirDocs)
- Registry model: Cessna 152 (registry code 2071835, https://openairdocs.org/model/cessna-152) (OpenAirDocs)
- Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs)
- Reported make and model: CESSNA 152
- Reported engine: LYC O235L2C
- Fatal injuries: 0
- Pilot flight hours: 778 total, 295 in this make and model, 77 in the last 90 days
- NTSB investigation: [NTSB MIA00LA238](https://openairdocs.org/ntsb/MIA00LA238) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000815014269A

## Narrative

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

(-23) DURING CLIMB ENGINE RPM DECLINED AN D FLIGHT INSTUCTOR STARTED IMMEDIATE RETURN TO THE AIRPORT. DURING THE TURN THE A/C COLLIDED WITH PINE TREES APPROX. 200 FEET HIGH. AND SUBSEQUENTLY CRASHED TO THE GROUND. THE ENGINE SEPARATED FRO A/C AND NEITHER PILOT OR STUDENT PILOT SUSTAINED INJURIES. THE PIC REPORTED THAT THE STALL WARNING HORN SOUNDED JUST SECONDS BEFORE THE IMPACT WITH THE PINE TREES. THE A/C ENGINE WILL UNDER GO FURTHER TESTS BY THE ENGINE MFR. (ON 8-13-00 THE ENGINE WAS TEST RUN BY THE MANUFACTURER AND THE FAA FSDO 15 AND THERE WAS NO LOSS OF RPM. THE ENGINE REACHED AND MAINTAINED 2400 RPM)                                                            (.4) THE FLIGHT INSTRUCTOR STATED THAT DURING CLIMB AFTER TAKEOFF, THE ENGINE LOST POWER AND THE RPM DROPPED TO ABOUT 2,100. HE TOOK THE CONTROLS FROM THE STUDENT AND INITIATED A LEFT TURN BACK TOWARD THE AIRPORT. WHEN HE REALIZED HE COULD NOT MAKE THE AIRPORT, HE LANDED IN TREES. A WITNESS STATED THE ENGINE DID NOT SOUND LIKE IT WAS PRODUCING FULL POWER FROM THE BEGINNING OF TAKEOFF ROLL AND THE AIRPLANE MADE A LONG TAKEOFF ROLL USING ABOUT TWO THIRDS OF THE 4,158 FOOT RUNWAY. AFTER LIFTOFF, THE AIRPLANE CLIMBED SLOW A ND THE PILOT'S INITIATED A TURN TO THE LEFT WITH A NOSE HIGH ATTITUDE. THE AIRPLANE STALLED AND THE LEFT WING DROPPED. THE AIRPLANE DESCENDED AND CRASHED INTO THE TREES. HE HEARD THE ENGINE CONTINUE TO RUN UNTIL THE AIRPLANE CRASHED. POSTCRASH EXAMINATION OF THE ENGINE SHOWED THE SPARK PLUGS WERE FOULED WITH CARBON AND LEAD DEPOSITS AND THE PROPELLER BLADES WERE BENT FORWARD. THE ENGINE WAS STARTED AND OPERATED ROUGHLY TO 1,700 RPM. AFTER CLEANING THE PLUGS AND CHANGING THE BENT PROPELLER, THE ENGINE WAS STARTED AND OPERATED TO 2,200 RPM, FULL STATIC RPM.

## 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 MIA00LA238](https://openairdocs.org/ntsb/MIA00LA238), Aug 15, 2000: Cessna 152 (N93589), Gainesville, FL, substantial damage. Probable cause: The flight instructor's failure to identify a partial loss of engine power during takeoff roll, and his failure to maintain airspeed while attempting to return to the airport after takeoff resulting…

## Other reports on N93589 (1)

Matched to the same aircraft by N-number and date.

- [Accident 19860403009599A](https://openairdocs.org/incident/19860403009599A), Apr 3, 1986: Cessna 152 (N93589), Murfreesboro, TN, Substantial damage. Ballooned on landing. Left tire was off runway side on second touchdown. Unable to get back on runway. Hit a tree.

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.
