Flight planning

[Guest Alias]

Hi,I'm using FSNavigator to prepare my flight plans, but as far as I can see, I can't use it on the MD11. I don't know if there is another way to prepare a flight plan in FSNav, but I do as follows:1 - pick up a departure runway2 - pick up an arrival runway3 - calculate autoroute4 - Export to PMDGThat used to work with 737 and 747 but not with MD11. The fact that I must choose a departure runway doesn't allow me to change it, if necessery. In the tutorial the departure point is: EGLL which is the aiport with all SIDs and STARs available, but, on the contrary of how the 737 and 747 behave, the MD11 doesn't recognize my departure airport but only the runway. :( well I hope someone understood what I meant. Does anyone have a clue? or are there other planners for quick export to MD11 FMC? Many thanks

[Guest Alias]

OK, after investigation I have found that the problem seems to be the MD11 neither the flight plan, nor the SID and STAR for LFPG as I thought. I have loaded the same plan succesfully on the 747. :( On MD11 everytime I try to change SID I got CTD.

[downscc 1,327]

Share the flight plan to LFPG then step through what you did, step by step, to get the CTD. Let's see if we can't reproduce it.

[Guest Alias]

Share the flight plan to LFPG then step through what you did, step by step, to get the CTD. Let's see if we can't reproduce it.

Hi Dan,here following the flight plan as it was generated by FSNavigator. The procedure on how to prepare it is in my original post, the procedure on how I load it on the FMC is the usual: the file's name is LFPGCYFB001 on the CO ROUTE. I then go to F-PLN page and see the first point is RW27L --> press the corresponding LSK to access the LAT REV page, click on SID and BOOM!Hope you reproduce it.ThanksExported from FSNavigator30LFPG1DIRECT1 N 49.0097 E 2.5478 39027L11 N 49.0237 E 2.5698 3901390--1000000-1000000D267B2DIRECT1 N 49.0177 E 2.4623 0000PG2742DIRECT1 N 49.0948 E 2.3412 0000PG2762DIRECT1 N 49.1175 E 2.3195 0000BVS2DIRECT1 N 49.4363 E 2.1532 0000OPALE2DIRECT1 N 49.8997 E 1.8850 0000ABUDA2DIRECT1 N 50.1163 E 1.7575 0000DIMAL2DIRECT1 N 50.4925 E 1.3663 0000ALESO2DIRECT1 N 50.5755 E 1.2255 0000ROTNO2DIRECT1 N 50.8572 E 0.7780 0000TIGER2DIRECT1 N 51.0672 E 0.4395 0000BIG2DIRECT1 N 51.3308 E 0.0348 0000HEMEL2DIRECT1 N 51.8055 W 0.4195 0000BUZAD2DIRECT1 N 51.9422 W 0.5522 0000WELIN2DIRECT1 N 52.2472 W 0.8522 0000TIMPO2DIRECT1 N 52.5588 W 1.1638 0000TNT2DIRECT1 N 53.0538 W 1.6700 0000POL2DIRECT1 N 53.7438 W 2.1033 0000RIBEL2DIRECT1 N 54.0162 W 2.2897 0000SHAPP2DIRECT1 N 54.5000 W 2.6272 0000MARGO2DIRECT1 N 54.7075 W 2.7747 0000GOW2DIRECT1 N 55.8705 W 4.4457 0000SUPIT2DIRECT1 N 57.3325 W 7.0850 0000BEN2DIRECT1 N 57.4780 W 7.3653 0000NINEX2DIRECT1 N 58.8555 W 9.5000 0000BALIX2DIRECT1 N 59.0000 W 10.0000 0000DARUB2DIRECT1 N 67.0000 W 60.0000 0000070E2DIRECT1 N 65.5000 W 70.0000 0000TIBEG2DIRECT1 N 63.6790 W 68.3858 0000CYFB1-1 N 63.7563 W 68.5558 1113501 N 63.7483 W 68.5380 1111111--1000000-1000000

[downscc 1,327]

What I hoped for was a flightplan in a readable format; e.g., ORIG SID FIX FIX STAR DEST. What you provided was the flight plan file created from your flight plan."press the corresponding LSK to access the LAT REV page, click on SID and BOOM" - doens't tell me the fix at which you are accessing LAT REV.By the way, I use FSBuild2 or manually enter fplns, don't have FSNavigator so I'm not using it when I try to duplicate your problem. Regardless, there should not be a CTD even if fplan entry is incorrect. That is what I am trying to duplicate.

[Guest Alias]

Hi Dan,I hoped to be able to upload the whole file-flight plan but the system does not allow me, anyway all you have to do to recreate the problem is to copy and paste the plan I gave you as it is. The departure is LFPG (RWY27L), no matter the SID in use when I try to change runway (by clicking on the LSK next to RWY27L) I got a CTD.The good thing is that it seems to happen only at LFPG as I have just succesfully completed a flight between OMBD and VHHX :( Thanks

[downscc 1,327]

FS9 or FSX? Current navdata cycle 0901 from Navigraph?EDIT: Disregard, I duplicated the CTD at LFPG on RW27L in FSX with Cycle 0901.... let's see what is going on here.Interesting.

[downscc 1,327]

I have reported the problem to the development team.It appears that if the number of SID procedures are reduced from about 159 to less than 150 it would work okay. Wow, that is a lot of procedures... I guess the government has an office whose full time job is creating departure procedures. The busiest airport in the world (KATL) has 16 RNAV DPs with which will allow you to depart in all directions. Anyway, problem confirmed and reported.Thank you,

[trisager 2]

I guess the government has an office whose full time job is creating departure procedures.

I'm sure they do :( I was wondering about the difference, though, so I took a closer look at the SID files. At least part of the difference must be a matter of naming - the LFPG SID section is longer than the KATL section, but not ten times longer. E.g. LFPG SIDs PTV1A,1B,1D,1E,1G,1H,1K,1L depart from different runways, but they all end at PTV. On the other hand, the BRAVS FIVE departure has eight distinct paths, depending on departure runway, to BRAVS (so if the French government office you mention ever get their hands on it, it will likely be renamed BRAVS1A, 1B, 1C, 1D, 1E, 1G, 1H, 1I).Still, even with that, the departures from LFPG are more complex than from KATL. I don't know what Atlanta airspace is like, but around Paris it must be intricate with de Gaulle, Orly and Le Bourget in fairly close proximity. Or maybe it is just a government thing ...Cheers,Tom

[Guest Alias]

Hi Dan,good to know you could be able to duplicate the problem :(, hope they will fix it.Now my question is why the 737 and 747 are immune...

[downscc 1,327]

The FMS/MCDU is new code.. the operation is actually very different from the Boeings. If I were a developer, I would not expect 160 separate departure procedures at one airport but regardless of that the problem I believe pmdg will get a fix out for it.

[tango4 4]

Hi everyone !First, I'm glad I have an answer to my problem because I had the same issue on FS9 MD11 at CDG.Regarding the number of procedures at LFPG, maybe I can shed a light on it...I happen to work as an ATC in real lifeat CDG !! ;)And I must say that it's true we have a lot of them and they are really complex. As you were able to guess, a big part of that complexity comes from the fact that we have Le Bourget and Orly very close to CDG. And by the way, we (at CDG) provide approach control for Le Bourget.And why so many letter ? Each group of letters is for a given configuration. We are either facing West or facing East. LFPG and LFPB configuration are linked. But Orly is obviously independent.So the 1A/B/C means LFPG/LFPB and LFPO facing West 1D/E/F means LFPG/LFPB facing West, LFPO facing East 1G/H/J means LFPG/LFPB and LFPO facing East 1K/L/M means LFPG/LFPB facing East, LFPO facing WestThere is a reason why there are no 1I departures, but I can't remember it right now ;)In each triplet of letters, the first one means departure from the north runway, the second one from the south runway, and the third one from Le Bourget.Historically, there were a lot of differences between the "linked" configuration (A,B,C,G,H,J) and the "invert"(the others !) configuration so we kept that designation. Fortunately, there are not many differences any more, except for some initial climb Flight Level, and some low altitude trajectories.I hope that itcould help you understand things a bit better.Don't hesitate to ask if you have some questions.Best regards.Charles

[Guest Alias]

Hi everyone !First, I'm glad I have an answer to my problem because I had the same issue on FS9 MD11 at CDG.Regarding the number of procedures at LFPG, maybe I can shed a light on it...I happen to work as an ATC in real lifeat CDG !! ;)

This makes of you my greatest friend as my home airport is LFPG

Don't hesitate to ask if you have some questions.Best regards.Charles

For sure I will...many thanks for now. :(

[Guest FrancoisH]

The problem is there is no "radar" departure in France or that for every runway, you have a new procedure... There is for jet and propellers, there is for different issues...Do not forget if KATL have the most intense traffic, LFPG is only 15 nm north of LFPO which are the first and the third most important airports in France, and you have LFPB which is only 2nm south west of LFPG and which have intense IFR business jet traffic... so all those airports together make you need many procedures for every case (like LFPO being open with opposite QFU)...This make Paris one of the most complex airspace in Europe, together with London and Amsterdam.Regards.

[tango4 4]

Well, we actually have some radar departures.One big reason why we don't use it a lot is environmental contrainsts. Basically, we cannot turn aircraft out of the SID before FL60 or approx 6Nm out in the departure (except for safety reasons of course).Another reason is that we make independent parallel departures between north and south runways: their axis are separated by less then 3Nm (our radar spacing), so the SID are designed to strategically separate the trajectories after 10Nm out. But this is becoming a bit technical here...And the reasons mentioned in the previous post also!Charles