PA-46 beta testing program

Avionvera

Know your aircraft. Trust the data. Running on your own Mac.

Avionvera is a local flight-record analysis app being built for general aviation, piston and turbine, starting with the Piper PA-46 family. Recordings in supported formats can be imported and reviewed; the measurements available depend on the recorder and format. Numeric engine and technique scores are currently available only for the 1989–2015 PA-46-350P Malibu Mirage with a JPI EDM-930. Other configurations do not receive a numeric score. Some recorder formats cannot be read today. It tracks trends against your own history and turns the evidence into maintenance observations and reports. Your archive is analyzed and stored on your Mac.

We are looking for a small number of volunteer PA-46 pilots, piston and turbine, to help us test how well the importer handles real-world files from different engine monitors, avionics, and export workflows.

Join the PA-46 beta

Where testing stands today

Numeric scores are currently available for one configuration:

PA-46-350P Malibu Mirage with the Lycoming TIO-540-AE2A engine and a JPI EDM-930 engine monitor.

Support for the rest of the PA-46 family is being developed, and this round is about whether your files import cleanly across aircraft installations, recorder formats and export workflows. Every PA-46 is welcome:

  • Mirage, Matrix, and M350 share the TIO-540-AE2A; each needs its own documentation, applicability and real-recording checks before scoring is enabled.
  • Malibu 310P with the Continental TSIO-520-BE: supported recordings can be reviewed without scoring; its own scoring limits come later, once checked against real data.
  • Meridian, M500, M600, M700, and JetPROP conversions are welcome too. Turbine engine analysis is still being designed, so there is no scoring yet, and some turbine recorder formats cannot be read today. Those files are exactly what we need to build it, so please join.

What it looks like

These screenshots use a demo record: a fictional aircraft, generated flights and a made-up logbook page. Your own recordings and logbooks turn into the same views once they import.

Avionvera summary for a demo aircraft: a warning on the latest flight, an open investigation into a drifting cylinder head temperature, a logbook reading with one record waiting, and a scorecard of the last ten flights
Summary. What deserves a look across every flight on file: warnings, open investigations with their evidence, logbook records waiting for you, and a rolling scorecard.
A single demo flight from Greenville-Spartanburg to DeKalb-Peachtree: hottest cylinder head temperature, TIT, oil and fuel figures, and the route on a map
One flight. The route on a map and the flight’s engine figures, with the hottest cylinder called out.
Aircraft-health and pilot-technique findings for one demo flight, showing cylinder 3 at 438 °F and a 78 °F cylinder-temperature spread
Plain-language findings. Each finding shows the numbers behind it, split into aircraft health and pilot technique. Here cylinder 3 runs hot and the cylinder temperature spread is flagged.
Logbook review: a fictional scanned logbook page beside the records read from it, one imported and one asking whether a date written day-first was read correctly
Logbook pages, checked against the page. Scanned logbook pages are read into maintenance records shown beside the page. Anything uncertain, like a date written day-first, waits for your answer.

What this first step involves

We ask for

  • Your name and email address
  • Your PA-46 model or variant and engine
  • Your engine-monitor model and avionics
  • Which file types you can export
  • Optional notes on how you get files off the airplane

Please do not send

  • Logbooks or maintenance documents
  • Passwords, account credentials, or API keys
  • Garmin-account or flyGarmin exports
  • Raw flight files of any kind

This form collects interest and equipment details only. We will need a real file from your setup later on; when we do, we will ask you and arrange a private transfer.

Join the PA-46 beta

Your answers go straight to our support mailbox as a single plain-text email. There is nowhere on this form to attach a file, on purpose.

Thanks, you are on the list

We have your details and will be in touch by email. Please do not send any files until we ask.

We send your TestFlight link and how to get started to this address.

For example PA-46-310P Malibu, PA-46-350P Mirage, M350, Matrix, Meridian, JetPROP.

For example TIO-540-AE2A, TSIO-520-BE, PT6A-42A.

For example JPI EDM-930, EDM-900, Garmin EIS, or “none”.

For example GTN 750, G500 TXi, G1000, Avidyne IFD, KLN 90B.

Available file types

Check every kind of file you are able to export. Do not attach any of them here.

How you usually get files off the airplane: SD card, USB stick, FlightStream to an iPad, an app you export from, and anything that has been awkward.

Reminder: no logbooks, maintenance documents, credentials, Garmin-account exports, or raw flight files. Equipment details only.

How we use what you send

  • Testing coordination only. Your name, email address, and equipment information are used to coordinate compatibility testing with you and for nothing else.
  • Your TestFlight link, by email. Your sign-up automatically receives one message with our TestFlight link and how to get started. That is the only automatic email.
  • Never sold or shared publicly. We do not sell this information, publish it, or share it with anyone outside SnickityBit Solutions.
  • Raw files come later, and privately. Testing import compatibility does mean we will need a real file from your equipment eventually. When we reach that point we will ask you first and agree on a private way to transfer it. Files are never uploaded through this page.
  • Ask us anything. Questions about any of this go to support@snickitybit.com.