Features
- Reads JPI EDM engine monitor downloads (.JPI and CSV)
- Reads Garmin GTN 650/750 logs; G1000 and G3X logs import as GPS tracks for now
- Reads ForeFlight KML and Garmin Pilot GPX (beta) track exports
- Every flight laid out: phases, cylinder temperatures, fuel flow and findings
- Trends across flights, each compared only with the flights before it
- Maintenance completions, meter readings and squawks beside the data
- Reads scanned logbook pages into records you check against the page
- Imports the records you already keep through a spreadsheet template, with no pages or OpenAI key needed
- Optional plain-language answers from OpenAI, with your own API key, that cite what they read
- No account: your archive is stored and analysed on your Mac
Your logbook, organized
Avionvera deciphers your scanned logbook pages into organized maintenance records that you check against the page, using your own OpenAI key. Already keep organized records? Fill in the app’s spreadsheet template and import it instead, with no pages and no key needed. Your recordings and your records then sit together, so you can see the big picture: each flight, how your engine changes over time, and what was done and when.
Your recordings, read
Your engine monitor and avionics already record every flight. Avionvera reads those files on your Mac and lays each flight out: its phases, cylinder temperatures, fuel flow, and the findings that stand out, with the route named from your own GPS fixes.
Change over time
Trends follow your engine from flight to flight. Each flight is compared only with the flights that came before it, so a later flight never colours an earlier one.
Maintenance beside the data
Record completions, meter readings and squawks, keep the documents that prove them, and read scanned logbook pages or import your own spreadsheet of records, checking everything before it is filed.
Honest about what it is
Avionvera is not an airworthiness decision: your logbook and your mechanic remain the authority.
Avionvera is being built for general aviation, piston and turbine, starting with the Piper PA-46 family, Malibu through M700. 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.
Some recorder formats cannot be read today, and G1000 and G3X logs import as GPS tracks only: their engine channels are not read yet, and logs from owners who fly behind them are exactly what we need to build that. The user manual lists what is read and how to get each recording off the airplane. It is in beta, and owner-pilots can sign up on the beta page to get the TestFlight link.
What leaves your Mac
Your archive is stored and analysed on your Mac, and nothing is sent on its own. A few optional features send something, each only when you ask (the two OpenAI features use your own OpenAI API key, and OpenAI may charge for their use): AI answers send a summary of the app’s analysis to OpenAI, logbook reading sends the page images you choose to OpenAI, and a feedback report or a recording comes to SnickityBit only when you send it for support. Response storage is turned off for OpenAI requests, but OpenAI’s own data-use and retention policies still apply to what is sent.
Get Avionvera
In beta for macOS 15 or later, through TestFlight. Sign up on the beta page.
Visit the Avionvera site