Most places restored power by midnight, as early as 6 p. Over 30 million people and 80,000 square miles 207,000 km. As a result, almost every company needs to have a power failure response strategy in place. Canadian task force investigating the blackout said in november that firstenergy employees failed to take steps that could have isolated utility failures because its datamonitoring and. A previouslyunknown software flaw in a widelydeployed general electric energy management system contributed to the devastating scope of the august 14th northeastern u.
A software bug at firstenergy corporation in ohio caused this power outage. Final report on the august 14, 2003 blackout in the united. Overcoming the causes of data center outages 365 data. From electronic voting to online shopping, a significant part of our daily life is mediated by software. There is a need for intelligent grid monitoring tools capable of giving early warning of conditions in which there is a heightened risk of instability and cascading failures. The blackout s primary cause was a software bug in the alarm system at a control room of the firstenergy corporation, located in ohio.
In a matter of seconds, large portions of ohio, michigan, pennsylvania, massachusetts, new york, connecticut, new. The causes of outages differ in a number of important ways. A ventricular septal defect is a hole in the heart that some babies are born with. Biggest software failures software testing can help catch. Acute kidney failure is sudden and can cause swelling, frequent dark urination, fatigue, nausea and more. The northeast blackout struck 15 years ago today extremetech. Northeast blackout 2003cause inadequate situational awareness of first energy s system. Chinese hackers may have been responsible for the recent power outage in florida, and the widespread blackout that struck the northeastern u.
May 17, 2016 as a result, almost every company needs to have a power failure response strategy in place. Feb 11, 2004 turns out after all the various speculation on reasons, the big northeast blackout from last summer was the result of a software bug that was only just discovered and not as many had speculated. A technician had shut it off to upgrade the software, and then gone to lunch. By thinkreliability staff on august 14, 2003, over 50 million people in the u. Its way too easy to cause a massive blackout in the us vox. As noted in chapter 1, given the numerous and diverse potential sources of disruption, it is impressive that relatively few largearea, longduration outages have occurred. The outage, which was much more widespread than the northeast blackout of 1965, affected an estimated 10 million people in ontario and 45 million people in eight u.
Cause, software bug in the alarm system in the control room of firstenergy. There is a hidden failure in the protection system e. Jul 16, 2011 the northeast blackout of 2003 was a widespread power outage that occurred throughout parts of the northeastern and midwestern united states and ontario, canada on thursday, august 14, 2003, just. Previous work using airborne measurements found decreased pollution in the northeast during the blackout, possibly from powerplant shutdowns. The 2003 northeast blackoutfive years later scientific american. The company points out, quite rightly but also narrowly, that it is too soon to tell whether its tripped power plant and lines were the cause or effects of the northeast blackout.
Blackout details and timeline the details of the 2003 blackout will now be summarized, but a more thorough investigation of the matter can be found in 1. All software failure modes can result in catastrophic failure and all can result in a noncritical failure. Ten years ago today, large portions of the midwest and northeast united states and into canada went dark. The blackouts primary cause was a software bug in the alarm system at a control room of the firstenergy corporation in ohio. Software crisis in software engineering ecomputernotes. The august 14 blackout affected the northeastern portion of the eastern. The multiple failures make the problem worse and worse, and a large area ends up in the dark. The northeast blackout of 2003 was a widespread power outage that occurred throughout parts of the northeastern and midwestern united states and the canadian province of ontario on thursday, august 14, 2003, just after 4. Taking after are 6 famous software disasters in as beneath. This causes a transient flashover event as current carried by the line is. Webmd symptom checker helps you find the most common medical conditions indicated by the symptoms blackouts memory time loss and confusion including medication reaction or sideeffect, transient global. Lack of investments into the grids high costpressure for the assetowners due to deregulation, leading to bottlenecks in transmission lack of communication among the operators need for more regulatory works rules, grid code etc. System blackout causes and cures by damir novosel 106.
Aug, 2008 the 2003 northeast blackout five years later. A huge 1965 blackout in the northeast prompted utilities to create the north american electric reliability councilnow called the north american electric reliability corporation nercto. The department of energy and natural resources canada jointly commissioned a task force that. Software bug contributed to blackout kevin poulsen, securityfocus 20040211. A collection of wellknown software failures software systems are pervasive in all aspects of society. More than 35 million people were hit by the northeast blackout in 1965, one of the largest outages in north american history. As a matter of fact, programming bugs can irritate, however, the defective programming can likewise be costly, humiliating, ruinous and savage. Scud missile attack patriot missile system, 2003 northeast blackout race condition therac 25 peak load conditions affordable health. However, as it turned out, the cause of the great 2003 northeast blackout was anything but sinister. Poor tree management, insufficient communications between electric utilities in the. Ultimately, a delayed alarm following the failure of a voltage monitoring tool. The blackout that exposed the flaws in the grid the new. Our world has become highly reliant upon the availability of continuous power. The northeast blackout of 2003 was a widespread power outage throughout parts of the northeastern and midwestern united states, and the canadian province of ontario on august 1428, 2003, beginning just after 4.
Turns out after all the various speculation on reasons, the big northeast blackout from last summer was the result of a software bug that was only just discovered. Blackouts occur when your bodys alcohol levels are high. Northeast blackout of 2003 the northeast blackout of 2003 is the second most widespread power outage in history. It specified that relay q29bd had tripped, but did not find a reason for the tripping, other than a possible sudden surge that momentarily raised the power above 375 mw. Northeast blackout of 2003 your expert root cause analysis. As the august 14th blackout began, a flaw buried in widelydeployed general. The northeast blackout of 2003 was a widespread power outage that occurred throughout parts of the northeastern and midwestern united states and ontario, canada on. Technical analysis of the august 14, 2003, blackout nerc. As will be shown, the 2003 northeast blackout was heavily based in these concepts. Later, it was determined that the major reason behind the failure was a software bug in the power monitoring and management system. Thats what happened in the 2003 northeast blackout that left 50 million people without power. A case study of the 2003 north american power outage.
Fifteen years ago, a software bug resulted in over 50 million people losing. Remembering the 2003 northeastern blackout in toronto. I saw the news story on the new england blackout on tv. I read the report from the federal power commission on the blackout.
For some customers, power was not restored for nearly four days. Solving the 1965 northeast blackout a stepbystep chronology. Over 30 million people and 80,000 square miles 207,000 km 2 were left without electricity for up to hours. Aug 14, 2018 the blackout was a telling example of how vulnerable modern infrastructure can be to disruption and a reminder that our sophisticated failure prevention systems are only as effective as the. In this page, i collect a list of wellknown software failures. On august 14 th, 2003, a blackout affected northeast america and canada in which millions of people were affected. The tripping of the sammisstar 345kv transmission line prompted the outcome propagating across borders and turning into a cascading blackout which affected eight states and two provinces in canada. A silent failure of the alarm function in firstenergys computerized energy management system ems is listed in the final report as one of the direct causes of a. The northeast blackout of 1965 was a significant disruption in the supply of electricity on tuesday, november 9, 1965, affecting parts of ontario in canada and connecticut, massachusetts, new hampshire, new jersey, new york, rhode island, pennsylvania, and vermont in the united states. The report makes clear that this blackout could have been prevented and that immediate actions must be taken in both the united states and canada to ensure that our electric system is more reliable. The blackout was a telling example of how vulnerable modern infrastructure can be to disruption and a reminder that our sophisticated failure prevention systems are only as effective as the.
Overcoming the causes of data center outages 365 data centers. The root cause of the outage was linked to a variety of factors. Blackouts memory time loss, dizziness, fainting and. One of them was buried in a massive piece of software compiled from four. Apr 08, 2004 a silent failure of the alarm function in firstenergys computerized energy management system ems is listed in the final report as one of the direct causes of a blackout that eventually cut off. Pataki reluctantly recalled one of the two major blackouts of the last 40 years in the northeast the 1965 power failure, which left an 80,000squaremile stretch of the united states and. The blackout that exposed the flaws in the grid the new york. The power outage that left 50 million wo electricity retro report the new york times duration. In more remote areas it took nearly a week to restore power. One piece of the system fails, and then the pieces near it cannot handle the increased load caused by the failure, so they fail. Dec 22, 2016 a blackout is a temporary condition that affects your memory. Aug 14, 20 home 10 years after the 2003 northeast blackout the cascading event, which started shortly after 4. Many others did not get their power back until two days later.
Nov 11, 20 in 2003, a blackout crippled areas of the u. The blackout was, in fact, triggered on a hot day by an. Apr 14, 2014 thats what happened in the 2003 northeast blackout that left 50 million people without power. The northeast blackout of 2003 was a widespread power outage throughout parts of the northeastern and midwestern united states, and the canadian province of ontario on august 14, 2003, beginning just after 4. The cascading event, which started shortly after 4. Software bug contributed to blackout securityfocus. Ten years later, we are still grappling with concerns over the vulnerability of the power grid. The northeast blackout of 2003 was a widespread power outage throughout parts of the. Ultimately, a delayed alarm following the failure of a voltage monitoring tool outside of cincinnati, ohio caused the issue. A task force looking into the cause of the massive aug. At that stage, power system is faced with overloaded equipment, voltage instability, transient instability, andor small signal instability. According to the ponemon institutes 2016 survey, cost of data center outages, ups system failure remains as the top cause of unplanned data center outages. That can result from a lack of generating capacitythe cause of the 2000 california blackoutsor because of one or more faults, as in the 2003.
A drug overdose can be fatal and causes sleepiness, confusion, coma, vomiting, and other symptoms. Sep 25, 2003 in the discussion of the 2003 blackout, some potential linking factors were listed that could contribute to the risk of a condition in which a blackout could occur. In the discussion of the 2003 blackout, some potential linking factors were listed that could contribute to the risk of a condition in which a blackout could occur. A wide variety of events can cause disruption of the power system. I will start with a study of economic cost of software bugs. Software failure cited in august blackout investigation computerworld.
The investigation cited a software glitch, inadequate operator training and trees too close to power lines. Other large blackouts are caused by equipment failures or operator errors like the big 2011. Much larger than the northeast blackout of 1965, in america alone, this blackout affected 45 million people in 8 states. In nearly every major blackout, the situation is the same. We present a case study for each software failure, the first is the iranian ir655 flight shootdown, the second is the ariane 5 flight failure, the third is the 2003 northeast blackout, and. Aug 14, 2019 blackout hits northeast united states a major outage knocked out power across the eastern united states and parts of canada on august 14, 2003. Very few businesses can operate effectively in the event of a sustained outage or blackout as was witnessed during the northeast blackout of 2003.
The media centre for ontarios independent energy system operator ieso noted that the blackouts causes stemmed from inadequate procedures and operations in the state of ohio, as outlined in final report on the august 14, 2003 blackout in the united states and canada. It specified that relay q29bd had tripped, but did not find a reason for the tripping, other than a possible. Northeast blackout caused by a software bug techdirt. The 2003 northeast blackoutfive years later scientific. Understanding the causes of data center outages and finding ways to address them are crucial to preventing business disruption that can lead to customer churn and damaged reputations.
767 124 42 539 506 586 727 815 1068 226 1243 714 438 1507 169 160 216 1584 32 297 1307 1017 476 894 1312 1609 381 628 1079 815 1242 350 1285 296 691 92 960 650 980 1121 100 532