Jump to content
Sign in to follow this  
patrico

New Radar Conact User

Recommended Posts

thanks Ron, I think make makerwys is not installed properly or at all, I am currently investigating or going back to the drawing board . No as far as I remember I only saw a  few airports count down, but I will get back  to you asap with news

Share this post


Link to post
Share on other sites

sorry for the late reply Ron but I have been very busy here, you were right makerwys was not running. I found it and double clicked on it and watched all 5500 airports and runaways count down like you said................many thanks.

 

Can I just use RC for the take only with assistance from the gate to the first waypoint and vectors only for landing..................again many thanks 

Share this post


Link to post
Share on other sites

If you are set up correctly RC should execute makerwys.exe. Be sure you put in the correct path to FSX or FS9 when asked. mine looks like this:

 

h:\program files\microsoft games\flight simulator 9

 

I have the above line entered into a text document (notepad) I created and saved in my documents folder. I created a shortcut to this document on my desktop (similar to the procedure following without the properties stuff). Anytime an application asks for the path to FS I open up this ducument by double clicking on the shortcut. Drag the mouse cursor from the beginning of the line to the end to highlight it. In the notepad or wordpad menu click Edit then Copy.

 

Now go back to the path query with the cursor resting in the empty path box. Now you need two fingers but if you have a typical keyboard you can do this with one hand. Hold down the Ctrl key with one finger and type the V key. For me with a clumsy left hand I use my right hand using my thumb on the Ctrl key and my third finger on the V key. This will paste the copied line into the path window. Then you can OK it to  continue. This avoids any lengthy typing which can also introduce errors.

 

If FS and RC are on the same PC you can just say NO to the WideFS question when asked.

 

If you are on Windows 7 it is best to create a shortcut to start RC so it has full access to your FS folder. Please do the following:

 

Open Windows Explorer or My computer and click the drive that RC is on. Navigate to the rcv4x folder click once on rcv4.exe. In the windows explorer menu click Edit then Copy. Now click on the icon in the system tray and click the icon that takes you to the desktop. Right click on the desktop space (not an icon) and click Paste Shortcut.

 

Now right click on this new shortcut. Click Properties. Click to enable run as admin. (Do not click OK here.) Click Advanced and click again on Run as Admin here so it is checked. Click OK to return to the first window and click apply to save all settings. Click OK  here now to close the properties window. Now when you double click this icon it will start up with full properties to run as user admin and program level admin.

 

Hope this helps.

Share this post


Link to post
Share on other sites

Ron could you please tell me what website you use to get your  flight plans across the pond (daily ones) and do they include a SID and STAR as well as the route

Share this post


Link to post
Share on other sites

flightaware.com has real world filed flightplans for FAA jurisdiction but also includes where one end is in an FAA territory.

 

As an example when you first open it up it comes up in the main area where you can insert a departure and destination area. Putting kjfk and egll lists a number of flights. When you click on the flight number it will come up with a flight information page including aircraft type, airline name, estimated and real duration, scheduled and real times, etc.

 

It is best to select an arrived flight so the full plan is available. For instance I typed in new york choosing the New York area ZNY from the dropdown to EGLL Heathrow. One arrived flight that came up was UAL922 EWR (Newark) to EGLL using a B767-300 (B763) departed at 09:10 EDT and arrived at 21:20 BST. Initial filed cruise was FL350.

 

The route filed was:

MERIT HFD PUT BOS EBONY SUPRY 4600N 05000W 4700N 04000W 4900N 03000W 5200N 02000W MALOT GISTI LAPMO LIFFY UL975 WAL UY53 NUGRA BNN1B

 

 

 

Departing was direct to MERIT intersection and HFD VOR. Transition to NATS crossing waypoints was SUPRY followed by the day's coordinates. NATS exit transition was at MALOT. Notice that two airways in Europe are used, UL975 and UY963 with transition and intersect coordinates listed adjacent to them. BNN1B is the STAR.

 

The track log and graph shows they climbed to a cruise of FL370 (estimated). I don't see it but flightaware used to have a decode option that expanded SID and STAR waypoints.

 

I have FSBuild and for fun I downloaded the weather archive in Active Sky (version 65 I use for FS9). I put the plan into it slightly modified to fit FSB's syntax as:

 

MERIT HFD PUT BOS EBONY SUPRY 4600N05000W 4700N04000W 4900N03000W 5200N02000W MALOT GISTI LAPMO LIFFY UL975 WAL UY53 NUGRA BNN1B

 

processing its FS9 export into AS65's route processing to create a weather snapshot for FSB and rebuilt it. The reported flightaware's duration was 06:42 and FSBuild predicted 07:02. I used a planned TAS of 450 knots so that's not too bad.

 

Here's the exported FS9 plan:

 

[flightplan]
title=KEWR to EGLL
description=KEWR, EGLL
type=IFR
routetype=3
cruising_altitude=37000
departure_id=KEWR, N40* 41.33', W074* 10.07',+000018.00
departure_position=22R
destination_id=EGLL, N51* 28.38', W000* 27.41',+000083.00
departure_name=NEWARK_LIBERTY_INTL
destination_name=LONDON/HEATHROW
waypoint.0=KEWR, A, N40* 41.33', W074* 10.07', +000000.00,
waypoint.1=MERIT, I, N41* 22.55', W073* 08.14', +26000.00,
waypoint.2=HFD, V, N41* 38.27', W072* 32.50', +36000.00,
waypoint.3=PUT, V, N41* 57.19', W071* 50.38', +37000.00,
waypoint.4=BOS, V, N42* 21.26', W070* 59.22', +37000.00,
waypoint.5=EBONY, I, N44* 54.08', W067* 09.23', +37000.00,
waypoint.6=4600N05000W, I, N46* 00.00', W050* 00.00', +37000.00,
waypoint.7=4700N04000W, I, N47* 00.00', W040* 00.00', +37000.00,
waypoint.8=4900N03000W, I, N49* 00.00', W030* 00.00', +37000.00,
waypoint.9=5200N02000W, I, N52* 00.00', W020* 00.00', +37000.00,
waypoint.10=MALOT, I, N53* 00.00', W015* 00.00', +37000.00,
waypoint.11=GISTI, I, N53* 00.00', W014* 00.00', +37000.00,
waypoint.12=LAPMO, I, N53* 24.11', W005* 56.44', +37000.00,
waypoint.13=LIFFY, I, N53* 28.48', W005* 30.00', +37000.00, UL975
waypoint.14=GINIS, I, N53* 27.38', W004* 51.29', +37000.00, UL975
waypoint.15=NATKO, I, N53* 27.11', W004* 38.07', +37000.00, UL975
waypoint.16=LYNAS, I, N53* 26.33', W004* 19.59', +37000.00, UL975
waypoint.17=ROLEX, I, N53* 25.41', W003* 58.04', +37000.00, UL975
waypoint.18=MALUD, I, N53* 24.47', W003* 36.29', +37000.00, UL975
waypoint.19=WAL, V, N53* 23.30', W003* 08.04', +37000.00, UY53
waypoint.20=MOGTA, I, N53* 10.08', W002* 38.09', +37000.00, UY53
waypoint.21=NANTI, I, N53* 08.15', W002* 34.00', +37000.00, UY53
waypoint.22=NUGRA, I, N53* 01.45', W002* 18.14', +36000.00,
waypoint.23=TOBID, I, N52* 13.00', W001* 27.59', +20000.00,
waypoint.24=SOPIT, I, N51* 57.29', W001* 06.25', +15000.00,
waypoint.25=WCO, N, N51* 51.10', W000* 57.44', +15000.00,
waypoint.26=BNN, V, N51* 43.34', W000* 32.59', +07000.00,
waypoint.27=EGLL, A, N51* 28.38', W000* 27.41', +000000.00,
 

 

and in FSX format:

 

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

<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>KEWR to EGLL</Title>
        <FPType>IFR</FPType>
        <RouteType>HighAlt</RouteType>
        <CruisingAlt>37000</CruisingAlt>
        <DepartureID>KEWR</DepartureID>
        <DepartureLLA>N40° 41' 33.00" , W74° 10' 07.00",</DepartureLLA>
        <DestinationID>EGLL</DestinationID>
        <DestinationLLA>N51° 28' 38.00" , W00° 27' 41.00",</DestinationLLA>
        <Descr>KEWR, EGLL</Descr>
        <DeparturePosition>22R</DeparturePosition>
        <DepartureName>NEWARK_LIBERTY_INTL</DepartureName>
        <DestinationName>LONDON/HEATHROW</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>60905</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="KEWR">
             <ATCWaypointType>Airport</ATCWaypointType>
             <WorldPosition>N40° 41' 33.00",W74° 10' 07.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>KEWR</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MERIT">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N41° 22' 55.00",W73° 08' 14.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>MERIT</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="HFD">
             <ATCWaypointType>VOR</ATCWaypointType>
             <WorldPosition>N41° 38' 27.00",W72° 32' 50.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>HFD</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="PUT">
             <ATCWaypointType>VOR</ATCWaypointType>
             <WorldPosition>N41° 57' 19.00",W71° 50' 38.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>PUT</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="BOS">
             <ATCWaypointType>VOR</ATCWaypointType>
             <WorldPosition>N42° 21' 26.00",W70° 59' 22.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>BOS</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="EBONY">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N44° 54' 08.00",W67° 09' 23.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>EBONY</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="4600N05000W">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N46° 00' 00.00",W50° 00' 00.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>4600N05000W</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="4700N04000W">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N47° 00' 00.00",W40° 00' 00.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>4700N04000W</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="4900N03000W">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N49° 00' 00.00",W30° 00' 00.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>4900N03000W</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="5200N02000W">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N52° 00' 00.00",W20° 00' 00.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>5200N02000W</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MALOT">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N53° 00' 00.00",W15° 00' 00.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>MALOT</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="GISTI">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N53° 00' 00.00",W14° 00' 00.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>GISTI</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="LAPMO">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N53° 24' 11.00",W05° 56' 44.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>LAPMO</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="LIFFY">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N53° 28' 48.00",W05° 30' 00.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>LIFFY</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="GINIS">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N53° 27' 38.00",W04° 51' 29.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>GINIS</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="NATKO">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N53° 27' 11.00",W04° 38' 07.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>NATKO</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="LYNAS">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N53° 26' 33.00",W04° 19' 59.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>LYNAS</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ROLEX">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N53° 25' 41.00",W03° 58' 04.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>ROLEX</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MALUD">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N53° 24' 47.00",W03° 36' 29.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>MALUD</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="WAL">
             <ATCWaypointType>VOR</ATCWaypointType>
             <WorldPosition>N53° 23' 30.00",W03° 08' 04.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>WAL</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MOGTA">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N53° 10' 08.00",W02° 38' 09.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>MOGTA</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="NANTI">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N53° 08' 15.00",W02° 34' 00.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>NANTI</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="NUGRA">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N53° 01' 45.00",W02° 18' 14.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>NUGRA</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="TOBID">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N52° 13' 00.00",W01° 27' 59.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>TOBID</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="SOPIT">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N51° 57' 29.00",W01° 06' 25.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>SOPIT</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="WCO">
             <ATCWaypointType>NDB</ATCWaypointType>
             <WorldPosition>N51° 51' 10.00",W00° 57' 44.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>WCO</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="BNN">
             <ATCWaypointType>VOR</ATCWaypointType>
             <WorldPosition>N51° 43' 34.00",W00° 32' 59.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>BNN</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="EGLL">
             <ATCWaypointType>Airport</ATCWaypointType>
             <WorldPosition>N51° 28' 38.00",W00° 27' 41.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>EGLL</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>
 

 

I put the FSBuild Navlog up for you just to see. I did not include estimated taxi and alternate extra fuel in the plan. You'll find it here:

 

https://www.dropbox.com/s/o0kppda24igq9si/KEWR-EGLL%20140923%201400Z%20%20UAL922.pdf?dl=0

 

as a pdf file.

 

I do not know about putting coordinates into the FS planner.  Some of the waypoints may not be in the fsx planner for you to enter unless you update the waypoints in FSX. Look for threads started by ap1 where that was covered with a freeware intersection and navaid update file for the current AIRAC so you can get these current named waypoints and navaids into FSX or FS9 to show up in its planner.

 

Reply here and I'll give you the information.

 

 

 

I just thought I'd go through the whole process so you could see how I set up a flight

Share this post


Link to post
Share on other sites

flightaware.com has real world filed flightplans for FAA jurisdiction but also includes where one end is in an FAA territory.

 

As an example when you first open it up it comes up in the main area where you can insert a departure and destination area. Putting kjfk and egll lists a number of flights. When you click on the flight number it will come up with a flight information page including aircraft type, airline name, estimated and real duration, scheduled and real times, etc.

 

It is best to select an arrived flight so the full plan is available. For instance I typed in new york choosing the New York area ZNY from the dropdown to EGLL Heathrow. One arrived flight that came up was UAL922 EWR (Newark) to EGLL using a B767-300 (B763) departed at 09:10 EDT and arrived at 21:20 BST. Initial filed cruise was FL350.

 

The route filed was:

MERIT HFD PUT BOS EBONY SUPRY 4600N 05000W 4700N 04000W 4900N 03000W 5200N 02000W MALOT GISTI LAPMO LIFFY UL975 WAL UY53 NUGRA BNN1B

 

 

 

Departing was direct to MERIT intersection and HFD VOR. Transition to NATS crossing waypoints was SUPRY followed by the day's coordinates. NATS exit transition was at MALOT. Notice that two airways in Europe are used, UL975 and UY963 with transition and intersect coordinates listed adjacent to them. BNN1B is the STAR.

 

The track log and graph shows they climbed to a cruise of FL370 (estimated). I don't see it but flightaware used to have a decode option that expanded SID and STAR waypoints.

 

I have FSBuild and for fun I downloaded the weather archive in Active Sky (version 65 I use for FS9). I put the plan into it slightly modified to fit FSB's syntax as:

 

MERIT HFD PUT BOS EBONY SUPRY 4600N05000W 4700N04000W 4900N03000W 5200N02000W MALOT GISTI LAPMO LIFFY UL975 WAL UY53 NUGRA BNN1B

 

processing its FS9 export into AS65's route processing to create a weather snapshot for FSB and rebuilt it. The reported flightaware's duration was 06:42 and FSBuild predicted 07:02. I used a planned TAS of 450 knots so that's not too bad.

 

Here's the exported FS9 plan:

 

[flightplan]

title=KEWR to EGLL

description=KEWR, EGLL

type=IFR

routetype=3

cruising_altitude=37000

departure_id=KEWR, N40* 41.33', W074* 10.07',+000018.00

departure_position=22R

destination_id=EGLL, N51* 28.38', W000* 27.41',+000083.00

departure_name=NEWARK_LIBERTY_INTL

destination_name=LONDON/HEATHROW

waypoint.0=KEWR, A, N40* 41.33', W074* 10.07', +000000.00,

waypoint.1=MERIT, I, N41* 22.55', W073* 08.14', +26000.00,

waypoint.2=HFD, V, N41* 38.27', W072* 32.50', +36000.00,

waypoint.3=PUT, V, N41* 57.19', W071* 50.38', +37000.00,

waypoint.4=BOS, V, N42* 21.26', W070* 59.22', +37000.00,

waypoint.5=EBONY, I, N44* 54.08', W067* 09.23', +37000.00,

waypoint.6=4600N05000W, I, N46* 00.00', W050* 00.00', +37000.00,

waypoint.7=4700N04000W, I, N47* 00.00', W040* 00.00', +37000.00,

waypoint.8=4900N03000W, I, N49* 00.00', W030* 00.00', +37000.00,

waypoint.9=5200N02000W, I, N52* 00.00', W020* 00.00', +37000.00,

waypoint.10=MALOT, I, N53* 00.00', W015* 00.00', +37000.00,

waypoint.11=GISTI, I, N53* 00.00', W014* 00.00', +37000.00,

waypoint.12=LAPMO, I, N53* 24.11', W005* 56.44', +37000.00,

waypoint.13=LIFFY, I, N53* 28.48', W005* 30.00', +37000.00, UL975

waypoint.14=GINIS, I, N53* 27.38', W004* 51.29', +37000.00, UL975

waypoint.15=NATKO, I, N53* 27.11', W004* 38.07', +37000.00, UL975

waypoint.16=LYNAS, I, N53* 26.33', W004* 19.59', +37000.00, UL975

waypoint.17=ROLEX, I, N53* 25.41', W003* 58.04', +37000.00, UL975

waypoint.18=MALUD, I, N53* 24.47', W003* 36.29', +37000.00, UL975

waypoint.19=WAL, V, N53* 23.30', W003* 08.04', +37000.00, UY53

waypoint.20=MOGTA, I, N53* 10.08', W002* 38.09', +37000.00, UY53

waypoint.21=NANTI, I, N53* 08.15', W002* 34.00', +37000.00, UY53

waypoint.22=NUGRA, I, N53* 01.45', W002* 18.14', +36000.00,

waypoint.23=TOBID, I, N52* 13.00', W001* 27.59', +20000.00,

waypoint.24=SOPIT, I, N51* 57.29', W001* 06.25', +15000.00,

waypoint.25=WCO, N, N51* 51.10', W000* 57.44', +15000.00,

waypoint.26=BNN, V, N51* 43.34', W000* 32.59', +07000.00,

waypoint.27=EGLL, A, N51* 28.38', W000* 27.41', +000000.00,

 

 

and in FSX format:

 

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

 

<SimBase.Document Type="AceXML" version="1,0">

    <Descr>AceXML Document</Descr>

    <FlightPlan.FlightPlan>

        <Title>KEWR to EGLL</Title>

        <FPType>IFR</FPType>

        <RouteType>HighAlt</RouteType>

        <CruisingAlt>37000</CruisingAlt>

        <DepartureID>KEWR</DepartureID>

        <DepartureLLA>N40° 41' 33.00" , W74° 10' 07.00",</DepartureLLA>

        <DestinationID>EGLL</DestinationID>

        <DestinationLLA>N51° 28' 38.00" , W00° 27' 41.00",</DestinationLLA>

        <Descr>KEWR, EGLL</Descr>

        <DeparturePosition>22R</DeparturePosition>

        <DepartureName>NEWARK_LIBERTY_INTL</DepartureName>

        <DestinationName>LONDON/HEATHROW</DestinationName>

        <AppVersion>

            <AppVersionMajor>10</AppVersionMajor>

            <AppVersionBuild>60905</AppVersionBuild>

        </AppVersion>

        <ATCWaypoint id="KEWR">

             <ATCWaypointType>Airport</ATCWaypointType>

             <WorldPosition>N40° 41' 33.00",W74° 10' 07.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>KEWR</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="MERIT">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N41° 22' 55.00",W73° 08' 14.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>MERIT</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="HFD">

             <ATCWaypointType>VOR</ATCWaypointType>

             <WorldPosition>N41° 38' 27.00",W72° 32' 50.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>HFD</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="PUT">

             <ATCWaypointType>VOR</ATCWaypointType>

             <WorldPosition>N41° 57' 19.00",W71° 50' 38.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>PUT</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="BOS">

             <ATCWaypointType>VOR</ATCWaypointType>

             <WorldPosition>N42° 21' 26.00",W70° 59' 22.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>BOS</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="EBONY">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N44° 54' 08.00",W67° 09' 23.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>EBONY</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="4600N05000W">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N46° 00' 00.00",W50° 00' 00.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>4600N05000W</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="4700N04000W">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N47° 00' 00.00",W40° 00' 00.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>4700N04000W</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="4900N03000W">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N49° 00' 00.00",W30° 00' 00.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>4900N03000W</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="5200N02000W">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N52° 00' 00.00",W20° 00' 00.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>5200N02000W</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="MALOT">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N53° 00' 00.00",W15° 00' 00.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>MALOT</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="GISTI">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N53° 00' 00.00",W14° 00' 00.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>GISTI</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="LAPMO">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N53° 24' 11.00",W05° 56' 44.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>LAPMO</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="LIFFY">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N53° 28' 48.00",W05° 30' 00.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>LIFFY</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="GINIS">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N53° 27' 38.00",W04° 51' 29.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>GINIS</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="NATKO">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N53° 27' 11.00",W04° 38' 07.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>NATKO</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="LYNAS">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N53° 26' 33.00",W04° 19' 59.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>LYNAS</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="ROLEX">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N53° 25' 41.00",W03° 58' 04.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>ROLEX</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="MALUD">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N53° 24' 47.00",W03° 36' 29.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>MALUD</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="WAL">

             <ATCWaypointType>VOR</ATCWaypointType>

             <WorldPosition>N53° 23' 30.00",W03° 08' 04.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>WAL</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="MOGTA">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N53° 10' 08.00",W02° 38' 09.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>MOGTA</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="NANTI">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N53° 08' 15.00",W02° 34' 00.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>NANTI</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="NUGRA">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N53° 01' 45.00",W02° 18' 14.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>NUGRA</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="TOBID">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N52° 13' 00.00",W01° 27' 59.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>TOBID</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="SOPIT">

             <ATCWaypointType>Intersection</ATCWaypointType>

             <WorldPosition>N51° 57' 29.00",W01° 06' 25.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>SOPIT</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="WCO">

             <ATCWaypointType>NDB</ATCWaypointType>

             <WorldPosition>N51° 51' 10.00",W00° 57' 44.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>WCO</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="BNN">

             <ATCWaypointType>VOR</ATCWaypointType>

             <WorldPosition>N51° 43' 34.00",W00° 32' 59.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>BNN</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

        <ATCWaypoint id="EGLL">

             <ATCWaypointType>Airport</ATCWaypointType>

             <WorldPosition>N51° 28' 38.00",W00° 27' 41.00",</WorldPosition>

             <ICAO>

                 <ICAOIdent>EGLL</ICAOIdent>

             </ICAO>

        </ATCWaypoint>

    </FlightPlan.FlightPlan>

</SimBase.Document>

 

 

I put the FSBuild Navlog up for you just to see. I did not include estimated taxi and alternate extra fuel in the plan. You'll find it here:

 

https://www.dropbox.com/s/o0kppda24igq9si/KEWR-EGLL%20140923%201400Z%20%20UAL922.pdf?dl=0

 

as a pdf file.

 

I do not know about putting coordinates into the FS planner.  Some of the waypoints may not be in the fsx planner for you to enter unless you update the waypoints in FSX. Look for threads started by ap1 where that was covered with a freeware intersection and navaid update file for the current AIRAC so you can get these current named waypoints and navaids into FSX or FS9 to show up in its planner.

 

Reply here and I'll give you the information.

 

 

 

I just thought I'd go through the whole process so you could see how I set up a flight

I was just wondering about those nat routes.  Since I have the update for the waypoints in FSX, should those coordinates show in the FSX planner, or will I have to create the waypoints?  Thank you.  Patrico, here's the link for the update of waypoints:  http://www.aero.sors.fr

Share this post


Link to post
Share on other sites

NATS coordinates change daily based on winds aloft. The flights are also one way to reduce chances of opposing aircraft colliding. There are two time windows, one for each way. There are five or six paths used.

 

So the answer to the waypoint update would be that it will not pull in any except the defined named transition points.

 

There are only five or six NATS coordinate pairs in a typical pond crossing path so it is not much to enter as custom waypoints in the FS planner.

 

On the FS map, does it show longitude and latitude as you drag points around? If you insert waypoints, can these be user waypoints defined by coordinates? (ap1: you can add custom user waypoints in Plan-G including by recording the cursor position as I recall.)

Share this post


Link to post
Share on other sites

NATS coordinates change daily based on winds aloft. The flights are also one way to reduce chances of opposing aircraft colliding. There are two time windows, one for each way. There are five or six paths used.

 

So the answer to the waypoint update would be that it will not pull in any except the defined named transition points.

 

There are only five or six NATS coordinate pairs in a typical pond crossing path so it is not much to enter as custom waypoints in the FS planner.

 

On the FS map, does it show longitude and latitude as you drag points around? If you insert waypoints, can these be user waypoints defined by coordinates? (ap1: you can add custom user waypoints in Plan-G including by recording the cursor position as I recall.)

In the FSX planner, you can create custom points by dragging the red line to anywhere you want it.  You then press edit I think and it allows you to enter in corrindates.  Now the corrindates I believe use the min sec format and it looks like from the plan you provided, it's in a different format.  I'll have to take a look at Plan-G and see what I can do.  There are places I found where you can enter corrindates and convert them, but I'm not quite sure what the two formats are.  One site is this:  http://transition.fcc.gov/mb/audio/bickel/DDDMMSS-decimal.html   Thanks for the response.

Share this post


Link to post
Share on other sites

phew! thank you both. I will be very busy over the next few days digesting both, 


FYI  I use  a  free  web site called FS Build for  my flight  planning 

Share this post


Link to post
Share on other sites

The formats I provided are actual .pln file contents that can be pasted into a text document and saved to you FS plan folders in your documents folder.

 

It is the coordinate syntax of the entries for the FS planners that I am not familiar with since I do not use those.


 

 


FYI I use a free web site called FS Build for my flight planning

 

Link? There was a free version 1.4 of FS Build but it is limited as it is well outdated as to compatibility.

 

Here is one in part free on-line planner that searches routes and can export.

 

http://rfinder.asalink.net/free/

Share this post


Link to post
Share on other sites

The formats I provided are actual .pln file contents that can be pasted into a text document and saved to you FS plan folders in your documents folder.

 

It is the coordinate syntax of the entries for the FS planners that I am not familiar with since I do not use those.

 

The FSX planner uses the min/sec format for corrindates.  I tested a flight inputting the corrindates from a flight from PANC to PHNL.  I converted the corrindates from flightaware using the site I posted above, and the planner allowed me to enter the waypoints.  I did all of the waypoints listed in flightaware all the way to the STAR entrance, and it looked like the corrindates I put in were correct.  On the GPS, the waypoints read WP1 etc.  I also tried Plan-G, but couldn't see how to do it.  I may keep trying, but for now, converting the corrdinates and putting them in FSX I think works fine.

Share this post


Link to post
Share on other sites

I am very close to  giving up on RC I know its  a great programme but I  have yet to make a successful flight using it as my ATC after 9 months. I do not want to be forced back into using the FMC and vnav and Lnav alone for my navigation  as its very unrealistic, I do need an ATC preferably button controlled due my speech impairment, My problem is RC still thinks that I am in a different location by a long shot. I have carried out everything Ron has sad. does anyone  know if the T7 is compatible with RC4?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • 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.
×
×
  • Create New...