>>2522652 Underrated post. This looks to be huge. They MUST win in Nov. to avoid a cell or gallows. They CAN'T win straight up. So they WILL try and steal it, even knowing results will be audited. They will lose and be even further incriminated at the same time.
>>2524076
Cool correlation. Glad there's somebody looking for these kinds of matches. Thanks. Somebody want to make a QProof from this?
>>2524482 You did nothing wrong. Look at all the digs here --> >>2523770 and you'll see that flight history records are incomplete depending on which site you dig first, you'll find more or less info. The first site we dug on (flightaware) didn't have anything past May 8, 2018, but others got the data after checking multiple sites. Goes to show that planefagging often requires deeper than 1-level digging to get at the nuggets of info. It's hard!
Planefags are dogged and relentless.
R7
Sorry: these links are all l.b.
Yes, someone caught their flight path on Flightradar24. Pics reposted.
AZAZ0909 flew from Michigan to Kansas City. Looks like it touched down briefly, then turned and is now heading back in the direction of MI.
Planefag camped on AZAZ0909.
R7, over.
These short flights with short stops have to be for picking up or delivering people and/or cargo and/or urgent documents.
Thank you for top cover.
Curiosity!
Over.
There are 4, actually. Flying low, and def in formation. Radar does not indicate where the flights originated. They keep popping on and off of ADSB radar. We'll try to follow them.
Over.
(Virtually all) websites that offer flight history have incomplete data, and some ask you to pay for it too (planefags never pay; we just dig harder). Some sites are better than others. Some capture only commercial flights. I have yet to sort out which sites to use for which flight histories. Best advice I can give, from limited experience, is: If at first you don't succeed, keep digging.
Go sit on a badthing and have a badexperience.