So about 5 years ago I set up a receiver in the UAE and it worked great. About 3 years ago I left the country but kept the receiver running at my parents house and until about 6 months ago it was working fine. I just came back to visit and found that the micro sd was dying so I replaced it. But having done that I found something a bit weird:
I’m barely getting any ADS-B messages, its mostly just listed under “Other” in flightaware. In my local data, almost all aircraft are listed as TIS-B. Anyone else in the area noticed this, I looked at other receivers in the area and they seem to be doing the same? I’m guessing this is due to the current situation in the region, but what would be the reason for not broadcasting ADS-B from commercial aircraft?
Also having not messed with this for a while, I totally forgot how I set up my airspy settings previously. Previous SD card got corrupted and I couldn’t access anything. I probably won’t be back here for another couple years so I put in a brand new high endurance card.
GPS jamming/interference/spoofing - take your pick. As you allude to in your post, this has to do with the current situation in the area around your feeder. This is occurring in many places in the world right now and has been going on in some locations for quite some time (i.e. years). A simple Google search will provide links to GPS jamming maps to show where GPS signal coverage is compromised. Unfortunately, this has become the new normal and my amateur understanding is I do not know we ever go back to “normal” wrt GPS, but hopefully someone comes up with robust solutions to overcome the current problems.
I have a different take from dvsvejk as I am looking at your stats in graphs1090 and on flightaware. The graphs1090 shows that there are distances being reported but skyware is not showing them. Also in your own stats, it shows that most of your airplanes being tracked are not in Iran which due to the battle going on make logical sense.
Also, if you look at the global flight tracking pages you can see plans flying into the UEA and track them. Example that is live as of this writing is MEA 428 flying into Dubai at 21:08 +4. The track logs show ADSB logs
I don’t know why the display is not working but I think it is a display problem. have you tried checking from my ADS-B on Flightaware. That is what is being logged.
All the nearby sites listed on fishymamba’s stat page exhibit the same - lots of “other” positions with a steep drop off in ADSB positions happening in the 4-5 May timeframe and not recovering. It is not just him, but everyone around him.
I was looking at the example flight that I provide for MEA428 and the last ADSB report was maybe around 100km from Dhabi and everything went estimated location on FlightAware which give major evidence to GPS jamming. And based on the location of the receiver, it would be in the middle of that jamming location and there are a fair number of piaware in the Dubai area for every single one of them not to know where the plane is.
