# Accident 20020404007699A: Cessna 172P, Pensacola, FL, April 4, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 4, 2002, 17:00 local time
- Place: Pensacola, FL
- Airport: Ferguson Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 30.3986° N, 87.3486° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=30.3986&lon=-87.3486&mi=10
- Aircraft: N64079, registered now (https://openairdocs.org/aircraft/N64079) (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
- NTSB investigation: [NTSB ATL02LA073](https://openairdocs.org/ntsb/ATL02LA073) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020404007699A

## Narrative

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

(-23) PILOT WHILE ATTEMPTING TO LAND, LOST CONTROL OF AIRCRAFT AND STRUCK TREES WITH LEFT WING ON THE WEST SIDE OF THE RUNWAY (36). SUBSTANTIAL DAMAGE TO LEFT WING, AND FUSELAGE. INSPECTION OF FLIGHT CONTROLS REVEALED FULL CONTINUITY. LANDING GEAR (FIXED) AND BRAKES WERE IN GOOD CONDITION AND FUNCTIONED NORMALLY. FLAPS WERE AT 10 (BOTH POSITION & INDICATED), SELECTOR WAS AT 30. MIKE JACK WAS NOT FULLY INSERTED INTO RECEPTACLE AND WOULD NOT TRANSMIT OUT. PILOT ATTEMPTED TO MAKE THREE DOWNWIND LANDINGS (RUNWAY 18) WITH WINDS FROM THE NORTH (RUNWAY 36) AT 20 KNOTS AND GUSTY. ON THIRD ATTEMPT PILOT DID A QUICK 180 (TURNING RIGHT) AT THE SOUTH END OF RUNWAY 36 RESULTING IN A LANDING LEFT OF CENTER ON TOUCHDOWN THEN VEERED INTO THE TREES. SKID MARKS IN GRASS INDICATED HEAVY USE OF RIGHT BRAKE INITIALLY AND FINALLY BOTH BRAKES IN AN ATTEMPT TO STOP AIRCRAFT FROM IMPACTING TREES. (.19) ON APRIL 4, 2002, AT 1730 CENTRAL STANDARD TIME, A CESSNA 172P, N64079, REGISTERED TO FERGUSON AVIATION, COLLIDED THE GROUND DURING AN ATTEMPTED LANDING AT FERGUSON AIRPORT IN PENSACOLA, FLORIDA. THE PERSONAL FLIGHT WAS OPERATED BY THE PILOT UNDER THE PROVISIONS OF TITLE 14 CFR PART 91 WITH NO               FLIGHT PLAN FILED. VISUAL WEATHER CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT. THE AIRPLANE SUSTAINED SUBSTANTIAL DAMAGE: THE PRIVATE PILOT AND HIS PASSENGER WERE NOT INJURED. THE FLIGHT DEPARTED PENSACOLA, FLORIDA, AT AN UNDETERMINED TIME. ACCORDING TO THE FIXED BASE OPERATOR, THE PILOT HAD BEEN CONDUCTING A PLEASURE FLIGHT, WHICH INCLUDED CLOSED TRAFFIC AT THE PRIVATE AIRPORT. THE PILOT HAD ATTEMPTED SEVERAL APPROACHES TO RUNWAY 18 WITHOUT LANDING. ON THE ACCIDENT APPROACH, THE PILOT DECIDED TO LAND. ACCORDING TO A WITNESS, THE AIRPLANE APPEARED TO HAVE STALLED OVER THE RUNWAY PRIOR TO THE COLLISION WITH THE GROUND. REPORTEDLY, THE PREVAILING WINDS WERE 330 DEGREES AT 12 KNOTS AT THE APPROXIMATE TIME OF THE ATTEMPTED 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 ATL02LA073](https://openairdocs.org/ntsb/ATL02LA073), Apr 4, 2002: Cessna 172P (N64079), Pensacola, FL, substantial damage. Probable cause: The pilot's inadequate compensation for a crosswind and his failure to maintain directional control during the landing roll. Contributing to the accident was the pilot's decision to land with a…

## Other reports on N64079 (1)

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

- [Accident 19830618026369A](https://openairdocs.org/incident/19830618026369A), Jun 18, 1983: Cessna 172P (N64079), Pensacola, FL, Substantial damage. Struck a pine tree while flying at 30 feet to show passengers speed sensation. Flew back to base.

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.