FTW93LA028 · Cessna 150F
Cessna 150F · Accident: loss of control on ground/water during landing
From F05 to an unrecorded destination
Event
- NTSB case
- FTW93LA028
- 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
Cessna 150F
- Aircraft type
- Cessna 150
- 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
- N8199S
- Operator
- Latimer, Lawrence · private individual
- Onboard fatalities
- Unknown
- Route
- From F05To 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
- 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 on ground/water
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush
- 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 › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE STUDENT PILOT WAS PERFORMING TOUCH AND GO LANDINGS AT THE UNCONTROLLED AIRPORT WHEN THE AIRPLANE STARTED TO PORPOISE AFTER TOUCHDOWN AND AIRCRAFT CONTROL WAS LOST. HE ATTEMPTED TO ABORT THE LANDING AND RECOVER FROM THE BOUNCING BY ADDING FULL POWER. THE AIRPLANE WAS SEEN BY EYEWITNESSES TO LEAVE THE RUNWAY SURFACE AND DRIFT LEFT IN A NOSE HIGH, RIGHT BANK ATTITUDE FOR APPROXIMATELY 200 YARDS AND THEN THE LEFT HORIZONTAL STABILIZER STRUCK A BUTANE TANK AND THE AIRPLANE CARTWHEELED TO IMPACT THE TERRAIN. THE FAA INSPECTOR DID NOT REPORT FINDING ANY MECHANICAL PROBLEMS WITH THE AIRPLANE.
Probable cause
THE STUDENT PILOT'S FAILURE TO MAINTAIN DIRECTIONAL CONTROL OF THE AIRPLANE. A FACTOR WAS THE STALL/MUSH.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW93LA028
- Event ID
- 20001211X16033
- Case number
- FTW93LA028
- 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: ee185ca7736a5f09db66617a62c517644bfeebdf945d5cca60b0fa6827c78402; retrieved 2026-09-21T23:05:27.872Z.