Regulations & Safety
FAA Investigates Near-Collision of Frontier Plane and Trucks at LAX
FAA investigates a close call at LAX where a Frontier Airlines plane braked abruptly to avoid trucks crossing a taxiway, highlighting ground traffic risks.
This article summarizes reporting by CBS News and Hunter Sowards.
The FAA (FAA) has launched an official investigation following a near-collision between a commercial passenger jet and two ground vehicles at Los Angeles International Airport (LAX). According to reporting by CBS News, a Frontier Airlines plane was forced to execute an abrupt braking maneuver on an active taxiway to avoid striking two trucks that unexpectedly crossed its path.
The incident, which occurred in early April 2026, has cast a renewed spotlight on airport ground traffic management and control tower visibility. While a disaster was averted, the close call arrives during a period of heightened national anxiety regarding aviation safety, following a tragic runway collision in New York just weeks prior.
At AirPro News, we are closely monitoring the FAA’s response to this event, as it raises critical questions about the protocols governing ground support equipment and the technological limitations of current air traffic control infrastructure at major international hubs.
The Incident at LAX
Flight Details and Evasive Action
As detailed in the CBS News report, the Frontier Airlines flight was carrying 217 passengers and 7 crew members when the incident unfolded. The aircraft was taxiing at a relatively low speed of approximately 15 mph. This reduced velocity proved to be a critical factor, affording the flight crew the necessary reaction time to halt the aircraft before making contact with the crossing vehicles.
Air traffic control audio captured the immediate aftermath of the near-miss, highlighting the sudden nature of the encounter. The Frontier pilot reported the event to the tower, emphasizing the severity of the situation.
“We just had two trucks cut us off. We had to slam on the brakes to not hit them,” the pilot stated over the radio.
In a subsequent transmission, the pilot underscored the proximity of the vehicles, noting the need to check on the cabin crew following the sudden deceleration.
“It happened so fast. I have to go check on the flight attendants in the back. It was real close, closest I’ve ever seen.”
Following the event, Frontier Airlines issued a statement commending their flight crew. According to the airline’s public remarks, the pilots were praised for their “quick thinking” which successfully averted a potential disaster. Fortunately, no injuries were reported among the passengers or crew members on board.
Systemic Vulnerabilities and Ground Traffic
Blind Spots in the Control Tower
The investigation is expected to probe not only the actions of the truck drivers but also the structural limitations of LAX’s ground monitoring. Brian Sinclair, a former F-18 pilot and current instructor at the U.S. Naval Academy, provided expert analysis on the incident, pointing out significant visibility challenges at the airport.
According to Sinclair’s assessment, air traffic controllers may have missed the unfolding danger due to known infrastructural blind spots. Sinclair noted that there are three specific locations at LAX where tower personnel simply cannot see the taxiways, creating an inherent operational risk.
Right-of-Way on the Tarmac
The presence of ground vehicles near active aircraft is a routine aspect of airport operations, but strict protocols govern these interactions. CBS News Senior Transportation Correspondent Kris Van Cleave explained that while LAX maintains separate lanes for aircraft and ground vehicles, these paths inevitably cross.
Van Cleave emphasized that standard right-of-way rules must dictate these intersections to maintain safety.
“But, there are times when those lanes intersect, and the rules of the road still apply. You got to yield for the bigger vehicle,” Van Cleave explained.
As of the latest updates, LAX authorities have not publicly identified the truck drivers, their contracting employers, or the specific reasons why they breached the taxiway intersection at that exact moment.
A Climate of Heightened Scrutiny
Contrasting with the LaGuardia Tragedy
To fully understand the gravity of the FAA’s swift investigative response, this LAX incident must be viewed within the broader context of recent aviation emergencies. Just weeks earlier, on March 22, 2026, a fatal collision occurred at New York’s LaGuardia Airport, sending shockwaves through the aviation industry.
In the LaGuardia tragedy, an Air Canada Express CRJ-900 jet (Flight 8646) carrying 72 passengers and 4 crew members collided with a Port Authority fire truck on an active runway. The fire apparatus was responding to a separate emergency when it was struck by the landing aircraft. The catastrophic impact resulted in the deaths of the two pilots, Antoine Forest and Mackenzie Gunther, and left dozens of passengers and crew members injured.
While the LAX close call has triggered similar anxieties, experts are quick to draw sharp distinctions between the two events. The LAX aircraft was moving at a low taxiing speed of 15 mph, whereas the LaGuardia aircraft was touching down at high landing speeds. Furthermore, the nature of the ground vehicles differed significantly.
“It is not a circumstance like we saw in LaGuardia, where you had vehicles that were responding to an emergency,” Van Cleave noted, highlighting the differences in operational context.
AirPro News analysis
At AirPro News, we assess that the LAX taxiway incident, while non-fatal, exposes critical vulnerabilities in ground vehicle tracking and tower visibility at major U.S. airports. The revelation that LAX operates with three known blind spots where controllers cannot visually confirm taxiway traffic is a glaring operational gap. We anticipate that the FAA’s final report may mandate the installation of supplementary surface movement cameras or enhanced ground radar systems to cover these specific blind spots.
Furthermore, the lack of immediate public accountability regarding the truck drivers suggests a potential breakdown in contractor training or ground crew communication. As the aviation industry continues to reel from the fatal LaGuardia collision, regulatory bodies are likely to exhibit zero tolerance for ground incursions, even at low speeds. We expect this investigation to serve as a catalyst for a nationwide review of right-of-way protocols between commercial aircraft and third-party ground service vehicles.
Frequently Asked Questions (FAQ)
What happened at LAX involving a Frontier Airlines plane?
In early April 2026, a Frontier Airlines passenger jet carrying 217 passengers and 7 crew members had to brake abruptly on an LAX taxiway to avoid colliding with two ground trucks that cut across its path. The aircraft was traveling at approximately 15 mph at the time.
Were there any injuries reported in the LAX incident?
No. Thanks to the low speed of the aircraft and the quick reaction of the pilots, the plane stopped in time, and no injuries were reported among the passengers or crew.
Why is the FAA investigating this specific close call?
The FAA investigates all runway and taxiway incursions to ensure safety protocols are functioning. This incident is receiving particular attention due to known visibility blind spots from the LAX control tower and a heightened national focus on ground safety following a recent fatal collision at LaGuardia Airport.
How does the LAX incident differ from the recent LaGuardia crash?
The March 22, 2026, LaGuardia collision involved a landing aircraft striking an emergency fire truck at high speed, resulting in two pilot fatalities and numerous injuries. The LAX incident involved a plane taxiing at a low speed (15 mph) and non-emergency ground trucks, allowing the pilots enough time to stop safely without any resulting injuries.
Sources: CBS News
Photo Credit: Frontier Airlines
Regulations & Safety
EASA Grounds 5 Airbus A380s Over Wing Mid Spar Cracks
EASA Emergency AD 2026-0119-E mandates urgent wing inspections on 16 A380s, grounding five before next flight.
This is a developing story. Information may change as official details are released.
This is original reporting and analysis by AirPro News.
The European Union Aviation Safety Agency (EASA) has mandated urgent inspections of 16 Airbus A380 aircraft, requiring five of the superjumbos to be grounded before their next flight following the discovery of wing mid spar cracks.
Emergency Airworthiness Directive 2026-0119-E, issued on June 22, 2026, takes effect on June 24, 2026. The regulatory action primarily affects the United Arab Emirates-based carrier Emirates (EK), which operates 15 of the flagged airframes, alongside a single aircraft operated by Australia’s Qantas Airways (QF).
Regulatory requirements and compliance timelines
EASA has divided the affected Airbus A380 fleet into two compliance categories based on manufacturer serial numbers. Operators of the five aircraft designated as Group 1 must complete the mandated wing inspections before the aircraft’s next flight. The remaining 11 aircraft, classified as Group 2, must undergo inspections within 25 flight cycles.
The directive permits limited operational flexibility for repositioning. Operators may conduct ferry flights to move Group 1 aircraft to maintenance facilities, provided these flights do not exceed three flight cycles, carry no passengers, and do not utilize Extended Operations (ETOPS) procedures.
Regardless of the inspection findings, airlines are required to report all results back to Airbus within seven days of completing the checks.
Operator impact and structural concerns
The emergency directive places an immediate operational burden on Emirates, the world’s largest operator of the Airbus A380. With 15 aircraft requiring specialized structural checks, the carrier faces potential scheduling and fleet utilization disruptions.
Conversely, the single Qantas aircraft affected by the directive, registered as VH-OQI, is already undergoing scheduled heavy maintenance in Dresden, Germany. This positioning ensures the Australian flag carrier will avoid immediate flight schedule impacts.
The regulatory action stems from ongoing monitoring of the aircraft’s structural health. In the directive, EASA stated the safety rationale clearly.
Following the review of the results of those inspections, it has been determined that the cracks found on certain aeroplanes could reduce the structural integrity of the wing.
AirPro News analysis
We note that wing spar cracking remains a persistent maintenance challenge for the global Airbus A380 fleet as the airframes age. This latest emergency directive builds upon previous regulatory actions, including EASA AD 2025-0280, which established repetitive inspection protocols for wing middle and outer rear spars. The escalation to a before-next-flight grounding for five specific airframes indicates that fatigue data or recent inspection findings have exceeded the manufacturer’s predictive models for those specific serial numbers. We expect regulatory scrutiny of the A380’s wing structures to remain stringent as the active fleet continues to accumulate flight cycles.
Photo Credit: Airbus
Regulations & Safety
Southwest Airlines Aircraft Struck by Ground Vehicle at Memphis
A ground equipment vehicle hit a Southwest Airlines jet during boarding at Memphis Airport on June 21, 2026, causing a 4-hour delay.
This is a developing story. Information may change as official details are released.
This article summarizes reporting by Fox News Digital and WREG Memphis.
A ground equipment vehicle struck a Southwest Airlines aircraft during passenger boarding at Memphis International Airport (MEM) on June 21, 2026, forcing the carrier to remove the jet from service for safety inspections.
The incident resulted in no reported injuries among passengers or crew. According to reporting by Fox News Digital, travelers on Flight 4013 were accommodated on an alternate aircraft and reached their destination approximately four hours behind schedule.
Ramp incident and operational recovery
The collision occurred while passengers were actively boarding the aircraft. A Southwest Airlines spokesperson confirmed to Fox News Digital that a ground vehicle contacted the jet, prompting the airline to immediately pull the aircraft from the active schedule to undergo mandatory safety evaluations.
The Memphis Shelby County Airport Authority acknowledged the event, describing it in a statement as an isolated incident at the Tennessee facility. Following the collision, Southwest arranged for a replacement aircraft to complete the flight.
Reports indicate a discrepancy regarding the flight’s final destination. While a company representative told Fox News Digital the replacement flight was bound for Dallas, the airline’s website showed Flight 4013 continuing service to Harry Reid International Airport (LAS) in Las Vegas. The delayed flight ultimately arrived at approximately 5:30 p.m. local time, well past its original 1:50 p.m. scheduled arrival.
Safety investigations and industry context
Southwest Airlines stated that the collision will be reviewed through its internal Safety Management System. The carrier emphasized in a statement that customer and employee safety remains its highest priority. The Federal Aviation Administration (FAA) routinely monitors and may independently investigate ramp collisions involving commercial aircraft and ground support equipment.
Ground safety remains a persistent operational challenge at major commercial airports. Collisions involving baggage carts, catering trucks, and pushback tractors frequently result in costly aircraft damage and significant schedule disruptions, even when no injuries occur.
AirPro News analysis
We note that this ramp incident comes during a period of significant operational transition for Southwest Airlines. In 2026, the carrier is executing a major strategy reset, which includes the elimination of its legacy open-seating policy and the reduction of 11 international routes. While ground equipment collisions are generally isolated events managed by local station operations, any aircraft taken out of service out of base places immediate pressure on fleet utilization. The swift deployment of a replacement aircraft at MEM indicates the airline maintained sufficient operational slack to recover the flight, albeit with a four-hour delay.
Sources: Fox News Digital, WREG Memphis, MiGFlug
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
-
Defense & Military6 days agoVC-25B Bridge Aircraft Arrives at Joint Base Andrews
-
Regulations & Safety5 days agoNTSB Warns First Responders on Ballistic Parachute Hazards
-
Defense & Military2 days agoVolatus Aerospace Opens Mirabel Drone Manufacturing Facility
-
Defense & Military2 days agoItaly Courts Germany and Saudi Arabia to Join GCAP Fighter Program
-
Airlines Strategy6 days agoAlaska Airlines Promotes CFO Shane Tackett to President and CFO