BLS uses Beyond ATC logs to keep a record of all interactions between you and the tower and all frequencies used.

It might encourage beginners to try out phraseology used by the automatic copilot.

It aims to help anyone interested in analysing a flight, particularly when there is an issue you may want to report,ie

vectoring or a choice of runway.

It also hopes to address some of the questions raised in the forum:

How can I check the metar changes throughout the flight?
How can I track the vectoring logic?
How can I highlight any speech which ATC failed to understand?

Note

ALWAYS RUN AS ADMINISTRATOR

Where are BATC logs ? 

BLS automatically locates the logs for you;they are always kept in:

:\users\\AppData\LocalLow\Skirmish Mode Games, Inc\BeyondATC\player.log

Note:

some log files contain no interaction between pilot and ATC; this happens when an error in BATC has occurred.

Player.log is contains information about your last flight . When you start BATC this file gets wiped and replaced

Player-prev.og covers the previous flight. BATC always overwrites logs unlike FSLTL.

BLS gives you the option to copy and rename your logs so they don't get overwritten by BATC.

What does it do?

Supports latest CPDLC features and includes additional comments when sending message was unsuccessful.

There are several 'options'

BATC 

The BATC tab attempts to provide a look,similar to Beyond ATC. However, it includes new icons representing a change of frequency or metar data.
Metar data shows the reason why a certain runway has been selected - often ignoring local knowledge.

In addition, a new icon has been used when you as a pilot take over from the copilot.

Analysis

It analyses pilot's communications logged by BATC using various colours - this option can be disabled.

ATC : YELLOW

ATC not understanding response : ORANGE

ATC Warning : RED

Pilot's response: PURPLE

Automatic Pilot's response : CYAN

The more confident you are communicating with ATC , the more purple you will see.

When Speech recognition fails

The Issues tab shows where speech recognition fails and helps you diagnose why ATC failed to understand what you said. 
For example , cases where 'nine' and/or 'niner' are not understood in frequencies or callsigns.
cases where '2' is transcribed as 'to' again when repeating frequencies and or callsigns.
when a pilot's phrase has not been added to ATC's idiom.

When the text is in CYAN, the issue is a bug worth submitting to BATC.

ATC tab

Here all ATC conversations are listed and colour coded according to the various stages of a flight ie

departure, cruise, descent,arrival and landing

There are still cases when ATC unexpectedly speaks with a non regional accent; ie Dutch for Manchester Radar . 

Click this tab to check out languages

Traffic

Traffic is show as a separate tag. Recently logs do not contain information regarding types of aircraft and flightnumbers. Initially, logs did contain such info shown in BLS.

What else does it do?

Show ATIS being updated in mid-flight.

Print out communication

Export communication as a txt file

Search 

Copy & rename logs 

Show SimBrief flightplan

(Loss of) Frequencies

Frequencies are included so possible issues are quickly identified. 

When BATC fails to connect to the flight simulator in mid stream it is important to note your current frequency else BATC looks blank when you restart in 'cruise' mode.
 You can obtain such data by loading the Player-prev log - File , Open Own Logs,Player-prev.log

Coming Next

GSX  

Show any GSX information included in a log.
List All your GSX profiles and all parking facilities includig parkingsystems

More Info

https://www.pinns.co.uk/osm/batc.html

New Version:

Complete overhaul of mapping tab with maps that can be dragged etc.