stringybfc

Sorry, that might have been a little misleading - the ATC wouldn't verbally report QFE, but it's not uncommon for QFE to be reported on a local digital ATIS service, eg: http://cityairportandheliport.com/info/, so for that component I was wondering if it might be incorporated in the "info" tab for an airfield. As you'll see in the top left box, both QNH & QFE are reported. This ATIS display is shown on monitors in the flying school & tower, and used by pilots when making initial contact with the tower. It is something that's easy to calculate, so not essential, more of a "nice to have". As for the altimeter setting - in UK we receive this verbally in hPa rather than inHg, so this is something that would be really advantageous to have a preference setting for, plus, some payware aircraft only provide a hPa subscale. Thanks Karl

Hi Dave, If flying patterns, it would be great to get the altimeter as QFE rather than QNH. As P2A knows the height of the airfield you're at, could a QFE reporting option (maybe a config checkbox) be added? Whilst I don't believe the sims report QFE, this could be derived: QNH + (aerodrome AMSL / 30). Additionally, the ability to report QNH/QFE in either hPa or inHg (maybe again with a checkbox option) would be great. Again if it's not presented directly by the sim, if memory serves me, it's 1 inHg = 33.8639 hPa. Thanks Karl

Thanks Dave, that would be great re information frequencies, thanks. Whilst locale specific changes are undoubtedly complex, is it something that might feature further down the product roadmap? I've also encountered quite a number of unhandled exception errors - some might be a result of user error, such as trying to save an unchanged frequency list, but I'm sure you'd still like to iron them out for user experience. How's best to report these to you? I'm conscious of creating too many bug threads on here!

Hi Dave, I'm currently evaluating P2A, and wanted to ask if there is scope to extend the comms patterns supported by P2A? At my local airfield, our comms sequence for circuits would be as follows: "Request -> Taxi": Me: "Barton Information G-XXXX parked east of the tower, information X, QFE 1018 for a circuit detail, 2 P.O.B" Info: "G-XX details correct, squawk 7365, cross runway 32 to holding point A3" Me: Squawk 7365. Cross runway 32 to holding point A3, G-XX" "Request -> Takeoff" Me: "G-XX ready for departure" Info a. "G-XX runway 26R. Take off at your discretion. Surface wind 260/10kts" -> "Taking off 26R, G-XX" OR Info b. "G-XX report lined up 26R" -> Me: "Report lined up 26R, G-XX" OR Info c: "G-XX hold position" -> Me: "Hold position, G-XX" "Report -> PatternLocation -> Downwind" Me: "G-XX downwind" Info: "G-XX Report final" Me: "Wilco, G-XX" "Report -> PatternLocation -> Final" Me: "G-XX final for touch and go" / "G-XX final for full stop landing" Info: <clearance & wind info> Me: "G-XX" - As explained by my instructor, the pilot's job is to get the plane down safely. On final at <500ft you've got to focus on your approach speed, carb heat, flaps, etc, so just repeating your callsign is enough. Additionally: At EGCB we use 120.25 (Barton Information), which is responsible for all of the above communications. However if I manually add 120.25 as an Information frequency, I'm presented with a limited set of dialogue. For instance I'm able to report my position within the circuit, but I'm not able to obtain any engine start, taxi, takeoff, or landing clearances. If I add it as a Twr frequency, it does allow those comms. Can the definition of Info frequencies be amended please? Thanks, Karl

Hi Dave, I'm currently evaluating the demo version and trying to get P2A working for my needs - predominantly VFR and Circuits/Patterns. I'm struggling to get started at my chosen airfield, EGCB: https://skyvector.com/airport/EGCB/Manchester-Barton-Airport The SkyVector link above shows EGCB's Information frequency, however this isn't listed in P2A. If would be great if P2A could obtain data from the installed scenery if possible (taxi routes, frequencies, etc), as this is already handled in an installed XP11 scenery pack. I added the Information frequency via Config->ATC Settings->Edit Controller Freqs, and restarted P2A to reveal the new frequency. I tuned to it but could not interact with it at all. So I added it again, this time as a Tower frequency, and it then allowed me to communicate. At EGCB, we use Barton Information for (amongst other things) all ground movements, T/O clearance, circuit reports, and landing clearance. Is this something that can be incorporated? Thanks Karl