WPR17LA201 · Cobalt Aircraft Industries Inc Co50 VALKYRIE
Cobalt Aircraft Industries Inc Co50 VALKYRIE · Accident: flight control system malfunction/failure during initial climb
From Castle Airport (MER) to Castle Airport (MER)
Event
- NTSB case
- WPR17LA201
- 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
Cobalt Aircraft Industries Inc Co50 VALKYRIE
- Aircraft type
- Cobalt CO50
- 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
- N523CA
- Operator
- Cobalt Aircraft Industries
- Onboard fatalities
- Unknown
- Route
- From Castle Airport (MER), Atwater, CATo Castle Airport (MER), Atwater, CA
- Aircraft age
- About 1 year (built 2016)
- 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
- Flight control system malfunction/failure
- 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 pilot reported that the purpose of the flight was to evaluate handling qualities of the experimental airplane at various configurations specified in the test card. After rotation, with the airplane about 50 ft above ground level (agl), the pilot experienced a loss of aileron control. As the airspeed increased, he began to attain some controllability and climbed to about 1,400 ft agl. After about 20 minutes of manipulating the flight controls and practicing climbing and descending using the trim, he stabilized the airplane around 90 kts. He thought that he would be able to land the airplane at an increased airspeed using steady thrust control and the rudder for directional control. During landing, with the airplane about 10 ft above the runway surface, the airplane experienced a loss of lift and landed hard, which resulted in damage to the right wing spar. For the test flight, the airplane manufacturer had changed the winglet position, which contributed to a loss of aileron effectiveness.
Probable cause
A loss of aileron effectiveness due to the airplane's design configuration, which resulted in the pilot's inability to control the roll axis and led to a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR17LA201
- Event ID
- 20170906X25126
- Case number
- WPR17LA201
- 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: f82dea0543a5639292c899f4a93a565f071080186624d827b5f931164a9b849b; retrieved 2026-09-16T05:47:52.509Z.