5/5 🧵 The core takeaway: both incidents ended safely, but they show how aggressively airlines and law enforcement now respond to even ambiguous threats. That’s the right call. If something on a plane even vaguely smells like a bomb issue, nobody gets cute. 📎 Source
4/5 🧵 What makes this more notable is the timing. This was the second United bomb scare in days. The day before, a United Boeing 737 bound for LaGuardia was diverted to Pittsburgh after crew flagged a suspicious beeping noise — reportedly one beep per second. That flight’s 159 passengers and 6 crew evacuated safely too, and bomb techs plus K9s also came up empty.
3/5 🧵 The practical impact was brutal even without a bomb: the flight left Denver just after 11:30 p.m. local time, more than 5.5 hours behind schedule, and landed at Dulles at 4:28 a.m. Monday. So the danger ended up being false, but the disruption was very real.
2/5 🧵 The Denver incident happened Sunday night on a United Airbus A321neo headed from Denver to Washington Dulles. Passengers got off the plane after a security concern triggered a full response, with police cars and emergency crews surrounding the aircraft. Travelers were brought back into the terminal, given food, and the plane was screened.
1/5 🧵 Two United flights, two bomb scares, two negative sweeps. The headline is the disruption, not an actual explosive: about 200 passengers were evacuated from a United flight at Denver, and nothing dangerous was found. That’s still a hell of a way to delay a trip.
5/5 🧵 The core takeaway: both incidents ended safely, but they show how aggressively airlines and law enforcement now respond to even ambiguous threats. That’s the right call. If something on a plane even vaguely smells like a bomb issue, nobody gets cute. 📎 Source
📎 Source
#threadstorm
4/5 🧵 What makes this more notable is the timing. This was the second United bomb scare in days. The day before, a United Boeing 737 bound for LaGuardia was diverted to Pittsburgh after crew flagged a suspicious beeping noise — reportedly one beep per second. That flight’s 159 passengers and 6 crew evacuated safely too, and bomb techs plus K9s also came up empty.
3/5 🧵 The practical impact was brutal even without a bomb: the flight left Denver just after 11:30 p.m. local time, more than 5.5 hours behind schedule, and landed at Dulles at 4:28 a.m. Monday. So the danger ended up being false, but the disruption was very real.
2/5 🧵 The Denver incident happened Sunday night on a United Airbus A321neo headed from Denver to Washington Dulles. Passengers got off the plane after a security concern triggered a full response, with police cars and emergency crews surrounding the aircraft. Travelers were brought back into the terminal, given food, and the plane was screened.
1/5 🧵 Two United flights, two bomb scares, two negative sweeps. The headline is the disruption, not an actual explosive: about 200 passengers were evacuated from a United flight at Denver, and nothing dangerous was found. That’s still a hell of a way to delay a trip.