American Flight Diverts After Nosy Passenger Causes Bomb Scare

Several days ago, I wrote about (what I’d consider to be) a ridiculous situation, whereby an American Airlines flight diverted due to a text that a passenger sent. When I first wrote about this, I mentioned that I was curious what the air traffic control audio was like from this incident. Well, now we know, so I’m updating this post to add that…

American flight returns to San Juan over “RIP” test

On Thursday, July 3, 2025, American flight AA1847 was scheduled to fly from San Juan (SJU) to Dallas (DFW). The flight was operated by an Airbus A321 with the registration code N902AA, with 193 people onboard.

The plane took off at 6:26AM, and flew for a little over 10 minutes, climbing to just over 16,000 feet. However, at that point, the plane turned around, and diverted back to San Juan. It landed there safely just over 30 minutes after departure, at 6:58AM.

American flight AA1847 returned to San Juan

While flights return to their origin all the time, the cause of this incident was anything but ordinary. As it turns out, the plane diverted because a passenger observed another traveler receive a text message saying “RIP” (rest in peace), and interpreted that as a threat to her flight. So she reported that to the flight attendant, and it was ultimately interpreted as a bomb threat, causing the diversion.

In the air traffic control audio posted online, here’s part of the dialogue:

American pilot: “We are declaring an emergency. We’re gonna do an overweight landing here on the runway. You know, we have a threat onboard with text messaging between passengers and flight numbers, so we’re gonna need authorities at the gate to meet us to figure out exactly what’s going on here.”
Air traffic controller: “Is the cockpit secure?”
American pilot: “Cockpit is secure. We just have a threat from out back. We’re not sure if it’s even credible or not at this point. But, you know, the way the things are, this holiday weekend and everything else, we figured the best course it’s just to be as safe as possible.”
Air traffic controller: “And they wanna know the level threat.”
American pilot: “We have, we’re checking right now. We are at a possible level three, so we’re treating it like a level three at this point.”

For those curious, a level three threat is one with “life threatening behavior.” The only higher threat is a level four, which is an “attempted or actual breach of the flight deck.”

Once the plane was back on the ground, airport security personnel and the TSA boarded the aircraft, to inspect it and interview passengers. The passenger who received the “RIP” text message was able to prove that a relative had died the day before, and that’s why he was taking the trip.

An airport official clarified that “it was a mix-up that was handled in accordance with safety protocols,” and that “there was no real threat to the flight or its passengers.” The flight ended up departing again at 9:40AM, just under 3.5 hours behind schedule.

The flight status for AA1847

Who is at fault for this absurd diversion?

Perhaps hindsight is 20/20, but I think we can all agree that a diversion over a simple text message containing the term “RIP” is ridiculous. But who is really at fault for this diversion?

Of course there’s the snooping passenger, who decided to report this in the first place, and set off this whole chain of events. We always hear the motto “if you see something, say something,” though all too often, that’s used by clueless people to simply make claims reflecting their own biases.

I’d argue that the party really at fault for this diversion is the crew, for taking this seriously. I wonder, did the “concerned” passenger really just share what she saw? Did she tell the flight attendants “hey, I saw someone texting the term ‘RIP,’ I think they must have a bomb?” And then the flight attendant was like “yeah, wow, that’s really concerning, let me call the captain, we need to divert immediately?”

I think this also reflects the “better safe than sorry” approach that so many airline crews take. They’ll never get in trouble for erring on the side of caution, but if they ignore something that ends up becoming an issue, that’s more of a problem for them.

This is reflected in what the pilot told ATC. He acknowledged he wasn’t even sure if the threat was credible or not, but “you know, the way things are, this holiday weekend and everything else,” it’s best “just to be as safe as possible.” With that logic, you might as well just divert every flight!

What really amazes me is how quickly all of this happened. The plane started turning back toward San Juan just 11 minutes after takeoff. So during that short, critical phase of the flight, the passenger noticed the text message, alerted the flight attendants, the flight attendants alerted the pilots, and the pilots made the decision to return to San Juan? That’s all very fast.

Bottom line

An American flight returned to San Juan just over 30 minutes after takeoff, for a bizarre reason. A passenger was snooping on the texts of a fellow passenger, and saw them receive an “RIP” text. Somehow that ended up being interpreted as a bomb threat, causing the flight to divert. I simply have no words. I’m not sure if it’s worse that the passenger reported this, or that the crew acted on it…

What do you make of this American diversion?

Conversations (30)
The comments on this page have not been provided, reviewed, approved or otherwise endorsed by any advertiser, and it is not an advertiser's responsibility to ensure posts and/or questions are answered.
Comment as a member

Membership is free and takes no more information than commenting as a guest. Earn status points for good contributions, and see fewer ads as your status grows.

Type your response here.

If you'd like to participate in the discussion, please adhere to our commenting guidelines. Anyone can comment, and your email address will not be published. Register to save your unique username and earn special OMAAT reputation perks!

  1. Loading comments…
Recent Comments
The latest from the OMAAT community.

The comments on this page have not been provided, reviewed, approved or otherwise endorsed by any advertiser, and it is not an advertiser's responsibility to ensure posts and/or questions are answered.

Munk-E Guest

Ridiculous diversion! This is not even the passengers own text; if it was the passenger's own text, I wouldn't blame them directly, but this was someone else's text! The flight attendants should have carefully thought through on if the bomb threat was even real to begin with, rather than diverting out of unnecessary fear. Even then, it's understandable why the flight diverted back. This nosy passenger could have costed all the hundreds of people's lives on the plane, with the flight already flying over the ocean; and they also caused a delay for the hundreds of people going to DFW (and possibly those with a tight layover of <1 hr at DFW) over a text that isn't even theirs. The passenger should be fined at minimum $10,000 if not more for causing potential danger on the plane, and for delaying people's flights; punishable under the Espionage Act of 1917. The Espionage Act of 1917 pertains to the passenger who falsely proclaimed of a non-existent bomb threat, in which the passenger " ma[de] or convey[ed] false reports or false statements" that "interfere[d] with the operation or success of the military or naval forces of the United States", namely the pilot on the American Airlines flight at that moment. Furthermore, the Supreme Court case of Schenck vs. United States (1919) found Charles Schenck guilty and charged him with conspiracy in violation of the Espionage Act of 1917 for mailing printed circulars critical of the military draft for World War I. The extent of danger to which the passenger's action of causing a whole flight diversion is analogous to the Canonsburg Opera House Disaster on August 26, 1911, in which a false shout of "fire" in response to a projector malfunction from a motion picture caused a sudden flash that triggered a panic that killed 26 people. Furthermore, the Canonsburg Opera House Disaster would also qualify as a violation of the Espionage Act of 1917 since the false alarm of fire "interfere[d] with the operation or success" of the theater, in which "false reports or false statements" on the nonexistent fire was made. The Supreme Court case of Schenck vs. United States (1919) would apply to the passenger that incited the diversion of the American Airlines flight with such similar circumstances to Charles Schenck pleading guilty. In conclusion, the passenger inciting the diversion should be charged with conspiracy in violation of the Espionage Act of 1917, supported by the Supreme Court case of Schenck vs. United States (1919), with the passenger's inciteful act punishable with a minimum fine of $10,000, under the Espionage Act of 1917.

0
‼ 0
Vic Guest

I work for an engineering services business. We are repeatedly warned to not use the short form of Bill Of Materials when not in a work meeting or if not on site. Slip ups still happen though.

0
‼ 0
Kevin Guest

What's next, someone working on the secret al-gebra code going to be imprisoned or detained? O wait, that has already happened. This is what happens when the US lacks in education.

1
‼ 0
LAXLonghorn Guest

I don’t think anyone was at fault. Innocent text message expressing sympathy. Fellow passenger misread it (even if it wasn’t any of her business), and expressed reasonable concern. FAs should absolutely not have engaged with the passenger with the text message as that could have escalated and activated a potentially serious threat. Pilots were also in the right, and along with the FAs should be commended for their quick response.

0
‼ 0
BKH Guest

The busybody nosy pax is at fault. And the FA could have handled it better

1
‼ 0

Save posts to read later

Saving posts is a member feature. Become an OMAAT member to build a reading list you can come back to from any device.

Become a member
Meet Ben Schlappig, OMAAT Founder
5,883,136 Miles Traveled

43,914,800 Words Written

47,187 Posts Published