FTW01LA037 · Piper PA-28-180
Piper PA-28-180 · Accident: loss of control in flight during landing
From Tulsa Riverside Airport (RVS) to an unrecorded destination
Event
- NTSB case
- FTW01LA037
- 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
- 0
- 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
Piper PA-28-180
- Aircraft type
- Piper PA-28
- 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
- N7859W
- Operator
- Unknown
- 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
- Loss of control in flight
- 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(cfi) › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot was receiving an airplane checkout from a certified flight instructor (CFI). The private pilot taxied the airplane to runway 31, departed, and during the initial takeoff climb the CFI noted to the private pilot that there was a crosswind from the east. They decided to remain in the pattern and execute a landing to a full stop. The CFI reported that due to the 'choppy conditions' the private pilot 'kept the airspeed a little higher than normal' during the final approach. During the landing flare/touchdown, the airplane touched down, bounced, and drifted left of the runway centerline. The private pilot initiated a go-around; however, the CFI assumed control of the airplane, reduced the throttle to idle, and attempted to land the airplane. As the airplane was descending back to the runway, a 'wind gust caught the airplane from the right,' and subsequently, the airplane departed the runway. The airplane contacted a snow bank off the left side of the runway, crossed a taxiway, and came to a stop upright.
Probable cause
the certified flight instructor's (CFI) failure to maintain directional control of the airplane during landing. A contributing factor was the gusty wind condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW01LA037
- Event ID
- 20010110X00076
- Case number
- FTW01LA037
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 960d380b8cf563982314d2c658b10a0b9230368d5324525c9d65b365950d8d28; retrieved 2026-09-22T12:16:52.334Z.