ERA14LA329 · Flight Design Gmbh CT-SW 2006
Flight Design Gmbh CT-SW 2006 · Accident: aerodynamic stall/spin during initial climb
From Royalton Airport (9G5) to Royalton Airport (9G5)
Event
- NTSB case
- ERA14LA329
- 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
Flight Design Gmbh CT-SW 2006
- Aircraft type
- Flight Design CT-SW 2006
- 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
- N508CT
- Operator
- Schnabel John A
- Onboard fatalities
- Unknown
- Route
- From Royalton Airport (9G5), Gasport, NYTo Royalton Airport (9G5), Gasport, NY
- Aircraft age
- About 8 years (built 2006)
- 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
- Initial climb
- Defining eventThe 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
- Aerodynamic 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
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot was taking off in the light sport airplane for a local flight. Witnesses reported seeing the pilot begin the takeoff. During the rotation, the airplane appeared to pitch up higher than normal, followed by up-and-down pitch oscillations and left bank oscillations; it climbed no higher than about 75 ft. The airplane began a slow left bank, which was not consistent with a normal takeoff procedure, before impacting trees south of the runway in a left-wing-low attitude. The pilot indicated to his son before he died that the airplane experienced flight control issues related to the autopilot.
Postaccident examination of the airplane revealed that the flaps were symmetrically extended 15 degrees, and there was no evidence of preimpact failure or malfunction of the flight controls for roll, pitch, or yaw. According to an airplane performance study, the pilot was operating the airplane about 4 knots above its stall speed during the left turn; however, the location of the main wreckage with respect to the airplane's last GPS data point indicated that the bank angle likely increased and exceeded the airplane's critical angle-of-attack, which resulted in an aerodynamic stall.
Data from the engine's recording device indicated that, during the beginning portion of the takeoff sequence while the airplane was over the runway, the engine rpm decreased about 50 rpm and then increased nearly 900 rpm about the point and time when the airplane banked left and hit the trees. Postaccident operational testing of the engine revealed that it produced full-rated power with no evidence of preimpact failure or malfunction. The reason for the reduced power setting at takeoff could not be determined.
Although the pilot reported that the pitch-and-roll oscillations during takeoff were related to the autopilot, it could not be determined during examination of the autopilot whether the autopilot was engaged during the accident flight. Postaccident testing of the autopilot controller and roll servo revealed no evidence of preimpact failure or malfunction; the override torque value of the roll servo was within limits.
The autopilot controller minimum airspeed was found set to a value of 0, which would have disabled the minimum airspeed alert if the autopilot were engaged. The pitch servo was found inoperative due to a failed voltage regulator; however, this condition would not have caused any increased torque or servo runaway. Following replacement of the failed component, the pitch servo tested satisfactorily, and the override value was within limits. Therefore, if the autopilot had been engaged and an autopilot malfunction had occurred, the pilot would have been able to override any pitch and yaw servo commands. Further, if the autopilot had been engaged and the controller minimum airspeed had been set to an appropriate value, it is likely that a stall alert would have occurred that provided the pilot with adequate time to respond to and avert an aerodynamic stall.
Probable cause
The pilot's failure to maintain adequate airspeed following a left turn during takeoff, which led to the airplane exceeding its critical angle-of-attack and experiencing an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14LA329
- Event ID
- 20140707X41002
- Case number
- ERA14LA329
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: aa9b3a18c176e3301b64228b830096330b1b5df8896205102a4ae114345254c0; retrieved 2026-09-14T17:21:15.580Z.