Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FSC9 imported flightplan from EHAM trouble

Featured Replies

Hey guys,

I am having a strange issue.  I can't seem to import an Flight sim Commander 9 generated plan to the 777 departing from EHAM.  I originally wanted to take the LRF from EHAM to RJTT, but I get 'INVALID ENTRY' and an error message of 'Destination airport not found in selected .rte file : Import Aborted'

 

I tried flightplans to other destinations, all have the same error.  The flight plans are accepted fine in 747v1, MD-11, and NGX.  I then moved  the 777 to EIDW, created a EIDW-RJTT plan in FSC9.  The EIDW RJTT plan imported fine.  The plans show up in the Route Request too.   Flightplans going to EHAM were fine as were all previous FSC9 generated plans.  Just for ducks, I also tried to create a flight plan from Rotterdam EHRD and got the same INVALID ENTRY errors.  I tried both plans that were 'auto generated' and ones that I created myself within FSC9, something is wrong in the Holland area. 

 

 

Can anyone else with FSC9 or another flight plan generator make it out of EHAM?

 

Cheers

TJ

"The knack of flying is learning how to throw yourself at the ground and miss." - Douglas Adams
war2.jpg
Tejon 'TJ' Stanley

 

 


Can anyone else with FSC9 or another flight plan generator make it out of EHAM?

 

Not me, I have the same problem as you describe (using Aivla EFB btw), I get the error message on first attempt to load the CO route, any further attempts just fail silently (and erase the destination airport I had filled in manually in the RTE page). In my case the attempt was a route EHAM SBGR.

 

Could only get out of EHAM by manually inputting the route.

 

Still trying to figure out if there is any user error here, before submitting a ticket.

 

Regards and happy flying,

 

Cristian Gonzalez.

I have started using pfpx which allows me to export flightplan to pmdg and fsc.

Bilal Asif Khan

Same here. There´s another thread with same problem and more people. I submitted a ticket this morning. Let´s wait....

 

Best.

 

Miquel Egea.

  • Author

Well it is a headscratcher, I can't tell what is different between plans that work and don't work.  Hopefully PMDG will look into this.  I created two flight plans for testing EHAM-EDDM and EDDM-EHAM, using same waypoints in each direction, going DIRECT to each waypoint. 

 

Can PMDG figure out why EDDMEHAM.rte imports just fine, while EHAMEDDM.rte is rejected?  Both plans work fine in 747, MD11, and NGX.

 

Here is the data for EDDMEHAM.rte

 

Generated and exported by FlightSim Commander · Version 9.3.HF_1 · Build: 06-September-2013

14

EDDM
1
DIRECT
1 N 48.3538 E 11.7861 1486
-----
1
0

1
1486
-
-1000000
-1000000

LELTA
2
DIRECT
1 N 48.4931 E 10.9553 0
0
0
0

RIDAR
2
DIRECT
1 N 48.5884 E 10.8028 0
0
0
0

LIRSU
2
DIRECT
1 N 50.1867 E 6.4533 0
0
0
0

LNO29
2
DIRECT
1 N 50.2678 E 6.2750 0
0
0
0

PELIX
2
DIRECT
1 N 50.4969 E 5.7625 0
0
0
0

LNO
2
DIRECT
1 N 50.5858 E 5.7103 0
0
0
0

TERLA
2
DIRECT
1 N 50.6825 E 5.6656 0
0
0
0

BROGY
2
DIRECT
1 N 51.1825 E 5.4489 0
0
0
0

LUTOM
2
DIRECT
1 N 51.2656 E 5.4210 0
0
0
0

LOPIK
2
DIRECT
1 N 51.9308 E 5.1292 0
0
0
0

ROVEN
2
DIRECT
1 N 51.9629 E 5.1149 0
0
0
0

OGINA
2
DIRECT
1 N 52.0975 E 5.0546 0
0
0
0

EHAM
1
-
1 N 52.3081 E 4.7642 -13
-----
0
0

1
-13
-
-1000000
-1000000

 

 

******************************************

Here is EHAMEDDM.rte

 

Generated and exported by FlightSim Commander · Version 9.3.HF_1 · Build: 06-September-2013

12

EHAM
1
DIRECT
1 N 52.3081 E 4.7642 -13
-----
1
0

1
-13
-
-1000000
-1000000

OGINA
2
DIRECT
1 N 52.0975 E 5.0546 0
0
0
0

ROVEN
2
DIRECT
1 N 51.9629 E 5.1149 0
0
0
0

LUTOM
2
DIRECT
1 N 51.2656 E 5.4210 0
0
0
0

BROGY
2
DIRECT
1 N 51.1825 E 5.4489 0
0
0
0

TERLA
2
DIRECT
1 N 50.6825 E 5.6656 0
0
0
0

LNO
2
DIRECT
1 N 50.5858 E 5.7103 0
0
0
0

PELIX
2
DIRECT
1 N 50.4969 E 5.7625 0
0
0
0

LNO29
2
DIRECT
1 N 50.2678 E 6.2750 0
0
0
0

RIDAR
2
DIRECT
1 N 48.5884 E 10.8028 0
0
0
0

LELTA
2
DIRECT
1 N 48.4931 E 10.9553 0
0
0
0

EDDM
1
-
1 N 48.3538 E 11.7861 1486
-----
0
0

1
1486
-
-1000000
-1000000

"The knack of flying is learning how to throw yourself at the ground and miss." - Douglas Adams
war2.jpg
Tejon 'TJ' Stanley

I already emailed this issue to the Guys at PFPX.

 

It seems PMDG changed the format of the FPL in the new 777.

The routeplanners are not up to date yet. 

Issues known with PFPX,Routefinder,FSC etc.

The guys from pfpx are looking in to it. 

 

Don't know about the others but to drop them an email won't hurt ;)

Tip: make an manual route in the fmc, save it and include it in the mail to show the difference between them :)

 

Greetings Mark

Mark Visch

  • Author

I created a manual plan in the 777 using the same one auto generated by FSC9 which worked fine from EHAM.   It still doen't quite explain why other plans generated by FSC9 work fine, while those just from EHAM/EHRD area don't work...possibly other airports too.

 

Here is EHAMEDDM001.rte as directly entered in the 777, following the route autogenerated in FSC9.

 

PMDGFMC *5.1*

15

EHAM
EHAM
-
1
1
0
DIRECT
1 N 52.3081 E 4.76417 -13
-----
1
0

1
- -13 -1000000 -1000000
- -1e+006
0 0 0 0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 -1000000 0

dtobase
dtobase
-
2
0
0
DIRECT
1 N 52.3081 E 4.76417 -13
1
0
0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
113.04
0
0 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 -1000000 0

OGINA
OGINA
-
2
1
0
UN852
1 N 52.0975 E 5.05463 0
0
0
0
X
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0

0
141.883
0
0
0.569007 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 999 0

ROVEN
ROVEN
-
2
1
0
UN852
1 N 51.9629 E 5.11485 0
0
0
0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0.283143 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 999 0

LOPIK
LOPIK
-
2
1
0
UN852
1 N 51.9308 E 5.12916 0
0
0
0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0.243468 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 999 0

LUTOM
LUTOM
-
2
1
0
UN852
1 N 51.2656 E 5.42101 0
0
0
0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 999 0

BROGY
BROGY
-
2
1
0
UN852
1 N 51.1825 E 5.44889 0
0
0
0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 999 0

TERLA
TERLA
-
2
1
0
UN852
1 N 50.6825 E 5.66556 0
0
0
0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 999 0

LNO
LNO
-
2
1
0
UN852
1 N 50.5858 E 5.71028 0
0
0
0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 999 0

PELIX
PELIX
-
2
1
0
UZ210
1 N 50.4969 E 5.7625 0
0
0
0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 999 0

LNO29
LNO29
-
2
1
0
UZ210
1 N 50.2678 E 6.275 0
0
0
0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 999 0

LIRSU
LIRSU
-
2
1
0
UZ315
1 N 50.1867 E 6.45333 0
0
0
0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 999 0

RIDAR
RIDAR
-
2
1
0
Y161
1 N 48.5884 E 10.8028 0
0
0
0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 999 0

LELTA
LELTA
-
2
1
0
DIRECT
1 N 48.4931 E 10.9553 0
0
0
0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 999 0

EDDM
EDDM
-
1
1
0
DIRECT
1 N 48.3538 E 11.7861 1467
-----
0
0

3
- 1517 -1000000 -1000000
- -1e+006
0 0 0 0
X
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0
4
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
0 -1000000 0 0
-1000000 -1000000 0

-----
-----
-----
-----
-----
-----
-1e+006
EHAMEDDM
69
0 1
2
2
-1e+006 0
-1000000
-1000000
1

 

******************************

Here is the autogenerated EHAMEDDM.rte FSC9 plan of the same route.

 

Generated and exported by FlightSim Commander · Version 9.3.HF_1 · Build: 06-September-2013

14

EHAM
1
DIRECT
1 N 52.3081 E 4.7642 -13
-----
1
0

1
-13
-
-1000000
-1000000

OGINA
2
UN852
1 N 52.0975 E 5.0546 0
0
0
0

ROVEN
5
UN852
1 N 51.9629 E 5.1149 0
0
0
0

LOPIK
5
UN852
1 N 51.9308 E 5.1292 0
0
0
0

LUTOM
5
UN852
1 N 51.2656 E 5.4210 0
0
0
0

BROGY
5
UN852
1 N 51.1825 E 5.4489 0
0
0
0

TERLA
5
UN852
1 N 50.6825 E 5.6656 0
0
0
0

LNO
5
UN852
1 N 50.5858 E 5.7103 0
0
0
0

PELIX
2
UZ210
1 N 50.4969 E 5.7625 0
0
0
0

LNO29
5
UZ210
1 N 50.2678 E 6.2750 0
0
0
0

LIRSU
2
UZ315
1 N 50.1867 E 6.4533 0
0
0
0

RIDAR
2
Y161
1 N 48.5884 E 10.8028 0
0
0
0

LELTA
2
-
1 N 48.4931 E 10.9553 0
0
0
0

EDDM
1
-
1 N 48.3538 E 11.7861 1486
-----
0
0

1
1486
-
-1000000
-1000000

 

 

 

"The knack of flying is learning how to throw yourself at the ground and miss." - Douglas Adams
war2.jpg
Tejon 'TJ' Stanley

Yep I had the same problem today as well! 

I wanted to go from EHAM - KBOS and couldn't import it as well...

 

EDIT: I am using FSBuild 2.4.019.

Arjen Vandervelde

Me too, no plans generated with FSC9 from EHAM or EHRD can not be imported in the 777. Tried EHBK to LOWI and EHGG to LOWI and worked fine, but not EHAM or EHRD to LOWI.

Johann van Rhyn

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.