I am trying to program in the PORTE3 departure out of KSFO (runway 01R) and came up with the attached KSFO.txt. I doubt it is entirely correct, and I cannot figure out how to tell it to follow the 350 radial from SFO until 4 miles DME.Anyways, here is what this procedure is drawing on the map at takeoff:http://forums.avsim.com/user_files/21059.gifHere it is intercepting the 350 radial (sort of):http://forums.avsim.com/user_files/21061.gifHere it is flying well past the 4 DME point, and looking at the LEGS page you can see the FMC has gotten very confused as to where this point is (6902nm away now). It looked OK at takeoff.http://forums.avsim.com/user_files/21060.gifCan someone else try this KSFO.txt and takeoff of 01R with the PORTE3 departure. Should this work? Was this kind of thing tested? This seems pretty buggy, but it could be more poor attempt at a SID.Lee Hetherington (KBED)

Lee,Does this work? (don't have time at the moment to go try it myself...)SID PORTE3 RNW 01R KEEP HDG UNTIL 1000 HDG 320 INTERCEPT RADIAL 350 FROM NAVAID SFO KEEP HDG UNTIL 4 FROM NAVAID SFO HDG 200 INTERCEPT RADIAL 135 FROM NAVAID PYE NAVAID PORTE NAVAID PESCA NAVAID WAGESRyan

Lee-Anthony is looking into those issues... no worries- they should (;-)) be fixed for the update.

Ryan,I think that sort of works. Does KEEP HDG after an INTERCEPT mean keep track? That is what you want when you are tracking a radialThis screenshot has me concerned, however. It was supposed to fly heading 200 until intercepting the PYE 135 radial, but it appears it has computed (INTC) without properly factoring in the radius of the turn, so it overshoots 200 all the way to 175. What is with the straight line from SFO 350 8 DME to (INTC)? It appears to be trying to get on that line. I would have expected HDG 200 to mean just that: fly heading 200. Am I expecting too much?http://forums.avsim.com/user_files/21149.gif(Note, I extended the SFO 4 DME to 8 DME just as an experiment.)Lee Hetherington (KBED)

Yeah Lee, I think Anthony or Lefteris already posted that all waypoints right now are treated as overfly and it doesn't yet predict the turn radius the way PIC does. It's like the opposite thing going on - PIC does all predictive turns but can't do overflys, whereas it's reversed on the NG. I hope they can add the turn prediction soon...Ryan

Lee !How do you manage to get that green doted sircle around SFO displayed ?I've been looking all over for it !!Steinar

Via the FIX page,You enter the VOR, then the radial and distance.Useful for DME ARCS, or for reports like "BAW062 call me 60 miles of LON VOR" then you draw and arc of 60 miles of LON VOR and for ETOPS operations.Wait a little for the PMDG manual, I think you will get a VERY more complete description of the FIX page.http://forums.avsim.com/user_files/21883.jpgRegards[table border=0 width="100%" cellpadding="6" cellspacing=0][tr bgcolor=0066CC][td valign=center width=50%] Charly Diaz Azcue[br /] BAW062 [br /] HC270CH[td valign=center width=1%] Q8 [/td][/tr][/p][/p][/table]

Actually, with UNTIL 4 kinds of statements it is not anticipating the turn (correctly). Otherwise, it seems to be anticipating turns pretty well.Lee Hetherington (KBED)