FTW98LA184 · Cessna 182N
Cessna 182N · Accident: overrun during landing
From Moore County Airport (DUX) to 4AC
Event
- NTSB case
- FTW98LA184
- 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 182N
- Aircraft type
- Cessna 182
- 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
- N9008G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Moore County Airport (DUX), Dumas, TXTo 4AC
- 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 › Crosswind component, exceeded
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot landed on runway 35 (4,010 ft. x 60 ft., asphalt) at Albuquerque's Coronado Airport. There was a crosswind from the west. The airplane touched down midfield on its right main wheel and to the right of the runway centerline, leaving a 225 foot skid mark. The left main wheel then touched down and left a 350 foot skid mark. The left tire blew out and deflated. The airplane went off the end of the runway, down a slight hill, and came to rest on a service road. Recorded winds at Albuquerque International Airport, located 10 miles south of Coronado, were 260 degrees at 8 knots, with gusts to 24 knots. Under these conditions, a 090 crosswind existed. The computed crosswind component varied between 8 knots (9.2 mph) and 24 knots (27.6 mph).
Probable cause
The pilot's failure to attain the proper touchdown point during landing, resulting in an overrun, and his exceeding the airplane's maximum crosswind component. A factor was the gusty crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA184
- Event ID
- 20001211X09863
- Case number
- FTW98LA184
- 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: 1c175af97533aa85a260e71de54bdec68765d2bcdd4419c6f00ec5a8918d0ddd; retrieved 2026-09-22T17:53:19.253Z.