Hi All Here's what I do: 1. Create FP in FSBuild, without SID or STAR2. Export FP to FSX and PMDG3. Start FSX, LOAD AP and start gate.4. Start RC and load FP, input start gate into RC.5. Load FP in FMC6. Contact CLR and ground for departure runway.7. Fly route8. Hopefully Land OK!! Question 1. How do you get the start runway and SID into RC?2. How do you get destination STAR and runway into RC? Is this the correct procedure? regards

RC reads the flight plan you loaded into it, so you need any procedure you want it to use to be actually on that flight plan (you can tell this by the fact it reads out 'by the published departure procedure', rather than saying a specific SID, since it is fluffing it a bit and does not really handle SIDs and STARs in the exact way it is done in the real world, which is fair enough, as that would be a pretty massive undertaking, although we may see it in newer versions). There is a way around that though, you can reduce the nagging settings in RC a fair bit and that way it gives you enough leeway to fly a SID or STAR anyway. The start runway can be changed right there in RC, when you get your taxi clearance, if you don't get the runway you want, request another, you will see a radio option for that. Al

have you read the flight planning section in the manual? flight planning, with departure procedures and stars are discussed, step by step, using two different flight planners as examples. jd

Thanks guys, I understand how SID and STAR work as part of the Flightplan. I also understand that you can change the departure and arrival runway.What I'm missing is that your FP includes the SID and STAR that you think you might get; not knowing the weather situation at this point. I use FSBuild.So, I exported a 'complete' flightplan to FSX and PMDG. I 'fire up' FSX go to the start airport and start gate. Check the 'controller info' and then fire up Radar contact. I get the weather and get a different departure runway to the 'filed' flight plan. I use real weather btw. So I change to the departure runway as given by ATIS. So me and the AI are all going the same way. Now, here is where I get lost. I have the correct runway as per ATIS but my 'Filed' flightplan is not the same. I can change the FMS to reflect the new runway and SID, again that's not the problem. So far FMS, ATIS and AI aircraft are all the same. The only exception is the flightplan that was loaded into Radar contact is not. Therefore the 'filed' SID is now not the same as the actual SID. I hope you understand what I'm saying and sorry for being a 'pain' Thanks for your understanding

When using runway specific SIDs and STARs include the common waypoints to all runways into the flightplan. RC for departure monitors your progress when you have selected that you will use a DP or waypoints are within 30 nm in which case that indicates a DP automatically. For arrival you do nearly the same procedure. Shortly after 40 nm out approach will contact you with the assigned runway. Ack your first vector but then request an IAP to that runway or one of your choice and RC will no longer monitor you until you are on final when it switches you to tower. It is important that your FMC terminal procedure database waypoints be in sync with your flight planner database. In the case of FSBuild 2.4 (a free upgrade from 2.3) that is easily accomplished with a Navigraph subscription that supports your FMC terminal procedure database. (FSB 2.4 includes a cycle 1013 database.) Remember that the subscription for a Navigraph period allows you to download as many formats needed at no additional cost. Here's my tip sheet for using FSB with RC. Sections 6 and 11 deal with your question: 1. Include this line in FSbuild.cfg:NAVCHKDUPDIST=100This decreases the chance of using the wrong duplicate named local (to the airport) waypiont from a nearby airport. Local waypoint names are not exclusive. It decreases the database search when it is named in the route to within a 100 nm radius of your airport. You will find these in terminal procedures such as "D" number something within a SID or STAR to define a merge or turning point.2. When doing a Auto Generate (Route) be sure the SR (Stored Route) button next to it is "up" that is not highlighted. Auto Generate will use a stored route if found by default and most are out of date with old waypoints and terminal procedures. Having Stored Routes off forces it to search a path with fresh data. (Now off by default in version 2.4.)**REVISED 6/16/11** 3. FS Build database updates will be exclusively released through navigraph.com. It should be part of the FMC data line. For those not familiar with Navigraph each subscription term (cycle) includes multiple format downloads at no additional cost. This is very convenient for aligning FMC/navigation equipment databases with the flightplanner so among other things ATC data and your nav equipment data should match as you send a plan to ATC and then load it including terminal procedures into your FMC. The 2.4 upgrade includes the thirteenth cycle of 2010. The FSB upgrade is free to 2.x version users and is available via your order history on simmarket.com.4. Where an airport uses specific runways for different terminal procedures select the runway using an estimate based on weather and if the runway fits your aircraft requirements before doing the Auto Generate. This helps select the correct SID and STAR for the runway and direction of departure and arrival.5. After the Auto Generate and/or first build look at the map created to spot any obvious errors. In the route grid look for any sudden non-sensible changes in direction or extremely long legs not in the correct direction creating a zig-zag in the map. (See item 6 following to correct).6. Be aware there is an option you can set for each session titled "Build Route from Grid Table". It does not stick between sessions. This lets you build from an edited route grid that you may have modified without recreating the table with the same error on your next build/export. For example you might wish to drop an errant waypoint when proofing the map and rebuilding.7. Sometimes the name of a procedure (SID/STAR) does not match the name exactly in a published route and the procedure will not expand into its plan waypoints in the grid table. You can click on the arrow in the SID/STAR box to see what close name is in the FSB database. (Another reason to keep up with AIRACS.) For example KMSP has a current real such as this one:http://flightaware.com/resources/airport/KMSP/DP/WAUKON+THREEbut the FSB database only has UKN2. (It does have UKN3 now with the latest available AIRAC update). If so in the route line just change UKN3 to UKN2 so it will expand. Here's a real route from flightaware.com for KMSP to KMDW:KMSP UKN3 DBQ CVA MOTIF3 KMDWthat can be pasted into the FSB route line. If UKN3 or MOTIF3 does not expand in the route grid to individual way points look in the upper part of FSB in the airport section dropping down the SID or STAR box to get the available version and substitute that label in the route line and rebuild. Note that the SID and STAR dropdowns may follow the chosen runway in certain areas.8. Sometimes it takes a second build to get the map to move and/or magnify. The mouse scroll wheel lets you magnify. Just click on the portion of the map you want to center on and scroll to magnify.9. If you click on a line in the route grid table to highlight it, the waypoint on the map will turn red. This is useful for finding errant waypoints that cause an error in the path. That line can then be edited or deleted and a rebuild accomplished with the build option to build from the route grid table.10. If you are running a weather program such as active sky, first build the route in FSB exporting to FS9 using an anticipated cruise altitude and specify the nearest aircraft profile. In AS get the weather you wish to use. (I always get the weather for the zulu time of the departure in FS since time of day affects weather characteristics). Import the plan into AS via the new route button, check the altitude and choose an appropriate true airspeed in knots (this is your no wind ground speed). Process the route. When it is finished click the button to print a hard copy of all. Use this AS navlog for METAR data at both ends and winds aloft and temperature aloft that can be used for FMC data. (You'll also get your estimated average wind at your specified altitude - handy for FMC data.) Leave AS running. Now go back to FSB and your chosen aircraft profile. Enter the surface temperature from your departure METAR, then estimated total taxi time, hold time, and extra time (sometimes called discretionary fuel). Now turn on again your FS9 export along with any FMC export you might use. Rebuild and you'll see the messages regarding the export completion. On the route selection on the left which brings up your route window select the navlog tab and click the .pdf to save the navlog in a file or the print button to get a hard copy so you can easily reference the estimated fuel and other data. This estimated fuel has now taken into account your winds aloft data - no need to enter it in FSB. Now that you have the hard copy and exported your route, you can first optionally save the plan by selecting flightplan window, then clicking the category tab, then select user category. Now click file, save from the menu bar. The name you might want to embellish. Click Save Route To User Flight Plans. For another session, you can recall this working plan and just build.11. If you are using an aircraft with nav equipment that has its own terminal data procedures in its nav equipment (think FMC) you might wish to use step 6 above to take out the waypoints of the terminal procedures keeping just the transition points and build and export with just them. This easily in most cases lets you select the SID and STAR assigned by ATC on your nav equipment by providing a clean legs list in your nav equipment. If you need ATC to monitor the waypoints of the terminal procedure than just export all. To keep ATC and you nav equipment in sync, you might consider importing the full plan into your nav equipment and not using your nav equipment procedure database.This is kind of long but through experience I've described some tricks I've used watching out for any pitfalls.Be sure to check the FSBuild forum for updates.

many thanks for your time and explanation. Just need time to read and digest all this ;-)