RotorLab - Drone Fleet Management, Flight Logs & Performance

Design it. Fly it. Prove it.<br>Know what your fleet is doing. Prove what it<br>did.

Drone fleet management built on real flight physics. Hours, pilot<br>currency, component life, insurance, and safety records assemble themselves from the<br>flights you actually fly — so the audit trail is ready before anyone asks<br>for it.

Create your account<br>See it in action

Nothing to install · runs in your browser · your data stays private to your account.

45<br>data points per flight

16<br>airframe types supported

±0.1%<br>equations cross-checked

TWR<br>3.8 : 1<br>hover<br>18.6 min

Live readout recomputing

Quad X · Quad H · Tricopter · Hexa · Y6 · Octo · X8 · VTOL transition

Where your morning starts<br>The Fleet Ops Dashboard

Your whole operation on one page, read from your own records.<br>Included with every plan.

{{ic_grid}}

The numbers, up front

Hours, flights, aircraft available, what is grounded, what is open in the<br>safety log. Same place every time.

{{ic_chart}}

Flying, charted

Activity over any period, with hours ranked by aircraft and by pilot.

{{ic_alert}}

What needs you today

Grounded airframes, parts at a life limit, lapsed currency, expiring cover,<br>occurrences past review.

{{ic_check}}

Your layout, not ours

Operations, Maintenance, or Compliance views — or pick your own panels<br>and order. Yours alone; it does not move anybody else&rsquo;s.

{{ic_shield}}

A day you can prove later

Export any period as a signed, verifiable PDF — what an insurer or an<br>auditor asks for.

{{ic_pulse}}

Straight to the work

Every panel opens the page behind it, so you land on the aircraft or the<br>record that needs you.

End to end<br>From the sticks to the audit trail

Your ground station talks to a Fleet Server on your own network, which feeds<br>ATAK in real time and files the flight to RotorLab when it is done. The Fleet<br>Server is the only thing holding a RotorLab key and the only thing that reaches<br>the internet — so a station lost in the field carries nothing that opens<br>your account.

Fleet Server ============ -->

MAVLink<br>your network

RotorLab ============ -->

Fleet Server Cloud<br>HTTPS &middot; /api/v1

ATAK (live) ============ -->

CoT, live

RotorLab GC<br>Ground station in the field<br>Holds no credential

Fleet Server<br>Buffers, caches, holds the key<br>Runs on your own network

RotorLab.app<br>Your system of record<br>Hours, currency, compliance

ATAK<br>Live tracks and sensor footprints

Flights, telemetry, and live tracks out

Roster, registry, and checklists back down

The left-hand box, for real: RotorLab GC flying the aircraft.

And the arrow coming back: your roster and its currency warnings,<br>at the launch point.

RotorLab TAK Fleet Server

Runs on your own network. Talks MAVLink to your aircraft and ground stations,<br>pushes live tracks to ATAK, and files finished flights to RotorLab — queuing<br>them when the link is down.

Fleet Server &rarr;

Fleet Server Cloud

Not a product — a switch inside Fleet Server. Paste a RotorLab Device<br>Key and flights, checklists, and logs start filing themselves. Needs a licensed<br>Fleet Server and a RotorLab subscription; costs nothing on top of them.

How the link works &rarr;

RotorLab MAVLink/ATAK Bridge

Any ground station onto the TAK network. Every aircraft on it becomes a live<br>MIL-STD-2525 track, and a named map marker sends GOTO, RTL, LAND, or HOLD back.<br>Licensed per workstation, unlimited aircraft.

The Bridge &rarr;

verification -> flight -> running a program. That was the right<br>order when RotorLab was a calculator that had grown an operations half.<br>It is now a fleet operations product that happens to own a very good physics<br>engine, and the running order says so: the operator meets the dashboard and<br>these records first, and the physics arrives later as the reason to believe<br>the numbers. An operations manager should not have to scroll a quarter of<br>the page to find their own product. -->

Underneath it<br>The audit trail builds itself

Hours, currency, component life and coverage all answer one question: what has this<br>fleet flown? Every figure is calculated from your own flights and names the ones it<br>came from.

{{ic_logbook}}

Flight log & currency

Every flight is one record — typed in, read from a log, or filed by a ground<br>station. Hours and currency follow. A missing date reads unknown, never expired.

{{ic_wrench}}

Maintenance & component life

Serialized parts with limits in hours, cycles, or months. Life is spent by flying,<br>and a part&rsquo;s history follows it to the next airframe.

{{ic_shield}}

Authorizations & reporting

Waivers and certificates with what they cover and when they expire, plus the<br>recurring reports built from flights already on record.

{{ic_book}}

Operations manual

A manual whose live sections read your real roster, aircraft, and limits. Publish a<br>revision to freeze what you approved — and hear about it when your records<br>drift away from it.

{{ic_pulse}}

Fleet health & forensics

Vibration, pack sag and motor balance...