Jump to content

Recommended Posts

Posted (edited)

When going direct any waypoint that is the beginning of a transition on a STAR, and adding a crossing restriction distance BEFORE the waypoint i.e. KIIDD/-20, the FMS does not accept it and results in an error ALONG TRK WPT N/A.   However if I type KIIDD/+20, it will accept it.    I tested this at several airports (ABQ, ELP, OKC) with STARs and it occurred at all of them.

But it works at waypoints/VORs when a STAR is NOT loaded in the FMS.  I could fly direct KIIDD, stand alone, and cross -20 east  or west (+20) if it was just KIIDD in the FMS and no STAR loaded.  Looks like the FMS coding doesn't like a crossing point BEFORE a waypoint that is the beginning of a transition.    Every waypoint after the first waypoint works fine +/-.  

947706796_CL650-2022-05-1213_57_12.png

crossing1.png

Edited by Chaz

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...