---
title: "PINAX Ai: Airline On-Time Performance Software | FlightAtom"
description: "PINAX Ai is airline on-time performance (OTP) software: a live D15 and A15 dashboard, delay-code and block-time analysis, and emailed daily and weekly reports."
canonical: https://www.flightatom.com/products/pinax.html
last_updated: 2026-10-27
publisher: FlightAtom
---

# PINAX Ai · Airline on-time performance software: Read the operating day at a glance. See where punctuality is lost.

PINAX Ai lets airline operations teams follow on-time performance live on one wallboard, see which department leads each controllable delay cause, find the block times behind late arrivals, and start each morning with an emailed operations brief. The wallboard, daily brief, weekly delay report and up to a year of punctuality and delay-code analysis read the same flight records with the same definitions. D15 and A15 sit beside the flight counts behind them.

[Request a demo of PINAX Ai](https://www.flightatom.com/#demo-pinax) · [Explore PINAX Ai](https://www.flightatom.com/products/pinax.html#product-tour)

[Email me the brochure, PINAX Ai](https://www.flightatom.com/resources/brochure.html#product=pinax&placement=hero)

Operations control and on-time performance teams, department heads and airline management · Independent product · Fits your operation as it changes

![PINAX Ai full-screen wallboard with synthetic demonstration data. An amber On-time Performance banner reads Room for improvement, driven by A15 75.0% (4 eligible), KBOS MVFR and D15 80.0% (5 eligible), with 5 of 5 due sectors operated. Flight progress cards follow DEM flights out of and back to New York. KPI cards show OTP D15 80.0% (D0 40.0%), OTP A15 75.0% (A0 50.0%) and 7.8 min delay per sector. Below are a departure punctuality chart by flight, three open actions for Network Operations, three delay codes with their lead department or External, and airport weather tiles.](https://www.flightatom.com/products/screens/current/pinax-signature-20261011.webp)

*Read the day on one wallboard · Demonstration data*

## In brief: What is PINAX Ai?

PINAX Ai is FlightAtom's airline on-time performance software for operations control, performance teams and airline management. It runs a live operating-day dashboard designed for wall screens, analyzes up to a year of punctuality, delay codes and block times, and emails a daily operations brief and a weekly delay report from the same flight records. Every punctuality figure is shown with the flight count behind it.

- **Category:** Airline on-time performance software
- **Built for:** Operations control and on-time performance teams, department heads and airline management
- **Automation:** Deterministic analytics and statistical clustering; no generative AI
- **Availability:** Available · independent product
- **Fits your operation:** As your operation grows or changes, we adapt PINAX Ai to fit, and you approve each change before it goes live.

## How it works · PINAX Ai: Each figure, and how PINAX Ai computes it.

Each tile is one figure PINAX Ai computes and the rule or statistic that produces it.

- *Wallboard* · **D15 · A15** · Shares of departures and arrivals within 15 minutes of schedule, each beside its flight count; the day is rated on the weaker.
- *Wallboard* · **Controllable delay** · Delay minutes coded to Engineering, Ground Operations or Flight Operations form the controllable share; external, knock-on and uncoded delay stay outside it.
- *Daily brief* · **TDR** · Technical dispatch reliability: the share of departed sectors that did not leave 15 or more minutes late with a delay code beginning with 4.
- *Analysis* · **Block time** · Each route's median gate-to-gate time against its published block: 5 or more minutes over is under-blocked, 10 or more under is over-blocked.
- *Weekly report* · **OTP trend** · Flight-weighted linear fits over windows from 30 days to a year, graded by strength, with no direction given when there is no clear trend.
- *Analysis* · **Day archetypes** · K-means clustering with fixed seeding groups past operating days by outcome and delay-cause mix; the same dates always give the same groups.

*Each badge names one view where that figure appears.*

## Inside PINAX Ai: From today's wallboard to the record behind it.

PINAX Ai screens captured in October 2026 from an isolated demo with synthetic records and neutral geography. Open a screenshot for a closer look.

### Read the day on one screen

The full-screen wallboard rates the day on the weaker of D15 and A15, here A15 at 75.0%. It puts flight progress, D0 and A0, delay per sector, rule-based actions with owners and the day's delay codes on one screen. Synthetic demonstration data.

![PINAX Ai full-screen wallboard with synthetic demonstration data. An amber On-time Performance banner reads Room for improvement, driven by A15 75.0% (4 eligible), KBOS MVFR and D15 80.0% (5 eligible), with 5 of 5 due sectors operated. Flight progress cards follow DEM flights out of and back to New York. KPI cards show OTP D15 80.0% (D0 40.0%), OTP A15 75.0% (A0 50.0%) and 7.8 min delay per sector. Below are a departure punctuality chart by flight, three open actions for Network Operations, three delay codes with their lead department or External, and airport weather tiles.](https://www.flightatom.com/products/screens/current/pinax-1-20261011.webp)

*Read the day on one screen · Demonstration data*

### Separate controllable delay from external

Across 365 selected days, every delay code is ranked by coded minutes and assigned once to Engineering, Ground Operations, Flight Operations or external and knock-on causes. The footnote states the controllable share, here 61.9%. Synthetic demonstration data.

![PINAX Ai delay analysis across 365 selected days with synthetic demonstration data. Cards show 6.8 min delay per operated sector, 930 h 37 min observed OUT delay, 2,295 delayed sectors and 99.1% delay-code coverage. The Delay-code analysis panel ranks twelve delay codes by coded minutes, from 41 Aircraft defects (Controllable, Engineering, 211 h 10 min, 22.7%) down to 89 Departure airport restrictions / ATFM (External, 1.9%). Each row names its department or marks it External and knock-on, and a footnote reports 61.9% controllable and 31 min observed but unattributed.](https://www.flightatom.com/products/screens/current/pinax-2-20261011.webp)

*Separate controllable delay from external · Demonstration data*

### Test each block against reality

PINAX Ai compares each route's actual gate-to-gate time with its published block. YYZ-JFK and JFK-MCO run a median 9 minutes over their published block and get a suggested block that would contain 90% of sectors, while BWI-JFK runs a median 11 minutes under its block and is marked over-blocked. Synthetic demonstration data.

![PINAX Ai block-time analysis with synthetic demonstration data. Cards show block variance of +1 min, block held on 48% of 8222 measured sectors, and 6.1% of on-time departures (438 of 7159) still arriving late. The Block time by route list covers 8 routes: YYZ-JFK and JFK-MCO are under-blocked at a median +9 min, with suggested blocks of 125 and 185 min that would contain 90% of sectors; five routes hold their published block; BWI-JFK is over-blocked at -11 min.](https://www.flightatom.com/products/screens/current/pinax-3-20261011.webp)

*Test each block against reality · Demonstration data*

### Name each kind of day

Deterministic k-means clustering groups operating days by punctuality, cancellations, block pressure and delay-cause mix and names each group from what its days share; here 27 days disrupted by departure-station weather carry 22.7% of the delay on departures from New York. The scope can be narrowed by date, airport or city pair, downloaded as CSV or printed as a PDF report. Synthetic demonstration data.

![PINAX Ai Performance analysis page on the Day archetypes view with synthetic demonstration data, labelled Demo data. The report is filtered to 3 Nov 2025 – 10 Oct 2026, departing New York (JFK), 3,864 flights, with CSV download and Print report controls. The Kinds of day, and what each costs panel reports 2 archetypes across 342 days: Elevated delay (315 days, 3.4 min delay per sector, 77.3% of delay, no single cause dominates) and Departure station weather — disrupted (27 days, 18.2 min delay per sector, 22.7% of delay, with departure station weather carrying 70.3% of it).](https://www.flightatom.com/products/screens/current/pinax-4-20261011.webp)

*Name each kind of day · Demonstration data*

### Check readiness for the next sectors

The readiness view counts aircraft on the board, open deferred defects, crew duties within two hours of their duty-period limit and training due. It rates each aircraft's tightest turn, all without naming anyone. Synthetic demonstration data.

![PINAX Ai Operational readiness page with synthetic demonstration data, labelled Demo data and updated 10:47 am New York time. Summary cards show 7 aircraft monitored, 2 deferred defects across 2 aircraft, 1 crew duty within two hours of its FDP limit and 2 training items due in 30 days. A Today's aircraft rotation table lists five tails with sectors, block time and tightest turn; N02DA's 43 min turn is marked Tight turn and the others Ready. Technical readiness and Duty and currency panels give maintenance, active duty, training and overdue task counts, with no names.](https://www.flightatom.com/products/screens/current/pinax-5-20261011.webp)

*Check readiness for the next sectors · Demonstration data*

### Close out each day in a brief

For each completed operating day, PINAX Ai produces a PDF operations brief. Page 1 sets the day's technical dispatch reliability beside its rolling 30-day figure, plots each departure's delay against its scheduled time, totals delay by code and station, and lists the sectors that need attention. Synthetic demonstration data.

![Part of page 1 of a PINAX Ai daily operations brief PDF for 10 October 2026, synthetic demonstration data. Day totals: 24 sectors planned, 0 cancelled, TDR 24/24 100.0%. Rolling 30 days: completion 100.0% (680 of 680) and technical dispatch reliability 98.2% (668 of 680). How the day ran plots departure delay by scheduled time against a 15 min threshold. Where the time went: 4 reported delay categories totalling 53 min, all Controllable: 33 Loading equipment at KJFK (27 min) and 15 Boarding at CYYZ and KJFK (11 min each) and KBOS (4 min). What needs attention: DEM405 JFK – BWI, +27 min departure.](https://www.flightatom.com/products/screens/current/pinax-6-20261011.webp)

*Close out each day in a brief · Demonstration data*

[Request a demo of PINAX Ai](https://www.flightatom.com/#demo-pinax) · [Email me the brochure, PINAX Ai](https://www.flightatom.com/resources/brochure.html#product=pinax&placement=product_tour)

## Capabilities: From today's wallboard to Friday's delay report.

The wallboard, the analysis, the briefs and the reports read the same flight records with the same definitions, so their figures agree.

### Read the day on one wallboard

D15 and A15 sit beside the flight counts behind them, and the day is rated on the weaker of the two, so strong departures cannot hide late arrivals. Completion, delay per sector, station departure punctuality and zero-tolerance D0 and A0 for the same sectors share the screen, and authorized users can step the board back through the past year.

### See how much delay was controllable, and whose

The wallboard states how much of the day's delay was controllable and names the lead department for each controllable cause: Engineering (40-49), Ground Operations (10-39 and 50-59) or Flight Operations (60-69). External, knock-on and uncoded delay stay visible on their own, and a Friday report groups the week's delay log by department, reconciles coded minutes against observed delay and shows what share of delayed sectors carry a code.

### Start each morning with the operations brief

Each completed operating day becomes a PDF brief, emailed at a set hour to each account that opts in, so nobody assembles the morning report by hand. It covers completion, D15 and A15 with D0 and A0, daily and rolling 30-day technical dispatch reliability, every sector with its delay reasons, station punctuality and open deferred defects, then looks ahead to the coming day's sectors with passenger counts, crew cover and a TAF check at each expected arrival.

### Find the block times behind late arrivals

PINAX Ai compares each route's and flight number's actual gate-to-gate time with its published block, classes it as under-blocked, over-blocked or holding, and counts sectors that left on time but still arrived late. It splits taxi-out, airborne and taxi-in time, and suggests a block that covers 90% of sectors once five or more measured sectors show a route is under-blocked.

### Answer a specific performance question

Filter up to the past year by date range, departure airport, arrival airport or directional city pair across punctuality, delay, block-time, day-archetype and trend views. Any scope exports as an A4 PDF report of one view or all five, with flight, delay, route and schedule CSV files.

### See what needs attention now

Rule-based checks raise up to three actions at a time, each with an owner and a due time: cancellations, missing movement times, overdue departures, punctuality misses and airport weather from current METAR observations. The board refreshes every minute, keeps the last good picture if an update fails, and keeps the screen awake in full-screen mode.

### Ask the pilots what they saw

PINAX Ai can email the pilots rostered on a delayed flight a signed survey link that needs no account and does not show the recorded delay codes. An optional crew delay log, granted one account at a time, lists late departures by roster code, never by name, and ranks a code only after it has flown ten sectors in the window.

### Check readiness across aircraft, crew and tasks

The readiness view shows each aircraft's rotation and tightest turn, active and next-seven-day maintenance, open deferred defects, crew duties within two hours of their recorded flight duty period limit, training expiring within 30 and 90 days, and overdue operations tasks, all as counts without crew names.

### Give each screen and person the right access

Administrator, Operations manager and Wallboard viewer presets, or a custom set, decide which views each account can open, and every account change is recorded in an audit trail. Accounts set up as wallboard screens stay signed in while the screen keeps refreshing, and personal accounts confirm sign-in with a six-digit code sent by email. With Keycloak single sign-on, the roles assigned there set PINAX Ai permissions and are rechecked every few minutes.

## Workflow & control: Statistics that show their work.

PINAX Ai uses deterministic calculations and classical statistics. Each measure is defined with its formula in the operator manual, which must be updated in the same change as the code, and the wallboard labels its data as live, limited, stale, unavailable or demo.

### Honest denominators

Every punctuality figure carries the flight count behind it. Cancellations stay in the delivery denominator, range D15 and A15 are summed from flights rather than averaged from daily percentages, and A15 is shown as unavailable rather than calculated on a smaller base when arrival times are missing.

### Trends that state their confidence

OTP trends fit flight-weighted lines over 30 days, three months, six months and a year, and label each fit from 'Clear trend' to 'No clear trend'. PINAX Ai withholds the direction when the fit is too weak and states when the fitted line would reach the target only if that date falls within 90 days.

### Day archetypes from clustering

PINAX Ai groups 30 or more operating days by outcome and delay-cause mix using k-means clustering with fixed seeding, so the same dates always give the same groups. Each group is named by its severity within the selected scope and its dominant cause, with how often it occurs and its delay per sector.

### Operational boundaries

PINAX Ai reads its full operational record from myairops. A ForeFlight Dispatch feed gives a reduced picture without delay codes, operational cancellations, a formal A15 or crew and readiness records, and another operations system needs a new connector. Each deployment is adapted to the operator's airline code, base, time zone, fleet and targets. Flightradar24 positions, ForeFlight passenger counts, the seven-day weather outlook, email delivery and single sign-on each need their own credentials or agreements. Analysis covers the past year, and its trend lines and day archetypes describe recorded performance rather than forecasting it. Briefs, weather flags and readiness counts support management review; they are not dispatch releases, meteorological briefings, crew legality checks or maintenance control. A native iPhone and iPad app on the same accounts is awaiting public release.

## Evaluate PINAX Ai: Make the next step measurable.

Agree a representative sample and a baseline from your current process. These are proposed evaluation measures, not published performance results.

### Bring a representative example

An operating period with a known source and a specific punctuality question.

### Inspect the complete workflow

Trace the denominator, inspect flights, and prepare a management brief.

### Compare with your baseline

Report preparation time; source coverage; agreement with independently calculated metrics.

[How to structure an evaluation](https://www.flightatom.com/resources/evaluation-guide.html) · [Compare product responsibilities](https://www.flightatom.com/platform.html#compare) · [Deployment and data handling](https://www.flightatom.com/trust.html#deployment)

## Related reading: Go deeper on the workflow.

- [Airline operations software](https://www.flightatom.com/solutions/airline-operations-control-software.html)
- [What is an operations control centre?](https://www.flightatom.com/resources/airline-operations-control-centre.html)

## Questions & answers: Before you book a demo.

### What do D15 and A15 mean in PINAX Ai?

D15 and A15 are the shares of flights that depart or arrive within 15 minutes of schedule. PINAX Ai shows each beside the flight count behind it, adds zero-tolerance D0 and A0 for the same sectors, and rates the day's punctuality on the weaker of the two. When arrival times are missing, A15 is reported as unavailable rather than calculated on a smaller base.

### How does PINAX Ai analyze block time?

PINAX Ai compares each route's and flight number's actual gate-to-gate time with its published block. A route whose median runs 5 or more minutes over its block is under-blocked, and one 10 or more minutes under is over-blocked. When at least five measured sectors show a route is under-blocked and one published block applies across the range, PINAX Ai suggests a block that would have covered 90% of them, rounded up to the next 5 minutes.

### How does PINAX Ai attribute delay codes?

PINAX Ai assigns each delay code once to an accountable group: Engineering for codes 40-49, Ground Operations for 10-39 and 50-59, Flight Operations for 60-69, and external or knock-on causes for other numeric codes, including 70 and above. Records without a code are reported as uncoded. The wallboard and the weekly report use the same mapping to separate controllable from external delay minutes.

### What is in the PINAX Ai daily operations brief?

The daily brief is a PDF for each completed operating day. It covers completion, D15 and A15 with D0 and A0, delay per sector, daily and rolling 30-day technical dispatch reliability, every sector with its delay reasons, station punctuality, open deferred defects by aircraft, and the next day's sectors with passenger counts, crew cover and a TAF check at each expected arrival. PINAX Ai can email it at a set local hour, 07:00 by default, and Monday's edition covers Friday to Sunday.

### How does PINAX Ai calculate technical dispatch reliability?

PINAX Ai counts a technical incident when a flight leaves the gate 15 or more minutes late with a delay code beginning with 4. Technical dispatch reliability is the share of departed sectors without such an incident, reported for the day and for a rolling 30 days. Cancelled sectors are measured separately through completion.

### Can PINAX Ai ask pilots why a flight was delayed?

Yes. PINAX Ai can email the pilots rostered on a delayed flight a private, signed survey link that is valid for 30 days and needs no account. The survey asks what they saw without showing the recorded delay codes, and each response is kept with a snapshot of the flight. Requests go out manually or automatically from a crew directory the operator maintains.

### Which systems does PINAX Ai connect to?

PINAX Ai reads schedules, aircraft, delay codes, OUT, OFF, ON and IN times, cancellations, crew assignments, and readiness records such as maintenance, deferred defects, crew duties and training from myairops. Current METARs and TAFs come from the Aviation Weather Center. Flightradar24 positions can refine flight progress without changing movement times or KPIs, ForeFlight can add passenger counts to the day-ahead brief, and Open-Meteo can add a seven-day destination outlook. PINAX Ai is a standalone product and does not require AURORA Ai.

### Is PINAX Ai a generative AI product?

No. PINAX Ai's measures, briefs and reports are deterministic calculations. Its OTP trends use flight-weighted linear regression, and its day archetypes use k-means clustering with fixed seeding to group past operating days by outcome and delay cause. Both describe recorded performance; PINAX Ai does not forecast punctuality.

### What happens to PINAX Ai when our operation grows or changes?

As your fleet, routes, rules or teams change, we adapt PINAX Ai to match, and you approve each change before it goes live.

## See PINAX Ai in action: Start with your workflow.

A focused walkthrough, with the people and decisions that matter to your team.

[Request a demo](https://www.flightatom.com/#demo-pinax)

---

Source: https://www.flightatom.com/products/pinax.html
Contact FlightAtom: hello@flightatom.com · Request a demo: https://www.flightatom.com/#contact