dbb1052

I've noticed that the VOR frequencies sometimes show up in the P2ATC flight plan and sometimes they don't, even in the same flight plan. Is there a reason for this or something I'm doing wrong? Thanks, Doug

As always thanks Dave. I will work on that later. I did open up the "taxi mnt" for KSFO and the strange taxi routes show up there. I tried to paste a screen shot for you, but can't seem to paste pictures in the forum? Now I need to work through the instructions and try to fix it. Thanks again Doug

I seem to get a lot of taxi routes that seem illogical. I tried to paste two P2ATC taxi maps from recent flights out of KSFO to illustrate the problem, but I could not paste into this message? I'll try to describe the routes, Taxing to 01L, It went on A toward the departure end of 01L then across 01L and across 01R then left on L to M then back across 01R to get to 01L. In another one to 01L from a different gate, it went on A toward the departure end of 01L to G then across 01L and across 01R then right on L to M then back across 01R to get to 01L. I t doesn't seem logical to loop around like this and cross multiple runways, when there is a simple direct route to the runway. I just ignore the taxi path and in both of these cases taxi on A to M to the runway. However, I then run into a problem where I do not get instructions from ground to contact the tower for takeoff clearance. If I try to contact the tower directly, it just sends me back to ground for taxi instructions. I have found that if I just taxi onto the runway and then contact the tower, it will then give me takeoff clearance. I'm not sure what the logic is here, but it seems strange. Any thoughts or suggestions would be appreciated.

I seem to get a lot of taxi routes that seem illogical. I tried to paste two P2ATC taxi maps from recent flights out of KSFO to illustrate the problem, but I could not paste into this message? I'll try to describe the routes, Taxiing to 01L, It went on A toward the departure end of 01L then across 01L and 01R then left on L to M then back across 01R to get to 01L. In another one to 01L from a different gate, it went on A toward the departure end of 01L to G then across 01L and 01R then right on L to M then back across 01R to get to 01L. I t doesn't seem logical to loop around like this and cross multiple runways, when there is a simple direct route to the runway. I just ignore the taxi path and in both of these cases taxi on A to M to the runway. However, I then run into a problem where I do not get instructions from ground to contact the tower for takeoff clearance. If I try to contact the tower directly, it just sends me back to ground for taxi instructions. I have found that if I just taxi onto the runway and then contact the tower, it will then give me takeoff clearance. I'm not sure what the logic is here, but it seems strange. Thanks, Doug

On a departure with no SID, why does ATC try to vector you to intercept the course line from the airport to the first waypoint and not vector you direct to the first waypoint, then as filed? From what I can tell in the real world it seems you would get vectors directly to the first waypoint, not back to the course line between the airport and the first waypoint. Here is my specific example: The flight today was KBUF to KJFK. When I turn to the heading assigned by the tower (080), but cut the turn off when I was lined up with the first waypoint and flew directly toward the first waypoint (~100), I was told I was off course and got several vectors directing at a sharp angle (205) to the direction I was flying. Then when I request direct to the first way point. I get the following reply all in one long message "DELTA Twenty Six Zero One your flight plan seems to be out of date. Please file a new one and call back for clearance. Cleared direct to Golf Echo Echo (my first waypoint) then as filed Expect the ILS approach to runway Two Two Right with the CIMBL transition at KENNEDY International Altimeter is Two Niner Eight Six at BUFFALO NIAGARA International Contact CLEVELAND Center on One Two Five Point Eight Seven have a good morning". After that it seemed ok for a while, but then no descent clearance until I gave up and just flew my flight plan. Then much later, when I was well into my arrival, I got a message to resume navigation and climb to my cruise altitude. I shut it off at that point. Not a major issue, and I may not understand non-SID departure vectors, but something just doesn't seem right? Thanks.

I would still like to go back to the original issue. Why does ATC try to vector you to intercept the course line from the airport to the first waypoint and not vector you direct to the first waypoint, then as filed? From what I can tell in the real world it seems you would get vectors directly to the first waypoint, not back to the course line between the airport and the first waypoint. Not a major issue, everything works, it just doesn't seem right? Thanks.

In my last 3 flights, twice recently, once into KSEA and once into PAJN there was no clearance to decend or the clearances were way off from the STAR bringing me in too high ie. KSEA cleared only to 14500 but chart is 3200 at KARFO. At PAJN never cleared me below cruise altitude FL 360 even after I ignored it and landed it was still telling me to climb to FL360. The altitudes in the flight plan in Pilot2ATC looked correct in both cases ie. agreed with the STAR and IAF going into KSEA and would have brought me to the correct altitude for the approach at PAJN. But ATC ignored what was in the filed plan. I actually reflew the flight into KSEA using same flight plan imported from SimBrief and next time it worked correctly, but then my next flight was to PAJN and did not work? Have been using Pilot2ATC for a long time and never had these problems before. Version 2.6.3.2 Beta 8S4 MSFS 2020 PMDG 737