# Incident 20000718025579I: Cessna 172P, Jessup, GA, July 18, 2000

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 18, 2000, 18:00 local time
- Place: Jessup, GA
- Airport: Jessup-Wayne County Airport
- Damage: Minor damage
- Phase of flight: To Aborted (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 31.6607° N, 81.9294° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=31.6607&lon=-81.9294&mi=10
- Aircraft: N51996, registered now (https://openairdocs.org/aircraft/N51996) (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: 1
- Fatal injuries: 0
- NTSB investigation: [NTSB MIA00LA223](https://openairdocs.org/ntsb/MIA00LA223) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000718025579I

## Narrative

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

(-23)STUDENT APPROACHED JES (HESUP WAYNE CO.) FROM S.E @ APPROX 2500', RECEIVED JES WX INFO VIA AWOS PRIOR TO ARRIVING @ APT ON FRQ 340 FLEW OVER MID FIELD @ 1500' DETERMINED FROM THE WIND SOCK WINDS INFO RECEIVED THAT THEY WERE STRAIGHT DOWN RWY 10. CALLED TRAFFIC AND ADVISED THEM OF INTENTIONS.  ENTERED THE LEFT DOWNWIND FOR RWY 10 AFTER DESENDING TO T.P.A NO TRAFFIC IN PATTERN @ APT APPROACH AND LANDING SUCCESSFUL-TOUCHING DOWN ON MAIN GEAR 1ST.  NOT SMOOTH BUT OK.  COME TO FULL STOP AND CLEANED UP. FLAPS UP, CARB HEAT OFF ETC.  APPLYING FULL POWER STICKS WHEN TO ADVANCE IT--THE PLANE STARTED TO FISH TAIL, RETARDED THE THROTTLE TO REGAIN CONTROL, BUT WAITED TO APPLY BRAKES THERE WAS SUFF RWY TO COMPLETE A NORMAL T/O, FULL THROTTLE AGAIN TRIED TO STEER WITH RUDDERS-WAS LOSING CONTROL AGAIN, ABORTED TAKE-OFF-PULLED THROTTLE BACK, APPLIED NECESSARY BRAKING, TRYING TO COME TO A COMPLETE STOP USING RUDDER FOR DIRECTIONAL CONTROL WIND RIGHT DOWN RWY NO AILERON CORRECTION PUT IN PLANE VEERED TO LEFT OFF RWY AND FLIPPED OVER, BENDING BOTH WINGS, PROP AND VERTICAL STAB.

## 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 MIA00LA223](https://openairdocs.org/ntsb/MIA00LA223), Jul 18, 2000: Cessna 172P (N51996), Jesup, GA, substantial damage. Probable cause: The failure of the student pilot to maintain directional control during takeoff resulting in an excursion off the runway and collision with adjacent foliage. A factor in the accident was the…

## Other reports on N51996 (3)

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

- [Incident 20190816014309I](https://openairdocs.org/incident/20190816014309I), Aug 16, 2019: Cessna 172P (N51996), Sanford, FL, Minor damage. A Cessna 172 aircraft operated by L3 harris reported a bird strike on approach into Sanford international airport (ksfb). The pilot stated that they were on an…
- [Incident 20190427022779I](https://openairdocs.org/incident/20190427022779I), Apr 27, 2019: Cessna 172P (N51996), Sanford, FL, No damage. Reported by air traffic: Orlando, FL (sfb): CONN202, C172, veered off the side of runway 9R during a landing. There was no damage to any surface equipment.…
- [Incident 20150124004299I](https://openairdocs.org/incident/20150124004299I), Jan 24, 2015: Cessna 172P (N51996), Sanford, FL, Minor damage. On 1/24/2015, at Orlando Sanford International Airport, the CFI was giving instruction in the pattern to a student pilot. During the 12th landing on rwy 27L…

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.