The National Transportation Safety Board is investigating a close call between an Alaska Airlines Boeing 737 and a FedEx Boeing 777 at Newark Liberty International Airport. The incident occurred on the evening of Tuesday, March 17, 2026, when both aircraft were attempting to land on crossing runways. The event has drawn federal scrutiny to an airport already under pressure from recent construction, staffing constraints, and rising air traffic demands.
What Happened on Runway 4L and 22L
Alaska Airlines Flight 294, arriving from Seattle, overflew the FedEx cargo jet as both planes approached intersecting runways at Newark Liberty, according to the Associated Press. The Alaska Airlines aircraft was a Boeing 737; the FedEx plane was a Boeing 777. An air traffic controller issued instructions to both crews during the encounter, according to the Washington Post. No collision occurred, and neither aircraft reported damage, but the margin between routine operation and catastrophe was narrow enough to trigger a federal investigation.
The NTSB confirmed it is looking into the event. No preliminary findings or docket details have been released yet, and neither Alaska Airlines nor FedEx has issued public statements detailing pilot actions or onboard system alerts during the encounter. That information gap means the full sequence of decisions, from controller clearances to cockpit responses, is still unknown. Until the NTSB publishes its initial factual report, the precise vertical and lateral separation between the two jets cannot be stated with certainty.
Crossing Runways and the Risk They Carry
Newark’s runway layout includes intersecting paths, a configuration that demands precise sequencing by air traffic controllers. When two aircraft are cleared to land on runways that cross, timing errors measured in seconds can put planes on a collision course. The FAA distinguishes between runway incursions, where an aircraft or vehicle enters a runway without authorization, and airborne losses of separation, where spacing between planes in flight falls below required minimums. The Newark close call appears to involve the latter category, though the agency’s accident and incident database has not yet classified the March 17 event in its public datasets.
That distinction matters because it shapes the investigation’s scope and the safety recommendations that may follow. Runway incursions often point to ground-level communication breakdowns or signage failures. Airborne separation losses, by contrast, tend to implicate sequencing decisions, radar coverage, or controller workload. For passengers and cargo carriers alike, the practical consequence is the same: two large jets came too close together at one of the busiest airports on the East Coast.
Crossing runway operations are not inherently unsafe, but they leave less margin for error. Controllers must choreograph arrivals and departures so that no aircraft reaches the intersection at the wrong moment. That choreography depends on accurate speed control by pilots, reliable surveillance technology, and clear communication on crowded radio frequencies. When traffic levels rise or runway configurations change, the complexity of that task increases sharply.
Newark’s Operational Pressures
The close call lands at a moment when Newark has been managing overlapping operational constraints. The FAA has issued several public statements on Newark addressing capacity limits, runway construction timelines, and the need to balance demand with safety. Those statements have emphasized coordination with airlines and the Port Authority of New York and New Jersey as traffic patterns shift.
U.S. Transportation Secretary Sean P. Duffy recently marked the early completion of a major runway project at Newark, describing the work and its implications in a department briefing on the runway reopening. The project’s ahead-of-schedule finish was framed as a win for efficiency and passenger convenience, restoring capacity sooner than expected. At the same time, the department acknowledged ongoing telecommunications upgrades and staffing efforts involving the FAA and local partners.
The tension here deserves direct attention. Reopening a runway ahead of schedule boosts capacity, but it also reintroduces complexity into air traffic patterns at a facility where controllers are already stretched. Most public messaging has treated the early reopening as unqualified good news. That framing misses a real operational risk: when runway configurations change, controllers must adapt to new traffic flows, and the transition period can create momentary confusion. Whether that dynamic played any role on March 17 is unknown, but the coincidence of timing warrants scrutiny rather than assumption.
Nationally, the FAA has been under pressure to explain how it is managing a surge in demand with finite staffing and aging infrastructure. In broader agency statements, officials have highlighted investments in technology, controller training, and collaborative decision-making with airlines to maintain safety margins as traffic grows. The Newark incident will likely become a test case for whether those measures are keeping pace with real-world complexity at major hubs.
Newark’s History of Landing Incidents
Newark has a documented record of landing-related safety events involving cargo operations. In 1997, a Federal Express McDonnell Douglas MD-11 registered as N611FE crashed during landing at the airport. The NTSB’s investigation summary for that accident describes how the aircraft broke apart and caught fire after a hard landing and attempted go-around.
The full investigative docket for that case, designated DCA97MA055, is available through the NTSB’s online docket for the Newark crash. That material includes cockpit voice recorder transcripts, performance analyses, and the board’s final report. For researchers examining patterns over time, the agency’s broader docket search portal allows cross-comparison of Newark events with similar accidents and incidents elsewhere in the system.
The 1997 crash and the 2026 close call are different events with different causes, but they share a common thread: the difficulty of managing high-volume operations at an airport with a constrained physical footprint and crossing runway geometry. The NTSB’s safety recommendations from the earlier crash addressed approach procedures and go-around protocols, emphasizing the need for clear criteria and training when pilots must abandon a destabilized landing. Nearly three decades later, the question is whether the systemic conditions at Newark have evolved enough to match the volume of traffic the airport now handles.
NTSB’s Broader Focus on Near-Miss Events
The Newark investigation fits within a pattern of increased NTSB attention to aviation near-misses. In recent years, the board has warned that a string of close calls at major airports should be treated as leading indicators, not anomalies. Near-miss investigations are designed to uncover weak points in procedures, technology, and human factors before a catastrophic accident occurs.
In testimony and public remarks, NTSB leaders have stressed that runway safety is a system problem rather than a series of isolated errors. That system includes controller staffing levels, the ergonomics of radar displays, the reliability of surface detection equipment, and the clarity of standard operating procedures in both control towers and cockpits. When two large aircraft converge on crossing runways, any ambiguity in those elements can compress reaction time to seconds.
The Newark case will likely probe several recurring themes. Investigators are expected to examine how controllers sequenced the Alaska and FedEx flights, what separation standards applied to their approaches, and whether any automated alerts were generated in tower or terminal radar systems. They will also look at cockpit decision-making: how quickly pilots recognized the developing conflict, what guidance they had from onboard systems, and how they executed any instructions to adjust altitude or go around.
Another focus will be organizational learning. If the NTSB identifies contributing factors linked to procedures or equipment, it can issue safety recommendations to the FAA, airlines, or airport operators. Those recommendations are not binding, but they carry significant weight. In past runway-related cases, the board has urged changes such as revised approach spacing rules, enhanced controller training on complex runway configurations, and expanded use of surface movement radar and warning systems.
What Comes Next for Newark
For now, operations at Newark Liberty continue, and passengers are unlikely to notice visible changes while the investigation is in its early stages. Behind the scenes, however, the close call is almost certain to prompt internal reviews by the FAA, Alaska Airlines, FedEx, and the Port Authority. Those reviews may lead to interim steps, such as temporary adjustments to runway use during peak periods, even before the NTSB issues formal findings.
The outcome of the investigation will matter beyond a single night in March. Newark is a critical node in the national airspace system, and its ability to safely handle intersecting runway operations under heavy load has implications for schedules, airline networks, and public confidence. If investigators conclude that the system worked as designed and that separation was never compromised, the event may still reinforce the need for vigilance as traffic grows. If they find that the margin was unacceptably thin. Newark could become the catalyst for a new round of runway safety reforms across the country.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
