Speaker A
At 10 4 on a hot Thursday afternoon, August 14th, 2003, the light started going out across a huge piece of North America. Within a few minutes, power lines and power plants were switching themselves off one after another from
A minute-by-minute look at the August 14, 2003 Northeast blackout: how trees, a silent alarm software bug, and cascading grid failures plunged 50 million people into darkness.
Key Takeaways
- Grid failures are often cascading: a small, seemingly minor event can trigger a chain reaction across distant regions.
- Software bugs in critical monitoring systems can silently disable safety warnings, leaving operators blind.
- Routine maintenance such as tree trimming is essential to preventing line failures under heat-induced sag.
- Protective shutdowns that save individual equipment can collectively worsen a regional outage.
What the video covers
- On August 14, 2003, a cascading failure knocked out power to about 50 million people across Ohio, Michigan, Ontario, New York, New England and beyond.
- The eastern US grid is one interconnected system where power must match demand every second, and overloaded lines shift their current onto neighbors.
- The trigger chain began with a coal plant shutdown at East Lake 5, followed by a line outage in southern Ohio caused by a brush fire that corrupted a grid monitoring model.
- First Energy's control room alarm system froze silently at 2:14 PM due to a race condition software bug, leaving operators unaware of developing problems.
- Lines sagged into trees that had not been trimmed back, tripping three major lines in under 30 minutes without triggering alarms.
- Overloaded lines around Akron and Cleveland failed one after another, and the Sammis to Star line tripped at 4:05 PM, redirecting huge power flows through Michigan, Pennsylvania, Ontario and New York.
- Protective systems disconnected 265 power plants and over 500 generating units to avoid damage, which worsened the spread of the blackout.
- Within about 4 minutes, roughly 61,800 megawatts of demand disappeared from the grid, and the outage was largely over by 4:13 PM.
- Recovery took anywhere from hours to nearly a day and a half, and cities faced water boil orders, beach closures and sewage concerns.
- Investigators concluded the root causes were inadequate tree trimming, the undetected software bug, and insufficient situational awareness among operators.
Full Transcript — Download SRT & Markdown
Speaker A
Ohio and Michigan all the way to Ontario, New York, and New England. Around 50 million people lost power.
Speaker A
About 10 million of them were in Canada, and the rest were spread across eight American states. Subway trains stopped in their tunnels. Elevators froze between floors. Traffic lights went blank right at rush hour. And when investigators finally pieced it all
Speaker A
together, the story started with something that sounds almost silly. A few trees in Ohio that nobody had cut back and a computer alarm that stopped working without telling anyone. So, which state went dark first? How did a problem inside one control room in Ohio
Speaker A
end up switching off New York City hundreds of miles away? And could the same thing happen again? Let's walk through that day minute by minute and state by state. Starting a few hours before anything went wrong. First, a
Speaker A
quick picture of how this works. America doesn't really have one power grid. It has three big ones. And almost everything in this story happens inside just one of them. The western grid covers the mountains and the Pacific coast. Texas runs its own. And the
Speaker A
biggest by far is the eastern grid, a giant web that stretches from the Great Plains to the Atlantic and up into Canada, including Ontario. Everything on that web is tied together. A power plant in Ohio and a light bulb in Manhattan
Speaker A
are really parts of the same machine, and that machine has one strict rule. The power going in has to match the power being used every single second, or things start to shut down to protect themselves. Big lines are also built
Speaker A
with backups. When one goes down, its electricity doesn't simply vanish. It shifts onto the other lines nearby, and they suddenly have to carry more.
Speaker A
Electricity doesn't follow a route that anyone picks. It flows along every connected path at once, a bit like water spreading through a network of pipes.
Speaker A
More current makes a line hotter. Metal stretches as it heats up, so a hot line sags lower, closer to whatever is growing underneath it. That's why utilities are supposed to keep the trees under their big lines cut well back.
Speaker A
Remember that because it ends up mattering a lot in this story. August 14th, 2003 was a hot, sticky Thursday across the Midwest and the Northeast.
Speaker A
Air conditioners were running everywhere, so the demand for power was high. It was warm, but investigators later called the weather normal for August. Nothing about the day itself should have been a problem. In northern Ohio, the power company was First
Speaker A
Energy, based in Akran. Its control room in Wadsworth, a small city west of Akran, watched over the big lines feeding Cleveland, Akran, and Toledo. At 1:31 in the afternoon, one of First Energy's big generating units shut itself down. It was East Lake 5, a coal
Speaker A
fired unit on the shore of Lake Erie, just northeast of Cleveland. Losing one plant is normal, and grids are built to handle that. But East Lake 5 had also been helping to hold up the voltage around Cleveland and Akran. So the area
Speaker A
now leaned harder on power coming in over long lines. Then at 202 a line in southern Ohio went down because of a brush fire burning underneath it. That line belonged to a different company and on its own it wasn't a big deal. But it
Speaker A
caused a sneaky problem. The regional grid watchdog called MYSO used a computer model to keep an eye on the whole area. And that outage left its model working with bad data. For the next couple of hours, the people whose
Speaker A
job was to watch over that part of the grid were partly blind. And it was about to get a lot worse. At 2:14 in the afternoon, inside First Energy's control room, the alarm system stopped working.
Speaker A
That system was supposed to sound off every time something important changed on the grid. A line trips, a warning pops up, the operators deal with it.
Speaker A
That's how they keep track of thousands of pieces of equipment. Instead, it froze without a sound. No error message, no warning. The screen still showed numbers, so everything looked normal, but those numbers had quietly stopped updating. A backup server kicked in, and
Speaker A
it failed, too. Within about half an hour, the operators had lost a big part of their monitoring tools, and nobody in the room realized it. Weeks later, engineers found the cause. It was a software bug buried in the alarm
Speaker A
program. A rare timing problem that programmers call a race condition. Think of two people trying to squeeze through the same doorway at exactly the same moment and getting stuck. Two parts of the program grabbed for the same data at
Speaker A
the same instant, and the alarm process got stuck in a loop. A bug like that can hide for years, waiting for just the right mix of events. On August 14th, it got one. At 305, the first of First
Speaker A
Energy's big 34500VT lines failed. It was called the Harding to Chamberlain line, and it was carrying a normal load, well within its limits.
Speaker A
In the heat, it sagged down into a tree that had been allowed to grow too tall underneath it, and the line tripped off.
Speaker A
That was the first one. In the control room, nothing happened. No alarm, no warning. The operators had no idea the line was gone. Its power shifted onto the lines that were left. At 3:32, the Hannah to Juniper line, now carrying
Speaker A
extra current, sagged into another tree and tripped. 9 minutes later, at 3:41, a third big line, Star to South Canton, touched a tree and went down, too. Three major lines gone in just over half an hour, and the people in charge of them
Speaker A
still believed their system was fine. Other people did notice. Neighboring utilities and the regional watchdog saw strange readings and started calling First Energy to ask what was going on, but the operator's own screens looked calm, so they doubted the warnings. It
Speaker A
wasn't until around 3:42 that they started to realize something was really wrong with their computers, and by then the grid was already slipping away.
Speaker A
Meanwhile, the lines that were left kept heating up. Starting at 3:39, 16 smaller lines around Akran overloaded and dropped out one after another. By around 4:00, the grid around Cleveland and Akran was like a bridge with half of its
Speaker A
cables cut. Everything was hanging on whatever was left. At 40:05 and 57 seconds, the Samos to Starline tripped.
Speaker A
This one wasn't a tree. It was carrying so much power that its protective equipment read the overload as if something had shorted out on the line and switched it off. That was the moment it stopped being an Ohio problem. With
Speaker A
that line gone, the power that had been flowing into northern Ohio went looking for other ways in. It swung around through Michigan, through Pennsylvania, and around Lake Erie through Ontario and New York. At 410, grid operators in New
Speaker A
York saw a surge of 3,500 megawws rush across the state toward Ontario. Then, protective systems all over the map started doing their job, switching equipment off to save it. Lines opened, generators disconnected, and within seconds, the blackout spread in every
Speaker A
direction. In all, 265 power plants shut down with more than 500 generating units between them. Those safety systems weren't broken. A generator that falls out of step with the grid can badly damage itself. So, the safest thing it
Speaker A
can do is disconnect. Investigators found that none of them were badly damaged. But everyone that let go made things a little worse for everything still connected. By 4:13, it was over.
Speaker A
Northern Ohio, Southeast Michigan, most of Ontario, and almost all of New York State had gone dark. In total, about 61,800 megawatts of demand had vanished from the grid. Roughly what tens of millions of homes use on a summer afternoon.
Speaker A
Here's how it landed state by state. Most of it happened in well under a minute, so it was less like a line of dominoes and more like a wave washing over the map. Ohio was where it began and Ohio got hit hard. Cleveland, Akran,
Speaker A
and Toledo went dark along with a big part of the northern half of the state.
Speaker A
In Cleveland, the blackout knocked out all four of the big pumping stations that bring drinking water from Lake Erie. That had never happened before in the city's history. Those pumps serve about 1 and a half million people in
Speaker A
Cleveland and its suburbs, and they were all told to boil their water. The National Guard brought in water tankers and the city closed its beaches over fears that sewage could flow into the lake. The city's water commissioner said
Speaker A
it was the crisis of his career. Next door in Michigan, about 2.3 million households lost power, including people in Detroit, Ann Arbor, and Lancing.
Speaker A
Detroit's water system, one of the biggest in the world, serves more than 4 million people. With its pumps down, the water pressure dropped and 126 communities had to boil their water for days. Gas station pumps need electricity, too. Drivers lined up at
Speaker A
the few stations that still worked and the governor signed an order to rush nearly a million gallons of gasoline into the Detroit area. Across the river in Canada, Ontario lost most of its power. About 10 million people there
Speaker A
were in the dark, including the people of Toronto. Several of Ontario's nuclear reactors had shut down completely. And a reactor that stops all the way has to be restarted slowly. It took days. For more than a week, the province had rolling
Speaker A
blackouts and asked people to use as little power as they could. New York State lost about 80% of its power. From upstate cities like Albany all the way down to Long Island and New York City, it went dark. Pennsylvania got off
Speaker A
lighter. Only parts of the state lost power and most Pennians kept their lights on. In New Jersey, it reached the northern part of the state, including Newark, and the governor declared a state of emergency. Western Connecticut went dark, too, and so did parts of
Speaker A
Massachusetts and several towns in Vermont, eight states in all, plus Ontario. But the strangest scenes of all, came from New York City, where the power went out at 411, right at the start of rush hour. More than 400 subway
Speaker A
trains stopped wherever they were, many of them in tunnels. About 400,000 passengers had to be led out, and it took nearly 3 hours to get everyone out.
Speaker A
Thousands of people were stuck in elevators, and firefighters spent the evening getting them out. Cell service was patchy, so people lined up 10 deep at payoneses to call home. It was less than 2 years after September 11th, and
Speaker A
for a lot of people, the first fear was terrorism. Officials said quite quickly that it wasn't, but armed counterterror teams were still sent out to guard city landmarks. Mayor Michael Bloomberg asked people to stay calm, go home, open their
Speaker A
windows, and drink plenty of water. Be sure you don't make an inconvenience into a tragedy, he told them. With no trains, hundreds of thousands of people simply walked home. Huge crowds poured across the Brooklyn Bridge and the other
Speaker A
bridges over the East River in the evening heat. Time Square went dark. As the sun went down, the giant screens stayed black, and the city that never sleeps went darker than anyone could remember. Many people sat outside on
Speaker A
stoops and sidewalks because their apartments were sweltering, and there were no fans, no air conditioning, and in tall buildings, often no running water because the pumps that lifted upstairs had stopped, too. And compared with the blackout of 1977, the night
Speaker A
stayed remarkably calm. There were some arrests, but nothing like the looting and fires that had torn through parts of the city back then. And then something happened that a lot of New Yorkers had never seen. With the city lights off,
Speaker A
they looked up and saw the stars. Some people even spotted the Milky Way and satellites drifting overhead. It wasn't even a perfect night for it. The moon was only 2 days past full, and its glow washed out a lot of the fainter stars.
Speaker A
People saw them anyway. NASA's astronomy picture of the day later showed the city that night from across the Hudson. Most of the light left came from cars, a few generators, flashlights, and candles.
Speaker A
For many people, the heat made it a hard night, especially older people stuck high up in apartments with no air conditioning and no working elevators.
Speaker A
The city officially linked only a handful of deaths to the blackout. But a study published years later estimated about 90 extra deaths in New York City, a jump of about 28% over a normal day.
Speaker A
Getting the power back took a long time because you can't just flip a grid back on. Plants have to restart and every piece has to be reconnected slowly and in balance or it trips all over again.
Speaker A
Some areas had their lights back within a few hours. In New York City, the last neighborhoods got power back at 9:03 the next night, about 29 hours after it went out. Cleveland's boil water order ended over the weekend. Detroit's lasted until
Speaker A
Monday because the city had to show clean water tests before it could lift it. The cost to the United States was estimated at somewhere between 4 and 10 billion. In Canada, the whole economy shrank by 0.7% that August. Soon after,
Speaker A
the United States and Canada set up a joint task force to find out exactly what had gone wrong. It wasn't a terrorist attack, and it wasn't one single failure. The final report described a chain of them. First Energy
Speaker A
hadn't kept the trees under its lines trimmed. Once its alarm went down, it didn't understand what was happening on its own system, and it didn't warn its neighbors in time. If the alarm had worked that afternoon, the operator's
Speaker A
screens would have filled up with red warnings as each line dropped. The watchdog's own tools had also been struggling at the worst possible time, so nobody outside had the full picture either. As for the software bug, it was
Speaker A
tracked down about 8 weeks after the blackout. Engineers poured over roughly a million lines of code before they could make it happen again on purpose.
Speaker A
And here's the part that surprised a lot of people. Many of the rules broken that day were voluntary. Utilities were expected to follow them, but there was no real penalty if they didn't. That changed in 2005. Congress passed the
Speaker A
Energy Policy Act and grid reliability rules became mandatory with fines for breaking them. By June 2007, the first set of those rules, 83 of them, could be enforced across the United States. Tree trimming under big lines stopped being
Speaker A
optional. Today, a utility that lets trees grow into its high voltage lines can be fined. Grid operators also got more training and stricter rules about telling each other when something starts to go wrong. To see how big 2003 really
Speaker A
was, compare it with the famous blackout before it. In 1965, the Northeast blackout cut power to about 25 million people. Most of those people had their power back within about 13 hours. In 1977, New York City went dark for about
Speaker A
a day, and that night turned into looting and fires in parts of the city.
Speaker A
Here's a detail most people forget. In 1977, the city was without power for about 25 hours. In 2003, New York City waited even longer, about 29. In 2003, it was 50 million people across eight states and a Canadian province. It's
Speaker A
still the largest blackout in North American history. So, could it happen again? Big outages still happen, usually because of storms, heat waves, or deep freezes like Texas in 2021. But the exact chain from 2003, the untrimmed trees, the silent alarm, and the
Speaker A
neighbors who never got a clear warning, is exactly what those new rules were written to stop. If a blackout like that hit your area today, a few simple things would make it a lot easier. Keep a couple of flashlights where you can find
Speaker A
them in the dark, a few gallons of water, a battery or crank radio, and a charged power bank for your phone. And if someone in your home depends on medical equipment that needs power, talk to your utility ahead of time. Many
Speaker A
utilities keep a list of customers who need extra help when the power goes out.
Speaker A
It all started with a few trees in Ohio and a computer that went quiet without telling anyone. By the end of the afternoon, 50 million people were sitting in the dark. Were you caught in the blackout of 2003? Or do you remember
Speaker A
where you were when the lights went out? Tell me in the comments. And if you want to see how your state would hold up if the grid failed today, that video is right
Topics:2003 blackoutpower gridNortheast blackoutFirst Energycascading failureelectrical gridOhiosoftware buginfrastructuregrid reliability
