Would it be possible in future productions for ATC to allow descent at descretion and allow the following of a STAR instead of getting vectored? Also, taxi instructions would be nice.

Read the pinned topic about v5 suspended coding...

 

John

Pilot discretion for delaying descent beyond TOD is already available in the menu in RC4. In some cases you may hear "at your discretion. RC4 calculates the TOD for constant descent based the the three to one rule of thumb to the 12,000 foot or FL120, or 11,000 foot or FL110 dictated by your arrival direction and estimated runway assignment. The TOD is not calculated to the airport altitude. Those crossing restrictions at 40 nm out are not flexible even with the use of NOTAMS.

 

You can navigate your STAR once you have been contacted by approach at 40 nm out, acked the first vector but immediate request an IAP approach to the assigned runway. Where a STAR is runway specific for RC's purposes just include the STAR waypoints common to all runways in the .pln sent to RC. Be sure STAR waypoints in the FMC match the ones in the .pln sent to RC until about 35 nm out when your IAP will be granted. Once you have the IAP granted you can finish the approach using FMC guidance. You will not hear nor be held to vectors or waypoints by RC. The next time you hear from RC will be on final when told to contact tower.

 

Included in the attached document are suggestions for syncing your FMC and plans sent to RC including the FMC terminal procedure databases. I used FSBuild v2.4 as an example.

 

 

 

A recent revision is that Aerosoft now offers AIRAC updates for planners and nav equipment (FMC, etc.) in addition to Navigraph. Consider at least a one time update to sync your planner and nav equipment SID/STAR databases.

 

In RC also investigate the use of NOTAMS that places RC in an advisory capacity.