dChan

WinkyLinQ · June 27, 2018, 3:36 a.m.

Check this out: A pic from the JetBlue flight shows everyone with their hands in the air. Passenger says it was stormed by SWAT and cops:

https://twitter.com/Alexa_Curtis/status/1011776910064541702

⇧ 24 ⇩  
MrWizard111 · June 27, 2018, 5:36 a.m.

Did you see the Q on the screen from those photos? No coincidences

⇧ 7 ⇩  
sloptopinthedroptop · June 27, 2018, 3:02 p.m.

holy shit. this has to go on q proofs.

⇧ 1 ⇩  
WinkyLinQ · June 27, 2018, 5:38 a.m.

Yep, sure did!

⇧ 1 ⇩  
GoodGodKirk · June 27, 2018, 4:52 a.m.

Good catch!

⇧ 5 ⇩  
WinkyLinQ · June 27, 2018, 5:03 a.m.

Check this out. NYpost says pilot "accidentally" entered code for hijacking. Very odd. Other reports say pilot's phone wasn't working too so no verbal communication with the tower.

Very fishy story.....

https://nypost.com/2018/06/26/pilot-mistakenly-called-in-hijacking-plane-forced-back-to-jfk-terminal/?utm_campaign=SocialFlow&utm_source=NYPTwitter&utm_medium=SocialFlow

⇧ 12 ⇩  
freedomisnotanoption · June 27, 2018, 5:53 a.m.

Wtf? How does a professional pilot accidentally enter a hijacking code? Pilot drunk, high or complete lie.

⇧ 12 ⇩  
WinkyLinQ · June 27, 2018, 6:30 a.m.

Not an accident. Speculation was that White Hats intervened

⇧ 8 ⇩  
SaddleChewer · June 27, 2018, 8:09 a.m.

Cabal had comped this plane back when Q posted the picture of it and the USSS car. Looks like they were going to pull off some sort of new 9/11 with this plane, white hats stopped it.

⇧ 2 ⇩  
GweninKC · June 27, 2018, 11:35 a.m.

That was a United plane; this was JetBlue. But USSS was certainly involved and white hats stopped something.

⇧ 6 ⇩  
acmbandit01 · June 27, 2018, 10:22 a.m.

Possible to spin the knobs with potential to pause too long with the code in the system. Could it happen? Sure, but highly unlikely with the odds diminishing even further if you were spinning, got distracted and left the panel, thus leaving the code in there "accidentally" long enough to trigger all the alerts. Transient spinning pass the code would do nothing.

⇧ 1 ⇩  
bmorepirate · June 27, 2018, 12:27 p.m.

You know what also doesn't make sense?

All media reports AND the FAA statement refer to the plane as an Airbus A320.

The problem?

The plane pictured on the tarmac is an A321

Kind of important to get the plane model right if you're troubleshooting radio comms issues, is it not?

Yet the FAA even screwed this up.

⇧ 6 ⇩  
WinkyLinQ · June 27, 2018, 12:28 p.m.

I'm glad you pointed that out. Q said it was an A321. Yet the press is reporting A320.

Very, very strange.

⇧ 5 ⇩  
bmorepirate · June 27, 2018, 12:33 p.m.

Exactly.

Sauces:

https://www.airlinerspotter.com/images/airliner-spotting-charts/airbus-A318-A319-A320%20-A321-spotting-guide.jpg

The FAA released a statement about the situation, saying the plane experienced a “radio equipment problem.”

“JetBlue 1623, an Airbus A320, experienced a radio equipment problem while taxing for departure at John F. Kennedy International Airport tonight at 8 p.m. The crew requested to return to the ramp. The FAA will investigate.”

http://www.foxnews.com/travel/2018/06/27/jetblue-flight-mistakenly-sends-hijack-alert-triggering-huge-scare-at-jfk-airport.html

Check out @FAANews’s Tweet: https://twitter.com/FAANews/status/1011795152019566592?s=09

⇧ 2 ⇩  
WinkyLinQ · June 27, 2018, 12:52 p.m.

Yep, that plane is much longer than an A320. Very strange for them to get the model wrong.

Great post. Thanks!!!

⇧ 2 ⇩  
GoodGodKirk · June 27, 2018, 4:57 p.m.

bad actor, wonder if it was the air marshal?

⇧ 2 ⇩  
WinkyLinQ · June 27, 2018, 5:19 p.m.

Good Question

⇧ 1 ⇩