MyFBO is going away. Your maintenance history is inside it.
Get it out — into something open, exportable, and free. This page is about rescuing the records, and it is upfront about the large part of MyFBO that MyTailLog deliberately does not do.
Read this first: MyTailLog is not a MyFBO replacement.MyFBO's core was scheduling, dispatch, and billing. MyTailLog does none of those, and won't — they're on the explicitly-out-of-scope list, not the backlog. If what you need is a booking calendar and an invoice run, keep looking; you should hear that here rather than three weeks into a migration.
What we are is the records half: an AI-read, searchable index of your maintenance history that tells you what's due and hands you everything back on demand.
Do the export first, worry about the destination after
The one irreversible step in any shutdown is losing access. Before anything else, pull every export MyFBO will give you and save it somewhere you control — maintenance history, uploaded documents, aircraft details, open squawks. While you're at it, photograph the physical logbooks; they're the legal record and they're the one copy no vendor can take away.
Then you can take your time choosing where it lands. Everything below still works months from now on a folder of PDFs and photos.
We read what you can actually get out
There is no import wizard that needs their schema, and no ticket to open. Pages come in as PDF, JPEG or PNG— a multi-page PDF is split into one page each, in order — or straight from your phone camera, which detects the page edges, deskews and crops. A plain photo of a paper page, taken in the hangar with no signal, queues on the device and uploads when you're back online.
Then a vision model reads each page into structured entries, in minutes, with a confidence score on every field and a cropped snippet of the scan showing where each value came from. It is self-serve and free at the point of use — not a transcription service you pay per aircraft and wait weeks for. The flip side, stated plainly: you are the reviewer. Nobody else checks the entries; the app's job is to show you precisely where to look.
If your MyFBO export is a CSV or a spreadsheet, there is no direct importer today. Print it to PDF and it goes through the same extractor as a scan. It works; it is also a gap we'd rather name than dress up.
What the migration actually looks like
- Enroll the aircraft.Type the tail number; the FAA registry lookup fills make, model and serial. Five logbooks are created — airframe, engine, prop, avionics, and Other for A&P documents.
- Upload into the right logbookand let extraction run. Start with the last few years if the backlog is large; the searchable index is useful long before it's complete.
- Review with the original page beside the entry. Flagged fields first; accept the clean ones in a click.
- Take a
.zipbackup the same day — every row plus the original scans, re-importable anywhere. That is the step that means this never happens to you again.
After that, Status, the Part 91 maintenance forecast, AD/SB compliance, the equipment list, oil trending, and the records-gap audit all come alive from your own entries, and reminder emails arrive before things come due.
What moves over, and what doesn't
| Moves over | How |
|---|---|
| Maintenance & inspection history | Upload the PDFs, scans, or photos of the pages. A vision model reads each one into structured entries — date, hours, work performed, parts, AD/SB references, signature — with a confidence score per field. |
| AD compliance state | Track ADs with FAA reference lookup (Federal Register, with a DRS fallback for legacy ADs). Scan an A&P's AD compliance report into the Other logbook and it becomes the ground truth — corroborating what you already track and adding what you didn't. |
| Installed equipment | Reconstructed from the log entries as they're extracted — installs and removals proposed for you to confirm, rather than a list you retype. |
| Weight & balance | Scan the W&B sheet into the Other logbook; it becomes a new revision with history, and goes stale-flagged if equipment changes after it. |
| Permanent records | Airworthiness certificate, registration, radio station authorization, POH/AFM, STCs, 337s, 8130-3s and manuals go in the Records Vault, next to the logbook scans. |
| Aircraft identity & hours | Enrollment fills make, model and serial from the FAA registry by tail number. Enter your current hobbs/tach, then log readings as you go — or connect MyFlightBook and let the daily sync pull them. |
| Open squawks | Re-entered by hand (there aren't usually many). Severity and reporter are tracked, and they stay open until a mechanic resolves them. |
| Doesn't | Why |
|---|---|
| Scheduling & the booking calendar | Deliberately out of scope. We do not build flight-school ops, and this is not on a roadmap. |
| Dispatch, rental & instruction rates, invoicing, card payments | Out of scope. MyTailLog has no billing system of any kind — not for you, and not for your renters. |
| Membership dues and auto-charge | Out of scope, same reason. |
| Member, renter and CFI rosters; org roles | Sharing is two roles — viewer and editor — scoped to one aircraft. There is no organization layer. |
| Flight logging and pilot currency | We track aircraft hours for maintenance forecasting, not flights or pilots. A pilot logbook is a different product. |
| Weather briefing | Fully commoditized elsewhere, and unconnected to records. |
| A direct CSV / spreadsheet importer | Not built. Pages come in as PDF, JPEG or PNG. Print or export a CSV to PDF and it goes through the same extractor as a scan — that works, but it's a workaround, not a feature. |
| An automated MyFBO connector | There isn't one, and there won't be. This is a manual migration: you export, you upload, we read. |
Why this can't happen to you again here
- MIT-licensed, public source. The whole app, schema and security policies are yours to run. Nobody can announce a shutdown that takes that away.
- A full ZIP export whenever you want one — a manifest, every row as plain JSON, and the original scan and document files. It re-imports into any MyTailLog instance, including your own.
- No billing to lapse. There are no plans, no card on file, and nothing that flips your account to read-only.
- The paper is still the record. MyTailLog is an index of your logbooks under 14 CFR 91.417, never a replacement for them — so the worst case has always been losing an index, not losing your history.
What it costs to move
Nothing. There is no billing in MyTailLog at all, and no migration fee, because there are no humans in the loop to pay.
The one thing worth planning around: reading pages costs AI calls, so the shared key has a per-person daily cap and an overall daily budget. A backlog of several hundred pages may take a few days at that rate — or add your own Anthropic API key in Profile and run it in one sitting on your own account. The FAQ has the details.