Yes. See post #385 above, re database and live status.
Yes, there's a lot of junk posted there, but some posters are more reliable than others. This doesn't look like junk to me. The only pic that I...
Probably here... https://forum.flightradar24.com/threads/1871-Data-errors-in-Flightradar24-aircraft-database?p=118530&viewfull=1#post118530
:)
A [miscoded?] TEX2 is what I reckon, too.
Unfortunately, that's correct. I've already added most of these hexes to the database in recent months, but due to technical problems, the...
You must be reading one of my posts elsewhere...;)
Used callsign 161846 , last month.
AE4C63 usually has been using RONIN and SHADY callsigns, but for a couple of days in September 2018 it used R00289.
Should be 18-21029 by sequence. 18-20988 possibly miscoded.
Wasn't this re-regd from EM-7095 to OR-3129 ?
60-0059 would have been my guess, if I had to. We'll have to wait and see, I think.
I've not seen that reported anywhere else. Is it confirmed? It looks out of sequence, but that don't always follow.
I see that it's been flying out of Leeuwarden this week, participating in Frisian Flag 2019, but 4076 should be 48D8A4, so looks like a miscode.
Already in, thanks James. AE587D had previously been reported as 60-0061, and will show as such on live pages until the d/b gets reloaded live-...
Correct hex is A0FD39, but it's miscoded ADFD39 Already in the database.
UH-1D data removed. Tactical hex codes change too often, so it's not worth adding any new ones to the database. It's still worth posting the data...
email sent, James.
Database updated, thanks. Don't expect it to go live anytime soon, though. :rolleyes: It's actually a miscode, and should be using 44F6A3.
Callsign VCM95A. More likely to be Venezuelan?
Separate names with a comma.
