Database Edit Requests

ADFFB2
64-13222
T38
T-38C Talon
USAF

 

ADFF0B currently in the database as T38 64-13206.

This would appear to be incorrect. Possibly a miscode at the time?

Hex would suggest a TEX2, and it's been flying out of Pensacola, as JEDI63, along with a bunch of other TEX2s using JEDI callsigns.
https://tar1090.adsbexchange.com/?icao=adff0b&showTrace=2020-03-30

Possibly 95-3009, [455th FTS, Pensacola] but that's just a calculated guess.

 

Database error...

AE14A9 in the database as N819AE

This BE9L should be 160853

 

AE622D
69-6613
UH1
UH-1N Iroquois
USAF

 

Database error...

AE0023 in the database as 67-14851

T38 should be 67-14922

 

Database error...

AE00ED in the database as 70-1566

T38 should be 68-8142

 

AE64A9
19-21078
H60
UH-60M Black Hawk
USARMY

 

AE5790
14-20672
H60
UH-60M Black Hawk
USARMY

 

AE6247
69-6665
UH1
UH-1N Iroquois
USAF

 

AE633B
17-72451
EC45
UH-72A Lakota
USARMY

FY17 unconfirmed

 

AF351F is a miscode F-35 default hex code for multiple nation's, not just RAF aircraft.

 

Hi Wiedehopf, I attempted to establish contact with "cab" but alas, no response has been forthcoming. I am unable to proceed until the problem has been fixed, specifically: terminating the Planebase overwrite function. All changes made to fix their errors have been reverted back. This has happened on at least two separate occasions now so I guess must be happening when the database administrator imports the latest Planebase sqb. I know in VRS config there is a setting to automatically pull the latest database from the Planebase server and also settings to enable/disable overwrites but since VRS has been ditched in favour of tar1090 I have no idea if this is still a 'thing' in your version.

 

Today, AF351F is shown as 13-5067!

 

Skymaster: this is once again a problem with the third party database they are using. I have checked "our" database and it shows the following data, which I believe is your original entry from some time ago judging by the comment :

13222061 ~ AF351F ~ F35 ~ Lockheed Martin F-35 Lightning II ~ Various ~ Used by various F-35A's and B's

The registration field between the hex and type code is blank.

 

Yes, that's probably one of my entries.

Ideally, the reg field should show as 'Various'

 

Can we not have a google form that takes updates in a consistent format, allow for notes, and then we can actually compile a list what needs updating . This 32 pages of bullshit provides no real way to consolidate the updates even if we *get* a method to update.

And on that note how does no one here know where the data comes from? It either comes from planbase (which is useless as no one can become a member unless another member recommends you) and the 1090tar or what ever seems to be a cluster fuck also.

It’s not difficult to write an import that gets the data, and shitcans any records that are older than the local copy’s timestamp.

Then write a import to take the spreadsheet from the google form that has correctly formatted fields, and light that up after it has been reviewed by members on adsbx.

Is this not a better solution? Or path to one?

 

4CC517
TF-ORI
Eagle air Iceland
Dornier 328-110
civil

 

P4 NGK
is in the database as from The Kingdom of the Netherlands, this is incorrect.
This registration belongs to the Czech Republic

 

Complete rubbish!

 

48605B
PH-LLN
ANWB Medical Air Assistance
Airbus H135 P3
civil

Arrival images