# Incident 20140116001519I: Cessna 152, Tulsa, OK, January 16, 2014

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 16, 2014, 10:35 local time
- Place: Tulsa, OK
- Airport: Riverside
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operator: SODS
- 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: N94268, a cancelled registration (https://openairdocs.org/deregistered/N94268-2020-06-22) (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: LYCOMING 0-235-N2C
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor, private pilot
- Pilot flight hours: 286 total, 202 in this make and model, 51 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20140116001519I

## Narrative

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

ON 01/16/2014 N94268, C152, ON LANDING TOUCHED DOWN HARD AND VERED RIGHT, OFF OF RWY. PROP STRUCK A TXY SIGN. @ 1035C.

1/16 1635Z.

ON 01/16/2014 INTERVIEWED THE PILOT/INSTRUCTOR, NO ISSUES NOTED WITH LOGS OR CERTIFICATES. HE STATED THAT UPON LANDING THE STUDENT FAILED TO MAKE PROPER CORRECTIONS AND WAS GETTING BEHIND THE AIRCRAFT WHEN ASKED THEN COMMANDED TO TURN CONTROLS OVER TO THE INSTRUCTOR. THE STUDENT IGNORED / FROZE ON THE CONTROLS CREATING A DELAY IN THE TRANSFER FINALLY TO THE INSTRUCTOR WHICH CAUSED THE AIRCRAFT TO DEPART THE RUNWAY AND HIT THE TAXI-WAY SIGN. NO INJURIES TO EITHER OCCUPANT.

ON 01/17/2014 AN INTERVIEW WITH THE STUDENT WAS CONDUCTED, NO ISSUES NOTED WITH LOGS OR CERTIFICATES AND HIS STATEMENT WAS AS FOLLOWS: MY INTENTION WAS TO GO AROUND , I START THE PROCEDURE WITH A FULL POWER BUT MY INSTRUCTOR WAS ASKING ME TO RELIEVE THE CONTROLS , I RELIEVED THE CONTROLS MAY BE IN THE SECOND OR THIRD TIME HE ASKED ME , IT WAS HARD TO RELIEVE THE CONTROLS IN THIS SITUATION , SO HE TOOK THE CONTROLS, PUT POWER TO IDLE, FULL AILERONS DEFLECTION TO THE LEFT AND TRY TO CONTROL THE SITUATION AND CORRECT THE LANDING BUT THE SITUATION WAS UNCONTROLLABLE SINCE THE WIND IS VERY STRONG  , THE AIRPLANE DRIFTS TO THE GRASS AND GET OUT OF THE RWY, THIS HAPPENS IN MAY BE 4 TO 5 SECONDS.

OPERATIONAL CONTRIBUTING FACTORS: STUDENT APPEARED TO DELAY OR FREEZE AND STATED HE WAS SCARED, DID NOT TURN OVER CONTROL OF THE AIRCRAFT TO THE INSTRUCTOR WHEN REQUESTED TO DO SO AT THE CRITICAL LANDING PHASE OF THE FLIGHT.

VERBAL COUNSELING WAS GIVEN TO THE INSTRUCTOR ON 01/16/2014 AND THE STUDENT ON 01/16/2014 ON THE IMPORTANCE OF TRANSFER OF COMMAND OF THE AIRCRAFT AND EACH OF  THEIR RESPECTIVE RESPONSIBILITIES, BOTH WERE ATTENTIVE, COOPERATIVE AND APPEARED TO FULLY UNDERSTAND THEIR RESPECTIVE REQUIREMENTS.

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.