Hijack Code Triggers Midair Panic

nationalusnews.com — A passenger aboard a United Airlines flight allegedly attempted to breach the cockpit multiple times, triggering an emergency hijack code and forcing the plane to divert — a chilling reminder that aviation security threats are not a relic of the past.

Story Snapshot

United Airlines Flight 2005, en route from Chicago to Minneapolis, was diverted to Madison, Wisconsin after a passenger allegedly attempted to breach the cockpit.
The flight crew transmitted squawk code 7500 — the internationally recognized emergency transponder signal indicating a hijacking — prompting an immediate security response.
Crew members restrained the passenger before the aircraft landed safely; no injuries were reported and the suspect was taken into custody.
Authorities had not officially classified the incident as a confirmed hijacking attempt as of initial reporting, leaving the full legal picture unresolved.

Emergency Diversion Over Chicago-to-Minneapolis Route

United Airlines Flight 2005 departed Chicago bound for Minneapolis when the situation escalated mid-flight. According to reporting, the flight crew transmitted squawk code 7500 — the standard international transponder code used to signal unlawful interference or a hijacking — alerting air traffic controllers to a serious security emergency onboard. The aircraft was diverted to Dane County Regional Airport in Madison, Wisconsin, where it landed safely. ^[1]

United Airlines described the diversion publicly as an effort “to address a security concern with an unruly passenger,” stopping short of using the word hijacking in its official statement. ^[3] However, the transmission of the hijack transponder code tells a more alarming story. Aviation crews are trained to treat ambiguous cockpit-adjacent behavior conservatively — once that code goes out, controllers and law enforcement respond as if a hijacking is underway until proven otherwise. ^[1]

Cockpit Breach Attempts Reported by Crew

Passengers and crew reported that the individual made multiple attempts to breach the cockpit door during the flight. Air traffic controllers, monitoring communications from the aircraft, feared at one point that a hijacking was actively in progress. ^[7] Flight attendants and crew members intervened physically, restraining the aggressive passenger before the plane touched down in Madison. No passengers or crew members were reported injured during the confrontation. ^[2]

Upon landing, law enforcement took the suspect into custody. Reports indicated the individual was transported for a psychiatric evaluation following the incident. ^[4] The exact charges filed against the passenger were not publicly confirmed in initial reporting, leaving open the question of whether prosecutors would pursue aircraft piracy, interference with a flight crew, assault, or a lesser offense — each carrying dramatically different legal consequences.

Official Classification Still Unclear — But the Facts Speak Clearly

Authorities had not officially labeled the event a hijacking attempt in the public record available at the time of reporting. ^[1] That gap between operational response and legal classification is common in aviation security incidents. Crews are trained to respond to the worst-case scenario first and sort out the legal definition later. The transmission of squawk code 7500 and multiple reported cockpit breach attempts are not the hallmarks of a routine unruly-passenger situation — they are the hallmarks of a crew doing exactly what they were trained to do when facing a potential hijacking. ^[1]

United Airlines Flight to Minneapolis Diverted Due to Failed Hijack Attempt https://t.co/nZSTVfjgS0

— The Golden Era (@ElaineR7) May 30, 2026

This incident fits a troubling broader pattern of in-flight security events that escalate rapidly before the facts are fully established. A separate incident involving a United Airlines flight to Newark similarly involved a passenger who allegedly assaulted a flight attendant and attempted to breach the cockpit. ^[6] Americans who fly expect that their government and the airlines responsible for their safety take these threats seriously — not minimize them with bureaucratic language about “unruly passengers” while crews are physically wrestling someone away from the cockpit door. The full investigative record, including any Federal Bureau of Investigation (FBI) findings, Federal Aviation Administration (FAA) reports, and charging documents, will ultimately determine what happened aboard Flight 2005. Until then, the crew’s in-the-moment judgment — and the emergency code they transmitted — deserves to be taken at face value.