What's new in RotorLab

The Builder takes an optional rated motor power and ESC current limit; with one set, full throttle stops there, and the thrust, current and wiring checks read that point. Builds without them calculate exactly as before. The aircraft catalog adds the Agras T55, T60, T70, T70P, T70S, T100, T100S and the FlyCart 100, now 96 DJI aircraft, and every aircraft DJI publishes a motor rating for uses it. Where DJI publishes a top speed, the model's drag is fitted to it, so the speed figures match DJI's own.

The Builder can start from 88 DJI aircraft, from the Mini to the Matrice and the Agras. Every figure says where it comes from: DJI's published specification, another named source, our estimate, or a fit to DJI's rated hover time, and the model's hover time is compared with DJI's own. Registering an aircraft can pick the model from the same catalog. Sign-up asks two optional questions, what describes your organization and whether you build or buy your aircraft, and the setup guide follows your answers. Add-ons can be chosen at sign-up on a paid plan. Public-safety and DFR programs can request a purchase-order quote from sign-up and the pricing page. The sign-in pages use the new design. An aircraft whose defects, work or other records cannot be read now shows condition unknown, never ready to fly. A published transparency period can only be changed by a correction that says why, and the earlier copy stays public. Public-safety organizations are asked to choose how long exact flight positions are kept.

The free Log Analyzer reads your first log straight away, with nothing to fill in. After that it asks once for an email address, with no link to open, and the analyzer stays open in that browser. Under every reading you can have it emailed to you, or save it to a free account. About RotorLab now introduces the leadership and the team, and the partner logos show in light and dark mode. The Privacy Policy is updated to describe the analyzer as it now works; you will be asked to accept it the next time you sign in.

An event page now opens with the date, the place, what a ticket costs and two buttons: Get tickets and Get directions. On a computer the tickets sit beside the description and stay in view as you scroll; on a phone they come straight after the event. The welcome page shows the matching screen from the app for each stage again: the Builder, the Ops Dashboard, Fleet Health, Maintenance and a program report.

Four new pages: safety management (the hazard register, risk acceptance and the flight-data signals behind it), the operations manual builder, Part 107 recordkeeping (what an operator keeps and how each record maps to RotorLab) and About RotorLab. The public pages load faster on a phone, read more clearly with stronger text contrast, and each event now has a page of its own with its date, place and tickets in search results. The release notes and newsletter can be followed as feeds, and the Data Processing Addendum and the Government Customer Addendum are linked from every page.

Each event page opens with the event, when and where it is and a ticket button, then the description, the prizes drawn on the day, the ticket types with the order form beside a short explanation of how tickets work, and a map with directions. The ticket page carries the same design, with the scan code large and clear in light and dark mode and when printed. Events now sits in the top bar beside Docs and Developers on every public page.

Signing in opens the console you work in. A dashboard opened by an account with no organization now says so and offers the right place, instead of asking for records it cannot show.

Audit and evidence now shows what you hand over: the package and its manifest, a Program Status report, a Flight Records register, a pilot's Flight Log, a Maintenance Log and the public check at rotorlab.app/verify, each with its sections boxed and explained. Click any section to read what it shows, where it comes from and why the regulator, the insurer or the customer reading it cares. The documents are from a demonstration organization. The sample downloads are now one document: a short sample pilot logbook whose code checks at rotorlab.app/verify, so anyone can try the check with a real file. The sample dossier, performance report and audit binder downloads are retired; the audit page shows what those contain. Starting a trial no longer passes through the pricing page: the sign-up page opens on the trial, and a different plan can be picked right there. The contact page is rebuilt in the new design with the new postal address, and the public pages use the width of a large screen.

The Program status PDF printed the Aircraft table's Time heading over Open defects. Every table in every RotorLab PDF now gives each heading its own room, so the program status, aircraft availability, flight records, audit binder, maintenance log, security and design dossier reports read cleanly at the top of each table.

How we validate opens with what it is for and the counts in one row; its fourteen topics sit in fold-outs that name how many checks matched, with every equation, derivation and reference still there. Release notes show the newest release in full and every earlier one by month, with a search. Coverage and the Security Analyzer page lead with what you get and keep the detail in fold-outs. The legal documents gain a section index beside the text, unchanged. The newsletter and events pages say what will appear when there is nothing yet, and the developer page folds its endpoint table by area.

Evidence now opens with the run's headline figures in one row, then five short sections: how the readers and diagnostics were measured, every claimed format file by file, the scripted flights with planted faults, the same files through Fleet Manager, and how to reproduce it. Every number is still written by the dated validation run, and the per-format commentary, the check coverage table, the airframes and the sources sit under fold-outs for the evaluator who wants them.

The Trust Center now opens with eight answers a security reviewer looks for first, with every commitment kept in full under The specifics, one section per topic. Pricing, the pages for manufacturers, fleet operators, public safety, film and custom builds and education, and the Fleet Server, RotorLab GC, ATAK Bridge and Developers pages are rewritten the same way: a short promise, real screenshots, and the detail an evaluator needs in a table or a fold-out instead of a column of paragraphs. Headings no longer wrap mid-sentence, and every page reads on a phone without sideways scrolling.

The pages around the new front page now look like it: Pricing, the Trust Center, Status, Developers, Verify a document, RotorLab Racing, Partners, Education, the pages for RotorLab GC, the Fleet Server and the ATAK Bridge, and the pages for manufacturers, fleet operators, public safety and film. Each opens light, with the switch to dark at the top, and says everything it said before. Every public page, from the release notes and the newsletter to events, coverage, the legal documents and the free Log Analyzer, now has the same header and footer, so Trust Center, Status, Docs, Developers, Pricing and Contact sales are one click away wherever you are, and the footer lists every product, industry and resource.

The front page at rotorlab.app is new: one record per aircraft, from the first drawing to the audit, with the five stages of an aircraft's life (design, fly, monitor, maintain, prove) one click apart, the teams that work from the record, where RotorLab runs, and the technical resources an evaluator reads first. These pages open light, with a switch to dark at the top. Each part of the platform has its own page: Design, Flight records, Fleet health, Maintenance and Audit and evidence, each with real screens of the product, how it works, what it can do and the specifics a technical lead will want to check. To talk to someone about your program, rotorlab.app/contact-sales reaches the sales team, and a person replies by email. Support stays at rotorlab.app/contact.

The Records page opens on At a glance: details recorded, flights with no stated purpose, records older than your window, open legal holds, what was disposed of and what was withdrawn, each a click to its section. Under it, Needs attention says what to do next. The sections sit on tabs: Completeness, Calls, Schedules, and Holds and disposal. On Authorizations, every tab reads the same way: the heading and what it is for, the figures, then one bar with the add button first and search beside it. Insurance has a search of its own, across title, insurer, policy number and aircraft. On the Ops Dashboard, Your account has its own box between the setup guide and Readiness, and Hide puts it away until you bring it back.

Record an occurrence now sits at the top of the Occurrences page, so you can record one from either tab. The Overview opens with Record what happened: choose the kind of thing that happened, such as a near miss, a link loss, a flyaway or a battery that swelled or heated, and the form opens with it filled in. When nothing is on record yet, the page says what is worth writing down instead of standing empty.

My Account now holds only what is yours: your profile, preferences, sign-in security and your data. Everything your organization sets up has its own page, Organization: people and roles, settings, data and privacy, integrations, billing and support access, each section one click away in a menu down the side. A search box at the top of each menu, also opened with Ctrl+K, finds any setting by its name or a word you would use for it (SSO, 2FA, invoice, webhook). Old links and bookmarks still open the right place.

RotorLab is the Official Crash Analyzer of MultiGP: when a race quad comes down at a MultiGP event, this is what reads the log, from the club track to the 2026 MultiGP Championship. Events are now one click away: Events is in the home page menu and the footer of every public page, and the racing pages link to upcoming events. An event is now limited only by its ticket types: a ticket type with no limit set never runs out, and an event reads Full only when every ticket type is gone.

In the United States, Part 107 asks for an airspace authorization in Class B, C and D airspace and in Class E only within a surface area designated for an airport. Class E that starts at 700 or 1,200 feet, which covers most of the country away from airports, was reported as needing one. A flight filed there now reads as controlled airspace above its floor with no authorization needed below it, and the summary says why. Class E surface areas, Class B, C and D, and every place the FAA publishes a UAS facility map still read as needing one. Flights filed before this release keep the reading they were filed with. Airspace zone feeds added in the admin console are now used in airspace checks as soon as they refresh. A flight's Airspace at filing now names the day the airspace data was downloaded, and the warning that the data was older than one 56-day charting cycle appears only when it really was; flights filed before this release no longer show that warning, because their stamp did not say when the data was downloaded.

The detailed FAA class airspace, special-use and security restriction layers are now downloaded in smaller pieces, so their refresh runs steadily in the background without slowing anything else down. The airspace your flights are checked against is unchanged.