FTW82DA248 · Cessna 172P ROBERTSON STOL 172P ROBER
Texas Westaire Cessna 172P ROBERTSON STOL 172P ROBER · Accident: hard landing
From F71 · Fort Worth, TX to F71 · Fort Worth, TX
Event
- NTSB case
- FTW82DA248
- 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 172P ROBERTSON STOL 172P ROBER
- Aircraft type
- Cessna 172
- 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
- N55276
- Operator
- Texas Westaire
- Onboard fatalities
- Unknown
- Route
- From F71 · Fort Worth, TXTo F71 · Fort Worth, TX
- 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 › Directional control, not maintained
- Pilot in command › Flare, improper
- Pilot in command › Inadequate transition/upgrade training
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCRAFT WAS EQUIPPED WITH A ROBERTSON STOL KIT. AFTER OPERATING THE AIRCRAFT IN SLOW FLIGHT ABOUT 1/2 HR, THE PILOT ELECTED TO LAND. THE APPROACH WAS FLOWN AT 45 KTS WITH A 500 FT/MIN SINK RATE. POWER WAS ADDED TO ARREST THE SINK RATE JUST BEFORE TOUCHDOWN, BUT REPORTEDLY, TOO MUCH WAS APPLIED AND THE AIRCRAFT BOUNCED AND BALLOONED IN THE AIR. REPORTEDLY, THE PILOT OVERREACTED AND REDUCED TOO MUCH POWER, THEN THE AIRCRAFT BOUNCED AGAIN. AFTER THE SECOND BOUNCE, FULL POWER WAS APPLIED, BUT THE PLANE DRIFTED TO THE LEFT OF THE RUNWAY AND TOUCHED DOWN IN A SOFT AREA. THE NOSE GEAR SHEARED OFF IN THE SOFT TERRAIN AND THE PLANE FLIPPED OVER. THE PILOT STATED THAT HE WAS UNFAMILIAR WITH THE AIRCRAFT'S RESPONSE TO POWER. HE ASSUMED THAT FROM HIS EXPERIENCE IN OTHER MODELS, HE COULD FLY THE STOL MODEL OF THE CESSNA 172.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW82DA248
- Event ID
- 20020917X03325
- Case number
- FTW82DA248
- 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: e74b808bc008217f260c24b57d1f9cf2e9f7c58a17a0b05785940917f8c553b3; retrieved 2026-09-24T02:48:32.854Z.