Regulations & Safety
NTSB Releases Preliminary Report on Socata TB21 Crash in Arizona
NTSB issues preliminary report on fatal Socata TB21 crash near Prescott, Arizona, detailing flight timeline and ongoing investigation.

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
Photo Credit: X
Regulations & Safety
NTSB Warns First Responders on Ballistic Parachute Hazards
NTSB Safety Alert SA-102 warns first responders that undeployed BPRS rockets on downed aircraft can fire at any time.

The National Transportation Safety Board (NTSB) is urging first responders to exercise extreme caution around downed aircraft equipped with ballistic parachute recovery systems (BPRS), warning that undeployed rocket mechanisms pose a severe risk of injury or death during rescue operations.
Following the issuance of Safety Alert SA-102 on January 20, 2026, the NTSB released a supplementary educational video on June 18, 2026, to amplify its safety campaign. The agency noted that while systems like the Cirrus Airframe Parachute System (CAPS) are designed to save lives in flight, “they pose a hazard to first responders at an accident site if the rocket did not activate before or during ground impact.”
Hidden hazards in the wreckage
First responders frequently need to extricate occupants from deformed fuselages following an aviation accident. The NTSB warned that the activation cable running along the airframe of a BPRS-equipped aircraft may be under tension and near its breaking point due to crash damage. Any sudden movement or structural cutting could inadvertently trigger the solid-propellant rocket.
If you must cut through the fuselage to free an occupant, avoid cutting the activation cable of the BPRS. If you need to cut the cable, be aware that this could activate the rocket.
The agency explicitly advised emergency personnel to contact the NTSB before attempting to disable any undeployed parachute systems, as the rocket can fire at any time if the system is compromised.
Historical precedent and emergency protocols
The safety alert cited three specific accident investigations where undeployed BPRS rockets created immediate hazards for ground personnel.
On February 16, 2016, an Evolution Revo crashed near Buckeye, Arizona. First responders operated around the wreckage for an hour before a Federal Aviation Administration (FAA) inspector alerted them to the active rocket hazard. On March 28, 2021, a Cirrus SR22 GTS crashed near Marana, Arizona. The pilot attempted an in-flight deployment that malfunctioned, leaving the rocket potentially active on the ground. On March 20, 2025, a Cirrus SR22 crashed near LaFayette, Georgia. In that accident, the BPRS rocket activated several minutes after the crash while emergency crews were positioned near the burning aircraft.
To mitigate these risks, the NTSB mandates that first responders immediately contact its 24/7 Response Operations Center at 844-373-9922 upon identifying a BPRS at an accident site.
AirPro News analysis
We note that as manufacturers like Cirrus Aircraft and BRS Aerospace continue to popularize whole-airframe parachutes, the intersection of aviation safety and local emergency response becomes increasingly complex. Local fire and rescue departments are typically the first to arrive at general aviation accident sites, yet they may lack specialized training on aircraft-specific ballistic hazards. The NTSB’s ongoing educational campaign, culminating in the June 2026 video release, underscores a critical gap in cross-disciplinary safety protocols that the aviation industry must actively help close to protect ground personnel.
Sources: National Transportation Safety Board
Photo Credit: NTSB
Regulations & Safety
Ubisoft Co-Founder Claude Guillemot Killed in France Plane Crash
Claude Guillemot, Ubisoft co-founder and EVP of Operations, died June 19 in a Cessna 421 crash near La Baule, France.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by AP News by Angela Charlton, with additional corporate statements reported by Forbes.
Claude Guillemot, a co-founder of the global video game publisher Ubisoft Entertainment SA, and an unnamed flight instructor were killed on June 19, 2026, when their twin-engine Cessna 421 crashed during final approach to La Baule-Escoublac Airports in western France.
The 69-year-old executive served as Ubisoft’s Executive Vice President of Operations and Chairman of Guillemot Corporation SA. According to reporting by AP News, the aircraft was traveling from Rennes to La Baule for a weekend aviation gathering when it went down in a field near the airport and caught fire.
Flight and investigation details
The flight originated in Rennes on Friday evening. Local authorities confirmed two fatalities at the scene, identified as Guillemot and the flight instructor. Guillemot owned the Cessna 421 and was a licensed, experienced pilot. He was reportedly traveling to the Atlantic coast to participate in a private aviation event expected to draw over a hundred aircraft.
The Bureau d’Enquêtes et d’Analyses pour la Sécurité de l’Aviation Civile (BEA), alongside French judicial authorities, has initiated an investigation into the accident. The official cause of the crash has not been determined. Because both occupants were licensed pilots, investigators have not yet confirmed whether Guillemot or the instructor was at the controls at the time of the accident.
Ubisoft confirms executive death
Guillemot was one of five brothers who founded the video game publisher in 1986. The company has since grown into a major international developer, known for highly successful franchises including Assassin’s Creed. On June 20, 2026, Ubisoft released an official statement confirming the loss of its co-founder.
“Ubisoft was deeply saddened to learn of the death of Claude Guillemot, co-founder of the group and chairman of Guillemot Corp., in an accident. Our thoughts are with his family and loved ones during this difficult time. No further statements will be made at this time.”
AirPro News analysis
The loss of a founding executive and operational leader presents an immediate transition requirement for Ubisoft and Guillemot Corporation. While corporate succession plans have not been publicly detailed following the accident, the sudden departure of a key figure who has been with the company since its 1986 inception will require the board to stabilize operational oversight. We expect the BEA investigation to follow standard protocols for general aviation accidents, focusing on weather conditions, aircraft maintenance records, and pilot inputs during the critical final approach phase.
Sources: AP News
Photo Credit: AP News
Regulations & Safety
FAA and EASA Pledge Cooperation on Aviation Certification
FAA and EASA commit to harmonizing certification pathways and expanding safety data sharing for advanced aviation technologies.

The Federal Aviation Administration (FAA) and the European Union Aviation Safety Agency (EASA) formally committed to deepening regulatory cooperation and harmonizing certification pathways for advanced aviation technologies on June 18, 2026.
Announced during the 2026 FAA and EASA International Safety Conference in Chantilly, Virginia, the joint pledge outlines a framework to streamline oversight and advance data-driven Safety Management Systems (SMS) across the global aerospace sector. According to a press release issued by the FAA, the agreement prioritizes collaboration at all organizational levels under the existing United States-European Union Aviation Safety Agreement.
Harmonizing certification and data sharing
The bilateral agreement focuses on several core objectives designed to keep pace with rapid technological advancements. Regulators plan to strengthen information exchange regarding safety oversight and expand the sharing of operational data to support future rulemaking. A primary goal of the pledge is to streamline approval processes for advanced aviation technologies, ensuring that certification pathways remain consistent between the two regulatory bodies.
FAA Administrator Bryan Bedford highlighted the necessity of the agreement during the conference.
“This is one of the most innovative moments in aviation, not just for America but also for our international partners. Sharing information and fostering conversations about safety allow us to strengthen our international partnerships and ensure aviation systems evolve safely and efficiently.”
EASA Executive Director Florian Guillermet echoed this sentiment, noting that strong cooperation between regulators is essential to maintain high safety standards as the industry evolves. Guillermet stated that aligning approaches will allow both agencies to support innovation while preserving public confidence in aviation.
Industry collaboration and future milestones
The joint pledge served as the culmination of the three-day conference, which operated under the theme “Safety Together: Innovation, Integration and Trust.” The event gathered approximately 400 senior aviation professionals, including representatives from manufacturers, airlines, industry associations, and regulatory bodies.
During the event, National Business Aviation Association (NBAA) President and CEO Ed Bolen participated in a fireside chat with Guillermet and FAA Deputy Administrator Chris Rocheleau. The discussion emphasized the requirement for continuous government and industry collaboration to manage the integration of new technologies.
To ensure the pledge translates into actionable policy, executive leadership from both the FAA and EASA committed to meeting regularly. These meetings will focus on reviewing progress, identifying emerging priorities, and sharing implementation updates. The agencies also confirmed that the next FAA-EASA International Aviation Safety Conference is scheduled for June 22 through June 24, 2027, and will be hosted in Cologne, Germany.
AirPro News analysis
We view this renewed commitment between the FAA and EASA as a critical prerequisite for the successful rollout of Advanced Air Mobility (AAM) and electric vertical takeoff and landing (eVTOL) aircraft. Historically, divergent certification standards between the United States and Europe have forced original equipment manufacturers (OEMs) to navigate costly and time-consuming parallel approval processes. By explicitly targeting the harmonization of certification pathways for advanced technologies, the two largest Western aviation regulators are signaling an intent to prevent regulatory fragmentation. The emphasis on expanding Safety Management Systems (SMS) also indicates a shift toward predictive, data-driven oversight rather than reactive rulemaking.
Sources: Federal Aviation Administration
Photo Credit: EASA
-
Sustainable Aviation4 days agoDelta Air Lines Installs VCT Finlets on 240 Boeing 737NG Jets
-
MRO & Manufacturing6 days agoHoneywell Aerospace Spin-Off Approved, Nasdaq Debut June 2026
-
Aircraft Orders & Deliveries6 days agoMooney International Bids to Acquire Spirit Airlines Assets
-
Defense & Military2 days agoVC-25B Bridge Aircraft Arrives at Joint Base Andrews
-
MRO & Manufacturing6 days agoAirbus CEO Warns on EU Costs at New A321neo Line Opening
