KSAN.xml cycle 0809 for Level-DdepartureBRDR5rwy27 transition**************** below has no name: Also, waypoints 1 and 2 have the same Lat/Lon.Should intercept a PGY radial before going to BROWS?Normal32.610333-116.979083000at(INTC)Intc32.610333-116.979083000at01200Leftrwy 09 transition*****************The first intc goes out 172nm!May have to check them against the actual procedure.

Hi Vaughan,Thanks for bringing this to my attention. I will need to do a little code fixing. It seems the NFD procedures slipped in a code I've not seen used before so I have to account for it now.I think I will also examine the data to see if those codes are used at other airports too. If other airports are affected I'll issue an amended set of procedures shortly.RegardsTerry

Ok,Sounds good to me.For the BORDER5 SID, the rwy27 transition to PGY19is not on a VOR radial.I got out my old modified KSAN.xml to get the lat/lon.Here it (PGY DME 19) is as PGY85.(INTC)Intc32.782203-117.22541418050000at190 96AutoPGY85 **************************************Normal32.763842-117.30775118020000aboveFly-byAuto(INTC)Intc32.610339-116.97908120040000above1120260LeftPGYNormal32.610339-116.97908125060000aboveFly-byAuto

Well, the introduction of the "new" leg codes caused the problem here. Not knowing what to do with the "new" legs my program just went on it merry way and screwed up a few waypoints. Unfortunately the Level-D procedure checking utility I use to check all the procedures did not catch the errors. I'm working to fix my conversion program now.RegardsTerry

Ok,At least you know what caused it.Thanks for the feedback.