I grew up in hotels. My dad managed them. I lived in them. And one of the first stories he ever told me about the industry wasn't about guest satisfaction scores or revenue management or which brand had the best loyalty program. It was about Kansas City. About a Friday night tea dance in an atrium lobby where people were laughing and dancing and the skywalks above them were holding weight they were never designed to hold. He told me about the sound. He'd heard it described by someone who was there. He said you never forget a story like that, and he was right, because I never have.

Forty-five years ago today, two suspended walkways inside the Hyatt Regency Kansas City collapsed into the lobby below. One hundred and fourteen people died. Two hundred and sixteen were injured. The hotel had been open for one year. One year. A $50 million showpiece, brand new, the kind of property that's supposed to represent the best of what this industry builds... and it killed people because of a change that happened on paper, between an engineering firm and a steel fabricator, that nobody bothered to recheck. The original design called for continuous hanger rods supporting both walkways. The fabricator proposed splitting them into two separate rods to simplify assembly. The engineer approved shop drawings reflecting that change without recalculating what it meant for the load on the fourth-floor connections. That single approval, that single failure to recheck, doubled the stress on connections that were already designed to handle only 60% of the minimum code requirement. The walkways were hanging by a thread from the day they were installed. It just took a crowded Friday night to prove it.

Here's what haunts me about this story, even now, even after all these years of reading FDDs and evaluating brand standards and arguing about franchise fee structures. The system that failed wasn't some rogue actor or freak accident. It was a chain of professionals doing their jobs... almost. The fabricator proposed a change (reasonable... fabricators do this). The engineer approved it (routine... engineers review shop drawings constantly). But nobody stopped to ask the one question that would have saved 114 lives: does this change alter the math? The answer was yes. Catastrophically yes. And nobody checked. Not the engineering firm. Not the construction team. Not the city inspector. The original engineer of record later had his license revoked for gross negligence. His firm lost its ASCE membership. Victims' families were awarded approximately $140 million. The hotel reopened in October 1981, roughly two and a half months after the collapse, after a significant reconstruction, was eventually reflagged, and today operates under a completely different name. You can stay there tonight. Most guests have no idea what happened in that lobby.

I think about this story every time I watch our industry skip a step. Every time a brand pushes a PIP timeline that doesn't allow for proper inspection. Every time an owner defers a structural assessment because the capital reserve is thin. Every time a management company inherits a property and nobody orders a fresh engineering report because the last one was "only" eight years old. We are an industry that obsesses over the guest experience (and we should)... but the foundation of the guest experience, the literal foundation, is that the building doesn't hurt anyone. That sounds obvious. It was obvious in Kansas City too. The connections that failed were visible. They were above the lobby. People walked under them every day. And still, nobody checked. The engineer of record later accepted full responsibility, but responsibility after the fact is a funeral speech, not a safety protocol.

This anniversary isn't about blame. The people who failed have been named, judged, and in some cases destroyed by what happened. It's about the question underneath the blame, the one that applies to every owner, every operator, every brand executive reading this right now: who in your chain of command is actually checking? Not assuming. Not approving shop drawings without recalculating. Not signing off because the timeline is tight and the budget is set and someone above them needs this project done by Q3. Actually checking. Because Kansas City taught us something that 45 years hasn't dulled: the cost of not checking isn't a budget overrun or a delayed opening. It's a lobby full of people who trusted you to get it right.

So a 20-year-old with 1.8 million social media followers allegedly rented an Airbnb in Kissimmee, Florida, organized a physical fight between two women at 4 AM, filmed it, and posted it online for content. The victim was 19. The arrest didn't come until almost two months later, in a different county. The charges? Misdemeanor battery and criminal conspiracy. Bond was set at $1,000.

Let that sit for a second. Not the crime itself... the infrastructure around it. A short-term rental platform that screens "high-risk bookings" didn't catch this. A property owner (unnamed in every report, which tells you something about accountability in the STR model) apparently had no idea what was happening inside their asset. And a platform that made its party ban "permanent" back in 2022 still couldn't prevent someone from using a rental as a content studio for staged violence. Airbnb's technology is supposed to flag exactly this kind of booking... last-minute, young demographic, party-prone market like Kissimmee. Either the screening failed or it's not as effective as the press releases suggest.

Look, I'm not here to pile on Airbnb for one incident. But I am here to point out something that hotel operators in high-STR markets consistently undervalue: the structural safety advantage you already have. You have a front desk. You have security cameras in common areas. You have a night auditor who would notice if someone was running a fight club in room 214 at 4 AM. You have liability insurance that actually covers what happens inside your building. You have staff. That's not a cost center... that's a moat. Research shows that even a handful of safety-related reviews on Airbnb listings can drop occupancy by 1.5-2.4% and nightly rates by 1.5%. Incidents like this don't just damage the specific listing. They create doubt about the entire model, especially for families booking near theme parks (which is basically all of Kissimmee).

The bigger pattern here is what I'd call the accountability gap. Osceola County requires STR operators to get conditional use permits, collect tourist development tax, limit occupancy to three guests per bedroom plus two. But enforcement is reactive. Nobody's checking at 4 AM. Nobody's onsite. The regulatory framework assumes good faith from hosts and guests, and that assumption breaks exactly when it matters most. Hotels don't operate on assumed good faith. Hotels operate on staffed shifts, operational protocols, and people who are physically present when things go wrong. That's not a bug in your cost structure. That's the product.

What's frustrating is how rarely hotel operators actually market this advantage. I talked to an independent owner last month who competes directly with about 300 STR listings in his market. He'd never once mentioned safety, security, or professional staffing in his marketing. Not once. He was competing on rate and amenities against a model that literally cannot guarantee someone is awake in the building. If you're running a hotel within a five-mile radius of a market where STRs dominate... Kissimmee, Nashville, Scottsdale, any tourist-heavy corridor... this story is ammunition. Not in a fear-mongering way. In a "here's what you get when you book with us" way. Staffed buildings. Accountability. Someone who answers the phone at 4 AM who works for the hotel, not an app.