Image: Wikimedia Commons · CC BY-SA 3.0 · via Wikimedia Commons
Beechcraft B200 crash at Southend Airport: AAIB details loss of control moments after takeoff
Investigation into July 2026 Southend Airport crash reveals aircraft yawed left then lost control, killing four onboard including two pilots and medical staff.
The gist
Southend Airport Beechcraft B200 lost control shortly after takeoff, crashed in fatal fireball killing all four onboard, says AAIB update.
Continuing coverage
All Flight Safety →- UK investigators probe limited clues in fatal Zeusch King Air crash at Southend
- EASA bans flights over Gulf states amid renewed US-Iran hostilities
- Two Jets Trigger TCAS Alert Over Atlantic After Cruising Altitude Conflict
- Kenya Airways Dreamliner Returns to Nairobi Due to Flight Controls Spoiler Issue
- Pentagon Ends Suspension of South Carolina Apache Pilots After July 4th Coastal Flyover
On July 13, 2026, a Beechcraft B200 Super King Air operated by Zeusch Aviation crashed shortly after taking off from London Southend Airport, resulting in the deaths of all four people onboard. The Air Accidents Investigation Branch (AAIB) has since provided an update on the tragic accident as investigators continue to examine the circumstances surrounding the crash. The aircraft yawed slightly to the left prior to rotation and then lost control soon after becoming airborne, ultimately crashing and erupting in a fireball that caused severe damage and prevented preservation of much physical evidence.
The AAIB confirmed that after lift-off, the aircraft deviated left from the runway centerline during a climbing left turn. It reached an altitude between 70 and 80 feet above the runway before completing a 90-degree turn and beginning to descend uncontrollably back toward the ground. Eyewitnesses reported the plane rolling left almost into an inverted position before impact, emphasizing the sudden loss of control during the critical initial climb phase.
Due to the intense impact and subsequent post-crash fire, the physical remains of the Beechcraft B200 were heavily damaged, limiting investigators’ ability to examine the airframe and components fully. Detailed technical scrutiny has been conducted in close cooperation with the manufacturer, but the overall focus remains on identifying the contributing technical, operational, human, and organizational factors behind the accident.
The AAIB’s investigation team has leveraged various data sources to reconstruct the flight path and sequence of events. Analysis of witness videos, airport CCTV footage, and Automatic Dependent Surveillance-Broadcast (ADS-B) data permitted a detailed trajectory mapping despite the absence of onboard flight data recorders. The Beechcraft B200 was not required to be equipped with cockpit voice or flight data recorders, common in smaller aircraft, posing additional challenges for determining precise causal factors.
Zeusch Aviation, the operator of the ill-fated flight, is primarily engaged in missions such as medical evacuations, transplant flights, aerial mapping, and various surveillance and relay operations. The presence of a doctor and a nurse among the fatalities underlines the aircraft’s medical role at the time of the accident. The crash represents one of the UK’s gravest recent aviation tragedies, renewing attention on flight safety oversight at smaller regional airports and with special-mission aircraft.
In immediate response to the crash, London Southend Airport suspended operations to manage emergency response and secure the accident site. The incident also triggered intense activity from the AAIB and collaborating partners who remain committed to uncovering all relevant facts. The investigation timeline has not been finalized but will culminate with a comprehensive report outlining causes and safety recommendations.
The AAIB emphasized that its thoughts continue to be with the families and loved ones of those who lost their lives, and all affected by this devastating accident. As the inquiry progresses, the focus remains on understanding the complex interplay of factors that led to the loss of control in the seconds after takeoff. This will be crucial to informing prevention measures to avoid recurrence of similar tragedies in the future.
Frequently asked questions
- What caused the Beechcraft B200 to crash at Southend Airport?
- Investigators found the aircraft yawed left before losing control shortly after takeoff, dipping and rolling before crashing; technical and human factors are being examined.
- Were flight data recorders available to aid the investigation?
- No flight data or cockpit voice recorders were on board as the Beechcraft B200 was not required to have them, so investigators relied on videos, CCTV, and ADS-B data.
- Who were the victims of the Southend Airport crash?
- All four onboard perished, including two pilots, a doctor, and a nurse, reflecting the aircraft's medical evacuation role operated by Zeusch Aviation.
Read more
All Aviation Safety →
EASA bans flights over Gulf states amid renewed US-Iran hostilities
The European Union Aviation Safety Agency (EASA) has told airlines not to operate in the airspace of Bahrain, Kuwait, Qatar or the United Arab Emirates as renewed fighting between the United States and Iran creates unacceptable risks to civil aircraft. The new Conflict Zone Information Bulletin, issued July 14, 2026, also covers airspace over the Gulf of Oman within the Muscat Flight Information Region west of 58 degrees east longitude. EASA's recommendation applies at all altitudes and flight levels and remains valid through July 29 unless the agency rescinds it. The bulletin applies to EASA-regulated airlines and foreign operators flying to, from or within the European Union under an EASA authorization. Individual countries retain authority over their airspace, but EASA's guidance effectively tells airlines under its oversight to stay out of many of the region's aviation corridors. EASA said repeated violations of the US-Iran ceasefire had again created a high level of risk across the Gulf. Iranian efforts to control the Strait of Hormuz, attacks against commercial ships and related US military action have increased the danger in the region, according to the bulletin. EASA also pointed to major US military facilities in Gulf states as potential targets for Iranian missiles and drones. EASA said missile and drone activity, interceptions and falling debris pose a threat to nearby airspace. The agency also warned that active US and regional air defenses could mistake a civilian aircraft for a military target. "Unpredictable military developments, combined with the possible use of missiles, drones, combat aircraft and air-defense systems, create a high risk to civil flights at all altitudes and flight levels within the concerned airspace," EASA said. The agency issued the tougher warning less than a week after allowing a broader Middle East and Persian Gulf bulletin to expire. On July 8, EASA said an overall reduction in short-term tensions meant it would replace the previous bulletin with a lower-level information note covering the wider region. Separate warnings remained in place for Iran, Iraq and Lebanon. The situation has since deteriorated. Iran fired ballistic missiles at a US air base in Jordan on July 14, while US forces carried out a third consecutive night of attacks after Iran moved to close the Strait of Hormuz. EASA advised airlines to continue monitoring regional airspace developments and follow notices issued by national aviation authorities. Separate EASA bulletins advising airlines not to operate in the airspace of Iran, Iraq and Lebanon remain in effect through August 31.
Passenger refuses to sit beside woman citing Sharia law, assaults flight attendant on Turkey-Germany flight
A German resident of Turkish descent was arrested upon landing on a flight from Turkey to Germany, after he refused to sit next to a female seat mate, only to then punch the flight attendant when she tried to help with the situation. The guy then proceeded to insult police officers in Turkish, leading to even more charges… talk about awful behavior. Passenger causes commotion on Turkey to Germany flight German media is reporting on an incident that happened on June 1, 2026, on a flight from Samsun, Turkey (SZF), to Dusseldorf, Germany (DUS). This happened on a SunExpress flight, with that being a leisure airline that's a joint venture between Lufthansa and Turkish Airlines. According to reports, the 29-year-old man ended up in a situation where he was sitting next to a female, which he wasn't comfortable with, claiming it was in violation of Sharia law. When the flight attendant confronted him, he reportedly punched her in the face. German Federal Police were called to the airport in Dusseldorf shortly before 7AM, to take a report of the assault. A criminal complaint was subsequently filed. The passenger confessed to the crime, though the conversation didn't go smoothly. The man reportedly insulted the police officers in Turkish, thinking they wouldn't understand. However, since one of the officers spoke Turkish, the man received an additional charge of insult, beyond his charge of assault. One detail that's not known is the context in which he ended up sitting next to a woman. Like, how did this incident only happen while the plane was in the air, and not on the ground in Turkey, before departure, since presumably he would've been offloaded at that point? This incident happened on a SunExpress flight This situation is obviously terrible on all levels Even as someone who isn't really religious, I think people are entitled to there sincerely held religious beliefs. However, if your religious beliefs impact the ability of others to go about their day, I think it's on the person with the religious beliefs to make accommodations, rather than putting that burden on others. On the topic of Sharia law, as you'd expect, different people have different interpretations. The idea is that direct contact and interaction with the opposite gender (if not related by blood, marriage, etc.) is only allowed for necessity. I guess the idea here is that if you're sitting next to someone on a plane you could accidentally touch, and that was presumably an issue for him. Now, let me point out that not all people with that general belief system interpret things that way, and many will view it as being fine to sit next to someone of the opposite gender on a plane. If this is really how the guy felt, he should've purchased an extra seat (which SunExpress allows) to prevent any potential touch. Of course the irony here is that he was so concerned about inadvertently making contact with a female, only to then… slap a female, which I'm pretty sure would qualify as direct contact. Then the icing on the cake here is that he insulted the police officers, which is a criminal offense in Germany, and it can even lead to imprisonment. Ouch all around… This guy should've purchased an extra seat, if it was so important Bottom line A passenger on a SunExpress flight had quite the meltdown, when he first refused to sit next to a woman, only to then punch the flight attendant when she tried to intervene. When the flight was met by police in Germany, he then insulted the officers, which is also a crime in Germany. While I respect sincerely held religious beliefs, this guy was 100% in the wrong on all counts here, and I imagine he'll be held accountable for his behavior. What do you make of this flight seating incident?
Oregon launches comprehensive public drone pilot training and testing framework
The Oregon Department of Aviation released a training and testing template July 10 for public agencies that operate drones. This new template provides additional model standards that public agencies may adopt and customize for pilot qualifications, recurrent training and public-safety missions. Training Beyond Part 107 The FAA requires Part 107 certificate holders to complete online recurrent training every 24 calendar months, in an effort to maintain aeronautical knowledge recency. Oregon's document goes further by adding written test questions, practical flight evaluations, emergency drills, airspace-deconfliction exercises, privacy and public-records training, maintenance requirements and launch-decision checklists. "This is the next step in building safe and accountable public agency drone programs in Oregon," Oregon Department of Aviation Director Kenji Sugahara said. "A policy tells an agency what the rules are. Training and testing show whether people can actually apply those rules in the field. That matters when drones are being used near roads, bridges, neighborhoods, emergency scenes, firefighters, patients, helicopters, or disaster areas." Public-Agency Requirements Oregon law already requires public bodies to register public-use drones with the state aviation department and submit annual reports. Those reports must summarize how frequently the aircraft were used, explain the primary purposes of the flights and direct the public to the agency's drone policies. Educational institutions register as drone users rather than registering each aircraft. The template is designed for cities, counties, state agencies, fire departments, emergency managers, transportation departments and other public bodies. Optional sections address Drone as First Responder programs, fire and EMS support, search and rescue, emergency management, mutual aid, remote operations and FAA-authorized flights beyond visual line of sight. The department said the document does not create new flight authority, authorize law enforcement activity or permit operations beyond FAA limits.
Large drone collides with LAPD helicopter over San Fernando Valley, forcing emergency landing
A large drone struck a Los Angeles Police Department helicopter during a patrol over the San Fernando Valley, damaging the aircraft's windshield and forcing the crew to make a precautionary landing. The Airbus AS350 was flying near the 101 Freeway and Reseda Boulevard in Tarzana shortly before 15:00 local time on July 7, 2026, when it collided with the drone, according to the LAPD and a preliminary Federal Aviation Administration (FAA) report. The pilot landed safely at nearby Van Nuys Airport (VNY). Neither of the two officers aboard the helicopter was injured. Authorities described the drone as measuring approximately three feet by three feet, considerably larger than most hobbyist drones. Investigators have not identified its make or model or the person operating it. The collision happened as firefighters battled a brush fire near the Encino Reservoir. An LAPD official said the drone operator may have been attempting to record the fire, although authorities have not determined whether the aircraft was deliberately flown near the helicopter. The FBI and FAA have opened investigations. Los Angeles Mayor Karen Bass called the incident "completely unacceptable" and warned drone operators against interfering with police and firefighting aircraft. "This is a warning to anybody who's flying a drone that interferes with Fire or Police: We will find you, you will be arrested, and you will be prosecuted," Bass said. Drones operating near wildfires can put a halt to aerial firefighting operations as crews cannot safely share the airspace with an unidentified aircraft. The FAA generally limits drones to 400 feet above the ground, with additional restrictions around airports and emergency operations. Authorities have not released photographs of the damaged helicopter or video showing the collision. The drone operator remained unidentified as of July 13. The incident is the latest collision involving a drone and a crewed aircraft in US airspace. The FAA receives thousands of reports each year involving drones operating near airplanes and helicopters, although confirmed midair collisions remain relatively rare.
The Daily Touch & Go
The day's best aviation news in your inbox. Free, no spam.