Hi All,I've been lurking here for a few months now, so I'd thought I come out of the shadows :-batI've started writing some simple STARS but need a little help with the TEDDY2 leg shown below.What's the best way to define the FL290 crossing ALT 50NM East of HNK? Do I need to SLEW there, note LAT & LON and add that as a custom fix, or is there a more elegant way?Many thanks!

Hello Mark !I've been fideling quite a bit with the SID/STAR syntax for a couple of weeks now. In my opinion I think adding fixes is the easyest way to do allot of things.You don't have to slew your way to get the LAT & LON for the fix. As long as you know where it is in distance and HDG/radial from another navaid you can use the syntax "COLOCATED" instead of LAT & LON.Ex:FIX D50HNK COLOCATED HNK 090 50I've also found it necesary to insert additional fixes like:FIX LT (lefturn) COLOCATED VOO 350 1This, just to make it turn the righ way according to the actual SID.To make a ARC-DME in an aproach pattern you will (so far) have to insert several fixes with the same distance parameter and just change the radials to the NAVAID with increments of 10 or 20 degrees. Be also aware of this:To overfly a waypoint (ex, not to start a turn before you have passed the waypoint) you should use the syntax "NOT BEFORE 0 FROM NAVAID/FIX XXX"Thanks to Lee Hetherington for this advice!I don't know if this will be changed in the upcoming patch, nor do I know if they will add further syntaxes to make SID / STAR scripting even more advanced.Maybe Lefteris can answer this ? Kind regards,Steinar Thom

I don't think you need another fix to define the altitude constraint. Does ... NOT BEFORE 50 FROM NAVAID HNK 29000 ... not work? If course, it would be better if it would accept 29000A.Lee Hetherington (KBED)

Gentlemen,Many thanks for the help - I'll give your suggestions a try and let you know what happens.