FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA238 · Flight Design Gmbh CTSW

5 Jul 2025 · Joliet, IL, United States

Flight Design Gmbh CTSW · Accident: loss of control in flight during landing

From Watervliet Municipal Airport (40C) to an unrecorded destination

Report a problem

Event

NTSB case
CEN25LA238
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

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
N646MA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Watervliet Municipal Airport (40C), Watervliet, MITo not recorded
Aircraft age
About 20 years (built 2005)
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
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that he conducted a straight in approach to runway 31. The pilot stated that he chose runway 31 because the intersecting grass runway (4/22) was closed due to blimp operations that were being conducted on the airfield. Shortly after touchdown, a sudden gust of wind relaunched the airplane into the air. The pilot stated that the wind gust was so strong that he could not keep the airplane aligned with the runway. The airplane settled onto the runway and exited the paved runway surface to the left. The nose landing gear dug into the soft ground and the airplane nosed over. The airplane sustained substantial damage to the right wing. The reported wind was from 210° at 13 kts, gusting to 18 kts. The pilot reported that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operations.

Probable cause

The pilot’s failure to maintain directional control during the crosswind landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN25LA238
Event ID
20250707200476
Case number
CEN25LA238
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, coordinates, cause areas. 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: 72c378b722f909829de454e822aa12c34952a228622f54b90d4744d8c752d421; retrieved 2026-09-16T20:03:08.367Z.