im doing a flight from OTTAWA to TORONTO on AP , NAV ETC…8000 ’ ATC, in the middle of the route , the plane ( tried with cessna 172, and cessna caravan ) turn back by itself without doing anything else and want to return to were i left from. all the route seems to be perfect, no double waypoint etc…even if i disengage the AP and doing it manual to reposition the plane then re engage the AP the plane sitll want to return were i left. and doesnt want to continue the route.
and just before doing that, ATC ask to change frequency. so i wonder is it another atc problem or else.
Any chance you could supply your route, and the legs where you observed this behaviour.
Screenshots might be more illustrative, as long as someone could replicate.
Is this not a known bug for which there’s a workaround?
I’ve certainly had issues on the map screen when bringing a route in from Skyvector, via Littlenavmap, where an additional line is drawn between the Departure, and Arrival points. Building them by hand in LNM solves it, but I never spent any time working out what was wrong with Skyvector imported ones.
They always look okay in LNM, but MSFS interprets them wrong.
CYOW/14 DCT TUKIR RAGID4 CYYZ/15L this is the route i had from simbrief,
this is the route i had from msfs NAV LOG
CYOW TUKIR LIBEM CRUISE IGSAP UDNOX DESCENT RAGID DENKA DUGDA ONGOX
BEFNI ZTO CYYZ
plane going back at UDNOX everytime i tried it 3 times
DESCENT i think its not suppose to be part of the route but they put it in msfs log and
ATC doesnt ask to descend. i didnt try to descend by manual. didnt have time anyway because
the plane turn around before you do something else.
even on the msfs map its the same route but without the DESCENT suppose WAYPOINT.im
sure its not a waypoint but even atc doesnt ask to descend.
heres the answer…ive done another test from ottawa to toronto…arriving near UDNOX i wanted to make a test and descend to 3,000 as per the chart. and the navlog.
about 2 miles passing UDNOX ATC ask to continue to TORNI , so the plane again go aound and get back to TORNI about 70 mn . i let go to , arriving at TORNI …ATC ASK to continue to LIBEM way back again…so i dont know if the pilot is drunk or shoot himself with crack, but something goes wrong and what i think is the problem is ATC AGAIN. …after 1h45 of flight and going nowere.
sorry ive put a new post instead of replying to you just look down ive put the flight plan
no ATC as issues since the begining and i didnt saw any corrections
CYOW/14 DCT TUKIR RAGID4 CYYZ/15L this is the route i had from simbrief,
this is the route i had from msfs NAV LOG
CYOW TUKIR LIBEM CRUISE IGSAP UDNOX DESCENT RAGID DENKA DUGDA ONGOX
BEFNI ZTO CYYZ
plane going back at UDNOX everytime i tried it 3 times
DESCENT i think its not suppose to be part of the route but they put it in msfs log and
ATC doesnt ask to descend. i didnt try to descend by manual. didnt have time anyway because
the plane turn around before you do something else.
even on the msfs map its the same route but without the DESCENT suppose WAYPOINT.im
sure its not a waypoint but even atc doesnt ask to descend.
heres the answer…ive done another test from ottawa to toronto…arriving near UDNOX i wanted to make a test and descend to 3,000 as per the chart. and the navlog.
about 2 miles passing UDNOX ATC ask to continue to TORNI , so the plane again go aound and get back to TORNI about 70 mn . i let go to , arriving at TORNI …ATC ASK to continue to LIBEM way back again…so i dont know if the pilot is drunk or shoot himself with crack, but something goes wrong and what i think is the problem is ATC AGAIN. …after 1h45 of flight and going nowere.
[/quote]
I just popped that in to Skyvector and it looks okay, as you’d expect. I’m not sure I’ll have the time to fly it this evening, but I’m always up for flying users routes, and 222nm is not too onerous.
So this is filed as IFR?
TORNI is all the way back near TUKIR. That’s pretty odd. Can we assume that this is not aircraft related, as I’d like to fly this in the Mooney?
I’m flying that exact route atm on the TUKIR -> LIBEM leg. I’ll let you know how it works out for me.
I checked in Navigraph and FS2020 and the RAGID4 arrival is no longer valid. It has been replaced by RAGID5. Perhaps this is why the flight can’t complete, because RAGID4 does not translate any more.
I’m coming in and it’s RAGID5 for me as well. That could indeed be the issue.
I’m trying to find which cycle replaced RAGID4 with RAGID5. On a Google search I see a fly-in from 2019 that was still referencing the approach. I’m guessing that the Skyvector database being used is out of date, leading to this issue.
Currently flying that plan in the Mooney, just coming up on LIBEM, using RNAV 15L Z.
I foolishly turned on live weather, and live players. It’s 3 degrees at 4000ft, as low as I am able go, its cloudy, and I have no anti-ice. 
Coming up on RAGID. ATC is a little confused. I’m at 6000, but it thinks I’m at 4000. Luckily the clouds are just below me now, and further SW have all but gone. Lucky escape. I did catch some ice, but at only -3 degrees this swiftly melted. Far more concerned about the Air Canada that has been following me, and is now 200ft above me, and a quarter mile off my left wing.
Still good, approaching DUGDA, and now with Approach. On way to ONGOX, and have not been turned about.
On final from OTEPO (IAF) to SEKUR (FAF).
Touchdown!
It wasn’t an ILS approach, but I did have the ILS for 15L tuned on NAV2. It never captured the localiser for some reason. I might just give that a quick go in isolation. The AP pitched up massively, which I had seen in the past. Ended up having to land manually, but that was a really enjoyable flight, and I had no ATC issues, other than the part where it thought I was an a different altitude. I ended up clearing that by requesting an increase in altitude instead of a decrease, and I think that reset it.
1 Like
I like the CYOW - CYYZ route. I fly it often, typically in the TBM. May have to try it in the Mooney at some point since it’s reasonably fast. But in these conditions with icing… Ouch… I just did CYGK to CYOW wiht the C182 and I was encountering icing at 4000 feet as well.
no its not , im flying cessna 172 and cessna caravan with no problem, its comming from the atc, the atc saying to go back to torni 70 mn , not the aiprplane.
i was feeling that the atc had control of the aircrafts when reaching UDNOX.
and push them to go back, by itself. i am AP, NAV, FD, IFR, not touching nothing.
more.
I never got that. But in flying that plan, and flown around CYYZ, I think there is something wrong with the ILS for runway 15L, and 15R. They seem very shallow. Runway 5 was fine. When approaching 15L, or 15R, unless I’m skimming the roofs of houses, the HSI shows the horizontal line buried at the bottom. The AP in the Mooney just decides to trim up until it goes into a stall, again this does not happen on runway 5. 15R seemed a little better, but also seem misaligned, and off to the left of centre.
Other those airport oddities, I never saw any unexpected routing issues, either by ATC or the AP. The one anomaly was the altitude one, and I think I may have managed to trip up ATC somehow.
i will try with different approaches and different runways. but i dont htink it will solve the problem because the airplane goes back at UDNOX far from the approach.