can some one give me an overview of how they work; especially the STAR procedures. How do I activate them? In my past two flight ATC had been telling me I was "off-course" when I thought it was understood to them that I was flying my STAR. This is since I had already gone past the last way point I had filed (and I thought I was then free to do whatever until I got to the final approach fix).Any help greatly appreciatedThanks, Sam

Look at the flightplan write-up in the RCV4 manual pages 89 - 99 to get an overview.If you are using an FMC guided aircraft, use your flight planner to include the waypoints in your flight plan and then export to both FS9 and your FMC so they have the same DP/STAR waypoints. Your FMC database may not match for the DPs (SIDS) and STARS and even enroute. You can use the runway approach listings selecting them for your FMC as a guide (LSK on the right side of the APP list for the destination airport after LSKing ARR).At some point about 40 miles out RC approach will announce the intended runway and start issuing vectors which mean the STAR no longerr applies. After acking there will be an option to select an IAP meaning you will do your own navigation. If applicable select the IAP for the announced runway so you are in synch with weather and the active that AI are using. You then add it to your FMC as above and follow your FMCs guidance.If you are taking vectors then depart VNAV and LNAV and use HDG and ALT controls on your MCP (as well as speed control) to follow RC instructions. I recommend you still add the chosen runway on your FMC APP page so you can see the final approach on your ND for guidance.Similar procedures apply for LNAV navigation by GPS.For departures know how to do a direct to on your FMC or GPS. When departure releases you to go to a waypoint on your own, it means direct-to from your present position, not return to your original flight path. If using other navigation, home the OBS to give you direct to guidance. If you are going to an intersection the using VORs can be more difficult as you need to follow two VOR indicators or VOR plus DME. You can also use a VOR plus an NDB by following an RMI for the NDB. The heading RC expects you to follow is in the RC window top status line along with the waypoint you are expected to hit withion credit limits.If you are not using pilot auto acknowledge but use your own ack commands, if you see an outstanding ack on the menu RC can miss giving you the next command causing you to miss the waypoint. When you do ack you may still have to go to the missed waypoint, probably in the reverse direction, or use the RC extended menu to get the RC direct-to command option that allow you to pick the next waypoint from a list and remove from the credit list the waypoint you missed.RC expects you to fly your flight plan waypoints and deviate if necessary from waypoints inserted by your FMC or GPS database.In addition if you miss an altitude crossing restriction RC will issue delay vectors until you reach it the assigned altitude if you are not on an IAP or have selected preflight no crossing restrictions on the preflight main RC menu.For US airports I highly suggest downloading the free bundled charts from www.flightaware.com - resources. These will help you choose the correct DP and STAR based on your departure or arrival direction and expected runway use to be included in your flight plan. Many of these points are common until you get close enough to be runway specific. These are current charts that may differ from the database of your FMC or flight planner and even your installed scenery. RCs database is generated from your FS scenery so anytime you add scenery or AFCADs make sure you rebuild the RC Scenery using the command on the main RC page.Without knowing how and what you are flying I can only guess what might be causing your discrepancies.If you are flying an aircraft guided by an FMC search this forum for FMC or FMS for threads regarding synchronization and other issues.For navigation via VOR and NDB go to:http://www.stoenworks.com/Aviation%20home%20page.htmlwhere you will find a number of how-to articles for VFR and IFR navigation, plus some interesting fun stories.And most important, fly the tutorials in the RC manual at first with appropriate default aircraft to keep navigation control simple and you'll also see in the manual a lot of additional information.

That explains a lot ...I have another follow up quesiton and this may sound amateurish but as many say best way to learn is to try it out while reading lol.Anyway, I was doing a flight from Istanbul to Karachi. On approach to khi, I was told to descend additional 5000 feet in 30 meters.According to my FSC (FlightSim Commander), I was hitting my mark very close. The RC ATC then gave me delay vector away from the planned STAR approach added on FSC flightplanner. I was flying for abt 40 mins (no word from the ATC) at my assigned altitude until I realized this is called a delay vector lol. At this point I requested to fly directly to my next waypoint on my planned route.1) My question here would be after given a delay vector, is asking for fly direct to next waypoint the best way to recover to flightplan ?2) Second question here was the ATC kept asking me to descend to new assigned altitude when I was already at assigned altitude. I kept pressing B to make sure my altimeter was correct.How reliable is "B" button?I finally did altimeter revisions manually.Which bring me to a follow-up third question.3) I am planning to do my next flight to Beijing from khi. I understand chinese airspace follow different technique to do altitude reading. I believe there is a chart for that. Does RC simulate that difference as well ? If so, do you guys know where I could find that conversion chart?I had a third question but I think the above post helped in answering.The fourth question was abt how to fly on STAR approach. When I got to my next waypoint, the RC ATC gave me vector heading for approach again away from STAR. Btw I think based on STAR chart I would have been bit high and close to rwy to make clear approach. I guess hypothetically if I wanted to stick on STAR route I would have requested for IAP then.

Edited February 21, 201214 yr by biloo

Answers within your quote in red:

That explains a lot ...I have another follow up quesiton and this may sound amateurish but as many say best way to learn is to try it out while reading lol.Anyway, I was doing a flight from Istanbul to Karachi. On approach to khi, I was told to descend additional 5000 feet in 30 meters (miles?).According to my FSC (FlightSim Commander), I was hitting my mark very close. The RC ATC then gave me delay vector away from the planned STAR approach added on FSC flightplanner. I was flying for abt 40 mins (no word from the ATC) at my assigned altitude until I realized this is called a delay vector lol. At this point I requested to fly directly to my next waypoint on my planned route.RC will vector you around forever if you missed a crossing restriction altitude. If you miss a checkpoint it will vector you back to it. In this case you can use direct next checkpoint a checkpoint from the pop-up list to go to from your PRESENT POSITION direct to that checkpoint. If you look at the RC window it will show the checkpoint it expects you to cross and a heading to it. If you are in the departure or approach phase you must come within two nm of it and if on center you must be within five miles of it for it to be credited. In the RC options there is a check box called checkpoint ding that will chime every time you get a waypoint credit. Be aware that if you do not respond (if you have the comms) with an acknowledgment RC will "stall" and not see you cross a waypoint or meet a crossing restriction.The crossing restriction occurs about 40 nm from destination and depending on your approach direction will be either 11,000 feet (or FL110) or 12,000 feet (or FL120).There is another reason for delay vectors. If you chose the RC option to enable holding and you have a VOR within three miles of the airport you have the option of using a holding pattern or accepting delay vectors. The are randomly issued if you have enabled this feature. Get the RC 43 updated manual from http://www.jdtllc.com/v4/rcv43.pdf and look at the tutorials and about holds.1) My question here would be after given a delay vector, is asking for fly direct to next waypoint the best way to recover to flightplan ?You must fly directly from your present position to a selected waypoint if you choose that option. You do not go back to your original path. See previous note above.2) Second question here was the ATC kept asking me to descend to new assigned altitude when I was already at assigned altitude. I kept pressing B to make sure my altimeter was correct.The 'B' only works where the transition altitude is 18,000 feet which is not the case outside of FAA US areas. That is hard coded in FS. You can see the transition altitude in the controller page of RC. When RC gives an altitude in feet, not flight level, you use the local pressure as noted by the RC controller. If RC gives an altitude in flight level use the standard pressure of 29.92 in. or 1013 mb. If this is not followed RC will not see you at the correct altitude.How reliable is "B" button?I finally did altimeter revisions manually.manually is correct. See previous answer.Which bring me to a follow-up third question.3) I am planning to do my next flight to Beijing from khi. I understand chinese airspace follow different technique to do altitude reading. I believe there is a chart for that. Does RC simulate that difference as well ? If so, do you guys know where I could find that conversion chart?RC4 does not issue altitude in meters. RC4 is based on ICAO rules at the time and feet is standard. I use this site for on-line conversions:http://www.onlinecon...ngth_common.htmHave this site set up and ready to go with the desired conversions if you need it and alt-tab to it if needed. Some advanced aircraft panels may offer dual feet/meters readings. However RC does feet only.In the various flight sim libraries there are utilities provided to do this calculation.I had a third question but I think the above post helped in answering.The fourth question was abt how to fly on STAR approach. When I got to my next waypoint, the RC ATC gave me vector heading for approach again away from STAR. Btw I think based on STAR chart I would have been bit high and close to rwy to make clear approach. I guess hypothetically if I wanted to stick on STAR route I would have requested for IAP then.IAP is good for the last 35 miles of your approach after you accept the assdigned runway and request it. The assigned runway issued by RC is chosen first by ai patterns if present and then by winds and runway length and facilities. Up to that point RC needs to see the STAR waypoints in your plan sent to it and used by your aircraft.Here's a document I wrote about that:

thANKS Ron, I am going to try it out :)It makes sense to me.....