FTW02LA254 · Cessna 152
Spartan School of Aeronautics Cessna 152 · Accident: hard landing
From Tulsa Riverside Airport (RVS) to an unrecorded destination
Event
- NTSB case
- FTW02LA254
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 152
- Aircraft type
- Cessna 152
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N94112
- Operator
- Spartan School of Aeronautics
- Onboard fatalities
- Unknown
- Route
- From Tulsa Riverside Airport (RVS), Tulsa, OKTo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Hard landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that this was the first supervised solo flight for the 34-hour student pilot. The instructor stated that earlier in the day she had flown with the student, who had successfully completed seven full stop landings. The instructor reported that on the student's supervised solo flight, the student failed to reduce power and "looked a little high and a little fast as he approached runway 19L." The instructor also stated that as the airplane came down and the wheels touched the ground, the airplane bounced off the runway and its nose wheel touched the ground. The instructor reported this happened three times, and the third time "it seemed as if the airplane's nose wheel folded undernearth as the airplane skidded off the right side of the runway." The airplane came to rest in an upright position approximately 1,500 feet from the approach end of the runway.
Probable cause
the pilot's improper recovery from a bounced landing, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02LA254
- Event ID
- 20020917X01838
- Case number
- FTW02LA254
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2002-09-06.
- API snapshot SHA-256: 9e56fc66fc5c462f65c99f80fae18c4abf85463d002612c859a2d2bace7e2d5a; retrieved 2026-09-22T10:19:43.413Z.