Recommended Posts

When generating an autoplan the programme shoes the desired level on the right hand side but assigns the max level chosen at the departure airport, i.e FL90. However when I take off from a London airport and go to the FL shown the ATC kicks in and tells me to decend to FL40, I am sure this is correct but not sure why the programme is showing FL90 throughout the plan apart from the descent levels which are correct. Have I got a setting wrong for SID's?

Share this post


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

Let me know what your Flt Plan route and procedures are and I'll look into it.

Thanks,

Dave

Share this post


Link to post
Share on other sites

Never mind the Flight Plan.  I found the bug and will have it fixed for release 2505R3.

Thanks for the report.

Dave

Share this post


Link to post
Share on other sites

Still getting this issue where the generated flight plan shows my altitude at flight level 120 or whatever at the starting airport before I have even taken off. Anyone else with this

Share this post


Link to post
Share on other sites

Floyd, could you share the flight plan you are having this issue with.  

Thanks,

Dave

Share this post


Link to post
Share on other sites

I
3 version
0
6
1 KBUF 12000 42.94042 -78.73058
11 WOZEE 12000 42.93379 -78.73879
11 ISTON 12000 43.12972 -79.06445
11 LINNG 12000 43.30275 -79.3548
11 SEDAB 11000 43.36613 -79.38184
11 DEGRO 8500 43.52449 -79.44966
11 VERKO 7000 43.59701 -79.54427
11 DARPU 4000 43.47417 -79.72166
11 DANIP 3000 43.425 -79.7925
11 MASAR 6000 43.38467 -79.8505
11 DULPA 3000 43.56403 -79.82344
11 KERPU 2030 43.62459 -79.73591
1 CYYZ 618 43.67439 -79.66371
0

This one had me at 12000 ft at Buffalo.

Share this post


Link to post
Share on other sites

Thanks Floyd.

Looks like you might be on a back level of P2A.  There was an issue like this in a previous version, but the latest version fixes it and provides planned altitudes for the climb, so exporting to XP-11 format, with a climb rate of 2000 FPM, you get:

I
1100 version
CYCLE 1810
ADEP KBUF
ADES CYYZ
NUMENR 12
1 KBUF ADEP 727 42.94042 -78.73058
11 WOZEE DIRECT 1000 42.93379 -78.73879
11 ISTON DIRECT 6000 43.12972 -79.06445
11 LINNG DIRECT 10000 43.30275 -79.3548
11 SEDAB DIRECT 11000 43.36613 -79.38184
11 DEGRO DIRECT 12000 43.52449 -79.44966
11 VERKO DIRECT 12000 43.59701 -79.54427
11 DARPU DIRECT 10000 43.47417 -79.72166
11 DANIP DIRECT 9000 43.425 -79.7925
11 MASAR DIRECT 8000 43.38467 -79.8505
11 DULPA DIRECT 4500 43.56403 -79.82344
11 KERPU DIRECT 2500 43.62459 -79.73591
1 CYYZ ADES 569 43.67672 -79.63066
 

Dave

Share this post


Link to post
Share on other sites

X Plane 11 format

I
1100 version
CYCLE 1811
ADEP KBUF
ADES CYYZ
DESRWY RW05
STAR NAKBO2
STARTRANS APDAX
APP I05
NUMENR 0
1 KBUF ADEP 727 42.94042 -78.73058
1 CYYZ ADES 569 43.67672 -79.63066

 X Plane 10 format

I
3 version
0
6
1 KBUF 16000 42.94042 -78.73058
11 APDAX 16000 43.28695 -81.25056
11 NUBER 9500 43.45778 -80.3775
11 IKBAT 7000 43.49417 -80.1725
11 ILANI 5000 43.48988 -79.93117
11 DULPA 3000 43.56403 -79.82344
11 KERPU 2030 43.62459 -79.73591
1 CYYZ 618 43.67439 -79.66371
0

This is using the latest version of Pilot2ATC from the website 2.5.0.6 X64.

Share this post


Link to post
Share on other sites

I just uploaded 2506R2.  It should do it correctly.

Let me know.

Thanks,

Dave

Share this post


Link to post
Share on other sites

Actually, I rechecked and there are conditions whereby you get the wrong altitudes. 

Turns out there was another little bug in the altitude calculations.  Will get out a 2506R3 with the fix.

Thanks,
Dave

Edited by Dave-Pilot2ATC

Share this post


Link to post
Share on other sites

Tried a couple of flights, one worked ok but the last one wanted me to get to 29000 in 6.4nm from airport. 

I
3 version
0
6
1 KDFW 607 32.91571 -97.02597
11 MECHL 29000 33.02028 -96.9975
11 BORDD 29000 33.01378 -96.92275
11 JYMME 29000 33.00917 -96.86197
11 OWLLS 29000 32.95922 -96.78883
11 SKTRR 29000 32.75605 -96.79247
11 DARTZ 29000 32.28576 -96.81105
11 BRDEN 29000 31.88652 -96.65582
11 TORNN 29000 31.52039 -96.51471
11 BILEE 28000 31.16451 -96.38156
3 TNV 17000 30.28853 -96.05824
11 OHIIO 6000 30.13823 -95.08405
11 PNUUT 5500 30.10267 -95.13549
11 KAFDO 2000 29.80028 -95.10703
11 AVVOS 1600 29.71035 -95.20662
1 KHOU 91 29.65416 -95.26871
0

Anything I can do?

Share this post


Link to post
Share on other sites

Thanks for the example issue.  I did find another bug in the climb calculation and it will be fixed in the next update.

Thanks,

Dave

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