DIG to find RADAR TRACE of Q400 CRASH

(not found yet)

>>2575411 lb

>>2575382 lb

Last flight history for Bombardier Q400, unauthorized takeoff from SEATAC circa 8pm PDT on August 10, 2018

This flight log from

https://flightaware.com/live/flight/N449QX

is actually quite baffling.

This plane routinely made a 30-minute flight between Victoria, BC and Seattle-Tacoma International. On Friday August 10th, the log says it flew to Victoria and then, supposedly, the return flight was CANCELLED the morning of 8/10. So HOW did the plane get back to SEATAC in order to be hijacked by Rich? (I know some anon mentioned this earlier but I wasn't paying attention, sorry. I am now!).

One wonders if the log is correct.

I need to check some more websites for logs.

So far I have not found a radar trace of the ill-fated flight.

I'll keep digging for while....

R7

>>2575566

OK part of the mystery solved (diff. sites have diff. flight history data).

https://www.flightradar24.com/data/aircraft/n449qx

has one additional flight. The 9:30 AM from Victoria to SEATAC on 8/10 was cancelled, but the plane flew to SEATAC at 11:15 on 8/10 and arrived at noon.

So that explains how it got to SEATAC prior to the 8pm hijacking.

Unfortunately this site doesn't have a radar trace of the ill-fated flight either.

Digging continues.

>>2575631

Right. We ignore the sheriff's helicopter.

I wonder if it's possible to find a radar trace based on passive radar echoes, regardless of whether the plane's transponder was turned on…

• Did this plane have an ADSB transponder?

• Was it turned on?

• Does it turn on automatically when the engine is on?

Really have a bunch of technical questions and I'm not a pilot so bear with me while I dig. Dig with me if you like, would appreciate planefag companionship on the journey…

R7, over.

>>2575708

Appreciate the input, pilotfag.

That's what I was afraid of.

So far have not found anything.

Still digging.

Found its registration while looking for ICAO # to try a different radar site.

>>2575747

This is a valid line of inquiry. If we can find a radar trace it would be relevant. If we can't, then we can rule out getting any info from radar. One way or the other, we need to do due diligence to see if we can find a radar trace. After a while if we can't find anything we'll declare "not found after due diligence." Let the planefags work. Serious planefag digs are not slides but attempts to silence us are.

>>2575829

Here's an article about the incident. I got the tail number from that.

https://airwaysmag.com/uncategorized/breaking-horizon-air-q400-stolen-crashes-near-seattle/

I am striking out searching for flight history and radar trace of the supposed ill-fated flight.

I don't believe anything until well-sauced and there is too much contradictory info about the incident. I am feeling that if /whitehats/ did it, perhaps by remote control, they PURPOSELY left a huge broad trail of breadcrumbs forcing the MSM to cover the story, while temping the public to doubt the official stories out of MSM.

There were a couple(? at least 1) report on the bread yesterday afternoon/evening of a Pacific Northwest resident whose wife heard a loud sound overhead during the time when the incident supposedly occurred. I'd like a timestamp and detailed report on this purported eyewitness info.

Over.

>>2575747

<flown away from the scene

Your thinking isn't clear.

We're not asserting that the plane escaped from the crash site – or that it didn't.

All we want to know is whether there exists a radar trace of the plane's flight from takeoff to wherever the radar trace ends. Even if a trace is found, we will still have questions about whether the data is real or phoney, and how its authenticity can be proven or disproven. Planefags are very very skeptical! So far we are finding no radar traces, and evidently if the transponder was never turned on, then civilian logs will not have any data on the flight.

However even if civilian logs exist, we will doubt them until proven, because we KNOW that military special ops has the ability to inject data into networks and databases, and would do so if necessitated by military orders in a national security situation.

So do not tell us to stand down. It's not your call.

>>2575631

We saw 3.5 min of video from a local TV station yesterday. It appeared to be from a drone circling the crash site. Some debris was visible through the very dense evergreen trees, and some people and lights were visible on the ground. Multiple trees were sheared off at the same height, consistent with a possible crash trajectory. But the quantity of debris appeared small. It was hard to tell through the trees. There was a plume of smoke, and we have seen a news article that firefighters are working a wildfire at the crash site.

Here's that video I'm talking about. Decide for yourself.

https://www.king5.com/video/news/local/skyking-video-fire-still-burning-on-ketron-island-after-stolen-plane-crashes/281-8217242

>>2576034

I resolved how the plane got back from Victoria BC to Seattle. Here →

>>2575636

>>2575943

The Alaska Airlines – Horizon Airlines thing doesn't bother me. Airlines do this thing called "code sharing" where the same plane basically works for different airlines and uses their callsign. Registration Numbers do not change and are linked to the plane's owner. Callsigns indicate who is operating the plane at a given time and change with every takeoff for commercial flights.

>>2575892

>>2575999

That is a diagram. Who made it? Where did it come from?

This is where someone WANTS us to think the plane went. We don't have to believe it, but knowing that someone WANTS us to think this is relevant to the investigation into what really happened.