Description of the issue: During multiple airline missions with the 737 max I have been ordered to go back up to a cruise alt of FL350 even though I am less than 100 miles from the airport. It doesnt request a decent, and when I start to decend on my own the ATC proceeds to badger me to return to FL350 all the way to the landing. Sometimes I have been able to still complete the mission but most of the time if that mission step is not met, I cannot proceed to the stop area or park or anything even after a successful landing. The only option at that point it gives me is to “skip to decent” and when I do that it puts me 100 miles out from the airport again on an awful approach.
If applicable, which aircraft is experiencing this issue: 737 Max
FREQUENCY OF ISSUE
I would say this happens in 2/3 missions with the airline 737 max missions.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
1.Fly according to flight plan
2.Start decent at a sensible distance from airport
3.Listen to ATC badger you even when you are on approach mode or even have landed at the destination airport.
YOUR SETTINGS
What peripherals are you using, if relevant:
Turtle Beach yolk, keyboard, mouse, xbox controller
[END OF FIRST USER REPORT]
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•
I also tend to encounter this on any mission except for some with ILS approaches that remain IFR all the way until landing. Otherwise, either I get a descent too late or they basically force me to Cancel IFR and dump me VFR with too much energy too high for the approach.
Generally speaking, you should start to descend 10nm plus 3nm miles per 1,000 feet you have to descend. So if I have to descent from 36,000 feet to 4,000 feet I would need about 32 x 3 + 10 = 96nm + 10nm = 106nm from the airport. The extra 10nm is because you will need time to slow down and bleed off energy before the approach.
Not only in missions, also in free flight.
It’s worth noting that the first days after release, ATC worked correctly in this regard, provided that a flight plan with STARs was filed.
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes
Provide extra information to complete the original description of the issue:
• its not just the 737. I get it on 80%of my missions. Being told to expedite my climb to 9k while im on final.
If relevant, provide additional screenshots/video:
•
Yeah, when I have done it correctly like you say I am able to land safely and park, but the mission still will not register as completed and will force me to “skip to decent” even after 3 or more hours flying on AP to try and avoid the skip deduction. Then when I skip to decent it puts me in a dive with no throttle and no airspeed, and then I am able to land it by some miracle and they deduct all the money for the skip penalty. Its garbage.
That is insane that they probably fixed something trivial and meaningless and broke something so vital. I am not familiar with STARS, unfortunately I am using xbox for my platform, so I am limited with flight planning tools. I would love to be able to use one. Although I am not confident the game will recognize any deviations from the default path and will probably not allow mission completion.
I just want to add that they are making forward progress in this. I’m in the SU3 beta and just did an approach into KDFW and ATC talked me down the whole way in a timely manner that matched my arrival and approach procedures.
For anyone who wants to contribute on this issue, Click on the button below to use this template: