Regulations & Safety
EVA Air Captain Suspended After Alleged Cockpit Assault at LAX
EVA Air suspends captain following alleged cockpit assault during taxi at LAX. Investigation launched by airline and Taiwan Civil Aeronautics Administration.

This article summarizes reporting by Aviation24.be, Focus Taiwan, and other industry sources.
EVA Air Captain Suspended Following Alleged Cockpit Assault at LAX
EVA Air has suspended a senior captain and launched a formal investigation following reports of a physical altercation inside the cockpit of a Boeing 777-300ER at Los Angeles International Airport (LAX). The incident, which reportedly took place in late December 2025 or early January 2026, involved a dispute over taxiing speed that escalated into physical violence between the flight deck crew members.
According to reporting by Aviation24.be and Taiwanese media outlets, the conflict occurred while the aircraft was preparing for departure to Taipei (TPE). The altercation has drawn the attention of Taiwan’s Civil Aeronautics Administration (CAA), which has initiated an independent probe into potential safety violations.
While the flight completed its transpacific journey safely, the incident has raised significant questions regarding Crew Resource Management (CRM) and the airline’s decision to allow the pilots to continue the flight immediately after the alleged assault.
Details of the Cockpit Dispute
The incident reportedly began during the taxi-out phase at LAX. Sources indicate that the First Officer, a Malaysian national serving as the Pilot Monitoring (PM), believed the aircraft was moving too fast. Standard Operating Procedures (SOP) generally dictate a taxi speed limit of approximately 30 knots.
Escalation to Violence
Reports from Focus Taiwan suggest that the First Officer issued verbal warnings regarding the speed, which were allegedly ignored by the Captain, a Taiwanese national identified by the surname Wen. Following the ignored warnings, the First Officer intervened by manually applying the brakes.
This intervention reportedly enraged the Captain. According to details summarized by Simple Flying and Mothership.sg, the Captain physically assaulted his colleague in response to the braking maneuver.
“The captain… reportedly became enraged by the intervention and punched the first officer at least four times.”
, Summary of reports via Aviation24.be
The First Officer reportedly sustained visible physical injuries, including bruising and swelling on the back of his hand. Despite the violence in the flight deck, the aircraft proceeded to take off and complete the long-haul flight to Taiwan.
Operational Response and Investigations
Following the flight, EVA Air moved to address the situation, though whistleblowers have criticized the timeline of the airline’s response.
Airline Findings vs. Crew Allegations
EVA Air has stated that the Captain is currently suspended from flight duties pending the outcome of the investigation. However, the airline offered a defense regarding the technical cause of the dispute. According to the carrier, preliminary data retrieved from the aircraft’s Quick Access Recorder (QAR) suggests the plane was not speeding and remained within regulatory limits during the taxi sequence.
The case is set to be referred to the airline’s disciplinary review board once the investigation concludes. The Taiwan CAA has also stated it will impose legal penalties if the investigation confirms that flight safety was compromised by the crew’s conduct.
Whistleblower Concerns
The handling of the incident has sparked internal criticism. A whistleblower cited in Taiwanese media, including The Reporter, questioned why the airline’s emergency response plan was not activated immediately. The primary concern raised was the fitness of the Captain to command a flight immediately after exhibiting what was described as “emotionally unstable” behavior.
Critics argue that allowing a pilot who has just allegedly assaulted a crew member to operate a 12-hour flight across the Pacific poses a severe risk to passengers and crew, regardless of whether the taxi speed was technically within limits.
Broader Context: Safety and Labor Challenges
This cockpit altercation is the latest in a series of operational and personnel challenges facing EVA Air. Industry observers note that the airline has dealt with several high-profile incidents in recent years.
- October 2025: A flight attendant reportedly died after allegedly being denied medical leave and working while ill on a flight from Milan to Taipei, sparking labor disputes.
- August 2024: Six flight attendants were injured when flight BR238 encountered severe turbulence during meal service.
- May 2023: A pilot was fired after failing an alcohol test, though the airline faced scrutiny for allegedly allowing multiple re-tests rather than immediately grounding the individual.
AirPro News Analysis
The Breakdown of Crew Resource Management (CRM)
While the physical assault is the most sensational aspect of this story, the underlying safety failure is the total collapse of Crew Resource Management (CRM). Modern aviation safety relies on the “two-person rule,” where pilots cross-check each other to prevent errors. If a First Officer feels they cannot speak up, or worse, if they are physically attacked for intervening, the safety net is destroyed.
Furthermore, the decision to continue the flight is perplexing from a risk management perspective. A cockpit environment where one pilot has struck another is, by definition, a hostile work environment. Communication and trust, which are essential for handling in-flight emergencies, would be non-existent. If these allegations are substantiated, it suggests a significant lapse in the safety culture regarding pilot fitness and conflict resolution.
Frequently Asked Questions
Was the flight cancelled?
No. Despite the altercation occurring on the ground at LAX, the flight continued to Taipei and landed safely.
Was the plane actually speeding?
EVA Air claims that data from the Quick Access Recorder (QAR) indicates the aircraft was within standard taxi speed limits, contradicting the First Officer’s perception at the time.
What is the status of the pilots?
The Captain has been suspended pending investigation. The status of the First Officer has not been publicly specified beyond the reporting of his injuries.
Sources:
Photo Credit: Boeing
Regulations & Safety
NTSB: Thermal Plugs Caused AA Flight 3023 Tire Failure
NTSB determines melted thermal relief plugs caused tire failure on American Airlines 737-8 at Denver, triggering emergency evacuation.

The National Transportation Safety Board (NTSB) has determined that melted thermal relief plugs caused the left main landing gear tires to fail on an American Airlines Boeing 737-8 during a July 2025 takeoff roll at Denver International Airport (DEN), prompting a high-speed rejected takeoff and emergency evacuation.
The final aviation investigation report, published on August 26, 2026, officially closes the inquiry into American Airlines Flight 3023. The document details the mechanical sequence that led to the tire failure while highlighting significant passenger noncompliance during the subsequent evacuation, as travelers ignored crew commands and retrieved carry-on baggage.
Mechanical sequence and rejected takeoff
The incident occurred on July 26, 2025, involving a Boeing 737-8, registration N306SW, equipped with CFM International LEAP-1B28 engines. According to the NTSB, the flight experienced an approximate 25-minute delay while awaiting departure at runway 34L.
During the subsequent takeoff roll, as the aircraft reached an indicated airspeed between 90 and 100 knots, the captain reported hearing a loud pop accompanied by a noticeable bump. The flight crew initiated a rejected takeoff at speeds above 80 knots.
The NTSB determined the probable cause of the incident was the melting of thermal relief plugs in the left main landing gear. This melting released tire pressure and caused the tires and wheels to fail during the takeoff roll. The agency noted that this failure resulted in abnormal airplane handling characteristics, which prompted the flight crew to reject the takeoff. Debris from the fractured wheels caused minor damage to the aircraft, including a three-inch dent on the lower skin of the left wing.
Emergency evacuation and passenger behavior
Following the rejected takeoff, the flight crew initially instructed the cabin to remain seated. Between 30 and 45 seconds later, after identifying smoke and fire originating from the left main landing gear, the crew ordered an emergency evacuation.
The aircraft carried 175 occupants, comprising 169 passengers and six crew members. The NTSB final report confirms that zero injuries occurred during the event. This official casualty figure supersedes preliminary media reports from July 2025 that had indicated minor injuries and hospital evaluations.
The investigation report draws specific attention to passenger behavior during the emergency egress. The NTSB stated that the cabin crew described the evacuation as rapid but hindered by significant passenger confusion and noncompliance. Despite flight attendants repeatedly commanding passengers to leave their belongings behind, multiple individuals retrieved their carry-on baggage. The NTSB concluded that this noncompliance directly slowed the flow of egress from the aircraft.
AirPro News analysis
The NTSB findings regarding American Airlines Flight 3023 add to a well-documented and growing safety concern within the commercial aviation sector. Passenger retrieval of carry-on baggage during emergency evacuations is a recurring issue that compromises the 90-second evacuation standard mandated by the Federal Aviation Administration (FAA).
When passengers stop to open overhead bins and carry luggage down escape slides, they not only slow the egress rate for those behind them but also introduce the risk of puncturing the evacuation slides or injuring fellow passengers. We continue to see official accident reports cite passenger noncompliance as a negative factor in evacuation efficiency. This recurring behavioral pattern has prompted safety advocates and lawmakers to question whether current FAA evacuation certification tests, which rely on compliant participants, accurately reflect real-world human behavior during an emergency.
Sources: National Transportation Safety Board
Photo Credit: National Transportation Safety Board
Regulations & Safety
Marine One Loss of Separation at DCA: NTSB Preliminary Report
NTSB cites radio line-of-sight failure after Marine One and Envoy Air E-170 came within 0.82 NM at Reagan National.

This is a developing story. Information may change as official details are released.
This is original reporting and analysis by AirPro News.
A loss of separation occurred on August 4, 2026, between a Sikorsky VH-3D operating as Marine One and an Envoy Air Embraer E-170 departing Ronald Reagan Washington National Airport (DCA). The incident took place approximately two miles north of the airport at 14:34 EDT and prompted an immediate Federal Aviation Administration (FAA) relocation of radio equipment after investigators identified a communication failure.
According to a preliminary report released on August 27, 2026, by the National Transportation Safety Board (NTSB), air traffic controllers at DCA did not receive a required three-minute pre-departure warning from the helicopter. The event triggered a review of strict Safety protocols implemented following a fatal midair collision in the same airspace in January 2025.
Incident timeline and separation data
The loss of separation occurred when Marine One departed The Ellipse simultaneously with Envoy Air flight 3742 departing runway 1 at DCA. Preliminary FAA estimates indicate the aircraft came within 0.82 nautical miles (NM) laterally and 700 feet vertically. The NTSB is currently analyzing surveillance data to establish the exact closest point of approach.
President Donald Trump was on board the Sikorsky VH-3D at the time of the incident. In a statement provided to CBS News, White House spokesman Kush Desai confirmed the President was never in danger.
Marine One flights are piloted by the finest aviators in the world, and the White House maintains the utmost confidence in these patriots and other security officials who are responsible for ensuring the President’s safety.
No injuries were reported among the occupants of either aircraft, and both flights continued to their respective destinations without further incident.
Communication failure and FAA response
The NTSB preliminary report points to inadequate radio line-of-sight coverage between The Ellipse and the DCA tower as the primary factor in the missed pre-departure warning. A DCA tower controller reported that the transmission attempt from the helicopter was “broken and unreadable,” according to CBS News.
Following the August 4 incident, FAA technicians evaluated the infrastructure and confirmed the line-of-sight deficiency. To resolve the issue, the agency relocated the helicopter-control radio equipment to the top of the DCA control tower. Subsequent communication checks were successful.
CBS News also reported that recent construction at the White House may have contributed to the radio line-of-sight degradation, though the NTSB has not yet issued a final determination on the cause.
Regulatory context and prior airspace changes
The airspace surrounding DCA operates under highly specific procedural rules designed to deconflict fixed-wing airline traffic from frequent VIP helicopter movements. These procedures were significantly tightened following a fatal midair collision on January 29, 2025, involving an airliner and an Army Black Hawk helicopter near the airport.
Following the 2025 accident, regulators instituted a requirement for a ground stop at DCA anytime a Helicopters passes on a conflicting route. The failure of the three-minute warning on August 4 prevented controllers from initiating this required ground stop for the Envoy Air departure.
Air traffic controllers and Marine One pilots had previously met on July 28, 2026, exactly one week prior to the incident, to discuss ongoing communication challenges in the sector.
AirPro News analysis
The August 4 loss of separation highlights the fragility of procedural deconfliction in the Washington, D.C. airspace. While the FAA characterized the event as a momentary loss of separation, the failure of a critical communication link reveals a single point of failure in the safety protocols established after the 2025 collision. We note that the rapid relocation of the radio equipment by the FAA demonstrates an acknowledgment of the infrastructure gap. As the NTSB continues its Investigation, we will monitor the docket for potential systemic recommendations regarding how VIP helicopter movements integrate with high-volume Commercial-Aircraft traffic at DCA, particularly concerning redundant communication systems.
Sources: National Transportation Safety Board
Photo Credit: National Transportation Safety Board
Regulations & Safety
FAA Moves to Fire Two LaGuardia Controllers After Fatal Collision
FAA initiates termination proceedings against two LaGuardia controllers for early shift departures on the night of the March 22, 2026 runway collision.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by Reuters by David Shepardson and Doyinsola Oladipo.
The FAA has initiated termination proceedings against two air traffic controllers accused of leaving their shifts early on the night of a fatal runway collision at LaGuardia Airport (LGA) in March 2026. The agency is classifying the unauthorized early departures as timecard fraud amid a broader national crackdown on the practice.
The disciplinary action follows the March 22, 2026, accident in which Air Canada Express Flight 8646, operated by Jazz Aviation LP, collided with an aircraft rescue firefighting (ARFF) vehicle while landing on Runway 4. According to Reuters, the two controllers allegedly departed the facility approximately one hour before their scheduled shifts ended, a practice colloquially known as an “early shove.”
Disciplinary actions and union response
The FAA stated its commitment to holding employees accountable, emphasizing that it will not compromise the safety or efficiency of the national airspace system. U.S. Secretary of Transportation Sean Duffy condemned the practice, stating that while most controllers complete their full shifts, the department will not tolerate fraud from individuals who unfairly burden their colleagues and impact the airspace.
The National Air Traffic Controllers Association (NATCA) confirmed it is actively discussing the allegations with FAA leadership. The union indicated that these internal discussions are the appropriate forum for addressing the matter. Reuters reports that the FAA is currently conducting a nationwide enforcement effort targeting employees who leave on break at the end of their shifts and fail to return.
The March 22 collision and investigation
The NTSB continues to investigate the March 22 collision under investigation ID DCA26MA161. The official cause of the accident remains undetermined. The aircraft involved was an MHI RJ Aviation CRJ-900, and the ground equipment was an Oshkosh Striker 1500 ARFF vehicle.
Official NTSB figures confirm that 76 people were on board the aircraft, including 72 passengers, two flight attendants, and two pilots. The captain and first officer sustained fatal injuries. Thirty-nine individuals were transported to local hospitals, with six reported to have serious injuries.
It remains unverified whether the controllers’ early departure directly influenced the events leading to the collision. Speaking in March 2026, NTSB Chair Jennifer Homendy noted that operating with two controllers in the tower cab during a midnight shift is common practice across the national airspace system, suggesting the facility may have been operating at standard staffing levels at the time of the accident.
Regulatory response to surface safety
Following the LaGuardia accident, the FAA accelerated initiatives to improve surface visibility at airports. On May 13, 2026, the agency announced a $16.5 million investment to equip all airport vehicles with transponders.
These vehicle movement area transponders (VMATs) are designed to provide ATC with better situational awareness of ground equipment operating on runways and taxiways.
AirPro News analysis
We note that the FAA’s decision to pursue termination for timecard fraud rather than operational errors highlights a strict administrative approach to facility management. By focusing on the unauthorized absence, the agency addresses the “early shove” culture directly without preempting the NTSB’s ongoing safety investigation into the collision’s root causes. The distinction between administrative violations and operational fault will likely remain a focal point as NATCA engages with FAA leadership.
Photo Credit: Mike Segar – Reuters
-
Technology & Innovation7 days agoSkyband Systems M100 LRU Validates GNSS Jamming Protection
-
MRO & Manufacturing6 days agoBoeing SPEEA Engineers Reject Contract, Authorize Strike
-
Military Technology6 days agoSaab Unveils A3-001 Supersonic Stealth Drone Concept
-
Business Aviation6 days agoFTAI Aviation Closes $2B Warehouse Financing for 2026 SPV
-
Business Aviation6 days agoSyberJet SJ30-2 Sets Transcontinental Speed Record
