ID REACH355

[EK01]

Hi Guys,

Above aircraft came on the interface today showing as a Learjet C-21A, registration 84-0094 and in the details at the bottom is showing as belonging to the USAF. However in the grid, itself it is showing as belonging to Aer Arann which is clearly incorrect. How do I delete the Aer Arann information from database explorer. I have tried a few permutations but, so far, without success.

Cheers.

[tarbat]

The logo is derived from the Flight ID, in this case REACH355.

So, you would need to change the REA.BMP logo in the logos folder to something more appropriate, say like the RCH.BMP one.  However, that would also change the logo for genuine Aer Arann flights as well.

Only you can decide whether having the correct logo for USAF Reach flights is more important than having the correct logo for Aer Arann flights.  Normally the USAF Reach flights have a Flight ID of RCHxxx

[DaveReid]

The logo is derived from the Flight ID, in this case REACH355.

So, you would need to change the REA.BMP logo in the logos folder to something more appropriate, say like the RCH.BMP one.  However, that would also change the logo for genuine Aer Arann flights as well.

Only you can decide whether having the correct logo for USAF Reach flights is more important than having the correct logo for Aer Arann flights.  Normally the USAF Reach flights have a Flight ID of RCHxxx

A better solution would be some more robust logic in the RadarBox code that resolves logos.

AFAIK, the ICAO rules state that a genuine three-letter ICAO prefix should be followed by either a number (with or without a suffix), e.g. BMA8HY, or an alphanumeric combination where letters and numbers can be mixed provided that the combination starts with a number, e.g. RYR8KG3.

From the above it follows that, if the 4th character of the Flight ID is a letter, as in the REACH355 example, then the preceding letters aren't going to be a valid ICAO code, or if they are it's just a coincidence - either way they shouldn't be used as the basis for displaying a logo.

Something for a future RB release, perhaps ?

[RodBearden]

As an extension of Dave's suggestion, how about logic that if the third character is a number, use just the first two letters - many airlines use their IATA code.

Rod

[viking9]

Don't Reach aircraft transmit RCH followed by numeric characters and not REACH?

Tom

[Fenris]

Not all of them it seems, there is probably no standard way of programming the transponder specified.

Some sort of "If this is received, link it to that logo" approach would be useful because everyone's situation is just a little different and some local munging would go a long way to fixing it.

[viking9]

Not all of them it seems, there is probably no standard way of programming the transponder specified.

Some sort of "If this is received, link it to that logo" approach would be useful because everyone's situation is just a little different and some local munging would go a long way to fixing it.

Brian,

I've checked back on all C-17 Reach flights in my logs and they all send RCH followed by three or four digits. I have never seen one listed as transmitting 'Reach' from the transponder. If they did then SBS-1 and RadarBox woud have to convert it, something I very much doubt happens.

Tom

[abrad41]

Tom

Hi Tom, I think I have seen some of the tankers on the base useing the Reach call sign instead of the QID callsign.

Andy

[Keith L]

I have (rarely) seen REACH*** as a reported callsign, oddly, there was one today:

AE0188   REACH355 84-0094   LJ35   USA - Air Force   24/02/2009 14:05

I've also noticed aircraft which usually wear a RCH callsign sometimes showing E1234 as a callsign where 1234 are the last digits of the tail number.

Keith

[viking9]

Hi Andy and Keith,

Well yes , REACH355 is the aircraft under discussion. I've just read an email from a guy in the States and he says that there are a number of C-21As over there transmitting RCH but not REACH.  84-0094 is from the 375th AW.

As to KC135s of the 100th ARW using 'Reach' in their callsigns, I understood that is sometimes used when tanking Reach aircraft. Even then the transponder sends RCH. Of course the flight crew on 100th ARW often miss-key their c/s either intentionally or otherwise and I get a totally different c/s on RB from that heard on VHF/UHF.

BTW Andy, have you any word on RAMMAs coming our way? I see some exclusion zones set up in the oggin for tomorrow night. Assume it's for AAR. Would be great for our RHWW meet at the Hall on Thurs if we had a couple in.

Tom

[Keith L]

Doh, sorry Tom that was dumb of me.  Here are a couple:

ADFE6D  REACH544  91-1653  C130  US Mil 2 19/02/2009 10:02
ADFDBE  REACH378  93-7311  C130  US Mil 2 13/02/2009 13:22
ADFE83   REACH145  92-0548  C130 US Mil 2  12/02/2009 20:54

Cheers  Keith

[abrad41]

Hi Tom

We don't hear to much in our department until they hit the ground.

Andy

[EK01]

Thanks, guys.

As Aer Arann are unlikely to transmit ADSB, I think as suggested by Tarbat, I will change there bitmap of REA to show the same logo as that of RCH.

Cheers.

[viking9]

Doh, sorry Tom that was dumb of me.  Here are a couple:

ADFE6D  REACH544  91-1653  C130  US Mil 2 19/02/2009 10:02
ADFDBE  REACH378  93-7311  C130  US Mil 2 13/02/2009 13:22
ADFE83   REACH145  92-0548  C130 US Mil 2  12/02/2009 20:54

Cheers 

Keith

Hi Keith,

Thanks for listing those for me. They are in my MyLog too but until you listed the mode S I wasn't able to search for them as MyLog has no facility for searching on Flight ID (Hopefully in the next version).

I think it is still extremely rare for a Reach aircraft to transmit 'REACH' so I would not make any changes to the logos.

Tom

[viking9]

Hi Tom

We don't hear to much in our department until they hit the ground.

Andy

Hit the ground! Ouch! :-)

Tom