Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ATC redirection after deviating

Featured Replies

OK I admit I am not a good flyer, so I tend to wander of course. RC2.2 lets me know, without sparing my blushes, and then tells me to turn onto a heading that seems totally wrong.Yesterday I was flying Orly - London and went wide on the sharp turn onto 278 (or thereabouts). I was told of the error and asked to stear 105!! I ignored the message and steared to rejoin the track. From then on until just before landing I was repeatedly asked to turn onto an ever more southerly heading. I even requested, and was accepted for, 'direct to the next waypoint' to force the situation and try and clear the problem. But still I was prompted to turn back.I have had this before and my reluctance to follow orders this last time, was that when I did before I flew thru' the track and on and on and on without ever being redirected again!Apart from flying more accurately what can I do to satisfy the RC2.2 controllers?Nigel

Nigel,Sounds like you missed a waypoint. Watch the scorllbar. If it doesn't change to the next waypoint, and you don't hear a "Ding!" after passing it, you weren't close enough to it to get credited.

  • Commercial Member

sounds like you missed a checkpoint. if you file a checkpoint in your flight plan, you are expected to progress it, within 10 miles.if you had departure procedures enabled, you have to fly within 2 miles of every checkpoint in your departure procedureApart from flying more accurately what can I do to satisfy the RC2.2 controllers?i think you answered your own question ;-)

I accept that I was wrong but for realisim I am sure mistakes are made in the air too. Surely in real ATC they don't say "you've been a bad boy, now fly back to the waypoint and then turn round and then come back here and continue on your track", I have not heard that in many many years of listening. Even RC is forgiving on altitude excursions and doesn't say go back and try that again!Nigel

Nigel,Real ATC gets really unhappy when pilots are off their filed route without notification and permission because of the closeness of other aircraft on other routes.However, in real life as in RC you can request direct another checkpoint. If this happens again, request the next checkpoint, and fly towards it when granted.This is all speculating that you really did miss a checkpoint and it's not something else. If you do miss, watch your scrollbar and see if the number doesn't advance when you pass the checkpoint.

Well I did try to 'force' the situation and did request direct to the next waypoint and it was accepted. But still the controllers kept trying to get me to turn back. I think as far away as London, they were directing me to fly back to the Orly waypoint! But apart from those prompts the ATC control was O.K.Nigel

  • Commercial Member

was your first checkpoint within 40 miles of the departure airport? if so, you had a departure procedure, and those are a little less forgiving in terms of missing checkpoints

I can suspect what is the problem in your situation, because I have experienced it also:Let us say you have "missed" waypoint no.1 after departure.You proceed along your flight plan, but you are constantly requested to turn back, towards the direction of the missed waypoint no.1As you continue flying along your flight route, you now pass over waypoint no.2 and maybe waypoint no.3. But RC still wants you to fly back to waypoint no.1, which you missed.What is very important is that when you request a "Direct to", you request it for a waypoint in your route which lies ahead of your current position.If you request a Direct to the next waypoint to the one appearing as being "active" in the scrollbar, you will be granted a "direct" to waypoint no.2 in our example, which is still behind you. Even if you request a "Direct to" Waypoint no.3 in our example, it wil still be behind you. Thus, even though you are granted the "Direct to", you are still expected to turn and fly back.Solution: Make sure you request a "direct to" a waypoint which is lying ahead of your present positionStamatis

  • 4 weeks later...

Hmm - makes me think of an experience i had once. My destination airport was Van Nuys and not far from this airport i was told to keep a westerly course (some 270 degrees) and so i did. For 10 NM, for 20 NM, for 30 NM - hmmm - for 40 NM (what's going on), for 50 NM - far out over the Pacific on my way to Hawaii. What's going on????? I took over control and was lectured about heading 270 degrees - and Jamie saying "Roger OK" (or whatever), but i had neither the time nor the amount of fuel to visit Hawaii, so i closed my ears and made it back to Van Nuys. After having turned of the engines i was still told to climb to the last assigned altitude, heading west.I almost wished i could strangle Jamie that day - not to mention the controller... :-lolCheersLars

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.