AirGuard reads your flight many times a second and hands back a complete, honest record of it. The layer above that — models that turn the record into a warning while you are still in the air — is what we are building now, and this page is explicit about which is which.
The device only helps if the numbers are right. Everything above this layer depends on clean, continuous, time-aligned data.
GPS track and accelerometer data through the jump, not just a start and end point.
Altitude, freefall speed and descent profile from fused barometric and motion sensing.
Recording runs on the device from power-on to landing, so a gap in coverage is not a gap in the record.
Every channel is stamped against one clock, which is what makes the streams comparable later instead of merely adjacent.
What is waiting for you in the hour after you land, and what it took to record it properly.
Pairing, device configuration and post-jump review on iOS and Android, over Bluetooth.
Every descent recorded automatically, ready to annotate rather than reconstruct from memory.
Altitude, speed and track plotted against each other, so a jump can be examined rather than just remembered.
The record belongs to the person who made it. Nothing is published, sold or shared on your behalf.
Mount the device and pair it with the app before you board.
Position, altitude and speed captured continuously, on the device.
The descent is already recorded — nothing to start, stop or remember.
The full jump waiting in the app, ready to annotate and keep.
Every board is probed on the bench before it ever sees a jump: rails measured, sensor timing captured on the scope, firmware stepped through under the microscope. Nothing about the sensing stack is taken on trust from a datasheet.
Everything below is under active development and none of it ships in AirGuard today. We would rather you knew that from us than found it out from the device. Each item is here because the sensing layer above was built to carry it.
Wind speed and temperature recorded as you met them, alongside the flight data, so conditions can be read back against the descent.
Patterns across motion, flight and conditions evaluated together rather than one threshold at a time, running on the wearable so a decision does not wait for coverage.
Warnings raised before a limit is crossed, tuned so they stay rare enough to be believed. Rare is the hard part, and it is why this is not shipping yet.
Critical events notifying the contacts you nominate, with position and the conditions the device recorded.
A support team following the descent as it happens instead of waiting on a radio call. Needs a radio the current unit does not carry.
Predictions refined as jump data accumulates — which needs devices in the field first, and the consent of the people wearing them.