The Washington Hilton Just Got Shot Up Again. Hotels Still Can't Solve This Problem.
A gunman charged a Secret Service checkpoint at the Washington Hilton during the White House Correspondents' Dinner, and the 1981 Reagan shooter is now giving security advice on social media. The real question for hotel operators isn't whether your property is a target... it's whether your security plan survives first contact with an actual threat.
So the same hotel where a president got shot in 1981 just had another gunman show up with a shotgun, a handgun, and multiple knives during the biggest political dinner of the year. And John Hinckley Jr.... the guy who shot Reagan at that exact property 45 years ago... is now publicly calling the hotel "not secure" and saying they should stop hosting major events. We live in strange times.
Look, I'm a technology guy. My instinct is to evaluate this through the lens of systems, access control, surveillance architecture, threat detection. And there IS a technology story here. But the more I thought about it, the more I realized the technology angle is almost a distraction. The Washington Hilton had the Secret Service running security. Metal detectors. Checkpoints. Credential verification. The most sophisticated physical security apparatus available in the United States. And a 31-year-old guy still got close enough to hit an agent in the vest before being stopped. The system worked (nobody died), but it worked at the last possible moment... the human equivalent of a system catching an error in production instead of in testing. That's not a success story. That's a near-miss report.
Here's what actually matters for hotel operators. The suspect was a registered guest. He had a room. He brought weapons into the building the way any guest brings luggage... through the front door. Every access control system, every surveillance camera, every AI-powered threat detection platform I've evaluated in the last three years has the same fundamental vulnerability: a credentialed person inside the perimeter is trusted by default. Hotels aren't airports. You don't X-ray luggage at check-in. You don't wand guests walking through the lobby. The entire hospitality model is built on the assumption that the person with a room key belongs there. That assumption is the attack surface, and no amount of technology patches a philosophical vulnerability. I talked to a security consultant last year who put it bluntly: "The hotel's product IS access. You can't sell access and restrict access at the same time. That's the whole problem."
The technology that exists today... gunshot detection sensors, AI-driven behavioral analytics, weapons detection portals that look like regular doorframes... works in controlled environments. Convention centers. Stadiums. Places where everyone enters through the same chokepoint and nobody expects to feel at home. Hotels are the opposite. Multiple entrances. Service corridors. Parking garages. Guest room floors accessible by elevator. You'd have to fundamentally redesign the building to create the kind of security envelope that a high-profile event demands, and most properties (including the Washington Hilton, which was built in 1965) weren't designed for that. The suggestion floating around that venues should "buy out the entire hotel" for events like this is the only honest answer I've heard... and it's economically insane for anything short of a presidential appearance.
What's actually going to change? Insurance requirements will tighten for properties hosting large-scale events. Event contracts will include more specific security obligation language. Some hotel groups will invest in weapons detection systems for ballroom-level events (expect $150K-$400K per installation depending on throughput requirements, plus ongoing maintenance). But the fundamental tension... hospitality means openness, security means restriction... doesn't get resolved by technology. It gets managed by people making judgment calls at 2 AM with incomplete information. Which, honestly, is the same problem every hotel technology is supposedly solving and none of them fully do.
Let me be direct. If your property hosts events north of 500 attendees, pull your event security protocols this week and read them like you've never seen them before. Most of what's in there was written for liability coverage, not for an actual armed threat scenario. Two things to do right now: First, walk your building with your chief engineer and identify every unsecured entry point... service doors, loading docks, stairwell access from parking structures. You'll be surprised what you find propped open with a doorstop at 6 AM. Second, call your insurance broker and ask specifically what your event liability coverage looks like if a weapon enters through a guest room, not through the event entrance. That's the scenario nobody's underwriting correctly. This isn't about buying a $300K detection system. This is about knowing your building better than anyone who walks into it with bad intentions.