FuelDeck™ Beta — the unified platform arrives 2026 Letter from our CEO →

Home / Products / FuelScanner™

01 · Capture · FuelScanner™

Every ramp ticket, structured in seconds

FuelScanner™ is the capture layer of FuelDeck™. AI reads handwritten, printed and faxed aviation fuel tickets — pulling 32+ fields off each one and exporting clean CSV or IATA XML straight into the audited ledger. No retyping, no month-end meter-math surprises.

32+ fields / ticketCSV · IATA XML export<1 gal reconciliationSOC 2

Watch it read a ticket

From the fueler's pen to a clean record

A driver scribbles gallons, meter reads and a tail number on a paper ticket at the ramp. FuelScanner™ reads the same chaos a human would squint at — and turns it into typed, reconciled, exportable data.

reading · ramp-uplift-0049-217.jpg 1 ticket · 0/8 regions 0 tokens 32 fields
RAMP UPLIFT TICKET
No. 0049-217
YVR · BAY 4
JET-A
Date6 / 18 / 26
FlightAC 0118
TailC-FGDT
Meter start041,920
Meter end046,058
Gallons4,138
Density0.804
Temp °F61
R. Okafor Fueler signature
Extracted · structured output0/32 captured
Date99%
2026-06-18
Flight98%
AC0118
Tail #97%
C-FGDT
Meter Δ98%
4,138
Gallons (net)98%
4,138.0
Density (SG)95%
0.804
Temp °F91%
61.0
Signature96%
R. Okafor
Driver vs meter: 0.0 gal +24 more fields → posts to FuelCounter™

Core capabilities

Read, extract, sort — every ticket the ramp produces

The same engine does three jobs on every page: it reads the messiest handwriting region by region, extracts each value into typed, confidence-scored data, and sorts a mixed stack into uplifts, defuels and into-plane transfers — automatically.

01 · Read

Reads the page

Aviation-tuned vision detects each region — handwriting, printed meter, signature, stamp — and turns the page into structured tokens.

Handwriting · gallonshandwritten
Meter readsprinted
Tail & flighthandwritten
Fueler signaturesignature
Bay & product stampstamp
regions 0/5tokens 0
02 · Extract

Extracts the fields

Every region maps to a known aviation field — typed, normalised and returned with a per-value confidence score, ready for the ledger.

{ "tail": "C-FGDT",0.97 "gallons_net": 4138.0,0.98 "meter_delta": 4138,0.98 "supplier": "Allied",0.96 "product": "Jet-A",0.99 "txn_type": "uplift"0.97}
03 · Sort

Sorts the stack

Hand it a shift of mixed paperwork and it splits the batch by transaction type — uplifts, defuels and into-plane transfers — each indexed to its source image.

Uplift 0
Defuel 0
Into-plane 0

The capture pipeline

Five steps, one audit-ready record

No change to how a single fueler works in the field. The ticket they already write becomes structured data the moment it reaches FuelScanner™.

Snap or upload

Drag & drop or photograph the ticket — paper, printed, faxed or PDF. Batch a whole shift at once; no file is too messy.

Ingest

AI reads 32+ fields

Purpose-built aviation OCR extracts date, flight, tail, airport, supplier, product, gross/net gallons, meter reads, density, temperature, ticket number and transaction type — every ticket, every time.

Extract

Validation hints

Driver-written totals are cross-checked against printed meter reads within a sub-1-gallon tolerance. Anomalies — zero gallons, tail mismatch, defuels, missing fields — are flagged before they reach your books.

Check

Export CSV or IATA XML

Clean records export as CSV for any downstream tool or as standard IATA XML for industry exchange — with the original ticket image kept beside every value.

Export

Lands in the FuelDeck™ ledger

The record posts straight into the audited FuelDeck™ ledger, ready for FuelCounter™ to reconcile against supplier invoices and airline schedules — entered once, trusted everywhere.

Post

Why it matters

The ramp-to-database step, automated

Stop paying analysts to retype tickets and chasing meter-math errors after month-end.

NO RE-KEYING

Zero manual entry

The ticket the fueler already wrote becomes typed data automatically — no analyst transcribing numbers off paper at two minutes a ticket.

DEPTH

32+ fields per ticket

Flight, tail, fuel, meter, location, density, temperature, timing — every aviation-specific field captured, not just the gallons total.

SPEED

Ramp to database in seconds

Tickets go from a photo to a reconciled, exportable record in seconds — a full shift cleared without losing oversight or the audit trail.

At a glance

Formats in, structured data out

FuelScanner™ ingests whatever the ramp produces and emits clean, standard formats the rest of FuelDeck™ — and your systems — can read.

Input formatsHandwritten ramp tickets, printed tickets, faxed delivery notes, PDF & photo (drag-and-drop or batch upload)
Fields captured32+ aviation-specific fields per ticket — date, flight, tail, airport, supplier, product, gross/net gallons, meter reads, density, temperature, ticket #, transaction type
ValidationDriver-vs-meter reconciliation within a sub-1-gallon tolerance, plus anomaly flags surfaced before posting
Output formatsCSV for any downstream tool · standard IATA XML for industry exchange
IntegrationPosts directly into the audited FuelDeck™ ledger and onward to FuelCounter™; available via REST API
ProvenanceOriginal ticket image stored beside every extracted value, with a full immutable audit trail

Questions

FuelScanner™, answered

How accurate is it on messy handwriting?
FuelScanner™ is built for aviation tickets, not generic documents — it knows what a tail number, meter read and Jet-A density should look like, so it reads field by field rather than guessing at free text. Every value comes back with a confidence score, and low-confidence fields are flagged for a quick human check instead of being silently posted. Driver-written totals are also cross-checked against the printed meter reads within a sub-1-gallon tolerance.
What ticket formats can it handle?
Handwritten ramp tickets, printed tickets, faxed delivery notes, PDFs and photos — drag-and-drop one at a time or batch a whole shift. There's no change to how a single fueler works in the field; the ticket they already write is the input.
What does it export, and where does the data go?
Clean records export as CSV for any downstream tool or as standard IATA XML for industry exchange. They also post straight into the audited FuelDeck™ ledger and are reachable via REST API — entered once, available to every module.
How does FuelScanner™ connect to FuelCounter™?
FuelScanner™ is step 01 · Capture; FuelCounter™ is step 02 · Validate. Every captured ticket flows into the same FuelDeck™ ledger, where FuelCounter™ runs its five validation gates against supplier invoices and actual airline schedules. Because they share one record, nothing is ever re-keyed between capture and reconciliation.
Is our fuel data secure?
Yes. FuelScanner™ runs on Google Cloud / Firebase — SOC 2 compliant with a 99.95% SLA. Files and records are encrypted with TLS 1.3 in transit and AES-256 at rest, and every account's data is held under strict per-tenant Firestore isolation. See the full security overview.

Trust & security

Built to defend an audit

Capture is only useful if it's trustworthy. Every ticket FuelScanner™ reads is encrypted, isolated and traceable to its source image.

SOC 2 · 99.95% SLA

Google Cloud infrastructure

Built on Firebase / Google Cloud — SOC 2 compliant with a 99.95% uptime SLA across auth, storage and data.

TLS 1.3 · AES-256

Encrypted ticket images

Source files and extracted records are encrypted in transit with TLS 1.3 and at rest with AES-256.

Per-tenant isolation

Your tickets, only yours

Per-tenant Firestore isolation enforces strict access — no account can ever query another's data.

Read the full security overview →

Book a discovery call

Bring a stack of tickets. Watch them digitize.

Hand us a week of real fuel tickets — handwritten and all — and we'll show you the structured data, the confidence scores, and the errors FuelScanner™ catches before they hit your books.

Book a demo