Authorizations

The Authorizations page at https://rotorlab.app/coa records the permissions you operate under (COAs, waivers, and any other operating authorization), which aircraft each one covers, and when it expires. It also builds each authorization's operations report directly from the flight records already on file for the covered aircraft, so there is nothing to tag and nothing to forget.

RotorLab does not determine your regulatory obligations. You set the reporting period, you decide what is reportable, and every figure in a report cites the flights it was calculated from. The same page also carries an Airspace section and an Insurance section, described below.

The overview#

The page opens on four tabs: Overview, Authorizations, Insurance and Airspace. The overview reads across all of them.

The figures count both records together, because "what has lapsed" is not a question about one of them. An authorization or policy inside its notice window still counts as in force: it is valid today, and a board that said otherwise would report nothing valid on the day the notice window opened.

Renewals, soonest first is every expiry date you have on file, on one run: authorizations, insurance policies and aircraft registrations. Anything already past sits at the top with how many days ago it lapsed. The bar is how far off each date is across the year, so a month with four renewals in it looks like a month with four renewals in it. A record with no expiry date is not on this list. It is untracked rather than due, and putting it on a list of dates would invent one.

Aircraft not named on any authorization and Aircraft not named on any policy list the airframes that are registered, in service, and named on nothing that stands today. Plenty of flying needs no authorization at all, so these say what your record shows, not what you need. Each name opens that aircraft.

The authorizations list searches across title, number, authority and area, and narrows by standing.

Recording an authorization#

Press Add an authorization. The form takes:

Covers matters: only flights on the ticked aircraft are counted in this authorization's reports. An authorization with no aircraft shows a warning on its card and produces empty reports until you say what it covers.

An organization can hold up to 200 authorizations.

Renewal tracking and expiry warnings#

Every authorization carries a standing computed from its dates:

• Current: valid, with days remaining shown.
• Renew soon: expires within 60 days. The card and counter turn amber.
• Expired: past its expiry date, shown in red with days since.
• No expiry on file: no expiry recorded. This is not a claim that it is valid and not a claim that it has lapsed; add the date and RotorLab tracks the renewal.
• Not yet in effect and Surrendered for the remaining cases.

The counters at the top of the page total each state. On the Ops Dashboard, the Authorizations tile (part of the compliance preset) surfaces the same standings, and the Ops Manual reads the authorizations held into its live "Airspace authorization and waivers" block.

Operations reports#

Press Operations report on any authorization. The report is derived, never typed: a flight belongs in it when it was flown on a covered aircraft inside the reporting window. By default the report covers the last completed period of the authorization's reporting cadence; change the From and to dates and press Rebuild for any other window.

The report shows totals (flights, flight time, sorties, landings, night flights, aircraft flown, pilots), breakdowns by aircraft and by pilot, the sites flown, any flights with a crash detected in their logs, and the full flight list. A basis statement says plainly what was counted: the flights on record for the covered aircraft in the window, and how many registered aircraft the authorization does not cover.

Download text saves a plain-text rendering for pasting into whatever the authority wants; Download PDF produces the document that gets filed.

Airspace#

The Airspace section reads your filed flights against the FAA's published airspace data and reports four counts rather than one percentage: flights that needed no authorization, flights with an authorization recorded, flights missing one, and flights that could not be determined (no position on record, or no airspace data loaded on the install). Flights inside a standing flight restriction get their own warning, and the section shows which airspace charting cycle the data came from.

RotorLab is not a LAANC provider and issues nothing. This section reads the confirmations your crews recorded and says how much it could not determine. If no FAA airspace data is loaded on the install, every flight reads as undetermined and the page says so.

Insurance#

The Insurance section records what you hold and when it lapses. A policy takes a title, policy number, insurer, broker, coverage kind, status, inception and expiry dates, liability, hull, and deductible limits, the certificate holder, territory, exclusions and conditions, notes, and the aircraft named on it (leave all unticked if the policy covers the operation rather than a list of airframes).

Policies carry the same date-driven standings as authorizations (In force, Renew soon, Lapsed, No expiry on file, Not yet incepted, Cancelled), and a warning card leads the section when registered aircraft are not named on any current policy. That card says only that those airframes are not on a policy in force today; whether they need to be is a question for your broker and the contract. Each policy has a Summary link that opens a printable summary.

Related#

• Fleet Manager
• Ops Dashboard
• Ops Manual
• Public Reporting