I am thinking of purchasing RC. I know that it needs to have a flightplan to work and I currently fly a lot with Ifly 737 in FS2004. Could I export a flightplan from Simbrief into MSFS format, program the Ifly FMC with the same flightplan manually, and use the MSFS format for that route in RC ?  will that work ?  I am trying not to purchase separate flightplanner software, but trying to use RC with my Ifly 737

I'm not familiar with the requirements for the iFly FMC but providing SimBrief can generate a plan that can be read by FS then RC should also be able to read it.

 

Other iFly / SimBrief users may be able to confirm.

FYI:

 

I downloaded and read the user guide for Simbrief. It only mentions it outputs in MSFS format. RC can read FSX html and FS8/9 .pln formats and FSX non-html formats as well.

 

A positive note is that via Navigraph you can purchase an AIRAC subscription. Navigraph also supports later IFly formats so you can sync the terminal database data (SIDs, STARS, Approaches) between the FMC and the FS output sent to RC subject to restrictions regarding dynamic runway assignment noted in my following paper.

 

Here is a paper I wrote about why this is important but based on FSBuild:

 

fsb tips and update.pdf

 

---------------

 

Unlike some other planners, you still will have to enter your plan manually as you state into the IFly FMC as I did not see that format mentioned in the User Guide nor a brief look in its forums.

 

Importing plans is done on some real world aircraft via ACARS or other means and then checked by the responsible pilot. It offers some error proofing in that less is likely to be left out and typos, etc.

 

Some planners can also interface with Active Sky offering fuel planning in the process. I use archived weather stored from the real world. FSBuild is one. Some only can use real world weather which might introduce an error if you are located in a different time zone using real time flying but in a different area.

 

Just a couple of tips. not intending to be intrusive in your choices.

 

 

 

 

 

thanks for the info. I found out that Simbrief DOES have an option to output flightplans to the format the Ifly uses .FLTPLAN even though the documentation doesn't note it..  Problem solved.  looks like I will be purchasing RC.

Hi,

 

I use both products without any problems.

 

I still prefer FS Build for flight plans , but that's just my own preference.

You can use whatever means you like to generate iFly flight plans but you should enter them manually since you will lose all constraints otherwise...

 

DJ

FSBuild has in its build options a setting to include altitudes it calculates in the exported files. I looked directly at its AIRAC data for SIDs, STARs, and approaches and some waypoints in its procedures do have altitude restrictions in them.

 

In addition, you also have the I-Fly AIRAC data which also should specify the altitude restrictions.

 

RC itself does not use .pln altitude restrictions. Within the departure zone of 30 nm if you choose or are required to use your own navigation in this area for RC just choose the appropriate restriction option. Page 108 explains these.

 

Also investigate the NOTAMS option in RC which allows you flexibility in that RC becomes advisory.

Ron,

 

My point was that the various altitudes (other than cruise) and speed constraints are lost in the import to iFly. As a consequence you need to use approach/departure plates to restore that information within the FMC. Thus, it's a heck of a lot easier to simply enter the flight path data into the FMC manually. This guarantees that the constraints will be picked up from the AIRAC.

 

DJ

1. Doesn't the I-Fly have a terminal procedure data base which includes altitude restrictions? I use the PMDG B737NG classics and the altitudes are in that database including hard restrictions.

 

Here's an extract for the PMDG:

 

SID ORSKY6 RNW 04 RNW 12L RNW 12R RNW 17 RNW 22 RNW 30L RNW 30R RNW 35 FIX MSP FIX JURNY FIX RUMLE FIX PEDLN FIX ORSKY
  TRANSITION FOD FIX FOD
  TRANSITION OVR FIX ONTIJ AT OR ABOVE 12000 FIX GOOLD FIX SIMJI FIX EYHUX FIX PUMKN FIX OVR
SID RST6 RNW 04 RNW 12L RNW 12R RNW 17 RNW 22 RNW 30L RNW 30R RNW 35 FIX FGT FIX FOBUG AT OR ABOVE 4000 FIX DOKTR FIX CORDY FIX RST
  TRANSITION ALO FIX ALO

 

 

 

2. If you use a planner that has altitudes in its export for I-Fly, does it respect those altitudes? The I-Fly may not interpret those has hard and that might be the only change on the LEGS page.

I created a plan with FSBuild with an altitude restriction and sent out the I-Fly 737 format .flightplan file. Interesting no altitudes were in the export, just cruise.

 

That answers my question #2.

Ron,

 

With regard to 1. ... Yes, the iFly uses the Navigraph or NavdataPro AIRAC databases, but procedure names are not sent with the FSBuild flight plan - just waypoints. The waypoints without the context of a procedure are just waypoints and have no inherent constraints. As a consequence, if you want to import an FSBuild flight plan (and I do use FSBuild to create plans along with SimBrief) it is best to leave the procedures out of it and just import the route. Once that's done you can insert the SIDs/STARs manually and all the constraints will be automatically inserted. That's best practice with PMDG aircraft as well...

 

DJ

For 1.:

 

I use the non-sticky option to export from the current build so a  more complete .pln goes to RC, and then just as you say the center is exported to the FMC. That lets me use dynamic runway assignments from RC. Only the common procedure waypoints are sent to RC in the .pln file.