Newark Liberty International Airport is a pressure cooker. If you've ever flown in or out of Jersey, you know the drill. It's crowded, it's loud, and the margins for error are razor-thin. Recently, those margins almost vanished when an Alaska Airlines jet and a FedEx cargo plane found themselves in a terrifying dance on the same runway.
The Federal Aviation Administration (FAA) is currently scrambling to figure out how a Boeing 737 operated by Alaska Airlines and a FedEx wide-body plane ended up sharing the same concrete. It wasn't a "close call" in the way a car almost clips your bumper in a parking lot. It was a high-speed, high-stakes lapse in coordination that could've ended in a catastrophic fireball. This isn't just a one-off mistake. It's a symptom of a crumbling air traffic control system that's being pushed past its breaking point.
The Seconds That Saved Hundreds of Lives
On the morning of the incident, Alaska Airlines Flight 158 was cleared for takeoff. At the same time, a FedEx plane was on its final approach to land on the very same runway. In the aviation world, this is the ultimate sin. You don't put a departing plane and a landing plane in the same space at the same time.
The FedEx pilots were the ones who noticed the conflict. They saw the Alaska jet sitting there or beginning its roll and realized the math didn't add up. They aborted their landing, executed a "go-around," and climbed back into the safety of the sky.
Imagine being a passenger on that Alaska flight. You're buckled in, phone in airplane mode, maybe thinking about your connection. You have no idea that thousands of pounds of FedEx cargo are screaming toward you from above. It's chilling. The National Transportation Safety Board (NTSB) has joined the FAA in this investigation because "near misses" like this are happening with an alarming frequency across the United States.
Why Newark is a Logistical Nightmare
Newark (EWR) isn't just another airport. It's part of the most complex airspace in the world, squeezed between JFK and LaGuardia. Controllers there have to juggle arrivals and departures from three major hubs while managing some of the most congested flight paths on the planet.
The problem isn't just the volume of flights. It's the staffing. We've heard for years that the FAA is short-handed. Controllers are working mandatory overtime, six-day weeks, and ten-hour shifts. When you're exhausted, your brain doesn't process spatial data as quickly. You miss a blip on the screen. You forget a tail number.
In this Newark incident, the focus will likely stay on the communication between the tower and the cockpits. Did the controller clear both planes simultaneously? Was there a misunderstanding of a "hold short" instruction? Or did the technology fail to alert the tower that the runway was occupied? Honestly, it's usually a mix of all three.
The Technology Gap Nobody Wants to Talk About
We're in 2026, yet much of our air traffic infrastructure feels stuck in the 1990s. While planes have advanced sensors, the ground-based systems responsible for preventing runway incursions—known as ASDE-X—don't always catch every movement in real-time.
These systems are designed to sound an alarm when two objects are on a collision course. But those alarms can sometimes be late. In several recent close calls at major U.S. airports, it was the pilots' eyes, not the tower's computers, that prevented a disaster. That's a terrifying reality. We rely on "see and avoid," which is basically the same tactic used by pilots in the 1940s.
The NTSB is Tired of Warning Us
Jennifer Homendy, the chair of the NTSB, hasn't been shy about her frustration. She's been shouting from the rooftops that the U.S. aviation system needs a massive tech overhaul and a hiring surge. The Newark incident is just the latest entry in a long list of "runway incursions" that have plagued the industry over the last two years.
We've seen similar scares in Austin, New York, and Burbank. In each case, the narrative is the same: a misunderstanding of instructions or a lack of situational awareness. The NTSB is going to pull the "black box" data from both planes. They'll listen to the tapes. They'll interview the controllers who were on duty.
But the truth is already staring us in the face. We're asking too much of an aging system. We're pushing more flights into the sky while the people on the ground are burnt out and the equipment is glitchy.
What You Can Do as a Passenger
You can't control the FAA. You can't fix the Newark tower. But you can change how you fly. If you're worried about safety, pay attention during taxiing and takeoff.
- Keep your seatbelt fastened until the gate. Many injuries in "go-around" situations happen because people think they're safe once the wheels almost touch the ground.
- Watch the windows. If something feels wrong—like a plane getting too close or an engine sound changing abruptly—trust your gut and stay braced.
- Support FAA funding. It sounds boring, but the only way to fix this is with money for better tech and more controllers.
The investigation into the Newark close call will take months. The final report will likely be hundreds of pages of technical jargon. But the takeaway for the rest of us is simple: we got lucky again. We shouldn't have to rely on luck to get from Newark to Seattle.
Check your flight status through the airline app rather than third-party trackers for the most accurate delay info following these types of investigations. If you're flying through EWR this week, expect extra scrutiny and potentially longer taxi times as the FAA likely implements "precautionary spacing" while the heat is on.
