Aris

FSX/Accleration ATC Altitude Problem

Recommended Posts

Hello everyone,

Lately I've been having problems with the default ATC on my FSX-Acceleration installation.

I usually use PLAN-G to make some medium distance IFR plans and fly them using freeware and payware aircraft and FSX's built in ATC.   A couple of months ago on some of the flights, I would set up a flightplan for FL310-320 etc and whenever I passed 10,000 the ATC would clear me for a FL roughly 10,000 above what I had in the plan.   If I asked for a lower FL the ATC would either subtract the altitude from the original filed flightplan -or- just say "FL denied".

An example would be as such:   A flight plan from Athens to Rome with a B732 and a requested altitude of  32,000, in which passing FL100-120 the ATC would clear me to FL420.  If I asked for 10,000ft decrease it would either clear me to FL220 -or- sprew out "FL denied".  Sometimes if I cancelled and reload the IFR flightplan, everthing would work fine.

This is a reacurring problem which seems to be getting worse as time goes by.  

 

Any help would be greatly appreciated since I really don't want to have to reinstall FSX since I've got tons of modified aircraft!

 

Thanks!

Aris

Share this post


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

If you used the FSX flight planner would ATC give you the correct altitudes?  Has something accidentally modified Plan-G causing this to happen?

 

Share this post


Link to post
Share on other sites
53 minutes ago, charliearon said:

If you used the FSX flight planner would ATC give you the correct altitudes?  Has something accidentally modified Plan-G causing this to happen?

 

To be honest I haven't used the FSX flight planner since I sometimes fly with waypoints which I add manually in Plan-G.

Also, this doesn't always happen;  sometimes the same flightplan will work perfectly, other times the ATC will give a peculiar altitude.

 

Share this post


Link to post
Share on other sites

I have had it happen only a couple of times.  Never really an exact 10,000 feet difference, but way

higher than planned.  It also will happen 100 or less miles from destination so I will acknowledge

ATC and begin a very slow climb until ATC realizes their foolishness and has me descend back

down to the proper altitude.  ATC can be quirky!

Share this post


Link to post
Share on other sites
2 minutes ago, charliearon said:

I have had it happen only a couple of times.  Never really an exact 10,000 feet difference, but way

higher than planned.  It also will happen 100 or less miles from destination so I will acknowledge

ATC and begin a very slow climb until ATC realizes their foolishness and has me descend back

down to the proper altitude.  ATC can be quirky!

Thanks Charlie!
Hopefully I *will* find the time to do a full re-install with FSX-SE which I've purchases a year ago and haven't even downloaded yet! :)

 

Share this post


Link to post
Share on other sites

ATC will clear you for whatever cruise altitude is specified in the flight plan's .pln file, so it's more a matter of "garbage in, garbage out" than a serious error in FSX.

PLN files may be edited with Notepad or similar, so check (and edit) the cruise altitude in that file before loading the flight plan in FSX.

Share this post


Link to post
Share on other sites
42 minutes ago, Bjoern said:

ATC will clear you for whatever cruise altitude is specified in the flight plan's .pln file, so it's more a matter of "garbage in, garbage out" than a serious error in FSX.

PLN files may be edited with Notepad or similar, so check (and edit) the cruise altitude in that file before loading the flight plan in FSX.

Actually I did have a look at the .pln file and didn't *find* any errors concerning altitude.   I've attached a rather pesky flightplan which seems to not want to work correctly if anyone wants to take a look at it.

Spoiler

<?xml version="1.0" encoding="UTF-8"?>

<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>LFLL to LGAT</Title>
        <FPType>IFR</FPType>
        <CruisingAlt>33000</CruisingAlt>
        <DepartureID>LFLL</DepartureID>
        <DepartureLLA>N45° 43' 32.00",E5° 4' 51.00",+000820.00</DepartureLLA>
        <DestinationID>LGAT</DestinationID>
        <DestinationLLA>N37° 53' 19.55",E23° 43' 37.83",+000065.00</DestinationLLA>
        <Descr>LFLL, LGAT</Descr>
        <DeparturePosition>18L</DeparturePosition>
        <DepartureName>Saint Exupery</DepartureName>
        <DestinationName>Hellinikon</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>61637</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="LFLL">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N45° 43' 32.00",E5° 4' 51.00",+000820.00</WorldPosition>
            <ICAO>
                <ICAOIdent>LFLL</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="GEMLA">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N45° 34' 20.00",E6° 20' 23.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>GEMLA</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="VANAS">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N45° 27' 26.00",E6° 44' 49.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>VANAS</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MEDAM">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N45° 15' 52.00",E6° 56' 24.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>MEDAM</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ATMAD">
            <ATCWaypointType>User</ATCWaypointType>
            <WorldPosition>N45° 13' 9.00",E7° 0' 9.00",+000000.00</WorldPosition>
        </ATCWaypoint>
        <ATCWaypoint id="NITAM">
            <ATCWaypointType>User</ATCWaypointType>
            <WorldPosition>N45° 6' 21.00",E7° 9' 28.00",+000000.00</WorldPosition>
        </ATCWaypoint>
        <ATCWaypoint id="PES">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N42° 26' 9.70",E14° 11' 3.90",+000029.00</WorldPosition>
            <ICAO>
                <ICAOIdent>PES</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="URIPI">
            <ATCWaypointType>User</ATCWaypointType>
            <WorldPosition>N41° 52' 32.00",E15° 11' 4.00",+000000.00</WorldPosition>
        </ATCWaypoint>
        <ATCWaypoint id="DIVKU">
            <ATCWaypointType>User</ATCWaypointType>
            <WorldPosition>N41° 30' 0.00",E15° 50' 16.00",+000000.00</WorldPosition>
        </ATCWaypoint>
        <ATCWaypoint id="BAR">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N41° 8' 39.30",E16° 46' 35.20",+000104.00</WorldPosition>
            <ICAO>
                <ICAOIdent>BAR</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="FASAN">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N40° 51' 40.00",E17° 26' 0.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>FASAN</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="BRD">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N40° 36' 39.10",E18° 0' 10.30",+000082.00</WorldPosition>
            <ICAO>
                <ICAOIdent>BRD</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ORSOM">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N40° 21' 54.00",E18° 26' 48.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>ORSOM</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="KRK">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N39° 26' 37.89",E20° 4' 21.99",+000065.00</WorldPosition>
            <ICAO>
                <ICAOIdent>KRK</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="PARNA">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N39° 15' 44.00",E20° 25' 49.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>PARNA</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="GARTA">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N38° 59' 6.00",E20° 58' 6.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>GARTA</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ELVAS">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N38° 31' 29.00",E21° 50' 31.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>ELVAS</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="IXONI">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N38° 18' 54.00",E22° 13' 56.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>IXONI</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="PIKAD">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N38° 3' 41.00",E22° 41' 52.00",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>PIKAD</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="LGAT">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N37° 53' 19.55",E23° 43' 37.83",+000065.00</WorldPosition>
            <ICAO>
                <ICAOIdent>LGAT</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>
 

 

Share this post


Link to post
Share on other sites

I see 2 differences with mine and that is

first line; "encoding="windows-1252"?

and then just under IFR I have an extra line;

<RouteType>HighAlt</RouteType>

maybe that has something to do with it?

Herman

Share this post


Link to post
Share on other sites

I don't think so.

Here's a flight plan that was generated with LittleNavMap for comparison:

 

Spoiler

<?xml version="1.0"?>
<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <!-- Created by Little Navmap Version 1.2.4 (revision c9478a9) on Saturday, March 11, 2017 16:32:11 -->
    <FlightPlan.FlightPlan>
        <Title>MKJP to KMIA</Title>
        <FPType>IFR</FPType>
        <RouteType>HighAlt</RouteType>
        <CruisingAlt>30000</CruisingAlt>
        <DepartureID>MKJP</DepartureID>
        <DepartureLLA>N17° 56' 24.43",W76° 47' 56.50",+000010.00</DepartureLLA>
        <DestinationID>KMIA</DestinationID>
        <DestinationLLA>N25° 47' 33.87",W80° 17' 26.26",+000008.00</DestinationLLA>
        <Descr>MKJP, KMIA</Descr>
        <DeparturePosition>12</DeparturePosition>
        <DepartureName>Norman Manley Intl</DepartureName>
        <DestinationName>Miami Intl</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>61472</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="MKJP">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N17° 56' 8.00",W76° 47' 14.99",+000010.00</WorldPosition>
            <ICAO>
                <ICAOIdent>MKJP</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MLY">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N17° 55' 48.89",W76° 46' 39.45",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>MK</ICAORegion>
                <ICAOIdent>MLY</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="SAVEM">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N18° 26' 48.00",W77° 1' 48.00",+000000.00</WorldPosition>
            <ATCAirway>UA301</ATCAirway>
            <ICAO>
                <ICAORegion>MK</ICAORegion>
                <ICAOIdent>SAVEM</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="TOTON">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N19° 32' 30.00",W77° 34' 6.01",+000000.00</WorldPosition>
            <ATCAirway>UA301</ATCAirway>
            <ICAO>
                <ICAORegion>MK</ICAORegion>
                <ICAOIdent>TOTON</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="UCA">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N22° 0' 54.23",W78° 48' 56.95",+000000.00</WorldPosition>
            <ATCAirway>UA301</ATCAirway>
            <ICAO>
                <ICAORegion>MU</ICAORegion>
                <ICAOIdent>UCA</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="URSUS">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N24° 0' 0.19",W79° 4' 11.28",+000000.00</WorldPosition>
            <ATCAirway>UA301</ATCAirway>
            <ICAO>
                <ICAORegion>K7</ICAORegion>
                <ICAOIdent>URSUS</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ELLEE">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N24° 52' 50.21",W79° 41' 24.06",+000000.00</WorldPosition>
            <ATCAirway>A509</ATCAirway>
            <ICAO>
                <ICAORegion>MY</ICAORegion>
                <ICAOIdent>ELLEE</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="EONNS">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N25° 17' 48.19",W79° 59' 12.62",+000000.00</WorldPosition>
            <ATCAirway>A509</ATCAirway>
            <ICAO>
                <ICAORegion>K7</ICAORegion>
                <ICAOIdent>EONNS</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="DHP">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N25° 47' 59.87",W80° 20' 56.53",+000000.00</WorldPosition>
            <ATCAirway>A509</ATCAirway>
            <ICAO>
                <ICAORegion>K7</ICAORegion>
                <ICAOIdent>DHP</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="KMIA">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N25° 47' 33.87",W80° 17' 26.26",+000008.00</WorldPosition>
            <ICAO>
                <ICAOIdent>KMIA</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>

 

Share this post


Link to post
Share on other sites
On 3/31/2017 at 0:00 PM, Bjoern said:

And ATC doesn't clear you for FL330 with that one?

It cleared me up to FL240 then passing 240 it cleared me for FL430.   When I asked 4,000 decrease, it cleared me for FL290 which means that it does consider FL330 the cruising level but wants me to go up to FL430 anyway (oh, and if I level off at FL330, it keeps telling me to expedite my climb to FL430)

 

Share this post


Link to post
Share on other sites
On 3/31/2017 at 0:49 PM, electricman said:

I see 2 differences with mine and that is

first line; "encoding="windows-1252"?

and then just under IFR I have an extra line;

<RouteType>HighAlt</RouteType>

maybe that has something to do with it?

Herman

I'll try and copy/paste the route type and see how things go!

 

Share this post


Link to post
Share on other sites
On 4.4.2017 at 9:22 PM, Aris said:

It cleared me up to FL240 then passing 240 it cleared me for FL430.   When I asked 4,000 decrease, it cleared me for FL290 which means that it does consider FL330 the cruising level but wants me to go up to FL430 anyway (oh, and if I level off at FL330, it keeps telling me to expedite my climb to FL430)

That really shouldn't happen. Maybe a reinstall isn't such a bad idea...

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