When you landed and were reprimanded for entering a taxiway, were you also experiencing issues with ATC or the pilot declaring intentions to land on a runway which was contrary to the original flight plan (usually a runway which isnt reconmended and in the opposite direction)?
For example, the original flight plan may have been Rwy 23R (Recommended) into a head wind, but instead permission or declaration was given for landing upon the opposite runway of 05L with a tailwind.
The reason I ask, is because I’ve been experiencing these two issues together a lot, and it seems to have some correlation, which may be why sometimes we don’t receive the penalty and sometimes we do.
My theory is that landing on the runway in the opposite direction (even if permission or declaration is given) it’s registering us taxing down the runway to park, instead of landing, because the original flight plan which was filed with ATC conflicts.
yeah that make sense but i am pretty sure it’s not the case. I mean normally I check the recommended runway infront and adjust my flightplan before filing it. Also all communication is normal when this issue happens.
Need to do some testing on your theory. I noticed too that atc is changing flightplan in flight since SU2, especially at arrival.
Update: all said above is just happening. Recommended runway is 18L as I also filed in my flightplan. ATC has changed it to 36R when I reached TOD. Normally I would request for the right runway but will keep it like this and see…
2nd update… yep got the penalty
Your theory holds up for this flight but need more flights to get a consistent result
It’s true that the EFB changes automatically when approaching from SU2, but even when it does change, sometimes the bug appears and sometimes it doesn’t, so it’s hard to say for sure.
Flight plan with recommended runway, approach said runway and then ATC deviates from the flight plan and approves landing on the opposite runway. I then use the Coms tab to reselect my original planned runway which is approved, but then upon landing I get dinged.
From what I recall, every time I’ve been reprimanded for landing on a taxiway and overspeed, it’s been paired with the ATC deviation from the original flight plan.
Next time I’m on the sim, I’ll experiment with it and see if the theory is consistent with reality, and see if it holds any weight. If so, then maybe we have a solution, if not then at least we’ve ruled out the possibility.
And maybe we find a
Workarround. This bug is the reason you can not make another mistake during the flight. Its a 25% penalty.
I also noticed that right after touchdown i got the did you recieve my last message from atc warning. I am sure that i acknowledged every message before landing. Right after landing i get the taxiway penalty and the taxi speed penalty
I get that “recieve my last message” also randomly but I don’t think it is related. Didn’t get any penalty everytimes when it happened, that message was there also in SU1
Everything according to flightplan and atc didn’t send me to another runway - no penalty
Almost everything according flightplan, on approach atc send me to another runway but this time (different than yesterday) I selected the original runway by using the atc menu - still got a penelty
Consistent factor I can see so far is ATC doing the wrong stuff
I also tested it with two flights yesterday, albeit to the same destination airport.
ATC stuck to the original filed flight plan both times and had me land Rwy 02 at KCDA, via RNAV approach. Both landings were successful with no penalty.
So far, I’ve been unable to test a flight with ATC directing me to the opposite runway. I was hoping to test the theory on the same airport to limit the variables. Hence both approaches into KCDA.
Did ATC change your approach as you declared your intentions to land?
For example, if you were filed to land on Rwy 23, but ATC granted clearance to land on Rwy 05. This conflict seems to result in the Twy penalty. It needs further testing, but so far there seems to be a strong correlation from my point of view.
Interesting… going to test that. Did already a bunge of tests on the possibilities earlier on this topic but had too many different results to come to a conclusion
We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes. Vip Pilatus 12. Taxiway Penalty while landing on runway on almost every mission. It is now even happening with Firefighter missions flying the AT-802.
Provide extra information to complete the original description of the issue:
• I believe you have disgruntled saboteur employees corrupting your program. OR a bunch of glue sniffing meth-head amateur programmers hiding in corners picking their noses or watching ■■■■ instead of working.
Seriously though, if you don’t do something soon to correct the multiple problems then we will join the other half of people who have already left.
Are you getting this? I HAVE BEEN VERY PATIENT AND HAVE HAD QUITE ENOUGH OF THIS HALF-BAKED BETA TESTER PROGRAM YOU CONVINCED AND CONNIVED US INTO PURCHASING!
DO SOMETHING BEFORE YOU ARE OUT OF BUSINESS AND OUT OF A JOB! YES I AM SHOUTING!!!(AD INFINIUM)
If relevant, provide additional screenshots/video:
•
yeah that make sense but i am pretty sure it’s not the case. I mean normally I check the recommended runway infront and adjust my flightplan before filing it. Also all communication is normal when this issue happens.