WPR26FA097 · SOCATA TB21
SOCATA TB21 · Accident: collision with terrain/object (non-CFIT) on approach
From John Wayne Orange County International Airport (SNA) to Prescott Regional Airport - Ernest A. Love Field (PRC)
Event
- NTSB case
- WPR26FA097
- 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
- Ongoing
- 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
SOCATA TB21
- Aircraft type
- Socata TB21
- 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
- N967WM
- Operator
- Cameron English
- Onboard fatalities
- Unknown
- Route
- From John Wayne Orange County International Airport (SNA), Santa Ana, CATo Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZ
- Aircraft age
- About 36 years (built 1990)
- 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
- Approach · VFR pattern final
- 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
- Collision with terrain/object (non-CFIT)
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On February 4, 2026, about 1950 mountain standard time, a Socata TB21, N967WM, was destroyed when it was involved in an accident near Prescott, Arizona. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
ADS-B data captured by the FAA showed that the airplane departed from John Wayne/Orange County Airport (SNA) Santa Ana, California, in visual meteorological conditions about 1650 Pacific standard time (PST), with a planned destination of Prescott Regional /Ernest Love Field Airport (PRC) Prescott, Arizona, about 278 nautical miles east of SNA The enroute cruise altitude was about 11,500 ft mean sea level (msl) and the airplane flew on an easterly heading for about 2 hours. Air Traffic Control audio indicated that the pilot contacted the PRC tower controller about 1944 and announced his intention to land. The tower controller instructed the pilot to maintain an altitude at or above 6,500 ft msl, pass over the airport, and enter the downwind for Runway 21L. The pilot acknowledged the instructions and flew over the airport about 1947. At 1948:06, the tower controller cancelled the altitude restriction, instructed the pilot to extend the downwind, and stated he would call the base turn. The pilot acknowledged the controller’s instructions. About 1948:46, the controller cautioned the pilot about his proximity to the final approach course with another airplane on final approach, and the pilot acknowledged. While flying downwind, the pilot continued past the airport, flying over a large area of unlit pastureland. At 1949:01, the controller cleared the pilot to land on Runway 21L. At this time the airplane was about 3 nautical miles northeast of PRC and the pilot began the left turn to the base leg of the airport traffic patttern. ADS-B data indicated that as the airplane turned, it rapidly descended, losing about 800 ft of altitude and gaining about 58 knots of airspeed in about 16 seconds. The airplane disappeared from radar at 1950:45. Subsequently, the tower attempted to contact the pilot multiple times and requested assistance from other airplanes in the area in locating the airplane. The airplane came to rest inverted in upward sloping pasture consisting of grassy vegetation on a northeasterly heading at an elevation of about 4,900 ft msl. The main wreckage was located about 3 miles northeast of the approach end of runway 21L near the extended center line of the runway. The initial impact point (IIP) was marked by a ground scar that contained fragments from the left position light. A debris path extended about 440 ft from the IIP on a magnetic heading of about 287°. All major components of the airplane were located within the debris field. Both wings had separated from the fuselage and were fragmented along the debris path. The fuselage and empennage remained attached and came to rest about 360 ft west of the IIP and the engine was located about 60 ft west of the fuselage. A ground scar with 5 propeller strike marks was located about 31 ft west of the IIP and was collocated with the propeller blades and hub. The two propeller blades exhibited chordwise scratches, nicks, and gouges. One propeller blade displayed S bending and the other propeller blade was bent outboard. The airplane was recovered to a secure location for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record WPR26FA097
- Event ID
- 20260205202392
- Case number
- WPR26FA097
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2026-02-05.
- API snapshot SHA-256: b0836e6295cc656645ca0be35d3e3e6e72ffe9f8c577d262fdace04c785b3895; retrieved 2026-09-15T09:13:09.005Z.