Newark air traffic control briefly loses radar access 2nd time in 2 weeks
The FAA said the telecommunications outage impacted communications and radar displays at Philadelphia Terminal Radar Approach Control that guides aircraft in and out of Newark Liberty around 3:55 a.m. ET on Friday and lasted approximately 90 seconds.
WABC reported air traffic controllers could be heard on a radio transmission telling a FedEx plane that their screens went dark.
The latest incident highlights the air traffic control network's aging infrastructure and comes a day after Transportation Secretary Sean Duffy proposed spending billions of dollars to fix it over the next three to four years.
1:48
Staff shortages at Air Traffic Control could impact travel
The FAA said Wednesday it was taking immediate steps to address ongoing problems that have disrupted hundreds of flights at Newark since April 28 especially from United Airlines UAL.O, the largest carrier at the airport located just outside New York City.
Story continues below advertisement
The FAA said it is increasing air traffic controller staffing, adding three new, high-bandwidth telecommunications connections and deploying a temporary backup system to the Philadelphia TRACON during the switch to a more reliable fiber-optic network.
Get breaking National news
For news impacting Canada and around the world, sign up for breaking news alerts delivered directly to you when they happen. Sign up for breaking National newsletter Sign Up
By providing your email address, you have read and agree to Global News' Terms and Conditions and Privacy Policy
Duffy said Thursday that the FAA had two redundant lines 'both are up and working now' at Philadelphia.
The FAA did not immediately answer why the backup did not prevent Friday's incident.
Newark has been hit by runway construction, FAA equipment outages and air traffic control staffing shortages that prompted urgent calls from lawmakers for investigations and new funding.
FlightAware said Newark on Friday is experiencing inbound flights delayed averaging more than four hours and departure delays averaging 1 hour or more.
Duffy said Thursday controllers overseeing planes at the busy airport lost contact with aircraft on April 28 for 30 to 90 seconds, an incident that raised serious alarm.
The FAA last year relocated control of the Newark airspace to Philadelphia to address staffing and congested New York City area traffic.
(Reporting by David Shepardson; Additional reporting by Doyinsola Oladipo and Rajesh Kumar Singh Editing by Chizu Nomiyama)
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Global News
10 hours ago
- Global News
Harbour Cruises yacht runs aground off shores of West Vancouver
A passenger vessel known for cruises around the waters of Vancouver ended up in a precarious situation Sunday with passengers on board. The Joint Rescue Coordination Centre Victoria says it learned the MV Harbour Princess ran aground off West Vancouver late Sunday morning. The MV Harbour Princess belongs to Harbour Cruises, a local cruise ship and marine operator. The boat hit rocks east of Point Atkinson near Lighthouse Park, with the marine rescue coordination centre notified of the crash around 11:30 a.m. 'We were having lunch and all of a sudden, 'boom' we hear and we crashed,' said one passenger. It is unclear how many passengers were on board the vessel, which touts a capacity of up to 275 guests. 'It was a very abrupt stop, a lot of broken glass,' said another. Story continues below advertisement 0:56 Rescue at sea performed by Canadian and U.S. crews A large response followed, including a hovercraft from the JRCC, multiple Coast Guard boats, the Vancouver Police Department's marine unit, and several civilian vessels. Get breaking National news For news impacting Canada and around the world, sign up for breaking news alerts delivered directly to you when they happen. Sign up for breaking National newsletter Sign Up By providing your email address, you have read and agree to Global News' Terms and Conditions and Privacy Policy Passengers remained on board while the vessel was freed from the rocks. It then made its way back to port in Coal Harbour with help from a hovercraft. 'We received orders to go to the lower deck, put our life jackets on, and [there was] no problem. We were saved.' Story continues below advertisement After coming ashore, passengers told Global News that even though the vessel did not take on water, it was a scary experience. 'When I felt it, I knew we ran aground,' said Michael. 'With all the glass breaking and stuff, and that poor baby crying, that was one of the worst experiences I've ever experienced in my life.' B.C. Emergency Health Services reported one patient was transported to hospital in stable condition. Global News reached out to the company for more information on why the boat ran off course, but they declined to comment at this time.
CTV News
2 days ago
- CTV News
Broken altimeter, ignored warnings: Hearings reveal what went wrong in DC crash that killed 67
National Transportation Safety Board Chairwoman Jennifer Homendy, on monitor left, swears-in the witnesses from left: Dan Cooper, Sikorsky Aircraft, Lance Gant, Federal Aviation Administration, U.S. Army CW4 Kylene Lewis, Steve Braddom, U.S. Army, and Scott Rosengren, U.S. Army, during the NTSB fact-finding hearing on the DCA midair collision accident, at the National Transportation and Safety Board boardroom, Wednesday, July 30, 2025, in Washington. Over three days of sometimes contentious hearings this week, the National Transportation Safety Board interrogated Federal Aviation Administration and Army officials about a list of things that went wrong and contributed to a Black Hawk helicopter and a passenger jet colliding over Washington, D.C., killing 67 people. The biggest revelations: The helicopter's altimeter gauge was broken, and controllers warned the FAA years earlier about the dangers that helicopters presented. At one point NTSB Chairwoman Jennifer Homendy scolded the FAA for not addressing safety concerns. 'Are you kidding me? Sixty-seven people are dead! How do you explain that? Our bureaucratic process?' she said. 'Fix it. Do better.' Victims of the January crash included a group of elite young figure skaters, their parents and coaches and four union steamfitters from the Washington area. Here is a look at the major takeaways from the hearings about the collision, which alarmed travelers before a string of other crashes and close calls this year added to their worries about flying: The helicopter's altimeter was wrong The helicopter was flying at 278 feet (85 metres) — well above the 200-foot (61-metre) ceiling on that route — when it collided with the airliner. But investigators said the pilots might not have realized that because the barometric altimeter they were relying on was reading 80 to 100 feet (24 to 30 metres) lower than the altitude registered by the flight data recorder. The NTSB subsequently found similar discrepancies in the altimeters of three other helicopters from the same unit. An expert with Sikorsky, which makes the Black Hawks, said the one that crashed was an older model that lacked the air data computers that make for more accurate altitude readings in newer versions. Army Chief Warrant Officer Kylene Lewis told the board that an 80- to 100-foot (24- to 30-metre) discrepancy between the different altimeters on a helicopter would not be alarming, because at lower altitudes she would be relying more on the radar altimeter than the barometric altimeter. Plus Army pilots strive to stay within 100 feet (30 metres) of target altitude on flights, so they could still do that even with their altimeters that far off. But Rick Dressler of medevac operator Metro Aviation told the NTSB that imprecision would not fly with his helicopters. When a helicopter route like the one the Black Hawk was flying that night includes an altitude limit, Dressler said, his pilots consider that a hard ceiling. FAA and Army defend actions, shift blame Both tried to deflect responsibility for the crash, but the testimony highlighted plenty of things that might have been done differently. The NTSB's final report will be done next year, but there likely will not be one single cause identified for the crash. 'I think it was a week of reckoning for the FAA and the U.S. Army in this accident,' aviation safety consultant and former crash investigator Jeff Guzzetti said. Army officials said the greater concern is that the FAA approved routes around Ronald Reagan International Airport with separation distances as small as 75 feet (23 metres) between helicopters and planes when planes are landing on a certain runway at Reagan. 'The fact that we have less than 500-foot separation is a concern for me,' said Scott Rosengren, chief engineer in the office that manages the Army's utility helicopters. Army Chief Warrant Officer David Van Vechten said he was surprised the air traffic controller let the helicopter proceed while the airliner was circling to land at Reagan's secondary runway, which is used when traffic for the main runway stacks up and accounts for about 5% of flights. Van Vechten said he was never allowed to fly under a landing plane as the Black Hawk did, but only a handful of the hundreds of times he flew that route involved planes landing on that runway. Other pilots in the unit told crash investigators it was routine to be directed to fly under landing planes, and they believed that was safe if they stuck to the approved route. Frank McIntosh, the head of the FAA's air traffic control organization, said he thinks controllers at Reagan 'were really dependent upon the use of visual separation' to keep traffic moving through the busy airspace. The NTSB said controllers repeatedly said they would just 'make it work.' They sometimes used 'squeeze plays' to land planes with minimal separation. On the night of the crash, a controller twice asked the helicopter pilots whether they had the jet in sight, and the pilots said they did and asked for visual separation approval so they could use their own eyes to maintain distance. Testimony at the hearing raised serious questions about how well the crew could spot the plane while wearing night vision goggles and whether the pilots were even looking in the right spot. The controller acknowledged in an interview that the plane's pilots were never warned when the helicopter was on a collision path, but controllers did not think telling the plane would have made a difference at that point. The plane was descending to land and tried to pull up at the last second after getting a warning in the cockpit, but it was too late. FAA was warned about the dangers of helicopter traffic in D.C. An FAA working group tried to get a warning added to helicopter charts back in 2022 urging pilots to use caution whenever the secondary runway was in use, but the agency refused. The working group said 'helicopter operations are occurring in a proximity that has triggered safety events. These events have been trending in the wrong direction and increasing year over year.' Separately, a different group at the airport discussed moving the helicopter route, but those discussions did not go anywhere. And a manager at a regional radar facility in the area urged the FAA in writing to reduce the number of planes taking off and landing at Reagan because of safety concerns. The NTSB has also said the FAA failed to recognize a troubling history of 85 near misses around Reagan in the three years before the collision, NTSB Chairwoman Jennifer Homendy said 'every sign was there that there was a safety risk and the tower was telling you that.' But after the accident, the FAA transferred managers out of the airport instead of acknowledging that they had been warned. 'What you did is you transferred people out instead of taking ownership over the fact that everybody in FAA in the tower was saying there was a problem,' Homendy said. 'But you guys are pointing out, 'Welp, our bureaucratic process. Somebody should have brought it up at some other symposium.'' Associated Press writer Leah Askarinam contributed. Josh Funk, The Associated Press
Winnipeg Free Press
2 days ago
- Winnipeg Free Press
Broken altimeter, ignored warnings: Hearings reveal what went wrong in DC crash that killed 67
Over three days of sometimes contentious hearings this week, the National Transportation Safety Board interrogated Federal Aviation Administration and Army officials about a list of things that went wrong and contributed to a Black Hawk helicopter and a passenger jet colliding over Washington, D.C., killing 67 people. The biggest revelations: The helicopter's altimeter gauge was broken, and controllers warned the FAA years earlier about the dangers that helicopters presented. At one point NTSB Chairwoman Jennifer Homendy scolded the FAA for not addressing safety concerns. 'Are you kidding me? Sixty-seven people are dead! How do you explain that? Our bureaucratic process?' she said. 'Fix it. Do better.' Victims of the January crash included a group of elite young figure skaters, their parents and coaches and four union steamfitters from the Washington area. Here is a look at the major takeaways from the hearings about the collision, which alarmed travelers before a string of other crashes and close calls this year added to their worries about flying: The helicopter's altimeter was wrong The helicopter was flying at 278 feet (85 meters) — well above the 200-foot (61-meter) ceiling on that route — when it collided with the airliner. But investigators said the pilots might not have realized that because the barometric altimeter they were relying on was reading 80 to 100 feet (24 to 30 meters) lower than the altitude registered by the flight data recorder. The NTSB subsequently found similar discrepancies in the altimeters of three other helicopters from the same unit. An expert with Sikorsky, which makes the Black Hawks, said the one that crashed was an older model that lacked the air data computers that make for more accurate altitude readings in newer versions. Army Chief Warrant Officer Kylene Lewis told the board that an 80- to 100-foot (24- to 30-meter) discrepancy between the different altimeters on a helicopter would not be alarming, because at lower altitudes she would be relying more on the radar altimeter than the barometric altimeter. Plus Army pilots strive to stay within 100 feet (30 meters) of target altitude on flights, so they could still do that even with their altimeters that far off. But Rick Dressler of medevac operator Metro Aviation told the NTSB that imprecision would not fly with his helicopters. When a helicopter route like the one the Black Hawk was flying that night includes an altitude limit, Dressler said, his pilots consider that a hard ceiling. FAA and Army defend actions, shift blame Both tried to deflect responsibility for the crash, but the testimony highlighted plenty of things that might have been done differently. The NTSB's final report will be done next year, but there likely will not be one single cause identified for the crash. 'I think it was a week of reckoning for the FAA and the U.S. Army in this accident,' aviation safety consultant and former crash investigator Jeff Guzzetti said. Army officials said the greater concern is that the FAA approved routes around Ronald Reagan International Airport with separation distances as small as 75 feet (23 meters) between helicopters and planes when planes are landing on a certain runway at Reagan. 'The fact that we have less than 500-foot separation is a concern for me,' said Scott Rosengren, chief engineer in the office that manages the Army's utility helicopters. Army Chief Warrant Officer David Van Vechten said he was surprised the air traffic controller let the helicopter proceed while the airliner was circling to land at Reagan's secondary runway, which is used when traffic for the main runway stacks up and accounts for about 5% of flights. Van Vechten said he was never allowed to fly under a landing plane as the Black Hawk did, but only a handful of the hundreds of times he flew that route involved planes landing on that runway. Other pilots in the unit told crash investigators it was routine to be directed to fly under landing planes, and they believed that was safe if they stuck to the approved route. Frank McIntosh, the head of the FAA's air traffic control organization, said he thinks controllers at Reagan 'were really dependent upon the use of visual separation' to keep traffic moving through the busy airspace. The NTSB said controllers repeatedly said they would just 'make it work.' They sometimes used 'squeeze plays' to land planes with minimal separation. On the night of the crash, a controller twice asked the helicopter pilots whether they had the jet in sight, and the pilots said they did and asked for visual separation approval so they could use their own eyes to maintain distance. Testimony at the hearing raised serious questions about how well the crew could spot the plane while wearing night vision goggles and whether the pilots were even looking in the right spot. The controller acknowledged in an interview that the plane's pilots were never warned when the helicopter was on a collision path, but controllers did not think telling the plane would have made a difference at that point. The plane was descending to land and tried to pull up at the last second after getting a warning in the cockpit, but it was too late. FAA was warned about the dangers of helicopter traffic in D.C. An FAA working group tried to get a warning added to helicopter charts back in 2022 urging pilots to use caution whenever the secondary runway was in use, but the agency refused. The working group said 'helicopter operations are occurring in a proximity that has triggered safety events. These events have been trending in the wrong direction and increasing year over year.' Separately, a different group at the airport discussed moving the helicopter route, but those discussions did not go anywhere. And a manager at a regional radar facility in the area urged the FAA in writing to reduce the number of planes taking off and landing at Reagan because of safety concerns. Monday Mornings The latest local business news and a lookahead to the coming week. The NTSB has also said the FAA failed to recognize a troubling history of 85 near misses around Reagan in the three years before the collision, NTSB Chairwoman Jennifer Homendy said 'every sign was there that there was a safety risk and the tower was telling you that.' But after the accident, the FAA transferred managers out of the airport instead of acknowledging that they had been warned. 'What you did is you transferred people out instead of taking ownership over the fact that everybody in FAA in the tower was saying there was a problem,' Homendy said. 'But you guys are pointing out, 'Welp, our bureaucratic process. Somebody should have brought it up at some other symposium.'' ___ Associated Press writer Leah Askarinam contributed.
