clr100

Dave, Found the GA Ramp to be incorrect at KCLT. So of course the taxi instructions are also incorrect. Any way to change the position of the GA Ramp using taxi maintenance or otherwise? Chris

I've this happen to me as well. Could you post what you found out to be the problem as a result of the log files? Thanks.

Dave-P2A, Great to know you are looking at it for the future. So far I am liking what I see, particularly your support and desire to improve the product. I will send you the log file with all the errors. DaveCT, LOL. I know exactly what you mean. No, I don't want a real reprimand, just a virtual reprimand. In truth, it would be nice to know when I am doing things incorrectly so that I can correct my errors. But I know that involves a lot more intelligent ATC and more coding. There are probably an infinite number of scenarios to cover, but it would be cool. Chris

Still working on the trial and getting a feel for how the ATC works. Just wondering if ATC ever corrects you or reprimands you when you blatantly disregard their instructions. For example if you fly into controlled airspace without being cleared or being in the wrong pattern or taxing down the wrong taxiways. For example I was flying into a controlled airfield and requested a full stop landing on a 21R. ATC responded: "Baron Five Sierra XRay Expect to enter on a Right downwind for Runway Two One Right. call downwind". Instead, I disregarded their instruction and flew a straight in approach. I landed and reported to Tower that I was clear of runway. Tower just welcomed me and told me to contact Ground. When I checked out the log file there was a ton of error messages, one per second, following the ATC directive to enter the Right downwind pattern. The errors all appeared to be exactly the same, Error in ATCFlt.OnSecondTimerFired: System.NullReferenceException: Object reference not set to an instance of an object. at P2A_2018.modP2ADataGlobal.PositionIsPastSegment(GeoPoint Pos, FPWpt Wpt1, FPWpt Wpt2) at P2A_2018.ATCFlt.c05967a6f758bc7422757832c8e5dc1da() at P2A_2018.ATCFlt.onSecondTimerFired() : 09/02/2019 20:56:12 It appears that it was looking for me in the pattern and was detecting that I was out of position. The errors finally stopped when when I was about to land. If I am correct about these error messages in the log file being related to pattern position, why is the pattern position tracked if ATC never tells me I am out of position. Not a big deal but just curious and trying to determine the depth of this application. For the record I intended to fly a straight in approach but was fumbling around looking for the straight in request and couldn't find it, so settled for just the full stop request, and they of course directed me into the pattern when I was headed directly for the runway. So far I have been enjoying trying it out.

Dave, Thanks for checking it out. QUESTION 1: Regarding the runway overrun issue, how do I import the airport taxiways from x-plane Thought I was pretty careful with radio frequency changes but certainly could have made a mistake. I am using the x-plane default Baron 58 + REP (reality expansion pack by Simcoders). I don't think they mess with the comms. As I typically do, after departing KFLG, I switched the frequencies to tower and ground for KPRC so I can easily swap when on the ground. So if I wasn't on KPRC Tower (125.3), I would have been on KPRC Ground (121.7). If the logs are showing different, then there may be as you stated some sort of issue between the aircraft comms and P2A comms. I did all my radio switching via the aircraft comms. I did check several times to see if the aircraft and P2A comms matched and they always did, but I might have missed it when they were different. I will attempt to do the same flight using the P2A comms only to see if results are different. I will then attempt the flight with the default Baron 58. QUESTION 2: What exactly is the effect of the Controller Radius settings under ATC Settings tab in the P2A Config screen? Do they affect the comms range in any way? If not, what is the comms range if any? I will let you know the results of my test flights. Chris

Dave, I tried another flight in reverse from KPRC to KFLG and then back again. At first I had a problem getting a clearance response from KPRC Tower when I used the phrase “Request Departure” but when I changed that to “Ready for Departure” they responded correctly clearing me departure. I couldn’t seem to get KFLG Tower to respond when approaching their airspace, but that might have been that my phrasing was not correct. I think they responded to just my call sign, saying “go ahead”. But that is the extend that I could get them to respond. The return flight out of KFLG to KPRC was more troublesome again. The Tower would never clear me for departure no matter how I phrased or even when using SayIt. I also again had the problem when when approaching KPRC and contacting their Tower. I kept getting the directive to contact Tower on 134.5 which is the KFLG Tower. I would continue to hear this no matter what I did. My radio was clearly tuned to KPRC Tower. I did not actually try to contact KFLG to see what would happen. These airfields are only 47 miles apart. Is it possible that ATC was getting confused between the airfields because of their close proximity. I emailed you the log file for this flight as well. Chris

Thanks Dave. I have restarted P2A since, so I will try and fly it again both with and without a flight plan and will send you the log files if I have the same problems. Chris

Just bought the trial yesterday and have been reading manual. Set up an easy first 20 min flight today from KFLG to KPRC. So I start engines, put a direct to flight plan into the aircraft NAV. I tune my Comm 1 radio to 121.9 and contact Ground, "Ground, Baron five sierra xray, request taxi to runway two one". Ground responds with taxi instructions to runway 21. I repeat instruction and taxi, holding short at 21. I call Ground, "Ground <callsign> holding short runway two one." Ground replies to contact tower on 134.55. I repeat instruction. So far so good. I switch Comm 1 to Tower on 134.55. I call Tower, "Tower, <callsign>." Tower responds, "<callsign>, this is Tower, go ahead." So I know Tower is hearing me. I call Tower, "<callsign>, ready for departure runway two one". THIS IS WHERE IT STARTS TO GO OFF THE RAILS. I hear (not sure from whom but I am still tuned to the tower) "<callsign>, contact Tower on 134.55". Uh, I just contacted you. Not sure what to do, so I repeat call to Tower with just my callsign and they reply again with "<callsign>, this is Tower, go ahead". I repeat "<callsign>, ready for departure runway two one." I again hear the response, "<callsign>, contact Tower on 134.55." So I try going back to ground. I switch to ground frq 121.9 and call "<callsign>, holding short runway two one." They respond telling me to call Tower on 134.55. I switch Comm one back to 134.55. This just goes on and on. They never acknowledge my being ready for departure and clearing me. So I just take off and head for KPRC. When I get in range of KPRC, I tune KPRC Tower frq of 125.3. I call KPRC, "Tower, <callsign>." They respond, "<callsign, this is Tower, go ahead." Then I say, "<callsign>, inbound for landing runway zero three." They respond with, "<callsign>, contract Tower on 134.55." WHAAAT? THAT'S THE KFLG TOWER AND I AM AT KPRC! I'M SO CONFUSED. I am clearly doing something wrong, either in my phraseology, or in my setup. I did not put any flight plan into P2A, as I just wanted to do a simple VFR to try thngs out. Is it required to have a flight plan? The ground comms seemed to work ok without flight plan. I was careful to check that my phrases were correct in the lower right box. But even if they weren't I wouldn't expect this endless loop to contact the KFLG Tower, even when in KPRC airspace. Also KFLG has only Ground and Tower frequencies. Anyone have any suggestions as to what I might be doing wrong? I am anxious to try this again with hopefully better results.

Hi, Just downloaded the P2A trial last night. Because my tail number is N45SX, one of the first things I noticed was Microsoft Anna's annoying phonetic pronunciation for "X" (Xray). Definitely needs to be spelled as X-ray. I would also suggest spelling phonetic L as Lema instead of Lima. She pronounces the "I" as "eye". All the rest of the phonetic alphabet seems to be okay. Also, I am running Windows 7 64-bit, and find Microsoft Anna's voice somewhat difficult to understand. Any suggestions on downloadable voices to replace Anna, preferably free. I've done some Google searching, and it doesn't appear to be that easy to accomplish. Maybe next year I will bite the bullet and go to Windows 10. Chris