hi, i decided to give a try on pilot2atc mainly because it works both on p3d v4 and xp 11. 1st thing i must say is that i dont know how to use it at all and i dont have any other experience with atc programs 🙂

so i have installed it, i opened it, and i pressed connect and everything was fine. i connected to p3d , i was in lgav airport in athens, that appeared to the map of pilot2atc.

then i started making a flight plan: i was suprised how easy it was and without any reading of the manual or tutorial from youtube i did it !! lgav to loww (vienna), i put sid, stars, approach everything appeared right on the pilot2atc map. 

then i pressed saved and i chose the pmdg 747 folder in my p3d v4 to save it. i got the filename lgav-loww. but when i load the flight plan on the 747 fmc , by entering lgav-loww to the co route, i just see the origin and dest airports. i dont see the whole flight plan. the legs etc etc , that i see on pilot2atc menu. is it normal? 🙂 my .. innocent logic says that if i fill a flight plan to pilot2atc then i dont have to do it again to the airplanes. 

ps. i use navigraph latest 1805. i installed it right and to pilot2atc and pmdg 747 v3. 

 

thank you !!

Nikos,

Glad you're enjoying the program.  Most complex airliner FMCs, like PMDGs,  require you to enter the procedures in the FMC and not import them.  Therefore, the P2A export function does not export the SID, STAR and Approach waypoints. 

If you had airways or other en-route waypoints, those would have been exported.

Once you import the plan to the aircraft, you can easily look at the bottom of the P2A flight plan to see what SID, STAR and approach to enter.

Dave

On 4/29/2018 at 9:49 AM, Dave-Pilot2ATC said:

Nikos,

Glad you're enjoying the program.  Most complex airliner FMCs, like PMDGs,  require you to enter the procedures in the FMC and not import them.  Therefore, the P2A export function does not export the SID, STAR and Approach waypoints. 

If you had airways or other en-route waypoints, those would have been exported.

Once you import the plan to the aircraft, you can easily look at the bottom of the P2A flight plan to see what SID, STAR and approach to enter.

Dave

Hello Dave;

Was the tool ever updated in include the SID's. STAR's as part of the import? Since it has been close to 10 months since this was posted I was hoping that it did.

Thanks.

Forshaw. 

You'll have to ask PMDG if they will allow import of the procedures into their FMC.  That is not a P2A function.

Dave,

I'm a newbie (still in trial period).

The question I have concerns intermediate waypoints in an exported flight plan.  I'm using x-plane 11 and FF320.

Here is the problem I'm having with a KLAS-KLAX plan

This following sequence is set up by P2ATC:

KLAS 26R BOACH8 WHIGG DCT SHTNR SMASH SALLY GLESN ANJLL CAANN BOYEL CRCUS LYCOM TAANK (and several other WAYPOINTS in the ANJLL4 STAR and the ILS approach) KLAX ILS25R

This following sequence is what's exported to corte.in  using the Export Function (Import-Export SID/Star/Appr Waypts and Export Cleared Flight Plan selected in the Config Menu):

RTE KLASKLAX01 KLAS 26R BOACH8 WHIGG DCT SHTNR ANJLL4 SHTNR KLAX ILS25R CRCUS CI20 FL340

Note that the waypoints SMASH SALLY GLESN are not exported to Corte.In.  These 3 way points are not part of a SID or STAR.  When using the Corte.In plan, the omission causes ATC requests for course corrections between SHTNR and ANJLL.

I assume I'm doing something wrong.  I'd like to put the  P2ATC plan into the aircraft's FMC without having to enter the omitted waypoints manually.  I realize that I have to select the SID and STAR myself, and that's fine with me.

Thanks,

ASB

Because SHTNR is part of the SHTNR transition for the ANJLL4 arrival, the waypoints after that are removed.  If you use the SALLY transition, for example, SHTNR and SMASH are left in the flight plan and SALLY is the first STAR waypoint.

Dave

Thank you, Dave

This must be a database issue.  I'm using NavDataPro - latest IRAC, and on this ANJLL4 doesn't offer any transitions on the MCDU, so I can't even force SHTNR as a transition manually.

At this point in my experience with the program, and with the apparent shortcomings of of the database and/or the MCDU of the FF320, I guess it would be nice to be able to produce a raw version of all the waypoints on the P2ATC plan as filed as an export option, even the SIDs, STARs and approaches.

Regards,

ASB

I would report this issue to the FF320 folks if their MCDU doesn't show those transitions.  

Both the data and the charts from Navigraph 1903 show transitions for: CGNEY, DNERO, HAKMN, OTOOL, SALYY, SHTNR.

Dave