New features:

• Tap to Fly 2D

  In the 2D map view, you can tap anywhere on the map to send the BLK2FLY to that location.

  After tapping on the 2D map, you can select the target altitude for the destination using the slider on the left side and then choose to confirm or cancel the mission.

   

   

  This feature requires a valid GNSS signal and is therefore unavailable indoors. When flying indoors, the button to confirm the destination is disabled and appears greyed out.

• Automatic Landing Zone Evaluation

Whenever a landing is ongoing (whether during a normal Land in place, the final vertical landing phase of a Return to launch, or an Emergency landing) BLK2FLY evaluates the landing zone beneath it to ensure that it is flat and free of obstacles. In the BLK2FLY Live app, a suitable landing zone is visualized with an H and a green circle. An unsuitable landing zone is indicated with an H and a red circle.

 

If the landing zone is detected as suitable (green circle), BLK2FLY proceeds with the landing.

If the landing zone is detected as non suitable (red circle), for instance due to uneven ground or an obstacle, BLK2FLY either initiates an automatic rerouting process to nearby suitable landing spot, or if rerouting is disabled in the settings, hover and request user confirmation to land in place via a pop-up.

 

Landing Zone Rerouting Enabled (default setting)

If Landing Zone Rerouting is enabled and BLK2FLY detects a non-suitable landing zone beneath it, BLK2FLY hovers and automatically searches for an alternative landing spot within a 6-meter radius. When a suitable landing spot is found, the BLK2FLY Live app highlights the new landing location (green circle). It provides the user with time to cancel the rerouting by pressing the x-button next to the new landing spot visualisation:

• • 10 s for normal landing phases
  • 5 s for emergency landings

 

If the operator does not cancel at this stage, BLK2FLY moves horizontally to the new alternative landing spot using obstacle avoidance. Once BLK2FLY reaches the spot, it initiates a new landing process and continues evaluating whether the area beneath is safe.

If the newly selected landing location is also determined to be unsafe for any reason, BLK2FLY behaves differently depending on the landing mode:

• • Normal landing: BLK2FLY hovers and the user is prompted via a pop-up alert to either continue descending or abort the operation.
  • Emergency landing: BLK2FLY continues descending and completes the landing procedure without performing any further landing spot evaluation or rerouting.

Note:

The automatic landing zone evaluation is a supportive safety feature designed to reduce the likelihood of damage caused by landing on unsuitable surfaces. However, it remains the responsibility of the operator to abort the process and take manual control to ensure a safe landing if the system evaluates the landing zone incorrectly or behaves unexpectedly or in an unsafe manner.

The landing process and any rerouting can be aborted at any time by pressing the large X-button. In this case, BLK2FLY hovers and waits for further instructions.

During landing, including during nudging, obstacle avoidance is always disabled. The automatic landing zone evaluation assesses only the area directly beneath BLK2FLY.

The automatic landing zone evaluation and rerouting functionality is disabled in degraded flight conditions, for instance loss of position control or missing LiDAR data.

• SSO Login for Hexagon GeoCloud

Note: The former Reality Cloud Studio (RCS) was/will be replaced by Hexagon GeoCloud in Q2 2026. Login credentials and access remain unchanged.

Hexagon GeoCloud now supports Single Sign-On (SSO), and the BLK2FLY Live app has been updated to integrate this new authentication method. A new “Log In with SSO” button has been added to the Profile screen.

When selected, users are prompted to enter their email address. After tapping “Log In”, a browser window opens where the user completes the SSO authentication workflow.

• Minimum altitude limit

To prevent the BLK2FLY from descending below a defined minimum altitude (particularly over water, where obstacle-avoidance performance is limited) the BLK2FLY now supports a configurable minimum altitude limit (relative to the take-off point). Users can set this lower-altitude boundary directly in the app, ensuring that the drone cannot descend below the defined threshold during both manual and autonomous flight.

When the minimum altitude limit is reached during flight, the user is notified with an on-screen notification.

An active minimum altitude limit prevents the drone from flying below this limit during both manual and autonomous missions and is independent of whether obstacle avoidance is enabled or not. However, it can always be breached by landing or disabled in the settings.

If the minimum altitude is adjusted during flight to a new value that is higher than the drone’s current altitude, or if a landing is aborted below the minimum altitude limit, the BLK2FLY will not be allowed to descend any further and can only fly sideways or ascend.

Improvements / Fixes:

• Joystick improvements
  Improved joystick input: Delivering smoother, more predictable straight-line flight.
• GNSS Firmware update
  The firmware on the GNSS u-blox module has been updated to a more recent release and re-tuned. This upgrade addresses a known issue that could cause occasional drops in the reported number of satellites. With the new updates, this problem has been resolved.
• Exploratory scanning improvement
  During exploration missions, the BLK2FLY now follows a smoother, more continuous path throughout the entire flight, reducing direction changes or discontinuities in the map.
• Online Airspace Restrictions Service discontinued
  The online airspace-restriction service in the BLK2FLY Live App has been removed due to the provider’s discontinuation of the service. The option to load geozones from custom files remains available as before and should be used by users (authorities/countries usually provide these files). The existing notification system is still in place; however, it now checks only for geozones loaded from custom files. We also recommend that users rely on third-party applications for evaluating and monitoring flight restrictions.
• Project Browsing
  Improved project browser stability and responsiveness, including smoother tab switching and more reliable reload behavior. Minor UI issues in the project browser have been fixed for a cleaner and more consistent user experience.
• Download Raw Sensor Data in human readable format
  It is now possible to download sensor data stored in the BLK2FLY log files directly from the app. In the Support section, users will find a new page dedicated to Sensor Data Download.

 

After selecting the desired log file, the user can choose Download. The logs are converted into CSV format, packaged into a single zipped file, and downloaded to the iPad. Users can also choose the storage location and assign a custom name to the downloaded file.

• Possibility to update the Access Point Password
  Users can now set a new Access Point password for the BLK2FLY using the app (the default password is printed on the device label). The new password must have at least 10 characters and include at least one letter and one number. After the password is updated, the BLK2FLY will automatically turn off, and the user will need to pair the device again. If the password gets lost, a new one can be set through an already paired app. Performing a factory reset will restore the password to the default value printed on the label.

• Changes in the digital interface
  Various updates have been implemented to enhance the device’s cybersecurity. These changes require users to run the latest version of both the app and the device firmware; otherwise, the connection will be blocked.
• Battery diagnostic improvements
  Users will receive an error notification, and take-off will be prevented if the battery is in a degraded state.