Hello Peter,
During flight press the SkyDemon orb to bring up the main menu, then press Radio. That is the Radio screen.

Hi Tim

Sorry to chip in on this again. It's all very well to say that access to 'Listening Squawks' is available via the 'Radio Screen' – so are airfield radio services (obviously), but if you are not prepared to add 'Listening Squawks' to airfield information when the 'What's Here' menu is invoked, what was your rationale for including airfield radio services in the first place? What's the point of having airfield radio services available nested under the 'What's Here' menu, if I have to then invoke the 'Radio Screen' to get at the 'Listening Squawk'? Since you've made the decision to include radio services nested under the 'What's Here' menu (a decision which I applaud by the way), I cannot understand why you are so reluctant to include 'Listening Squawks' for those airports that provide them, especially since 'Listening Squawks' are inextricably linked to radio services anyway.

Mike
_________________________________________

Listening Squawks are encoded as big chunks of airspace in our data, because they have geographical limits. Frequencies, on the other hand, are just bits of data associated with an airfield. Going from an airfield to a corresponding listening squawk is not straightforward.

If someone is flying in a new area, how are they supposed to know which airfield(s) nearby offer a listening squawk? Open the What's Here menu for every airfield onscreen until they find one that has one? That would be ridiculous. Opening the Radio screen tells you exactly which listening squawks are available at your current position.

Ah! I understand now, and what you say makes perfect sense. Not being a programmer, I imagined that a listening squawk was like a radio frequency – 'just a bit of data associated with an airfield.'

However, if I bring up the 'What's Here' menu, and I do so for a specific airport, as opposed to 'a chunk of airspace,' would that still preclude the listening squawk for that airport from being included along with radio services, because at that point, I am looking only at data specific to that airport?

Mike
_________________________________________

Thanks Tim, I hadn't thought to look there.

Thanks again for your help

Peter

It's technically tricky (and slightly undesirable) for us to create a bridge between the screen that inspects an airfield, and all the airspace data which is located in a different part of the software. Listening Squawks are airspace data because they have geographical boundaries. I appreciate that the requirement is there though and that it is a legitimate (if very specific) requirement, so will give it some thought.

Many thanks Tim.

Mike
_________________________________________

Just a thought - but for some of this data (such as LARS areas, listening squawk areas, etc) it would be useful to be able to display it on the map during flight planning.  Not to show it all the time, as that would be very cluttered, but the ability to overlay LARS in a similar way that e.g. NOTAMS are shown would help visualise the areas that they cover.

I know I can preview the PLog which shows me all the frequencies I might need ..... but when I'm mentally going through the route before I fly it is nice to be able to plan for who I'm going to be talking to and when, and also given many LARS are only Mon - Fri, know what alternative units might provide a service.  That also gave me an idea, could you annotate on the Plog and Radio screen those radio services not normally active at the planned/current time (not sure if the data is available for that)??