Charter, flight training, rentals, the aircraft you manage for owners — Liito runs every line of your operation on one model of aircraft, maintenance, crew, and money. The same release and airworthiness discipline runs under every flight, applied to exactly what it requires.
Charter, a flight school, leaseback aircraft, an owner who flies their own jet — you keep it all straight across a stack of tools, spreadsheets, and sticky notes, and you make it work. Liito brings the whole operation into one place — the same airplanes, the same people, the same airworthiness — so you're not keeping the same facts in six places by hand.
On-demand customer flights, end to end: quote from a fee catalog, a signed charter agreement, dispatch through the §135 release gate, and an invoice reconciled against actual hours. Customer and crew itineraries go out by secure link.
Your internal Part 135 recurrent, check-rides, line checks, and IOE — and customer instruction, CFI/CFII-led, on a school aircraft like an SR22. Training events are a first-class parent of their legs; you sign off currency when the training actually meets the requirement.
The flying that isn't charter — renter-flown or company-flown — on the same operations calendar. Capture Hobbs, fuel, and consumables per flight, and invoice from usage. The same meters feed maintenance, so a rental hour counts toward the next inspection like any other.
Owner-use and positioning legs on the same schedule and the same airworthiness gate as everything else — with the Part 91 guard set, no §135 duty/rest or FRAT where the regulation doesn't ask for it. An owner trip runs through the same gate and the same records as the revenue fleet — not a side process in a spreadsheet.
One model of aircraft, maintenance, people, and money — and one release gate that knows which rules each flight flies under. Liito runs ten checks on a Part 135 leg, seven on a Part 91 or training leg, and routes the sign-off by risk only where §135 calls for it. You don't switch systems to switch missions.
Aircraft, maintenance, people, money. The reason a rental hour can move a charter aircraft's inspection due-date — or an out-of-currency pilot can hold a flight — is that none of it lives in a silo.
Every tail and the components on it as tracked resources — type-level configuration with per-tail overrides, so a fleet of the same model still carries its individual history. The aircraft detail is your fleet-management hub.
Hobbs and tach logged at flight close drive inspection due-dates, TBO, and AD compliance. Squawks, MEL deferrals by category, maintenance events with PIN-signed sign-off, and the return-to-service release — the airworthiness gate computes from real numbers, not memory.
One identity per person, one model of qualifications, and currency requirements that recur on their own clock. Duty and rest compute against §135.267 before you assign anyone; outside flying is captured by attestation. The same pilot record serves charter, training, and rental.
Calculated pricing — hours × type rate plus line items — a typed-name charter agreement that's ESIGN/UETA-compliant, and an invoice created the moment a quote is accepted. After the flight, Liito reconciles the estimate against actual meter readings.
The release gate checks a flight against the conditions at its scheduled time, not the moment you happen to look. A medical that lapses before the trip, an inspection that comes due mid-week, duty that runs over by the last leg — the gate flags it while there's still time to fix it on the ground, instead of discovering it at the ramp.
Every guard reads forward to the leg's scheduled departure and arrival — not just today's status. The airworthiness check even accounts for the hours the aircraft will fly before then: if a 100-hour inspection comes due before it lands, the leg won't release. You catch it with time to act, not at the ramp.
Airworthiness, pilot currency, medical, type rating, duty & rest, open squawks and MELs, and the §135.63 load manifest — ten checks on a Part 135 leg, seven on a training or owner-flown one. An open grounding squawk, an expired MEL, or an out-of-currency pilot blocks the leg either way.
On a Part 135 flight the FRAT score sets approval routing: a routine flight clears one way; an elevated score routes the sign-off to whoever holds the authority. On Part 91 and training legs the PIC's release is the authorization. The leg can't fly until the right person has signed.
Each result names the regulation behind it and pins the cause to the record that triggered it; the load manifest is PIN-signed at release. The result is an operational-control account you can stand behind — not a checklist someone ticked from memory.
Dispatch is a question about the future, not the present. Pick any moment on the schedule and Liito answers it for the whole fleet at once — because the same model that tracks an aircraft today can run it forward.
Move the time lens to a future moment and every tail resolves to a place: at base, enroute KBOS → KMVY, parked at its arrival airport, in the shop, or out on a rental or a check-ride. One request, the whole fleet — just where each airplane is and what it's doing, no raw IDs.
The airworthiness gate doesn't ask "is it airworthy now." It asks "will it be airworthy when this leg lands." It sums the flying between now and then — a 100-hour inspection due at 4,512 Hobbs, with 18 hours scheduled before the trip, projects past the limit on arrival, and the flight can't release. You see the conflict before you dispatch, not after takeoff.
Projection is event-driven: reschedule a flight, cancel one, record a meter reading, or close a maintenance event, and the fleet's projected readiness recomputes on the spot. The schedule moves; the answer moves with it.
The screenshots are the easy part. Being right about Part 135 — every guard, every citation, every regime — is the moat, because a wrong release isn't a bug, it's a grounded airplane. That model, and the projected-compliance engine behind it, is patent pending.
This is the walkthrough we run in a demo, on a seeded operating day with charter, training, and rentals all in motion. It moves from the whole day down to a single flight, and back out to what's coming.
Start at the dashboard. The useful question isn't whether every count is green — it's what needs attention and where the next click goes. Cards are commitments: a count, a label, and a drill-in that lands on exactly that filtered work, not a generic list.
Open a charter from Bedford to Austin. A high-level dispatch question becomes specific: who's the account, which tail is planned, which legs exist, and what would block release. Every red or yellow issue says what's wrong, why it matters, who owns it, what to click next, the evidence that resolves it, and whether release stays blocked.
One calendar carries trips, crew, maintenance, and rentals together. A dense day still tells you which event owns a badge and which resource it involves. Liito attributes conflicts to their source — it doesn't pretend to solve them automatically — so you can see exactly what to reschedule, inspect, or ask about next.
Change the time lens and watch projected readiness move while current facts hold still. One aircraft is under MEL pressure, another is out on a renter-flown rental, a third is mid check-ride, a fourth is repositioning for its owner — one fleet, four operations, one honest answer to "will this airplane be legal at the planned departure?"
Start a new event — a customer charter, an owner-use leg, a positioning flight, or a training sortie. The wizard is forgiving: you can see when a draft exists, where leg timing lives, when crew assignment becomes available, and exactly what Back and Create will do before you commit.
If your business is a single neat line, you have simpler options. Liito is for the operators whose week doesn't fit in one — and whose airplanes, people, and compliance are scattered across a stack of tools that have never talked to each other.
Different missions, one operation. That's the operator Liito was built for — and the reason it's one system, not four.
Liito is in operator preview. Tell us a little about your operation and we'll set up a walkthrough on a seeded day — the dashboard, a charter going from blocked to releasable, the schedule with rentals and training in the mix, aircraft projection, and the quote-to-invoice chain.
Thanks — we'll be in touch to set up your walkthrough. Keep an eye on your inbox.