# Incident 19930526019169I: Cessna 152, Tulsa, OK, May 26, 1993

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 26, 1993, 15:57 local time
- Place: Tulsa, OK
- Airport: Richard Lloyd Jones Jr Airport
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Operator: CB9T
- Location: 36.1540° N, 95.9928° W: Placed by OpenAirDocs: center of Tulsa, OK, within about 8 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.1540&lon=-95.9928&mi=10
- Aircraft: N4655P, registered now (https://openairdocs.org/aircraft/N4655P) (OpenAirDocs)
- Registry model: Cessna 152 (registry code 2071835, https://openairdocs.org/model/cessna-152) (OpenAirDocs)
- Reported make and model: CESSNA 152
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 37 total, 37 in this make and model, 25 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19930526019169I

## Narrative

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

STUDENT PILOT MADE A HARD LANDING.

## Other reports on N4655P (3)

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

- [Incident 19970408005369I](https://openairdocs.org/incident/19970408005369I), Apr 8, 1997: Cessna 152 (N4655P), Purcell, OK, Minor damage. Narrative: on April 8, 1997, at Chandler field, Purcell, OK, the pilot of a Cessna 152, N4655P, was performing touch and goes. During takeoff, the engine lost…
- [Accident 19851214076139A](https://openairdocs.org/incident/19851214076139A), Dec 14, 1985: Cessna 152 (N4655P), Aurora, IL, Substantial damage. Aborted takeoff due to low airspeed reading and landed nose low. Airspeed indicator reading 8 to 10 knots low.
- [Incident 19850910058859I](https://openairdocs.org/incident/19850910058859I), Sep 10, 1985: Cessna 152 (N4655P), Aurora, IL. CFI did not follow nor acknowledge ATC taxi instructions. Pulled onto active runway with traffic on final.

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.