Database Update Requests

[Runway 31]

Thanks Mike

Alan

[Runway 31]

Thanks Terry

Regarding your second post apart from one miscode the majority (Canadian/French/German/British/Swiss) are valid hex/reg tie ups from the country sequence and have no other details attached to them in the database as they have not been reallocated since de-registration.  As such they will be staying as is as hex/reg tie ups until they are reallocated

Alan

[Runway 31]

Thanks Michel

Alan

[CarlosAbreu]

Alan

04-12-2023 Updated file in attach.

Carlos

[Runway 31]

Thanks Carlos

Alan

[CarlosAbreu]

Alan

05-12-2023 Updated file in attach.

Carlos

[Runway 31]

Terry

N281X is an RV8 and is in the d/b as such maybe a typo?
Not all de-regs will be left with the hex/reg tie up applied only certain ones (normally biz jets) per an Airnav customer requirement

Thanks

Alan

[Runway 31]

Thanks again Terry

Alan

[CarlosAbreu]

Alan

06-12-2023 Updated file in attach.

Carlos

[ffa1978]

600082 EW-557TG Antonov An-26b Genex

[sples]

https://www.radarbox.com/data/mode-s/855188
855188 is the decimal format of the hexcode 0D0C94, and 0D0C94 fits the Mexico range, so pls correct it.

[Runway 31]

Thanks Carlos

Alan

[Runway 31]

Thanks ffa

Alan

[Runway 31]

Thanks Terry

Alan

[Runway 31]

Hi Spies

Unfortunately the hex code comes from the transponder of the aircraft and in this case the transponder is wrongly coded.  Nothing we can do about it, it will require the airline to have the transponder recoded correctly

855188 (decimal) decodes to 0D0C94 octal and it is in the database as such awaiting them correcting the transponder, however it was delivered out of TLS on delivery as VIV001 using 885188 on 1st August 2020 so i wouldnt hold your breath

Alan