Unruly passenger arrested after being restrained with duct tape during flight

A man was arrested for unruly behavior aboard an American Airlines flight, according to statements from the airline and the FBI. The incident prompted the aircraft to divert to Baltimore on Thursday night, as confirmed by both the airline and law enforcement authorities. Authorities described the passenger as being restrained during the flight with duct tape. No further details about injuries or the specific aircraft involved were provided in the material reviewed. The investigation is being handled by the FBI, with no additional information on motives or the flight number disclosed in the aggregated material.

ABC7 New York adds context by reporting a separate incident involving a United Airlines flight that originated at Newark Liberty International Airport and was destined for Louis Armstrong New Orleans International Airport. In that account, a passenger allegedly claimed to have a bomb on board, triggering a security response and an in-flight alert. The primary assertion from ABC7 New York is that the passenger was arrested after making the claim and that the aircraft landed safely, with the individual taken into custody afterward. The material does not specify whether this United flight is related to the American Airlines diversion or to the broader incident.

Other outlets summarize the United Airlines case similarly but with varying emphasis on in-flight responses. The New York Post describes a hijack alert in connection with the bomb claim and notes that the alert was issued by the flight crew during the flight. However, the Post does not provide flight number, destination, or aircraft type, and it centers on the in-flight security response rather than verified injuries. Simple Flying aligns with the Newark-to-New Orleans routing and adds that ACARS messaging was reportedly used to notify other United departures about the threat as the situation unfolded, confirming a safe landing at Louis Armstrong New Orleans International Airport (MSY) but without additional details about the passenger or any injuries.

WDSU’s reporting places the United flight in a broader regional context by also mentioning a separate Frontier Airlines incident at Ontario International Airport. WDSU confirms the United flight’s core elements: a hijack or bomb-threat alert and a safe arrival at MSY, with no reported injuries or terminal evacuations tied to the United event. The outlet notes that the deplaning information beyond landing was not disclosed in their material and reiterates that authorities identified the suspect as being arrested at the airport. TheOntario incident reference underscores the concurrent security environment but is not described as part of the United flight’s outcome.

WWLTV.com reiterates the United Airlines scenario, describing a hijack alert after a passenger claimed a bomb, followed by a safe arrival at the destination. The outlet also mentions that other outlets describe related security incidents on different flights, including the Ontario situation, while cautioning that the MSY flight details do not indicate injuries or on-board events specific to the United case. This framing supports a multi-flight security narrative without asserting a direct causal connection between the cases beyond shared themes of in-flight bomb-threat responses.

NOLA.com specifically isolates the Ontario International Airport incident involving Frontier Airlines, noting that authorities conducted a broad security sweep after a passenger overheard terms associated with bombs during a FaceTime conversation. This account clarifies that the Ontario event is separate from the United flight to New Orleans and emphasizes ongoing security actions unrelated to the diverted American Airlines flight. As such, the material presents parallel but distinct security incidents rather than a single, unified incident affecting a single flight.