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
Vehicle Crashes into Detroit Metro Airport Terminal Delta Check-In
A vehicle breached Detroit Metro Airport’s McNamara Terminal, causing minor injuries and minimal operational impact on Delta Air Lines flights.
This article summarizes reporting by ClickOnDetroit and Brandon Carr.
On the evening of Friday, January 23, 2026, a vehicle crashed through the glass entrance doors of the McNamara Terminal at Detroit Metropolitan Wayne County Airports (DTW), coming to a halt inside the Delta Air Lines baggage check-in area. The incident, which occurred during the evening rush, resulted in minor injuries but no fatalities.
According to reporting by ClickOnDetroit, the driver was taken into custody at the scene. While the situation created immediate chaos and scattered debris across the departures level, airport operations continued with minimal disruption.
The crash took place between 7:30 PM and 8:00 PM ET. Witnesses and local reports indicate that a blue four-door sedan, identified in verified reports as a Mercedes-Benz, breached the terminal’s exterior glass doors. The vehicle traveled into the check-in lobby before striking a ticket counter structure.
Video footage circulated on social media and reviewed by local outlets showed the sedan resting inside the terminal with both its hood and trunk popped open. The area surrounding the vehicle was covered in shattered glass and debris. Police immediately cordoned off the specific check-in zone with yellow tape.
According to witness accounts cited in local reports, the vehicle appeared to be moving at significant speed before impact. One witness, identified as “George” in reports, estimated the speed at approximately 45 mph just prior to the car entering the terminal.
Law enforcement officers from the Wayne County Airport Authority (WCAA) responded instantly to the crash. The driver, described as a male wearing a Detroit Lions jersey, surrendered to police without further incident. Video from the scene depicts the driver exiting the vehicle with his hands raised.
It is important to note that while other law enforcement incidents occurred in the region on the same evening, including a wrong-way driving incident on I-94 involving a suspect named Joel Masching, reports confirm these are separate events. The identity of the driver at the airport has not yet been released by the WCAA. Despite the severity of the crash and the busy time of day, no life-threatening injuries were reported. The WCAA Fire Department treated six individuals at the scene.
Airlines confirmed that its employees were among those assessed by first responders. In a statement regarding the safety of their staff and passengers, the airline noted:
“Three employees were among those checked by first responders.”
The airline further stated that there was no significant operational impact to flights. While the specific crash site was restricted for investigation and cleanup, the rest of the airport remained open, and there were no reports of mass evacuations or flight cancellations stemming directly from the vehicle incursion.
Perimeter Security and Infrastructure
This incident brings renewed attention to airport perimeter security, specifically the use of bollards, reinforced concrete or steel posts designed to prevent vehicles from ramming into pedestrian-heavy areas. While major U.S. airports, including Detroit Metro, utilize various physical barriers, the ability of a sedan to breach the glass doors suggests a potential gap in the physical defenses at that specific entry point.
Vehicle incursions into airport terminals are rare but have occurred historically. For example, a similar incident occurred at Los Angeles International Airport (LAX) in 2015. We anticipate that the Wayne County Airport Authority will likely conduct a review of curbside infrastructure to prevent similar occurrences in the future.
Was the airport closed due to the crash? Were there any fatalities? Is the incident related to other crimes in Detroit that night?
Incident Details and Timeline
The Scene Inside McNamara Terminal
Driver Taken into Custody
Injuries and Operational Impact
Delta Air Lines Statement
AirPro News Analysis
Frequently Asked Questions
No. The airport remained open, and Delta Air Lines reported no significant impact on flight operations. Only the immediate area of the crash was cordoned off.
No. Authorities reported no life-threatening injuries. Six people were treated at the scene, including three Delta employees.
Current reporting indicates this was an isolated incident. The driver is distinct from suspects involved in other local traffic incidents occurring around the same time.
Sources
Photo Credit: X
Regulations & Safety
House Committee Approves Bills to Support Aviation and Broadband Access
The House Committee advanced bipartisan bills to improve FAA staffing, protect U.S. assets abroad, and expand rural broadband in Appalachia.
This article is based on an official press release from The House Committee on Transportation and Infrastructure and legislative data from Congress.gov.
On January 21, 2026, the House Committee on Transportation and Infrastructure approved a slate of five bipartisan bills aimed at strengthening the U.S. aviation workforce, expanding rural broadband access, and protecting American assets abroad. Led by Chairman Sam Graves (R-MO) and Ranking Member Rick Larsen (D-WA), the markup session highlighted a legislative focus on modernizing Federal Aviation Administration (FAA) processes and responding to geopolitical challenges affecting U.S. supply chains.
The approved legislation addresses critical infrastructure needs, including the integration of military personnel into civilian air traffic control roles and the feasibility of using low-orbit satellite technology to bridge the digital divide in Appalachia. Additionally, the Committee moved to penalize foreign governments that illegally seize American-owned property, a measure with significant implications for maritime commerce.
“Today, the Committee approved legislation that modernizes the use of pilot certificates, strengthens rural broadband deployment, and protects American property abroad.”
, Chairman Sam Graves (R-MO)
Three of the five bills advanced during the session focus directly on aviation safety and efficiency. As the FAA continues to grapple with staffing shortages, the Committee approved H.R. 6744, the Military Air Traffic Control Transition Act. Sponsored by Rep. Laura Gillen (D-NY), this bill seeks to streamline the hiring process for military air traffic controllers transitioning into civilian roles within the FAA. By better recognizing military credentials, the legislation aims to create a faster pipeline to fill critical vacancies in the national airspace system.
The Committee also addressed the growing issue of unauthorized drones interfering with emergency response efforts. H.R. 6618, the Wildfire Aerial Response Safety Act, sponsored by Rep. Janelle Bynum (D-OR), mandates that the FAA study the impact of drone incursions on wildfire suppression. Unauthorized drones frequently ground aerial firefighting tankers due to safety risks; this bill requires an evaluation of counter-drone technologies to ensure airspace remains clear for first responders.
Additionally, the Committee moved to modernize pilot documentation with H.R. 2247, the Pilot Certificate Accessibility Act. Sponsored by Rep. Tim Burchett (R-TN), this legislation directs the FAA to update its systems to allow pilots to carry and present digital pilot certificates, moving away from an exclusive reliance on physical cards.
“The slate of bills advanced in today’s markup will improve air traffic control staffing, examine the increase in drone incursions during wildfire response, and explore opportunities to expand rural communities’ broadband access.”
, Ranking Member Rick Larsen (D-WA)
A significant portion of the markup was dedicated to protecting American commercial interests overseas. The Committee approved H.R. 7084, the Defending American Property Abroad Act of 2026, sponsored by Rep. August Pfluger (R-TX). This bill prohibits vessels from entering U.S. ports if they have previously utilized a foreign port or terminal that was illegally nationalized or expropriated from a U.S. entity.
According to legislative context provided by the research desk, this bill serves as a response to tensions regarding the seizure of U.S.-owned assets in Mexico, specifically the deep-water port and limestone quarry owned by Vulcan Materials Company. The legislation aims to economically isolate seized assets by effectively “blacklisting” vessels that utilize them, preventing those ships from participating in commercial shipping to the United States.
Addressing rural connectivity, the Committee advanced H.R. 2474, the Expanding Appalachia’s Broadband Access Act, sponsored by Rep. David Taylor (R-OH). This bill mandates the Government Accountability Office (GAO) to study the feasibility of incorporating low-orbit satellite technologies, such as Starlink or Kuiper, into broadband projects managed by the Appalachian Regional Commission (ARC).
The legislation acknowledges the economic and logistical challenges of laying traditional fiber-optic cables in rugged terrain. By exploring satellite alternatives, the bill pushes for a “technology-neutral” approach to closing the digital divide in hard-to-reach communities.
The approval of H.R. 6744 signals a pragmatic shift in how Congress views the FAA workforce crisis. Rather than relying solely on training new recruits from scratch, a process that takes years, legislators are prioritizing the removal of bureaucratic barriers for veterans who are already qualified. If enacted, this could provide immediate relief to understaffed control towers.
Furthermore, the advancement of H.R. 7084 represents an escalation in the use of maritime logistics as a tool of economic statecraft. By targeting the shipping vessels themselves, rather than just the foreign government, the U.S. is leveraging its status as a primary consumer market to deter the expropriation of American assets. This move suggests a hardening stance on protecting cross-border supply-chains from political interference.
Sources: House Committee on Transportation and Infrastructure, Congress.gov
House Committee Advances Aviation Workforce and Property Protection Measures
Modernizing Aviation Safety and Workforce
Defending U.S. Assets and Supply Chains
Bridging the Digital Divide in Appalachia
AirPro News Analysis
Photo Credit: Montage
Regulations & Safety
FAA Formalizes Permanent Airspace Restrictions at Reagan National Airport
FAA announces permanent airspace restrictions at Reagan National Airport effective January 2026 to enhance safety after a 2025 midair collision.
This article is based on an official press release from the Federal Aviation Administration.
U.S. Transportation Secretary Sean P. Duffy has announced the formalization of permanent airspace restrictions for aircraft operating near Ronald Reagan Washington National Airport (DCA). The Federal Aviation Administration (FAA) confirmed that these new regulations, which take effect on January 23, 2026, are designed to mitigate the risk of midair collisions in the congested airspace above the nation’s capital.
The regulatory changes come one year after a catastrophic midair collision involving a commercial airliner and a military helicopter near the airport. According to the FAA, the new rules codify temporary measures that were implemented immediately following the tragedy, ensuring that safety protocols regarding visual separation and helicopter routing are permanently enshrined in federal aviation regulations.
In an official statement, the Department of Transportation (DOT) emphasized that these measures reflect a commitment to modernizing safety infrastructure under the current administration. The rules specifically target the interaction between fixed-wing commercial traffic and rotorcraft, including helicopters and emerging powered-lift aircraft.
The Interim Final Rule, effective immediately, introduces several critical changes to how air traffic is managed in the Washington, D.C. metropolitan area. The primary focus of the regulation is to reduce the reliance on pilot visibility in complex airspace and to segregate different types of air traffic.
One of the most significant changes is the prohibition of “visual separation” procedures within five nautical miles of DCA. Historically, air traffic controllers could allow pilots to maintain safe distances from other aircraft by visually sighting them. Under the new rule, controllers must rely strictly on instrument-based separation standards in this zone, removing the potential for human error in visual identification.
The FAA has also permanently modified helicopter routes and zones. These changes are designed to shift rotorcraft traffic away from the flight paths utilized by commercial aircraft arriving at and departing from DCA, as well as nearby Dulles International (IAD) and Baltimore/Washington International (BWI). Additionally, the rule mandates that all military aircraft operating in the vicinity must broadcast their location data, ensuring they are visible to civilian air traffic control systems.
“After that horrific night in January, this Administration made a promise to do whatever it takes to secure the skies over our nation’s capital and ensure such a tragedy would never happen again. Today’s announcement reaffirms that commitment. The safety of the American people will always be our top priority.”
, Sean P. Duffy, U.S. Secretary of Transportation
These permanent restrictions are a direct response to the events of January 29, 2025, when American Airlines Flight 5342 collided with a U.S. Army Black Hawk helicopter over the Potomac River. The incident resulted in 67 fatalities and prompted an immediate review of airspace procedures in the region.
Following the crash, the National Transportation Safety Board (NTSB) identified insufficient separation and the risks associated with mixed-use airspace as contributing factors. The FAA initially responded with Temporary Flight Restrictions (TFRs) and updated procedures for the Pentagon Heliport. The announcement on January 22, 2026, transitions these temporary fixes into permanent federal law.
“We took decisive action immediately following the January 2025 midair collision to reduce risk in the airspace. This is a key step toward ensuring the highest level of safety for the traveling public.”
, Bryan Bedford, FAA Administrator
While the rules are effective immediately due to the urgent nature of the safety concerns, the FAA has categorized the regulation as an “Interim Final Rule.” This designation allows the agency to enforce the restrictions while simultaneously opening a public comment period, which will run until February 23, 2026.
The Department of Transportation framed the swift implementation of these rules as part of the “America First Agenda,” highlighting the administration’s focus on rapid infrastructure and safety modernization. The restrictions also impact general aviation, significantly curtailing non-essential helicopter and powered-lift operations, such as air tours and private transport, within designated sectors of the DC airspace.
FAA Formalizes Permanent Airspace Restrictions at Reagan National Airport
New Operational Restrictions and Requirements
Elimination of Visual Separation
Helicopter and Military Aircraft Protocols
Context: The January 2025 Tragedy
Implementation and Public Comment
Sources
Photo Credit: Carolyn Kaster/AP
-
MRO & Manufacturing2 days agoAirbus Starts Serial Production of Large Titanium 3D-Printed A350 Parts
-
Commercial Aviation6 days agoUnited Airlines Stores Boeing 777s Over Engine Parts Shortage
-
Commercial Aviation5 days agoQantas Fleet Renewal and Cabin Upgrades for Western Australia
-
Commercial Space7 days agoSingapore Airshow 2026 Launches Space Summit and New Features
-
Commercial Aviation5 days agoUnited Airlines Flight UA2323 Disabled After Hard Landing in Orlando