United Airlines Flight Makes Sudden U-Turn After Crew Member Spots Disturbing Messages

A United Airlines flight heading to New Jersey was forced to return to Las Vegas after a flight attendant reportedly spotted a passenger sending messages about hijacking the aircraft. The discovery prompted the pilot to change course, cutting short the journey before the plane could reach its destination.

United Flight 1681 was carrying 150 passengers and six crew members when the incident unfolded on October 24. The aircraft landed safely at Harry Reid International Airport, where police responded and arrested a 25-year-old man on suspicion of making threats or conveying false information concerning acts of terrorism. Passengers were later transferred to an alternative flight, which departed the following morning.

Flight Attendant Spots Messages That Triggered Alarm

United Flight 1681 departed Harry Reid International Airport in Las Vegas, bound for Newark Liberty International Airport in New Jersey. The Boeing 737 was carrying 156 people when a flight attendant reportedly noticed a passenger sending messages that referenced taking control of the aircraft.

The crew member quickly alerted the pilot rather than confronting the passenger directly. The discovery prompted an immediate change in the flight’s plans, with the pilot deciding to return to Las Vegas instead of continuing toward New Jersey

The pilot described the situation during a conversation with an air traffic controller shortly after takeoff. “The flight attendant saw him texting that he was going to hijack the aircraft. They called me. We went into lockdown, and we returned to Vegas,” the pilot said.

The reported messages raised a serious security concern while the plane was airborne. However, the available details do not establish the complete contents of the messages or whether the passenger had taken any steps to interfere with the aircraft.

Pilot Explains Why the Plane Returned to Las Vegas

The pilot’s communication with air traffic control revealed how the crew handled the reported threat. After learning what the flight attendant had observed, the pilot chose to bring the aircraft back to the airport, where authorities could respond on the ground.

During the exchange, the air traffic controller asked whether the passenger was cooperative or being restrained. The pilot reportedly replied that there was “no restraint” because the traveler was unaware of the situation.

That detail suggests the crew had not directly confronted the passenger at the time of the communication. The available account does not explain precisely what security measures were taken inside the cabin or whether the passenger knew the flight was returning because of the reported messages.

The aircraft eventually landed safely at Harry Reid International Airport at approximately 11:05 p.m. local time on Saturday, October 24. The Federal Aviation Administration described the incident as a passenger disturbance reported by the crew, while the circumstances surrounding the alleged hijacking messages remained subject to investigation.

Police Arrest 25-Year-Old Suspect After Landing

Following the aircraft’s return, the Las Vegas Metropolitan Police Department responded to the airport. Officers arrested 25-year-old Dante Milne on suspicion of making threats or conveying false information concerning acts of terrorism.

The arrest marked a significant development after the reported messages prompted the flight to turn around. Authorities were able to respond once the aircraft was back on the ground, allowing the incident to move into a police investigation.

The reported allegation does not establish that an attempted hijacking took place. The available information also does not confirm the suspect’s intentions, provide the complete contents of the messages, or establish whether additional charges were filed.

Further details about the investigation, including any evidence recovered from the passenger’s phone and the status of potential legal proceedings, were not included in the original account. The distinction between a reported threat and a proven offense remains important as investigators work to establish what happened.

Passengers Face an Unexpected Overnight Disruption

For the 150 passengers aboard the flight, the return to Las Vegas meant an abrupt change to their travel plans. Instead of continuing to Newark as scheduled, they found themselves back at the airport late on Saturday night.

After landing, passengers who were removed from the flight and the aircraft underwent a comprehensive inspection, according to the reported account. The available information does not specify exactly what the inspection involved or whether investigators identified any additional security concerns.

United Airlines arranged an alternative flight for the affected travelers. That replacement flight departed from Harry Reid International Airport on Sunday morning, allowing passengers to continue their journey after the overnight disruption.

Although the original flight did not complete its planned route, the reported outcome was that the aircraft returned safely and passengers were provided with another flight. Details about individual passengers’ experiences and the length of their wait were not available.

Why a Reported Hijacking Threat Can Prompt an Immediate Return

A message suggesting that someone intends to hijack an aircraft can create a serious security concern, particularly when it is discovered during a flight. Pilots and cabin crew must assess information that could affect the safety of everyone onboard, even when the full circumstances are not yet known.

In this case, the reported sequence was straightforward: a flight attendant noticed concerning messages, alerted the pilot, and the aircraft returned to Las Vegas. Police then arrested a passenger on suspicion of a threat-related offense.

However, a reported threat and an attempted hijacking are different events. The available account does not establish that the passenger attempted to seize control of the plane, threatened other travelers directly, or physically interfered with the crew.

The investigation must establish the context of the messages and whether they represented a genuine plan or conduct that violated the law. Until those details are confirmed, the allegations should be treated as allegations rather than proven facts.

What Remains Unknown About the United Airlines Incident

The safe landing brought the immediate flight disruption to an end, but several questions remain unanswered. The complete contents of the reported messages have not been established in the available account, and there is no confirmed explanation of what prompted the passenger to send them.

It is also unclear whether investigators found additional communications or evidence that clarified the passenger’s intentions. Details about any subsequent court proceedings or the final outcome of the investigation were not provided.

The reported arrest and the pilot’s account explain why the flight returned to Las Vegas, but they do not establish that a hijacking attempt occurred. Further information from the investigation would be needed to determine the precise nature of the alleged threat.

For the passengers, the immediate priority was reaching their destination after an unexpected interruption. For investigators, the next step is establishing exactly what the messages meant and whether the conduct behind them amounted to a criminal offense.