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.
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.
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.
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.
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.
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.
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 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.
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.
Question: What caused the collision between the two Endeavor Air planes at LaGuardia? Question: Was anyone seriously injured in the incident? Question: What happens next in the NTSB’s investigation?
NTSB Releases Preliminary Findings on LaGuardia Ground Collision
A Factual Breakdown of the Collision
Air Traffic Control Communications and Crew Actions
Two Different Perspectives
The Aftermath and Investigation
Assessing the Damage and Human Impact
The Investigative Path Forward
Preliminary Findings and Future Implications
FAQ
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.
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.
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
NTSB Finds No Mechanical Failure in Bangor Challenger 600 Crash
NTSB preliminary report on the Bangor Bombardier Challenger 600 crash cites severe winter weather and deicing as key factors, no mechanical faults found.
This article is based on an official preliminary report from the National Transportation Safety Board (NTSB).
The National Transportation Safety Board (NTSB) has released its preliminary report regarding the fatal crash of a Bombardier CL-600-2B16 airplane that occurred on January 25, 2026, at Bangor International Airport (KBGR) in Maine. The accident resulted in the deaths of all six individuals on board, including two crew members and four passengers.
According to the NTSB’s findings, investigators have found no evidence of flight control malfunctions or mechanical failures that would have precluded normal operation. Instead, the investigation is increasingly focusing on environmental factors, specifically the severe winter weather conditions and the deicing procedures conducted minutes before the aircraft attempted to take off.
The aircraft, registered as N10KJ and operated by KTKJ Challenger LLC, was en route to Châlons Vatry Airport in France after a refueling stop in Bangor. The flight originated from William P. Hobby Airport in Houston, Texas.
Data recovered from the Flight Data Recorder (FDR) and Cockpit Voice Recorder (CVR) provides a detailed timeline of the aircraft’s final movements. The NTSB report indicates that the jet arrived at the runway threshold during a severe winter storm characterized by falling snow and freezing temperatures.
The preliminary report states that the aircraft underwent deicing treatment with both Type I and Type IV fluids at approximately 7:20 PM local time. Following the application of the fluid, the plane remained stationary for about five minutes before beginning its taxi to the runway.
Investigators noted that the CVR captured a critical conversation between the flight crew regarding “holdover times.” Holdover time refers to the estimated length of time deicing fluid remains effective in preventing the accumulation of ice or snow on critical aircraft surfaces. This discussion suggests the crew was aware of the deteriorating conditions and the time sensitivity of their departure.
The aircraft reached Runway 33 at 7:40 PM and received clearance for takeoff. According to FDR data, engine power was increased for takeoff at 7:43:57 PM. The aircraft lifted off the runway approximately 30 seconds later. However, the flight was brief. Moments after becoming airborne, the aircraft veered off the right side of the runway. It scraped the ground, flipped over, and came to rest inverted in a grassy safety area. The debris field stretched approximately 1,270 feet long and 150 feet wide, with the wreckage sustaining significant damage from a prolonged post-crash fire.
The NTSB’s on-site examination and data analysis have ruled out several potential causes, narrowing the scope of the ongoing investigation.
A key finding in the preliminary report is the status of the engines. The NTSB states:
Data from the Flight Data Recorder indicates that both engines were producing takeoff power and continued to gain power until the recording stopped.
Furthermore, investigators found no evidence of anomalies with the flight controls prior to the impact. The wings remained attached to the fuselage despite the severity of the crash, and the landing gear was found in the extended position.
At the time of the accident, visibility was reported as approximately three-quarters of a mile due to snow. The presence of freezing precipitation is a critical factor in the investigation, particularly regarding the effectiveness of the deicing fluid used.
While the NTSB report focuses on technical details, local authorities and media have identified the six victims of the tragedy. According to reporting by the Bangor Daily News and other local outlets, the victims include Shawna Collins, Nick Mastrascusa, Tara Arnold, Jacob Hosmer, Shelby Kuyawa, and Jorden Reidel. The aircraft was linked to the Houston-based law firm Arnold & Itkin.
The Bombardier Challenger 600 series has a documented history regarding wing contamination. Aviation safety databases note that this aircraft type has a “hard wing” design that can be sensitive to even small amounts of ice or frost, which can disrupt airflow and lead to a stall during takeoff.
Previous incidents, such as the 2004 crash in Montrose, Colorado, and the 2002 crash in Birmingham, England, involved similar circumstances where wing contamination was cited as a contributing factor. The NTSB’s final report, expected in 12 to 24 months, will likely determine if the severe weather in Bangor exceeded the capabilities of the deicing fluid or if the holdover time was exceeded. The focus on “holdover times” in the cockpit voice recorder transcript is a significant detail. In severe winter operations, the window between deicing and takeoff is often measured in minutes. If the intensity of the snowfall increases, the effective time of the anti-icing fluid decreases rapidly. The fact that the engines were producing power and no mechanical faults were found strongly suggests that aerodynamic performance was compromised, a hallmark of icing accidents. This investigation will likely serve as a critical reminder of the strict limitations of deicing fluids in active precipitation.
Sources: NTSB Preliminary Report, Bangor Daily News, FAA Registry
NTSB Preliminary Report: No Mechanical Failure Found in Bangor Challenger 600 Crash
Sequence of Events
Deicing and Taxi
Takeoff and Impact
Investigation Findings
Engine and Systems Performance
Weather Conditions
Victims and Context
Aircraft History and Icing Sensitivity
AirPro News Analysis
Sources
Photo Credit: NTSB
Regulations & Safety
United Airlines Plane Collides with Deicing Truck at Denver Airport
United Airlines Flight 605 collided with a deicing truck at Denver International Airport amid a snowstorm, injuring the truck driver and delaying flights.
This article summarizes reporting by 9News, Richard Cote, CBS News and social platform X.
A United Airlines aircraft collided with a deicing truck Friday morning at Denver International Airport (DIA), resulting in injuries to the truck’s driver and forcing passengers to deplane on the tarmac. The incident occurred amidst a severe March snowstorm that has disrupted travel across the region.
United Airlines Flight 605, a Boeing 737-800 scheduled to depart for Nashville, struck the vehicle while exiting the deicing pad. According to the Federal Aviation Administration (FAA), the collision took place in a section of the airfield not controlled by air traffic towers.
The Incident occurred at approximately 8:26 a.m. local time as the aircraft was preparing for departure. According to reporting by 9News, the flight had been scheduled to leave Denver at 7:59 a.m. but was delayed due to winter weather conditions. The FAA confirmed that the aircraft was moving out of the deicing area when it struck the truck.
United Airlines confirmed the accident in a statement, noting that the aircraft “made contact with ground equipment” during the operation. Following the collision, the 122 passengers and six crew members on board were evacuated from the aircraft via stairs and transported by bus back to the terminal. No injuries were reported among those on the plane.
While the passengers and crew remained unharmed, the operator of the deicing truck sustained injuries. According to a United Airlines spokesperson cited by the Denver Gazette, the driver, an employee of a contractor used by the airport, was taken to a hospital. The extent of the driver’s injuries has not been publicly disclosed.
The collision occurred during a significant winter storm affecting Colorado’s Front Range. The adverse weather conditions had already severely impacted operations at Denver International Airports before the ground accident took place.
According to flight tracking data, more than 600 flights were delayed and scores were canceled at the airport by Friday morning. United Airlines and Southwest Airlines were among the carriers most heavily affected by the snow and ice. The FAA stated it would investigate the collision, specifically noting that the crash happened in a non-movement area where pilots and ground vehicles are responsible for maintaining visual clearance. United Airlines stated they were working to rebook customers on alternative flights to Nashville. In a statement regarding the safety of the operation, the airline said:
“United flight 605 made contact with the equipment… [We are] cooperating with airport officials and federal investigators.”
Ground collisions in deicing areas are relatively rare but can occur during periods of low visibility and high congestion, such as winter storms. In these “non-movement” areas, air traffic control does not provide separation instructions, placing the burden of safety on pilots and ground vehicle operators. The Investigation will likely focus on communication protocols and visibility factors present during the heavy snowfall.
Was anyone injured in the accident? What caused the collision? What happened to the passengers?
Collision on the Deicing Pad
Driver Hospitalized
Weather Context and Operational Impact
AirPro News Analysis
Frequently Asked Questions
Yes, the driver of the deicing truck was injured and transported to a hospital. No passengers or crew members on the aircraft were hurt.
The specific cause is under investigation by the FAA. The collision occurred while the aircraft was exiting a deicing pad during heavy snow.
Passengers were deplaned using stairs on the tarmac and bused back to the terminal to be rebooked on other flights.
Sources
Photo Credit: CBS News
Regulations & Safety
Skyryse Launches Universal Emergency Autoland for Helicopters and Planes
Skyryse unveils Universal Emergency Autoland for fixed-wing and rotary aircraft, enhancing safety with automated landings starting 2026.
This article is based on an official press release from Skyryse.
In a significant development for general aviation safety, Skyryse has announced the introduction of a “Universal Emergency Autoland” feature for its SkyOSâ„¢ operating system. According to the company’s official announcement, this technology represents the world’s first emergency landing system designed to be aircraft-agnostic, capable of safely landing both fixed-wing airplanes and helicopters in the event of pilot incapacitation.
The new capability is designed to address a critical gap in current aviation safety technology. While automated landing systems like Garmin Autoland have existed for several years, they have been restricted to specific fixed-wing airframes. Skyryse states that their new system leverages the SkyOS platform to bring similar “panic button” safety to the vertical lift market, including helicopters which require complex stabilization and control inputs to land safely.
Skyryse has confirmed that the Universal Emergency Autoland feature will be a core component of SkyOS. The system is currently undergoing “for-credit” testing with the Federal Aviation Administration (FAA), with the first production aircraft, the Skyryse One, expected to begin shipping in 2026.
The core promise of the Skyryse system is simplicity for the passenger during a crisis. According to the company, the system can be activated in two ways: manually, via a single tap on a touchscreen by a passenger, or automatically, if the system detects pilot unresponsiveness or erratic flight behavior.
Once engaged, Skyryse describes a fully automated sequence of events designed to bring the aircraft and its occupants to safety:
Mark Groden, CEO of Skyryse, emphasized the user-centric design of the feature in the company’s announcement:
“If you have an incapacitated pilot, you’re probably going to be pretty stressed… It would be so much easier to have, basically, a shortcut button for the passenger to press, and then they can focus on other things.”
The distinction between fixed-wing and rotary-wing automation is substantial. Landing a helicopter requires active management of stability across all axes, a task that has historically made retrofitting autopilots difficult. Skyryse claims to solve this through a triply-redundant fly-by-wire system that replaces traditional mechanical linkages.
According to technical details released by Skyryse, the system utilizes “advanced sensor fusion,” combining data from radar, lidar, and cameras. This suite allows the aircraft to perceive its environment in real-time, ensuring that it does not attempt to land on obstacles, even if GPS data is slightly inaccurate. While Skyryse has previously demonstrated fully automated autorotations (unpowered landings), this new feature is specifically designed for powered emergency landings where the engine is operational but the pilot is unable to fly. The announcement positions Skyryse as a competitor to established players like Garmin, whose Autoland system is the current industry standard for turboprops and light jets. However, Garmin’s solution does not support helicopters. Other manufacturers, such as Leonardo, are developing similar capabilities for specific models like the AW169, but Skyryse aims to offer a universal retrofit solution applicable to a wide variety of airframes, starting with the Robinson R66-based Skyryse One.
The introduction of a universal autoland system for helicopters marks a potential paradigm shift in general aviation safety. Historically, high-end automation has been the domain of expensive business jets. By designing SkyOS as an “operating system” rather than a bespoke avionics suite, Skyryse is attempting to democratize safety features.
If successful, this technology could significantly reduce accident rates in the helicopter sector, which statistically faces higher risks than fixed-wing aviation. The ability to retrofit this technology onto older airframes could also revitalize the legacy fleet, offering owners a safety upgrade that was previously impossible without purchasing a brand-new aircraft. However, the success of this rollout hinges on the FAA certification process, which is notoriously rigorous for fly-by-wire systems in general aviation.
Skyryse has outlined a clear roadmap for the deployment of this technology. The company is currently pursuing a Supplemental Type Certificate (STC) for SkyOS. The first aircraft to feature the Universal Emergency Autoland will be the Skyryse One, a modernized version of the Robinson R66 helicopter.
According to the press release, the Skyryse One is expected to ship in 2026. The Universal Emergency Autoland capability is slated to be available at launch or shortly thereafter as a standard feature of the SkyOS platform.
The system is designed to be aircraft-agnostic, meaning it can be installed on both helicopters and fixed-wing airplanes. The first certified aircraft will be the Skyryse One (a modified Robinson R66).
Garmin Autoland is currently certified only for specific fixed-wing aircraft (like the Piper M600 and Cirrus Vision Jet). Skyryse’s solution is the first to support vertical-lift aircraft (helicopters) in addition to airplanes.
Skyryse expects the first production aircraft featuring this technology to begin shipping in 2026, pending FAA certification. Sources: Skyryse Press Release
Skyryse Unveils Universal Emergency Autoland for Helicopters and Fixed-Wing Aircraft
How Universal Emergency Autoland Works
Bridging the Helicopter Safety Gap
Technical Implementation
Comparison to Existing Solutions
AirPro News Analysis
Timeline and Availability
Frequently Asked Questions
What aircraft will support Skyryse Universal Emergency Autoland?
How is this different from Garmin Autoland?
When will this technology be available?
Photo Credit: Skyryse
-
Regulations & Safety6 days agoGreen Taxi Aerospace Gains FAA Approval for Electric Taxi System
-
Regulations & Safety5 days agoUnited Airlines Plane Collides with Deicing Truck at Denver Airport
-
Regulations & Safety4 days agoNTSB Finds No Mechanical Failure in Bangor Challenger 600 Crash
-
Aircraft Orders & Deliveries5 days agoBoeing 777-9 Vibration Testing Advances 2026 Certification Plans
-
Aircraft Orders & Deliveries4 days agoBoeing Nears 500-Jet Order from China Ahead of Trump-Xi Summit