Regulations & Safety
NTSB Preliminary Report on Endeavor Air Ground Collision at LaGuardia
NTSB releases preliminary findings on Endeavor Air’s ground collision at LaGuardia Airport, highlighting communication and human factors.

NTSB Releases Preliminary Findings on LaGuardia Ground Collision
In the world of commercial aviation, safety is the paramount objective, built upon layers of procedure, technology, and human performance. When incidents occur, they are scrutinized to reinforce and improve this system. On October 1, 2025, an event at New York’s LaGuardia Airport (LGA) put this process into motion when two Endeavor Air aircraft, operating as Delta Connection, collided on the ground. The incident, while resulting in only one minor injury, triggered a full-scale investigation by the National Transportation Safety Board (NTSB).
The collision involved Endeavor Air flight 5155, a Bombardier CRJ-900 preparing for departure to Roanoke, and Endeavor Air flight 5047, another CRJ-900 that had just arrived from Charlotte. The event occurred at a low speed at the intersection of taxiways M and A. While ground incidents are not uncommon, a collision between two Commercial-Aircraft resulting in substantial damage warrants a thorough and transparent investigation. The NTSB’s role is not to assign blame but to meticulously uncover the factual sequence of events and determine a probable cause to prevent future occurrences.
The agency recently released its preliminary report, offering the first official, fact-based look into the circumstances surrounding the collision. This report is a critical first step, compiling data from flight recorders, air traffic control communications, airport surveillance, and crew interviews. It provides a timeline and a factual basis for the ongoing investigation, allowing us to break down the known elements of the incident while the NTSB continues its comprehensive analysis.
A Factual Breakdown of the Collision
The NTSB’s preliminary report provides a clear, moment-by-moment account of the events leading up to the collision. By examining air traffic control (ATC) transcripts and data from the aircraft, we can reconstruct the timeline and understand the instructions given to each flight crew. The clarity of these communications is a focal point of the investigation.
Air Traffic Control Communications and Crew Actions
According to the report, at 9:54:23 PM Eastern Daylight Time, the ground controller at LaGuardia instructed the crew of flight 5047 (the arriving aircraft) to taxi to their gate via taxiway B to taxiway M. The flight crew correctly read back these instructions, indicating a clear understanding of their cleared path. This part of the sequence appears routine and without any ambiguity.
Just over a minute later, at 9:55:37 PM, the same ground controller issued taxi instructions to flight 5155 (the departing aircraft). The clearance was to taxi to runway 13 via taxiways A to E and to hold short of runway 4. Critically, the instruction included the directive to “give way to another Endeavor Air airplane at taxiway M.” At 9:55:41 PM, the crew of flight 5155 read back the controller’s instructions. The collision occurred approximately one minute later, at 9:56:40 PM.
The investigation’s focus sharpens on the period between the readback and the impact. Airports surveillance video captured the event, showing flight 5047 turning onto taxiway M and coming to an abrupt stop as it neared the intersection with taxiway A. Approximately two seconds later, the right wing of the eastbound flight 5155 struck the nose of the stationary flight 5047.
Two Different Perspectives
Interviews with the flight crews provide crucial, albeit differing, perspectives. The crew of the arriving flight, 5047, stated their taxi was normal. The captain reported seeing the other aircraft approaching from his left and brought his plane to a stop. A few seconds later, their aircraft was struck. Their account aligns with the sequence of events captured by airport surveillance footage.
The account from the flight deck of the departing flight, 5155, is more complex. The first officer told investigators he recalled hearing the full taxi clearance and did not find it confusing. However, the captain’s recollection was different. He recalled the instruction to taxi and hold short of runway 4 but stated he did not recall hearing the specific instruction to “give way” to the other aircraft at taxiway M.
The captain [of flight 5155] stated he was focused on calculating performance numbers for landing at the destination airport. He saw flight 5047 to the right, attempted to veer left, and applied the brakes immediately before the collision.
This discrepancy in recollection is a central point in the preliminary report. Human factors, including cockpit workload and situational awareness, will likely be a significant area of focus as the NTSB continues its analysis. The data from the Cockpit Voice Recorders (CVR) and Flight Data Recorders (FDR) from both aircraft were successfully recovered and will be instrumental in building a complete picture of the actions and conversations inside each cockpit.
The Aftermath and Investigation
In the immediate aftermath of the collision, the priority was the safety of the 93 passengers and crew members across both aircraft. Emergency protocols were activated, and while the incident was low-speed, the damage to the multi-million dollar aircraft was significant. The subsequent investigation now involves a methodical process of evidence collection and analysis by the NTSB and other involved parties.
Assessing the Damage and Human Impact
The NTSB classified the damage to both aircraft as “substantial.” Flight 5155, with registration N902XJ, sustained heavy damage to its right wing. The report specifies that the outboard slat, the aileron, and the wing tip separated from the aircraft. Flight 5047, registration N480PX, incurred major damage to its nose and the captain’s windshield, which was directly impacted by the other plane’s wing.
Fortunately, the human cost was minimal. A single flight attendant aboard flight 5155 reported a minor injury and was transported to a hospital for evaluation. No other injuries were reported among any of the passengers or crew. Passengers from both flights were deplaned on the taxiway and transported by bus back to the terminal, a standard procedure to ensure safety after such an event.
The weather at the time of the incident was not a factor. The meteorological report for LaGuardia indicated clear skies and visibility of 10 statute miles, ensuring that visual conditions were optimal for ground operations.
The Investigative Path Forward
The NTSB’s investigation is a collaborative effort. The agency is leading the inquiry, with participation from several other organizations, including the FAA, the aircraft operator Endeavor Air, the Air Line Pilots Association (ALPA), and the National Air Traffic Controllers Association (NATCA). This multi-party approach ensures that expertise from all facets of the operation,piloting, air traffic control, and airline procedures,is brought to bear on the investigation.
The preliminary report is just the first public document in a process that can take 12 to 24 months to complete. Investigators will continue to synchronize the data from the flight recorders with ATC transcripts and surveillance video. They will conduct further interviews and analyze airline training protocols, airport signage, and any other factors that could have contributed to the incident.
The ultimate goal is to produce a final report that not only identifies a probable cause but also issues safety recommendations aimed at preventing a recurrence. These recommendations can influence everything from pilot training and ATC phraseology to airport taxiway design. Every incident is treated as a learning opportunity to further strengthen the safety of the national airspace system.
Preliminary Findings and Future Implications
The NTSB’s preliminary report on the LaGuardia ground collision successfully establishes a baseline of facts. It confirms that a clear instruction to “give way” was issued by air traffic control and read back by the departing flight’s crew. It also documents the captain’s lack of recollection of this critical command, highlighting a potential breakdown in situational awareness. The report meticulously details the physical damage and confirms the fortunate absence of serious injuries.
As the investigation moves forward, the focus will shift from “what happened” to “why it happened.” The final analysis will delve deeper into human factors, cockpit resource management, and operational pressures. The findings could have broad implications, potentially leading to new recommendations for training on high-workload phases of flight, even during ground operations. For now, the report stands as a testament to a transparent and methodical investigative process designed to ensure that every flight is a safe one.
FAQ
Question: What caused the collision between the two Endeavor Air planes at LaGuardia?
Answer: The NTSB has not yet determined a probable cause. The preliminary report is a statement of facts collected so far. It notes that air traffic control instructed the departing aircraft (flight 5155) to “give way” to the arriving aircraft (flight 5047), but a collision still occurred. The full investigation is ongoing.
Question: Was anyone seriously injured in the incident?
Answer: No. According to the NTSB, one flight attendant sustained minor injuries. There were no reported injuries to any of the passengers or other crew members on either aircraft.
Question: What happens next in the NTSB’s investigation?
Answer: The NTSB will continue to analyze all evidence, including the cockpit voice and flight data recorders, surveillance video, and interviews. This process typically takes 12 to 24 months. A final report will eventually be published, which will include an official probable cause and may contain safety recommendations to prevent similar incidents.
Sources
Photo Credit: NTSB
Regulations & Safety
Rio de Janeiro Mid-Air Helicopter Collision Kills Six
Two helicopters collided over Rio de Janeiro on June 14, 2026, killing six and triggering an EV battery fire. CENIPA is investigating.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by CNN Brasil.
Six people sustained fatal injuries on June 14, 2026, following a mid-air collision between two helicopters over the West Zone of Rio de Janeiro, Brazil. The deceased include American entertainer Oliver Tree Nickel and five other occupants across both aircraft.
The accident involved a Bell 206B JetRanger III and an Airbus AS350 B2. Following the airborne collision, the wreckage descended into an electric vehicle parking lot, triggering a complex post-crash fire involving multiple lithium-ion vehicle batteries. The Brazilian Aeronautical Accidents Investigation and Prevention Center (CENIPA) has opened an investigation into the sequence of events.
Aircraft and flight details
According to the National Civil Aviation Agency (ANAC), both helicopters maintained regular registration status at the time of the accident. The Bell 206B JetRanger III, registered as PP-MAC, was operated by Turfik Comércio de Frutas Ltda and carried a single occupant. The Airbus AS350 B2, registered as PR-DJJ, carried five occupants.
The Military Fire Department of the State of Rio de Janeiro (CBMERJ) received the initial emergency call at 08:59 local time. The collision occurred over the Recreio dos Bandeirantes neighborhood, specifically near Avenida das Américas.
Ground impact and secondary fire hazards
The wreckage from the mid-air collision impacted a BYD car dealership lot. CNN Brasil reported that the impact and subsequent fuel ignition destroyed approximately 20 electric vehicles parked at the facility.
The presence of electric vehicles introduced severe secondary hazards for first responders. CBMERJ spokesperson Fábio Contreiras detailed the challenges faced by fire crews on the scene.
“The fire in lithium batteries causes very high energy. It is a much more aggressive fire than a common fire,” Contreiras stated.
Victim identification and background
The Civil Police of the State of Rio de Janeiro (PCERJ) officially confirmed the identities of the six victims. In addition to Oliver Tree Nickel, the deceased include Argentine content creator Gaspar Prim DÃaz, Argentine video director Lucas Vignale, Brazilian music producer Lucas Brito Chaves, and pilots Alexandre Souza and Charles Marsillac.
Oliver Tree had recently performed in Buenos Aires, Argentina, on June 4, 2026, and in São Paulo, Brazil, on June 6, 2026, as part of an international tour.
Rio de Janeiro Mayor Eduardo Cavaliere addressed the loss of the flight crew in a public statement.
“I knew one of the pilots personally. They were 2 experienced pilots, with many flight hours, with a long career. It was a fatality, a tragedy,” Cavaliere said.
AirPro News analysis
While CENIPA will determine the factors leading to the mid-air collision, the ground phase of this accident highlights an emerging challenge for municipal emergency services. As electric aviation vehicle adoption increases, the probability of aviation accidents intersecting with high-density lithium-ion battery storage also rises. We anticipate that safety regulators and Aircraft Rescue and Firefighting (ARFF) organizations will need to update urban crash response protocols to account for the thermal runaway risks and specialized extinguishing requirements associated with large-scale EV battery fires.
Sources: CNN Brasil
Photo Credit: Ricardo Moraes – Reuters
Regulations & Safety
Missouri Skydive Plane Crash Kills 12 at Butler Airport
A Pacific Aerospace 750XL crashed after takeoff from Butler Memorial Airport on June 14, 2026, killing a pilot and 11 skydivers.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by CBS News, The Washington Post, SFGATE, KEYT, and Fox 10 Phoenix.
A Pacific Aerospace 750XL operated by Skydive Kansas City crashed shortly after takeoff from Butler Memorial Airport (BUM) on June 14, 2026, resulting in 12 fatalities.
The Missouri State Highway Patrol confirmed that the pilot and 11 skydivers died when the single-engine turboprop impacted a field adjacent to the airport and caught fire. The NTSB and the FAA have deployed investigators to the site, located approximately 65 miles south of Kansas City.
Accident sequence and emergency response
The aircraft departed BUM at approximately 11:20 a.m. local time. According to preliminary reports cited by SFGATE, the aircraft made a left turn shortly after takeoff. Emergency responders received a 911 call around 11:30 a.m. reporting that the aircraft had crashed into a field approximately 300 yards from the runway and was engulfed in flames.
Dennis Jacobs, acting airport manager and Bates County Emergency Management Agency director, told reporters that the aircraft appeared to lose power before stalling and impacting the ground nose first. The NTSB has not yet verified this sequence of events, and the official cause of the accident remains under investigation.
The Missouri State Highway Patrol, alongside the Butler Police Department and Bates County Sheriff’s Office, secured the scene. A statement from the highway patrol confirmed that all 12 occupants perished in the crash. The identities of the victims are being withheld pending family notification.
Aircraft and operator background
The aircraft involved was a Pacific Aerospace 750XL manufactured in 2010. The 750XL is a single-engine turboprop frequently utilized in commercial skydiving operations due to its climb rate and payload capacity. The flight was operated by Skydive Kansas City, a commercial skydiving center based at BUM.
This accident follows a previous skydiving-related aviation occurrence near the same airport. On May 25, 2024, a Cessna U206C experienced an in-flight emergency near BUM. In that incident, the pilot and six skydivers successfully evacuated the aircraft via parachute before it crashed into a hayfield, resulting in no fatalities.
AirPro News analysis
We note that the NTSB investigation will likely focus on engine performance, weight and balance, and environmental factors at the time of departure. The Pacific Aerospace 750XL is a specialized utility aircraft, and investigators will examine maintenance records and the operator’s procedures as part of their standard protocol. Until the NTSB releases its preliminary report, usually within 30 days, any statements regarding a loss of power remain unconfirmed eyewitness observations.
Sources: CBS News
Photo Credit: NZAero
Regulations & Safety
FAA Investigates Southwest Airlines Near Miss at Nashville
Two Southwest Boeing 737s came within 500 vertical feet near Nashville on April 18, 2026, after an ATC error during a go-around.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by CNN, Fox News, and The Washington Post.
Two Southwest Airlines (WN) Boeing 737 aircraft passed within 500 vertical feet of each other near Nashville International Airport (BNA) on April 18, 2026, after air traffic control instructions placed an aborting arrival into the path of a departing flight.
The incident, which occurred at approximately 5:30 p.m. local time, prompted both flight crews to execute evasive maneuvers following onboard Traffic Collision Avoidance System (TCAS) alerts. The Federal Aviation Administration (FAA) has launched an investigation into the airspace separation loss, which highlights ongoing scrutiny over air traffic control protocols and collision avoidance effectiveness.
Sequence of events and evasive maneuvers
According to statements provided to CNN and Fox News, Southwest Airlines Flight 507 was arriving from Myrtle Beach, South Carolina, when the flight crew initiated a precautionary go-around due to gusty wind conditions at BNA. During this maneuver, air traffic controllers instructed the crew to turn right.
The FAA confirmed in a statement that these instructions placed Flight 507 directly into the departure path of Southwest Airlines Flight 1152, which was taking off from a parallel runway bound for Knoxville, Tennessee. As the aircraft converged, TCAS resolution advisories activated in both cockpits. Flight tracking data from Flightradar24 indicates the two Boeing 737s came within 500 vertical feet of one another before the crews successfully altered their trajectories.
Both aircraft continued to safe landings without further incident. Flight 507 completed its arrival into Nashville on a subsequent approach, while Flight 1152 proceeded to its destination in Knoxville.
Regulatory investigation and safety context
The FAA is currently investigating the circumstances that led to the loss of separation. Southwest Airlines issued a statement emphasizing that the pilots of Flight 507 were complying with air traffic control directives when the conflict occurred, and that the crews responded professionally to the onboard traffic alerts to maintain safety.
The Nashville incident occurs against a backdrop of heightened national attention on mid-air collision risks. The Washington Post notes that aviation safety systems have faced intense public and regulatory scrutiny following a January 29, 2025, collision between an American Airlines aircraft and a military helicopter near Washington, D.C., which resulted in 67 fatalities. While the circumstances of the two events differ, the 2025 accident has amplified focus on the reliability of TCAS and air traffic control coordination in congested airspace.
AirPro News analysis
The activation of TCAS resolution advisories in this incident demonstrates the critical role of automated safety nets when procedural separation fails. While the FAA investigation will ultimately determine the root cause of the controller instructions, the event underscores the vulnerability of the go-around phase. Go-arounds are dynamic maneuvers that rapidly alter an aircraft’s energy state and expected flight path. These maneuvers require immediate and precise coordination between the flight deck and air traffic control, particularly when parallel runway operations are active.
Sources: CNN (via KESQ)
Photo Credit: Flightradar24 – Google Earth via CNN Newsource
-
Defense & Military5 days agoBoeing Withdraws T-7A Red Hawk from Navy UJTS Competition
-
Regulations & Safety3 days agoMissouri Skydive Plane Crash Kills 12 at Butler Airport
-
Commercial Aviation6 days agoAirbus A350-1000ULR EASA Certification Campaign Begins
-
Regulations & Safety6 days agoTurkish Airlines 777-300ER Wing Strike at Antalya Airport
-
Defense & Military5 days agoB-21 Raider Operational and Developmental Test Pilots Fly Together
