Flight Records Indicate A Covert Helicopter Rooftop EXFIL May Have Taken Place Just Minutes After Las Vegas Massacre
BY Herschel Smith
7 years ago
LAS VEGAS (INTELLIHUB) — Flight records and information obtained by Intellihub show that at least one assailant may have been extracted via helicopter for a 10:21 p.m. EXFIL from the southwest rooftop of the Delano Hotel just four minutes before Las Vegas Metropolitan Police Department helicopter N911WY arrived in the vicinity for the first time since shots were fired at crowd goers attending the Route 91 Harvest Music festival around 10:05 p.m., as the timeline indicates.
Even more disturbing is the fact that the aircraft’s transponder was transmitting the call sign “SWA4119” which is registered to a Southwest Airlines Boeing 737-7H4 passenger jet with the tail number “WN4119.”
According to the data, SWA4119 was originally scheduled to depart Tulsa (TUL) at 14:10 and arrive in Las Vegas (LAS) at 15:00 but was somehow delayed for over 7-hours giving “SWA4119” a new arrival time of 22:22 (10:22 p.m.) which doesn’t make sense because the craft was headed north and was too close to the airport to be aligned with any of the runaways.
You see, the aircraft that was displaying “SWA4119” between 10:21 and 10:22 p.m., which emerged on radar for the first time at 10:21, absolutely can not be a passenger jet because the actual flight data confirms that the aircraft slowed to a stop then changed its direction abruptly to a due north heading before proceeding to hover over the Delano in a very specific spot for approximately one-minute (i.e. the craft in question was, in fact, a helicopter because jets simply cannot hover or change speed and direction with such intensity.) This means that the operators of the craft were intentionally transmitting a fictitious call sign before going dark (invisible) from radar altogether.
To top it off, the Oct. 1 flight data for Southwest Airlines “WN4119” is showing inconsistencies.
The following screen-capture of the the aircraft’s flight history shows that “SWA4119” landed at 10:22 p.m. at (LAS) despite the fact that a transponder was pinging from the rooftop of the Delano at that exact same time.
Not to mention, the tail number listed for that exact flight is “N227WN” and not “WN4119” as the transponder was emitting in real-time suggesting that the plane on the tarmac that “landed” was “N227WN” which is a different aircraft entirely.
Thanks to reader B Bauch for this tip. Go read the rest at Intellihub, and make sure to watch the video he has embedded of official radar the night of the Las Vegas shooting.
I’ve been saying all along that while I don’t have a particular pet theory for what happened, the FedGov account could not and did not happen. The more we find out, the more my view makes sense.
You won’t find anything else out from the FBI or the Las Vegas police. The police have been shut down by the FBI, and the FBI doesn’t want you to know what they know about it.
|
|
On October 31, 2017 at 12:41 am, Ned said:
Saw this a day or so ago along with the flight radar video. Welcome to the same old world of WTF, and how many lies can our (((masters))) tell us.
It appears that whomever concocted and pulled off this mess counted solely on the MSM to bolster the story, and though that would be enough. Too bad for them that there is some real journalism taking place in the interwebz.
Almost no one trusts the FBI anymore. Las Vegas PD showed their colors long ago. The FIBBIES apparently spend all their time spying on us, and helping to cover up for the shadow government. Likely telling LVPD what to say as well. Too bad they changed the narrative so many times that even true believes think they’re full of crap.
I also saw a video someone took of FBI cleaning up the site the next day. Looked like a professional cover up. There’s so much crap flying around, I can only conclude false flag. Certainly can’t believe the government.
I wonder how many people actually died.
On October 31, 2017 at 6:55 am, J said:
I have used that radar/app to track a inbound family members flight.
I isn’t realtime (Visualy$,for obvious reasons, what i can’t remember, is if the Time Stamps are accurate with the visual landing of the aircraft.
No I am not a MSM narrative believer.
I am just putting out there what inhabe experienced with that Radar/App.
The answer to my question is easily found out, take a trip toa airport.
On October 31, 2017 at 9:28 am, Phelps said:
@j: These sites are all fed with private ADSB receivers. I run one of them.
So there are two ways to get the data. Some of the planes transmit their position constantly (ADSB), and those are pretty accurate and up to date. Helicopters tend to do this, because they are a lot more likely to be in unexpected places and need to be visible. The others only transmit their location in response to the tower asking them to, like a ping. That ping is only good for the tower to figure out where they are.
For these, you use multiple sites to listen for that ping, and triangulate the position. This is MLAT (mutlilateralization or Time Difference of Arrival). These can often lag behind, because they rely on the tower interrogating, then the reply, and then the calculation from multiple receivers to figure out where in the hell they are.
So, that’s a long way of saying there are two ways to tell what is going on, with various degrees of accuracy, along with a time delay from the website to aggregate all of the data, decode it, and then display it. I suspect there is a 5 minute or so time delay on flightdata.com (prob some stupid security concern) that you don’t see on your private receiver, and that gets pulled back out of the data in the historical view. I just compared my live view on my reciever to flightradar24, and it’s balls-on live. FR24 seems to be a more accurate site.
So looking at the comparison, I think I am going to start feeding FR24. They don’t do the censorship FD does (for example, FD won’t show FBI surveillance planes on the website, even when I see them on my reciever) and FR24 offers longer historical views. Once I’ve switched over, I’ll have my premium account there (they give you a free account for feeding the site) and I’ll look at this data myself. (FD has already put it behind the ala carte paywall.)
On October 31, 2017 at 11:03 am, revjen45 said:
I find it interesting that these high visibility mass shootings seem to occur at the times when gun-related legislation is under consideration.
On October 31, 2017 at 11:52 am, infoman said:
Air traffic control tapes on the night of the Las Vegas shooting:
“There’s active shooters on the runway. They’re on the airport property”
https://twitter.com/MikeTokes/status/924508300783185921
On October 31, 2017 at 4:25 pm, JFP said:
If I recall correctly the flight tracker sites have to delay data by 5 minutes on their websites. I think FlightAware does but it has been awhile since I looked into it. ADSB sure does make things interesting. $20 for a usb tv/radio receiver and $50 or so for a raspberry pi (or your laptop) and you have a nice little virtual radar setup.
On October 31, 2017 at 9:34 pm, J said:
@Phleps..
Thank You for that Info.
In all Honestly, now i will start to learn about some of what you were explaining.
Again, much Thanx for the….Primer Course.
J