Routes Reversed

[GulfTraveller]

Not sure whether it helps, but a quick check on Libhomeradar suggests the system is showing the previous sector recorded by the aircraft tracked. That would explain both the reversals and the corruptions.

[ACW367]

Definately a bug in reading the navdata.db3

here is a screenshot of the heathrow approach, with ANA201 in myflights.  This route has always been into Heathrow and has not changed with the summer timetable.  You can see the info shown, differs from that contained in the Navdata explorer.

Many of the other aircraft visable in myflights are also corrpted.
BMA948 showing EGLL-UUUD - in DB explorer as OSDI-EGLL datestamp 20100407110623

BAW435 showing EGLL-LIMC - in DB explorer as EHAM-EGLL datestamp 20101205141406

SIA308 showing WSSS-YMML - in DB explorer as WSSS-EGLL datestamp 20101203142044

IBE3176 showing correctly as LEMD-EGLL datestamp 20101203150904

[RNAGG]

I'm also having this problem.
 Uncheck the automatic update route and did the manual updates.

 Still is showing routes to information not listed in my database.

 If you do not have an urgent solution to this problem, it would be better not to have this option appearing on the label of the aircraft.

 What AirNav doing to correct this problem?

 Regards,

[EK01]

I can confirm that I did not have this route reversal problem prior to downloading the latest update.

[Runway 31]

A new navdata.db3 installation is now available:
http://www.airnavsystems.com/download/ANRB/DBUpdater/ANRBDBUpdater20110418.exe

Changes: New/Updated aircraft table;

Airnav, if as stated on the start of the d/b update thread as shown above, the only thing changed in the Navdat is the aircraft table, why are we having trouble with the routes table.  Was it changed as well and you didnt advise us?

Alan

[orkney]

Hello

As yet we have not updated the Navdata on our main computer and we are having this problem too.  No idea where the data is coming from as it is correct on the Navdata and the Central Airnav Database is also correct.

Andrew

[GulfTraveller]

All my observations here in Kuwait suggest that, where there is a corruption, it is showing the previous sector. Currently watching here DLH 618 (EDDF-OMAA-OOMS) as HECA-EDDF which was its previous flight. Would have thought that would lead to a quick solution. Interesting that not all flights are affected.

[Chris11]

Real junk being displayed here - definitely a corruption

[AirNav Support]

Ok, we are trying to gather the reports so far so we can pin point the cause.

Can you please reply stating whether you have used the new database updater and then seen an issue, whether the routes which are wrong have newly updated timestamp. Some of the replies are not helping at all.

[GulfTraveller]

No update here. DLH618 with previous sector showing has datestamp of 20101025.

[bratters]

If it's any help in a negative/positive sense I seem to be having no route problems.

I have NOT updated the navdata; the autopopulate routes is UNTICKED and I am NOT a Network subscriber. Flight display Lite in use, datasharing switched off.

[sted]

That's the same what I can observe on my computer. As long as I don't use the network all route infomation are shown correctly because the route information is taken from my local route data base, which I have created myself using an SQLite Editor and libhomeradar information.
And of course my autopopulate routes is UNTICKED as well.

From the moment I turn on the network all received network received flights suddenly contain wrong route information suggesting that these route information are not taken from my local database but coming in together with the flight data.

That should be avoided by a software change!

Frank

[tarbat]

I suspect these corrupted routes are coming from network aircraft.  These corrupted routes then get passed into the MyFlights list when the aircraft transitions from network to hardware.

I've got network turned off, and I maintain my own routes table, and all routes look okay.

[Runway 31]

BA SHT18V is showing in d/b explorer as Heathrow -Aberdeen which is correct and has a timestamp of 20100817174505

Its is however showing in myflights as Heathrow-Manchester which is wrong

BAW269 is showing in d/b explorer as Heathrow-Los Angeles which is correct and has a timestamp of 2011419210033

Its is however showing in Myflights as routing Heahtrow-Hong Kong

ANZ1 is showing in d/b explorer as Heathrow-Los Angeles which is correct timestamp 20110424215603.

It is however showing on Myflights routing Auckland-Melbourne which is incorrect.

I have updated using all the Navdatas as they become available.  From the 3 here chosen at random 2 new timestamps and 1 old, all showing correctly in d/b explorer but incorrectly on the screen

Alan

[tarbat]

Alan, do you have network turned ON?