Skip to content
View in the app

A better way to browse. Learn more.
The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ATC insist on raising my altitude above flightplan

Phantoms
in Microsoft Flight Simulator (2020/2024)

Featured Replies

I'm not a pilot so I'm sure I'm missing something. Many times during I get in a fight with ATC wanting to increase my flight level well above my flight plan altitude that I made using Low Altitude Airways in the World Map. One I almost always have issue with is flying over the ocean, mostly clear skys and low amounts of traffic between HEYDR and JEKER. My flightplan was made in the World Map using Low Altitude Airways and set for cruise of 10,000 Ft, but I'm constantly bombarded to climb and maintain 19,000 ft.

 

Is this a airspace issue, a airway issue or just a janky MSFS issue?

 

 

Here's my FP as made by the MSFS World Map. 

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

<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>Lynden Pindling Intl to Miami-Opa Locka Executive</Title>
        <FPType>IFR</FPType>
        <RouteType>LowAlt</RouteType>
        <CruisingAlt>10000.000</CruisingAlt>
        <DepartureID>MYNN</DepartureID>
        <DepartureLLA>N25° 2' 20.25",W77° 27' 58.43",+000013.25</DepartureLLA>
        <DestinationID>KOPF</DestinationID>
        <DestinationLLA>N25° 54' 26.70",W80° 16' 41.60",+000000.00</DestinationLLA>
        <Descr>Lynden Pindling Intl to Miami-Opa Locka Executive</Descr>
        <DeparturePosition>PARKING 23 PARKING NONE</DeparturePosition>
        <DepartureName>Lynden Pindling Intl</DepartureName>
        <DestinationName>Miami-Opa Locka Executive</DestinationName>
        <AppVersion>
            <AppVersionMajor>11</AppVersionMajor>
            <AppVersionBuild>282174</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="MYNN">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N25° 2' 20.25",W77° 27' 58.43",+000013.25</WorldPosition>
            <SpeedMaxFP>-1</SpeedMaxFP>
            <RunwayNumberFP>14</RunwayNumberFP>
            <ICAO>
                <ICAOIdent>MYNN</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="D0">
            <ATCWaypointType>User</ATCWaypointType>
            <WorldPosition>N25° 1' 8.78",W77° 26' 21.04",+000400.00</WorldPosition>
            <Alt1FP>416</Alt1FP>
            <AltDescFP>AT_OR_ABOVE</AltDescFP>
            <SpeedMaxFP>-1</SpeedMaxFP>
            <DepartureFP>FREDY2</DepartureFP>
            <RunwayNumberFP>14</RunwayNumberFP>
        </ATCWaypoint>
        <ATCWaypoint id="FREDY">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N24° 59' 42.00",W77° 24' 45.00",+000800.00</WorldPosition>
            <SpeedMaxFP>-1</SpeedMaxFP>
            <DepartureFP>FREDY2</DepartureFP>
            <RunwayNumberFP>14</RunwayNumberFP>
            <ICAO>
                <ICAORegion>MY</ICAORegion>
                <ICAOIdent>FREDY</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="JUTED">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N24° 51' 8.00",W77° 34' 1.00",+003200.00</WorldPosition>
            <SpeedMaxFP>210</SpeedMaxFP>
            <DepartureFP>FREDY2</DepartureFP>
            <RunwayNumberFP>14</RunwayNumberFP>
            <ICAO>
                <ICAORegion>MY</ICAORegion>
                <ICAOIdent>JUTED</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="HEROM">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N24° 53' 48.00",W77° 45' 45.00",+005400.00</WorldPosition>
            <SpeedMaxFP>210</SpeedMaxFP>
            <DepartureFP>FREDY2</DepartureFP>
            <RunwayNumberFP>14</RunwayNumberFP>
            <ICAO>
                <ICAORegion>MY</ICAORegion>
                <ICAOIdent>HEROM</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="NICKO">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N24° 59' 27.33",W78° 10' 45.56",+010000.00</WorldPosition>
            <SpeedMaxFP>210</SpeedMaxFP>
            <DepartureFP>FREDY2</DepartureFP>
            <RunwayNumberFP>14</RunwayNumberFP>
            <ICAO>
                <ICAORegion>MY</ICAORegion>
                <ICAOIdent>NICKO</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="PEACH">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N25° 25' 46.67",W77° 46' 22.84",+010000.00</WorldPosition>
            <SpeedMaxFP>-1</SpeedMaxFP>
            <ArrivalFP>OLAHS3</ArrivalFP>
            <ICAO>
                <ICAORegion>K</ICAORegion>
                <ICAOIdent>PEACH</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="SOFAR">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N25° 31' 59.97",W78° 14' 52.89",+010000.00</WorldPosition>
            <SpeedMaxFP>-1</SpeedMaxFP>
            <ArrivalFP>OLAHS3</ArrivalFP>
            <ICAO>
                <ICAORegion>K</ICAORegion>
                <ICAOIdent>SOFAR</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="HEYDR">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N25° 34' 37.45",W78° 26' 54.78",+010000.00</WorldPosition>
            <SpeedMaxFP>-1</SpeedMaxFP>
            <ArrivalFP>OLAHS3</ArrivalFP>
            <ICAO>
                <ICAORegion>K</ICAORegion>
                <ICAOIdent>HEYDR</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="FANUP">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N25° 38' 44.80",W78° 45' 58.99",+010000.00</WorldPosition>
            <Alt1FP>19000</Alt1FP>
            <AltDescFP>AT_OR_ABOVE</AltDescFP>
            <SpeedMaxFP>270</SpeedMaxFP>
            <ArrivalFP>OLAHS3</ArrivalFP>
            <ICAO>
                <ICAORegion>K</ICAORegion>
                <ICAOIdent>FANUP</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="JEKER">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N25° 42' 20.99",W79° 2' 49.77",+010000.00</WorldPosition>
            <Alt1FP>14000</Alt1FP>
            <AltDescFP>AT_OR_ABOVE</AltDescFP>
            <SpeedMaxFP>270</SpeedMaxFP>
            <ArrivalFP>OLAHS3</ArrivalFP>
            <ICAO>
                <ICAORegion>K</ICAORegion>
                <ICAOIdent>JEKER</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="DOPLY">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N25° 45' 23.99",W79° 17' 13.37",+010000.00</WorldPosition>
            <Alt1FP>10000</Alt1FP>
            <AltDescFP>AT_OR_ABOVE</AltDescFP>
            <SpeedMaxFP>270</SpeedMaxFP>
            <ArrivalFP>OLAHS3</ArrivalFP>
            <ICAO>
                <ICAORegion>K</ICAORegion>
                <ICAOIdent>DOPLY</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="OLAHS">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N25° 50' 21.16",W79° 35' 58.06",+010000.00</WorldPosition>
            <SpeedMaxFP>270</SpeedMaxFP>
            <ArrivalFP>OLAHS3</ArrivalFP>
            <ICAO>
                <ICAORegion>K</ICAORegion>
                <ICAOIdent>OLAHS</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="FISHB">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N25° 51' 7.21",W79° 38' 1.93",+010000.00</WorldPosition>
            <Alt1FP>5000</Alt1FP>
            <AltDescFP>AT</AltDescFP>
            <SpeedMaxFP>250</SpeedMaxFP>
            <ArrivalFP>OLAHS3</ArrivalFP>
            <ICAO>
                <ICAORegion>K</ICAORegion>
                <ICAOIdent>FISHB</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="JEPSI">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N25° 59' 15.58",W79° 57' 8.65",+009900.00</WorldPosition>
            <SpeedMaxFP>250</SpeedMaxFP>
            <ArrivalFP>OLAHS3</ArrivalFP>
            <ICAO>
                <ICAORegion>K7</ICAORegion>
                <ICAOIdent>JEPSI</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="FRRDY">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N25° 59' 57.26",W80° 28' 24.83",+004300.00</WorldPosition>
            <Alt1FP>5000</Alt1FP>
            <AltDescFP>AT</AltDescFP>
            <SpeedMaxFP>250</SpeedMaxFP>
            <ArrivalFP>OLAHS3</ArrivalFP>
            <ICAO>
                <ICAORegion>K7</ICAORegion>
                <ICAOIdent>FRRDY</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="A10">
            <ATCWaypointType>User</ATCWaypointType>
            <WorldPosition>N25° 59' 52.86",W80° 33' 58.06",+003300.00</WorldPosition>
            <SpeedMaxFP>250</SpeedMaxFP>
            <ArrivalFP>OLAHS3</ArrivalFP>
        </ATCWaypoint>
        <ATCWaypoint id="KOPF">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N25° 54' 26.70",W80° 16' 41.60",+000000.00</WorldPosition>
            <SpeedMaxFP>-1</SpeedMaxFP>
            <ApproachTypeFP>RNAV</ApproachTypeFP>
            <RunwayNumberFP>9</RunwayNumberFP>
            <RunwayDesignatorFP>LEFT</RunwayDesignatorFP>
            <ICAO>
                <ICAOIdent>KOPF</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>

 

Edited by Phantoms
spelling

James

  • Replies 42
  • Views 5.5k
  • Created
  • Last Reply

Default ATC is like asking a McDonalds worker for flying instructions. 

 

 

 

  • Author

Just want to make sure it's nothing I'm doing that's causing it.

 

James

2 hours ago, Bobsk8 said:

Default ATC is like asking a McDonalds worker for flying instructions. 

This we agree on.

| My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

I wish you luck!

Despite what everyone says here the default ATC is quite immersive it works. That means 1) you can import a simbrief flight plan properly, 2) it doesn't pick the wrong runways, 3) doesn't forget to tell you to do stuff...

1 minute ago, ErichB said:

Fly on VATSIM. 

Fly on Vatsim=Fly on Unicomm.

 

 

 

Just now, Bobsk8 said:

Fly on Vatsim=Fly on Unicomm.

The flightsimmers ATC dilemma:

Option 1:

Fly with canned spaghetti ATC and get :

100% ATC coverage together with fake sounding voices, dumb instructions, conflicting instructions, no actual human interaction, ATC by key press, and 20 years worth of forum threads complaining about canned ATC

Option 2:

Fly on VATSIM and get :

(depending on the time and where you flying) sparse to excellent coverage of ATC.  You need to compromise your choices, but, you interact with real people, excellent ATC quality, other aircraft flown by real people, authentic sounding and a substantially enhanced overall sim experience. .  Events will always guarantee ATC coverage and there are many of those all the time.   The only difference is compromise of choice.  Nothing else

Can never understand why people bang on about realism but chose to fly with Option 1. There is nothing realistic about it.  Even third party options.  If VATSIM didn't exist, I think I might have given up simming entirely by now.

 

23 minutes ago, ErichB said:

The flightsimmers ATC dilemma:

Option 1:

Fly with canned spaghetti ATC and get :

100% ATC coverage together with fake sounding voices, dumb instructions, conflicting instructions, no actual human interaction, ATC by key press, and 20 years worth of forum threads complaining about canned ATC

Option 2:

Fly on VATSIM and get :

(depending on the time and where you flying) sparse to excellent coverage of ATC.  You need to compromise your choices, but, you interact with real people, excellent ATC quality, other aircraft flown by real people, authentic sounding and a substantially enhanced overall sim experience. .  Events will always guarantee ATC coverage and there are many of those all the time.   The only difference is compromise of choice.  Nothing else

Can never understand why people bang on about realism but chose to fly with Option 1. There is nothing realistic about it.  Even third party options.  If VATSIM didn't exist, I think I might have given up simming entirely by now.

 

I am getting ready too start a flight in the US, as I type this. Controllers on duty in the US, ZERO. 

Edited by Bobsk8

 

 

 

2 minutes ago, Bobsk8 said:

I am getting ready too start a flight in the US, as I type this. Controllers on duty in the US, ZERO. 

Well it is anywhere from 8am to middle of the night in the US at the current time Bob - and a working day.   I did say, it's compromise of choice.

Pathetic indeed!
This is once again a repulsive example of the way discussions are conducted on AVSIM and immediately go off the rails.
The OP has asked an understandable and perfectly legitimate question, namely whether he has done something wrong in the preparation of the flight plan that leads to the ATC giving him incorrect altitudes.
Instead of effectively making fun of the OP's question, it would have been sufficient and helpful to tell him that he has not done anything wrong, but that the cause is the faulty implementation of ATC by MSFS.
A discussion about the advantages or disadvantages of VATSIM compared to the in-game ATC is completely superfluous.

Edited by asanosho

5 minutes ago, asanosho said:

A discussion about the advantages or disadvantages of VATSIM compared to the in-game ATC is completely superfluous.

It is not superfluous at all.  It is an ATC option and a more realistic one at that - whichever way you chose to slice the cake.   No need for histrionics  lad.  

Edited by ErichB

7 minutes ago, asanosho said:

Pathetic indeed!
This is once again a repulsive example of the way discussions are conducted on AVSIM and immediately go off the rails.
The OP has asked an understandable and perfectly legitimate question, namely whether he has done something wrong in the preparation of the flight plan that leads to the ATC giving him incorrect altitudes.
Instead of effectively making fun of the OP's question, it would have been sufficient and helpful to tell him that he has not done anything wrong, but that the cause is the faulty implementation of ATC by MSFS.
A discussion about the advantages or disadvantages of VATSIM compared to the in-game ATC is completely superfluous.

Some people simply have waaaaaaaaaaay too much time on their hands and tend to post the same useless 'information' over and over again in every topic that concerns certain subjects which they apparently have a pet peeve with. Better get used to it. Or simply visit this forum less frequently (like I've been doing lately).

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.