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.

Missing some RadarContact heading ATC messages

Featured Replies

Hi,i have some problems with RadarContact ATC.After takeoff i receive some instructions from ATC that send me offcourse of my loaded flighplan.All ok with altimeter, but after few minutes it seems that ATC fail to send me heading instructions, so i fly out of assigned ATC route. I receive a messages saying that i fail to accomplish with ATC heading instructions (but i don't receive them). After a while ATC send me back on course (2 or 3 fixes) and then redirect me toward my route. This happen one or two times each flight.What i have to do to solve this problem?Reinstall Radar Contact or there is something that i miss on configuration?This happen from about one month. No change in computer configuration.Thanks in advance,Maurizio BalvettiP.S. - Never have failed to respond to ATC instructions. (key 7 or 1 of my keyboard). No outstanding ACK :-)

Are you getting credits for each of your waypoints? In departure the acceptable radius is two nm and then higher up 5 nm.If your first waypoint is within 30 nm or you have selected either of the alt. restriction options on the controller tab you will be expected to navigate on your own through all of the initial checkpoints. Look at the top of the RC window as you are flying and see if the next waypoint indicated progresses as you are flying. In addition look to see if you are flying the same heading.It also would not hurt to make sure FSUIPC is current from the links at the top of this forum since that reports your position and heading to RC.Can you clarify what you mean regarding your "month" statement? Did this just start a month ago or are you saying it happens only occasionally about once a month. Is a particular scenery involved?It would not hurt to update your scenery database insuring that you are using makerwys.exe version 4.41 (or beta 4.42 from the FSUIPC support forum) available for both FS9 and FSX from the links posted above.

Are you getting credits for each of your waypoints? In departure the acceptable radius is two nm and then higher up 5 nm.If your first waypoint is within 30 nm or you have selected either of the alt. restriction options on the controller tab you will be expected to navigate on your own through all of the initial checkpoints. Look at the top of the RC window as you are flying and see if the next waypoint indicated progresses as you are flying. In addition look to see if you are flying the same heading.It also would not hurt to make sure FSUIPC is current from the links at the top of this forum since that reports your position and heading to RC.Can you clarify what you mean regarding your "month" statement? Did this just start a month ago or are you saying it happens only occasionally about once a month. Is a particular scenery involved?It would not hurt to update your scenery database insuring that you are using makerwys.exe version 4.41 (or beta 4.42 from the FSUIPC support forum) available for both FS9 and FSX from the links posted above.
Thanks for your kind reply.I forgot to say that i am using FSX SP21) Before what is happening now when i loaded the flightplan in FMC and in RC with SID departure everything was ok.2) Yes, all waypoints are indicated correctly in PFD and RC window and are cleared after passing them even if i fly offroute.3) FSUIPC is the latest version available4) "month" means that every flight from that date has the same problem even if departure and arrival are different. A short flight or a long flight have the same problem.5) I didn't use makerwys.exe. I use AIRAC from Navigraph. 6) Might be that this problem is generated from My Traffic X program ?Thanks in advance,Maurizio Balvetti
5) I didn't use makerwys.exe. I use AIRAC from Navigraph.
Sorry, i misunderstand about makerwys.exe. icon8.gifYes, I did it often even if i don't change anything on scenaryMaurizio Balvetti

Hi,i made a closer inspection on what is happening.After flying a little offline after takeoff i receive an atc message saying that i can resume my flightplan but soon after i receive a new message saying to fly about 180

  • Commercial Member
Hi,i made a closer inspection on what is happening.After flying a little offline after takeoff i receive an atc message saying that i can resume my flightplan but soon after i receive a new message saying to fly about 180

It sounds like your FMC AIRAC Terminal Procedures database (SID/STAR/IAP) does not match the flightplan you are sending RC. I say this because it started from your Navigraph AIRAC update. Here are two things you can do:1. Within RC choose no altitude restrictions (if you wish to use VNAV from your FMC) or altitude restrictions (RC will command altitudes) and you are on your own until the waypoint in your plan outside of 30 nm. This means your FMC can guide the aircraft up until 30 nm. At that point the waypoints from then on in your FMC and in RC must match. In the plan sent to RC include only the waypoints starting outside of thirty nm.2. If you have a flight planner that can export plans into your FMC use the planner's procedure database and important the entire plan into your FMC and on arrival only select the active runway, not the STAR, in the FMC when approach assigns the runway. If your planner supports AIRAC updates that would help.It also is important to understand that in RC when you are told to Resume Own Navigation it means to fly direct to the next waypoint in the RC window from your present position, not return to the original path. On the Smiths type FMC in Boeing models as used by PMDG, you punch the top left key twice and the LEGS page which gives a direct-to path and EXE the change.In RC if you miss a waypoint you can go to the extended menu (9 I believe) and choose direct waypoint and it brings up a list of the next few waypoints that you can select. Then the RC target waypoint will be updated and you can fly direct to there. (This does NOT apply to delay vectors due to crossing restrictions or holds if you implement them.)I also recommend you exclude waypoints within one mile from takeoff from RC's plan since they can be very hard to cross under certain conditions and within the 2nm tolerance.For a flight planner I use FSBuild payware. It has a little known option that can be set under Build options called Build From Route/Grid table. After your first build you enable it and then any changed you make in the route table will be reflected in your exports after the next build. This allows you to drop waypoints in the plan sent to RC. In other words if you include the SID in its planner you might export the whole table table to your FMC, select the Build From Route/Grid Table option, drop the close in waypoints, and then rebuild the plan sending it to FS (RC).Hope some of this explains what might be causing your problem and how to work it out.

  • Commercial Member
Hi,i made a closer inspection on what is happening.After flying a little offline after takeoff i receive an atc message saying that i can resume my flightplan but soon after i receive a new message saying to fly about 180
if this is reproducible, make a log. make sure you click debug BEFORE loading the .pln. i can tell you what is going wrong.jd
Hi,i don't know how to make a log. What's about "debug" ?Thanks a lot for all kind replies :-)Maurizio Balvetti
  • Commercial Member
Hi,i don't know how to make a log. What's about "debug" ?Thanks a lot for all kind replies :-)Maurizio Balvetti
pinned topic at the top of the forumjd

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.