Hi everybodyI've been using FSBuild to generate flightplans, including SIDs (not STARs; those are entered when I find the landing rwy) so RC4 can follow my SID. I thought I'd change my habits and use FSBuild to generate the flightplan but without the SID, and enter the SID directly from the FMC when I find out my departure rwy (most of the time I could guess which was the active, but occasionally I'll get it wrong). The problem now is that RC4 won't recognise my SID and it gives me plenty of grief on takeoff. Is there anyway that I could load the FSBuild flightplan into the FMC, add the SID and then export the modified flightplan in FS format so RC4 can read it? This refers to the 737/747/MD-11 and J41.Cheers, Chris Dalgarno

You can save the route from the FMC after you add the SID, but only in .rte format, so you would still need to use FSbuild to then convert it to FS format. I don't know of any other way with the programs you're using. Actually it doesn't matter which programs really since they will still need to be converted to FS format for other programs that read them, like RC4, Active Sky etc...When I used RC4, I would make various scenerios and rename them in the Flightplans folder to more easily know which I wanted to load.

FWIW:In FSBuild there is an option to build/export from an edited route grid table. It is not sticky between FSBuild sessions. Insert your expected SID and STAR, delete the non-common runway waypoints, and rebuild exporting to FS for RC, etc. Then delete all but the transition points for exporting into the FMC.Now this assumes FSBuild has been kept up-to-date with the free AIRACS from the FSBuild website and your FMC database is kept up to date. This will keep RC in sync with your FMC route.In RC you can elect to fly your filed departure and it will lat you do your own nav. If in the RC your first waypoint is within 30 nm you will be expected to navigate on your own. If you you open the Controller page you'll notice in this instance that ALT Restrictions is selected. If the first RC waypoint is outside No Dep Proc will be selected meaning vectors. Set this to one of the first two Alt types and you can use the FMC to navigate the first thirty miles on your own without vectors. In many cases that sets up a runway independent no vector waypoint list for RC departure.Use a similar procedure for arrival including in the RC plan common waypoints up to forty nm from destination. When approach contacts you request an IAP for the runway it suggests and your FMC can then be used for the approach without RC interference.I can't give details but while still far from release RC5 has a much better way of handling FMC guided departures and approaches.

Thanks Ron and Dan, I dug a little deeper into RC4 last night and discovered the 30 mile 'secret' from the departure point and got everything all tickety-boo. Kind of embarrassed, I've had RC4 for around 3 years now, use it 99% of the time and am only just discovering the enormous amount of 'stuff' that it can do. Never even played with NOTAMS before, although I'm not going to let the 1st Officer take the yoke just yet... :)Cheers, Chris Dalgarno

/I'm not going to let the 1st Officer take the yoke just yet... :)Cheers, Chris Dalgarno

He can