After I skipped cruise, I’m being spawned at start of IFR approach, and comms are forcing me to CANCEL IFR even if severe IFR conditions, then I’m forced to call an airport with VFR comms
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
YOUR SETTINGS
MEDIA
Please add a screenshot or video of the issue occurring.
Could you edit your post adding required and detailed information in the “Reproduction Steps”. It is very important for the devs/users to replicate/contribute.
You mentioned that you used the “skipped” functionality, so this is an example of key information that you should provide in “Reproduction Steps” (among others).
From what I’ve seen, this only happens when the destination airport is untowered. The sim seems to have no way of handling an IFR approach and landing in these circumstances, so it takes the easy way out and just cancels IFR. This issue is magnified by the fact that the majority of airports Career mode sends you to, especially pre-Airliners, are untowered.
This has less to do with career mode and more to do with the broken ATC in MSFS being too stupid to vector you to an approach of an untowered airport, even though it has all the information it needs in the flight plan.
Not only is flying VFR through clouds illegal in real life, it can also be deadly. Six months later and only six upvotes for this… One reason I don’t bother reporting the dozens if not hundreds of bugs with ATC/career mode. We really need an SU dedicated to ATC/career mode…
Digging into this a bit more, it seems to be another difference between Europe and the US. Apparently unrestricted airspace is more common in Europe, while it’s rare in the US above 1200ft. The thought of flying through clouds without ATC separation is wild to me, but I’m guessing the places where it exists in other countries are not heavily travelled.
Meanwhile, I have been surprised at how many close calls I’ve had with other aircraft while flying random routes around the US (again, something the ATC should be preventing but does not even notify you about until long after the TCAS starts screaming).
My post above still stands though: Every time ATC tells me to cancel IFR, I have been in Class E airspace, which requires you to be in contact with ATC in IFR conditions. If you’re flying into an untowered airport with no ILS, ATC is going to be asking you when you have the airport in sight. Even then, I don’t think they will be requesting that you cancel IFR. If you don’t cancel in the air, you’d be canceling after you land.
If you forget to cancel, ATC will be calling the airport or sending the police if they can’t get ahold of you to make sure you’ve landed safely if they don’t hear from you (something that can’t be simulated, fortunately! )
)