[Just realized that the one in question here isn’t a fix, my apologies! Though, just to show how for example some are set up this way.]
Is there a reason behind having a random fix on an arrival or departure procedure?
Obviously it’s simple to remove it, I’m just wondering if there is a purpose behind it. There are some I have noticed that are either several hundred and sometimes a few thousand nautical miles away, so that’s also why I wondered if it is just a mistake. Also, I do use SimBrief if it’s a known issue while using it for IF.
No worries either way just trying to learn and/or clear it up so I’m aware! Thanks in advance!
Not sure how I didn’t recognize that! Thanks, @Veloist ! I know there’s one I may or may not have screenshotted that was at least 1,000 nm away. Is that where sometimes—as you said—the out of the way fix or etc. makes ‘Act. Leg,’ easier on the turn?
If you’re getting random fixes outside of the approach procedure then it could be from copy+pasting a flight plan from another source, like simbrief or flightaware
Sometimes when I copy+paste I do get a random fix and I have to delete it. The reason why that happens—I guess it’s just decoded erroneously.
That’s why any time I do a copy+paste flight plan I ensure all the fixes do lead to a direct path
I figured it was a possible SimBrief[/technological] issue—specifically referring to the ones several hundred or thousand miles away. Thanks, again, @Veloist !
Theres only so many letters they can use for fixes so there are duplicate fixes and sometimes youll get one in Australia when you file a STAR for Baltimore. Same thing happens every now and then on the IF NATS, but, they seemed to have imrpoved it
And it may not entirely be simbrief’s issue, I think sometimes when plugging in a complete flight plan, if there are duplicate names for a certain waypoint then whatever decodes that flight plan in IF gets confused and just goes with that wrong one
Thanks,