Idiot mistakes that changed the course of history

We've all been there. We've all felt the slow burn of realization that comes when it finally becomes clear we've done something horribly wrong. Take solace in this: Whatever you did, you probably didn't change history for anyone but yourself.

These people changed the world on a grand scale, so large that it's still felt today. They changed the fate of entire nations, started a chain reaction that led to countless deaths, and sometimes, their mistakes led to centuries of persecution and racial hatred.

But there's a bright side here, too. Sometimes, history didn't change for the worse, it changed for the better. The important thing about mistakes is that we learn from them, and sometimes, it takes a big one for humans to sit up, take notice, and say, "Hang on a sec … we can fix this." And we do, occasionally, dust our collective selves off, push up our sleeves, and get fixing. That's as inspirational as you'll find in human history.

The bad planning of Louis XVI and Marie Antoinette

The French Revolution was a bloody period in France's history where (via History) unrest led to a lot of practicing with a guillotine. King Louis XVI took a final trip there in 1793, Marie Antoinette followed a few months later, and France changed forever.

Their deaths kicked off the Reign of Terror and led to thousands of executions and the rise of Napoleon. But here's the thing — they didn't need to die at all, and probably wouldn't have if Louis XVI hadn't made a whole series of dumb decisions.

The Smithsonian says it started when thousands of people stormed the Bastille, seized the royals, and escorted them to Tuileries. But here's the important part — they weren't locked up. Louis and Marie Antoinette both could have walked out the door any time, but they didn't. It wasn't until around two years later they finally snuck out, but they planned their escape pretty impractically. They traveled together in a slow wagon laden with things like a complete dinner service and wine chest, and Louis sent away the one person who probably could have helped them: his wife's lover, Count Axel Fersen. Not surprisingly, the royals were captured and escorted back to Tuileries. Then, Fersen organized an escape with help from Sweden's king, broke into the palace, and hung out with Marie for a day until Louis sent him away again. It wasn't long before the king was sent to the guillotine.

Columbus is bad at math, 'discovers' the New World

By now, everyone knows what a horrible person Christopher Columbus was, and what his arrival in the New World started. But he was only there in the first place because he was bad at math, and made errors in his navigational calculations that gave him a little extra convincing power when it came to getting financing for his voyages.

IEEE Spectrum looked into how bad Columbus' math was, starting with latitude calculations. While the ancient mathematician Eratosthenes came up with the standard that 1 degree of latitude was about 59.5 miles, Columbus decided he liked the findings of a medieval geographer from Persia better. Alfraganus thought 1 degree was 56.67 miles, and that's not too much of a difference, right?

Only, Columbus forgot that for the Persian geographer, a "mile" was the Arabic mile, which translated to 7,091 feet. Eratosthenes was working with a Roman mile, which was 4,856 feet. That's a huge difference, and he wasn't done yet. Columbus then mashed together the numbers and distances of explorers from Ptolemy to Marco Polo, added a bit of his own estimations, and completely screwed up the location of the Indies. By the time he was done, his calculations came with an impressive 58 percent margin of error, but they sounded good, he got his funding, and went off to "discover" the Americas.

Bad translation still causing problems in New Zealand

In 1840, representatives of the 125,000-odd Maori and the 2,000 or so settlers living in New Zealand signed the Treaty of Waitangi. In theory, it was supposed to protect the rights of the Maori, establish guidelines for trade and missionary activity, and keep other nations from poking around the country. There was a huge problem, though. When it was signed, the British signed an English-language version that didn't quite mean the same thing as the Maori-language version the native peoples signed.

According to New Zealand Tourism, the treaty had three articles, and the last two were plagued with some major translation issues someone should have bothered to double-check. At the heart is a dispute over whether the treaty gives the British government complete sovereign control over Maori lands. The British version says it does, but the Maori translation of the treaty suggests they were just allowing the British to use the land, not rule it. That huge disparity led to a 19th century punctuated with wars fought over land rights. Problems continued for decades, and even though attempts were made to clarify the treaty in 1975, those problems still continue.

Erwin Rommel goes home on the wrong day

Erwin Rommel is a fascinating figure, one of Nazi Germany's most prolific commanders and a man the International Churchill Society calls "a thoroughly decent man," mostly for his tendency to ignore many of Hitler's most horrible orders (as well as not reporting his knowledge of a 1944 conspiracy against the Fuhrer). He was a brilliant general, and headed a unit nicknamed the Ghost Division because it was so fast, so targeted, and so efficient. He was also supposed to be in Normandy for D-Day.

In the days leading up to the Allied invasion of the mainland's coast, he went deer hunting, and he also went into Paris to buy shoes for his wife's birthday. After looking at the tide tables and the approaching storms, he decided the Allies probably weren't going to attempt a Channel crossing in such unfavorable conditions. Instead of staying on what would very, very quickly become the front lines of the war, he headed home to Germany for his wife's June 6 birthday. The LA Times says he was at his country house in Germany when he heard about the invasion happening hours away. He got to Normandy as quickly as he could, but one of Germany's most prolific generals was essentially taken out of the action to attend a birthday party.

Two oopsies bring down the Berlin Wall

The fall of the Berlin Wall was one of the defining moments of the '80s, and it only happened because of two easily avoidable mistakes.

Tensions were already at a breaking point, and in November 1989, East Berlin Politburo members decided they needed to make some concessions if they wanted to keep anything resembling peace. They took to the airwaves to make an announcement that was supposed to say there would be an ever-so-slight relaxation of travel rules, but that they would retain the right to deny anyone passage at any time. The press conference was completely botched, though, and the reading of the announcement was garbled save a few phrases, including "possible for every citizen" and "right away, immediately." The New York Times says people interpreted that as free travel, and it's easy to see why.

The second mistake was even more insane. When thousands of people converged on border crossings they thought were open, Stasi officer Harald Jager called for backup somewhere around 30 times in a single night (via History). When his superiors didn't believe him about the chaos he was facing — and, at one point, called him "simply a coward," Jager kicked open the doors, allowed people to pass both ways, and started the real fall of the Berlin Wall … all because his superiors made the stupid mistake of underestimating him, his service, and his backbone.

Dutch traders aren't impressed with Australia, leave it for the British

In 1770, James Cook claimed Australia for Britain, and we all know how well that worked out for everyone living there. He wasn't the first European to set foot on the continent, though, and if it wasn't for a stupid lack of foresight, Australia might have been a Dutch colony.

According to the National Museum of Australia, Dutch explorer Willem Janszoon was actually the first European to make recorded, official contact with Australia. He landed there in 1606, on a ship that was part of the Dutch East India Company. Having spent some time along the VOC trade routes in Asia, he was dispatched on a mission to explore a largely unknown southern land mass to see if the Dutch might be able to harvest any gold or resources there. There weren't, but there were some understandably hostile native peoples that made them think twice about the whole endeavor.

Susan Broomhall, history professor at the University of Western Australia, says not everyone thought it was a worthless piece of land. Some argued for using Australia as a stepping-stone sort of colony along the Europe-Asia trade routes, and others said it was pretty much perfect for wine-making. Dutch East India Company officials weren't convinced, decided it wasn't worth the bother, and left the entire continent up for grabs.

A few stupid mistakes causes New York City's 1977 blackout

In 1977, New York City lost all power for 25 hours. The consequences were devastating. American Experience (via PRI) says around 800,000 people were stranded in the subways and elevators, while others set to looting and pillaging on a medieval scale. There were about a thousand fires set, more than 1,500 businesses were looted, and by the time the lights came back on, there were damages up to about a billion dollars. Some have credited the blackout as the catalyst that sparked the hip-hop movement, which is a nice bonus.

And it all happened because someone didn't know what buttons to push.

Schneider Electric looked at just what happened on that hot summer night in '77, and it started with a few lightning strikes. That's not uncommon, they say, and most substations are prepared for it. This one — run by Con Ed — wasn't. After lightning tripped the breakers, Con Ed tried to restart the station's generators. The problem? No one was there. When employees got there and started running system-wide procedures to get everything back up and running, they ran the wrong procedures. Instead of dumping the necessary 1,500 megawatts of load, they ran one that got rid of only a few hundred. The station shut down, and the Big Apple went dark.

A theater underestimates how much kids want free stuff

Even if you don't have kids, you know that kids like toys, right? In fact, it's safe to say that kids love toys, and if you think that's a given, it wasn't for event organizers at England's Victoria Hall, circa 1883.

The Smithsonian says the Victoria Hall disaster was one of the most devastating events in Victorian-era Britain, and it was completely avoidable. It started simply enough, with a variety show that packed the theater with around 1,000 children. Shouting out the promise of free toys to a group of children who didn't have many toys is the very definition of the word "mistake," and the kids surged forward as soon as the announcement was made. They left their seats, packed aisles, blocked staircases, and were crushed against doors. By the time the chaos cleared, 183 children were dead.

That tragedy led to an invention you use all the time — the push bar emergency exit. It took years for it to be installed in buildings around the world (and other similar tragedies would happen in the meantime), but those 183 children ultimately helped save the lives of countless others.

Captain gets drunk, causes a devastating oil spill

In 1989, the Exxon Valdez dumped 42 million liters of crude oil into Prince William Sound, devastating the coastline for hundreds of miles. Thousands of animals died immediately, and the effects are still being felt decades later. According to research reported in Scientific American, oil that settled into the sound's sediment has shorted the life span of fish, birds, and local mammals, and in 2018 Marine Insight looked at some of the farthest-reaching impacts. Tourism plummeted, more than 26,000 people had their jobs impacted, and even after $3.8 billion was poured into cleanup efforts, the oil is still there.

Yes, in 2018.

According to CNN, the majority of area species — including orcas and the Pacific herring — have never recovered and likely never will. That's a huge deal, as the Pacific herring is a cornerstone species that numerous other animals rely on for food.

So, why did it happen? Because the crew made some extraordinarily dumb mistakes. Captain Joseph Hazelwood was deep in alcohol-induced slumber at the time of the crash, and he'd left the ship — complete with non-functional radar — in the hands of a third mate. The third mate was absolutely not trained to take command and drove the ship right onto a reef he never saw. They were also severely under-crewed and had strayed from the normal shipping route, all compounding into a tragic disaster that changed the ecosystem forever.

Engineers try to stop the Challenger launch, get overruled

Vice News estimates about 17 percent of the U.S. viewing audience watched the Challenger disaster live in 1986, and it was a horrifying moment that shaped how everyone from NASA to the American public thought about the space program. Only 73 seconds after liftoff, dreams of space travel became a little less romantic and a little more terrifying, and if it wasn't for that disaster our commitment to exploring the nearest reaches of space would have been very different.

The Challenger disaster happened, says Space.com, because a series of O-ring seals were never tested in the cold. The morning of the launch — January 28, 1986 — was freezing cold, which led to the failure of the seals and ultimately ripped the shuttle apart.

And that brings us to the mistake. It wasn't until 2016 that NASA engineer Bob Ebeling came forward to be identified after carrying his guilt for three decades. Ebeling and four other engineers had been working at NASA contractor Morton Thiokol at the time of the launch, and when they heard of the conditions the shuttle was going to launch in, they tried to stop it. They argued that the rubber seals wouldn't work in the extreme cold, that the shuttle would explode … and they were overruled by both their managers and NASA. "Had they listened to me," he told NPR, "…it might have been a completely different outcome."

Typos give women the right to vote in Kuwait

In 1999, CNN reported that the Kuwaiti cabinet ruled to allow women to vote. Why? Because of typos in the Koran. Stick with this, it's complicated.

Earlier in the year, the Minister for Islamic Affairs had come under some extreme scrutiny when it was found his state-sanctioned version of the Koran was missing a verse. He was accused of doing it on purpose and using his power to try to change the Muslim faith. BBC News reported that in response, the government descended into turmoil and Sheikh Jaber al-Ahmad Al-Sabah responded by dissolving parliament and calling for elections.

A report by the Inter-Parliamentary Union says it was those elections that gave liberal candidates the chance to step forward. Liberal and Islamist candidates took a staggering amount of seats, and immediately started leaning on reforms that would advance women's rights and move toward stopping political corruption and public funds mismanagement. Amid all the turmoil, women got the vote for good in 2005, and it all started because someone couldn't be bothered to give the state-sanctioned version of the Koran another read-through before publishing it.