Jump to content

Archived

This topic is now archived and is closed to further replies.

thony79

Info

Recommended Posts

I just have a few questions before I make my purchase..1-Usually when i'm flying a long haul flight I'll cancel my IFR flight with ATC and use speedx4 and when I'm about 400nm to 300nm from my arrival airport I'll request an IFR clearance from ATC.. I'd like to know if I can do the samething with RC 2-Do I always have to open RC b4 lauching fsx or I could launch fsx and listen to ATIS at my starting airport then create the flightplan via fs build and open(load) it in RC while fsx is already launched

Share this post


Link to post
Share on other sites

1. There is an option to pause FS x miles from the destination. Enter 150 miles and you can leave RC/FS unattended but you must hand comms to the autopilot. Don't engage x4 if your plan has large turns as you may not receive credit for passing the waypoint. 2. You must always start FS first and then load the plan into RC and then start that. If you don't include SID waypoints in your plan you can create a generic one (first waypoint is end of SID) so that whatever end of the runway you depart from the route to the first waypoint (end of SID) will not be monitored by RC.


Ray (Cheshire, England).
System: P3D v4.5, Intel i7-8086K o/c to 4.6Ghz, Nvidia GTX 1080 Ti 11Gb, Samsung 970 EVO M.2 SSD, 1Tb Samsung 860 EVO SSD, Asus Prime Z370-A mobo, 32Gb G.Skill DDR4 3000Mhz RAM, Win 10 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke.
Cheadle Hulme Weather

Share this post


Link to post
Share on other sites

Thx for your quick answer Ray but since I started to have a better understanding of SID and STAR's I can't flight without them..I also have another question.. Let's say that my star is RNAV and it can't be found in fsbuild ... is there a way for me to load in my flightplan for RC to know that's the star I'll be using

Share this post


Link to post
Share on other sites

I wasn't suggesting you fly without SIDs and STARs. I suggested you don't include them in the plan loaded into RC. I don't use FSBuild but Ronzie may offer some guidance with that program. I use vRoute which doesn't include SIDs and STARs - just the generic route. But you can load the relevant SID and STAR in your CDU/FMC assuming you fly with one. It may help if you read this post as someone else had a similar question. http://forum.avsim.net/topic/347013-using-vroute/page__view__findpost__p__2092883


Ray (Cheshire, England).
System: P3D v4.5, Intel i7-8086K o/c to 4.6Ghz, Nvidia GTX 1080 Ti 11Gb, Samsung 970 EVO M.2 SSD, 1Tb Samsung 860 EVO SSD, Asus Prime Z370-A mobo, 32Gb G.Skill DDR4 3000Mhz RAM, Win 10 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke.
Cheadle Hulme Weather

Share this post


Link to post
Share on other sites

I understood what you meant and thx again for your help.Let's say that my SID is dorval6 from CYUL and in the sid I need to be vectored...Will RC vectors me to teh right waypoint and also if I have a star that includes vector to final will RC vector me as well..Sorry for asking so many questions

Share this post


Link to post
Share on other sites

I'm not familiar with that SID. Why do you need to be vectored by RC? If the final waypoint of that SID is XXXXX RC will only start monitoring you once you reach XXXXX if that is the first waypoint in the plan you load into RC. Alternatively, determine the winds before you create your plan and include the relevant waypoints in your plan. RC won't vector you but will monitor your progress as you pass all waypoints up to 30 miles from the departure airport. You have to pass within 2 miles of each waypoint up to 30 miles. Regarding STARs it all depends on how far from the arrival airport the STAR ends. If it's inside 40 miles you will be ordered down to either 11,000ft or 12,000ft depending on arrival runway. On contacting APP you can either choose RC vectors (the default option) or IAP. The IAP option allows you to fly your own approach and RC does not interfere with you. If you go with the default RC will vector you and the waypoints in your STAR will be ignored.


Ray (Cheshire, England).
System: P3D v4.5, Intel i7-8086K o/c to 4.6Ghz, Nvidia GTX 1080 Ti 11Gb, Samsung 970 EVO M.2 SSD, 1Tb Samsung 860 EVO SSD, Asus Prime Z370-A mobo, 32Gb G.Skill DDR4 3000Mhz RAM, Win 10 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke.
Cheadle Hulme Weather

Share this post


Link to post
Share on other sites

It sounds like you are talking about runway specific SIDS and STARs. Most of them have waypoints common to all runways. Just put those in the RC flight plan. In a bit I'll show you how to do that in FSBuild. Now if your first SID waypoint is within 30 nm RC will expect you to cross them on your own with no vectors. If it is outside that you'll get vectors to 30 nm lining you up for the first waypoint outside of 30 nm. For arrival RC will vector you starting about 35 nm out after having assigned the runway so if you need vectors you can just let RC do its thing. In FSB you can if terrain permits leave out a runway specific waypoint outside of that 35 nm. (If you want to navigate your own approach, ask for an IAP after RC assigns a runway and you ack that. It might assign a vector first but just ignore that.) Here's a tip sheet I made up for FSBuild on how to build a plan and then remove certain waypoints before exporting to RC or other ATC to accomplish what I describe. Note specifically items 6 (building and exporting from an edited grid table) and 11 (coordinating with terminal procedures in navigation equipment). I hope this helps. ---------------------------- 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 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+THREE but 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 KMDW that 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.------------------------------

Share this post


Link to post
Share on other sites

@Ronzie the dorval6 SID can be use for all the rwy at CYUL airport and the routering part it's written on the chart"Climb rwy heading or as assigned for RAD vector to assigned route and even when I enter it in my fmc right after the SID it's written Vector then the first waypoint of my assigned route... That's what I meant by vector by RC upon takeoff to my assigned route.

Share this post


Link to post
Share on other sites

It sounds like your first waypoint will be more than 30 nm out. RC will give take off instructions with runway heading or dictated heading and your first altitude assignment followed by more vectors. That waypoint should be placed in the plan by your planner. At some point RC will command Resume Own Navigation and which point you will go from your present position direct to that first waypoint. When there you can follow your FMC procedure if it follows those waypoints. FSBuild does not have the DORAL6 departure for CYUL. If you go into the FSBuild folder you'll see a file called SIDS.txt. Search for CYUL and you will see the procedures stored (based on the new format for navigraph data). The only SID that comes up is KIPAX2 probably because that is the only SID with waypoints. I generated a short plan in FSB from CYUL to KBOS. HerE's what turned up: In this plan NAPEE and YUL40 fall within the 30 nm limit and RC will expect you to navigate on your own crossing these and then direct to PLB outside that limit. Note that these waypoints are on J567 on NAPEE is only ten miles from the airport. FSB did not assign a SID as such. (On the KBOS there is no applicable STAR because all of the STAR transition points arriving from the northwest are further out.) I generated a longer plan to KMSP and this was a bit different; Here LEPEN is 38 miles out on J485 and you'll get vectors to line you up with that. On the arrival side: BITLR is 42 nm out and unless you elect otherwise vectors will start about 5 nm after that. RC will probably follow vectors similar to what is shown heading for a base entry to 30L near PRESS, base to just east of FGT followed by an interecept to 30L. I don't know what aircraft you are using but for departure where you do get vectors know how to do a direct to from your present position when RC states resume own navigation. For arrivals when vectors start it is tyime for MCP HDG, SPEED, and ALT control. (I do assign the approach navaid/runway for situational awareness so it shows up in the nav display. If the STAR database matches the plan that can go in too but remember ATC rules.)

@Ronzie the dorval6 SID can be use for all the rwy at CYUL airport and the routering part it's written on the chart"Climb rwy heading or as assigned for RAD vector to assigned route and even when I enter it in my fmc right after the SID it's written Vector then the first waypoint of my assigned route... That's what I meant by vector by RC upon takeoff to my assigned route.

Share this post


Link to post
Share on other sites

thx for the info but in regards to what aircrafts I'm using it's mostly PMDG and LDS and one thing that I hope will not happened with RC it's when I have to start my descent... It happens a lot with fsx ATC that you're being asked to start descent way too late therefore you're too high or too far to intercept the LOC for final appr

Share this post


Link to post
Share on other sites

RC uses the three in one rule to calculate its TOD to the crossing restriction forty miles out from destination. It usually starts you down from cruise a few miles before that shown on the NAV display. That's one reason a pilot's discretion descent is offered on the first descent from cruise. RC uses an averaging system for determining the MSA of an airport averaged in all quadrants. For those valley approaches we suggest using charts and NOTAMS to allow altitude deviation and then from forty nm out requesting the IAP approach which lets you fully conduct the approach up to the intercept on final without RC instruction or monitoring. The averages MSA that RC uses for calculating (with modification) the final intercept altitudecan be changed to match your route, but that is a preflight option. You can do this latter option by taking advantage of your FMC approach data as displayed on the LEGS page after you EXE the change in inserting the STAR and IAP in the FMC database.

Share this post


Link to post
Share on other sites

Hi guys, I seem to have the same (or very close) issue.In my case it's the CYOW2 SID at CYOW. It can be used with all the runways The route is (MSS ENE V167 SCUPP KBOS). Basically my problem is the same as above. The SID is as follows: Lets say i'm departing from RWY 32.Fly heading xxx to YOW then Vectors then MSS. That's what it also says in my FMC and in EFB. I then takeoff fly to YOW then waited and waited for vectors from RC but nothing until I got a warning from RC saying that I was off course (what???). RC THEN vectored me back to MSS. The way it should of happenned:(after YOW) get vectors from ATC to fly direct (or whatever) to MSS then as filed. Instead I got in trouble for not flying my route. I fly in real life so this was unexpected behaviour from ATC. What I did to solve the problem is not use SIDS that have vectors from ATC in them but it would be nice if this could be fixed. Thanks


Chris Verner

 

Home cockpit builder ...well trying anyway

Share this post


Link to post
Share on other sites

I forgot to add that if I try the same flight plan but dont wait for the vectors and go direct to the first waypoint, in this case MSS, RC also tells me that i'm off course and sends me backwards to some heading. To me, this does not make any sense at all. I have never heard any ATC giving instructions to go back (away from the destination) to get back on track. Just as if I would of missed a waypoint when in fact this is not the case. What I do when this happens is shutdown RC completely and complete the flight without ATC. I have no knowledge of how software works but I sure know how ATC works and RC becomes unusable in these situations. Thanks


Chris Verner

 

Home cockpit builder ...well trying anyway

Share this post


Link to post
Share on other sites

FSBuild did not include VOW in the SID so I added it manually. I don't have that chart. RC4 is set up that if a waypoint is within 30 nm of take-off then you are flying your own navigation. Since VOW is 11 nm away you will not get vectors and RC will expect you to cross VOW and then head direct to MSS. The only solution in this case is to drop VOW from the flight plan. Then your first waypoint is MSS 46 nm out. Preflight in RC's controller page you can elect NOTAMS which offers you flexibilty in deviating from those departure vectors so you can follow the FMC if you wish crossing VOW. RC's departure zone is 30 nm out and will adjust its vectors from VOW as your position changes and RC will issue you a resume own navigation which expects you to fly direct to MSS from your present position at just before 30 nm out. Try that.

Share this post


Link to post
Share on other sites

Thanks Ron!Will try this over the weekend.


Chris Verner

 

Home cockpit builder ...well trying anyway

Share this post


Link to post
Share on other sites

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    42%
    $10,670.00 of $25,000.00 Donate Now
×
×
  • Create New...