Jump to content

Recommended Posts

Posted

Not sure if this has already been mentioned, but I'm pretty sure the FMC is a bit off when intercepting radials on SIDS. I have a picture attached below showing the Offshore 9 departure out of KSFO - the intercept point appears to be a few miles after WAMMY, instead of before it. Then the plane wants to try and turn back to overfly WAMMY instead of just continuing to SEGUL. I'm using AIRAC 1607, so I doubt its the nav data? Am I doing something wrong (I entered this SID just like I did for every departure previously) or is this a bug?

https://skyvector.com/files/tpp/1607/pdf/00375OFFSHORE.PDF

https://skyvector.com/files/tpp/1607/pdf/00375OFFSHORE_C.PDF

 

 

IMG_1722.JPG

IMG_1723.JPG

Posted

This specific SID is a bit shitty, because he intercept before WAMMY is nearly impossible.

Basically, you fly over waypoint SENZY, then turn left to heading 203 until you intercept radial 151 from PYE. The problem being, in order for the intercept to occur before WAMMY, you need to be on heading 203 no earlier than 5 nautical miles past SENZY ; even with a generous overfly margin and a very low rate of turn, it remain incredibly hard to achieve.

FWIW, the NavDataPro coding doesn't include WAMMY at all, it's SENZY, heading 203, intercept PYE R-151 (which mathematically happens after WAMMY), then SEGUL and so on.

I also find noteworthy that while the FAA chart's illustration does display WAMMY, the text description (which, unless I am mistaken, is the binding part, not the picture) does NOT mention WAMMY either, only SEGUL…

 

Anyway, my point is, this departure will cause just about every X-Plane addon to barf, and should not be taken as an example of "this plane's LNAV is broken". My personal assessment of it is "Jeppesen and/or Navigraph's coding of this procedure is quite optimistic and possibly broken".

Posted

Yea I actually mentioned the "it's on the chart but not the narration" thing over on the pilotedge forums. I was tempted to just delete WAMMY completely from the legs page tbh, but I wasn't completely sure about the FAA regs on this one so... I'll probably end up completely disregarding WAMMY; just wanted to double check this wasn't a bug that would reappear once I try other intercepts.

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...