RotorLabDrone fleet management built on real flight physics. Hours, pilot currency, component life, insurance, and safety records assemble themselves from the flights you actually fly — so the audit trail is ready before anyone asks for it.
Nothing to install · runs in your browser · your data stays private to your account.
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.
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, and a part’s history follows it to the next airframe.
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 across every flight, 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.
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.
Most calculators multiply a fixed efficiency constant by weight. RotorLab computes hover power from actuator-disc theory — so prop size, air density and payload move the numbers the way they do in the air.
Induced power per disc from T1.5 / √(2ρA), summed across rotors and divided by figure of merit. Disc loading and density drive the result, with a coaxial penalty when stacked.
Set a flat-plate drag area and get a full induced-plus-profile-plus-parasite power curve: best-endurance speed, best-range speed, cruise range, and a thrust- or power-limited top speed.
Tailsitter-style craft whose airfoil arms become a wing in cruise. Reports stall and transition speed, wing loading, cruise endurance, and whether the thrust-borne phase can accelerate past stall.
Model packs feeding named buses, parallel packs that add capacity, and dedicated avionics batteries. Every BEC/UBEC rail is checked against its regulator and folded into endurance.
Drop in flight controllers, companion computers, AI accelerators, cameras, thermal, LiDAR, GPS, and radios — each wired onto a rail at the right voltage, with mass and draw fully editable.
Air density from the ISA model at your altitude and real temperature. Hot-and-high is the worst case for any rotorcraft, and the endurance and thrust penalty shows up directly.
Animated power-distribution diagram, mass breakdown, hover-power split, current-vs-limits, and endurance sweeps — exportable as a self-contained HTML report that opens anywhere.
A Math & validation page writes out every governing equation and re-evaluates it independently in your browser, confirming the engine agrees to within 0.1%. Change an input, everything rechecks.
A guided wizard walks every input in logical order, then the live console lets you tune anything and watch the readout recompute.
Airframe and type, props, motors, battery, ESC, payload, and environment — each field has a one-line note on what to enter.
AUW, thrust-to-weight, hover, and cruise endurance, top speed, disc loading, and limit checks update as you type.
Enter measured max thrust and hover current, tune figure of merit, and the numbers become specific to your hardware.
Keep builds in a private library, export profiles as JSON, and download a self-contained HTML report to share.
A console on the left, a readout on the right. Stat cards for the headline figures, an animated diagram showing where the power goes, and a checks panel that flags problems before you order parts.
From workshop test stands to FPV, VTOL transition, and field survey, RotorLab models the rotorcraft you actually fly.
Automate analysis and manage your builds from scripts, notebooks, and apps. Personal API keys, a versioned /api/v1, a daily quota plus purchasable credits, and an OpenAPI spec and Postman collection ready to import.
curl -H "Authorization: Bearer rl_..." \
-X POST https://your-instance/api/v1/analyze \
-d '{"airframe_type":"Quad X","motor_count":4}'
→ { "out": { "twr": 3.8, "hover_min": 18.6, ... },
"checks": [ ["ok", "ESC within rating"] ] }
Start free, add only what you use.
Not demos. The real tools, free forever — no card.
Drop in any ArduPilot, MAVLink, or PX4 log and read it in seconds — every mode change, event, and error on one timeline. Your file is never stored.
Read a log nowEvery equation we use, re-derived in your own browser and checked against our engine. Don’t take our word for the physics.
See the mathEvery report we issue carries a code. Your insurer or client enters it and confirms the document is genuine.
Verify a documentOur ground station, free to download and free to license. Connect it and flights file themselves into your logbook.
RotorLab GC →Your whole operation on one page. Pick a view, pick a period, export the day as a signed PDF.
Hours totalled per client, job reports you can hand over, and the safety record beside the technical one.
Hover power, endurance, thrust-to-weight, cruise, and range — across 16 airframe types, from the physics.
Fly the build before you buy the parts. Climb, cruise, hover, and drop, with wind and reserve.
Place every component and see exactly where it balances, to the millimeter.
How far your control and video links actually reach, from the standard equations.
Sweep one variable and watch endurance, range, and efficiency respond. Find the pack that hits your target.
Every flight, one record — typed in, read from a log, or filed by your ground station.
Add any of these to any plan. Fleet Manager and Fleet Health are billed per aircraft; the rest are one price for your whole organization.
Know what every airframe has actually flown. Hours and counts accrue from the logs filed against it.
Catch the motor going bad before it takes the aircraft down. Vibration, sag, and balance trended across every flight.
Answer “what happened” in minutes, not weeks. The timeline, the final seconds, and the usual causes ruled in or out.
Never fly a part past its limit. Life is spent by flying, and a part’s history follows it between airframes.
Know who is current to fly today, measured against your own rules, from each pilot’s record.
Never miss a renewal. Waivers and certificates with what they cover, when they expire, and the recurring reports built for you.
A manual that reads your real roster, aircraft, and limits — and tells you when your records drift away from it.
Watch a flight from anywhere in your browser. The aircraft dials out — no ports to open.
Call types and position handling for public-safety flying, plus a transparency portal you approve period by period.
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.
No, and that is deliberate. The aircraft dials out over an encrypted connection, so there are no inbound ports, no port forwarding and nothing new exposed on your network. Each channel is keyed to your account.
Sixteen types. Multirotors: Quad X, Quad H, Tricopter, Hexa, Y6, Octo, and Octo X8. Fixed wing: tractor, pusher, and twin. VTOL: transition, three quadplane layouts and two tiltrotors — hover physics for the lift rotors, wing-borne for cruise.
Yes, and most do. Everyone keeps a private build library while the organization keeps one set of flight, aircraft, and maintenance records — so the fleet has a single history no matter who flew. Team carries 10 users, Studio 50.
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.