simon2

I have just started to take a closer look at the sid/stars for LEAL as theres a Spanish Vatsim event on the 20th.The ALT NDB is north of the runway and the ALT VOR is just south of the runway. All the sid radials relate to the ALT VOR, yet the FMC uses the NDB for NAVAID ALT.Is there a way to define in the SID, to use the VOR rather than the NDB, other than creating a FIX for the VOR from the NDB?Simon

I have found a lot of instances when writing sids/stars when the fmc throws up a distance of around 3000+, when intercepting radials. I usually just try to find a work around until the team come up with a fix for this bug.try thisFIX SDG19 COLOCATED SDG 351 19STARSSTAR UVENA3E NAVAID UVENA FIX SDG19 FIX WPT30 FIX WPT31 FIX WPT32 FIX WPT33 HDG 220 INTERCEPT RADIAL 313 FROM NAVAID SDG NAVAID RECIF 3000 RNW 14 RNW 12ENDSTARSSimon

Ron on the PMDG 737 Operators Information Center page theres a revised pack of sids/stars of 6th Sept for 0309. There is also a revision to the 0309 navdata available from Richard Stefan's site. http://www.navdata.at/With these 2 sets of data there wasn't a problem with KMIA on my machine.Simon

I have just finished the LEPA SID/STARS file, you are welcome to download the file from herehttp://homepage.ntlworld.com/simon.butler2...usefulfiles.htmSimon

WolfgangThe NAVAID NB is in the database 6 times. I have found that the FMC doesnt like NB. Even when added as a FIX NB it reports an error. Thats why I have used FIX NB01.Add this FIX and replace the 5 NAVAID NB's in the sid text with FIX NB01 it should then work ok.FIXESFIX NB01 COLOCATED INUW 278 5.5ENDFIXESDont have the charts for here, so dont know how accurate they are.Simon

I have now updated my SID/STARS files for EGCC AND EGKK, I have removed the altitude constraints for waypoints with XXXX or ABOVE AT AND XXXX or BELOW AT, which were causing problems. I have left the waypoints in at these points so that you can manually check the constraints are met.These files can be downloaded from herehttp://homepage.ntlworld.com/simon.butler2...usefulfiles.htmSimon

Nigel I have have just had a very quick look at this SID and written a draft sid to see if it may get you started.FIXESFIX SAM27 COLOCATED SAM 036 27FIX SAM24 COLOCATED SAM 036 24ENDFIXESRNWSRNW 27RRNW 27LRNW 23RNW 09RRNW 09LENDRNWSSIDSSID SAM2F RNW 27R KEEP HDG UNTIL 580 HDG 270 INTERCEPT RADIAL 259 FROM NAVAID LON KEEP HDG UNTIL 7 FROM NAVAID LON HDG 272 UNTIL 12 FROM NAVAID LON HDG 270 UNTIL 13 FROM NAVAID LON HDG 265 UNTIL 15 FROM NAVAID LON HDG 265 INTERCEPT RADIAL 036 FROM NAVAID SAM FIX SAM27 FIX SAM24 6000 NAVAID SAMENDSIDSSTARSENDSTARSNote though there is only one true altitude constraint that can be included correctly at the moment, thats at SAM24 at 6000. The rest are ABOVE AT and are not supported for the time being by the fmc.The LON15 point may be better as a lon lat fix point. Hope this helps get you started.Simon

Hello DaveVNAV will disconnect if only a speed constraint is entered and no altitude constraint.I haven't entered any speed constraints in the sids I have done. I have entered altitude constraints, which seem to be causing problems. The 3000ft constraint on the HON1R/1Y sid from egcc, at HON58 or SANBA-5 (its the same point)is 3000 or above. I have set the constraint at 3000 here as the above feature isnt operational yet. And then later 5000 at SANBA.It should be possible to take off with an initial cleared altitude of say FL100 set in the MCP, select LNAV and VNAV and fly the sid until SANBA at which point VNAV should continue the climb to FL100.Important though dont set speed constraints against the waypoints that dont have alt constraints set.Flap settings will keep the speed down under VNAV and help around the initial turns.Hope this helpsSimon.

Hello RayI'll modify both files over the next couple of days, to sort the altitude constraints, back to work tomorrow:(Simon

I have just completed the EGKK sid/stars, you are welcome to download the file from here if anyone needs it.http://homepage.ntlworld.com/simon.butler2...usefulfiles.htmThe 180deg turns are reasonable but I have not worked out how to write them properly yet.Simon

Thanks for that information Anthony, I knew that I flown the sids before with vnav without a problem but got caught out with the speed constraints yesterday.I am part way through writing the egkk sid/stars now, so will get back to that.Simon

Hello Ray, your right, I'm unable to get vnav to engage on the HONIY dep, after several attempts. But I have flown the HON1R sid again without any problem with the mcp alt set at 5000.thanks Simon

Hello RayI've just flown out of egcc on the HON1R, with no problems, vnav hit the levels spot on. Setting 5000 in the MCP is fine, you could set higher if cleared to that initial altitude. VNAV would just continue the climb after sanba to the initial cleared altitude.Simon

Thanks for the info Ian and Ray, I will add the LISTO sids tonight.Simon

Hello Ian I have done the sid/stars for EGCC with the help of Terry. I have left out the LISTO sids, as they are for non jet aircraft except in times of congestion. It may not be quite as well written as some but it does the job. I am working on EGKK at the moment.You are welcome to download it from here. http://homepage.ntlworld.com/simon.butler2...usefulfiles.htmMy idea was to write a few that were missing at airports the VA I fly for uses,to make life easier on vatsim.Hope this helps Simon