# \[Release\] VFRnav 4.21 **URL:** \ **Category:** Updates & Releases\ **Created:** [December 15, 2025, 6:13pm UTC](https://forum.vfrnav.com/t/release-vfrnav-4-21/164 "2025-12-15T18:13:25Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![H655](https://forum.vfrnav.com/user_avatar/forum.vfrnav.com/h655/32/350_2.png) [@H655](https://forum.vfrnav.com/u/H655)\ **Post date:** [December 15, 2025, 6:13pm UTC](https://forum.vfrnav.com/t/release-vfrnav-4-21/164/1 "2025-12-15T18:13:26Z")
**VFRnav 4.21** adds several new configuration options and further improves the map display to support efficient and safe navigation. #### ✨ What’s New - **New:** A **dedicated overview of recent changes and new features** is now available directly in the **settings** , so you can quickly review what’s new in VFRnav - **New:** Option to enable a **coordinate grid** on the map via the settings - **New:** In addition to the existing **time-based course line** , you can now display a **distance ring** around your current position ([see forum topic](https://forum.vfrnav.com/t/featurerequest-erweiterung-einheit-fur-kurslinie-anpassen/162)). The distance can be configured in the settings. You can choose between a **full circle** or a **forward arc** representation * * * In addition to the changes listed above, we have continued to refine the **map style** to make it as **productive and safe as possible** during flight. As always, we look forward to your feedback and suggestions — feel free to contact us by **email** or here in the **forum**. ✈ ---
**Author:** ![KBfly](https://forum.vfrnav.com/user_avatar/forum.vfrnav.com/kbfly/32/28_2.png) [@KBfly](https://forum.vfrnav.com/u/KBfly)\ **Post date:** [December 15, 2025, 8:04pm UTC](https://forum.vfrnav.com/t/release-vfrnav-4-21/164/2 "2025-12-15T20:04:04Z")
👏👏👏👍👍👍…that should say it all. Many thanks, Hermann ---
**Author:** ![SonjaG](https://forum.vfrnav.com/letter_avatar_proxy/v4/letter/s/b5a626/32.png) [@SonjaG](https://forum.vfrnav.com/u/SonjaG)\ **Post date:** [December 16, 2025, 6:28pm UTC](https://forum.vfrnav.com/t/release-vfrnav-4-21/164/3 "2025-12-16T18:28:59Z")
Thanks from me too 😀 ---
**Author:** ![Andreas](https://forum.vfrnav.com/user_avatar/forum.vfrnav.com/andreas/32/84_2.png) [@Andreas](https://forum.vfrnav.com/u/Andreas)\ **Post date:** [December 18, 2025, 6:48am UTC](https://forum.vfrnav.com/t/release-vfrnav-4-21/164/4 "2025-12-18T06:48:20Z")
Good morning, the app keeps getting better. Recently, in addition to my Android smartphone, I also use an iPad mini 7. There, unfortunately the zoom function enlarges the map, but the text for locations, airfields and airspaces remains small and is very difficult to read in the cockpit. Perhaps this could be addressed in future so that the labels scale up as well? Regards ---
**Author:** ![Maurer](https://forum.vfrnav.com/user_avatar/forum.vfrnav.com/maurer/32/63_2.png) [@Maurer](https://forum.vfrnav.com/u/Maurer)\ **Post date:** [December 18, 2025, 6:48am UTC](https://forum.vfrnav.com/t/release-vfrnav-4-21/164/5 "2025-12-18T06:48:58Z")
Good morning everyone, What was fixed in update 4.21.2? Regards Stefan ---
**Author:** ![H655](https://forum.vfrnav.com/user_avatar/forum.vfrnav.com/h655/32/350_2.png) [@H655](https://forum.vfrnav.com/u/H655)\ **Post date:** [December 18, 2025, 8:44am UTC](https://forum.vfrnav.com/t/release-vfrnav-4-21/164/6 "2025-12-18T08:44:33Z")
> [@Andreas](#): > > There the zoom function is unfortunately such that, while the map is enlarged, the lettering of the places, airfields and also airspaces remains small and in the cockpit is very hard to read. Hello Andreas, could you take screenshots for comparison? Does the zoom behave differently on the iOS device than on the Android device? > [@Maurer](#): > > What was fixed in update 4.21.2? Hello Stefan, the Z updates (X.Y.Z version scheme) include small bug fixes that in most cases are device-specific. Normally we do not document these publicly. In this case, on some devices the phenomenon occurred that the Airtime info field did not jump back to the current time after landing. That was fixed in 4.21.2. Pilot’s regards (Fliegergruß) Hermann ---
**Author:** ![Andi-Link](https://forum.vfrnav.com/user_avatar/forum.vfrnav.com/andi-link/32/67_2.png) [@Andi-Link](https://forum.vfrnav.com/u/Andi-Link)\ **Post date:** [January 8, 2026, 7:36pm UTC](https://forum.vfrnav.com/t/release-vfrnav-4-21/164/7 "2026-01-08T19:36:42Z")
Simply, thanks !!! 😀 … for your (sing.) / your (pl.) constant dedication & efforts etc… … all the best .. Ahoy ---
**Author:** ![Maurer](https://forum.vfrnav.com/user_avatar/forum.vfrnav.com/maurer/32/63_2.png) [@Maurer](https://forum.vfrnav.com/u/Maurer)\ **Post date:** [January 16, 2026, 9:57am UTC](https://forum.vfrnav.com/t/release-vfrnav-4-21/164/8 "2026-01-16T09:57:18Z")
Hello Hermann, thanks for the info, even though you don’t normally publish it. As a bit of a nerd, I’m also interested in the minor changes and bug fixes, because from them I can sometimes tell whether a bug/phenomenon affecting me has been fixed or not. Thanks for your great work and happy flying Stefan ---
**Author:** ![H655](https://forum.vfrnav.com/user_avatar/forum.vfrnav.com/h655/32/350_2.png) [@H655](https://forum.vfrnav.com/u/H655)\ **Post date:** [January 20, 2026, 7:57am UTC](https://forum.vfrnav.com/t/release-vfrnav-4-21/164/9 "2026-01-20T07:57:29Z")
> [@Maurer](#): > > whether an error/phenomenon has been fixed for me or not yet. If you find any errors, feel free to post a short message here. If obvious bugs are still reproducible after a new release, I won’t be upset by a brief reminder. To be honest: our internal bug tracker is not always compatible with agile development and things can sometimes slip through. 🫣 Happy flying Hermann