FTW96TA289 · Cessna 182RG
Cessna 182RG · Accident: loss of control in flight on approach
From Steamboat Springs Bob Adams Field (SBS) to Rocky Mountain Metropolitan Airport (BJC)
Event
- NTSB case
- FTW96TA289
- 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 182RG
- 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
- N4314R
- Operator
- Wings of Denver
- Onboard fatalities
- Unknown
- Route
- From Steamboat Springs Bob Adams Field (SBS), STEAMBOAT SPGS, COTo Rocky Mountain Metropolitan Airport (BJC)
- 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
- Approach · VFR go-around
- 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
- Loss of control in flight
- 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
- Pilot in command › Proper alignment, not maintained
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
At the completion of a cross-country flight, the pilot intended to perform touch-and-go landings before the final landing. During flare for the first touch-and-go, the aircraft drifted left and the pilot added power to go-around. The pilot said the engine did not respond and ran 'rough.' The aircraft traveled a distance of approximately 6,000 feet parallel to the runway at a 'few' feet elevation and the landing gear hit a slight rise in the terrain. The aircraft then nosed over and came to rest inverted. Test runs of the engine could not duplicate the lack of power response reported by the pilot. Reported wind at the time was from 330 degrees magnetic at 9 knots and the runway of intended landing was runway 29. The pilot reported that following the accident, the windsock indicated the wind was from the east at 8 to 10 knots.
Probable cause
failure of the pilot to maintain directional control and runway alignment during a go-around, and the lack of power response from the engine for undetermined reason(s). The sudden wind shift was a related factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96TA289
- Event ID
- 20001208X06248
- Case number
- FTW96TA289
- 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: 3e8acb33bf3f8c7be07bee9e603392cca113f7e71f42b594ed1e8194c3aa2ab6; retrieved 2026-09-21T21:42:23.521Z.