Page 1 of 1

ICAO not matching tail number (registration)

Posted: Wed Sep 12, 2018 3:32 am
by TanerH

I'm feeding a VRS instance I set up, from a few different rpi's running dump1090, and I noticed something weird this evening.

VRS is attributing a different (incorrect?) tail number to an aircraft w/ ICAO "AAEC4B". The tail should be "N80243", and that's what my piaware host says.... but VRS is claiming it's "N917A".

Looking up said tail numbers, these both appear to be the same type of aircraft -- but why the discrepancy?

VRS in fact puts an asterisk (*) after the callsign, claiming "Route not known, callsign may not be correct".

I'm attaching 2 screenshots -- one from VRS and one from PiAware.
EDIT - image upload doesn't seem to work... here is an imgur link:

Thoughts? Again, these are both being generated from the same data (same dump1090 instance feeding both).


Re: ICAO not matching tail number (registration)

Posted: Thu Sep 13, 2018 9:50 pm
by kiwikieran
Flight aware has there database to search and Virtual Radar has there own one.
Flight Aware would most likely be the correct one so you can update Virtual Radar at if you wish to.

Re: ICAO not matching tail number (registration)

Posted: Thu Sep 13, 2018 10:59 pm
by kiwikieran
EX N80243
Beech 300 Super King Air 350C
Department of Homeland Security

Re: ICAO not matching tail number (registration)

Posted: Sat Sep 15, 2018 5:51 am
by TanerH
I was under the impression that at least the US-assigned ICAO addresses (A00001 - ADF669) are uniquely (mathematically) mapped to N1 - N999ZZ.

Is this not correct? shows N80243 for ICAO AAEC4B.

The FAA registry for "N917A" shows ( ... rtxt=N917A):

Mode S Code (base 16 / hex) ACB0AC

So, I'm not really sure what's going on here -- unless there are some possible weird exceptions allowed?