> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt
> Use this file to discover all available pages before exploring further.
# How to Use Operations Analytics
> Interpret KPI cards, navigate sub-tabs for fleet, crew, and financial data, identify anomalies, and run free-form queries against your operational data.
By the end of this guide, you will have interpreted KPI cards, navigated sub-tabs for fleet, crew, and financial data, identified anomalies, and run free-form queries against your operational data.
The Operations module must be enabled for your workspace. You also need the appropriate operations
permissions. Contact your workspace administrator if you cannot access these features.
You need any ops access role. Financial charts additionally require the `accounting.read`
permission and financial access.
## Navigate to Analytics
Open the Operations sidebar and click **Analytics** under the
**Analytics & Reports** group.
**Breadcrumb path:** Ops > Analytics
The landing page is the operations dashboard. Six sub-tabs are accessible from
the navigation cards in the middle of the page: Fleet Utilization, Crew
Analytics, Financial, Customers, Route Profitability, and Data Explorer.
## Set the date range
The date range tabs at the top of the dashboard control all charts and KPI
calculations on the landing page. Sub-tabs have their own independent date range
controls with the same options.
| Option | Window |
| ----------- | ------------------------------ |
| **7 Days** | Rolling last 7 days |
| **30 Days** | Rolling last 30 days (default) |
| **90 Days** | Rolling last 90 days |
| **1 Year** | Rolling last 365 days |
The selected range is appended to the URL as `?range=30d` (or `7d`, `90d`,
`365d`). You can bookmark a URL with a specific range to return to the same view.
For monthly operational reviews, use **30 Days**. For year-end performance presentations, use **1
Year**.
## KPI cards
Six KPI cards appear at the top of the dashboard. Each card shows the current
value for the selected date range, a sparkline trend, and a delta badge comparing
the current period to the equivalent prior period.
| KPI | What it measures | Delta behavior |
| ------------------------ | ------------------------------------------------------------ | --------------------------------------- |
| **Total Flights** | Count of all trips departing in the period | Up is positive |
| **Flight Hours** | Sum of block time across all trip legs | Up is positive |
| **On-Time %** | Percentage of completed and active trips vs. total | Up is positive |
| **Fleet Utilization** | Average block hours per aircraft per day | Up is positive |
| **Dispatch Reliability** | Completed trips as a share of completed + cancelled | Up is positive |
| **Open Squawks** | Current count of open discrepancies (point-in-time snapshot) | No delta -- squawks are not date-ranged |
The delta badge shows percentage change from the prior period of equal length. A
green badge means improvement; red means decline. The **Open Squawks** card has
no delta because it reflects the current state of the maintenance log, not a
time-bounded count.
KPI cards reflect data as of page load. Refresh the page to pick up trips or discrepancies entered
since your last visit.
## Critical alert banner
If any of the following conditions exist when the page loads, a red alert banner
appears above the KPI cards:
* One or more critical anomalies detected by the anomaly engine.
* One or more crew members with an expired currency item.
* One or more maintenance due items in **Overdue** status.
The banner includes action buttons -- **Review Crew** and **Due Items** -- that
navigate directly to the relevant module for resolution.
## Sub-tabs
The six navigation cards below the KPI strip link to dedicated sub-tab pages.
Each sub-tab has its own date range selector and a full-page set of charts.
### Fleet Utilization
**Path:** Ops > Analytics > Fleet Utilization
Tracks how intensively each aircraft is being used across the selected period.
| Section | Content |
| ------------------------- | --------------------------------------------------------------------------------------- |
| KPI strip | Total hours, average utilization rate (h/ac/day), total flights, revenue per block hour |
| Hours by aircraft | Bar chart comparing block hours across tail numbers |
| Daily utilization trend | Area chart of total fleet hours by day |
| Deadhead ratio | Per-aircraft ratio of non-revenue legs to total legs |
| Aircraft comparison table | Registration, make/model, hours, flights, revenue, deadhead legs |
Use this tab to identify underutilized aircraft, compare scheduling patterns
across the fleet, and spot revenue-per-hour outliers. In accordance with
14 CFR 5.71, utilization metrics contribute to safety performance monitoring
by surfacing aircraft that may be accumulating unusual operating patterns.
### Crew Analytics
**Path:** Ops > Analytics > Crew Analytics
Covers crew duty compliance, currency expiration status, and per-crew flight
hours. This tab is governed by 14 CFR Part 135 Subpart F (Flight Time and Duty
Limitations) and 14 CFR 5.71.
| Section | Content |
| --------------------- | --------------------------------------------------------------------------------- |
| KPI strip | Total crew members, average weekly hours, currency compliance rate |
| Duty compliance table | Per-crew rolling 7-day flight time vs. Part 135 limits |
| Currency status panel | Each crew member's currency items with status badges (Current, Due Soon, Expired) |
| Weekly hours trend | Stacked area chart of hours per crew member over time |
The duty compliance display uses a rolling 7-day window regardless of the date range you select.
This reflects the way 14 CFR Part 135 Subpart F limits are calculated operationally.
Currency status badges use the following color scheme:
| Badge | Meaning |
| ------------ | ---------------------------------------------------------------- |
| **Current** | Item is valid and not approaching expiration |
| **Due Soon** | Expiration is within the warning window |
| **Expired** | Item has lapsed -- crew member may not be legal to fly this item |
### Financial
**Path:** Ops > Analytics > Financial
Tracks cost trends, revenue performance, and profitability across the fleet.
Requires the `accounting.read` permission and financial access enabled for your
role.
| Section | Content |
| ----------------------- | ---------------------------------------------------------------------- |
| KPI strip | Total revenue, total costs, net margin, revenue per block hour |
| Revenue vs. costs trend | Dual-axis area chart by day |
| Cost breakdown | Stacked bar chart: fuel, landing fees, handling, crew, catering, other |
| Revenue by aircraft | Bar chart comparing revenue generated per tail number |
| Monthly P\&L summary | Table of revenue, cost categories, and net per calendar month |
Cost categories map directly to the trip estimate fields populated during trip
planning. Ensure trip estimates are completed for accurate financial analytics.
### Customers
**Path:** Ops > Analytics > Customers
Summarizes charter revenue and trip frequency by customer (passenger or
organization).
| Section | Content |
| -------------------------- | ------------------------------------------------ |
| Top customers by revenue | Ranked list with total spend and trip count |
| Trip frequency trend | Chart showing trip volume per customer over time |
| Customer segment breakdown | Charter vs. owner usage split |
### Route Profitability
**Path:** Ops > Analytics > Route Profitability
Analyzes the most-flown city-pair routes and their on-time performance. Use this
tab to identify high-frequency routes suitable for standardization and
low-performing routes with chronic delays.
| Section | Content |
| ----------------- | ------------------------------------------------------- |
| Popular routes | Ranked list of origin-destination pairs by flight count |
| OTP by route | On-time percentage per route |
| Revenue per route | Estimated revenue generated per city pair |
### Data Explorer
**Path:** Ops > Analytics > Data Explorer
The Data Explorer loads the last 90 days of operational data -- trips, trip legs,
trip estimates, aircraft, and crew -- into an in-browser SQL engine.
You write SQL directly in the editor; queries run entirely in your browser with no
server roundtrips.
Available data sets:
| Data Set | Key Fields |
| -------------- | ------------------------------------------------------------------------------------------ |
| Trips | Trip number, status, origin, destination, departure time, arrival time, aircraft |
| Trip Legs | Trip reference, origin, destination, departure time, arrival time, block time, flight time |
| Trip Estimates | Cost and revenue estimate fields per trip |
| Aircraft | Registration, make, model, status |
| Crew Members | Crew roster with role |
### Step 1: Open the Data Explorer
Click the **Data Explorer** card on the Analytics landing page.
### Step 2: Wait for the query engine to initialize
The in-browser SQL engine loads once on first use. A loading indicator
appears while the engine initializes. Subsequent visits in the same browser
session are instant.
### Step 3: Write a SQL query
Type your query into the SQL editor. Use the schema reference panel on the left
side of the page to browse available tables and columns.
### Step 4: Run the query
Click **Run Query** or press the keyboard shortcut shown in the editor. Results
render as a sortable table below the editor.
### Step 5: Export results
Click **Export CSV** above the results table to download the full result set as
a comma-separated file.
The query engine supports standard SQL including window functions, CTEs, and aggregate
expressions. For example, to compute average block time by route:
```sql theme={}
SELECT origin, destination,
ROUND(AVG(block_time), 2) AS avg_block_hours,
COUNT(*) AS leg_count
FROM trip_legs
GROUP BY origin, destination
ORDER BY leg_count DESC;
```
## Anomaly detection panel
The anomaly detection panel appears in the right column of the landing page,
below the maintenance card. It surfaces automated flags computed from the loaded
data when the page is requested. Anomalies are categorized by severity.
| Severity | Color | Meaning |
| ------------ | ------ | -------------------------------------------------------------- |
| **Critical** | Red | Requires immediate attention -- also triggers the alert banner |
| **Warning** | Orange | Warrants review before the next scheduling cycle |
| **Info** | Blue | Notable trend worth monitoring |
Current anomaly checks include:
* Aircraft with zero flight hours in the period (possible AOG or scheduling gap).
* OTP below a threshold indicating systemic departure delay patterns.
* Crew members approaching or exceeding rolling duty hour limits under
14 CFR Part 135 Subpart F.
* Maintenance due items in overdue status.
* Abnormal cost spikes in the daily cost trend.
Anomalies are computed at page load from the same data that populates the
dashboard. They are not persistent alerts -- refresh the page to re-evaluate.
## AI insights panel
If AI-generated insights are available for your workspace, an insights panel
appears above the natural-language query card. Each insight card shows a
category, severity, title, description, and a metric or action link.
Dismiss an insight by clicking the **X** on its card. Dismissed insights do not
reappear unless regenerated by a new analysis run.
## Ask Copilot (natural-language queries)
The **Ask Copilot** card on the landing page lets you ask free-form questions
about your operational data in plain English. The question is sent to the AI
service, which generates a response drawing on your workspace data.
Examples of effective questions:
* "Which aircraft had the most flight hours last month?"
* "Show me crew members with currency items expiring in the next 30 days."
* "What was our average cost per flight hour in Q1?"
The natural-language query feature must be enabled for your environment. It is available in
production by default.
## Export charts and data
The Analytics landing page and sub-tabs do not have a dedicated export button for
chart images, but you can export underlying data as follows:
* **Data Explorer:** Click **Export CSV** after running any query.
* **Reports:** Use the Export menu in the Reports hub (see
[How to Run Operational Reports](/en/how-to/ops/run-reports)).
For chart images, use your browser's built-in screenshot capability or a
screen-capture tool.
## Related
Generate and export point-in-time reports for fleet, crew, financial, and maintenance data.
Update crew currency items and duty records that feed the Crew Analytics tab.
Resolve overdue maintenance items that trigger anomaly alerts on the Analytics dashboard.
Complete trip estimates to ensure financial analytics reflect accurate cost and revenue data.