Welcome to AirTrack 2.3

Apart from correcting several bugs and problems and no doubt introducing a few new ones, this new version introduces small improvements as a result of feedback and feature requests that we received from our users.

The following is a brief summary of the most important new features:

On the PFD:
###########

New glideslope and lateral deviation bugs are now available when an ILS or VOR frequency is dialed into NAV1 or NAV2, thus helping precision approaches with limited visibility.

Stall speed markers have been added to the speed tape representing Vso, Vs, Vno and Vne. (*)

Flight director bars have been added to the attitude indicator.

Notes:

(*) Speeds between Vso and Vs are extrapolated and hence, may not be exact as each aircraft is different. When flaps are deployed AirTrack will only show the maximum speed for the first level of deployment.

On the MFD:
###########

Some DME calculations have been improved. The DME distance is the slant range distance from where you are, at your current altitude, to the DME coordinates, at its elevation, and not the horizontal distance.

Note that AirTrack performs its own internal DME calculations concerning distances, which is why this works with any flight sim and even when used with the internal GPS. As a consequence the reported DME distances may differ from those observed in the simulator as different rouding and calculation methods are used. If you find incorrect measurements please let us know.

On the FMC:
###########

When used with an iPad in landscape orientation, the FMC's flight plan now shows the frequencies of VOR, NDB and ILS points.

Plus, both the tracked distance and average speed are now reset on take-off, making them more significant.

And last but not least, it is now possible to enter fixed degree coordinates as well as half-latitude ones as points of flight plans using the ARINC424 naming convention (e.g. 5040N, 75W20, E5275, 7S550). This makes it easier to create Oceanic / NAT based flight plans where the points are not always real intersections and hence don't exist in the FMC database as such. Ask us how if you need help with the encoding.

On the MCP and Radio stack:
######################

Some users reported that the method for changing frequencies or entering numbers in the MCP was a fiddle and they were right; it was impractical in that it took far too long to set a number in these. For this reason we are introducing a new simple digit dialpad as a replacement which should allow numbers and frequencies to be entered in a matter of seconds.

Other general changes:
######################

In addition to this the way to represent latitude and longitude coordinates was changed throughout AirTrack to degrees / minutes / seconds as opposed to the decimal format, making it easier and more suitable as coordinates are often published and reported in this way.

The X-Plane FMC database has also been updated to 1104 as this update was made available at http://data.x-plane.com/

And that is the gist of what's new in 2.3.

Enjoy the app, let us know your thoughts or problems you may find and stay tuned for the next update.