Database Update Requests

[EK01]

Morning Alan,

RYR97ZN : LEAL-EGPH
RYR81AR : LIMC-LEZL
RYR51SL : GCFV-LIME
TVF86BB : LFPO-GMFF
TRA9P : EDDM-LEAL
RYR677B : LIME-LEAL
RAM730K : GMMN-LFML
EIN573 : LEAL-EIDW
DLH1332 : EDDF-GMMX
GMI2224 : EDDC-GCLP
IBK5151 : LIRF-LEMG
EZY91YZ : EGPF-LEAL
EZY61XL : EGNT-LEAL

Ian

[Runway 31]

Cheers Ian, that's them back in, thanks again

Alan

[EK01]

Alan,

Another couple plus a non-populator :

MON672 : EGCC-LEAL
VKG1764 : ESGG-GCLP

AE5747

Ian

[Runway 31]

Ian

AE5747,13-2017,31400217,Embraer A-29A Super Tucano,US - Air Force en-route of Afghan Air Force

Thanks again

Alan

[neroon79]

I'll check msg count later. But I checked the log mail for second entry of the flight id: non found. I suspect the same aircraft you came up with, so I checked that hex too. Same result: not listed in the log mail. As it is extremely uncommon, that a bad packet received entry occurs without an additional valid  entry, I would suggest a miscode at this point.

I'm on my way back to Hannover, so checking message count is currently impossible. (ICE @ 200 km/h +)

Ingo

[Runway 31]

Thanks Ingo, hear from you later and update after your check

Alan

[chris]

Hi Alan.

Can you shed any light on this one please.

A3C2AD  BTLCAT2                                                        2017/03/10 10:06:30 
A3C2AD  BTLCAT2                                                        2017/03/10 10:52:40 

Regards

Chris.

[Runway 31]

Hi Chris,

I would suggest that it is Puma ZJ954 out of Benson miscoding as it should use 43C2AD

Alan

[neroon79]

Hi Alan, back home and I checked 411E28:

First received at 6875ft / 51° 30.3'N 12° 5.4' E ( so it came from EDDP)
Last received at FL330 / 52° 14.0'N 14° 9.1'E out of EDDP it is a NE heading

Reception was on the outer NE to SE circle of my range.

569 messages with ADS-B received. Considering the flight path the received message count is the maximum possible count. If the airframe would ever have sent a correct hex on this path I would have received it.

From my point of view a 99,999% chance, that it was 451E28 miscoded or a new unknown airframe.

Ingo

[EK01]

Afternoon Alan,

CFG7PE : GCTS-EDDS
NLY696J : LOWW-LEMG
RAM221 : UUEE-GMMN
JAF5479 : LFML-GCFV
IBE32FB : LEMD-LIRF
ENT5235 : EPKT-GMAD
EXS75T : EGPH-LEAL
PRW639 : ESGG-GCLA

Ian

[Runway 31]

Thanks  for the information Ingo, I believe that LZ-CGP was to and from Vilnius.  411E28 is an unallocated UK hex code and given that is was using a CGF ID I would suggest that it was LZ-CGP miscoding as  it is one figure different from its correct code.  Looking at  the updater software the hex was picked up for the first time on 9/3 at 0408 UTC by a receiver in Berlin.  I will leave it at this time to see if it was a one off or if the hex is picked up again.

Alan

[Runway 31]

Afternoon Terry, thanks again

Alan

[Runway 31]

Hi Ian,

I thought that EXS75L would have populated for you as I added it in when it took of from Edinburgh
Have you got Auto-populate route data ticked in Preferences/Radarbox?

Many thanks

Alan

[EK01]

Alan,

Yes I do have auto-populate ticked. However, not sure if it is the 'stubby fingers' syndrome or not but you mention you updated EXS75L as it left Edinburgh however it was EXS75T when it arrived at Alicante !

Ian

[Runway 31]

Aye OK EXS75T, my mistake above.  I never have any of the RYR, EZY etc flight showing with no route info when they are in the d/b and was wondering why you get them and I don't

Alan