DEN05LA109 · Piper PA46-500TP
Piper PA46-500TP · Accident: in flight encounter with weather during landing
From Steamboat Springs Bob Adams Field (SBS) to Fremont County Airport (1V6)
Event
- NTSB case
- DEN05LA109
- 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
Piper PA46-500TP
- Aircraft type
- Piper PA46
- 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
- N804JH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Steamboat Springs Bob Adams Field (SBS), Steamboat Sprng, COTo Fremont County Airport (1V6), Canon City, CO
- 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
- In flight encounter with weather
- 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 · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that the pilot of a Twin Commander in front of him performed a go-around due to "erratic winds at the approach end of runway 11" and he elected to do the same. During the second approach, he became distracted maintaining a safe distance from the Twin Commander in front of him. He stated that during the landing, the winds shifted from a right crosswind to a left crosswind and then to a left quartering tailwind. The pilot stated that during the touchdown and landing roll, the airplane drifted to the left and he overcorrected. The airplane exited the runway to the right and ground looped, coming to a rest off the runway. Both the left and right main landing gear collapsed causing substantial damage. The METAR 30 nautical miles east reported the winds as 110 degrees at 10 knots. The METAR 30 nautical miles northeast reported the winds as 140 degrees at 12 knots.
Probable cause
the pilot's failure to maintain directional control during the landing roll. Contributing factors include the crosswind and windshear conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN05LA109
- Event ID
- 20050715X01030
- Case number
- DEN05LA109
- 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: 3e68d066ddfae9fe36a5e350b0b761d3b902c0edd2a426075a69703350155438; retrieved 2026-09-22T05:42:09.000Z.