Posted on 08/15/2015 2:20:05 PM PDT by wtd
WASHINGTON (AP) -- Air traffic was snarled and passengers' tempers frayed on Saturday as many flights to and from airports throughout a large swath of the Northeast stretching from New York down to the Carolinas were delayed or cancelled.
The Federal Aviation Administration blamed the problem on "technical issues" at an air traffic control center in Leesburg, Va. Around 4 p.m., the agency said the problem had been resolved, and that officials were working to lift any remaining orders to hold planes on the ground.
Delays began building about 9:45 a.m., according to FlightRadar24, a flight monitoring website. Flights bound for airports in the Washington area were some of the most affected, including Washington's Reagan National Airport and Dulles International, as well as Baltimore-Washington International Thurgood Marshall Airport and Charlotte-Douglas International Airport in North Carolina.
By midafternoon, 50 percent of inbound flights and 42 percent of outbound flights had been cancelled at Reagan National, and delays were averaging about three hours, according to FlightRadar24. In Baltimore, 58 percent of inbound flights and 36 of outbound flights had been cancelled, and delays were averaging over an hour.
(Excerpt) Read more at hosted.ap.org ...
?
Hmmmm?
evidence? or conjecture?
Cyber wars are ongoing. When something big happens it is sensible to conjecture a foreign cause.
Flight delays are being reported up and down the east coast, courtesy of a glitch in the new air traffic control computer system. The system went down Saturday morning and initially affected airports in Washington, D.C. and New York. But the outage quickly spread to Baltimore and other points, causing the cancellation of more than 200 flights and leaving passengers scrambling on a busy weekend. Washington Post describes the system affected:
ERAM stands for En Route Automation Modernization and is the computer system that processes flight and surveillance data, provides communications and generates display data to air traffic controllers.
ERAM is part of a larger infrastructure update called NextGen, with the rollout beginning about 18 months ago. It was designed to allow air-traffic controllers the ability to handle many more flights and to improve guidance of flights throughout the country.
NBC News reports that the computer system, years behind schedule and massively over budget, was installed in the last 18 months. Aviation Today reported in 2012 on the problems being experienced by ERAM that set back installation of the system by 3 years. The emphasis is mine. Tell me these guys didnt help design the healthcare.gov website:
Noting Lockheed Martins unique expertise in the en route automation environment, FAA intended to award it the ERAM upgrade in 2002 as a sole source, 10-year contract. However, Raytheon protested, causing FAA to establish an inquiry that subsequently upheld the protest, with Raytheon becoming a Lockheed Martin team member when the $2.1 billion contract was finally awarded in 2003.
The inquiry report revealed, however, that neither FAA nor Lockheed Martin appeared sure how the upgrade was to be accomplished, other than it would be an incremental decomposition,a term that evaded clear definition.Three officials gave three different views, while FAAs integrated product team lead for en route said she did not understand how it could be accomplished or how often one would have to go into the system at any or all of the ARTCCs to perform the incremental modifications. Theres nothing practical about this, the FAA integrated product team lead testified. This is the most complex thing that the agency will ever undertake.
Her ERAM product team lead also did not know how the fairly complex technical task of decomposing old software to get it to run on a new platform in a modern language might be performed. FAA did not conduct a risk assessment to examine the potential costs and benefits of incremental decomposition, nor did it know exactly what had to be incrementally decomposed, although it did acknowledge that this will necessitate multiple transitions of deployed ERAM functionality.
Yet, as the integrated product team lead explained, one must know what the software is in order to decompose it. Unfortunately, the Host system had been built in stages, with new functions and capabilities progressively added.
Consequently, it consisted of a set of separate hardware and software components physically interfaced together, but without a common design, infrastructure or software environment: a software bowl of spaghetti as both FAAs integrated product team lead and the associate administrator for research and acquisitions described it to the inquiry.
I will agree with the project lead on this point; its an enormously complex system thats bound to have a lot of bugs to work out. But dont you get the feeling reading the above that the FAA made this more complex than it should have been? That it proceeded without a full understanding of what it wanted to accomplish? That they were riding by the seat of their pants so that errors were magnified?
The FAAs chickens came home to roost today on the east coast.
And introduces vulnerabilities that can be exploited.
No one does IT as poorly as the feds.
Problems that go away by themselves, come back by themselves.
heep ‘olap tops.
have you heard of something called pumpkin?
Previous thread
Flight control problem keeps flights grounded in NY and DC area
http://www.freerepublic.com/focus/f-news/3325080/posts
Previous thread
Flight control problem keeps flights grounded in NY and DC area
http://www.freerepublic.com/focus/f-news/3325080/posts
“No one does IT as poorly as the feds.”
I’ve had to deal with them in the past. One guy that knows what he’s doing and five guys and two lesbians watching.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.