I've been digging into P2ATC on MSFS 2020 and really enjoying it. I've got some questions I'm hoping for some guidance that I couldn't find in the manual or online (or at least I'm not understand it).

1 - So far my experience has been using the stock ATC in MSFS. With stock, when I'm on my approach, the ATC will direct me down to the correct altitude to enter the approach. In P2ATC, I don't seem to get that level of direction. I think I'm noticing I will get a clearance from center for the approach with a final altitude, then hand off to tower or told to call back when on the ground. This final instructed altitude is too high. The altitudes are correct in the flight plan, I'm just not receiving any instructions on the following final steps. I'm wondering if at this point, I'm expect to execute the steps on own to catch the GP/GS? 

2 - I've noticed a few times ATC seems to get in a command loop. I'll be told to descend to an altitude and it will immediately repeat itself. It continues long past I get there. I just start clicking things and can get it to stop. Hitting clear in the say it box or clicking something in the flight plan might work. Am I doing something wrong, or is this a bug?

3 - Some clarification on changing runways on arrival. It seems when I file/verify/build the plan, it assigns an expected active runway. What I'm wondering is if the weather changes, will I be assigned a different runway when I near the airport or would I have to request a different runway. I have the force runway unchecked in the settings. 

4 - Sanity check on my process for starting a flight. Does this make sense or is there a better way?

• I'm building a basic flight plan in Navigraph. Export. It may be redundant, but I like the interface and I'm paying for it. 🙂
• I load that into P2ATC. Verify it. Then do the auto create. It builds a complete plan. Export.
• I then load the P2ATC plan into MSFS. 
• Connect P2ATC and file the plan.

I then let the NAV computer fly the plan or use HDG vectors from P2ATC if provided. Things go sideways when I try to program the approach into the MSFS flight computer and editing the plan in the MSFS flight computer is 100% disaster with 50% chance of crashing/freezing.

Thanks for any assistance.

1.  ATC will clear you for the approach.  At that point, you are cleared to descend to and follow all the altitude restrictions in the approach.  I most cases, ATC's last altitude assignment will be the FAF altitude if there is no transition.  With a transition, it will be higher in most cases.

2. Sometimes a set of commands get backed up in the system and all come out at once.  Off altitude commands are issued every 30 seconds if you are not climbing or descending at or above the "Minimum Vertical Velocity".  If these get backed up, then they may "spew" out. this should be an exception and if it happens, just ignore them.  There is a remote possibility that they won't stop, indicating ATC has lost it.  In these cases, if you're not on an approach, you can disconnect P2A, reconnect, file the flight plan and make an initial call to the controller you were speaking to like "Approach, Beech 1VB at 6000 feet".  Things should get back on track after that.

3. Yes, if the winds change, P2A will calculate a new runway.  In general, the last chance for a runway change is when you get the "Expect the xxxx arrival for the ILS to ...." call.  After that, there won't be changes even if winds change, unless something strange happens.

4. Your process if solid.  I would never try and input the plan into MSFS's GPS or FMS.  

Hope that helps.

Dave

Thanks, Dave. Very helpful. 

3 hours ago, AuFinger said:

Things go sideways when I try to program the approach into the MSFS flight computer and editing the plan in the MSFS flight computer is 100% disaster with 50% chance of crashing/freezing.

In P2ATC check the option "Import/Export SID/STAR/APPR waypoints", then you get at least all the waypoints (including approach waypoints) into the GPS/FMC.

Dirk

4 hours ago, Dave-Pilot2ATC said:

I most cases, ATC's last altitude assignment will be the FAF altitude if there is no transition.  With a transition, it will be higher in most cases.

Dave,

I noticed the following (it might very well be how it is done in the real world, it just seemed odd to me and that's why I'm asking): in virtually all approaches I've flown with P2ATC that lead into a transition, where I get "... descend via the XXX transition to YYY feet", ATC gives my my current cruise altitude, and not the altitude that the chart for the transition suggests...

For example:

"Descend to One One Thousand feet via the TAYTO transition" (which was my current cruise altitude)

but the chart indicates a much lower altitude (5500 ft) after reaching TAYTO:

 

As I said, this happens on every approach with a transition, and P2A always gives me my current altitude. Not a big deal, I know from that point on I'm on my own and I just descend to the published altitude anyways (without any objection from P2A) but I'm just wondering if that is really how it's supposed to work, or if it's a bug.

 

Thanks!

Dirk

 

 

12 hours ago, woodstock327 said:

In P2ATC check the option "Import/Export SID/STAR/APPR waypoints", then you get at least all the waypoints (including approach waypoints) into the GPS/FMC.

Dirk

Yes, thanks for mentioning that setting. That option is necessary for the procedure I outlined.

Essentially my process removes the the world map and entering any approach/arrival procedures into the flight computer for flight planning. One less thing for MSFS to muck up. 🙂

58 minutes ago, AuFinger said:

Essentially my process removes the the world map and entering any approach/arrival procedures into the flight computer for flight planning. One less thing for MSFS to muck up. 🙂

Yeah that's exactly what I'm doing too. For ILS / VOR approaches that's all I need, and for RNAV approaches (I mostly fly the TBM where this works) I can load the approach into the GPS mid-flight and then I just activate the appropriate approach leg once I'm past the IAF.

Dirk

Dirk,

Thanks for the report.  That sounds like a bug.

Dave