FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW82DA140 · Cessna 172M

17 Apr 1982 · Breckenridge, TX, United States

Tarrant Aero Assc Cessna 172M · Accident: hard landing

From F72 · FT WORTH, TX to Lamesa, TX

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
FTW82DA140
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 172M

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
N61923
Onboard fatalities
Unknown
Route
From F72 · FT WORTH, TXTo Lamesa, 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

  • Flight instructor(on ground) › Inadequate transition/upgrade training
  • Pilot in command › Compensation for wind conditions, improper
  • Pilot in command › Recovery from bounced landing, improper

Approximate · Estimated position: the centre of Breckenridge, TX, the place the record names. Not the accident site.

NTSB narrative

THE ACCIDENT OCCURRED AT AN EN ROUTE AIRPORT WHILE THE STUDENT PILOT WAS ON A CROSS-COUNTRY FLIGHT. UPON ARRIVAL AT THE EN ROUTE AIRPORT, HE ENTERED TRAFFIC FOR A LANDING ON RUNWAY 03 IN WINDS FROM 010 DEGREES AT 10 KTS GUSTING TO 27 KTS. THE STUDENT REPORTED THAT ON FINAL APPROACH, HE LOWERED 20 DEGREES OF FLAPS AND CONTINUED WITH A CRAB TO THE LEFT. REPORTEDLY DURING TOUCHDOWN, HE ENCOUNTERED A STRONG GUST OF WIND AND SUDDENLY FOUND THE PLANE ABOUT 6 TO 8 FT ABOVE THE RUNWAY. HE HELD SLIGHT UP ELEVATOR HOPING THE PLANE WOULD SETTLE TO THE RUNWAY, BUT THE NOSE FELL AND THE PLANE BOUNCED 2 TIMES. AFTER THE PLANE WAS SLOWED DURING THE LANDING ROLL, THE PILOT NOTICED A FLAT NOSE TIRE. HE CLEARED THE RUNWAY AND SHUT DOWN. AN INVESTIGATION REVEALED THAT THE PROPELLER AND FIREWALL WERE BENT. REPORTEDLY, THE STUDENT HAD RECEIVED NO INSTRUCTION IN CROSSWIND LANDINGS OR RECOVERY FROM BOUNCED LANDINGS.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record FTW82DA140
Event ID
20020917X02080
Case number
FTW82DA140
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: 430e4e79ffa712059a8f545ce7253c19e182cb71d055b78c51424290e7f1b9b0; retrieved 2026-09-24T03:24:44.894Z.