NTSB Issues Preliminary Report on Fatal Socata TB21 Crash in Arizona

The National Transportation Safety Board (NTSB) has released its preliminary report regarding the fatal crash of a Socata TB21 Trinidad near Prescott, Arizona. The incident, which occurred on the evening of February 4, 2026, resulted in the death of the pilot, who was the sole occupant of the aircraft. The report establishes a factual timeline of the flight’s final minutes, focusing heavily on communications between the pilot and air traffic control at Prescott Regional Airport (PRC).

According to the NTSB documents, the single-engine aircraft (Registration N967WM) was conducting a visual approach at night when it impacted terrain approximately two miles north of the runway. While the preliminary report details the sequence of events leading up to the crash, it does not yet determine a probable cause. Investigators are continuing to examine pilot history, aircraft maintenance, and environmental factors.

Flight Timeline and ATC Communications

The NTSB report outlines a specific chronology of the flight, which originated from John Wayne Airport (SNA) in Santa Ana, California, at approximately 4:50 PM PST. The flight proceeded to Arizona without incident until the approach phase into Prescott.

Arrival at Prescott

At 7:44 PM MST, the pilot contacted Prescott Tower to announce his intent to land. The tower controller initially instructed the pilot to maintain an altitude at or above 6,500 feet Mean Sea Level (MSL), cross over the airport, and enter a left downwind leg for the runway. The pilot acknowledged these instructions and proceeded to fly over the airport as directed.

The Final Maneuvers

Shortly after the initial approach began, the tower controller updated the instructions. At 7:47 PM MST, the controller advised the pilot that the altitude restriction was canceled and instructed him to extend his downwind leg. The controller stated that the tower would call the pilot’s base turn, the turn required to align the aircraft with the runway for landing.

Approximately 46 seconds after the instruction to extend the downwind leg, the controller issued a traffic advisory regarding another aircraft on final approach. The NTSB report notes:

“The pilot acknowledged this caution. This acknowledgment was the last communication from the aircraft.”

Radar contact was lost shortly after this transmission while the aircraft was maneuvering north of the airport. The wreckage was subsequently discovered in open terrain near Poquito Valley.

Wreckage and Environmental Conditions

The crash site was located in a remote field roughly two miles north of the runway threshold. First responders and NTSB investigators described the scene as a scattered debris field, consistent with a high-energy impact. The aircraft was destroyed upon impact.

Weather data included in the report indicates that the flight was operating under Visual Meteorological Conditions (VMC). Skies were reported as clear with good visibility, suggesting that adverse weather was likely not a primary factor. However, the crash occurred during hours of darkness in an area known for sparse ground lighting.

AirPro News Analysis

While the NTSB has not yet assigned a cause, the factual details regarding the “extended downwind” instruction at night are significant. In aviation safety, extending a downwind leg at night in mountainous terrain can expose pilots to spatial disorientation or controlled flight into terrain (CFIT), particularly if ground lighting is insufficient to provide a visual horizon. This phenomenon, often called the “black hole effect,” is a known risk factor for night approaches into airports surrounded by unlit terrain.

The Socata TB21 is a complex, high-performance aircraft. Managing a delayed base turn while monitoring traffic and maintaining terrain clearance at night imposes a high cognitive load on a single pilot. Future investigative updates will likely focus on whether the extended path took the aircraft into an area of rising terrain or if the pilot lost situational awareness during the maneuver.

Investigation Status and Next Steps

The current document is a preliminary fact-finding report. The NTSB emphasizes that it does not contain analysis or a determination of probable cause. A final report, which will include the board’s official conclusions, typically takes 12 to 24 months to complete.

Moving forward, investigators will focus on several key areas:

• Pilot Background: A review of the 64-year-old pilot’s training, medical certification, and potential fatigue factors.
• Mechanical Integrity: An examination of maintenance logs, the engine, and flight controls to rule out mechanical failure.
• ATC Handling: An analysis of the timing of the controller’s instructions, specifically the command to extend the downwind leg and the management of traffic separation.

Frequently Asked Questions

What is a Preliminary Report?

A preliminary report is an initial document released by the NTSB shortly after an accident. It contains factual information gathered on-scene, such as flight times, weather conditions, and wreckage location, but does not analyze the data or determine why the accident happened.

When will the cause of the crash be known?

The NTSB typically releases a final report, which includes the probable cause, 12 to 24 months after the accident. This allows time for detailed forensic analysis of the wreckage and review of all operational factors.

Was the weather a factor?

Current reports indicate the flight was operating in Visual Meteorological Conditions (VMC) with clear skies. However, the lack of daylight and the terrain environment are factors investigators will consider regarding visibility and spatial orientation.

Sources

• NTSB Preliminary Report