A United Airlines plane carrying roughly 200 passengers bound for Washington Dulles sat surrounded by police vehicles on the tarmac at Denver airport Sunday night after a bomb threat forced everyone off the aircraft. It was the second time in two days that a United flight faced a potential-bomb scare, raising fresh questions about who is calling in these threats and why the airline keeps finding itself at the center of them.
Travelers had already boarded the Airbus A321neo when the airline pulled them back off. A United Airlines spokesperson told Denver's 9News that passengers disembarked while the jet was screened over a "security concern." Footage obtained by Storyful showed cop cars ringing the aircraft and emergency crews positioned on steps beside the plane's doors, as the New York Post reported.
Passengers were given food inside the terminal while they waited. The plane finally left Denver just after 11:30 p.m. local time, more than five and a half hours behind schedule, and touched down at Dulles at 4:28 a.m. Monday.
The Denver evacuation came just one day after a separate United flight headed for LaGuardia was diverted to Pittsburgh over fears of a bomb on board. That Boeing 737 carried 159 passengers and six crew members.
Audio posted to liveatc.com captured a crew member's urgent assessment mid-flight:
"We are going to have to start treating this as a potential bomb... we are going to need to go and start a diversion and get things settled. It's a beeping noise, sequential, one beep per second."
FBI bomb technicians, Special Agents, local police, and the Allegheny County bomb squad all converged on the diverted plane. The Allegheny County Police Bomb Squad told WCVB that its Explosive Ordnance Disposal team and bomb-sniffing dogs swept the aircraft, passengers, and luggage with "negative results." No explosive was found. A United representative told the Post that the Pittsburgh flight's passengers and crew exited safely and no injuries were reported.
Two scares in two days, both involving United, both requiring massive law-enforcement mobilizations, and both turning up nothing. That pattern is worth examining. Every false alarm burns hours of federal and local manpower, strands hundreds of travelers, and tests a security apparatus that already faces questions about staffing and mission priorities.
Denver International Airport has seen bomb threats before. In a separate earlier incident, the FBI investigated after someone phoned in a threat against a United flight bound for San Francisco. The TSA said the plane was searched and nothing suspicious was found. Passengers had not yet boarded when that threat came in, and the aircraft was moved to a remote location before a sweep cleared it. Normal operations resumed afterward, Fox News reported.
In yet another Denver incident, a man aboard United Airlines Flight 570, preparing to depart for Salt Lake City, allegedly yelled "bomba," assaulted a fellow passenger, and tried to force open the emergency exit door. The plane returned to the gate, law enforcement met the aircraft, and passengers were rebooked onto a different plane. United spokesperson Andrea Hiller confirmed the disruption to Newsmax, stating the flight "returned to the gate after a customer attempted to open the exit door."
None of these incidents produced an actual explosive device. But each one consumed enormous resources and shattered the travel plans of hundreds of people. The cumulative cost, in overtime, in diverted aircraft, in delayed flights rippling across the system, adds up fast.
Broader questions about Homeland Security funding and threat readiness hover behind every one of these episodes. When bomb squads, FBI agents, and local police sprint to a tarmac, those resources are pulled from other duties. Repeated false alarms do not make the next response slower, professionals treat every call as real, but they do stretch already-thin personnel rosters even thinner.
Neither United nor law enforcement has publicly identified who made the bomb threat at Denver on Sunday night. The flight number of the Denver-to-Dulles plane has not been disclosed. It remains unclear which agency received or assessed the initial threat, whether the evacuation used emergency slides, or whether any arrests have been made.
The same gaps exist for the Pittsburgh diversion. The cockpit audio described a "beeping noise", but whether that noise came from a passenger's bag, a piece of equipment, or something else entirely has not been explained. The sweep came back clean. The plane was cleared. And 159 passengers were left to figure out how to get to New York.
Aviation disruptions have stacked up in recent months. LaGuardia, the very airport the diverted Boeing 737 was trying to reach, has faced its own crises, including staffing shortages among air traffic controllers that came under scrutiny after a deadly incident on the field.
Meanwhile, concerns about security at the nation's airports extend well beyond bomb threats. Investigators have probed whether hundreds of millions of dollars in cash moved through Minneapolis's airport with possible links to terror financing, a reminder that threats to aviation take many forms, not all of them as visible as a police cordon on a tarmac.
Nobody wants to be the official who waves off a bomb threat that turns out to be real. That is exactly why every call gets the full response: the dogs, the technicians, the evacuations, the hours-long delays. The system is built to treat every threat as credible until proven otherwise.
But when the same airline absorbs two scares in 48 hours, both cleared, both disruptive, both expensive, the public deserves to know whether someone is gaming the system. Hoax bomb threats are federal crimes. If these calls are coordinated, copycat, or targeted, law enforcement owes travelers more than "negative results" and a shrug.
United Airlines passengers did what they were told. They got off the plane. They waited. They ate whatever food the airline handed them in the terminal. They landed at Dulles five and a half hours late, in the dead of night, and went on with their lives. They did their part.
The question is whether the people responsible for finding and prosecuting whoever called in these threats are doing theirs.
