WPR23LA129 · Navion NAVION A
Navion NAVION A and TTD Yakovlev YAK-52 · Accident: midair collision en route
Event
- NTSB case
- WPR23LA129
- 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
Aircraft 1 · Navion NAVION A
- Aircraft type
- Navion A
- 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
- N610
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Falcon Field (KFFZ), Mesa, AZTo not recorded
- Aircraft age
- About 73 years (built 1950)
- 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
- Midair collision
- 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
- N2504U
- Operator
- TTD
- Onboard fatalities
- Unknown
- Route
- From Falcon Field (KFFZ), Mesa, AZTo not recorded
- Aircraft age
- About 36 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
- 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
- Midair collision
- 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
- Personnel issues › Action/decision
- 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 pilot of a Yakovlev Yak-52 reported that he was in the number three position, off the lead airplane’s left wing while in a four-airplane formation flight. The pilot of the lead airplane initiated a left turn and the formation followed. While in the left turn, the pilot of the number three airplane felt “a bump” from underneath and observed the number four airplane pass under his right wing, and ascend toward the lead airplane. The pilot of the number three airplane realized there had been a mid-air collision, broke away from the formation to the left, and executed an emergency landing. The number three airplane’s right wing sustained substantial damage. The pilot of a Ryan Navion reported that, he was in the number four position off of the number three airplane’s left wing in the four-airplane formation flight. The pilot of the lead airplane initiated a left turn and the formation followed. When the pilot of the number four airplane “felt to level off”, his airplane collided with the number three airplane from underneath. He then executed an emergency landing. The fuselage, vertical stabilizer, and rudder were substantially damaged. The pilots of both airplanes reported that there were no preaccident mechanical malfunctions or failures with the airplanes that would have precluded normal operation.
Probable cause
The pilot of the Ryan Navion’s failure to maintain visual sight of and clearance from another airplane during a formation flight, which resulted in a mid-air collision.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR23LA129
- Event ID
- 20230320106913
- Case number
- WPR23LA129
- 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: 3dc3ad8653f0b71eaa086ac15cb4c1cca83b3dfea9418ecdc4e29e8fc7fe70dd; retrieved 2026-09-13T18:41:13.506Z.