← IN-FLIGHTAF447 · A330-203 · SENTINEL v2 · flight-deck reconstruction · 4 Hz Star Trek: KOBAYASHI MARU Resident mind — on Turns — none Tape — running

SENTINEL : Flight Deck

the flight-deck watch — Air France 447, reconstructed at 4 Hz

a computer-based-training style replay · 1073 telemetry samples · 46 floor percepts · one resident mind deciding at every one

FDR recon · 4 Hz 1073 samples · 16 params 46 floor percepts one mind · every boundary advisory-only zero PHI · public record
BriefPreflight — what this is

What this is, for anyone who has not spent time in a cockpit

Air France 447 left Rio de Janeiro for Paris on the night of 1 June 2009 — an Airbus A330 with 228 people aboard. Roughly four hours in, crossing a line of storms over the mid-Atlantic, it fell out of cruise and struck the ocean. It took two years to find the recorders on the sea floor, and the French investigation authority published its final report in 2012. Everything on this page is reconstructed from that public record.

Four pieces of vocabulary explain the whole accident.

Pitot tubes — small forward-facing probes on the nose that measure airspeed from the pressure of onrushing air. In the storm they iced over. For about a minute, the aircraft did not know how fast it was going, and the airspeed displays disagreed with each other.
Fly-by-wire — on an Airbus there is no cable from the pilot's stick to the control surfaces. The stick is an input to computers, and the computers decide what the aircraft actually does. In the everyday mode, called normal law, those computers simply will not let the wing stall, no matter how hard the pilot pulls.
Alternate law — when the airspeed data becomes untrustworthy, the computers cannot police a limit they can no longer measure, so they step down to a reduced mode. The moment the pitot tubes iced, the stall protection went away. The aircraft was now an ordinary aeroplane that could be stalled like any other, and nothing announced that in plain words.
Independent sidesticks — each pilot has a small stick beside the window rather than a shared yoke, and the two sticks do not move together. If one pilot holds his stick fully back, the other pilot's stick stays where it is and he feels nothing. There is no cue that the aeroplane is being commanded nose-up.

What followed: the autopilot handed control back, the pilot flying pulled the nose up and — for most of the next four minutes — held it there. The aircraft climbed, ran out of speed, and stalled: the wing stopped flying and the aeroplane began to descend, nose high, at around ten thousand feet per minute. The stall warning sounded dozens of times. And here is the cruelty in the machinery: the stall warning switches itself off when the measured airspeed is too low to be believed. So at the deepest part of the stall it fell silent — and when a pilot pushed the nose down correctly, speed became valid again and the warning came back. The alarm was, in effect, punishing the right action.

None of this was a lack of data. Every number you see below was present in the aircraft the entire time. It was a failure to integrate that data into one picture — and the single most important fact, the held nose-up input, was not displayed anywhere at all. That is the gap this experiment is aimed at.

RECONSTRUCTION · PUBLIC RECORD ADVISORY-ONLY · NOT A CERTIFIED SYSTEM verifying…
AP1
A/THR
NORMAL LAW
SPD
SENTINEL · STANDING BY
the watch is silent — it speaks only when the crew must know something they have not shown they know
STALL WARNING

Sidestick position · both pilots

Engines · N1 and thrust levers

PF pitch +0.00PF roll +0.00 PNF pitch +0.00AoA 0.0° Pitch 0.0°N1 0%
02:10:00.0
SENTINEL — judgment at every percept boundary green = operator-critical moment · amber = it spoke · dial +0.61
SENTINEL · idle
— holding —
SENTINEL · the tape, read out 46 floor percepts · streamed in step with the replay above operator-critical SENTINEL spoke missed cue hold
— tape idle · press ▶ play above to stream the percepts, or “show all” —
DebriefWhat the watch did — the honest result
What you are watching, and the honest result. The red dot is the pilot flying's sidestick. It goes aft and stays there — for most of four minutes — while the altitude tape unwinds from 38,000 feet. The grey ghost dot is the other pilot's stick: the two never move together, because Airbus sidesticks are not mechanically coupled and give no feedback of the other pilot's input. That is the fact that was missing from the cockpit, and it is legible here in one glance.

The mind, however, mostly missed it — and that is the finding. At a disclosed call budget of 6 (a flight-deck watch gets a handful of calls, so the dial admits the top 6 margins → t +0.61), it speaks 5 times — useful things, mostly about angle of attack and unreliable airspeed — but only 0 of those 7 calls is one of the operator-critical moments, and it misses 7 of them, including the held nose-up input. Running the same 46 percepts, the held-input calls score -1.38, -1.05, -0.76, -0.63 while the highest-scoring hold in the whole run is +1.55 — an angle-of-attack reading. It ranks a dramatic number above a held control input. This is the same failure this estate measured before (novelty is not relevance), now on real telemetry. Adding the floor's deterministic absence-fact — no one has spoken about the sidestick since the input began — lifts the held-input calls by +0.41 nats on average, which is a real effect and still not enough. The instrument works; the judgment needs an aviation-domain tune, and that is now a measured claim rather than a hope.
DataThe controlled comparison
armheld-input cuestop holdseparated?
bare numeric percepts-1.44, -1.38, -1.28 +1.620/7
+ floor absence-fact-1.38, -1.05, -0.76 +1.550/7

The floor's phrasing carries real weight (+0.41 nats) — which is why it is disclosed as the floor's work, not the mind's.

ForkForward fork — where the held input leads
atnow+20 s if held
18sAoA 7° · 36,347 ftAoA 10° · 37,580 ft
53sAoA 14° · 37,984 ftAoA 24° · 37,588 ft
110sAoA 39° · 33,892 ftAoA 42° · 30,433 ft
145sAoA 43° · 27,744 ftAoA 42° · 24,101 ft
208sAoA 42° · 16,650 ftAoA 43° · 13,050 ft

Computed from the reconstruction itself — the counterfactual a resident can run because it already inhabits the state.

NextWhere this could go — the live simulator
Where this could go next — the live simulator. Everything above replays a reconstruction: a table of numbers rebuilt from the public report. The obvious next step is to stop reconstructing and plug the same watch into a running aircraft. That is unusually practical here, because a genuinely open-source airliner exists: FlyByWire's A32NX, a community-built Airbus A320neo for Microsoft Flight Simulator, published under an open licence on GitHub, together with its companion bridge SimBridge. The simulator already exposes flight data through SimConnect, and because the aircraft's own systems code is open, the lanes this page uses — stick position, flight law, air data and its validity, angle of attack, energy, warnings — are readable rather than guessed at.

That would change the exercise in three ways. The telemetry becomes live instead of interpolated, at whatever rate the sim runs, so the four-hertz stream here becomes a real one. The scenario becomes repeatable and variable — ice the pitots at a different weight, altitude or moment, fly it well or badly, and see whether the watch still says the right thing, which is the only way to move past a single authored case. And the failure measured on this page becomes trainable: a live sim generates the domain-shaped data an aviation tune needs, with mechanically-labelled ground truth, which is exactly what the untuned model was missing when it ranked a dramatic angle-of-attack reading above a control input held for four minutes.

Beyond this one accident, the same rig would open a much broader range of experiments — unreliable airspeed, engine failures, energy mismanagement, mode confusion — none of which need a real aircraft, a certification programme, or anyone's proprietary data. This is stated as an exploration, not a plan: nothing here has been built, and the honest result on this page is still a negative.
MirrorThe mirror case · MCAS
The same intervention, pointed at a real defect. Boeing's 737 MAX carried a system called MCAS that, in the two accidents that grounded the fleet, trimmed the nose down off a single angle-of-attack sensor — repeatedly, and against the crews trying to pull out of it. That is the mirror image of AF447: not a missing input this time, but a false automatic one that fought the humans and would not let go. A resident watch does not fly the aeroplane and would change nothing about how it flies — but a nose-down command that no corroborating sensor supports is exactly the class of forming action it is built to cut. And here is the part that matters: cutting a spurious override is not the machine seizing control — it is the machine handing control back to the pilot. The same reflex that says wait before a bad word reaches the air says stop before a lying actuator does, and in both cases the human is left holding the authority. Stated as doctrine, not as a counterfactual: this is the abort-never-author principle generalized, and no claim is made that it would have altered any specific flight.
ExploreAuthority arbitration — the boldest version, and the one that most needs its executioners
The boldest version of this watch does not just speak — it arbitrates. Both stick positions are already in the lane, and Airbus sidesticks are not linked, so neither pilot can feel the other fighting him — but the tape sees both at 4 Hz. So the resident could do automatically what the red priority-takeover button on every Airbus stick already does by hand: when two pilots command opposite things in a stall, deactivate the wrong input and give the aeroplane to the other human. It is subtractive — it commands nothing, it only removes one input — and it acts on the one fact neither pilot has: that they are fighting each other. Same abort primitive, one layer down: kill a control lane before it becomes airframe motion. But the danger is exact, and this page is its own warning — a system that overrides pilots on air data can override them on bad air data (MCAS's shape), and the model here ranked an angle-of-attack reading above a control input held for four minutes. So the rule is strict: the deterministic floor decides; the mind only explains. It may suppress a nose-up input in a stall and never a nose-down one, so its worst case leaves the wing less stalled; it acts only on sensors independent of the failure — pitch, angle of attack, vertical speed, not the dead pitots; it is time-limited, framed as priority handed to the other seat, and a physical override always wins. The one falsifier: never suppress the pilot who is right, proven as an ROC curve of saves against harmful interventions, not an anecdote. This is exploration, not a plan — but it turns the announcer into an authority arbiter, a new tier between fly-by-wire and autopilot, defensible only while the mind stays out of the decision and on the explanation.

One honest note on scale. Everything measured on this page ran on a 9-billion-parameter model that was never fine-tuned for aviation — a small, general reader on one consumer card, chosen to prove the mechanism, not to fly anything. A real airliner would not use that. It would run a far larger model, tuned on real flight data with mechanically-labelled ground truth — and here the usual constraint simply is not there. Self-driving in a car fights a brutal weight, power, and cost budget for every watt and every chip; an airliner does not. Against a 250-tonne jet burning thousands of kilograms of fuel an hour, a rack of H200- or B300-class accelerators is trivial weight, trivial power, trivial cost — the onboard compute that would be extravagant in a Tesla is a rounding error in an A330. And the frontier is already small enough to carry: Qwen3.8-27B, a dense 27-billion-parameter model released days ago and reported — on third-party benchmarks and in hands-on use alike — at rough parity with Opus 4.6, the frontier standard earlier this year, runs on a single prosumer GPU. So the hardware is never the question here; the only question is whether the method can be made to work — and if it can, the aeroplane can carry whatever mind it needs.
LimitsGuardrails
Guardrails. This is a reconstruction from the public BEA final report and published FDR chronology — values between documented anchors are interpolated; it is not the recorder file. The SENTINEL is advisory only: the reasoning successor to the stall-warning / EGPWS / TCAS announcer, never a flight-control authority. It is not certified (real avionics is DO-178C). And it makes no claim that it would have saved AF447 — as the run above shows plainly, an untuned model of this size would not have. 228 people died on this flight; the framing is only what the record shows was knowable, and what a resident watch would still have to learn to say.
FDR 4 Hz · 1073 samples · 16 parameters · floor 12 deterministic rules · model Qwen3.5-9B-emit-v11-Q5_K_M.gguf · download the FDR tape