DFW05CA218 · Cessna 152
Cessna 152 · Accident: hard landing
From Bridgeport Municipal Airport (XBP) to Bridgeport Municipal Airport (XBP)
Event
- NTSB case
- DFW05CA218
- 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
- Unknown
- 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
- N6459M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bridgeport Municipal Airport (XBP), Bridgeport, TXTo Bridgeport Municipal Airport (XBP), Bridgeport, 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
- Dual student › Compensation for wind conditions, inadequate
- Pilot in command(cfi) › Directional control, not maintained
- Pilot in command(cfi) › Remedial action, delayed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 360-hour flight instructor was teaching a student pilot how to land with a crosswind on Runway 17. The student pilot, who was flying the airplane, landed hard to the left of the runway centerline and the airplane bounced back into the air. While airborne, the crosswind pushed the airplane further to the left. The flight instructor attempted to take control of the airplane, but to no avail. The airplane entered the grassy area to the left of the runway, and it subsequently flipped over on to its back. The winds at the time of the mishap were reported from 200 degrees at 9 knots, gusting to 14 knots.
Probable cause
The pilot's inadequate compensation for wind conditions, and the flight instructor's delayed remedial action during a crosswind landing resulting in a loss of directional control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05CA218
- Event ID
- 20050831X01336
- Case number
- DFW05CA218
- 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, coordinates. 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: d114ca511fbe4d98febb11fc6eec25d2e7007064f8ba463d3ffa72626e4267a3; retrieved 2026-09-22T05:28:36.948Z.