Horizon
A compact vario and flight-awareness instrument built around calm audio, a portrait pilot display and glove-friendly physical controls.
Horizon is a compact, dedicated flight instrument for paragliding pilots—built around calm audio, glanceable information, physical controls, and honest field testing.
The product family grows from a compact, focused instrument toward traffic awareness and larger map-based navigation—without turning every model into the same device.
A compact vario and flight-awareness instrument built around calm audio, a portrait pilot display and glove-friendly physical controls.
The same locked Horizon format, extended with XC communication and traffic awareness for pilots flying farther and in busier shared airspace.
A minimal displayless vario with no microphones. The VIRON companion app provides its visual interface.
The largest and most fully equipped VIRON instrument, with maps, microphones and the broadest navigation and air-awareness feature set.
The goal is not to place every possible number on a small screen. Horizon should make the information that matters easier to notice, understand, and act on.
High-contrast information, tactile controls and deliberate audio behaviour are being developed together as one cockpit experience. The instrument should support the pilot’s attention—not compete for it.
Vario behaviour and alerts designed to inform without creating unnecessary urgency.
A portrait display with clear hierarchy and large, pilot-readable values.
Four tactile controls for predictable operation with gloves and in moving air.
Local blackbox logging for testing, replay, diagnostics and post-flight understanding.
Horizon is being designed as a complete loop rather than a loose collection of sensors and screens.
Barometric pressure, GNSS and motion sensing provide the prototype’s primary flight inputs.
Filtering and state logic turn raw sensor data into more stable, useful behaviour.
Audio carries continuous information while the display supports quick visual confirmation.
Blackbox data supports debugging, replay and transparent product validation.
This is the factual engineering snapshot. Everything above explains the products; everything here records what has actually happened and what comes next.
Updates remain available for readers who want the engineering detail, without spreading build status across the rest of the page.
The exterior shown above is now the selected product look for both Horizon and Horizon XC: a 3.5-inch portrait display, four physical side controls and the same compact visual identity.
“Look locked” describes the product appearance. Internal packaging, fit tolerances, manufacturing details and validation may still be refined before production.
Movement testing activated live GNSS position transmission from Horizon to the XC module. Forty-four fresh #FNS messages were transmitted and acknowledged, with no write failures or stale-position sends after movement stopped.
This proves the operational wired communication path. Live over-the-air traffic detection has not yet been demonstrated and remains the next major XC test.
The first successful image has been produced on the new 3.5-inch display using real Horizon hardware.
The electrical bring-up milestone is complete. Full driver integration, correct resolution and interface optimisation continue before display validation is finished.
The first batch contains five assembled four-layer Horizon PCBs. They power up, accept firmware and run the development display.
These are engineering units, not sale units. Deeper validation of charging, sensors, GNSS, audio, storage, Bluetooth, controls and endurance continues before enclosure and flight testing.
The companion experience now goes beyond a device status screen. A repeatable simulation layer can drive the same telemetry pipeline used by the real instrument.
That creates a safer place to test flight states, alerts, maps and interface decisions before taking changes into real air.
The first assembled units will go to selected pilots who can explain what happened in flight and separate personal preference from a repeatable usability issue.
Ground checks, independent backup instruments, defined scenarios and post-flight logs will be part of the testing process.
The companion experience uses the same telemetry path as Horizon and adds a deterministic flight simulation environment. That allows interface, audio and flight-state behaviour to be explored before every change is taken into real air.
The first units will go to selected pilots who can test honestly, explain what happened in flight, and help distinguish personal preference from a real usability problem.
Every test unit will be treated as development hardware. Horizon will not replace certified flight, navigation or traffic equipment.
Only assembled units that pass the relevant bench, power and interface checks move toward field evaluation.
Readability, button use, audio levels, mounting and workflow tested without adding flight risk.
Defined scenarios, independent backup instruments and structured post-flight reports.
Logs, faults and pilot observations become design decisions, not promotional quotes by default.
“The useful story is not that a pilot wanted to build a device. It is whether the device makes flying calmer, clearer and more understandable.”
VIRON Labs is an independent development-stage hardware project from Slovenia. Horizon is being built from real paragliding experience, embedded engineering and a commitment to earn every product claim through testing.
We are building a small, controlled group of pilots interested in development updates, critical feedback and—when the hardware is ready—structured prototype testing.
Joining the list is not a preorder and does not guarantee a test unit, commercial availability or a delivery date.