Independent decode Operator custody Evidence chain

The flight, as flown.

Evidence-grade flight data analytics and replay. Not a simulation, not a vendor interpretation - a verifiable account built from the operator's own raw recorder files.

Explore the replay →
No cloud dependency No installation or account Every value reproducible
ASFLOWN / SECTOR FLT-072 / OFFLINE VERIFIED
AircraftATR 72 / Sector Replay
SectorXXXX → YYYY
RecordedNATIVE RATE
1000 FT GATE 500 FT GATE
TIME  14:32:45
ALT   1,018 FT
IAS   128 KT
V/S   -860 FPM
FLAPS 30
STATE RECORDED
Weight off14:06:18
Band deviation14:32:45
Recovery14:33:04
Touchdown14:34:29
SHA-256 / 4A5FB21C99D0E388B421A9C73E55F20B... / RAW BUNDLE TRACEABLE / DISPLAY SERIES GATE-CHECKED
< 2 MBTypical replay file per sector
OfflineAny modern browser, no account
Native rateRecorded cadence is preserved
Operator-ownedRaw data remains in your custody
The legacy FDM funnel

The aircraft records the full story. The organization receives a list.

Flight Data Monitoring was intended to connect recorded operations with organizational learning. Four persistent gaps break that loop.

01

Latency & distillation

Native-rate records become batch triggers weeks later. The sequence, context and recovery are stripped away.

02

Opacity

Decode logic, conversions and thresholds sit inside proprietary systems the operator cannot independently audit.

03

Custody

Safety history moves into subscription clouds, creating sovereignty, continuity and vendor-dependence exposure.

04

The ground blind spot

Taxi fuel, holding, stand power, OOOI and single-engine taxi performance remain largely outside airborne-focused FDM outputs.

Two connected products

Per-sector replay and fleet-wide analytics, built from the same verified corpus.

Per-sector instrument

Open the sector. See the sequence.

One self-contained file plays the flight from parking bay to shutdown. It turns recorder data into a neutral debrief instrument, with evidence attached to every finding.

  • Journey atlas, ground milestones and live taxi counters
  • Flown vertical profile against geometric reference
  • Recorded event captions and matched debrief transcript
  • No installation, network connection or user account
FLT-072 / SECTOR 001OFFLINE / VERIFIED
Vertical profileRecorded vs reference
14:32:45Recorded event time
+50 ftDeviation at gate
FSF ALARCriterion cited to page
OUTOFFONIN
Operator sovereignty zone

The airline's data stays the airline's.

AsFlown independently decodes raw FDAU/QAR files against the airframer's published dataframe documentation. The resulting replay and analytics are delivered as self-contained files directly into the operator's custody.

Recorded, derived and reference values are visibly distinguished. Where no honest reference exists, the display shows a dash rather than an invented figure.

OPERATOR SOVEREIGNTY ZONE
Raw recorder filesOperator custody
Independent decodeAirframer documentation
AsFlown Replay
AsFlown Analytics
NO THIRD-PARTY VENDOR CLOUD REQUIRED
Interactive replay concept

Journey, energy, systems and evidence - visible together.

Use the controls below. The demonstration is self-contained and runs entirely in this HTML file. The production replay connects these views to real decoded sector data.

FLT-DEMO-072XXXX → YYYYSECTOR 001OFFLINE FILE
SHA-256: DEMO7A62...EVIDENCE-CHAIN

Journey Atlas

TAXI OUT
XXXX YYYY
Ground time00:04:10
Taxi fuel84 kg
Distance1.4 NM
State sourceRecorded

Energy & Vertical Profile

FLOWN VS REFERENCE
1000 FT 500 FT
REFERENCE GATE: 1000 FT
REFERENCE GATE: 500 FT
APPROACH DEVIATION / RECORDED+82 FT
Altitude0 ft
IAS0 kt
V/S0 fpm
Deviation—

Systems & Evidence

RECORDED / DERIVED
Aircraft stateNORMAL
GearDOWN
Flaps0
Weight stateON WHEELS
PowerplantRECORDED
NP 172%
NP 272%
Fuel used84 kg
Evidence logLIVE
14:02:00 Raw bundle fingerprint verified.
14:04:17 Engine start derived from recorded NP rise.
14:06:18 Weight-off-wheels recorded from squat switch.
14:02:00
The evidence chain

Never defend a number you cannot independently derive.

Each artifact declares its provenance. Recorded values, derived values and reference values remain distinguishable from source to screen.

Step 1Raw recorder file

Original FDAU/QAR source remains in operator custody.

Step 2Cryptographic fingerprint

Decoded bundle traceable to the operator's original source.

Step 3Documented conversion law

Airframer word position, sample rate and engineering-unit conversion.

Step 4Displayed value

Labeled as recorded, derived or reference - never mixed.

Core capabilities

Built to preserve reality, not smooth it into a story.

Native-rate preservation

Parameters are displayed at their recorded cadence rather than resampled into false smoothness.

Honest data gaps

Receiver fill and invalid frames are detected from raw words and rendered as labeled gaps, never interpolated over.

Versioned derivations

Derived quantities are generated by persisted routines and independently cross-checked at every point.

Cited references

Thresholds are tied to published material or the operator's SOP, with a dash where no valid reference is held.

Ground operations

Taxi, hold, stand power and OOOI are first-class operational data, not an afterthought.

Build-time gates

The replay consumes the same series as formal reports; the build fails if they diverge.

One record, four audiences

Make the recorded operation legible at every level.

A debrief instrument, not a surveillance letter.

The pilot sees the sector against cited criteria, with neutral wording and the sequence of events presented as recorded - including a go-around as the decision it was.

Neutral by designSupports just-culture handling and operator-controlled distribution.
Sequence over triggerShows development, response and recovery rather than a detached event code.
Offline deliveryOne file that opens without an account or network connection.
Matched transcriptPlain-text debrief output gate-checked to the display.

Findings that hold under audit.

Event determinations, displayed values and formal report figures are bound together by the evidence chain and reproducible from the original files.

Evidence attachedEGPWS activations, gate outcomes and band deviations arrive with timing and source.
Independent decodeDiscrepancies surface rather than inheriting incumbent errors.
Audit-readySupports SMS records and IOSA-style evidence trails.
Third-party verificationAn avionics shop can reproduce any selected parameter.

Move the fuel and turnaround conversation from estimate to record.

The ground phase is quantified using the aircraft's own positions and discretes, independent of manual logs or ACARS coverage.

Taxi time & fuelBy sector and aerodrome, compared with fleet medians.
Single-engine taxiUtilization and savings calculated at the operator's SOP rates.
OOOI decompositionExact triggers from NP rise, squat switch and parking brake state.
Maintenance awarenessHotel-mode use, stand power and engine-start ITT peaks.

Sovereignty, defensibility and organizational reach.

The same evidence can serve a safety review, a regulator, an insurer or a board meeting without requiring vendor infrastructure.

No accumulated cloud leverageThe airline retains custody of its safety history.
Defensible figuresReproducible from original data and documented conversion laws.
Board-readySingle-file evidence can be presented without integration or platform access.
Scalable coverageNew types are documented-decode exercises, not product rebuilds.
What distinguishes AsFlown

From vendor assurance to operator-verifiable evidence.

Attribute
Conventional FDM / FOQA
AsFlown
Data custody
Operator data uploaded to vendor infrastructure
Data remains with the operator; artifacts delivered as files
Decode
Proprietary and not independently auditable
Independent decode per airframer documentation
References
Embedded thresholds, origin often undocumented
Source and page cited, or operator SOP; dash where none exists
Primary output
Exceedance lists and dashboards
Sector replay with narrated findings plus fleet analytics
Deployment
Installed software and integration project
A file, in a browser, offline
Ground operations
Largely out of scope
Taxi fuel, SE taxi, hold and OOOI as first-class analytics
Defensibility
Rests on vendor assurance
Reproducible by third parties from raw files and documentation
Field validation

Proven on an in-service ATR 72 fleet.

Operator identity remains confidential. The verification protocol stands in place of a marketing logo wall.

Evidence from the proving fleet

Raw recorder files were independently decoded across more than ninety sectors. Approach screening was reconciled to incumbent systems to the second, a captured go-around was replayed as flown, and a latent GPS data-merge fault in legacy ground software was identified, root-caused and corrected.

90+Sectors independently decoded
To the secondEvent timing reconciliation
1Legacy decode fault identified
ATR 72End-to-end proving type

Independent verification protocol

Select any sector, second and parameter.
Use the airframer's published dataframe documentation.
Decode the parameter from the operator's raw file.
Compare it directly with the AsFlown display.

Checksums, procedure and document references are provided with delivery. The operator never needs to take a vendor's word - including ours.

Questions

What an operator will ask first.

No. The proving engagement begins with existing raw FDAU/QAR files. The replay and analytics are delivered as offline files and require no account, network connection or local installation.

Any selected parameter can be decoded from the operator's original raw file using the airframer's published dataframe documentation, then compared with the displayed value. Delivery includes checksums and document references.

No. The method is built around the dataframe architecture common to modern transport aircraft. The ATR 72 is the proven end-to-end type; another type is onboarded as a documented-decode exercise under the same verification gates.

No. It does not score pilots, invent missing references, simulate unrecorded channels or interpolate over data-quality gaps. Neutral wording and explicit source labels are design constraints.

Yes. The approval version is deliberately self-contained. The launch build can connect enquiry handling, analytics, consent tools, CRM, secure document exchange and operator authentication without changing the public-facing structure.