# Accident 20000207007319A: Cessna 172R, Olive Branch, MS, February 7, 2000 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: February 7, 2000, 14:35 local time - Place: Olive Branch, MS - Airport: Olive Branch Airport - Damage: Substantial damage - Phase of flight: Touch And Go Landing - Operating rules: General operating rules (Part 91) - Location: 34.9501° N, 89.8193° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=34.9501&lon=-89.8193&mi=10 - Aircraft: N2630B, a cancelled registration (https://openairdocs.org/deregistered/N2630B-2014-09-17) (OpenAirDocs) - Registry model: Cessna 172R (registry code 2072401, https://openairdocs.org/model/cessna-172r) (OpenAirDocs) - Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs) - Reported make and model: CESSNA 172R - Reported engine: LYC IO360L2A - People aboard: 1 - Fatal injuries: 0 - Pilot certificates: Student - Pilot flight hours: 36 total, 36 in this make and model, 14 in the last 90 days - NTSB investigation: [NTSB MIA00LA086](https://openairdocs.org/ntsb/MIA00LA086) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20000207007319A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23) PILOT WAS LANDING ON RUNWAY 36, WITH THE WINDS REPORTED FROM 280 @ 8 TO 10 KTS. DURING LANDING STUDENT PILOT ENCOUNTERED A GUST OF WIND AND FAILED TO COMPENSATE AND LOSS CONTROL OF AIRCRAFT. NO INJURY TO PILOT AIRCRAFT RECEIVED SUBSTANTIAL DAMAGE. (.4)ON FEBRUARY 7, 2000, ABOUT 1435 CENTRAL STANDARD TIME, A CESSNA 172R, N2630B, REGISTERED TO DOUGLAS AVIATION, INC., OPERATING AS A TITLE 14 CFR PART 91 INSTRUCTIONAL FLIGHT, CRASHED DURING A LANDING AT OLIVE BRANCH, MISSISSIPPI. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AND NO FLIGHT PLAN WAS FILED. THE AIRPLANE RECEIVED SUBSTANTIAL DAMAGE AND THE STUDENT PILOT, THE SOLE OCCUPANT, WAS NOT INJURED. THE FLIGHT ORIGINATED FROM THE SAME AIRPORT ABOUT 55 MINUTES BEFORE THE ACCIDENT. ACCORDING TO THE ASSISTANT CHIEF FLIGHT INSTRUCTOR FOR THE FLIGHT SCHOOL, THE STUDENT PILOT WAS CONDUCTING PRACTICE LANDINGS WHEN HE OVERCORRECTED FOR A CROSSWIND CONDITION AND RAN OFF THE SIDE OF THE RUNWAY, COLLIDING WITH A RUNWAY SIGN. ACCORDING TO THE STUDENT PILOT, HE HAD MADE ONE SUCCESSFUL TOUCH-AND-GO LANDING, AND THE ACCIDENT HAPPENED ON HIS SECOND LANDING, AT TOUCHDOWN. UPON MAIN LANDING GEAR TOUCHD OWN, THE AIRPLANE SWERVED LEFT AND HE CORRECTED WITH RIGHT RUDDER. UPON APPLICATION OF RIGHT RUDDER, THE RIGHT MAIN LANDING GEAR CAME OFF THE GROUND, AND HE THEN APPLIED HEAVY BRAKING TO BOTH MAIN WHEELS. THE AIRPLANE EXITED THE RUNWAY AND THE RIGHT MAIN LANDING GEAR COLLAPSED AS IT COLLIDED WITH A TAXIWAY SIGN. THE AIRPLANE CAME TO REST ON ITS RIGHT SIDE, SEVERELY BENDING THE RIGHT HORIZONTAL STABILIZER. HE STATED THAT HE EXPERIENCED NO MECHANICAL MALFUNCTIONS WITH THE AIRPLANE ON LANDING, AND THAT HE MAY HAVE INADVERTENTLY STEPPED ON THE LEFT TOE BRAKE. INSPECTION OF THE AIRPLANE BY FAA PERSONNEL REVEALED NO EVIDENCE OF PRECRASH ABNORMALITIES WITH THE FLIGHT CONTROLS. THE RIGHT MAIN LANDING GEAR AND THE NOSE GEAR REVEALED GROUND COLLISION DAMAGE, BUT THERE WAS NO EVIDENCE OF PROPELLER DAMAGE. THE RIGHT HORIZONTAL STABILIZER SPAR WAS BROKEN. ## 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 MIA00LA086](https://openairdocs.org/ntsb/MIA00LA086), Feb 7, 2000: Cessna 172R (N2630B), Olive Branch, MS, substantial damage. Probable cause: The student pilot's failure to maintain directional control during landing and the subsequent collision with a taxiway sign and collapsed right main landing gear. ## Other reports on N2630B (2) Matched to the same aircraft by N-number and date. - [Accident 20140407004269A](https://openairdocs.org/incident/20140407004269A), Apr 7, 2014: Cessna 172R (N2630B), Daytona Beach, FL, Substantial damage. On April 7, 2014, at approximately 1830 N2630B, operating under phoenix one four (PX14), landed in dab on runway 25L and was taxing back on taxiway whiskey to… - [Incident 20130914018651I](https://openairdocs.org/incident/20130914018651I), Sep 14, 2013: Cessna 172R (N2630B), Daytona Beach, FL, Minor damage. A student assigned to phoenix east aviation LLC. In Daytona Beach was involved in a ground mishap between two aircraft during taxi back to the ramp (N2630B)… 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.