Database Update Requests

[Runway 31]

Hi Keith,  I didn't put it in the d/b as it is a civil hex for a mil tactical code which is used then discarded.  If it is received again I will add it in.

Alan

[Runway 31]

Thanks Ingo,

Added it in this morning

Alan

[Northern Watch]

Hi Alan

Thanks, that makes sense to me. I will keep an eye out just in case.

Regards

Keith

[X]

Alan

* A4AD15                                                                 2014/12/05 15:33:21 
* A4AD15                                                                 2014/12/05 17:28:18 

Decodes to N400ER which is/was Piper PA-42-1000

X

[Runway 31]

Thanks X,

It is N400ER ex LN-ACV

Alan

[X]

Alan

Royal Jordanian according to c/s but not by its Spanish hex!

* 340734  RJA612   OJAI-OMDB                                             2014/12/07 01:21:00 

X

[Runway 31]

X

Post from Volker on mode_s shows that this is JY-AYT departing AUH.  It arrived using the correct 740347 so one box miscode>

Alan

[M]

FCM5PG   LOWW   EFHK
XMS001   EGKK   EFRO
XMS002   EFRO   EGKK
NWS3319   ULLI   MDPC
NWS3515   UUEE   MMUN
NWS3516   MMUN   UUEE
NWS3517   UUEE   MDPC
NWS3518   MDPC   UUEE
TSO553   UUWW   MDPC
TSO554   MDPC   UUWW
ABW501   UUEE   KDFW   via KORD

[neroon79]

Morning, the only unknown from Saturday:

3C646F nothing more

Have a nice Sunday!

Ingo

[Runway 31]

Many thanks M

Alan

[Runway 31]

Morning Ingo,

3C646F decodes to D-AICO unknown to me

Alan

[neroon79]

Hi Alan,

interesting, I got this hex on two different Radarboxes with about 100 messages on each device. Maybe a miscoded airframe or something else.

Ingo

[Runway 31]

Could be Ingo, maybe its new and just unknown to me.  I would normally expect a flight ID to show.

Alan

[neroon79]

The REG indicating that it should be some kind  of commercial aircraft. And in that case I would expect a flight id too. But if it's a miscoded small airframe a flight isn't necessarily received, especially if the airframe is at the edge of my reception range.

With low message count and airframe received on only one box decoding error or a scrambled packet would be my first guess. But in this case I got it at the same time on two boxes with quite high message count. Therefore I thought that it might be something else.

As usual in that kind of cases: time will tell...

Ingo

[Runway 31]

Yes indeed Ingo

Alan