GAA19CA373 · Flight Design CTSW
White Falcon Flight Design CTSW · Accident: loss of control in flight during landing
From Raleigh Executive Jetport (TTA) to Hazel Green Airport (M38)
Event
- NTSB case
- GAA19CA373
- 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 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
- N153SW
- Operator
- White Falcon
- Onboard fatalities
- Unknown
- Route
- From Raleigh Executive Jetport (TTA), Sanford, NCTo Hazel Green Airport (M38), Hazel Green, AL
- Aircraft age
- About 12 years (built 2007)
- 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
- 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
- Loss of control in flight
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, while on approach for landing on runway 26, the wind was reported to be from 240º at 8 knots. One second later, the wind shifted and was from 180º at 6 knots. The pilot flew the final approach with a left crosswind and crossed the threshold at 50 knots. As he leveled the airplane and was about to touch down at 45 knots, the airplane lifted about 7 ft, and the nose pitched up 20º. The pilot pushed the control stick forward and began to add power, but the airplane "violently slammed" onto the runway, and the left main landing gear collapsed. He added full right rudder and aileron to keep the airplane on the runway, but it veered left into tall grass. The airplane sustained substantial damage to the firewall and engine mount.
Probable cause
The pilot's failure to maintain airplane control during landing in gusting crosswind conditions, which resulted in a hard landing and landing gear collapse.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA373
- Event ID
- 20190627X30321
- Case number
- GAA19CA373
- 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: 0a07bb8313f3e81e3ad29dde995afa94af9d7c102fbd41c25a10245ca6b5f279; retrieved 2026-09-16T09:19:35.261Z.