What's new in RotorLab

The Fleet Server page now says what the on-premises software is for and that a new version is being built. It lists no features, dates or prices, and it is not on sale. The MAVLink/ATAK Bridge is no longer offered: its address now leads to the Fleet Server page, and the quote form offers no on-premises product for now. Quotes already filed keep their labels.

The RotorLab GC page now says only what the GC build on sale does. A command from the map is sent to the aircraft behind the per-verb switches and the master arm you set. The callsign list narrows whose commands are heard; a callsign is whatever the sending device reports, so the list does not prove who sent a marker. The page no longer describes Fleet Server as something you can buy today.

For on-premises software that checks its license: a license key can now carry entitlements, and the license service returns an entitlement signed by RotorLab that a box can check offline against its device. The public keys it is checked against are listed at /api/license/signing-keys. For a key that carries entitlements, a device id outside the allowed characters is now refused with a message, not trimmed, so a seat whose id breaks that rule is activated again. Nothing else about existing keys changes.

The Ops Manual's Download menu no longer wraps. Its draft item now reads Draft (PDF), marked DRAFT, and the PDF itself is unchanged. On a phone, the Import flight history menu on File Flights now opens to the right and stays on the screen.

As a member, the Add-ons card under What your organization has lists each add-on once. Fleet Manager reads Fleet Manager includes Fleet Health, and Currency reads Currency includes Training Programs.

Recent account activity on My Account now reads in words, such as Signed in, Sign-in failed, Password changed and Two-factor turned on, not the stored key. A screen reader hears a comma before the detail.

The permission grid on the Organization page now calls the row Types and Directives, the same words as the menu.

On the Security Analyzer's Aircraft tab, the summary now says how many stored logs are waiting and that the run assessed the newest ones, for example 3 of 4 stored logs waiting: the run assessed the newest 1. A button, Assess the other 3, assesses the rest, up to 50 at a time, and skips logs already assessed. On the Assess a log tab, an upload that is not one of your stored logs now says so, and that the aircraft's backlog does not change.

Flights opens with a Summary: flights by day, where flights took off, and the longest by time, with By aircraft, By duration and Farthest from takeoff one click away. Every figure is a count or a sum of filed flights. My Record gets Flights by day and Longest and farthest. A flight now shows the weather observation kept with it (wind, gusts, visibility, sky, temperature, altimeter), the station and time it came from, and what it was compared with. It states what the record shows and never clears a flight.

Report on these flights prints or saves a PDF, grouped by day with a subtotal for each day, from Operations, Maintenance, Part 107 or Custom columns. The pilot's Flight Log PDF uses the same day layout, with its words unchanged. Flights also filters by duration, highest point, distance, tags and a Drawn area, tags many flights at once, and exports the flights you filtered.

Each flight can carry the tags night, above cruise and cold battery. A tag is a measured value against a stated threshold, shown when you point at it, and a type with no cruise figure gets no above cruise tag. A flight also shows its Place, taken from your operating areas, the job's site or the flight's own site, never looked up elsewhere. Flights filed before this release have no stored track, so they carry no distance, above cruise or cold battery tag.

The aircraft reading that said Ready, advisory now says No flags, 2 notes (or No flags, 1 note). It stays green, and the notes are planning or setup items, named beside it. The line under every green reading says only what was read, such as defects, work, parts, tasks, bulletins past due and occurrences. It is a reading of your records, not permission to fly, and the remote pilot still decides before each flight. Ready with limits now says Limits on record, with the limit or open item named beside it. No go and Condition unknown keep their words.

An aircraft with no maintenance program and no flights on record has nothing to read it against. It used to show green. It now reads Nothing judged, in a neutral color, and the line names only what is missing. It is left out of the count of aircraft that read No flags or Limits on record. An aircraft that arrived with hours or flights counts as having flights.

Some aircraft that read green before now read Limits on record, because these are not planning notes: an aircraft with urgent work open, including a mandatory service bulletin open before its compliance date, whose work order is urgent; and an aircraft with a life-limited part whose flying before it was registered is not counted in its time, so its time is not known. The reason is named on the aircraft, and the open bulletin is named with its due date.

The fleet dashboard shows one green segment, No flags, with how many of those carry notes, beside Limits on record and Nothing judged. The count line now reads No flags or Limits on record, never available. Offline field kits, Dispatch, the register, Maintenance, the availability report and the aircraft record and Program status PDFs use the same words. The history strip and the availability report's column keep their meaning: a past day with limits or notes. Documents already issued keep their words and codes. A document issued from now on prints the new words and so carries a new code. In the API the state keys are unchanged (go, advisory, limits, no_go, unknown); only their labels change, and each reading now also carries notes, judged and missing.

Long record pages now open on tabs: the aircraft page (Overview, Work and defects, Life limits and dues, Health, Flights, Documents, Status history), the battery pack page (Overview, Health, Flights, Documents), the type page and My Record. The tab is in the address, so a link, a refresh and the back button land on the same tab, and old links to a section still land.

The Organization page has a new Team view, drawn from each member's Reports to. An organization admin sets Reports to when editing a member, and a line that would loop back on itself is refused. Admins and members who can view Members see the whole chart; any other member sees their own line up to the top and who reports to them. Every change is kept under History, and a person's lines clear when they leave, are disabled, or decline an invitation.

File Flights now reads what a log shows and holds it against your register, in one line before you save. What is new or different comes first, and what matches is folded into a tail. A match says only that the serials agree: a log can carry any serial, and RotorLab does not check the part or the aircraft. Maintenance can Add a part or Record a swap from the line, filled from the log. A member who files flights can Tell maintenance with one tap, and is never asked again about the same finding. A batch ends with one card per aircraft, and findings nobody has answered wait on the aircraft's Configuration under From the logs and on the Maintenance overview. A part that differs from the register, or that the register has on another aircraft, is dismissed by maintenance only. DJI camera serials, a telemetry log's autopilot id, and from an ArduPilot log the packs and the autopilot's CAN battery node (its name, unique id and version) and the smart-battery serial parameter are read. A telemetry log's parameters now come from the aircraft's own autopilot only, and whole-number PX4 parameters read correctly.

Packs added from a log: a clean 14-character DJI battery serial on an aircraft with one pack adds a pack marked To confirm, counted from that flight and filled from the catalogs where they know the model. It never reads green until a person confirms its details, with a cycle ceiling or a note that it has none, under their name and day. A doubtful serial asks on the filing line, and on an aircraft with several packs the line asks which pack the log names. One serial key now serves the flight form, Inventory and filing: case, spaces, dashes, dots and slashes are ignored, and retired packs are found too. Two records of the same pack can be merged: history and flights move to the kept pack, the counters are worked out again, and the merged-away record stays and says where it went. A pack has a retired date, and a retired pack is named from a log only for a flight on or before that day. Packs retired before this release have no retired date, so a log no longer names them by itself. A lent pack's gap, where its own counter is ahead of its flights here, shows, and a person closes it with a dated entry saying where it flew. A record that was never a pack is closed as such. The aircraft page lists the packs flown on it under Power, read only, and a printed pack label scans on File Flights to name a pack with no chip.

The green word for a battery pack is now No flags, not Serviceable, on the Batteries board, the pack page, Dispatch and the logbook. It reads: Inside its cycle ceiling, calendar life and health floor, with no damage recorded. It means the record shows nothing raised, not that the pack may fly. Unserviceable keeps its word and now reads: Recorded as swollen or damaged; not to be flown. The board's count reads 8 with no flags. Documents already issued keep their words.

Parts: a part's page has Correct the life, for the hours or flights it ran before RotorLab or the day it went into service, with a reason and where the right figure comes from. On a part with a life limit, a lower figure waits for a second person with Maintenance (manage) to countersign it, and nothing changes until then. The person who entered it cannot countersign it. Anyone with Maintenance (manage) can withdraw a waiting correction with a reason. An applied correction names who entered it, who seconded it and when, and Maintenance's Components tab lists the corrections waiting. A maintenance record that swaps two or more parts moves all of them or none. A place holds one part, at every kind of place, and a second part is refused with the part already there named. Replace every refuses a place that already holds two parts, so a person says which one came off. A place that still holds two parts says so on the aircraft's Configuration: remove the one no longer fitted, then replace the set. A part with no serial at a place kept by position reads By position and is not marked Untraceable. The Remote ID reminder names the paragraphs of 14 CFR Parts 48 and 89 it rests on. A change to a part's life limits is written to its history with the old and new value.

Your account: My Account has Verify your email. RotorLab mails a link, and the address counts as proven once you use it. An application that signs in with RotorLab as its OpenID provider now receives email_verified true when RotorLab holds a proof of the person's address: a mailed link they used, a confirmation from the organization's identity provider or directory on a domain proven through RotorLab's own mail, or the operator's one-time pass. Otherwise it receives false, which means not yet proven, not that the address is wrong.

Fixed: proving that your organization owns an email domain now sends the check through RotorLab's own mail, limited to 3 an hour and 10 a day for an organization, and the link is no longer shown on screen. Sign-in with your identity provider, directory provisioning and domain discovery keep working on every domain you have already proven.

The aircraft page has a Configuration: the places on the aircraft by system, set up by copying another aircraft, from its type or from a few questions. From the aircraft page you can Replace, Remove, Move or Fit a part, and each part is tracked by serial or by position, with one part per place. Every part has its own page with its history, and Go finds parts by serial or part number. You can attach files to parts, battery packs, defects and the aircraft.

One box fills a part's details from your own records. The type's places and the catalog are kept for the next aircraft of that type. Receive a delivery with a count and labels, or import a packing list and undo the import if it was wrong. A correction to a part's life is recorded with who made it, and a lowering needs a second person to countersign it. When a limited part moves between aircraft, the removal and the installation are written as a pair of records. After a module change, RotorLab reminds you of the Remote ID record to review.

A part taken off and put back on the same aircraft the same day no longer counts a flight filed later that day twice in its time since overhaul. A part at a by-position place reads by position, not Untraceable. An organization with no Part 135 certificate and no roster can release a maintenance record without an authorization number, and the record prints that none was named.

Fit and removal dates on a part are now checked. A date in the future, one that is not a real date, or one that falls before the part was in service, before its last removal or before its current fitting is refused with the reason. A new spare fitted with an earlier date moves its in-service date back to that fit, with a line on its history. A first fit dated before the part was received into stock stands, and the history says it was received on one day and fitted on another. A refusal says what day to use. A back-dated part at a position another part holds is refused, so a flight is never counted on two parts. A part with no serial now reads Untraceable the same on screen and on the aircraft report, the audit pack and the binder. Documents already issued keep their words.

The aircraft page shows the date the current fitting began and any hours and flights a part carried in from before, with where that figure came from, and its Add the parts fitted link lands on the parts list. A maintenance record is released once, even on a double click, and a record waiting for its inspector is not released past them. A refusal now comes before any part leaves the shelf. An airframe exchange made in the evening carries its parts on the organization's day, and a short notice names any part it left off, with a link to the parts.

Batteries: a retired pack's serial is not taken by a new pack (case and spaces at the ends are ignored), and a log filed late starts the pack's count at the right number. A telemetry log's firmware now comes from the aircraft itself. A part's history names the member who recorded it, never an address.

Regulatory Tracking is a new add-on, available on request. When RotorLab publishes a notice about a rule it follows, the Regulation Tracker shows it with the aircraft, aircraft types, manual sections, authorizations and credentials on your record that the rule names or that you recorded against it. Each notice quotes the official text, gives its dates and links to the source, and says nothing about what you must do. Your organization records its own response to each one, and the responses can be downloaded as a file.

The first eight notices are about FCC Covered List changes, the foreign-made parts rule, Section 232 duties on drone components, Part 89 and Part 48 false statement rules, the Part 108 proposal and an EU standard that is not yet cited. The tracker also lists what it does not cover. RotorLab publishes a notice when it chooses to, not on a schedule, and a notice is not legal advice.

An organization that holds the add-on gets an email when a notice reaches it, sent to its administrators. Turn it off under Notifications. The free tracker is unchanged.

Smaller: a citation written as a range, such as 14 CFR 107.1-107.299, is read as one citation that covers each section in it. The Ops Manual now says plainly that it does not check a citation against current law. The aircraft status history counts days with no flags, and the Builder battery field shows five digits.

Cards now line up on every page. A row of cards has one width and one height, three across on a wide screen, two on a tablet and one on a phone. A card that lists records shows the first three, then "and N more" as a link to the full list.

RotorLab reads your records. It does not clear a flight. The green reading is now No flags: nothing on record flags the aircraft, and that is not permission to fly. No go stays as it was. A credential, an authorization or a pilot's dates that have not expired read Not expired, and a certificate with no expiry under its rule reads No expiry by rule. Where the airspace data shows none, RotorLab says No airspace authorization indicated. A clean flight reads Nothing marked, a conformity inspection reads Recorded pass or Recorded fail beside the inspector's name, and a clean Security Analyzer result reads No findings. The fleet register no longer says an aircraft can fly. Your records do not change, and every document already issued keeps its code and keeps verifying. A document issued from now on prints the new words and so carries a new code. In a downloaded availability file, the column headed days go is now days no flags.

Reporting clocks and rule wording were corrected for South Africa, Singapore, Brazil and Japan, and the classification lines for the United States, United Kingdom, European Union, Canada, Japan and Singapore. A medical is asked of a South African pilot who holds a Remote Pilot Certificate or License, and of no one by default in Brazil.

Adding an aircraft slot on a purchase order now keeps the price you bought your slots at, on that invoice and at renewal, the same as a card. Two clicks at once add one slot and one invoice. If that invoice goes unpaid past its grace, only the slot it added stops working. The slots you already paid for stay on.

Smaller fixes: Dispatch opens faster for an organization with a long flight history, and its warning badge says what it counts. If your role cannot open a client, flight, battery, hazard or aircraft, the page says why and gives you a way back. A member with no name shows as a member, not by sign-in address, in the activity log and in more places across the app, to anyone whose role does not read members. A flight filed offline that loses its authorization record names the flight in the message you see. In the platform console, a custom-price order now keeps the item you picked, and Live activity has its rotating globe back. A live telemetry session no longer drops when the relay is busy.

Every record page now has a way back above its title, on desktop and on a phone. It takes you to the page you came from and names it, and a filtered board comes back with its filter. A job or client that does not exist now has a way back too.

On US inspection jobs and flights you can now record the approval you hold from a site's owner or administrator: the reference, who granted it, its dates and a note. RotorLab stores what you enter. It stays with the record, it does not print on a flight record or a client document, and it does not decide whether an approval satisfies a state's law. If a job is withdrawn, its withdrawn copy keeps the approval, and an audit package carries that copy. Public safety organizations billed in Florida also see a reminder on crowd monitoring flights, where they can name an authorization record or note where it is kept. It is a reminder only, and the flight saves either way.

The Launch sheet groups what it says about one person and keeps the warnings in view, and it now asks why you're flying. Your home page and record now say what is on record, such as "Current on record". On a flight's page, what stood at Launch has its own card, and a sortie that is out says the Launch reading again only when it has changed. If an authorization a job names is changed to a LAANC or airspace authorization, which RotorLab does not read on a job, the job's panel now says so and raises no warning from it. The name stays until you stop naming it.

A member who has no name on file no longer shows their sign-in address to people who may not read your member list, on occurrence records, the safety register, maintenance records, operating areas, logbooks, checklist runs, stock moves, batteries, manuals, possible duplicates and service difficulty reports, and over the API. They read as Member and a handle. Notices sent to a mailbox you nominate do the same. Documents already issued keep what they print, and their codes still verify.

A job can name the authorizations, operating areas and training roles it needs. RotorLab reads those records for the job's dates and each sortie, and warns on the job, on the sortie card and at Launch. It never stops a launch, and it does not decide what a job needs. Mark won shows how many pilots and aircraft read current for the job.

The Flights board, the job and client pages and the job list open much faster for a large organization, and deleting an organization's records holds the database for far less time. The no-purpose card on the Flights board now always matches the list it opens.

A member who has no name on file now shows as Member and their handle to anyone who cannot view members, on Dispatch, the Flights board, job and client pages, batteries, maintenance, training and occurrence lists, and no longer as a sign-in address in the words RotorLab writes (text someone typed, and coded documents, are outside this). On Dispatch, only a person who may read colleagues' records, the person themselves and the crew of that sortie see why a colleague has lapsed. Someone who plans sorties still sees that the colleague has lapsed. Documents already issued keep what they print, and their codes still verify.

Jobs now run the work from quote to invoice. Plan a sortie from a job and the pilot sees the site and the scope on the day, and nothing more of the job than they need. Mark a job complete and it names any sorties still planned. Mark it lost with a reason, give it your own job number, record what you delivered, and keep a bill-to address and contacts on the client. Set a follow-up date on a quoted job or a client and it comes up on the page when it is due, with a line that counts quoted, won and lost jobs and a timeline on each client. Record the date a job is billed through, and the client statement and the spreadsheet of a job or client (two files, one for the flights and one for the totals) say what changed behind that date and why. A new Client billing preset and a wider Chief pilot preset set who sees what. The organization export carries all of it: job numbers, addresses, contacts, deliverables and billed dates.

The Builder writes a Design report for any saved design: a numbered document with its principal characteristics, limits and margins, motor-out and hover figures, each with the basis it rests on, and a sign-off block. Send it, a design dossier or a Program status to a recipient from the aircraft type page, which shows how many times each went and to whom. A type page also shows what the aircraft flew against its design. Your own domain can try a send before you rely on it.

A pilot can share the licenses and certificates they hold with each organization they fly for, from My account, and the organization sees them marked as shared copies. The pilot can stop sharing at any time, and an organization can stop relying on a copy it was given. Because this adds to what we hold and say about you, you will be asked to accept updated terms the next time you sign in.

Program status adds a last-year view, with the dossiers you issued and how many times codes were looked up. Every document already issued keeps its code and its file check.

A job or client edit that changes nothing printed no longer marks issued records as changed at /verify, and a job moving from quoted to open or complete now reads as a status change, not a changed record. The public verification answer carries this as a new word, status_moved. For a job's flight record and a client flight statement, the page also says that any insurance printed is as it stood on the day of issue, and that it does not recheck it.

Two saves of one design at the same moment can no longer share a revision number.

Every document already issued keeps its code and its file check.

Signing in through your organization's identity provider now lands you signed in on the first page. Apps that sign in with RotorLab follow the same rules as signing in here, and see a confirmed email address as confirmed.

A payment now acts only on the order it was made for. Each product has one buy link that stays the same.

Many small fixes to labels, spacing and phone layouts, and new pictures on the Trust page.

A new organization's first sortie, or any change that reads today's date before it is saved, now answers at once. Before, it could pause for about 30 seconds while the organization's time zone was not yet on record.

The time zone is still recorded, on the next visit. Nothing else changes: your records, settings and pages are as they were.

The pricing page and your private plan link list each included add-on on one line that wraps under itself, and say in words what else an add-on opens, such as Fleet Manager for 3 aircraft, includes Fleet Health. A name is never repeated in brackets.

My Record keeps Run pre-flight in view at every width. The Flights board and an aircraft's Flights tab use the same words for a flight with no log file. The dashboard names aircraft by name, the battery record folds its trend charts on a phone, and the Audit page opens straight from the Organization pages. Status and Verify close with the short footer.

The Regulation Tracker, Public Reporting, Operating Areas, the Airspace Viewer and the Mission Planner read more simply: a column that holds one value on every row becomes one line, dates read in words, and the phone shows a dozen rules at a time. The engineering tools, the Log and Crash Analyzers, Compare Flights and the Security Analyzer got the same care: small files show in KB, figures show in your units, and tab rows fit or scroll. Tiles, tab rows, file pickers and labels line up the same way on every page.

The demonstration organization now resets cleanly even when one of its members has joined another organization.

Setup Wizard, Trade Study, Balance and CG, RF Link, Throttle Simulator, Model Calibration, Math and Validation and the Parts Library now put the answer first: the verdict sits at the top, a button that cannot be pressed says what it needs, long charts open full screen on a phone, and the equations and figures scroll in their own boxes. The Log Analyzer, Crash Analyzer and Compare Flights open on your flights with a stored log, newest first. Live Telemetry leads with your relay devices, and the Security Analyzer opens on your fleet.

The Regulation Tracker groups rules by jurisdiction with the next date first, and its change log shows the last 90 days with Show older. Public Reporting leads with its state and the one thing still missing. The Ops Manual leads with the manual and the block to review. Operating Areas shows Classify in the row, an area record links its jobs, and the Airspace Viewer starts with its search and a map. The Mission Planner opens where you fly and lists your three most recent missions under the map.

Single sign-on now takes you to your identity provider; before, the sign-in could not leave RotorLab. An organization behind a broker, such as Microsoft Entra External ID, can turn on sending the email domain as a hint. A card payment now activates only the order it was made for, and for the amount that order charges; any other payment waits for review. The Organization pages show dates and activity in words, and every section address opens its own section. The sign-in, invitation, Plan ended, status and verification pages share one look, and the Plan ended page now names your administrators.

The menu is in a new order: Ops Dashboard, Flying, Safety, Planning, People, Aircraft, then Records. Occurrences and Safety Management sit right under Flying, Authorizations moved to Planning, Public Reporting moved to Safety, Maintenance follows Aircraft, and Records starts folded. Types and Bulletins is now Types and Directives. The records-to-check lists are together on Retention and Holds, and Flights has a Checklist runs view.

Pages put the figures above the list they count, and a table cell holds one line, with the detail one press away. On a phone, tables read as cards. Dates read in words, such as Fri Oct 23, 2026, in place of 2026-10-23, and charts label their days the same way. Crew shows who is flying outside standing by name, and Training has a Sign off button on a lapsed cell. Clients and Jobs, occurrences, safety, authorizations and the aircraft record were rearranged the same way. On the Organization page, Export and binder is now Export and closing and Documents sent is now Recipients; roles read one line each, and sign-in labels sit above their fields.

After a card payment, the return page says "Payment submitted" and shows the real status of your order, the plan and the total, and tells a new buyer to check their email. The Plan ended page is the one notice of that state, and it fits a phone.

Pages now lead with what you came for, and a page no longer says "All clear" beside a card that is flagged: when something is live, the rest reads "Nothing else". My Record shows your own records. On Maintenance, "Closest to a limit" lists the worst part first and leaves scrapped parts out. The Setup Wizard counts read with the number first.

Tables keep one line per cell, with the detail one press away behind Why, and their headers stay in view as you scroll. Long record tables show the newest 10 rows, with All to see the rest. Batteries puts its summaries first. Dispatch quiets Launch on a sortie that is not cleared. Live Telemetry lists your relay devices as soon as it opens. The Plan page opens with nothing selected, so you choose before anything changes. On Retention and Holds, "pilots with credentials" no longer counts device and door accounts. The Dashboard's Jobs tile counts open jobs and names quoted jobs apart. Your record lists only the checklists you signed.