FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW96LA138 · Cessna 182A

2 Mar 1996 · Walsenburg, CO, United States

Cessna 182A · Accident: airframe, component or system failure during landing

From Chloride Airport (NM51) to 4V1

Report a problem

Event

NTSB case
FTW96LA138
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 182A

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
N6344B
Operator
Thad J. Englert · private individual
Onboard fatalities
Unknown
Route
From Chloride Airport (NM51), Edgewood, NMTo 4V1
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
Airframe, component or system failure
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

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

NTSB narrative

At the completion of a cross-country flight, the pilot made a normal landing. After touchdown, the aircraft swerved to the left and departed the side of the runway. As the aircraft departed the runway, the pilot elected to go around. After rolling across a grass area, the aircraft struck a fence and nosed over. Examination of the aircraft provided evidence that the left main tire was flat, and the valve stem was missing. Tire marks were found on the runway that were consistent with the track of the aircraft.

Probable cause

Failure of the pilot to maintain directional control of the airplane after the left main tire went flat during the landing roll. The flat tire was a related factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW96LA138
Event ID
20001208X05395
Case number
FTW96LA138
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: 7d272c354579f0d3be38d21354a00bc4514326181ffa76fee862648257ebcedb; retrieved 2026-09-22T22:46:42.234Z.