Two jets reportedly came within a few hundred feet of each other over one of America’s busiest airports—an alarming reminder that when government-run systems slip, everyday families pay the price.
Story Snapshot
- An Alaska Airlines Boeing 737 and a FedEx Boeing 777 cargo jet experienced a near-miss while approaching intersecting runways at Newark Liberty International Airport on March 18, 2026.
- Radar-based reporting indicated the aircraft passed within roughly 300–325 feet of each other before controllers intervened.
- Air traffic control instructed Alaska Airlines Flight 294 to execute a go-around; both aircraft later landed safely and no injuries were reported.
- The FAA and NTSB opened investigations, focusing on timing, sequencing, and procedures used during high-volume evening operations.
Near-Miss Over Newark Raises Fresh Questions About Airspace Reliability
Newark Liberty International Airport in New Jersey became the focus of federal investigators after a close call involving Alaska Airlines Flight 294, a Boeing 737 arriving from Portland, and FedEx Flight 721, a Boeing 777 cargo aircraft arriving from Memphis. The incident unfolded Tuesday night, March 18, 2026, around 8:15–8:17 p.m., as both aircraft approached intersecting runways. Reported radar analysis put the separation at about 300–325 feet before corrective action prevented contact.
According to publicly reported statements, an air traffic controller directed Alaska’s aircraft to perform a go-around while FedEx continued its approach to the intersecting runway. Alaska said its pilots are trained for go-arounds, and FedEx said its crew followed air traffic control instructions and landed safely. No damage or injuries were reported, but the scenario underscores how quickly routine operations can turn hazardous when timing and coordination at a high-density airport are even slightly off.
What the FAA and NTSB Are Investigating—and What We Still Don’t Know
The Federal Aviation Administration and the National Transportation Safety Board confirmed they are investigating, and that matters because these reviews can reveal whether a problem was a one-off breakdown or a symptom of deeper strain in the system. Reports indicate the go-around instruction came when the Alaska jet was very low—around 150 feet altitude—leaving little margin for error. The preliminary stage of an investigation typically focuses on controller sequencing, communications, and whether procedures were followed.
At this point, the public does not have final findings on causation, and the existing reporting does not establish intentional wrongdoing or a definitive controller error. What is clear is the underlying environment: Newark is a complex airport with intersecting runways designed to move a lot of traffic through tight airspace. That configuration can be efficient on paper, but it demands precision in real time—especially during evening arrival banks when multiple aircraft are converging and small delays can cascade.
Intersecting Runways, High Volume, and a System With Little Room for Mistakes
Newark’s layout is often described as inherently challenging because intersecting runways require careful timing to ensure two aircraft are never in conflict at the wrong moment. One expert perspective highlighted in reporting described the tower controller’s job as trying to get “that timing perfect,” acknowledging it “doesn’t always work.” That assessment frames the close call as an operational stress test: when traffic is heavy, the system relies on training, procedures, and quick decisions to maintain safe separation.
For travelers—especially families and older Americans who remember when competence and safety margins were treated as non-negotiable—this story lands differently. Aviation safety is not a culture-war issue, but it is a governance issue: the federal government oversees air traffic control, sets standards, and manages staffing and modernization. When Washington prioritizes trendy politics or bloated bureaucracy over core services, the public is left wondering whether the basics—safe skies and predictable operations—are being protected with the seriousness they deserve.
Why This Incident Matters Beyond Newark—and What Should Happen Next
The incident also occurred on a day when Newark saw another, separate aircraft incident earlier involving a collision at the gate during pushback operations, underscoring the operational pressures at the airport. The near-miss in the air is a different category of risk, but two incidents in one day naturally raise concerns about congestion, workload, and process discipline. Investigators may ultimately recommend procedural tweaks, additional training, or operational changes to reduce conflict risk on intersecting runway operations.
Until the FAA and NTSB complete their work, the responsible takeaway is caution without panic: the safety system did function in the sense that controllers issued a go-around and both crews complied, preventing a tragedy. Still, near-misses are warnings, not victories. The public should expect transparent findings and practical fixes that prioritize safety and competence over excuses, because Americans shouldn’t need blind faith to trust that the nation’s airspace is being managed with the discipline it demands.
Sources:
Planes Collide Newark Airport Tuesday
Close call between planes at Newark airport
