RotorLabRotorLab carries a drone program's whole record in one system: design the airframe against a validated physics engine, fly it on ArduPilot, PX4, DJI, Parrot and many others, and every flight, repair, sign-off and authorization lands on that aircraft's permanent record. Start from a real program instead of a blank page, watch the coverage numbers fill themselves in, and when someone asks, the answer is a document with a verification code. Built in Dubuque, Iowa.
The Log Analyzer needs no account and no card · nothing to install · your data stays private to your account.
Teaching UAS engineering? RotorLab for engineering programs.
One record travels the aircraft's whole life, and every stage leaves a document behind, ready the day someone asks.
Size the airframe against real physics, then calibrate it from your own hover.
sample: performance report ↓Freeze the design, sign the declaration, inspect every serial you ship.
sample: design dossier ↓Every flight lands on the aircraft's record and moves every clock that matters.
sample: pilot logbook ↓Three habits borrowed from the best tax software ever made, applied to something more fun than taxes.
Ship every serial born compliant, with the paper to prove it.
See how →File the flight; the records keep themselves.
See how →Teach on an engine students can see through.
See how →Qualify the one-off for the set that asks.
See how →Easy does not mean shallow. Every number on this page — hours, endurance, component stress, the audit trail itself — stands on a real flight-physics engine, not a grams-per-watt guess. Hover power comes from actuator-disc momentum theory, so prop size, air density, and payload move the numbers the way they do in the air. TurboTax never shows you the tax code; we publish our equations and invite you to check them.
Your whole operation on one page, read from your own records. Included with every plan.
Hours, flights, aircraft available, what is grounded, what is open in the safety log. Same place every time.
Activity over any period, with hours ranked by aircraft and by pilot.
Grounded airframes, parts at a life limit, lapsed currency, expiring cover, occurrences past review.
Operations, Maintenance, or Compliance views — or pick your own panels and order. Yours alone; it does not move anybody else’s.
Export any period as a signed, verifiable PDF — what an insurer or an auditor asks for.
Every panel opens the page behind it, so you land on the aircraft or the record that needs you.
Most fleet software assumes one rulebook. Win work in another country and your record-keeping quietly stops fitting — and you find out when a client, an insurer or a regulator asks for something it was never built to hold. RotorLab holds it. One account, one audit trail, eleven regulatory frameworks.
New cars tell you when a part is wearing out. Airliners have done it for decades. Your aircraft already log every flight in more detail than either. RotorLab is the system that listens.
Your ground station talks to a Fleet Server on your own network, which feeds ATAK in real time and files the flight to RotorLab when it is done. The Fleet Server is the only thing holding a RotorLab key and the only thing that reaches the internet — so a station lost in the field carries nothing that opens your account.
Runs on your own network. Talks MAVLink to your aircraft and ground stations, pushes live tracks to ATAK, and files finished flights to RotorLab — queuing them when the link is down.
Fleet Server →Not a product — a switch inside Fleet Server. Paste a RotorLab Device Key and flights, checklists, and logs start filing themselves. Needs a licensed Fleet Server and a RotorLab subscription; costs nothing on top of them.
How the link works →Any ground station onto the TAK network. Every aircraft on it becomes a live MIL-STD-2525 track, and a named map marker sends GOTO, RTL, LAND, or HOLD back. Licensed per workstation, unlimited aircraft.
The Bridge →Hours, currency, component life and coverage all answer one question: what has this fleet flown? Every figure is calculated from your own flights and names the ones it came from.
Every flight is one record — typed in, read from a log, or filed by a ground station. Hours and currency follow. A missing date reads unknown, never expired.
Serialized parts with limits in hours, cycles, or months. Life is spent by flying, a part’s history follows it to the next airframe, and the fleet learns how long each kind of part actually lasts here.
Waivers and certificates with what they cover and when they expire, plus the recurring reports built from flights already on record.
A manual whose live sections read your real roster, aircraft, and limits. Publish a revision to freeze what you approved — and hear about it when your records drift away from it.
Vibration, pack sag and motor balance trended against your own fleet’s learned normal, not a factory threshold, and flagged before they bite. After an incident, upload the log and get the timeline.
File flights against the job they were flown for and the hours total themselves, per job and per client. Hand the client a report with your own scope wording and the flights behind it.
The hazard somebody spotted, what was done, who closed it. Most occurrences damage nothing — a near miss, a link drop — and those are the ones worth keeping. Anything still open past review gets named.
What the air and the airspace were doing, kept with the flight: density altitude worked from the nearest observation, wind and temperature, and the controlled airspace and grid ceiling under the aircraft. Recorded whether or not it was a factor — the flight where it mattered is never the one you thought to write it down on. It tells you what was there. It does not tell you whether to fly.
The same airframe on a good day and a bad one, lined up: vibration, pack sag, motor spread, the lot. Differences too small to mean anything are left out rather than dressed up as findings, and where the analyzer cannot stand behind a number, the comparison says so instead of reporting a change.
Compass, GPS, barometer and the IMUs checked against each other rather than taken at their word — and the harmonic notch, whether the filter was really tracking the motors or set once and forgotten. When a log does not carry what a check needs, it tells you that, instead of handing you a clean result it never earned.
Policies, what each covers, when it lapses — and the question a filing cabinet cannot answer: which of your airframes are on no policy in force today.
Attach photographs to a job or an occurrence and tick the ones that go out. Location and camera data is stripped on upload. Your business details and logo appear on what you deliver.
For public-safety programs: publish what you fly at your own address, from records you already keep. Off until you switch it on, and every period is approved by hand.
The build file, the calibration, every flight, every repair, every authorization — one record per airframe, assembled as you work, ready the day a customer, an insurer, or a regulator asks. That is what design through compliance means.
Every question below is eventually asked of every serious operation. The record either existed before the question, or it does not exist at all.
An auditor gives you days, not months. Operations living in spreadsheets spend those days reconstructing; operations on RotorLab press Export. The difference is not effort — it is whether the trail was building itself all along.
After an incident, an insurer’s first question is about currency and maintenance on the day it happened. A logbook typed up afterward convinces nobody — least of all the person deciding whether to pay the claim.
Component hours, configuration changes, the last person to touch it. If that history lives in someone’s memory, it leaves when they do. If it lives in the record, it answers for itself — years later, signed and dated.
The question turns up in procurement questionnaires and insurance renewals, and the honest answer has always been a shrug. The UAS Security Verification Standard is open, vendor-neutral and free to read. RotorLab measures the flight logs you are already storing against it.
1 red and 7 amber failures are open. 24 requirements could not be decided from a log, and none of those count as passes.
Everyone keeps their own build library while the organization keeps one set of flight, aircraft, and maintenance records — so the fleet has a single history no matter who was on the sticks. Connect a flight controller and watch any flight live from any browser.
From workshop test stands to FPV, VTOL transition, and field survey, RotorLab models the rotorcraft you actually fly.
Every tool below ships with every account and reads the same build you are working on. Each link opens its guide in the documentation.
RotorLab Racing is a chartered MultiGP chapter in Dubuque — the only one in Iowa. An open racing chapter: fly what you race, standardized gates, and a ladder that runs from a field outside town to a world final.
Every tool on this page started as a question somebody asked at a track. What will this build actually pull? How long have I really got on this pack? Why did that one come down? The software is tested every weekend by people with nothing to gain from being polite about it.
No testimonials-page theater: three things you can check yourself, today.
Every governing equation, derived, referenced, and re-checked live in your browser against the engine — to 0.1%, on the Math & Validation page. A vendor who will not show you the math is asking for faith. We are asking for an inspection.
Our own MultiGP race team runs on these numbers. When the model is wrong, we crash — which is an unusually strong incentive to keep it right.
The security analyzer checks aircraft against an open, published verification standard — requirements anyone can read, dispute, and hold us to. Not a marketing checklist we grade ourselves on.
Choose a plan to create your account and start building. Every plan includes the full physics engine, build library, and reports.
Already have an account? Sign in
Accurate enough to order parts against — and you needn’t take our word for it. Every equation is re-derived in your own browser and checked against the engine: see for yourself, no account needed. Calibrate against one real hover and the numbers stop being generic and start describing your hardware.
It gives you the audit trail. Hours, currency, component life and authorization coverage are all calculated from the flights you actually flew, and every figure names the flights behind it. When an auditor or insurer asks how you know, you show them — instead of rebuilding it from a spreadsheet and somebody’s memory.
You get an answer in minutes instead of weeks. Upload the log and the Crash Analyzer gives you the event timeline, the final seconds, and the usual causes ruled in or out — as a report you can hand over. Confirm it against the raw log before you act on it.
In your private account, and nowhere else. No third-party AI, no external services. Exported reports are self-contained — they open in any browser with no connection and no dependency on us. Download or delete your stored logs whenever you like; neither ever needs a paid add-on.
There is machine learning, used carefully. A model trained only on your own fleet’s flights scores each new one against what normal looks like for your aircraft, and unusual flights wear an advisory badge that names the signals behind it. No score ever gates a flight, your data never trains anyone else’s model, and it all runs inside RotorLab: no third-party AI service ever sees your records. If you want your own assistant in the loop, point it at the read-only MCP endpoint and it can read your fleet records for you.
No. The Log Analyzer is free, needs no account and asks for no card. Drop in a .bin, .tlog or .ulg and read it now. Your file is never stored. Try that before you decide anything else about us.
Fourteen days with every feature switched on and no card asked for. Bring your real aircraft, pilots, and flights — a trial full of demo data tells you nothing. Two weeks in, you will know.
Size your next aircraft from real physics, then let the record build itself around every flight. Fourteen days, every feature on, no card.
Flight physics, fleet operations and what shipped — written for people who fly. No spam, unsubscribe in one click.
