# Accident 19960312005789A: Cessna 152, Baxley, GA, March 12, 1996

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 12, 1996, 16:30 local time
- Place: Baxley, GA
- Airport: Baxley Municipal Airport
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 31.7590° N, 82.3502° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=31.7590&lon=-82.3502&mi=10
- Aircraft: N105AT, a cancelled registration (https://openairdocs.org/deregistered/N105AT-2012-09-06) (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 O235*
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 173 total, 143 in this make and model, 12 in the last 90 days
- NTSB investigation: [NTSB ATL96LA064](https://openairdocs.org/ntsb/ATL96LA064) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960312005789A

## Narrative

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

(.19) ON MARCH 12, 1996, AT 1630 EASTERN DAYLIGHT TIME, A CESSNA 152, N105AT, WAS SUBSTANTIALLY DAMAGED FOLLOWING A LOSS OF CONTROL AND NOSE OVER DURING LANDING AT THE BAXLEY MUNICIPAL AIRPORT IN BAXLEY, GEORGIA. NO INJURIES WERE INCURRED BY THE PRIVATE PILOT OR HIS PASSENGER IN THE ACCIDENT.  THE AIRCRAFT WAS BEING OPERATED UNDER THE PROVISIONS OF TITLE 14 CFR PART 91 BY THE PILOT.  VISUAL METEOROLOGICAL CONDITIONS EXISTED AT THE TIME OF THE ACCIDENT, AND NO FLIGHT PLAN HAD BEEN FILED FOR THE PERSONAL FLIGHT.  THE FLIGHT DEPARTED ST. PETERSBURG, FLORIDA, AT ABOUT 1500.  THE PILOT STATED THAT  DURING THE FIRST LANDING ATTEMPT, HE FELT AND HEARD THE NOSE GEAR COLLAPSE, AS THE AIRPLANE TOUCHED DOWN ON THE RUNWAY. AT THIS POINT THE PILOT EXECUTED A GO-AROUND AND ESTABLISHED A TRAFFIC PATTERN FOR RUNWAY 26. WHILE ESTABLISHING THE APPROACH, THE PILOT REALIZED THAT THE NOSE GEAR HAD SEPARATED AND THE LEFT RUDDER PEDAL WAS STUCK ON THE FLOOR, AND HE HAD NO RUDDER CONTROL. ON THE SECOND LANDING ATTEMPT HE SHUT DOWN THE ENGINE AND THE PROPELLER STOPPED HORIZONTALLY. THE PILOT HELD THE NOSE OFF AS LONG AS POSSIBLE. HE STATED THAT WHEN THE NOSE WHEEL TOUCHED DOWN, THE AIRCRAFT VEERED OFF THE RIGHT SIDE OF THE RUNWAY, AND NOSED OVER IN THE SOD AREA NEXT TO THE RUNWAY. (.4) ACCORDING TO THE PILOT, DURING THE FLARE TO TOUCHDOWN PHASE OF THE APPROACH, THE AIRPLANE DROPPED ONTO THE RUNWAY. AS THE AIRPLANE TOUCHED DOWN, THE PILOT FELT AND HEARD THE NOSE GEAR ASSEMBLY COLLAPSE. AFTER THE TOUCHDOWN, THE PILOT APPLIED POWER AND EXECUTED A GO-AROUND. WHILE THE PILOT MANEUVERED FOR THE SECOND APPROACH, HE NOTED THAT THE LEFT RUDDER PEDAL WAS STUCK ON THE FLOOR AND HE DID NOT HAVE TOTAL RUDDER CONTROL. AFTER THE LANDING, THE PILOT HELD THE NOSE OFF THE RUNWAY AS LONG AS POSSIBLE. WHEN THE NOSE SECTION TOUCHED DOWN, THE AIRPLANE VEERED OFF THE RUNWAY, AND NOSED OVER IN THE SOD AREA NEXT TO THE RUNWAY. EXAMINATION OF THE AIRPLANE FAILED TO DISCLOSE A MECHANICAL PROBLEM, NOR DID THE PILOT REPORT A MECHANICAL PROBLEM. ACCORDING TO THE FIXED BASE OPERATOR, THE WINDS WERE SHIFTING BETWEEN 300 AND 010 DEGREES AS THE PILOT ATTEMPTED THE FIRST LANDING.

## 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 ATL96LA064](https://openairdocs.org/ntsb/ATL96LA064), Mar 12, 1996: Cessna 152 (N105AT), Baxley, GA, substantial damage. Probable cause: the pilot's improper flare, which resulted in a hard landing, a collapsed nose gear, and a subsequent nose over.

## Other reports on N105AT (4)

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

- [Incident 20021106032029I](https://openairdocs.org/incident/20021106032029I), Nov 6, 2002: Cessna 152 (N105AT), Bethel, AK, Minor damage. (-23) Mr. Amos and his student were conducting an engine run-up in CE-152, N105AT. They were not in motion. They were parked on golf taxiway. During the course…
- [Incident 19921013046459I](https://openairdocs.org/incident/19921013046459I), Oct 13, 1992: Cessna 152 (N105AT), Cedar Key, FL, Minor damage. Pilot failed to accelerate to rotation speed. Aborted. Departed end of runway. Hit a bush.
- [Incident 19900921062549I](https://openairdocs.org/incident/19900921062549I), Sep 21, 1990: Cessna 152 (N105AT), St Petersburg-C, FL, Minor damage. Aircraft bounced on landing. Wheel separated from aircraft. Skidded to stop.
- [Incident 19881104060779I](https://openairdocs.org/incident/19881104060779I), Nov 4, 1988: Cessna 152 (N105AT), Macon, GA. VFR pilot caught on top was assisted by ATC to descend below clouds for a safe landing.

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.
