Skip to content

For owner-pilots · Aeroplanes and helicopters · EASA first

Your aircraft, in full view.Even when a CAMO manages it.

Techlog, maintenance, documents, pilot logbooks and trips in one shared record, with an ops desk that plans the trip and writes to the airports for you. Built for owner-pilots of aeroplanes and helicopters, and for the co-pilots and maintenance crew who share the aircraft with you. Paper goes in, a live picture of your aircraft comes out.

Early access. In regular use on a real aircraft. First invitations go to owner-pilots in Europe.

One flight, as FlightDex records it LHBS → LOWW
BLOCK OFF
08:42Z
TAKE-OFF
08:51Z
LANDING
10:07Z
BLOCK ON
10:13Z
BLOCK 1:31
  • Techlog — row closed, counters carried forward
  • Maintenance — hours added to every due item
  • Logbook — drafts for PIC and second pilot
  • Everyone subscribed — PDF of the sheet by email
  • See everything. The due list, the open defects, the expiring certificates, the hours. The same view your maintenance crew sees.
  • Digitise everything. Photograph it, forward it, drop it. AI files it, reads it and proposes the update. You confirm.
  • Share with everyone who flies or fixes it. The record belongs to the aircraft, not to one pilot’s phone.
  • Fly abroad with an ops desk. Navlog in. Airports researched, PPR, handling and departure mails drafted, replies tracked. You approve every mail.
The techlog of D-EDMO on a phone: one card per flight with block and flight time, landings, the G1000 counter and fuel. The techlog of D-EDMO on a phone: one card per flight with block and flight time, landings, the G1000 counter and fuel.
The aircraft overview of the demo aircraft D-EDMO: an airworthiness warning with an open defect, overdue items and a deferred defect, then the TTAF, landings, engine hours, next inspection, fuel, TKS and O2. The aircraft overview of the demo aircraft D-EDMO: an airworthiness warning with an open defect, overdue items and a deferred defect, then the TTAF, landings, engine hours, next inspection, fuel, TKS and O2.

Why

You are responsible for the aircraft. You should be able to see it.

Under EASA Part-ML the owner is responsible for continuing airworthiness. Contracting a CAMO hands it the contracted tasks; it does not take the aircraft out of your hands. What the contract spells out for you is a copy of the maintenance programme and notice each time the aircraft has to go in. It does not spell out a live due list, the AD decisions, the remaining life of parts, or the reasoning behind them.

Meanwhile you owe the CAMO something too: flying hours, every defect found in operation, and notice of any pilot-owner maintenance within 30 days. Today that goes by email, paper or a spreadsheet.

What a typical shared aircraft runs on today

  • Paper techlog in the aircraft, hours copied into a sheet on Sunday evening
  • Spreadsheets one for hours, one for fuel, one for money, one nobody updates
  • WhatsApp where squawks go to be forgotten
  • The CAMO’s PDF a status report from last month
  • A shoebox invoices, CRSs, the old logbooks, the POH supplement you cannot find

One shared record of the aircraft, live, for everyone who flies or fixes it.

a year, privately owned aircraft
77 h
a year, group-owned aircraft
107 h
single-engine piston, 2019 average
€226 / h
piston helicopter, 2019 average
€501 / h
In Europe an aircraft owned by a private individual flies about 77 hours a year; one owned by a group flies about 107. Every one of those hours costs real money (in the 2019 survey, on average about €226 an hour for a single-engine piston and about €501 for a piston helicopter). Those hours deserve a record that is complete, shared and yours. — GAMA-IAOPA General Aviation Survey 2019

Your own ops desk

Professional flight management, for the pilot who is also the operator.

LiveEvery step below is Live.

An airline has an ops department and a dispatcher. You have FlightDex. Import the navlog: it builds the trip, researches every airport, drafts the PPR, handling and departure mails to the airports and handlers, and keeps track of every reply. It does the legwork. You approve every mail before it goes.

  1. Import the navlog.

    ForeFlight navlog PDF, Garmin .fpl or GPX, or type it in. FlightDex builds the legs and the stops: fuel stop or stay, the fuel you asked for, the handler.

  2. Every airport researched.

    Opening hours, PPR rules, handling, slots, fuel, customs and Schengen, frequencies, contacts. From the AIP and the airport’s and handlers’ own pages, every field with its source and a confidence. You approve what is right; later research never overwrites it.

  3. The trip checked.

    Night from the sun position, opening hours, daily restrictions, turnaround, fuel, handling, missing people. The AI adds its own warnings and questions.

  4. Who do we write to?

    For every stop FlightDex suggests the recipients and says why: the handler you picked, or the airport’s ops office. Tick the ones you want.

  5. Mails drafted. You approve.

    Arrival, handling and PPR requests to the destination and the fuel stops, with the slot and PPR questions inside; a departure notice to the handler where the aircraft is parked. Change anything. Nothing goes out until you press Send.

  6. Replies threaded and read.

    Each airport and handler is one thread. Replies are matched back and summarised: confirmed, question, quote or declined, with the booking reference, the slot, times and prices pulled out for you to copy onto the stop. If they ask something the trip can answer, the AI drafts the reply.

  7. When the plan changes.

    Threads without an answer are flagged, and a short reminder is one click away. ETA moved? The update mail states only what changed. You are notified when a reply needs you.

Illustration · the mail tab of a trip LHBS → LIPV → LFML
  • LIPV Fuel stop · Airport ops

    Confirmed

    Arrival, PPR and fuel request

    PPR confirmed. Booking reference and slot copied to the stop.

  • LFML Stay · Handler

    Action needed

    Handling and slot request

    Question: which day does the aircraft depart? A reply is drafted.

  • LFML Stay · Fuel

    Awaiting reply

    Fuel uplift before departure

    No reply yet. Reminder ready.

Every mail: drafted by AI, sent by you.

NextComing soon

  • GENDEC and UK GAR pre-fill
  • A PPR, handling and customs checklist per stop
  • Live NOTAM, weather and fees
  • Flight-plan filing and ForeFlight sync
  • Your own sending address (today the mail goes from one shared FlightDex address)

Trips & ops mail, step by step →

What it does

What FlightDex does

  • Live

    Transparent, even under a CAMO

    The due list by hours, days or landings, whichever comes first. Defects with their deferral reference and the CRS that closed them. An airworthiness check before every flight. Everything audited.

    Live proof In beta

    On a real DA50 RG, the AI read the aircraft’s own paperwork and proposed a 66-item maintenance programme, every line with its source, for the owner and the CAMO to confirm.

    In beta on this one type; a generator for other types is coming soon.

    NextComing soon

    CAMO guest access, AD/SB engine, component log cards, 12-month forecast.

  • Live

    Paper-free

    Invoices, CRSs, certificates, the POH, logbook scans. Drop them, photograph them or forward them by email. AI classifies them, reads the expiry and the TTAF, and proposes what to do. You confirm.

    Email forwarding is in beta.

    NextComing soon

    POH into structured limits and W&B, aircraft and engine logbooks into a maintenance history, old paper techlogs backfilled.

  • Live

    One aircraft, many pilots, and your maintenance crew

    Roles per aircraft: admin, pilot, maintenance, viewer. Your mechanic sees the same live techlog, defects and hours as you. Close a flight and both pilots get their logbook draft.

    NextComing soon

    Shared ownership workspaces (in beta), booking, cost per hour, group billing, mechanic portal.

  • Live

    Your avionics log, imported

    Drop the G1000 NXi SD-card log: block times, touch-and-goes, airports and fuel-flow-integrated burn fill the techlog row. GPX, KML and CSV tracks become logbook drafts, with helicopter leg detection.

    NextComing soon

    Garmin legacy and G3X, JPI EDM, Dynon, IGC, flyGarmin, helicopter VEMD photo capture.

  • Live

    Open by design

    Paper-faithful techlog PDF, FCL.050 logbook PDF, CSV in the formats your other apps read, monthly backup by email. Imports from six logbook apps.

    NextComing soon

    Public REST API, signed webhooks, CAMO feed, records-transfer bundle.

How it works

From chocks off to a closed record, without paper

LiveEvery step below is Live for aeroplanes.

  1. Open the flight.

    Departure, fuel on board, oil, TKS and O2 carry forward from the last row. PIC is you.

  2. Airworthiness check.

    Open defects, overdue items, expired certificates or deferrals show up full-screen. You acknowledge; the owner and maintenance are notified. It warns, it does not block.

  3. Fly.

  4. Land and close.

    Type the sheet or drop the G1000 log. Block and airborne times, landings, the hour-meter reading, fuel used from fuel flow, oil added.

  5. Validation.

    Counter delta against block time, fuel used against the tank difference, departure against the last arrival. Blocking errors stop you. Warnings ask you to confirm.

  6. PDF to everyone.

    The paper-faithful techlog sheet goes out by email the moment the row closes.

  7. Logbook drafts for both pilots.

    Night from the sun position, cross-country, IFR, instructor time with zero landings for the right seat.

  8. The due list moves.

    Every maintenance item gets the hours and landings. Warnings go out when a threshold is crossed.

A new flight filled in from a G1000 NXi log: LHBS to LOWW, block 1:30, airborne 1:16, 10.1 USG from fuel flow, and every field it filled marked G1000. A new flight filled in from a G1000 NXi log: LHBS to LOWW, block 1:30, airborne 1:16, 10.1 USG from fuel flow, and every field it filled marked G1000.
A new flight filled in from a G1000 NXi log: LHBS to LOWW, block 1:30, airborne 1:16, 10.1 USG from fuel flow, and every field it filled marked G1000. A new flight filled in from a G1000 NXi log: LHBS to LOWW, block 1:30, airborne 1:16, 10.1 USG from fuel flow, and every field it filled marked G1000.

AI, with a human in the loop

Suggest, then you confirm. Always.

FlightDex uses AI to read what you give it: a CRS, a fuel receipt, an insurance certificate, a page of a paper logbook, a work report. It classifies the document, pulls out the date, the expiry, the issuer, the amount, the registration and the TTAF, and proposes an action. Link this receipt to Saturday’s flight. Create a maintenance event from this CRS. Set this certificate to expire on 14 March. Nothing is applied until you accept it.

  • AI document classification and suggestionsLive
  • AI maintenance programme proposal, on one aircraft typeIn beta
  • A programme generator for other typesComing soon

If you run FlightDex without an AI key, every step still works by hand.

AI digitisation in detail →

A work report filed by AI, with a suggestion to update the engine oil change item: performed 14 Oct 2026 at TTAF 318.2 h, confidence 91 %, Reject or Accept. A work report filed by AI, with a suggestion to update the engine oil change item: performed 14 Oct 2026 at TTAF 318.2 h, confidence 91 %, Reject or Accept.
A work report filed by AI, with a suggestion to update the engine oil change item: performed 14 Oct 2026 at TTAF 318.2 h, confidence 91 %, Reject or Accept. A work report filed by AI, with a suggestion to update the engine oil change item: performed 14 Oct 2026 at TTAF 318.2 h, confidence 91 %, Reject or Accept.
Real example, from a real aircraftIn beta
We pointed the AI at one DA50 RG’s own scanned paperwork: work reports, the ARC, the equipment list, the AFM. It proposed 66 maintenance items across inspections, documents, avionics, engine, propeller, retractable gear, O2 and TKS, and cabin equipment. Each line carried its source document and a high/medium/low confidence. It also flagged an expired ARC sitting in the document store, gearbox oil debris to watch over the next 50 hours, and an EASA AD that needed the CAMO’s confirmation. Every item loaded as “proposed”, for the owner and the CAMO to review and confirm line by line. That is the standard: the AI drafts, people decide.

Aeroplanes and helicopters

Built for both. Honest about where each stands.

  • Live

    Aeroplanes

    The techlog, maintenance tracking, G1000 NXi import, documents, trips and the pilot logbook are in regular use on a single-engine piston aeroplane.

  • Live

    Helicopters — pilot side

    The pilot logbook knows helicopters: a separate helicopter view, FCL.740.H type ratings for several types, LAPL(H) and IR(H) recency, helicopter extras. Track files from ADS-B or your EFB use helicopter leg detection: airborne above 15 kt, hover stops counted as landings.

  • Coming soon

    Helicopters — aircraft side

    Helicopter techlog fields, rotor and engine hours, starts and NG/NF cycles, Robinson 12-year/2,200-hour limits, VEMD and EMU photo capture, heliport lookup. We will record and evidence turbine cycle counters. We will never compute them.

The full helicopter page →

Integrations

Your avionics, your EFB, your logbook app

Live
  • Garmin G1000 NXi CSV
  • GPX
  • KML (ForeFlight, FR24)
  • CSV tracks
  • ForeFlight navlog PDF
  • Garmin .fpl
  • flylog.io
  • ForeFlight Logbook
  • MyFlightbook
  • mccPILOTLOG
  • CrewLounge
  • LogTen Pro
  • Any CSV/XLSX with column mapping
  • PDF, JPEG, PNG, HEIC, DOCX, XLSX documents
In beta
  • Flightradar24 API
  • Forward-by-email ingest
Coming soon
  • Garmin legacy CSV (G1000, Perspective, G3000, TXi, GI 275)
  • G3X / G5
  • JPI EDM
  • Dynon SkyView
  • IGC
  • CloudAhoy
  • EI MVP / CGR
  • Rotax B.U.D.S.
  • flyGarmin / PlaneSync
  • AirSync
  • Helicopter VEMD / EMU / Cabri photo capture
  • CAMP
  • Traxxall
  • Veryon
  • Leon
  • Crewchief
  • Accounting exports

The full formats table →

For your maintenance crew and your CAMO

They see what you see. Nothing more to chase.

Live

Give your mechanic or CAMO the maintenance role on your aircraft. They get the same live techlog, the same hours and landings, the same defect list. They can defer a defect with the ML.A.403 reference and a limit, close it with a CRS reference, record a maintenance event with the TTAF and the CRS, and accept the AI’s suggestion when the work report arrives by email. Every change is audited with a before/after diff. CRS-linked documents cannot be deleted.

Coming soon

A free read-only guest role for CAMOs and shops, a scheduled hours-and-defects report to your CAMO, a work package from your defects and due items, and an AI import of your CAMO’s status report with a diff against what FlightDex expects.

For CAMOs and mechanics →

A deferred defect with its ML.A.403 reference, a limit by date and TTAF, the reason and the history of changes. A deferred defect with its ML.A.403 reference, a limit by date and TTAF, the reason and the history of changes.
A deferred defect with its ML.A.403 reference, a limit by date and TTAF, the reason and the history of changes. A deferred defect with its ML.A.403 reference, a limit by date and TTAF, the reason and the history of changes.

Trust

Records you can stand behind

EU hosted.
The app and its database run in the European Union, on a Hostinger server in Frankfurt, Germany. AI steps send the document or text being read to Anthropic.
Append-only audit trail.
Every change keeps its before and after. Nothing is deleted; entries are voided and keep their sequence number.
24-hour lock.
A pilot can edit their own row for 24 hours. After that only an admin can, with a mandatory reason.
CRS documents stay.
A document linked to a CRS, a flight or a defect cannot be deleted.
Offline first.
Installable app. Record a row at a field with no signal; it syncs later, with conflicts shown side by side.
Bilingual.
English and Hungarian, in the app and in every email. More languages are on the roadmap.
Your data is yours.
PDF, CSV and ZIP exports on every plan. Whole-aircraft export and a records-transfer bundle: coming soon.
AI you can switch off.
Every AI feature degrades to a manual step without a key.

Roadmap

What we are building next

  1. 1.Aircraft category, type library and helicopter counters

    Coming soon
  2. 2.CAMO access and a scheduled feed to your CAMO

    Coming soon
  3. 3.Universal import framework: Garmin legacy, G3X/G5, EFB tracks into the techlog

    Coming soon
  4. 4.AI aircraft, engine and prop logbook digitiser

    Coming soon
  5. 5.AI maintenance programme generator for any type

    Coming soon

Dates are intentions, not promises. Items move when early-access owners tell us what hurts most.

The full roadmap →

Pricing

Pay for what you fly

A free logbook to start. A Pilot plan for your own flying. An Aircraft plan per aircraft for owners, and the pilots you invite use the aircraft free.

Free
€0
Pilot
€5.90 / month
Aircraft
€24 / month · per aircraft
See pricing

FAQ

Questions owner-pilots ask

All questions →

Is FlightDex my official techlog?

Not by itself. FlightDex is a record-keeping aid. Whether an electronic techlog is accepted as the aircraft’s record is for your authority and your CAMO to decide. Many owners keep the paper sheet as the legal record and run FlightDex as the live, shared copy, with the PDF of every flight archived. Ask your CAMO before you switch.

Does FlightDex replace my CAMO?

No. It is not CAMO software and it does not make your aircraft Part-ML compliant. Your CAMO/CAO, or your owner-declared maintenance programme, remains the legal anchor. FlightDex gives you a live view of the record and helps you meet your own duties toward your CAMO: hours, defects and pilot-owner maintenance notices.

Does it work for helicopters?

Partly, and we are honest about it. The pilot logbook fully supports helicopters today: a helicopter view, FCL.740.H type ratings, LAPL(H) and IR(H) recency, and helicopter leg detection on track files. The aircraft side (helicopter techlog, rotor hours, starts, NG/NF cycles, Robinson 12-year/2,200-hour limits, VEMD photo capture) is coming soon and first on the roadmap.

Which avionics logs can it read?

Live today: Garmin G1000 NXi CSV into the techlog, with touch-and-go detection and fuel integrated from fuel flow. GPX, KML and CSV tracks into the logbook. Coming soon, in order: Garmin legacy CSV (older G1000, Perspective, G3000, TXi, GI 275), G3X/G5, EFB tracks into the techlog, JPI EDM, Dynon SkyView, IGC, flyGarmin/PlaneSync, helicopter VEMD/EMU photo capture, CloudAhoy, EI, Rotax B.U.D.S. The full list is on the integrations page.

Where is my data hosted?

The app, its database, the uploaded files and the backups: in the European Union, on a Hostinger server in Frankfurt, Germany. AI steps send the document or text being read to Anthropic (see the AI questions). Billing is not live yet; when it is, payments will be handled by a payment provider and FlightDex will never see your card details.

Can I get my data out?

Yes, at any time and on every plan: the techlog as a paper-faithful PDF and CSV, the logbook as an EASA PDF, CSV and ZIP, and every document you uploaded. The logbook ZIP is also emailed to you monthly. A whole-aircraft export and a records-transfer bundle are coming soon.

Bring your aircraft out of the black box

Join the early-access list. We email you when your invitation is ready. If you have a log file from your avionics or engine monitor, send us an anonymised sample and we will build your importer sooner.

FlightDex

Join early access

Tell us about your flying and your aircraft. We email you when your invitation is ready, and nothing else.

I am