An A320 fly-by-wire trainer that runs on a laptop with no graphics card and no installer: FlyByWire's real A32NX flight-control computers, hand-flown in the browser from Dallas Fort Worth.
Fly it in your browser ·
Download for Windows (unzip, double-click
A32X.exe) · The pilot's guide
In VR: open the site in a Meta Quest's browser and press VR at the bottom right, for the flight deck in true stereo (not yet tried on a headset).
It has two parts:
- A flight simulator (
flight/, GPLv3). The real FlyByWire A32NX flight-control computers — two ELACs, three SECs, two FACs, two FCDCs — run at 50 Hz and fly a JSBSim airframe of ours, fitted to cited A320 data. It flies in the browser, straight fromfile://, with a joystick or the keyboard, starting at Dallas Fort Worth (KDFW). It also flies headless, which is how it is tested. - A systems trainer (
app/, MIT): systems, ECAM, flows and graded drills.
Unofficial. "Airbus", "A320" and "A32NX" belong to their owners. Not affiliated with Airbus, FlyByWire Simulations or Aerowinx, and not suitable for type training.
The flight simulator is the product, at its seventh pre-release,
0.1.6 (ROADMAP.md, P7):
- The A32NX computers fly our A320 in normal, alternate and direct law. The instructor's failures take them there, and the scripted crew lands every degraded case but the double hydraulic losses. In the clean configuration the protections hold the A320's bank, load-factor and low-speed angle-of-attack limits.
- The airframe is fitted to cited data: stall speeds and alphas by configuration, approach attitudes,
the drag rise, roll and damping, the stall and past it, the drag of the flaps and gear, and its
engines' thrust and spool-up against the type certificate, the certification rules and the public
ANP noise-and-performance database, whose A320 entry Airbus developed: inside 77 of its 80 targets,
the three outside held-out checks left open (the pitching moment deep past the stall, and the stall
at Mach 0.70 and 0.78).
Public numbers, not Airbus's flight-test data.
flight/README.mdhas every row, its source, and the fit. - In the browser: the flight core as WebAssembly, a joystick mapped from the pilot's own hands, KDFW and Dallas drawn as a 1980s full-flight simulator drew them (a GPU tier over a floor that runs on software rendering), an ILS on every runway, wind and turbulence, ground idle and reverse thrust, and a VR button for a Quest headset (true stereo from the captain's seat; untested on a headset).
- The gate's judge scores a hand-flown ILS against stabilised-approach bands, from 1,000 ft to the stop; a saved recording names the build that flew it and replays natively to the same verdict. The debrief plays the flight back on a timeline, in the manner of Tacview, and a saved recording opens in the page (Ctrl+O) and flies again through the core, its verdict set against the one it was saved with.
- Left in P7: the gate itself, five hand-flown approaches, stable and repeatable. Known open: a fast, full back-stick pull with full flaps can stall it, A32NX's protection acting on a lagged alpha (asked upstream as flybywiresim/aircraft discussion #11009). After the gate, the cockpit displays (P8) and the FMS (P9).
The systems trainer. No Node needed: open app/web/index.html — double-click it. The page is one
committed script with its content inlined, so it works straight off the disk. To rebuild or develop:
cd app
npm ci
npm run build:web
npm run check # typecheck + 182 tests
The flight simulator. Nothing to build: fly it at flightsim.bochen.xyz,
or take the Windows zip from Releases, unzip it
and double-click A32X.exe (Windows SmartScreen warns on the unsigned launcher: More info, Run anyway).
The pilot's guide says how to fly it. To build it yourself: CMake against two
clones kept outside this repository, A32NX and JSBSim at pinned commits; the browser build adds
Emscripten 6.0.12 and Node. flight/README.md has the recipes: Build and run, The browser
simulator and Getting the sources. Native, in short:
cmake -S flight -B flight/build -DA32NX_DIR=<A32NX clone> -DJSBSIM_DIR=<JSBSim clone>
cmake --build flight/build --config Release
ctest --test-dir flight/build -C Release --output-on-failure
Two artefacts, as ROADMAP.md sets them (Decisions, packaging):
a32x-cbt.zip: the systems trainer alone, MIT.npm run packageinapp/builds it andnpm run gatechecks it.a32x-sim-0.1.6-win64.zip: the flight simulator for Windows, GPLv3.A32X.exe, a launcher of ours, opens the page beside it in Microsoft Edge as an app window, or in the default browser; the trainer rides along under its own MIT notice, with every licence and notice. Beside it,a32x-sim-0.1.6-source.zip, its Corresponding Source: this repository at the commit and the exact A32NX and JSBSim sources compiled into it, with Emscripten 6.0.12 named.npm run releaseinflight/webbuilds both, the first from the second, andnpm run release:gatechecks them (flight/README.md, The Windows release). Published on GitHub as pre-releases, each with its source zip andSHA256SUMS; from 0.1.1 the pilot's guide comes beside them as a PDF.
Neither needs an installer. Unzip, then open the trainer's index.html, or run the simulator's
A32X.exe. Tested in Chrome and Edge on Windows; other browsers and systems have not been tried.
| path | what |
|---|---|
app/ |
the systems trainer — systems, panel, ECAM, procedures. MIT. |
flight/ |
the flight simulator: the A32NX computers flying a JSBSim airframe, the browser shell (flight/web), and the tools that score and fit the airframe. GPLv3. |
docs/ |
the pilot's guide (and its pictures), provenance, architecture, and the design study of the PSX reference |
reference/ |
screenshots |
Everything outside flight/ is MIT (LICENSE). flight/ is GPLv3 (flight/LICENSE): it compiles
FlyByWire A32NX, GPLv3, and JSBSim, LGPL-2.1. MIT code may travel inside the GPLv3 simulator; nothing
from flight/ goes into app/.
No third-party source is vendored. app/ is original TypeScript; the behaviour in it was worked out
by study. docs/provenance.md names every source and the position taken on each.
Read CLAUDE.md, then docs/provenance.md, then ROADMAP.md. The suite must be green before any
commit.