DEN01LA026 · Sukhoi SU-29
Sukhoi SU-29 · Accident: airframe, component or system failure during landing
From 2V2 to an unrecorded destination
Event
- NTSB case
- DEN01LA026
- 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
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
- N55SU
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 2V2To 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
- 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
- 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
- Other maintenance personnel › Maintenance, major repair, inadequate
- Other maintenance personnel › Material defect(inadequate quality of material)
Approximate · Estimated position: the centre of Longmont, CO, the place the record names. Not the accident site.
NTSB narrative
During landing, the airplane exited the right side of the runway and the left wing impacted the ground. The pilot taxied to his hangar. Postaccident examination was delayed several months (until December 11, 2000) to allow Sukhoi representatives to assess the damage. They determined that several structural tubes just aft of the engine firewall needed to be replaced. The damaged area of the fuselage was where the main landing gear attached to the fuselage. It could not be determined if the structural damage that occurred on August 14, 2000, was the result of one landing or progressive damage from several landings. The tubes that needed replacement following the August 14, 2000, event had been previously damaged (bent or broken) during an accident on May 11, 1996. At that time, several unsuccessful attempts were made to acquire Russian materials and technical assistance. The decision was made to perform the repairs using American materials. According to the Sukhoi representatives, the American tubing and welding rods were 'incompatible' with the original Russian materials.
Probable cause
The inadequate structural materials (American manufactured verses original Russian materials) used during a major repair.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN01LA026
- Event ID
- 20010110X00093
- Case number
- DEN01LA026
- 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: e4a5f72f132b5b3c0934d4a99abfe5dce8d5bfecc0baccc137c743c5aee6c0b2; retrieved 2026-09-22T12:35:33.840Z.