DEN03LA043 · SOCATA TBM 700
SOCATA TBM 700 · Accident: in flight encounter with weather during landing
From Centennial Airport (APA) to Aspen-Pitkin County Airport (Sardy Field) (ASE)
Event
- NTSB case
- DEN03LA043
- 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
SOCATA TBM 700
- Aircraft type
- Socata TBM-700
- 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
- N700GJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Centennial Airport (APA), Englewood, COTo Aspen-Pitkin County Airport (Sardy Field) (ASE), Aspen, 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
- 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
- Dual student › Aircraft control, not maintained
- Pilot in command(cfi) › Supervision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The approach was stabilized at 100 knots with landing gear and flaps in the landing position. The approach was normal until approximately 100 feet above the runway at which time the airplane encountered a turbulence condition causing rapid-roll tendencies right and left. As the student began his landing flare at about 15 feet above the runway, the left wing dropped rapidly combined with a sudden high sink rate. At that point the flight instructor took control of the airplane, applying corrective rudder, aileron, pitch and power corrections. Despite the flight instructor's actions, the left wing struck the runway. Winds at the time were reported 310 degrees at 6 knots. The temperature was 2 degrees Celsius. Records suggest that the winds were variable throughout the day.
Probable cause
the dual student's failure to maintain aircraft control and the inadequate supervision by the flight instructor. Contributing factors include the tailwind and the turbulence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN03LA043
- Event ID
- 20030221X00244
- Case number
- DEN03LA043
- 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: c66f1f780ad6b3c751a77f2f0b8a9908aee880c448f6b628b4bd062c42ee7f88; retrieved 2026-09-22T09:35:52.678Z.