Database Update Requests

[Runway 31]

Thanks Michel

Alan

[CYYZGUY]

Hi Alan, I have a plane coming up with no information being filled in.  No Aircraft type, silouette, route, company etc etc..

The mode-S is ABA51D and a Flight ID of N85BE

Any ideas?

regards,

Jason

[Runway 31]

Hi Jason,

ABA51D N85BE Bombardier BD-100-1A10 Challenger 300 20423 BEF Management was N415BE and has a pending number change authorised 18/11 from N415BE on the FAA eist.  So looks like they have completEd the change and have yet to advise the FAA.

Thanks again

Alan

[EK01]

Morning Alan,

RLX3349 : LEZL-LDRI

Ian

[EK01]

Alan,

Just come on :

33FE75     No further information
3F83E7     Flight ID : GAF051

Ian

[Runway 31]

Hi Ian,

I have nothing on your 2 military flights other than the German is a tactical code.

Thanks again

Alan

[Runway 31]

Could whoever used the Report Aircraft Error to Database Update Team feature of Database Explorer to advise me of an error, please note that A3EC41 has been in the database as a GL5T since February 2011.  If you still had it as an F900 this may suggest that you may need to update your database.

Many thanks

Alan

[Northern Watch]

Hi Alan

Another trip to Aberdeen today and picked up the following but the picture was incorrect.  I see in the past that there is a way of blocking this anomalies.  I have deleted the details after the c/n in the d/b and deleted the picture in the "photo" file, is there anything else I should do?

3B77F2  / 33 / Socato TBM700A / French Airforce.  Picture is of a military jet.

In addition, the owner of 3CD437 / D-CHRB / Citation is Hahn Air.

The Altitude problem was more than evident again as well as a number of c/s being duplicated on aircraft and the problem with aircraft appearing and disappearing that have similar mode S codes to those on the screen matching height and c/s.  What a nightmare if you are monitoring aircraft at an airport. Are Airnav aware of the other problems as well as the altitude glitch?

Regards

Keith

[Runway 31]

Hi Keith,

What version of the software are you using on your laptop as there should be no problems with V5 and duplicates and similar hex codes etc.  Also the ones you are having problems with are they mode-s equipped or not or both.  Also do you have call sign and squawk validation ticked in preferences as this error checks non mode-s aircraft.

Regarding the photo problem, that is still being worked on.

Alan

[Northern Watch]

Hello Alan

I am using Windows XP on a netbook. Problem seems to be with those not fully mode S equipped. I did not have the call sign and squawk validation ticked until about half way through my short stay there but I am sure this did not make any difference.  I did a screenshot at one point and will try and recover it and post it to you shortly.

Regards

Keith

[Runway 31]

Hi Keith,

Thanks for the answer, I was wanting to make sure you were using version 5.

Unfortunately you can only do full error checking with mode-s equipped aircraft.  The call sign and squawk validation is a compromise for non-mode-s as we look for 2 same call sign and squawks from the aircraft providing the hex code before displaying the call sign and route.  We had initially set this to 5 same and this was OK in the central belt where there was plenty of interogation activity between ground based radars and aircraft transponders.  Away from the central belt 5 same validations kept to many call signs and routes etc from being displayed due to limited interogatations from the ground based radar.  Two same squawk/ call sign validation was therefore taken as a compromise to ensure maximum display with an element of error checking but this then leaves room for errors creeping in.

Please also acknowledge my limited technical knowledge in providing this answer.

Alan

[Northern Watch]

Hi Alan

Sorry I only managed to capture the map view rather than mylog but I have checked and it looks as if it only occurred to limited mode S aircraft for example Helicopter G-TIGV shows c/s VADER2 which was the same as Falcon G-FRAS. Also, Helicopter G-CHYI also had VADER2 as a c/s at one point.  Jetstream's 40098C / G-MAJJ and 400984 / G-MAJB both had the same c/s EZE85F both timed out within 11 seconds of one another although I cannot confirm that one or the other were in range. Falcon G-FRAH had c/s EZE41LK, the same as Jetstream G-MAJD.  I am sure there were a few more but surely there are others out there that are using XP?

Confused

Keith

[Runway 31]

Its not the Windows version that is the problem Keith, it is the fact that you cannot error check non mode-s equipped aircraft in the same manner as mode-s equipped as per my previous reply.  The ones you mention are not mode-s equipped aircraft.  Mode-s equipped aircraft have error checking as part of their signal whereas non mode-s dont have.  Again excuse my limited knowledge.

Alan

[Michel]

Alan,

TRA863C EHAM-LEBL

Michel.

[Runway 31]

Thanks again Michel

Alan