RotorLab logo RotorLabDocs

Fleet Manager

The Fleet Manager at https://rotorlab.app/fleet is your aircraft registry. Each airframe holds its own record: name, tail number, serial, model, an optional source build, and the flight history that accumulates against it. Flight time and flight count are derived from the flights filed against the aircraft, never typed.

The registry is the per-aircraft product: Fleet Manager is billed per slot, one slot per registered airframe. If the add-on is not on your account, the page says so and links to the add-ons section of your account.

The overview#

The page opens on where the fleet stands, all of it counted from the flights: how many airframes are available and how many are in maintenance, the hours and flights of the last 30 days, the hours on record since your first filed flight, and how many registrations are expired or expiring.

Below that, Fleet flying over the year plots twelve months, bars for hours and a line for flights, with every month drawn whether or not anything flew in it. Where the fleet stands counts each status, and Busiest airframes ranks hours over the last 30 days. An amber bar there is an airframe that was logged by name and never registered.

Worth a look raises four things, and none of them is a fault:

  • a registration that has expired, and one expiring within 60 days;
  • an airframe with nothing filed against it in 90 days, or nothing ever;
  • an airframe with no airframe type stated, which is what the aircraft page draws from.

An airframe with no registration on file is not raised: RotorLab never requires a registration to fly or to file, so a blank field is "not recorded", not "overdue". A retired aircraft is never called idle either; it is finished, not parked.

Each entry opens that aircraft's own page.

Registering an aircraft#

Press Register an aircraft:

  • Name: required, unique within your organization, up to 80 characters. This is the name flights attach by.
  • Registration: the tail number, for example N123AB.
  • Serial: the airframe serial.
  • Model: for example Freefly Alta X. Aircraft of the same model are compared against each other on the Fleet Health page.
  • Remote ID: the broadcast module serial. Optional; recorded so you can produce it on request without reading it off the airframe. RotorLab never checks it and never requires it to fly or to file.
  • Build: link the aircraft to a saved build from your library, so one design can back many airframes.
  • Status: Active, In maintenance, or Retired.
  • Notes: free text.

Registering consumes one Fleet Manager slot. The aircraft row and the slot are written together; if no slot can be taken, nothing is registered.

Flights filed before you registered

If flights were already filed under this name (as free text, from the logbook or a ground station), registering an aircraft with the same name adopts them: the hours, the health trend, and the maintenance clock all start from the history that already exists rather than from zero.

Only an organization admin registers and edits aircraft. Members see the fleet read-only and can still file flights against it.

Slots and per-aircraft billing#

An aircraft slot is what a subscription pays for: your organization holds a number of slots per feature, and each aircraft the feature is switched on for spends one. The card at the top of the page shows each per-aircraft feature as a pill, for example "Fleet Manager: 3 of 5 slots" or "Fleet Health Monitoring: not enabled". An entitlement with no seat cap shows as covering all aircraft.

  • A registered aircraft always holds a Fleet Manager slot. Removing the aircraft frees it.
  • Other per-aircraft features (Fleet Health Monitoring) are switched on and off per aircraft with the checkboxes in the Covered for column. Switching one off frees its slot straight away.
  • Buy more slots under the add-ons section of My account.

When every slot is in use and you try to register another aircraft, the page prices one more slot on the spot and spells out exactly what you will be charged before you confirm. On a one-time purchase you buy one additional slot; on a monthly or yearly subscription the subscription quantity moves to cover the whole fleet, and the confirmation states the new total. After payment you are brought straight back and the registration finishes automatically.

The register#

Each row shows the aircraft name and serial, Registration (with its expiry and the Remote ID serial beneath it when recorded), Model (with the airframe type), Status, Flights, Hours, Last flown, and Covered for (the per-aircraft feature checkboxes). The name opens that aircraft's page; edit beside it opens the registration dialog; a health link jumps to that aircraft on the Fleet Health page.

Search matches the name, registration, serial, model, Remote ID and airframe type. The status list narrows to one status, and every column with a header you can click sorts by it: click again to reverse. Numbers and dates sort largest-first on the first click, names A to Z.

The flight-record spine#

Every flight filed in the Pilot Logbook or by a connected ground station that names a registered aircraft becomes part of that aircraft's record. That spine is what everything else hangs off: airframe hours, health trending, component life, and maintenance history.

A card above the table surfaces unregistered flying: flights filed against airframe names that no registered aircraft carries. Those flights are logged and counted in your reports, but they build no airframe record. The card lists each name with its flights, hours, and first and last seen dates, and a one-click Register button per name so the existing flights attach the moment the aircraft exists. If no slot is free, the button prices one, takes you to payment, and registers the airframe automatically once the payment clears.

Status and retirement#

Set an aircraft's status to In maintenance while it is down; the Ops Dashboard's availability tile counts it separately. Set it to Retired when it leaves service: retired aircraft keep their whole record and are hidden from the table unless show retired is ticked.

Remove deletes an aircraft only when it has no filed flights. An aircraft that has flown cannot be deleted; the page tells you to retire it instead, so its flight record is kept.

Logs, the free analyzer, and the paid one#

Storing a flight log against an aircraft is free and never metered, and you can always download or delete your own files. Reading a log is the paid act, and there are two readers:

  • The free Log Analyzer reads a log you upload in the browser, for example to pre-fill a logbook entry. Nothing is kept.
  • The paid Crash Analyzer produces the full diagnosis, and Fleet Health Monitoring reads stored logs automatically for the aircraft it is switched on for. A stored log on an unmonitored aircraft stays stored and downloadable; reading it later needs Fleet Health on that aircraft or the Crash Analyzer on the account.