I'm thinking about buying RC4 but would like to clarify a few things first.. When you're creating ur flight plan prior to loading it onto RC4 do u create the SID and star at the same time or just select Published dep in RC4 and u select the SID directly in the fmc.. if you've programmed a STAR in the fmc will RC4 still vector you to ur landing rwy. Does RC4 have progressive taxi???Can you use fplans that were created in fsbuild??

RC must be sent all waypoints including those of a SID or STAR from beyond 30 nm from your departure airport to 35 nm from destination. Outside of those departure and arrival ranges if you use any part of an FMC terminal procedure those waypoints must match what you send to RC.If your first waypoint is within 30 nm from departure RC assumes you are flying a published departure procedure and you do your own navigation to the first waypoint outside that range. There are two preflight options to force this in RC.Similarly in flight at about 35 nm from your destination airport you are contacted by approach with an expected runway. After you acknowledge this you have the option to request an IAP which turns off vectoring and you navigate the remainder on your own. RC will not monitor you until you are on the last stages of final where you'll be instructed to contact tower.If you are using runway specific SIDs and STARs you can just include common waypoints for all runways outside of the 30 nm mile departure limit and 35 nm arrival limit, request these options to do your own navigation, and then use your FMC terminal procedures.RC will assign the departure and arrival runways with first priority of observing AI, the using winds and runway features to come up with the best guess if no AI are active at the time runways are chosen.I use plans created with FSBuild version 2.4 which now has available a Navigraph subscription. One subscription fee includes multiple navdata downloads so for the same fee you can update your compatible FMC databases and the FSBuild databases to keep all of your terminal waypoints in sync with the flightplan sent to RC. FSBuild also has a feature that once you enter or generate a route you can choose a build option to build from the generated route grid. This allows you to delete non-common runway procedure waypoints from the grid from your plan sent to your FMC and RC if you choose to navigate parts of departure and arrival telling RC you will do your own navigation.RC does not provide progressive taxi in version 4. It will show you a heading to the assigned departure runway threshold. I use airport diagrams and if complex will taxi in an overhead view.I am pasting below a hint sheet I made for using FSBuild with RC4 or similar ATC apps:----------------------FSB tips: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 12/31/10** 3. Starting soon in 2011 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.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+TWObut 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.----------------Also your free upgrade from FSBuild 2.3 to 2.4 is available from your simmarket.com account order history if you did not catch the e-mail. The released version is 2.4.18. Check the FSB forums.If you click my tag it will take you to the RC web site. Choose documentation and download the RC4 manual which includes tutorials. Pay particular attention to the areas of departure and arrival.

I'm thinking about buying RC4 but would like to clarify a few things first.. When you're creating ur flight plan prior to loading it onto RC4 do u create the SID and star at the same time or just select Published dep in RC4 and u select the SID directly in the fmc.. if you've programmed a STAR in the fmc will RC4 still vector you to ur landing rwy. Does RC4 have progressive taxi???Can you use fplans that were created in fsbuild??

there is a whole section in the manual on flight planning, sids and stars. probably would be best to read that, then if something isn't clear, i'm sure we can answer that question. www.jdtllc.com/v4/rcv43.pdfjd

Thanks for the info guys but in regards to the star... if I don't know the rwy that I'll be landing on bcuz it will be given to me by ATC how can I know what STAR that I have to use...Sorry if it's a lame question but I'm really a newbie therefore just trying to know as much as I can

Most STARS and SIDS are direction oriented but with common waypoints for all runways. Just include the common waypoints in your flight plan sent to RC.For arrival select an IAP for the assigned runway after you ack the assignment, then complete the STAR using your own navigation following charts or navigation from an instrument terminal database of procedures as in a GPS or FMC. For departure select one of the altitude restrictions which will let you navigate your own way to the first waypoint outside of 30 nm hopefully the first common waypoint of a SID.In both cases described RC will not monitor your position within 30 nm of departure and 35 nm of arrival.You can also preflight assign the NOTAMS feature. For departure you'll hear RC ATC state "Let me know when you can procedure on course" and if you then select the On Course that in the you will be expected to go direct from your present position direct to the next filed waypoint (as shown in the status section of the RC window). For arrival as you transition down from center to approach you'll hear RC ATC give a long statement about it is the pilot's responsibility to stay clear of obstacles. That gives you flexibility to depart from vectors. It does not wave your arrival altitude crossing restriction.

Even though I've loaded a star when the flight plan was created but for final approach I have to vectored... will ATC vector me for final

For arrival ATC will insist vectoring you from about 35 miles out and you ack and then request an IAP which will let you choose a runway if needed and then you will be left to navigate on your own. You can also request a different runway if you wish vectors. On an IAP request RC will not monitor you until you are on the last few miles of final at which point you will be told to contact tower. If there is no approach radar at the airport, center will line you up toward the airport so you can follow the published chart getting to the IAF on your own.

the manual covers all of these flight planning questions. www.jdtllc.com/v4/rcv43.pdf jd