# Aerotracker software version

**URL:** <https://forum.safesky.app/t/aerotracker-software-version/2081>\
**Category:** English\
**Created:** [July 19, 2025, 8:53pm UTC](https://forum.safesky.app/t/aerotracker-software-version/2081 "2025-07-19T20:53:24Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![McPike](https://avatars.discourse-cdn.com/v4/letter/m/ea666f/32.png) [@McPike](https://forum.safesky.app/u/McPike)\
**Post date:** [July 19, 2025, 8:53pm UTC](https://forum.safesky.app/t/aerotracker-software-version/2081/1 "2025-07-19T20:53:24Z")

</div>

Hi, I would like to learn what the current (latest) software version is for the Aerotracker. I have 1.0.6, however in the documentation I can see higher version numbers. Thanks!

---

<div class="post-metadata">

**Author:** ![tnowak](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.safesky.app/tnowak/32/351_2.png) [@tnowak](https://forum.safesky.app/u/tnowak)\
**Post date:** [July 24, 2025, 6:05am UTC](https://forum.safesky.app/t/aerotracker-software-version/2081/2 "2025-07-24T06:05:32Z")

</div>

Hello, I believe that version 1.0.6 is the latest “public” version available. Testing is currently underway on a new version, but I am not sure when it will be released.

---

<div class="post-metadata">

**Author:** ![Smurf](https://avatars.discourse-cdn.com/v4/letter/s/ee59a6/32.png) [@Smurf](https://forum.safesky.app/u/Smurf)\
**Post date:** [July 31, 2025, 1:07pm UTC](https://forum.safesky.app/t/aerotracker-software-version/2081/3 "2025-07-31T13:07:43Z")

</div>

I got the info that they are working on a version that will display relative altitude and distance (no bearing) of Mode-S traffic that should be released soon. Definitely interesting!

---

<div class="post-metadata">

**Author:** ![tnowak](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.safesky.app/tnowak/32/351_2.png) [@tnowak](https://forum.safesky.app/u/tnowak)\
**Post date:** [August 1, 2025, 7:01am UTC](https://forum.safesky.app/t/aerotracker-software-version/2081/4 "2025-08-01T07:01:29Z")

</div>

Yes, the software/firmware is being tested now. Distance to the conflicting aircraft will always be estimated, and is based on received signal strength.

---

<div class="post-metadata">

**Author:** ![McPike](https://avatars.discourse-cdn.com/v4/letter/m/ea666f/32.png) [@McPike](https://forum.safesky.app/u/McPike)\
**Post date:** [August 14, 2025, 8:31am UTC](https://forum.safesky.app/t/aerotracker-software-version/2081/5 "2025-08-14T08:31:24Z")

</div>

> I made some flights with the new software version and indeed Mode-S traffic is displayed as a circle with a relative height indication. This seems to work well. My only feedback is that 10NM (I could verify the actual position on Safesky ipad split screen) seems too much for a warning. I would suggest to reduce that to 5 NM. Now there are quite a few aircraft displayed that can never be a factor and it triggers unnecessary tension.

---

<div class="post-metadata">

**Author:** ![tnowak](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.safesky.app/tnowak/32/351_2.png) [@tnowak](https://forum.safesky.app/u/tnowak)\
**Post date:** [August 14, 2025, 4:14pm UTC](https://forum.safesky.app/t/aerotracker-software-version/2081/6 "2025-08-14T16:14:05Z")

</div>

I am testing the Aero Tracker with SkyDemon. I have noticed many more Mode S only aircraft (in my vicinity, while flying) than expected. Post flight checks showed that they were MLAT detected on ADS-B Exchange, so should have been displayed as MLAT and not Mode S only. The SafeSky team is aware so, hopefully, a fix will be out soon.

10 NM range alerts do seem a bit excessive..

---

<div class="post-metadata">

**Author:** ![Tristan](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.safesky.app/tristan/32/10_2.png) [@Tristan](https://forum.safesky.app/u/Tristan)\
**Post date:** [August 21, 2025, 8:43am UTC](https://forum.safesky.app/t/aerotracker-software-version/2081/7 "2025-08-21T08:43:20Z")

</div>

The latest firmware version is indeed automaticly updating your Aero-tracker to trigger alerts for Mode-S (bearingless) targets.

More details here: [2 - What traffic will ... | SafeSky Library](https://docs.safesky.app/link/122#bkmrk-%F0%9F%93%A1-mode-s-traffic-rec)

---

<div class="post-metadata">

**Author:** ![Tristan](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.safesky.app/tristan/32/10_2.png) [@Tristan](https://forum.safesky.app/u/Tristan)\
**Post date:** [August 21, 2025, 8:45am UTC](https://forum.safesky.app/t/aerotracker-software-version/2081/8 "2025-08-21T08:45:17Z")

</div>

It’s a very good feedback: open question to participants: shall we either decide of a low 5NM value for beardless targets to avoid too many alerts, or should this be a configurable option?

---

<div class="post-metadata">

**Author:** ![McPike](https://avatars.discourse-cdn.com/v4/letter/m/ea666f/32.png) [@McPike](https://forum.safesky.app/u/McPike)\
**Post date:** [August 21, 2025, 1:15pm UTC](https://forum.safesky.app/t/aerotracker-software-version/2081/9 "2025-08-21T13:15:39Z")

</div>

Hi Tristan, indeed 5NM seems more than enough. Anything beyond 2NM is usually not visible anyway, unless it is a B747. A larger distance produces a lot of circles on the map.
