FTW00LA089 · Cessna 152
Cessna 152 · Accident: loss of control in flight during landing
From T67 to an unrecorded destination
Event
- NTSB case
- FTW00LA089
- 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 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
- N48821
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From T67To 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 in flight
- 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
- Tree(s)
- 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 › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the landing on runway 32, the airplane touched down on the right main landing gear, bounced to the left main landing gear, and turned 45 degrees to the left. The solo student pilot added full power to abort the landing, and the aircraft started to climb; however, the left wing struck a tree. Subsequently, the airplane spun around, the left wing hit a railroad track, and the nose landing gear dug into the terrain. The airplane slid down the railroad track before exiting the track and coming to rest 60 feet west of the runway centerline. The student pilot was endorsed for solo flight, and he had accumulated a total flight time of 29 hours in the make and model aircraft. Wind was from 300 degrees at 6 knots.
Probable cause
The pilot's failure to maintain aircraft control during landing. A factor was the crosswind condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00LA089
- Event ID
- 20001212X20494
- Case number
- FTW00LA089
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2000-03-01.
- API snapshot SHA-256: 895a8a19b6fc89352061148e4b5b4f5278b3d6382885b768c3d690f42a8c7aa4; retrieved 2026-09-22T13:06:30.267Z.