You can use FSB with RC and the PMDG FMC for dynamically assigned runways in flight to get the SID and STAR waypoints for runway specific versions. FSBuild has an option in Build Options to Build from the Grid Table. It is necessary however using at least a one time subscription (period or single use) from navigraph.com or the Aerosoft product to get the AIRAC formats to update the FMC and FSBuild 2.4 (up) products so that the terminal procedures in the FMC and FSB are current and synchronized.

 

First you do a full build using a SID and STAR based on departure and arrival direction. Use the expected one based on winds for now. Don't export the full build.

 

Now turn on the Build from Route Grid Option. Delete waypoints not common to all runways as much as possible. For departure these will be the line after the Airport through the last not common waypoint. For arrival the reverse is true after the last common waypoint through the line just before the airport. Now in export options click FSX or FS2004 as needed. Click Build again and the plan for RC will be exported. Cick on export options on FSX or FS 2004 to turn those off. Click on PMDG.

 

Now further edit the grid table to delete the remaining lines between the airport and the airway transition point. Build again to create the FMC route which now includes just the airports, transition points, and non SID/STAR enroute points. These excluded points will be in your FMC data base and when you select them from your DEP or ARR FMC page will be added to the LEGS page. See the FMC manual about how to perform that.

 

We have to do each version because as far as RC SID and STAR waypoints can be part of the enroute phase and must be included in the plan.

 

RC has a several options that may allow some flexibility when there are differences in the terminal procedures. First there is the NOTAMs feature. Then the DP with or without altitude restrictions for navigating on your own the first 30 nm of departure without RC monitoring nor vectors to the first waypoint outside of 30 nm when RC ends the departure phase transitioning to enroute. For arrival there is the IAP option which lets you navigate on your own without RC monitoring after you accept the approach runway assignment and first vector, after which the option becomes available.

 

Here's a tip sheet about FSBuild itself and then about how to use it with RC. It might apply to some other planners that allow the expanded waypoint table editing feature.

 

 

 

While not runway specific DP or STAR here's what thee FSBuild route table looks like.

 

 

 

Note the VIA column which can help you identify waypoints related to the terminal procedures and airways.

 

and the FAA chart (updated to SCHEP5).

 

 

 

Now if your read the DP description and for the case of RC you would drop the MSP waypoint VOR from the plan which is on the airport and too easy to miss in certain cases to get an RC waypoint credit which is a two nm radius around the waypoint for departure and approach within those 30nm and 35 nm limits respectively.

Now in export options click FSX or FS2004 as needed. Click Build again and the plan for RC will be exported. Cick on export options on FSX or FS 2004 to turn those off. Click on PMDG.

 

Actually you can select both at the same time, so you only have to build once. An even better idea, is to go into options, and and select all the formats for all the different addons you have. Then when you do a build by default, a plan will be created for each. This makes certain that the flight plans are in sync no matter which addon aircraft or addon you use. This is especially important with ATC addons or for default ATC. This is the biggest issue I have with PMDG's decision to remove existing SIDS and Stars from Flightplans. In theory the PMDG SIDs and Stars should match, if NAVDATA between FSBUILD and PMDG is up to date, but I've seen some differences. For default FSX that's not an issue for Stars, since ATC will vector you anyway. It does matter for PFE which does use the defined STAR in the FS Flightplan For SIDs it also matters as you can fly a SID if it is defined in the FSX flightplan. I know they say it's not prototypical for SIDs/Stars to be included in the flightplan but as we all know some compromises are necessary in FS!

Is it possible to make an IFR or VFR flight plan using the FSX Flight Planner for an aircraft such as the Pilatus PC 12, Bonanza or any GPS Equiped aircraft without an FMC and then export it to Radar Contact without the use of an additional Flight planner such as FSBuild?

This would allow me to first become familiar with Radar Contact and the ATC system, and then at a later time install a Flight Planner like FSBuild. It would be easier rather then trying to learn RC, FSBuild and ATC all at the same time.

Thanks again

ress

RC will read FSX plans in XML native format no matter what creates it. You may run into difficulties though if you use the procedures in the GPS for SIDs or STARs and those waypoints are not in the plan sent to RC.

Tom:

 

When I was referring to multiple exports I was taking about two different exported plans, one with less waypoints, for the PMDG FMC since the rest are in the terminal procedures database. RC needs most of the full plan to get the waypoints between 30 nm our from the departure airport to about 40 nm out from destination which is the enroute phase within RC.

 

Sure, you can export the same plan simultaneously in multiple formats, but I was talking about a modified plan for each service.

 

As I recall in the PMDG FMC when you inserted the terminal procedure if it spotted the transition point on the LEGS page it knew where to to the insert. If you decided not to use the PMDG database (from the APP page) if you imported a full plan it was not touched. You did have to watch out for discontinuities.

Thanks for your reply Ron as to using Radar Contact with GPS only aircraft and the FSX Flight planner without a third party Flight Planner, I am assuming the answer to my question is a yes.

I am aware of the inability to use SIDS and Stars, however it would be really refreshing to fly an IFR flight in the Pilatus with out being given ATC Ping Pong heading changes and vectors that require carrying an additional in-flight meal service and a second trip to the Lav before final.

Much appreciated.

ress

Thanks for your reply Ron as to using Radar Contact with GPS only aircraft and the FSX Flight planner without a third party Flight Planner, I am assuming the answer to my question is a yes.

I am aware of the inability to use SIDS and Stars, however it would be really refreshing to fly an IFR flight in the Pilatus with out being given ATC Ping Pong heading changes and vectors that require carrying an additional in-flight meal service and a second trip to the Lav before final.

Much appreciated.

ress

 

 

Actually default ATC approach vectoring has a very logical approach, and similar to Stars once you understand what it's doing. On initial approach it will assign you a runway usually an ILS if available and vector you to a parallel approach to the runway, either downwind, upwind depending on direction (Or crosswind if approaching from that direction.) Then about 27nm (Could be further or shorter, depending on defined approach data in the AFCAD, and Traffic) from the runway, you will be vectored Crosswind. At some point you will be given final approach clearance to intercept the ILS and vectored to it on an angle usually about 30 degrees. The trouble happens because ATC doesn't take in consideration wind and other factors, that can veer the aircraft off it's invisible line. As your aircraft goes more and more away from it it reaches it's tolerance and vectors you back, usually a 30 degree turn left or right, followed by another back to the original coarse. This is what gives the impression that ATC is vectoring you all across the sky. This is also how AI is vectored, which is why you constantly hear coarse corrections to AI throughout the flight! . If you use more complex aircraft like the NGX, while these coarse correction still occur, it won't be as often. maybe 1 or twice on the approach.

If you have SID - STAR charts you can edit your FSX plan view to add or delete waypoints as needed I would assume if they are recognized. In FS 2K2 I immediately went to a planner that correctly let me do that so I inserted waypoints as needed. I used it in FS9 as well. This was the freeware Nav 3.1 (version 3 with the .1 update for FS9 I think.). FSX will take FS9 plans. It was only after using the PMDG series that I acquired FSBuild.

 

As an FS9 user I also use Active Sky (6.5 for me). FSBuild sees its loaded weather and uses winds aloft for adjusting its fuel planning. I process the FS9 plan in Active Sky printing out the full report which has winds/temperatures aloft for waypoints along your route as well as METARS and TAF (forecasts), average wind over the route (also seen by FSB) and add that to the printed out navlog of FSB. This is almost equivalent to a dispatch report handed to the airliner crew.

 

There are dispatch planner products but AFAIK they only use real-time weather. I use archived weather in AS for the Z time of the departure location to match the saved time of day in my saved flight in a parked partially cold and dark condition.

 

I never cared for the map/drag flight planner in FS9 and I never could get its form to print and yes, I do have IE on the PC being a prerequisite to that.

E Mailing an FSX Flt PLn

How can I send a Flt PLN created in the FSX Flt Planner and saved by E Mail to another FSX user. The same for a Flt PLN saved in Radar Contact format using Controll Shift ; ?

ress

There are three files saved when using ctrl-shft-; :

planname.rcd

planname.wx

planname.flt

 

The last two are FS files.

 

You can send these two another RC/FSX user provided that person has the same aircraft and scenery. You would also send the .pln file of that name. All of these except the .pln file are "state" files meaning snapshots of the environment and aircraft status at the time of the save. When RC loads the .rcd it will look for the same name .wx and .flt files.

 

Open a .flt file in wordpad and you can read what it stores. The is a section way down that specifies the aircraft. The other non-pln files are binary.

 

The proper way to send them is to zip them up (all reside in the FSX plan folder under your documents) so they preserve the format and attach the zip to an e-mail.