WPR22FA048 · Zenith Zodiac CH601XL
Zenith Zodiac CH601XL · Accident: system/component malfunction/failure (non-power) en route
From French Valley Airport (F70) to an unrecorded destination
Event
- NTSB case
- WPR22FA048
- 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
- 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
Zenith Zodiac CH601XL
- Aircraft type
- Zenith ZODIAC CH601XL
- 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
- N601KS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From French Valley Airport (F70), Temecula, CATo not recorded
- Aircraft age
- About 14 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
- En route · cruise
- 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
- System/component malfunction/failure (non-power)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft structures
- Aircraft › Aircraft systems
- 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
About seven minutes after departure, following what appeared to be an uneventful takeoff and initial climb, the airplane began a 180° turn toward the departure airport. A few minutes later, witnesses heard a loud bang, and the airplane pitched down aggressively, rolled inverted, and impacted the ground in a steep, nose-down attitude. During the descent, the pilot’s flight bag and other cabin contents fell out of the airplane, and the sound of buffeting wind noise and the pilot struggling were heard on the airport’s common traffic advisory frequency.
Examination did not reveal any anomalies with the flight controls or engine that would have precluded normal operation, and all components from the airplane were found in the immediate vicinity of the impact site. There was no evidence of bird strike.
The owner/builder of the airplane stated that he had once experienced the canopy opening on takeoff but was able to land safely. As a result of this event, he disabled the standard lock and installed a set of two small over-center latches, each mounted to the rear sides of the canopy frame with two soft aluminum rivets.
Examination of the canopy system revealed damage signatures that appeared to indicate that the rivets of one latch had separated in shear, and the other latch had twisted away from the airframe. It is likely that the accident was initiated by the failure of the mounting rivets in one latch, which caused the canopy to partially open on one side, then twist the latch away from the other side, resulting in an open and possibly deformed canopy. The reason for the initial failure could not be determined; however, the owner of the airplane was shorter than the pilot and had raised the seat and moved it forward during construction. The modification would have resulted in the accident pilot having to lean inboard, or sit with his head tilted, to avoid touching the canopy. It is possible that the airplane encountered turbulence that caused the pilot to hit the canopy, resulting in the failure of one of the latches.
Multiple instances of canopies opening in flight were reported for this airplane model. Because an open canopy disturbs airflow over the horizontal stabilizer, flight control difficulties can result in a loss of control nose-down pitching motion, often accompanied by a loud banging sound and cabin contents being sucked out, all which were observed in this accident. Although the Pilot Operating Handbook (POH) provides instructions for continued flight with an open canopy, evidence from both this and previous accidents suggests that both the nose-down motion and associated negative G-forces can be hard for pilots to maintain airplane control.
The airplane’s POH suggested the installation of a secondary backup latch system, and 2 weeks following the accident, the manufacturer issued a safety alert recommending such. The accident airplane was not equipped with a secondary latch.
Probable cause
The failure of the airplane’s canopy latch system, which resulted in the canopy opening in flight and a loss of airplane control. Contributing to the accident was the lack of a secondary canopy latch as recommended by the kit manufacturer.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22FA048
- Event ID
- 20211123104310
- Case number
- WPR22FA048
- 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: dd2efb3c647c312ba6df9f3bb55bdcc9ef53bfe458b12ea4faeba77a5ad4f607; retrieved 2026-09-15T07:37:51.193Z.