Attempting to use the GOMO5N departure from LPAZ, the data places the Santa Maria vor (VSM) in the middle of the water. This causes the FMC to create a route doubling back on itself.
It seems like the VSM vor shouldn’t be in the procedure at all, because its not positioned to be useful in such a procedure, from either runway, and doesn’t appear specified in the “paper” chart.
Hello! Thank you for the feedback.
We shall investigate. Large parts of the team are on vacation until next Monday, but I’ll keep you posted!
Kind Regards,
Malte
Hello, I think this is just a reminder to turn once you hit 1500’ from the VSM VOR. There is actually no waypoint-just an altitude to start your turn to intercept the 209 degree VOR.
This is caused by whatever is rendering the procedure on the map not obeying rule 3.12 of attachment 5 of the ARINC424 spec.
If you say “the FMC doubles back on itself” means the FMC doesn’t correctly implement this rule either. You didn’t specify which simulator or which add-on you are talking about.
Anyway, the GOMO5N SID uses the VSM VOR as an anchor for the leg to GOMON. You do NOT overfly the VOR, you simply put it behind you so that you are on a straight line between the VOR and the point.
The correct sequence is: climb on heading 358 to 1500ft, then turn left to heading 206 until you intercept the line between VSM and GOMOS, and then follow that line to GOMOS.
Yes, simulator issue.
there’s two separate issues here:
-MSFS doesn’t know how to interpret this and therefore draws a wrong flightplan in the simulator.
-Navigraph charts doesn’t know how to interpret this either and also draws the wrong flightplan in the browser and on the iPad
