Pilot Beta Programme
We are building the world's first internal wing pressure dataset. Fifty pilots fly with the instrument. Here is what that involves.
Real-time pressure across four points inside the canopy, while you fly.
Apply for the Pilot BetaAfter every flight
This lands in your logbook, for every flight you fly.
Not a track and a duration. Your whole day, read back to you — where the air was working, every climb you found, and the wind at each height you flew through.
Every figure above comes from real beta flights. Our evidence base is still small, and we say so. Satellite imagery © Esri, Maxar.
Pricing
What it costs.
One payment of £199 including VAT — £165.83 plus VAT at 20 per cent. The unit is yours the day it reaches you. There are no hours to fly off, no balance to clear and nothing you owe us afterwards. This is a subsidised price for a capped first cohort. We are not crossing out a higher number next to it: we have never sold a ParaBaro at a market price, so any number we crossed out would be one we had invented.
What the £199 covers, and what it does not:
| What you get | A ParaBaro receiver and four wing sensor modules, shipped to you. |
| When it is yours | On delivery. Title passes when the unit reaches you, and it does not depend on anything you do afterwards. |
| What you owe after that | Nothing. No hours, no uploads, no balance, no subscription. If you never send us a flight you still own the unit. |
| How a place is decided | On your application, before you are asked to pay. The cohort is capped and we read every application. |
| Why it is this price | It is subsidised. We want the recordings more than we want the margin, and we would rather say that than dress it up as a discount. |
Sending us your flights is a separate, optional thing — it is the contributor programme, and nothing you own depends on it. Full terms — delivery, warranty, data rights — are on the beta rules.
The arrangement
What the beta involves.
The beta runs on a simple arrangement. You fly with a ParaBaro sensor on your wing. We share the pressure data with you. You tell us what you felt in the cockpit. The instrument logs; the debrief is the conversation between what the wing was doing and what you were feeling.
Pressure data on your own wing.
Every flight, logged across four internal channels. After each block, we share the traces with you.
Firmware updates throughout.
You receive every firmware release during the programme, including features developed in response to pilot feedback.
A direct line to the team.
This is a 50-pilot cohort. When you have a question or find something odd in the data, you reach the team directly — not a support queue.
What we are asking for
What we are asking for.
The programme produces useful data when pilots fly their normal routines, not staged ones. What we need is straightforward.
Flight hours with the device. You fly as you normally fly. The sensor modules fit to your wing before you go up and can stay in place between flights. Each module weighs approximately 20 grams; the four modules add approximately 80 grams, split between two points on the wing. The sensors are designed to minimise aerodynamic and handling effects, and the system has been flown across multiple EN classes during development without pilots reporting a noticeable change in handling. No modifications to the wing are made.
Paired IGC and CSV files uploaded after each flight. The IGC file is what your GPS logger already records. The CSV is what ParaBaro generates. Together they give us pressure traces with positional context — the thing that has not existed before.
A short debrief per block. Not every flight. A debrief when we review a block of flights together — roughly every four to six weeks. You tell us what you noticed. We show you what the instrument recorded. That conversation is where the data gets better.
Feedback when something does not work. Firmware issues, connectivity problems, data gaps. You report what you find; we fix it.
ParaBaro is a supplementary awareness tool, not a safety device. Flying with it does not change how you fly. It records.
The process
What happens after you apply.
You submit the application. You will see a confirmation on this page immediately and receive an email from us within a few minutes. If you do not receive the email, check your spam folder and write to info@aviometrics.com.
We read your application personally. We review every application by hand — the scoring we use internally is for prioritisation, not for automated rejection. Within 7 days from submission, you will receive a direct reply, even if the decision is not yet final.
You hear whether you are in. Within 14 days from submission at the latest, we will tell you clearly: you are in, you are on the reserve list, or we cannot include you in this cohort. If we cannot include you, we will say why and, where we can, point you to what would change that.
If you are in: we agree a ship date for your sensor, sort out the payment, and you receive a device setup guide and a brief call with the team before your first flight with it.
If you are not in this cohort: your application stays on file for the next cohort. We will write to you when the next wave opens, before it is announced publicly.
Apply now
Apply for the Pilot Beta.
We ask you to register before submitting because your application is linked to your flight data from day one. That is a mechanical detail of how the platform works; it is not a commitment to send us anything.
Common questions
Frequently asked questions.
If you are a wing manufacturer or test partner looking for the Validation Programme, that information is on the Partnerships page. The methodology behind the measurement is on /research.