Last week brought three widely reported occasions in which the plans and intentions of engineers went awry, but in different ways and with different consequences. Together, they say something about why such incidents are newsworthy and how the size of a mishap or accident, measured by the number of people affected, influences the way the incident is covered.
The local incident happened on Wednesday, Nov. 11. A building site at the intersection of Bedford Avenue and Flatbush Avenue required the excavation of a square area to a depth exceeding a full story, right next to a three-story apartment building with a store on the ground floor. Normally, the weight of a building is carried by the ground beneath and beside it. Removing underlying layers of soil immediately next to a building requires shoring the exposed vertical surface with a partition that can withstand the resulting horizontal pressure formerly opposed by the removed soil.
Around 4 P. M. that day, the shoring apparently failed, and the soil underneath the apartment building came crashing into the excavation, removing its support from underneath that side of the building. A portion of the building then collapsed, killing eight people and injuring eighteen more.
Somewhere in the world, a building or part of a building collapses nearly every day. But when more than one person is killed, and when the manner of death is peculiarly horrible, it can make national headlines. Imagine that you're sitting on your couch watching a soap opera one second, and the next second everything around you vanishes into a heap of rubble that ends your life. The power of such an image makes it fearful all out of proportion to its unlikelihood, which is another reason it was so widely covered.
The national incident happened on Friday (yes, it was the 13th) of November. The U. S. Federal Aviation Administration (FAA) was installing some new telecommunications equipment as part of a long-delayed upgrade. When a flight controller at an FAA-operated control center speaks with a pilot, his or her voice is carried over a complex system resembling a specialized telephone network, which automatically routes the conversation between the control center and radio transceivers sited in locations that will reach the plane in question. Evidently, due to conflicts between the new parts of the system and the legacy parts, it began to break down to such an extent that the FAA managers declared a "ground stop," meaning no flights were allowed to take off anywhere in the U. S. Many flights in progress were ordered to turn around or land at a different airport than planned. After five hours, the stop was partially lifted, but the disruption to air traffic was so extensive that it will be many days before flight schedules return to normal.
Unlike many countries, where air-traffic-control organizations are private and paid for with operating fees from the airlines, the U. S. government directly operates and pays for the FAA, which makes it subject to the political whims of Congress. Although funds have been allocated for upgrades, even the very process of improvement can cause problems, as we saw last week. No fatalities or injuries were directly attributed to the shutdown, but thousands of travelers and tons of cargo were affected, and the monetary cost of the disruption both to airlines and their customers is probably in the many millions of dollars.
The international accident occurred Thursday afternoon, Nov. 12. Unlike the other two, this one affected me personally, as most of my email comes through my university, which uses Microsoft Outlook as its email service. I began to notice Thursday afternoon that the last email I'd received came around noon. I can usually count on a steady flow of (mostly junk) email twenty-four hours a day, so I checked around on the internet and discovered that not only Microsoft email, but other Microsoft services such as Teams were also affected. Updates from Microsoft online stated that a failed "health check" on many servers had caused them to go offline, leaving the vast bulk of Microsoft traffic to be handled by a few remaining servers, which quickly got overwhelmed.
As it happened, I wasn't urgently needing to email anything, so the problem amounted for me to an almost welcome respite from having to check my email. Eventually, old emails began to show up close to a day later. But governments and health-care organizations around the world, which were part of the estimated 400 million users of Microsoft internet products globally, had more serious problems, although no fatalities or injuries were directly attributed to the outage. However, an estimate by the Anderson Economic Group put the outage's price tag at around $7 billion from lost sales and other causes.
There's an old saying in the news business: "if it bleeds, it leads." If an engineering-related incident kills or seriously injures anyone, especially if the numbers are high, it's going to make the news somewhere. And if the circumstances are particularly gruesome or horrifying, which well describes the Brooklyn building collapse, it's even more likely to receive at least nationwide coverage. Thousands of people die in more mundane ways every day without the world taking notice, but a morbid part of human nature is attracted to sudden, violent, and unexpected death caused by a failure of our built environment that we normally trust so well.
If death and injury are not present, large numbers will often make the news cut. One flight delay goes unnoticed, but thousands of delays and cancellations across the entire U. S. with knock-on effects on international flights made the FAA ground stop highly newsworthy. And when the cause isn't a natural one, but a failure of what should be one of the most reliable government telecommunications networks around, the news value increases further because politics gets in the mix.
Finally, although Microsoft is a publicly-traded private company, its size in terms of revenue exceeds that of some small nations, and its reach is truly global. So even something as comparatively trivial as having one's email hung up for a day or so made the news, because it affected so many people.
Lessons were learned from all these mishaps, and let's hope that if anything like them happens in the future, at least they won't happen again all in one week.
Sources: For the Brooklyn building collapse, I referred to Wikipedia's "2026 New York City building collapse" and https://www.cnn.com/2026/11/11/us/live-news/brooklyn-building-collapse-nyc. For the FAA ground stop, I referred to https://apnews.com/article/flights-halted-airports-faa-f81b0904331dafad6133f291e5f531a8. And for the Microsoft outage, I referred to Wikipedia's "2026 Microsoft outage" and https://www.securityweek.com/microsoft-365-outage-disrupts-outlook-exchange-online-and-teams/.
No comments:
Post a Comment