European Aviation Operating System

One aviation network.
GA Flight is the operating layer for aviation organizations  and the network they share. Every sortie, every pilot, every aircraft sits on one continuous record. Built in Europe, for European aviation.

Purpose-built for real operational continuity, not a generic template adapted to aviation.

EU-Hosted
Data Residency
Signed Records
Training Evidence
Audit Trail
Every Action Logged
Portable ID
Pilot Continuity
PLATFORM THREAD · --:--:-- UTC
  • ChainSortie → Logbook → Aircraft → Finance
  • SourceOne signed record
  • HostingEU data residency
  • AuditEvery action logged
One sortie · Six downstream records · Zero rekeying

The sortie, followed through.

Each stage inherits from the previous. Training, aircraft, maintenance, and billing stay on the same operational thread.

  1. 01Planning
    Sortie slot

    Instructor, aircraft, student, and objective linked as one operational object.

    AffectsFleetTraining
  2. 02Dispatch
    Brief & release

    Aircraft release posture and instructor assignment confirmed before block-off.

    AffectsFleetCompliance
  3. 03Flight
    Execution

    Block-off, block-on, maneuvers, and outcomes captured once, in context.

  4. 04Signature
    Training evidence

    Instructor signs the sortie. Training stage and logbook entry are written from the same event.

    AffectsTrainingPilot record
  5. 05Aircraft
    Hours & release

    Tach/Hobbs posted to utilization history. Maintenance counters and next-release check recalculated.

    AffectsFleetMaintenance
  6. 06Finance
    Billing line

    Billable line and student account update are generated from the signed sortie, with full traceability.

    AffectsFinanceCompliance

why this, why now

European aviation is reaching for infrastructure.

The previous-generation tool stack was built to manage operations. GA Flight is built to write them — once, continuously, into a signed ledger that operators can carry.

fragmentation

Three silos per flight

Planning, logbook, and billing live in separate systems. Every sortie gets re-typed. Every audit becomes archaeology.

regulation

EASA retention is rising

ARA.GEN.220 records need to stay verifiable for years. Screenshots and spreadsheets won't hold up — signed ledgers will.

composition

The network wants a substrate

Pilot identity, school directory, maintenance records — they only compose if they share a common signed layer. That layer is what GA Flight builds.

what GA Flight replaces

From fragmented tools to one signed chain.

The same operation, rewritten once on infrastructure instead of stitched across four applications.

previous generation

GA Flight layer

Flight scheduling in one app
Planning bound to aircraft, instructor, student and objective — one operational object
Paper logbook or PDF export
Logbook entries written from the signed sortie, immutable by design
Manual billing after the fact
Charge emitted from the same signed event, traceable line by line
Maintenance tracked in a spreadsheet
Hours accrued automatically, next-release check recalculated on every landing
Compliance reconstructed during audit week
Evidence packs built continuously, signed by the organization, verifiable offline
workflow continuity · act 1

A stack, not a tool.

GA Flight is built in four composable layers. Every operation on L2 is bound to an identity on L1, written to the ledger on L3, and surfaced as actionable signal on L4. You don't pick features — you sit on infrastructure.

  1. L4 · Intelligencepreview
    Ops Twin — daily briefing

    priorities · opportunities · delta-since-yesterday · evidence pointers

  2. L3 · Authoritylive
    Signed ledger

    hash chain · Ed25519 signing · evidence packs · share tokens

  3. L2 · Operationslive
    One thread, eight modules

    planning · flights · training · logbook · fleet · maintenance · finance · compliance

  4. L1 · Identitylive
    Portable pilot & aircraft

    org · pilot · aircraft · entitlements · cross-org continuity

every layer is observable · every layer is composable · every record is signed

composable layers
4
operational modules
8
ledger signing
Ed25519
hosting & residency
EU
workflow continuity · act 2

The sortie, followed through.

Each stage inherits from the previous. Training, aircraft, maintenance and billing stay on the same operational thread — one record, one chain, one signature.

  1. 01Planning
    Sortie scheduled

    Instructor, aircraft, student, objective — one operational object.

    affectsfleettraining
  2. 02Dispatch
    Release authorized

    Aircraft release posture and instructor assignment confirmed before block-off.

    affectsfleetcompliance
  3. 03Flight
    Sortie flown

    Block-off, block-on, maneuvers, outcomes — captured once, in context.

    affectslogbook
  4. 04Signature
    Evidence written

    Instructor signs. Training stage and logbook entry are written from one event.

    affectstrainingpilot recordlogbook
  5. 05Aircraft
    Hours accrued

    Tach/Hobbs posted. Maintenance counters and next-release check recalculated.

    affectsfleetmaintenance
  6. 06Finance
    Billing emitted

    Billable line and student account update, fully traceable to the signed sortie.

    affectscompliance
ledger anchorseq 0x8f4c2a → 0x8f4c3b
6 records linked · 1 signaturechain verified
workflow continuity · act 3

One flight closed, the chain did the rest.

Every sortie ripples across planning, flights, logbook, training, fleet, maintenance, finance and authority — written once, signed once, verifiable forever.

ops-log · live
  1. 14:31:04.112[planning]sortie.createOPS-SLOT-24-031 · C172 F-GXYZ · student Laurent · instr. Dupontok
  2. 14:32:00.448[flights]flight.block_offLFPG · VFR · block-off 14:32 UTCok
  3. 15:51:22.003[flights]flight.block_onLFPG · block-on 15:51 UTC · 1h19m airborneok
  4. 15:52:10.781[flights]flight.closemaneuvers captured · outcomes captured · instructor signaturesigned
  5. 15:52:11.019[logbook]logbook.writeentry 24-031 · pilot Laurent · PIC 1h19m · XC 1h19mchained
  6. 15:52:11.221[training]training.stage_advancesyllabus IFR · stage 03 → stage 04 · 1 of 3 remainingchained
  7. 15:52:11.412[fleet]fleet.hours_accrueF-GXYZ · tach +1.3 · hobbs +1.3 · next release check -18hchained
  8. 15:52:11.604[finance]finance.bill_lineaccount L-142 · line 24-031 · €198.50 · traceablechained
  9. 15:52:11.812[authority]chain.signbatch 0x8f4c3b · Ed25519 · 9 records · pack emittedsealed

9 records · 1 signature · 0 manual entries — one flight closed, the chain did the rest

signed & verifiedevidence_pack · pilot_portable

Pilot evidence pack

Sophie Lambert · PPL(A) · 127 flights · 2023–2026

subject
pilot · sophie.lambert@ga-flight.eu
range
2023-06-14 → 2026-04-19 · 127 flight entries
chain
seq 0x00a3c1 → 0x8f4c3b · 2 384 entries
signed by
Aéroclub de Mérignac · Ed25519 · key 2024-k1
emitted
2026-04-19 · 16:48:05 UTC

Manifest SHA-256

a3c1f2…9e4b7d2e01…3cab5f88c9…142a8f4c3b

authority chain

Every record, provably yours.

Every signed record in GA Flight can be packed, signed with the organization's Ed25519 key, and handed to a pilot, inspector, or successor school. The pack verifies against the chain — without GA Flight having to be online.

  • Logbook entries bound to the flights they came from — instructor signatures preserved.
  • Training credits traceable to the signed sortie that issued them — no re-keying, no drift.
  • Share tokens with expiry, access counts, clean revocation.
  • Self-verifying open pack format — records survive any migration.

Aviation Operations As A Network

Every operator joins a network designed to compound.

GA Flight is built so that the value of being on the platform grows with each operator, pilot, and aircraft on it. The architecture is in place from day one — regardless of network size today.

Identity

A pilot's record travels with them.

A student's logbook, training stage, and signed records travel across organizations. Schools no longer lose pilot continuity at handoff. Pilots no longer rebuild their record from scratch.

Authority

Evidence aggregates beyond a single organization.

Operational records, instructor signatures, and aircraft history aggregate into authority-facing packs (DGAC, EASA national authorities). The chain extends beyond a single organization's perimeter.

Network signal

Discovery grounded in real operational records.

Marketplace, school discovery, and instructor matching are grounded in real operational records — not marketing profiles. Verified flight history, fleet, and training pathways will become the connective tissue as the network grows.

The network exists in architecture today. Its scale will grow as operators join — we describe its design, not its current size.

ops twin · morning briefing

What opens each morning.

A single view that tells you, each morning, what's moving, what's at risk, what can earn — and why.
Your morning on Ops TwinMonday · 20 April 2026 · 07:02 UTC

What's moving

4
  • F-GABC — 100h inspection due in 14 flight hours

    Maintenance due-check fired on last sortie. Plan window now or block schedule later.

    evidence · maintenance.due_check
  • Sophie Lambert passed PPL stage 3

    Credit issued automatically on signed sortie — solo XC window open.

    evidence · training.credit_issue
  • Weather — IFR at LFBD through 11:00 local

    3 VFR sorties dispatch-held. Re-brief or re-slot.

    evidence · weather.metar
  • Instructor Dubois reached weekly hour cap

    Reassign 2 remaining sorties or flag rest window.

    evidence · ops.instructor_load

What's at risk

2
  • Fiscal period 2026-Q1 closes in 3 days

    7 flights still unbilled. Risk: journal lock with missing lines.

    evidence · finance.period_lock
  • 3 medicals expiring in < 30 days

    Lambert · Dubois · Martin. No sorties bookable on expiry.

    evidence · compliance.medical_check

What can earn

2
  • Re-slot 4 IFR-held sorties to Wednesday PM

    Forecast CAVOK · same CFI/aircraft pairs still viable.

    + €1 240 expected revenue

    evidence · ops.reslot_candidates
  • Open 2 extra solo slots for stage-3 students

    F-GABC idle Thu AM. 6 students eligible. Avg billable 1.1h ea.

    + €780 expected revenue

    evidence · training.solo_eligible

every card links to its source · every number is traceable · ops-twin · briefing v1 · signed to chain seq 0x8f4c3b

See It In Action

The platform, in three surfaces.

The Web Console runs daily operations for aviation organizations. The Pilot Portal gives every student a durable view of their own training record. Both pull from the same operational core.

Web Console

Dispatch, flights, training, fleet, maintenance, finance, compliance.

Full details
GA Flight web console — planning and dispatchProduction interface

Pilot Portal

Logbook, training progression, documents, payments, pilot identity.

Full details

Schools

Discover flight schools with real operational profiles. Training pathways, fleet, and history — not marketing copy.

Explore schools
GA Flight operations dashboardProduction interface

Console screenshots show the production interface with sample data. Portal preview is illustrative of the production interface.

platform

Four layers, one platform.

GA Flight is built as a composable stack — every layer is observable, every layer is replaceable in principle, no layer claims to be a silver bullet.

L1 — Identity

live

org · pilot · aircraft · entitlements

Organizations, pilots, aircraft and entitlements modeled as identity objects. Pilots carry their record across schools. Aircraft carry their history across owners. Role and permission are first-class, not afterthoughts.

portable pilot identitycross-org continuityaircraft historyrole & entitlementSee the layer

L2 — Operations

live

planning · flights · training · logbook · fleet · maintenance · finance · compliance

Planning, flights, training, logbook, fleet, maintenance, finance and compliance — wired on one shared substrate so every operation writes once and propagates across the stack.

one signed sortiedownstream propagationno re-keying8 modules, one threadSee the layer

L3 — Authority

live

hash chain · Ed25519 · evidence packs · share tokens

Ed25519-signed hash chain, typed evidence packs (aircraft, pilot_portable, compliance, training, finance, audit), share tokens with expiry and revocation, offline-verifiable manifests.

Ed25519 signingevidence packsshare tokensoffline verifySee the layer

L4 — Intelligence

preview

Ops Twin · priorities · opportunities · evidence pointers

Daily briefings generated from the operational thread, with priorities, opportunities, and delta-since-yesterday — every insight carries an evidence pointer back to the underlying signed record.

daily briefingpriorities & risksrevenue opportunitiesevidence pointersSee the layer

Web Console

Operational control for aviation organizations.

The Web Console is the daily command environment for dispatch, flights, training, fleet, compliance, and financial control — for every organization that trains pilots and flies aircraft.

  • 01Dispatch planning and sortie sequencing
  • 02Flight records and execution traceability
  • 03Training workflow and stage continuity
  • 04Fleet availability and utilization control
  • 05Maintenance release and schedule alignment
  • 06Finance controls and payment visibility
  • 07Compliance surfaces for leadership teams
  • 08Cross-function operations visibility

Console Activity

Operational events stay linked instead of being re-entered across disconnected tools.

  1. 01Dispatch board aligns sortie slots with instructor and aircraft availability.
  2. 02Completed flight and training outcomes write directly into pilot progression records.
  3. 03Aircraft hours and event data inform maintenance windows and release readiness.
  4. 04Finance and compliance surfaces receive aligned operational evidence.

Student / Pilot Portal

A pilot-facing layer that reflects real training and operational history.

Current phase

Instrument proficiency | Stage 03

Recent activity

Cross-country sortie logged and signed

Document status

Medical and ID records up to date

Billing status

Open balance with traceable history

Pilot Continuity

A durable portal for every student and pilot.

This is not a disconnected add-on. The portal is the pilot expression of the same operational record used by schools and instructors.

  • 01Digital logbook continuity across organizations
  • 02Training stage and syllabus progression clarity
  • 03Signed records and document access
  • 04Integrated school billing visibility
  • 05Portable pilot identity over time

Aviation Network

Three entry points into the GA Flight network.

Operators, pilots, and the public each have a dedicated surface. All grounded in the same operational core.

School Discovery

Flight schools with credible public profiles.

Real training pathways, fleet records, and operational history — not a marketing directory.

Public Utility

Daily METAR and TAF awareness.

Free public surface for pre-flight planning, dispatch preparation, and club display mode.

Marketplace

Jobs and opportunities on aviation records.

Connections grounded in verified flight history and training progression — not generic profiles.

network · bootstrap phase

Honest framing : the network is young.

We are seeding the directory and the pilot-portable identity layer. Until coverage is meaningful, the network's value is primarily the infrastructure it sits on. We say so out loud rather than overclaiming.

Authority packs (Beta)API + webhooks (Beta)Automation rules (Beta)EFB runway (Planned)

Why GA Flight

Credibility earned through operational clarity.

GA Flight is built around the realities of flight training organizations and pilot progression, with product depth where aviation organizations need reliability most.

platform baseline

GA Flight is the infrastructure layer for European general aviation — built for flight schools, aeroclubs, ATOs and flight training organizations. Every operation writes to a signed ledger. Every pilot carries a portable identity. Every record survives the software.

Signed by the organization

Every operational record carries an Ed25519 signature from your organization's key — not a screenshot, not a PDF, a ledger entry.

Portable pilot identity

Pilots carry their signed logbook across schools, aeroclubs and training organizations. Identity is not locked to the vendor.

Offline-verifiable evidence packs

Authority packs verify against the signed chain without GA Flight needing to be online. The proof travels with the record.

Four composable layers

Identity, operations, authority and intelligence sit on the same substrate — observable and replaceable independently, not bundled into one opaque app.

EU-hosted, residency-guaranteed

Data stays in European jurisdictions. No US-to-EU transfers for training records, no extraterritorial exposure on pilot files.

Open pack format

Evidence packs are a documented format — readable beyond GA Flight and beyond today. Regulators can verify them in 2036.

01

One signed chain, not four silos.

Planning, flights, training, logbook, fleet, maintenance, finance and compliance all write to one thread. No re-keying between systems. No drift between sources.

02

EU-first finance. France, Germany and Portugal first complete.

Aligned with EASA Part-FCL record-keeping. Structured for DTO and ATO inspections. The finance core is a country-pack architecture — no hardcoded jurisdiction. France, Germany and Portugal are the first complete packs (FEC with lettering + CGI-aligned mentions; DATEV EXTF v7.0 + §14 UStG mentions + USt-IdNr / Steuernummer validation; PT-SAFT schema 1.04_01 with CompanyID = NIF + SNC chart + CIVA mentions). SAF-T baseline remains wired for PL/NO/LU/HU and those per-country packs ship in sequence. Shipped as scoped, not over-promised.

03

Records that outlive the vendor.

Signed evidence packs verify offline against a portable public key. If GA Flight disappeared tomorrow, your regulatory archive would still be readable and verifiable.

04

Infrastructure, not a vertical tool.

Four composable layers, typed packs, public verifier, open formats. The platform for European general aviation — not another vertical dashboard.

what we're building next

The trajectory, honestly stated.

No precise dates. No commitment calendar. The direction is clear and the code that backs it is already in motion.

  1. next 6 months

    Public pack verifier · OSS verifier CLI · /regulatory complete · permanent proof rail · 5 EU schools

  2. next 12 months

    Ops Twin TV mode · cross-org authority packs · pilot_portable in production · 20+ EU schools

  3. next 24 months

    Avionics SDK · EFB layer · partner API · 100+ listed schools · sector-reference chain

regulatory alignment

Aligned, never certified.

GA Flight is built to EASA Part-FCL record-keeping expectations, structured for DTO/ATO inspections, and verifiable offline for ARA.GEN.220 retention. Honest mapping, module by module.

Organization Entry

Move your organization onto one system.

Create your organization profile and align planning, flights, training, fleet, maintenance, finance, and compliance in one command structure.

  • For school owners and operations managers
  • For chief instructors and admin teams
  • For multi-aircraft training organizations

Student & Pilot Entry

Keep your pilot identity durable across organizations.

Follow progress, access records, and stay connected with the organizations and training pathways shaping your trajectory.

  • Logbook and progression continuity
  • Documents and payment traceability
  • Direct link into ecosystem opportunities
EU-Hosted
Data Residency
Signed Records
Training Evidence
Audit Trail
Every Action Logged
Portable ID
Pilot Continuity