I had a couple flights over the last couple weeks, in the PMDG 777, where Pilot2ATC descended very late.  I had to basically do my own 360 to get low enough to start the approach.  These were flights NOT on a STAR, but vectored.  I was also using FS2Crew as well, if that matters.  But, I did everything I was supposed to do ( I thought), just way to high when the approach was hanf=ding me off to tower, where there was NO way, I was going to be able to land at the airport without a crash dive 🙂

Has anyone else seen that ever, or am I just maybe missing something?!

Be sure your Descent Rate is set correctly in the Flight Plan as P2A uses this to calculate the TOD point.  1800-2000 FPM is typical for airliners.   If you want more time for the descent, decrease this number....maybe to 1200 or so.

Then, once you start the descent, be sure and maintain the planned Descent Rate and Groundspeed, slowing below the planned groundspeed if you think you might be coming in high.  If you have a tail wind, you'll need to have a lower Indicated Airspeed to keep the groundspeed down.  

It is possible that the TOD was not calculated exactly right.  If you think it was way off, please email me ([email protected]) the log file for the flight and I might be able to determine what went wrong.

P2A Log files are located in: C:\Users\<UserName>\AppData\Roaming\P2A_200\Logs where <UserName> is your PC user name. 
Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab.
A new one is created each time you start Pilot2ATC, and is closed when you shut it down. So if you take the most recent one after you have the error and after you shut down P2A, you should have the correct one.  
Dave

Edited September 15, 20196 yr by Dave-Pilot2ATC

I might have had the Descent Rate wrong.  I guess I assumed it set it properly, but I didn't even think to look 😞  I will check next time 🙂 

I've quite a few times now had IFR flight plans where ATC just forgets about me and never directs me to land as I pass right over the field.

Please email me ([email protected]) the log file for the flight where this happened and I will see if I can figure out what went wrong.
P2A Log files are located in: C:\Users\<UserName>\AppData\Roaming\P2A_200\Logs where <UserName> is your PC user name. 
Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab.
A new one is created each time you start Pilot2ATC, and is closed when you shut it down. So if you take the most recent one after you have the error and after you shut down P2A, you should have the correct one.  
Dave

Ok next time it happens I will, thanks for your support.

On 9/21/2019 at 6:54 PM, rinkerbuck said:

I've quite a few times now had IFR flight plans where ATC just forgets about me and never directs me to land as I pass right over the field.

KORD by any chance? It's been doing that to me ever since I got the new FSDT scenery. I asked if anyone else was experiencing this over on the FSDT forum but never got a response.

 

I doubt that scenery is causing this issue.  There is a bug in the current version that causes an error that knocks ATC off.  It seems to only occur with specific conditions based on tracking the current waypoint in the flight plan.

This bug is fixed in the next update.

Dave

I did a flight again in the PMDG 777 from KSFO-CYYZ.  I was not descended properly again.  I had to do my own long extended heading to descend enough to turn back to the airport to intercept the ILS.  I was being handed off to tower at, like 13000 feet?!  I was NOT on a STAR, btw; just vectors.

So, I don't know what I am doing wrong, but it has happened multiple times in a row with the PMDG 777.

If getting vectored, the Vector Leg distance is critical also.  For a 777, it should be at least 5NM, more if you want more room to maneuver.  Set that on the FltPln tab of Config.

You also may need to slow your speed sooner to allow more time for descent and set your Descent rate lower in the Flight Plan so P2A starts you down sooner.

Dave

Is there perhaps a way to save these settings per plane, and then just pick the plane? It's kind of a chore to have to change all this stuff every time we go from a 747 to a DA-62.

 

20 minutes ago, eslader said:

Is there perhaps a way to save these settings per plane, and then just pick the plane? It's kind of a chore to have to change all this stuff every time we go from a 747 to a DA-62.

 

Yep same thing goes for mee too. Could you Dave consider in some future updates somekind pre settings, for airliners and ga ? Maybe something like that you could choose whatkind of plane you are flying ? It could be in the callsign page ? You could check it in box, like now when you check the "heavy" on callsign ?

Yes, an aircraft settings capability is on the list of future enhancements.

Great. Thanks Dave

On ‎9‎/‎24‎/‎2019 at 3:37 PM, Dave-Pilot2ATC said:

If getting vectored, the Vector Leg distance is critical also.  For a 777, it should be at least 5NM, more if you want more room to maneuver.  Set that on the FltPln tab of Config.

You also may need to slow your speed sooner to allow more time for descent and set your Descent rate lower in the Flight Plan so P2A starts you down sooner.

Dave

Is there a nm distance chart by airplane type?!  I will look into what mine is set to and make it bigger.  Is 5nm enough though, or more like 10nm?!  I have no idea.