# Accident 19990611023989A: Cessna 172P, Ravenna, OH, June 11, 1999 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: June 11, 1999, 00:15 local time - Place: Ravenna, OH - Airport: Portage County Airport - Damage: Substantial damage - Phase of flight: To Aborted (Fixed Wing) - Operating rules: General operating rules (Part 91) - Location: 41.1498° N, 81.2404° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=41.1498&lon=-81.2404&mi=10 - Aircraft: N62953, registered now (https://openairdocs.org/aircraft/N62953) (OpenAirDocs) - Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs) - Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs) - Reported make and model: CESSNA 172P - People aboard: 2 - Fatal injuries: 0 - NTSB investigation: [NTSB NYC99LA137](https://openairdocs.org/ntsb/NYC99LA137) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/19990611023989A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (.19) ON JUNE 11, 1999, ABOUT 0015 EASTERN DAYLIGHT TIME, A CESSNA 172, N62953, WAS SUBSTANTIALLY DAMAGED DURING AN ABORTED LANDING AT PORTAGE COUNTY AIRPORT (29G), RAVENNA, OHIO. THE CERTIFIED FLIGHT INSTRUCTOR (CFI) AND STUDENT PILOT WERE NOT INJURED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED FOR THE FLIGHT THAT ORIGINATED FROM KENT STATE UNIVERSITY AIRPORT, KENT, OHIO. NO FLIGHT PLAN WAS FILED FOR THE INSTRUCTIONAL FLIGHT CONDUCTED UNDER 14 CFR PART 91. THE STUDENT PILOT STATED THAT HE AND THE CFI COMPLETED THREE FULL STOP LANDINGS BEFORE THE ACCIDENT, AND EXPERIENCED NO PROBLEMS WITH THE BRAKES. THE AIRPLANE LANDED ON RUNWAY 27, A 3,500 FOOT LONG, 75 FOOT WIDE RUNWAY. ACCORDING TO THE STUDENT PILOT, DURING THIS APPROACH, HE LANDED "ABOUT HALF WAY DOWN THE RUNWAY." HE DID NOT FEEL THE BRAKES WORKING PROPERLY, AND PROCEEDED TO ABORT THE LANDING. THE AIRPLANE BECAME AIRBORNE AT THE END OF THE RUNWAY, BUT SETTLED TOWARD THE GROUND. THE FLIGHT INSTRUCTOR TOOK CONTROL OF THE AIRPLANE, AND PERFORMED A FORCED LANDING TO A FIELD. THE STUDENT PILOT FURTHER STATED THAT HE LATER WENT BACK TO THE AIRPORT AND OBSERVED APPROXIMATELY 800 TO 1,000 FEET OF SKID MARKS ON THE RUNWAY, BE GINNING BEYOND THE TOUCHDOWN POINT, EXTENDING TO WHERE THE AIRPLANE BECAME AIRBORNE AGAIN. THE CFI STATED THAT THE AIRPLANE TOUCHED DOWN AT ABOUT 55 KNOTS, WITH APPROXIMATELY 2,000 FEET OF RUNWAY REMAINING. HE DID NOT FEEL THE AIRPLANE SLOWING, AND DEPRESSED THE BRAKES. HE NOTICED THAT THE AIRPLANE WAS NOT BRAKING EFFECTIVELY, AND INSTRUCTED THE STUDENT PILOT TO ABORT THE LANDING. AS THE AIRPLANE PASSED OVER THE DEPARTURE END OF THE RUNWAY, IT BEGAN TO LOSE LIFT. AT THIS POINT, THE CFI TOOK CONTROL OF THE AIRPLANE AND PERFORMED A FORCED LANDING TO A FIELD. WHEN ASKED ABOUT THE SKID MARKS, HE STATED THAT ALTHOUGH THE BRAKES DID NOT SEEM TO BE WORKING DURING ROLLOUT, THEY MUST HAVE WORKED DURING THE ABORTED LANDING. HE BELIEVES THE STUDENT PILOT MAY HAVE "DRAGGED THE BRAKES" DURING THE ABORTED LANDING. ACCORDING TO THE OWNER OF THE FLIGHT SCHOOL, HE INSPECTED THE BRAKES AFTER THE ACCIDENT AND FOUND NO MECHANICAL MALFUNCTIONS. HE ALSO SENT THE AIRPLANE TO AN INDEPENDENT MAINTENANCE FACILITY. THE FACILITY DID NOT FIND ANY DISCREPANCIES WITH THE BRAKING SYSTEM. THE OWNER FURTHER STATED THAT THE AIRPLANE HAD UNDERGONE AN ANNUAL INSPECTION THE DAY BEFORE THE ACCIDENT, AND THE FLI IGHT WAS THE FIRST AFTER THE INSPECTION. NEW TIRES WERE MOUNTED ON THE AIRPLANE DURING THE ANNUAL INSPECTION. WHILE INSPECTING THE WRECKAGE, HE NOTICED SIGNIFICANT WEAR ON BOTH TIRES. EXAMINATION OF THE WRECKAGE BY A FEDERAL AVIATION ADMINISTRATION INSPECTOR REVEALED NO MECHANICAL MALFUNCTIONS. THE INSPECTOR OBSERVED SKID MARKS BEGINNING APPROXIMATELY 300 FEET FROM THE DEPARTURE END OF THE RUNWAY, AND ENDING APPROXIMATELY 2 FEET BEFORE THE END OF THE RUNWAY. THE SKID MARKS WERE IN LINE WITH MARKS ON THE GRASS WHERE THE AIRPLANE HAD TRAVELED OFF THE END RUNWAY. (-23)UPON LANDING AT 29G, STUDENT PILOT NOTICED THE BRAKES WERE NOT FUNCTIONING PROPERLY. ATTEMPTED A GO-AROUND. DID NOT GET CLIMB PERFORMANCE EXPECTED AND FLIGHT INSTRUCTOR ABORTED THE MANUEVER, LANDING WEST OF THE RUNWAY IN A FIELD. AIRCRAFT CAME TO REST 300 YARDS WEST OF THE RUNWAY IN A BRUSH FIELD. INSTRUCTOR AND STUDENT WERE NOT INJURED. ## 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 NYC99LA137](https://openairdocs.org/ntsb/NYC99LA137), Jun 11, 1999: Cessna 172 (N62953), Ravenna, OH, substantial damage. Probable cause: The pilot-in-command's failure to maintain aircraft control during landing. ## Other reports on N62953 (1) Matched to the same aircraft by N-number and date. - [Accident 19870808043919A](https://openairdocs.org/incident/19870808043919A), Aug 8, 1987: Cessna 172P (N62953), Stow, OH, Substantial damage. Hard landing. Touch and go landings. Lost directional control. Veered off runway. Collided with a windsock pole. 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.