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.

Checkpoint Not Credited

Featured Replies

I filed a flight plan from Kabul (OAKB) to Khojaghar (OAKG), Afganistan. I used Bagram (OAIX)as my first and only interim waypoint. I realize it is within 30 miles of Kabul and was very careful to fly directly over the base. Received the "ding" (more than once, in fact it dinged several times as I flew over the base) and the next waypoint, Khojaghar, immediatley appeared along with the remaining distance and relevant heading. A few minutes later the controller says I've strayed off course and wants me to do a 180 back toward Bagram "until receiving suitable for own navigation". The first time I flew the controller's required heading, arrived over Bagram again, got "dings" again and headed back toward Khojaghar. Same story! I tried 3 times with same result each time. Then I remembered on Sunday I had a similar issue with a waypoint (a VOR)inside 30 miles on a flight from Alexandria to Shreveport, La. I'm using FS9 and RC3.1. Oh, and I can get the second page on the adventure menu, but it will not let me select direct next checkpoint. All the other options, including cancel IFR work, but not direct checkpoint. Can't understand how the program recognizes the waypoint, dings, changes the adventure menu to the next waypoint and then performs as though I've missed the waypoint? Any help would be appreciated.Jim W.

  • Commercial Member

send me the .pln file, and i'll try it.was it just oakb..oaix..oakg?what is the total distance of the flight?jd

I had a similar problem flying from CYYT to LFVP (route was CYYT-YYT-LFVP) with multiple dings and all. I ended up just shutting down RC3 and flying VFR to LFVP. It was only a short flight anyway!!

Devin
CYOW

  • Commercial Member

a number of my beta testers have tried this, including me. i flew the .pln file with v4, and didn't have the problem. john burgess flew it with v3.1 and had the same results as you did.putting our heads together, i think we have the answer. in the manual we state that you need to have a waypoint (ndb, intersection, or vor) somewhere near the arrival airport. in your case you don't.in cases like this, we suggest adding one near the arrival airport, or include the arrival airport as a waypoint in your plan.i believe john or doug has sent you a new .pln, would you give it a try.the reason why v4 worked for me, was because i fixed that problem. if there are no checkpoints in the flight plan, i make the arrival airport the last checkpoint. i guess we know it works :-)let us know how the new .pln worksjd

Thanks jd!! Looking forward to V4!!! I've almost wornout V3.1 ;-)

Devin
CYOW

I inserted a waypoint (self generated fix) near the destination airport and it worked perfectly. Thanks for the help.

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.