WPR25LA187 · Flight Design Gmbh CTLS
Ample Aviation Flight Design Gmbh CTLS · Accident: runway excursion during takeoff
From Kayenta Airport (0V7) to an unrecorded destination
Event
- NTSB case
- WPR25LA187
- 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
- Event fatalities
- Unknown
- 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 CTLS
- Aircraft type
- Flight Design CTLS
- 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
- N454CT
- Operator
- Ample Aviation
- Onboard fatalities
- Unknown
- Route
- From Kayenta Airport (0V7), Kayenta, AZTo not recorded
- Aircraft age
- About 17 years (built 2008)
- 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
- Takeoff · rejected takeoff
- 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
- Runway excursion
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The right-seated pilot stated that both he and the left-seated pilot were flying for the purpose of building their total airplane hours. After departing, they maneuvered for about an hour and opted to land at a local airport and eat lunch. Despite waiting for a while for the wind to become calmer, they departed in gusting crosswind conditions. The right-seated pilot was flying the airplane and after reaching about 10 ft above ground level (agl), the wind suddenly changed directions, and they were unable to maintain airplane control. The left-seated pilot asked for control of the airplane then attempted to touch back down on the runway, but the airplane’s wheels contacted vegetation adjacent to the runway. The nose gear collapsed, and the airplane flipped over, coming to rest inverted. The airplane incurred substantial damage to the fuselage during the accident sequence. The pilots reported no pre-impact mechanical malfunctions or failures that would have precluded normal operation.
Probable cause
The pilots’ failure to maintain airplane control during takeoff in gusting crosswind conditions, which resulted in a runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR25LA187
- Event ID
- 20250623200375
- Case number
- WPR25LA187
- 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: 7248f49eeb887e3039b41761d811f9e8b8f0fa0a61fe570107e7db4e3cf83438; retrieved 2026-09-16T19:59:42.067Z.