MichiP

2.3.1.0 Airway not Load

Recommended Posts

Hi,

when I try to Load an Airway the waypoints are not filled in the flight plan. 

I use the airac cycle 1711.

I tried the following steps.
- New Flightplan, new waypoint EDDM, new waypoint INPUD, new waypoint UPALA
- open Wapoint option for UPALA and select "load airway",
- then i choose  airway "UL610" and to wpt "BATTY" and press "Load", neither the legs nor the waypoint "BATTY" have been inserted in the plan

Then I tried another way I add the BATTY wpt by hand and choose the ariway on the UPALA wpt once more. But the legs also did not fit in the plan.

Greeting

Mike

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Mike,

I just tried it and it worked fine for me with both AIRAC 1711 and 1710. 

First thing I would try is rebooting the PC to clear out all the cache, etc. that might be interfering.

It seems you have access to the data because you are able to enter the waypoints without errors.

You might also try entering the destination airport before you start entering waypoints, although I did not have to do that.  It worked fine just following your steps.

Dave

Share this post


Link to post
Share on other sites

Hi Dave,

thx for the fast reply. I think I can narrow the problem.. 

I installed a new version of Pilot2Atc on another PC and it worked as expected.
Then I copied all files from the Data-Directory of the new Pc to the old Pc and vola it functioned as expected.
Then I started the update via NacDataPro to the newest airac and got the same problem as described above.

Please let me know If i should try another test.

Gretting

Mike

Share this post


Link to post
Share on other sites

Sounds like your NavDataPro update may be damaged.

My previous test was using Navigraph.  I just updated my NavDataPro installation using the NDP desktop installer and got the proper results using NavDataPro 1711.

Are you running the NDP installer as Admin?  Can you re-download the data update and run the installer again?  Can you update the data on the other computer and copy the files like with the earlier version that worked?

If that doesn't work, you may need to open a ticket with Aerosoft.

Dave

Share this post


Link to post
Share on other sites

Hi Dave,

you were right, i figured out the problem. The Database which comes with the new airac is wrong. I will step back to the original airac 1705 and live with the errors.

Thx for your help

Greeting Mike

PS:

For your information the results what i figured out

Original airac from Pilot2Atc (1705)

select Id from Airways where Identifier = 'UL610';
Result: 
5283

select Airways.Id, Fix1Identifier, Fix2Identifier 
from AirwaySegments, Airways 
where AirwaySegments.Airway_Id = Airways.Id
and Airways.Identifier = 'UL610';
Result:
5283    KFK    KARGI
5283    KARGI    SOMGU
5283    SOMGU    ELVON
5283    ELVON    DEKEK
5283    DEKEK    YAA
5283    YAA    IST
5283    IST    FENER
5283    FENER    VADEN
5283    UTEKA    DONIV
5283    DONIV    PELOV
5283    PELOV    TISAK
5283    TISAK    TONDO
5283    RENKA    GONBA
5283    GONBA    STAUB
5283    STAUB    MAMOR
5283    MAMOR    UNKUL
5283    UNKUL    UPALA
5283    UPALA    INBED
5283    INBED    LOHRE
5283    LOHRE    ADKUV
5283    ADKUV    LAMLA
5283    LAMLA    BATTY
5283    NIK    DENUT
5283    DENUT    LUMEN
5283    LUMEN    BULAM
5283    BULAM    DIBLI
5283    DIBLI    RAPIX
5283    RAPIX    SUNUP
5283    SUNUP    TEBRA
5283    TEBRA    KOPUL
5283    KOPUL    UNSAD
5283    UNSAD    NILON
5283    NILON    GILDA
5283    GILDA    LAM
5283    LAM    HEMEL

After Update:
select Id from Airways where Identifier = 'UL610';
Result:
6980
6981
6982
6983

thats the first error because i assume that should be a unique id.

select Airways.Id, Fix1Identifier, Fix2Identifier 
from AirwaySegments, Airways 
where AirwaySegments.Airway_Id = Airways.Id
and Airways.Identifier = 'UL610';
6980    UL610    UL610
6980    UL610    UL610
6980    UL610    UL610
6980    UL610    UL610
6981    UL610    UL610
6981    UL610    UL610
6981    UL610    UL610
6981    UL610    UL610
6981    UL610    UL610
6981    UL610    UL610
6981    UL610    UL610
6981    UL610    UL610
6981    UL610    UL610
6981    UL610    UL610
6982    UL610    UL610
6982    UL610    UL610
6982    UL610    UL610
6982    UL610    UL610
6982    UL610    UL610
6982    UL610    UL610
6982    UL610    UL610
6982    UL610    UL610
6983    UL610    UL610
6983    UL610    UL610
6983    UL610    UL610
6983    UL610    UL610
6983    UL610    UL610
6983    UL610    UL610
6983    UL610    UL610
6983    UL610    UL610
6983    UL610    UL610
6983    UL610    UL610
6983    UL610    UL610
6983    UL610    UL610
6983    UL610    UL610

thats the second error.

Share this post


Link to post
Share on other sites

Since my NavDataPro update was not corrupt, it seems you could run the NavDataPro update again and get a good database that's up to date.

Share this post


Link to post
Share on other sites

Hi Dave,

that's weird. Clearly I tried the update several times but always with the same result. I used V 1711 R1 from Aerosoft-Server. I dont understand why i receive another result.

So I will wait for the next cycle and hope it will be correct.

Thx and Greeting

Mike

Share this post


Link to post
Share on other sites

Hi Dave,

 

I have the same problem but I suspect there is more to it. I first noticed that while importing a .pln file I only got the departure and destination airport loaded. Trying to add the airways manual they wouldn't load. I restored AIRAC-cycle 1710 and got an database error while starting P2A. Next step I removed all files from the data-folder and did a full install 2.3.1.0 which contains the AIRAC-cycle 1701. Database error is gone but still the .pln-file will only load departure airport and arrival airport. I can't load airways (adding waypoints is no problem).

 

I don't think the issue is related to the upgrade of the AIRAC-cycle to 1711 as it also happens with 1701.

I use the folowing versions: P3D 4.1, NavDataPro, Windows 10. Flightplan used ELLX MMD8X MMD UM163 CTL UT10 ALESO UT420 BUZAD OLIV3A EGBB.

Regards,

Rob

 

Share this post


Link to post
Share on other sites

I have just conversed with the NavDataPro team and there is an issue with the data content related to Airways.  Very strange that it's gone undetected for so long, but they will be fixing it in a coming update.

Thanks for the reports.

Dave

Share this post


Link to post
Share on other sites

Thanks Dave,

 

Did some additional testing. I have around 55 pln.files in my flightplan folder. It seems that it only happens with flightplans in Western Europe. Anyway good to hear that it will be resolved by the NavDataPro team.

 

Again thanks for your support.

Rob

Share this post


Link to post
Share on other sites

Hi,

i downloaded the new version with NavDataPro. It seemed that the problem is solved.

Thank you.

Greeting

Mike

Share this post


Link to post
Share on other sites

Mike,

The problem is not fixed yet.  Good news is, it is not evident with all airways.

Should be fixed with the 1712 AIRAC release and once it is, the NavDataPro 1701 will also get fixed.

Thanks,

Dave

Share this post


Link to post
Share on other sites

Hi Dave,

there is a new Dataset for download. With this set (1711 R2) my described problem is solved.

Greeting

Mike

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now