Hi.

Been flying around 55 hours so far and what I noticed flying IFR flights (mostly in TBM930) that ATC always vectors me too high for final approach. When I look in the APP charts of that airport I am flying to the real altitude at that point is much lower than what the ATC vectors to. Then I notice the runway approaching and still don't have a landing clearance and ATC is bugging me to keep 3000 feet of altitude...

Sometimes I just cancel the IFR before final approach, but when I don't I am guaranteed to have to make a quick descent to the final. I wonder if the problem is with the MSFS2020 ATC itself as I doubt the problem is in the NavBlue MSFS uses.

Last flight I was on final approach to KSAN runway 27 and in the APP chart it says REEBO point is 2000 feet of altitude and 3,5 degrees descent altitude yet ATC vectored me to 3000 feet before landing clearance and I had to make a hard descent beyond that point so I don't overshoot the runway.

I think the ATC controllers in FS2020 get paid per thousand feet of altitude they can get every plane up to.  I'm in a 172 and they want me to go from 6000 to 12,000 feet for an approach.  I just switch to VFR at that point.  

At least you are getting vectored! Would be happy for a IAF or FAF vector at the point....

Just put the IAF in your FP - descend for it normally and you're good regardless to ride the rails to the #'s. Controllers love to 'slam dunk' you in the real world also 🙂

Edited September 12, 20205 yr by Flyfaster

2 hours ago, Concorde79 said:

Hi.

Been flying around 55 hours so far and what I noticed flying IFR flights (mostly in TBM930) that ATC always vectors me too high for final approach. When I look in the APP charts of that airport I am flying to the real altitude at that point is much lower than what the ATC vectors to. Then I notice the runway approaching and still don't have a landing clearance and ATC is bugging me to keep 3000 feet of altitude...

Sometimes I just cancel the IFR before final approach, but when I don't I am guaranteed to have to make a quick descent to the final. I wonder if the problem is with the MSFS2020 ATC itself as I doubt the problem is in the NavBlue MSFS uses.

Last flight I was on final approach to KSAN runway 27 and in the APP chart it says REEBO point is 2000 feet of altitude and 3,5 degrees descent altitude yet ATC vectored me to 3000 feet before landing clearance and I had to make a hard descent beyond that point so I don't overshoot the runway.

This is a bug reported and discussed before.

Ah finally, I thought it was just me. I was flying the 747 to dublin and ATC just didn't seem to be telling me to go lower or give clearance. If I went below 3000ft they told me to get back up there.

Then they gave me permission to land when I was on top of the runway. So what ATC want me to do in MSFS2020 is to stop all engines, put up full flaps and speedbrake and just let my belly flop on to the runway from 3000ft?

Just don't be using Self Loading Cargo or PACX otherwise they are going to be complaining about whiplash.

'Thank you for choosing the Boeing 747 as your favourite plane to fly with, now ATC have given me clearance foe landing so please keep your arms and legs inside the plane as we do the gravity drop. The Crew and I hope you had a fantastic flight and enjoy the landing'

On 9/12/2020 at 3:20 PM, kerosene31 said:

I think the ATC controllers in FS2020 get paid per thousand feet of altitude they can get every plane up to.  I'm in a 172 and they want me to go from 6000 to 12,000 feet for an approach.  I just switch to VFR at that point.  

Unless you are "Real Traffic" just transitioning their airspace.  At which point you are x thousand feed above your assigned altitude and need to immediately drop to 10000.  

I've found recently the opposite is true, as they order me to final approach altitude way early.  My last flight to KHSV from KATL, I was directed down to 2k way before final.  Seemed to fly half the state of Alabama at 2000 ft hoping not to take the tree's off the hills surrounding Jones Valley.

I find you have to cancel ATC before descent as both ATC and Navblue in MSFS are broken and incorrect in their data. I just determine my descent per the Jeppesen charts and flight plan provided to me from Navigraph and Simbrief. I just go to flight following in ATC so I'll be left alone.

Lee

Last time I flew the TBM 930 IFR, the ATC told me to go down to 7000 feet in an area with 6000 feet mountains. Then back up to 13000 feet. Then back down to 7000 feet. I just had to cancel IFR. 

I know ATC in MSFS is not perfect, but in a sense in real life you have to deal with a lot of similar stuff. I could be vectored high! ATC could ask to slow down or to give best forward speed! Perfect things happens only in perfect world !🙂  Of course pilot  in real life can always say "unable" which is not possible in MSFS!

51 minutes ago, Republic3D said:

Last time I flew the TBM 930 IFR, the ATC told me to go down to 7000 feet in an area with 6000 feet mountains. Then back up to 13000 feet. Then back down to 7000 feet. I just had to cancel IFR. 

Yup have stopped flying MSFS ATC descents altogether and just fly published arrivals and approaches to the IAF/FAF. ATC can and will kill you. Remember if they have a bad day you don't go home. They do 🙂

Edited September 15, 20205 yr by Flyfaster

2 minutes ago, sd_flyer said:

I know ATC in MSFS is not perfect, but in a sense in real life you have to deal with a lot of similar stuff. I could be vectored high! ATC could ask to slow down or to give best forward speed! Perfect things happens only in perfect world !🙂  Of course pilot  in real life can always say "unable" which is not possible in MSFS!

ATC is fairly unable in MSFS 🙂

1 minute ago, Flyfaster said:

ATC is fairly unable in MSFS 🙂

Yep you can ignore and don't have to talk to ATC supervises or FAA LOL But it would be nice if Aosobo could add to ATC "possible pilot deviation please write down phone number" LOL

I've found that if I just request a lower cruising altitude when I reach the TOD as advised by Simbrief or Foreflight, everything works out fine, and the ATC will get me on a decent final approach path.

I've heard a lot of people complaining about the ATC being useless, but I have to say that it's a big step up from the last one I used in FS2004. The vectoring to final approach doesn't send me miles out of my way, and so far they've respected my flight plan's arrival, approach and transitions every time. 

On 9/12/2020 at 3:11 PM, Flyfaster said:

Controllers love to 'slam dunk' you in the real world also 🙂

Not to the degree they do in the sim. I've been turned short "final" and told to call the tower at 15,000 AGL.

In the few IFR flights I've done, it's almost like ATC forgets about your altitude once you get to the approach phase, and then suddenly remembers "oh yeah, I'm supposed to make that plane intersect the ground," then wants you to to divebomb the airport.

I almost wonder if it wasn't set up with the expectation that ATC would tell you to descend via the SID, only whoever was supposed to actually program ATC to tell you that called in sick, so no one ever tells you to descend. 😉

 

 

Edited September 15, 20205 yr by eslader

3 hours ago, eslader said:

Not to the degree they do in the sim. I've been turned short "final" and told to call the tower at 15,000 AGL.

In the few IFR flights I've done, it's almost like ATC forgets about your altitude once you get to the approach phase, and then suddenly remembers "oh yeah, I'm supposed to make that plane intersect the ground," then wants you to to divebomb the airport.

I almost wonder if it wasn't set up with the expectation that ATC would tell you to descend via the SID, only whoever was supposed to actually program ATC to tell you that called in sick, so no one ever tells you to descend. 😉

 

 

Almost as funny as hearing all the 'other' traffic being told they are '20,000ft above assigned altitude'