Flight Design GMBH CTSW accident near Gettysburg, Pennsylvania, September 13, 2009
On September 13, 2009 at about 1:15 pm local time, a Flight Design GMBH CTSW, registered N466CT, was substantially damaged in an accident during landing near Gettysburg, Pennsylvania (Gettysburg Regional airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The failure of the left main wheel attachment fitting due to overstress.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 13, 2009 · about 1:15 pm local time · cases in 2009
- Place
- Gettysburg, Pennsylvania · Gettysburg Regional · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Flight Design GMBH CTSW · all CTSWs on the register
- Registration
- N466CT · registry record · serial 07-02-12
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
During landing, the right main landing gear touched first, followed by the left main gear which was accompanied by an audible “thump.” The left main gear collapsed and the airplane veered off the edge of the runway. The left main landing gear attachment fitting was examined at the NTSB materials laboratory and no preexisting fractures were noted. The steel fitting was constructed from tubing and bar stock, and was powder-coated after fabrication. Examination revealed that the fitting failed due to overstress midway along the angled tube portion and that the fractures were consistent with bending loads experienced during landing and taxiing. The examination further revealed that the wall thickness was less than the manufacturer's specifications, and that the interior of the angled tube had been counter-bored prior to the powered coating and final assembly at the factory. Review of the NTSB database revealed that there were two additional accidents that occurred with identical damage incurred; in all instances, the parts failed from an overstress fracture that initiated in approximately the same location.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Landing gear collapse during landing defining event
- Runway excursion during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft systems › Landing gear system › Main landing gear › Design other cases naming the landing gear
- cause Aircraft › Aircraft systems › Landing gear system › Main landing gear › Capability exceeded other cases naming the landing gear
- cause Organizational issues › Development › Design › Equipment design › Manufacturer
Pilot
- Certificate: private, sport pilot
- Ratings: single-engine land
- Flight time: 190 hours in all; 70 in this make and model
- Last flight review: April 18, 2008
- Medical certificate: Sport Pilot
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 90 hours
- Last inspection: condition inspection, August 29, 2009; 8 hours since
- Maximum gross weight: 1,320 lb
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 912ULS (piston); 0 hours total
The flight
- Departed from: W05 Gettysburg PA
- Destination: W05 Gettysburg PA
- Flight plan: none
- Runway 24, 5,500 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 230° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 57°F (14°C)
- Altimeter: 30.01 inHg
- Observation at 1:16 pm from DMW, 18 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on October 7, 2010. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 (Memo) | PDF, 1 page | View Download |
| 2 | Record of Conversation with Pilot/faa Inspector | PDF, 2 pages | View Download |
| 3 | Materials Laboratory Factual Report 09-078 | PDF, 5 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N466CT the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N466CT on the register today · the tail number may have moved to another aircraft since
- Flight Design Gmbh CTSW 181 registered today · the model family and its accident history
- Engine: Rotax 912ULS 63 aircraft carry this series today · as the NTSB recorded it
- Gettysburg Regional · nearest airport
- Accidents and incidents in Pennsylvania 1,836 since 1982 · 233 in the last ten years
- Pennsylvania 6,195 aircraft registered
- Other NTSB records under N466CT 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/ERA09LA540.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
