I have been flying some regional routes and the issue I keep running into is RC4 will only give me a couple way points and then have the destination airport as the next way point. An example of this was I was flying from KMEM-KDFW and I got 3 way points or something and then while still 300+ miles out I saw DFW as my next way point. 

 

I then got ATC messages telling me I am off course when I am not but because RC4 is showing the destination airport as the next way point then obviously to it I am off course. 

 

Is there any fix for this or does RC4 only work with flights that are much longer? I have not had this issue on longer flights just the shorter ones like this. 

 

I don't think RC4 has anything to do with this but is there anyway to have a airport use multiple runways for landing simultaneously? 

 

PFPX gives the following route.

 

ELVIS1 WONEE DCT LIT WILBR3

 

That's the ELVIS1 SID and the WILBR3 STAR. If you include those waypoints in the plan you load into RC4 it may work better. Some of the SIDs and STARs in the US can be quite long. If you're getting the off course warning it suggests the next waypoint (or airport) is at least 100 miles away.

 

There's no fix as such. You just need to take the SID and STAR into account with your plan.

 

Regarding you final point that would be controlled by how the AFCAD is designed for an airport. Nothing to do with RC4.

The easiest answer first:

 

FS9 and FSX will use for ai simultaneous runways if they are parallel (with 7.5 degrees heading difference). Where separation exceeds this and you still want simultaneous runways there is a technique called "crosswind runways" where you create a number of runways of narrow width and short length in a star patern and then move the "star" way off into the FS boonies. RC will not see these runways (excluded by makerwys.exe in the scenery rebuild) but they do show up in the runway menus for FS ATC. More on that from the tutorial on this ADE support site:

 

http://www.scruffyduck.org.uk/filemanager/navega.php?PHPSESSID=7cf31e470df6a5ee4991168d97d6cf8e&dir=.%2FTutorials%2FAirport%20Design

 

As to your question:

 

RC can use a flight plan of maybe at just 80 miles or more. There needs to be as I recall at least one VOR outside of the immediate airport traffic area.

 

I created using FSbuild 2.4 a KMEM to KDFW plan flying at 38,000 feet (FL380).  It was just over 400 nm. Here is a navlog quickie (I did not specify holding or taxi allowances.):

 

KMEM-KDFW Navlog.pdf

 

Note that the AWY column stands for airway/SID/STAR labels.

 

Here is the FSX .pln you can copy/paste into a text editor and save in the appropriate folder:

 

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>KMEM to KDFW</Title>
        <FPType>IFR</FPType>
        <RouteType>HighAlt</RouteType>
        <CruisingAlt>38000</CruisingAlt>
        <DepartureID>KMEM</DepartureID>
        <DepartureLLA>N35° 02' 32.00" , W89° 58' 36.00",</DepartureLLA>
        <DestinationID>KDFW</DestinationID>
        <DestinationLLA>N32° 53' 48.00" , W97° 02' 16.00",</DestinationLLA>
        <Descr>KMEM, KDFW</Descr>
        <DeparturePosition>18L</DeparturePosition>
        <DepartureName>MEMPHIS_INTL</DepartureName>
        <DestinationName>DALLAS/FORT_WORTH_INTL</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>60905</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="KMEM">
             <ATCWaypointType>Airport</ATCWaypointType>
             <WorldPosition>N35° 02' 32.00",W89° 58' 36.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>KMEM</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="CHETO">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N34° 56' 30.00",W90° 00' 44.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>CHETO</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MUDHO">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N34° 56' 29.00",W90° 06' 25.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>MUDHO</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="NIXOE">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N34° 56' 01.00",W90° 13' 32.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>NIXOE</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="CHLDR">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N34° 53' 36.00",W90° 48' 04.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>CHLDR</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ANSWA">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N34° 44' 27.00",W91° 46' 32.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>ANSWA</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="EDWAH">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N34° 11' 56.00",W92° 16' 14.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>EDWAH</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MATIE">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N34° 05' 41.00",W92° 33' 02.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>MATIE</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="WASKO">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N34° 03' 36.00",W92° 38' 38.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>WASKO</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="TXK">
             <ATCWaypointType>VOR</ATCWaypointType>
             <WorldPosition>N33° 30' 49.00",W94° 04' 23.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>TXK</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="GLOVE">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N33° 52' 18.00",W95° 06' 15.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>GLOVE</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ROBEY">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N33° 42' 01.00",W95° 41' 20.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>ROBEY</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="BYP">
             <ATCWaypointType>VOR</ATCWaypointType>
             <WorldPosition>N33° 32' 14.00",W96° 14' 02.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>BYP</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="KARLA">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N33° 23' 57.00",W96° 23' 56.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>KARLA</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="COVIE">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N33° 17' 34.00",W96° 31' 31.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>COVIE</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="LEMYN">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N33° 11' 53.00",W96° 38' 15.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>LEMYN</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="KDFW">
             <ATCWaypointType>Airport</ATCWaypointType>
             <WorldPosition>N32° 53' 48.00",W97° 02' 16.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>KDFW</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>
 

 

or for FS9:

 

[flightplan]
title=KMEM to KDFW
description=KMEM, KDFW
type=IFR
routetype=3
cruising_altitude=38000
departure_id=KMEM, N35* 02.32', W089* 58.36',+000341.00
departure_position=18L
destination_id=KDFW, N32* 53.48', W097* 02.16',+000607.00
departure_name=MEMPHIS_INTL
destination_name=DALLAS/FORT_WORTH_INTL
waypoint.0=KMEM, A, N35* 02.32', W089* 58.36', +000000.00,
waypoint.1=CHETO, I, N34* 56.30', W090* 00.44', +03000.00,
waypoint.2=MUDHO, I, N34* 56.29', W090* 06.25', +05000.00,
waypoint.3=NIXOE, I, N34* 56.01', W090* 13.32', +07000.00,
waypoint.4=CHLDR, I, N34* 53.36', W090* 48.04', +19000.00,
waypoint.5=ANSWA, I, N34* 44.27', W091* 46.32', +38000.00,
waypoint.6=EDWAH, I, N34* 11.56', W092* 16.14', +38000.00, Q34
waypoint.7=MATIE, I, N34* 05.41', W092* 33.02', +38000.00, Q34
waypoint.8=WASKO, I, N34* 03.36', W092* 38.38', +38000.00, Q34
waypoint.9=TXK, V, N33* 30.49', W094* 04.23', +38000.00,
waypoint.10=GLOVE, I, N33* 52.18', W095* 06.15', +36000.00,
waypoint.11=ROBEY, I, N33* 42.01', W095* 41.20', +25000.00,
waypoint.12=BYP, V, N33* 32.14', W096* 14.02', +15000.00,
waypoint.13=KARLA, I, N33* 23.57', W096* 23.56', +11000.00,
waypoint.14=COVIE, I, N33* 17.34', W096* 31.31', +10000.00,
waypoint.15=LEMYN, I, N33* 11.53', W096* 38.15', +10000.00,
waypoint.16=KDFW, A, N32* 53.48', W097* 02.16', +000000.00,
 

 

You can try these.

 

I have used much shorter plans without issue some as short as 120 nm or less for tests without issue. One such plan is:

 

[flightplan]
title=KMSP to KDLH
description=KMSP, KDLH
type=IFR
routetype=3
cruising_altitude=15000
departure_id=KMSP, N44* 52.55', W093* 13.18',+000841.00
departure_position=4
destination_id=KDLH, N46* 50.31', W092* 11.37',+001428.00
departure_name=MINNEAPOLIS-ST_PAUL_INTL
destination_name=DULUTH_INTL
waypoint.0=KMSP, A, N44* 52.55', W093* 13.18', +000000.00,
waypoint.1=GEP, V, N45* 08.44', W093* 22.23', +09000.00,
waypoint.2=RZN, V, N45* 49.13', W092* 22.28', +15000.00,
waypoint.3=KDLH, A, N46* 50.31', W092* 11.37', +01428.00,
 

in FS9 format. This has two VORs in it.

 

Try one of the flightplans suitable to your sim.

 

You can paste in a reply here a .pln file that was failing so we can look at it, or at least provide the waypoints.

 

 

 

 

ELVIS1 WONEE DCT LIT WILBR3

 

That's the ELVIS1 SID and the WILBR3 STAR. If you include those waypoints in the plan you load into RC4 it may work better. Some of the SIDs and STARs in the US can be quite long. If you're getting the off course warning it suggests the next waypoint (or airport) is at least 100 miles away.

 

I will try it with including a extra VOR and see what that does. Thank you again for the help. 

 

I see thank you very much for the info. I didn't think I could edit the plans in RC4 but now I realize I can click on that box haha.

 

 

FS9 and FSX will use for ai simultaneous runways if they are parallel (with 7.5 degrees heading difference). Where separation exceeds this and you still want simultaneous runways there is a technique called "crosswind runways" where you create a number of runways of narrow width and short length in a star patern and then move the "star" way off into the FS boonies. RC will not see these runways (excluded by makerwys.exe in the scenery rebuild) but they do show up in the runway menus for FS ATC. More on that from the tutorial on this ADE support site:

 

Interesting because I always thought it was so cool seeing other planes take off and land while I was taxiing at DFW I started to wonder if perhaps that should be happening at other airports. Thank you for the info.