FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24FA309 · Nanchang China CJ-6A

22 Sept 2024 · Lancaster, CA, United States

Cra Travel Nanchang China CJ-6A and Fight'S On! Yakovlev YAK 52 · Accident: abrupt maneuver en route

Report a problem

Event

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

Aircraft 1 · Nanchang China CJ-6A

Aircraft type
Nanchang China CJ-6
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
N313YK
Operator
Cra Travel
Onboard fatalities
Unknown
Route
From Watsonville Municipal Airport (WVI), Watsonville, CATo Payson Airport (PAN), Payson, AZ
Aircraft age
About 60 years (built 1964)
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
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
Abrupt maneuver
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Aircraft 2 · Yakovlev YAK 52

Aircraft type
Yakovlev YAK-52
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
N5287
Operator
Fight'S On!
Onboard fatalities
Unknown
Route
From Watsonville Municipal Airport (WVI), Watsonville, CATo Gillespie Field (SEE), San Diego, CA
Aircraft age
About 37 years (built 1987)
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
Not recorded
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
Not recorded
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 › Physical environment
  • Personnel issues › Psychological
  • 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 pilots departed in separate airplanes (a Nanchang CJ-6A and a Yak 52) as a formation flight from the same airport, with the Yak as the lead airplane and the CJ-6A as the dash 2 (wingman) off the Yak’s right wing. According to the Yak pilot, during the flight the pilots briefed their detachment procedure over the radio because they were bound for separate destinations. The briefed procedure was for them to accelerate from 210 kilometers per hour (kph) to 250 kph, at which time the CJ-6A would pitch up and bank left toward the east while the Yak would continue straight. However, during the detachment, and while the Yak pilot looked away briefly to scan his instruments, the CJ-6A entered a slightly inverted and nose-low position above the Yak and the airplanes collided. The Yak’s propeller blades separated and the pilot subsequently made a forced landing on a nearby road, while the CJ-6A rolled right several times and then impacted the ground. Postaccident examination of the CJ-6A and Yak did not reveal any preimpact mechanical anomalies or malfunctions that would have precluded normal operation. The CJ-6A accident site signatures indicated that the airplane impacted the ground in a wings-level and slightly nose-low attitude as most of the energy was absorbed by the lower engine bay. Paint transfer markings and damage signatures from both airplanes indicated that the airplanes collided when the CJ-6A was inverted and canted slightly right of the Yak’s longitudinal axis. The Yak’s propeller impacted the CJ-6A’s left wing and the Yak’s left wing impacted the CJ-6A’s vertical stabilizer, which resulted in a partial separation of the airfoil. There was insufficient evidence to determine either airplane’s final movements prior to the midair collision. The CJ-6A was not equipped with an ejection seat; however, the pilot had a parachute and may have decided to jump from the airplane since the wreckage indicates that the pilot’s canopy was fully open at impact. However, a witness reported that the airplane was in a roll prior to its collision with terrain, so the pilot may not have been able to initiate a jump. Toxicological testing detected the presence of ethanol in the CJ-6A pilot’s cavity blood and gastric contents. Ethanol was not detected in the pilot’s vitreous fluid, which is the preferred specimen type. The other two tested specimen types also contained npropanol. In the presence of extensive injury, this indicates that the detected ethanol likely was from postmortem sources rather than alcohol consumption. It is unlikely that the CJ-6A pilot was impaired by the effects of ethanol at the time of the accident. The pilots were both part of an association that teaches pilots the fundamentals of formation flight through various clinics. The detachment procedure they used was not in the association’s formation flight manual. In addition, while the Yak pilot reported that they briefed the procedure, there were no recordings to show how the detachment procedure was communicated and whether there were any interpretation errors. The pilot of the CJ-6A did not exhibit any abnormal behavior over the radio or on the ground prior to departure and the flight was not in an area of adverse weather conditions, so it is unknown why the CJ-6A pilot rolled into a nearly inverted position during the detachment. While the accident was initiated by the CJ-6A pilot’s improper roll during the detachment procedure, the Yak pilot failed to continue monitoring the CJ-6A during a critical time as he turned his attention away from the airplane during the detachment.

Probable cause

The CJ-6A pilot’s failure to maintain separation and the Yak pilot’s failure to monitor the other airplane during a detachment, which resulted in a midair collision.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24FA309
Event ID
20240922195157
Case number
WPR24FA309
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: aaa1b96729433271b07f27c9148fe8028bb4ea2241e2616352b568cbb84abe0c; retrieved 2026-09-13T18:12:14.821Z.