Alaska Airlines Flight 294 And Fedex Flight 721 In Deadly Radius: Disaster Averted As Passenger Jet Overflies Cargo Giant In Shocking Newark Near-Miss!
Image generated with AiImage Credit- Alaska Airlines
Hundreds of lives hung in the balance on a Tuesday evening at Newark Liberty International Airport when a Boeing 737 passenger jet and a massive Boeing 777 cargo freighter nearly collided over the tarmac. The Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) have launched a high-priority investigation into the March 17, 2026, incident, which saw Alaska Airlines Flight 294 overfly FedEx Flight 721 with a vertical separation of roughly 300 feet—a distance experts describe as a terrifyingly thin margin for error in commercial aviation.
Advertisement
Advertisement
Seconds from Catastrophe: The Newark Standoff
The harrowing event unfolded at approximately 8:17 p.m. as Newark’s complex web of intersecting runways became the stage for what could have been a historic aviation disaster. Alaska Airlines Flight 294, arriving from Portland, Oregon, was on its final descent to land. Simultaneously, FedEx Flight 721, a heavy Boeing 777 originating from Memphis, Tennessee, was also cleared to land on a runway that intersected the path of the Alaska jet.
According to preliminary data released by the NTSB and tracked via government-monitored radar, both aircraft had been given the green light to touch down. It was only at the final moment—when the Alaska Airlines Boeing 737 was a mere 150 feet above the ground—that an air traffic controller recognized the looming disaster and barked an emergency “go-around” instruction. The Alaska pilots reacted instantly, pulling the nose up and climbing directly over the FedEx jet that was already occupying the intersecting runway space below them.
Advertisement
Advertisement
Federal Watchdogs Demand Answers
The NTSB has officially opened a probe into the event, classifying it as a serious “overflight” incident. While both planes eventually landed safely—the FedEx crew completing their rollout and the Alaska pilots circling back for a successful second attempt—the narrowness of the miss has sent shockwaves through the Department of Transportation.
The FAA confirmed that the primary focus of the investigation centers on why both aircraft were cleared for intersecting paths simultaneously. In the hierarchy of aviation safety, the air traffic control tower acts as the ultimate safeguard; however, in this instance, that safeguard appears to have buckled under the pressure of Newark’s high-density traffic.
Advertisement
Advertisement
The Complexity of Intersecting Runway Operations
Newark Liberty is notorious among pilots for its challenging layout. Unlike airports with parallel runways that allow for independent streams of traffic, Newark relies on intersecting strips that require surgical precision from controllers. To maintain safety, every landing must be timed to a fraction of a minute to ensure that the “protected area” of one runway is clear before another aircraft crosses it.
Former federal safety officials have noted that the controller in charge of Alaska Airlines Flight 294 and FedEx Flight 721 may have waited too long to mitigate the closing distance between the two jets. When a go-around is ordered at 150 feet, the aircraft is essentially in its “landing flare,” a stage where engine response and lift must be instantaneous to avoid striking the ground or another vehicle.
A System Under Strain: Staffing and Fatigue
This near-collision does not exist in a vacuum. It comes during a period of intense scrutiny regarding the United States’ air traffic control infrastructure. Government reports from the FAA have repeatedly highlighted a chronic shortage of certified professional controllers. This staffing crisis has led to increased mandatory overtime, with many controllers working six-day weeks and ten-hour shifts.
The NTSB will likely examine the shift logs and fatigue levels of the personnel on duty at Newark that Tuesday night. The pressure to maintain “throughput”—the number of planes taking off and landing per hour—is immense at East Coast hubs, and experts fear that the push for efficiency is beginning to erode the traditional margins of safety that the U.S. aviation system is known for.
Corporate Responses and Pilot Precision
Alaska Airlines issued a statement affirming that while the incident was serious, their flight crew followed standard emergency procedures perfectly. The airline emphasized that “go-arounds” are a routine part of pilot training, designed precisely for moments when the runway environment becomes unsafe.
FedEx similarly confirmed that their crew followed all ATC instructions and was unaware of the proximity of the Alaska jet until the post-flight debrief. Both companies are cooperating fully with the NTSB, providing flight data recorder information and cockpit voice recordings to help investigators reconstruct the final seconds of the approach.
Advertisement
Advertisement
What Happens Next?
The NTSB investigation is expected to take several months to produce a preliminary report, with a final determination of “probable cause” potentially taking a year or more. Investigators will be looking at:
- ATC Audio Records: Reviewing the exact phrasing and timing of the clearances given to Alaska Airlines Flight 294 and FedEx Flight 721.
- Radar Geometry: Using ADS-B data to calculate the exact distance between the two hulls at the moment of overflight.
- Human Factors: Assessing whether visual obstructions or digital display errors contributed to the controller’s delayed reaction.
As the FAA works to modernize the NextGen air traffic system, this incident serves as a grim reminder that even with the most advanced technology, the human element remains the most critical link in the safety chain. For the passengers aboard Alaska 294, a routine flight ended in a heart-stopping climb, but for the aviation industry, it is a wake-up call that the skies over America are becoming increasingly crowded and dangerously complex.
Case Study: The Newark Intersecting Runway Near-Miss
Background
On the evening of March 17, 2026, a Boeing 737-9 (Alaska 294) and a Boeing 777F (FedEx 721) came within 300 vertical feet of a collision at Newark Liberty International Airport. Despite both aircraft being cleared to land on intersecting runways, a late “go-around” order by Air Traffic Control (ATC) forced the Alaska Airlines jet to overfly the FedEx freighter. This incident serves as a critical study in Human Factors, ATC Workload, and Airport Surface Management.
Incident Overview
- Date/Time: March 17, 2026 | 20:17 local time
- Location: Newark Liberty International Airport (EWR)
- Aircraft A: Alaska Airlines Flight 294 (Boeing 737-9) from Portland (PDX)
- Aircraft B: FedEx Flight 721 (Boeing 777F) from Memphis (MEM)
- Environment: High-density night operations; intersecting runway configuration.
Timeline of Events
- 20:12: Both aircraft are established on their respective final approaches. EWR was utilizing an intersecting runway configuration to manage heavy arrival flow.
- 20:15: ATC issues landing clearances to both flights. FedEx 721 is cleared for the primary arrival runway, while Alaska 294 is cleared for the intersecting strip.
- 20:16:45: Real-time telemetry indicates the “closure rate” between the two aircraft is exceeding safe separation parameters.
- 20:17:10: Alaska 294 is at an altitude of 150 feet AGL (Above Ground Level), seconds from touchdown.
- 20:17:15: The Tower Controller issues an urgent “Alaska 294, Go Around” instruction.
- 20:17:20: Alaska 294 initiates a maximum-thrust climb. Radar data confirms it overflies FedEx 721 with approximately 300–325 feet of vertical separation.
Critical Analysis & Root Causes
A. The “Late Call” Phenomenon
A primary focus of the NTSB investigation is the timing of the go-around. Expert analysis suggests the controller “waited too long” to rectify the converging paths. In intersecting operations, the Land and Hold Short Operations (LAHSO) or timed-separation protocols require a buffer that was seemingly ignored or miscalculated in this instance.
B. Systemic ATC Pressures
The incident occurred amid a documented national shortage of roughly 3,500 air traffic controllers. High-stress environments like Newark often require “complex sequencing” where the margin for error is measured in seconds. Fatigue and workload saturation are being investigated as contributing human factors.
C. Pilot Response and Procedure
The outcome of this case is a testament to pilot training. The Alaska Airlines crew executed a “balked landing” procedure at an extremely low altitude (150 ft), which involves transitioning the aircraft from a high-drag landing configuration to a high-performance climb in a matter of seconds.
Technical Data Comparison
| Parameter | Alaska 294 (B737) | FedEx 721 (B777) |
| Status at Conflict | Short Final (150ft) | Touchdown/Rollout |
| ATC Instruction | Emergency Go-Around | Continue Landing |
| Minimum Separation | ~300 Feet (Vertical) | N/A (Occupying Surface) |
| Recovery Action | TOGA (Takeoff/Go-Around) Power | Standard Braking |
Lessons Learned & Recommendations
- Enhanced Technology: The incident highlights the need for ASDE-X (Airport Surface Detection Equipment) enhancements that can predict intersecting path conflicts earlier in the approach phase.
- Operational Thresholds: Recommendations may include increasing the minimum altitude at which a “land-and-sequence” instruction can be adjusted for intersecting runways.
- Staffing Correlation: The NTSB is expected to use this case to further argue for federal investment in ATC hiring and the reduction of mandatory six-day work weeks to combat fatigue.
Advertisement
