Liito connects the trip, the aircraft, the schedule, and the money, so you catch what's coming while you can still fix it: a flight held when a medical or inspection lapses, a maintenance-deferral (MEL) clock caught before you sell the trip, a double-booked rental flagged before it happens, and the hours billed before they slip away.
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.
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 runs the whole operation on one set of records: the same airplanes, the same people, the same airworthiness picture. So you're not keeping the same facts in six places by hand.
Your bread and butter, and the strictest flying you do. Every leg clears the §135 gate before it goes, and the invoice settles on the hours you actually flew.
Your own pilots' currency and your customers' lessons, in one place. A sign-off counts only when the training actually met the requirement, not just because the airplane flew.
A rental hour is just another hour. Renter-flown or company-flown, it lands on the same meters and moves the next inspection like a revenue leg does.
The airplanes you manage for owners, held to the same gate and records as the fleet you fly for hire. They run on the Part 91 ruleset, so none of the §135 duty, rest, or FRAT requirements apply.
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 on the §135 flights it routes the sign-off by the flight's risk score. Switch missions, not systems.
This is the walkthrough we run in a demo. Start on the dashboard, open up why each flight is held, and finish by planning the next trip with the same checks in place.
The day opens as a sentence, not a wall of green counts: what is held and why, what is waiting on a customer, what is moving. Each held flight states its blocker in plain words, next to the one button that starts the fix.
Open the trip, and the fuzzy "are we good to go?" gets a concrete answer. The whole lifecycle sits on one face: request, quote, schedule, payment, release, each stage naming its state. Every blocker cites the check behind it in plain words, and each leg wears its own status, held, projected, or set.
One calendar carries trips, crew, maintenance, training, and rentals together. Liito shows which trip or rental owns the conflict and what to check next. It does not pretend to have made the call for you.
Every airplane has its own page, and the page answers for any moment: move the clock and the location, commitments, and readiness re-answer for that time, while today's actual numbers stay put. Set it to the planned departure and N427AV tells you itself: not legal to fly that day.
After the four surprises, start the next piece of work by naming what it is: a charter quote, a charter that skips the quote, a training flight, a rental, or ground maintenance. Each choice opens its own planning flow, and they all land on the same schedule underneath, so the checks are already waiting.
Price the trip, send it to the customer, and carry the accepted quote straight into operations.
Build a charter quote →Plan a customer charter that does not begin with a quote.
Plan the charter →Schedule the student, the instructor, the airplane, and the window together.
Create training →Reserve an exact airplane for a renter-flown block.
Create rental →Schedule ground work against an exact airplane, on the same schedule as the flying.
Schedule maintenance →A trip is built on the same six lines it will be dispatched from: what, who, when and where, aircraft, crew, review. Liito names the next slot at every step and keeps the live record beside you as it fills in, so planning is never a maze of tabs; it is one form becoming one trip.
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 on the ramp.
Every check projects to the leg's scheduled departure and arrival, not just today's status, so you catch a problem with time to act, not on the ramp.
Ten checks on a Part 135 leg, seven on a Part 91 or training leg: airworthiness, pilot currency, medical, type rating, duty & rest, open squawks and MELs, and the §135.63 load manifest among them. An open grounding squawk, an expired MEL, or an out-of-currency pilot blocks the leg either way. This is the regulatory and airworthiness release: weather, fuel, and airport judgment stay with the people who fly and dispatch, and their sign-off lands on the same record.
On a Part 135 flight the FRAT score sets approval routing: a routine flight clears through the normal path; 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 points you to the exact thing that caused it; the load manifest is signed at release. The result is an audit-ready record of who cleared the flight and why, 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 project it forward. Not a prediction: a projection.
Pick any future moment on the schedule and every airplane shows where it is: at base, enroute KBOS → KMVY, parked at its arrival airport, in the shop, or out on a rental or a check-ride. Ask once and you get the whole fleet: where each airplane is and what it's doing, in plain terms.
The airworthiness gate doesn't ask "is it airworthy now." It asks "will it be airworthy when this leg lands." It adds up the hours scheduled between now and then. A 100-hour inspection comes due at 4,512 Hobbs; with 18 hours on the schedule before the trip, the aircraft crosses that limit before it lands, and the flight can't release. You see the conflict before you dispatch, not after takeoff.
Projection updates itself: reschedule a flight, cancel one, record a meter reading, or close out a maintenance visit, and the fleet's projected readiness updates on the spot. The schedule moves; the answer moves with it.
A wrong release grounds an airplane. The projected-compliance engine built to prevent that, and how Liito connects aircraft, maintenance, people, and money, are patent pending.
A trip for 13 Foot Capital, KBED to KAUS and back, is sitting in the quote queue, pending the client's approval. N427AV is assigned. Commercially, it is ready to sell.
N427AV is also carrying a deferred pitot-heat squawk under a Category B MEL, deferred until July 23. Liito projects that squawk to the planned departure date, not just today's status. The aircraft, the quote, and the squawk all show the same thing: the assigned tail won't be legal to fly by the time the trip departs. Dispatch does not have to piece that together from three screens. It is one picture.
So the operator resolves it while the quote is still pending, by moving the trip to another tail or clearing the squawk, before the client has been told an airplane is theirs. The conflict that would have shown up on the ramp gets handled at the quote.
A rental hour moves a charter airplane's next inspection. An out-of-currency pilot holds a flight. That only happens because aircraft, maintenance, people, and money are one model, not four systems stitched together.
Set a model up once, then let each tail diverge. A fleet of identical airplanes still carries each one's own components, times, and history.
Airworthiness you can prove, because it's computed, not remembered. Hobbs and tach close out each flight and advance the inspections, the TBOs, and the ADs automatically.
One record per pilot, and it follows them across charter, training, and rental. Currency runs on its own clock, and duty and rest clear against §135.267 before you ever assign a trip.
You bill what you flew, not what you quoted. A quote turns into a signed agreement and an invoice on its own, and the final number trues up to the meters when the flight closes.
Liito Labs builds operations software for regulated industries, where the cost of a missed check is a grounded asset, a fine, or a shutdown. Liito, for aviation, is our first product, and our focus today.
Underneath it is Viiste, an engine built to generalize: it models regulation as forward-looking checks, evaluates every release against the time of the operation rather than the present, and keeps an auditable account of every decision, each one tied to the rule behind it. We started in aviation, where the rules are dense and the stakes are physical. The same engine extends to other regulated operations.
Liito Labs was founded by Aaron Elder: years in high-tech bringing order from chaos, and a pilot and airplane owner. He first met the problem in his own flying: the facts that keep an airplane legal, scattered across too many places. Operators live it every day, across whole fleets. Liito is built to help them.
Liito is auditable because every decision is structured, recorded, and tied to the rule behind it. That same discipline is what makes the operation readable by software. Because the record is kept this clean, modern software can act on it directly, instead of guessing at it through a stack of exports and screens. The calls that must be made by the book are still made by the book. Everything around them is built to be read and acted on: by your dispatchers today, and by the software agents that will optimize operations in the background tomorrow.
Yes. The rules flex to your ops spec, your authorizations, and your limitations. Liito fits your operation, not the other way around.
You don't switch all at once. Bring over the piece that hurts most, charter, training, or maintenance tracking, and add the rest when you're ready. Liito runs best when the whole operation is on it, and it earns that one piece at a time.
Liito is in preview with multiple operators, and not yet generally available. Demos open as availability does. Tell us a little about your operation and you'll be first in line for a walkthrough on a sample day: the dashboard, a flight going from held to released, the schedule with rentals and training in the mix, aircraft projection, planning the next trip, and the quote-to-invoice chain.
Thanks, you're on the list. We'll reach out to set up your walkthrough as demos open.