Passenger jet had to abort takeoff to avoid runway collision at New York's LaGuardia Airport
When a passenger jet roaring down the runway toward takeoff at New York's LaGuardia Airport had to slam on the brakes earlier this month because another plane was still on the runway, Renee Hoffer and all the other passengers were thrown forward in their seats.
Hoffer wound up in the emergency room the next day after the near miss on May 6 because her neck started hurting and her left arm went numb.
'The stop was as hard as any car accident I've been in,' Hoffer said.
Both the Federal Aviation Administration and the National Transportation Safety Board said Monday that they are investigating the incident in which a Republic Airways jet had to abort takeoff and slam to a stop because a United Airlines plane was still taxiing across the runway. The close call happened despite the airport being equipped with an advanced surface radar system that's designed to help prevent such close calls.
In audio from the tower that ABC obtained from the website www.LiveATC.net, the air traffic controller said to the pilot of the Republic Airways jet: 'Sorry, I thought United had cleared well before that.'
At the time that controller was directing the Republic Airways jet to takeoff, a ground controller on a different radio frequency was directing the United plane to a new taxiway after it missed the first one it was supposed to use to exit the runway.
When the passengers got off the plane after the close call at 12:35 a.m., Hoffer said the gate agents refused to even give them hotel vouchers for the night because they blamed the weather even though another passenger said she had an app on her phone that showed another plane was on the runway.
Hoffer said she's been stuck in a customer service nightmare since the flight Republic was operating for American Airlines ended abruptly. She said neither the airline nor the FAA has answered her complaints while she continues to nurse the pinched nerve in her neck that the ER doctors identified.
Both the airlines and the airport referred questions to the FAA.
The number of close calls in recent years has created serious concerns for the FAA, NTSB and other safety experts. The NTSB's investigation of a February 2023 close call in Austin highlighted the concerns, but there have been a number of other high-profile near misses. In one case, a Southwest Airlines jet coming in for a landing in Chicago narrowly avoided smashing into a business jet crossing the runway.
LaGuardia is one of just 35 airports across the country equipped with the FAA's best technology to prevent such runway incursions. The ASDS-X system uses a variety of technology to help controllers track planes and vehicles on the ground. At the other 490 U.S. airports with a control tower, air traffic controllers have to rely on more low-tech tools like a pair of binoculars to keep track of aircraft on the ground because the systems are expensive.
Expanding the systems to more airports is something Transportation Secretary Sean Duffy would like to do if Congress signs off on his multi-billion-dollar plan to overhaul the nation's aging air traffic control system.
But it's clear the technology is not perfect because close calls continue happening. The FAA is taking a number of additional steps to try to reduce the number of close calls, and it plans to install an additional warning system at LaGuardia in the future.
But the rate of runway incursions per 1 million takeoffs and landings has remained around 30 for a decade. The rate got as high as 35 in 2017 and 2018. But generally there are fewer than 20 of the most serious kind of incursions where a collision was narrowly avoided or there was a significant potential for a crash, according to the FAA. That number did hit 22 in 2023 but fell to just 7 last year.
To help, there are efforts to develop a system that will warn pilots directly about traffic on a runway instead of alerting the controller and relying on them to relay the warning. That could save precious seconds. But the FAA has not yet certified a system to warn pilots directly that Honeywell International has been developing for years.
The worst accident in aviation history occurred in 1977 on the Spanish island of Tenerife, when a KLM 747 began its takeoff roll while a Pan Am 747 was still on the runway; 583 people died when the planes collided in thick fog.
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Daily Mail
15 hours ago
- Daily Mail
Grade-school math sum leaves people scratching their heads... can you solve the simple problem in 30 seconds?
What seemed like a regular grade school math problem had people totally stumped on social media. The equation 9 x 3 - 9 shared by @BholanathDutta on X left social media users completely mystified. So, are you smarter than a fourth grader? Or better yet, the average adult on X? See if you can solve this equation in 30 seconds or less. But first, here's a hint: Ever heard of PEMDAS? The age-old acronym guides you through the proper order for solving a complicated calculation like this one. It stands for Parentheses, Exponents, Multiplication, Division, Addition, and then Subtraction. Using that method, the solution is easy. There are no parentheses or exponents, so multiplication is first. 9 x 3 = 27 Then, the equation reads: 27 - 9 ÷ 3 But before doing any subtraction, PEMDAS implies that division is next. 9 ÷ 3 = 3 Now, it's painless. 27 - 3 = 24 Did you get it right? Commenters under the original X post made the common error of solving the math sum left to right, instead of utilizing the elementary principle. First they multiplied. 9 x 3 = 27 Then, subtracted. 27 - 9 = 18 And then divided. 18 ÷ 3 = 6 A few people even, inexplicably, got 9 as their answer. It had to take some mental gymnastics to find that solution. Sure, a calculator could be an easy shortcut. But, nothing beats the satisfaction of solving a problem yourself.
The Independent
2 days ago
- The Independent
Air traffic controllers in Florida briefly lost radar after fiber optic line was cut
Air traffic controllers in Florida briefly lost their radar Friday after a fiber optic line was cut, but the outage didn't lead to disruptions like what happened after similar outages around the Newark, New Jersey, airport this spring. Controllers were able to continue directing planes across five states in the Southeast because a backup system kicked in as designed. The Federal Aviation Administration said no flights were disrupted. The FAA said the radar center in Jacksonville, Florida, continued operating but on alert status because its primary communication line went down. A contractor was working on repairing the severed fiber line Friday afternoon. Authorities didn't specify what caused the severed fiber line or where it happened. The FAA didn't say exactly how long the radar was offline, but when air traffic controllers in a different facility in Philadelphia lost radar twice this spring it took 90 seconds for their systems to reboot after the system went down. Those incidents led to major disruptions at Newark Liberty International Airport in New Jersey because five controllers went on trauma leave after those outages, and that facility in Philadelphia directs planes in and out of the airport. Hundreds of flights had to be cancelled in Newark because the remaining controllers couldn't safely handle every flight on the schedule. Operations at that airport have since improved significantly An FAA spokesperson said there was 'no loss of critical air traffic service' in Jacksonville because the backup system kicked in. That center is responsible for planes flying across roughly 160,000 square miles of airspace across most of Alabama, Georgia, Florida, North Carolina and South Carolina. The problems in Newark were blamed on the failure of aging copper wires that much of the nation's air traffic control system still relies on. Transportation officials said the Newark problems demonstrated the need for a multi-million-dollar overhaul of the system that they are lobbying Congress to approve.
The Independent
4 days ago
- The Independent
NTSB says runway lights that might have helped in foggy San Diego crash hadn't worked since 2022
The runway lights that would have helped guide a small jet into a San Diego airport in foggy weather before the plane crashed, killing all six aboard, hadn't worked since 2022, investigators said. But it's unclear whether the pilot who was based at the airport knew the lights were out service. The National Transportation Safety Board's issued its preliminary report Wednesday on the early morning crash of May 22 that also injured eight people on the ground. It confirmed that the Cessna came in too low as it approached the airport and struck power lines before the plane broke apart, crashing in a nearby neighborhood. The plane struck one home and that 20 vehicles were also damaged by the crash and ensuing fire. The jet was carrying a music executive named Dave Shapiro and five others. No one in the neighborhood of U.S. Navy housing died, but eight people were treated for smoke inhalation from the fiery crash and non-life-threatening injuries after the crash near Montgomery-Gibbs Executive Airport. The pilot acknowledged the weather conditions for landing at the small airport were not ideal and debated diverting to a different airport while discussing the visibility with an air traffic controller at a regional Federal Aviation Administration control facility, according to audio of the conversation posted by The FAA had posted an official notice for pilots that the runway alignment lights were out of service, but the NTSB said that had been the case since March 2022. Repairs to those lights had been delayed while waiting for an environmental study. The NTSB said it appeared the pilot tried to activate the lights by keying his microphone seven times while approaching the airport. The NTSB said the pilot was based out of the executive airport near where the crash occurred. Shapiro had a pilot's license and was listed as the owner of the plane. But the preliminary report did not say whether investigators have determined whether the pilot knew the runway lights were not working. A power surge had also knocked out the weather system at the airport but the pilot was aware of the fog and an air traffic controller gave him weather information from Marine Corps Air Station Miramar, about 4 miles (6.4 kilometers) to the north. The NTSB said the plane was only about 60 feet (18 meters) above the ground when it struck the power lines above the neighborhood. The NTSB said the plane should have been flying almost 200 feet (60 meters) higher as it approached the airport. Wednesday's report does not list the cause of the crash. That won't be officially determined until the final report is done sometime next year.
