DEN05FA002 · Sukhoi SU-29
Sukhoi SU-29 · Accident: loss of control in flight while maneuvering
From Santa Fe Municipal Airport (SAF) to an unrecorded destination
Event
- NTSB case
- DEN05FA002
- 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
- 1 · 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
Sukhoi SU-29
- Aircraft type
- Sukhoi SU-29
- 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
- N92CG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Santa Fe Municipal Airport (SAF), Santa Fe, NMTo not recorded
- 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
- Maneuvering
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/spin
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aircraft 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 Russian-built aerobatic airplane had taken off just prior to the start of the air show. The airplane held outside the show area for a T-33 jet, which was the show's first performance. The pilot then went into his routine. The airplane was approximately 1,500 feet above ground level (agl) when the pilot entered his second maneuver, a torque roll. On reaching its maximum height, the airplane was observed to tail slide and enter an inverted spin. A witness said, "The pilot attempted to recover but didn't make it. The airplane struck the ground upright, in a slight right bank and nose down attitude. On contact with the ground, the airplane exploded and was engulfed in a fireball." Another witness, also one of the air show's performers, described the torque roll. He said that in this maneuver, the airplane pulls up into a vertical climb at full throttle. As the airplane runs out of airspeed, torque from the engine and propeller turns the airplane. The airplane then falls off one direction or the other, nose down, and the pilot flies the airplane out of the dive. The witness said he saw the airplane come out the bottom of the smoke and enter an inverted flat spin. The witness said he saw the airplane make three revolutions. The witness said he thought the pilot had gone too far. "He came off the throttle, the rotation stopped, then the airplane yawed. I heard the engine come in. The airplane came around in a positive attitude. He was getting low. He was upright in a spin. He went to full power. He made a turn and a half and then hit [the ground]." An examination of the airplane revealed no anomalies. A former importer and dealer of SU-29's, who was also a pilot and mechanic who had flown and maintained SU-29's, stated that at the altitude the accident airplane was operating, the pilot cannot reduce power at all during the torque roll maneuver. He said," that if you do reduce power, the airplane will fall off wrong and you will not have enough altitude to recover." Examination of recorded video/images taken of the flight sequence through the ground impact showed the airplane come out of the torque roll into an inverted spin with full left rudder and slight upward elevator controls. The airplane descends in an inverted spin attitude for 3 revolutions before the airplane makes a clockwise roll around its longitudinal axis, placing it in an upright, nose down attitude. About 3.4 seconds prior to the airplane coming out of the inverted attitude, the rudder moves toward neutral. The airplane enters a left downward spiral. At this point, the airplane is less than 600 feet agl. The airplane makes 1.5 left-turning spirals. On completion of the first spiral, the rudder is deflected left and the elevator is deflected upward. At the end of 1.5 spirals, the airplane is approximately 150 feet agl. At this point, the airplane stops its spiral motion and falls straight down to the ground in a 47-degree nose down pitch attitude. On impact, the airplane's rudder shows full right deflection. The elevator is full up (full aft stick deflection).
Probable cause
the pilot's failure to maintain aircraft control resulting in the inverted spin, spiral, and subsequent impact with terrain. Factors contributing to the accident were the inadvertent stall spin, the spiral, low altitude, and the pilot's delayed attempt to recover from the spin and spiral.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN05FA002
- Event ID
- 20041008X01599
- Case number
- DEN05FA002
- 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: eb77570b9a5edcca11bcca05f43b904d8743482ac4908d286c127ddc9f308c67; retrieved 2026-09-20T18:19:25.766Z.