FTW96LA032 · Cessna 175
Cessna 175 · Accident: overrun during landing
From Landers Loop Airport (AR89) to an unrecorded destination
Event
- NTSB case
- FTW96LA032
- 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 175
- Aircraft type
- Cessna 175
- 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
- N7421M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Landers Loop Airport (AR89), Dover, ARTo 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 · landing roll
- 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
- Overrun
- 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 › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER LOCATING THE 2,000-FOOT GRASS AIRSTRIP, THE PILOT CIRCLED AT 1,000 FEET ABOVE THE GROUND AND ENTERED A LEFT HAND PATTERN FOR RUNWAY 27. THE PILOT ESTIMATED THAT THE SURFACE WINDS WERE FROM 200 TO 220 DEGREES AT APPROXIMATELY 20 KNOTS. THE PILOT ENCOUNTERED MODERATE TURBULENCE WHILE IN THE TRAFFIC PATTERN AND REPORTED ENCOUNTERING SEVERE TURBULENCE AND A DOWNDRAFT PRIOR TO TOUCHING DOWN. THE PILOT STATED THAT HE MANAGED TO CONTROL THE AIRPLANE AND TOUCHED DOWN AT ABOUT THE MIDPOINT OF THE STRIP. AFTER TOUCHDOWN THE PILOT ATTEMPTED TO STOP THE AIRPLANE; HOWEVER, THE AIRPLANE OVERRAN THE END OF THE RUNWAY AND IMPACTED BRUSH. THE PILOT STATED THAT 'THE WIND MUST HAVE CHANGED TO A TAILWIND,' AND 'JUST FELT LIKE A DOWNWIND LANDING BUT IT STILL LOOKED LIKE I HAD ROOM TO GET IT STOPPED.' THE WINDS AT HARRISON, ARKANSAS, 29 MILES NORTH, WERE REPORTED FROM 170 DEGREES AT 18 KNOTS, GUSTING TO 26 KNOTS.
Probable cause
THE PILOT'S SELECTION OF A DOWNWIND RUNWAY FOR LANDING. FACTORS WERE THE TAILWIND AND THE PILOT'S MISINTERPRETATION OF THE WIND CONDITIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96LA032
- Event ID
- 20001207X04708
- Case number
- FTW96LA032
- 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: 70cd30efd42fa7f08aa45c15c80e8542dd9249c75eef37dcaa4e3bcc5351777d; retrieved 2026-09-22T23:07:15.137Z.