11:56 AM
Connect Directly

FAA Resolves Flight Plan System Failure

Air traffic controllers had to enter flight plan information manually Thursday morning, delaying some East Coast flights.

Airline passengers can expect residual delays following the restoration of a flight plan processing system that had failed Thursday morning.

The failure primarily affected air travel out of airports serving East Coast cities such as Atlanta, Boston, New York, and Philadelphia. The impact on West Coast cities is believed to have been minimal.

As of 8:30am PT, the FAA's Flight Delay Information map showed all green for destinations in the Western half of the United States.

During the outage, flight plans were being processed manually.

"Air traffic controllers on the ground at major airports are getting no automated flight plan information and have to enter that information manually, a cumbersome and time-consuming process," said the National Air Traffic Controllers Association in a statement.

Flight plan information includes an airplane's destination, its type, and its speed.

"This is not a safety issue," said an FAA spokesperson via e-mail. "We have radar coverage and communications with planes."

The spokesperson said that the agency was investigating the cause of the problem.

The NATCA said that the problem was a failure of the National Airspace Data Interchange Network, which handles computerized flight processing plans for every flight in the country. The system is located in two locations -- Atlanta and Salt Lake City -- and the NATCA said that it failed in both locations.

"[There] will be flight delays throughout the day due to the "ripple effect" of this outage," the ATCA said.

ATCA also said that weather equipment is affected, meaning that NOTAM alerts (Notice to Airmen) were not being processed.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2014-07-22
Gitlist allows remote attackers to execute arbitrary commands via shell metacharacters in a file name to Source/.

Published: 2014-07-22
Multiple cross-site scripting (XSS) vulnerabilities in the web UI in Sophos Anti-Virus for Linux before 9.6.1 allow local users to inject arbitrary web script or HTML via the (1) newListList:ExcludeFileOnExpression, (2) newListList:ExcludeFilesystems, or (3) newListList:ExcludeMountPaths parameter t...

Published: 2014-07-22
jmx-remoting.sar in JBoss Remoting, as used in Red Hat JBoss Enterprise Application Platform (JEAP) 5.2.0, Red Hat JBoss BRMS 5.3.1, Red Hat JBoss Portal Platform 5.2.2, and Red Hat JBoss SOA Platform 5.3.1, does not properly implement the JSR 160 specification, which allows remote attackers to exec...

Published: 2014-07-22
The org.picketlink.common.util.DocumentUtil.getDocumentBuilderFactory method in PicketLink, as used in Red Hat JBoss Enterprise Application Platform (JBEAP) 5.2.0 and 6.2.4, expands entity references, which allows remote attackers to read arbitrary code and possibly have other unspecified impact via...

Published: 2014-07-22
Elasticsearch Logstash 1.0.14 through 1.4.x before 1.4.2 allows remote attackers to execute arbitrary commands via a crafted event in (1) zabbix.rb or (2) nagios_nsca.rb in outputs/.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Where do information security startups come from? More important, how can I tell a good one from a flash in the pan? Learn how to separate ITSec wheat from chaff in this episode.