DEN08LA008 · Flight Design Gmbh CTSW
Flight Design Gmbh CTSW · Accident: hard landing
From Afton Municipal Airport (AFO) to Afton Municipal Airport (AFO)
Event
- NTSB case
- DEN08LA008
- 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
Flight Design Gmbh CTSW
- Aircraft type
- Flight Design CTSW
- 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
- N245CT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Afton Municipal Airport (AFO), Afton, WYTo Afton Municipal Airport (AFO), Afton, WY
- 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
- Hard landing
- 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
- Design stress limits of aircraft › Exceeded
- Landing gear, main gear › Failure, total
- Pilot in command › Proper alignment, not corrected
- Pilot in command › Recovery from bounced landing, not obtained
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 said he flew over the airport and noted the wind sock, segmented circle, and wind-T were indicating a calm wind from the north. He made his approach to runway 34 using 30 degrees of flaps and maintained 45 knots using elevator control, but did not trim for this speed. He sensed he was slightly low so he increased power until he saw both VASI (visual approach slope indicator) bars turn white. He then reduced power to idle. The airplane bounced but "not hard enough to have a wheel fall off." The pilot said he was going straight down the runway into "a few knots of wind." When the airplane touched down again, "the stub of the right main gear dug into the runway" and caused the airplane to veer to the right and off the runway. The right wing struck the ground and the airplane nosed over. The flight instructor's version of events was somewhat different. He said the pilot's performance in the traffic pattern was "somewhat ragged and less precise and exhibited tension." He overshot his downwind-to-base turn by 20 degrees. The instructor took control of the airplane to reestablish a stable approach, and then returned control to the pilot. Threshold crossing airspeed was 55 knots. The pilot allowed the right wing to settle giving a right turn. The instructor tried to recover but it was too late. The airplane "landed hard with the right wing low resulting [in] major ballooning. When the bottom fell out, the plane landed extremely hard on the right main gear [and] proceeded off the runway" at a 20 to 30 degree angle and nosed over in the grass. The airport manager, who witnessed the accident, said the airplane was not aligned with the runway centerline when it landed hard. The impact tore off the right main landing gear. The airplane veered off the runway and nosed over. The right wheel was found on the left side of the runway, and the airplane came to a halt about 300 feet off the right side of the runway. Laboratory examination revealed "the fracture was overstress, consistent with bending from a hard landing impact. There was a compression buckle at the top and a tensile fracture at the bottom. There was also considerable plastic deformation, but no indication of pre-existing cracks or defects." Steel type, wall thickness, yield strength, tensile strength, and hardness measurements met or exceeded. "The fracture . . . [was the] result of impact on landing." According to the airplane manufacturer, the gear assembly was designed in accordance with ASTM 2245, and successfully passed a drop test of 550 mm (21.7 inches) at a weight of 600 kg (1,323 pounds).
Probable cause
The pilot's failure to correct the alignment of the airplane and his improper recovery from a bounced landing, resulting in exceeding the design stress limits that caused the right main landing gear to fail. A contributing factor in this accident was the instructor's inadequate supervision of the pilot.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN08LA008
- Event ID
- 20071029X01678
- Case number
- DEN08LA008
- 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: e734ee9c3ff0403992503e3a27520aa896ba5a8f47965a00c4ce17c0a756f0db; retrieved 2026-09-21T18:22:30.429Z.