Welcome to Vanished Skies, MH370. Most stories
about this flight start with opinions or end
with assumptions. This one starts with a method.
We work inside -outside, meaning we follow what
the aircraft systems do on the inside and match
it to what the world sees on the outside. Radar,
satellite handshakes, timing, route logic, all
treated like one single chain. Think of it like
an outside black box, built from signals, not
speculation. And once you see the pattern, it
doesn't unsee. Ed, let me pick it up right there.
Because this is the exact moment where the audience
needs a new lens. Up to now, you've been explaining
how we stopped looking at MH370 as only an outside
story. Radar on one side, satellite on the other,
and instead started treating the airplane like
its own signal environment. a system that can
be studied from the inside out. So now we're
going to introduce something that becomes a visual
language for that. This is the red BFO template.
And before anyone thinks this is just another
graph, it's not. The red template is more like
a recorder surface, almost like flash paper.
Think of it like this. Every time something changes
in the system, power shifts, resistance shifts,
a mode changes, there's a tiny burn in the signal.
Not a flame you see, but a reaction you can measure.
And when you lay those reactions out across time,
what you get is a trackable pattern. That's what
the red template is doing. It's taking the BFO
line, the one most people treat like a simple
Doppler number, and showing it as a behavior
trace, a fingerprint, a timeline of how the system
is reacting. Because in our approach, that BFO
line isn't just a value. It's a record of effort.
how much power is being pulled against resistance
in the system. And here's the key. Once you can
see it this way, you can stop treating the signal
like a mystery and start treating it like a readable
sequence. That's why this red template comes
first. Because it sets you up for the next step,
what Ed calls the barcode effect, where we take
what used to look like one long continuous stream,
like that big blue strip of ACARS activity, and
we start rebuilding it into segments. We don't
lose the big picture. We rebuild it with more
resolution. So as you look at this red BFO template,
don't look for the answer right away. Look for
the structure. Where the signal tightens. Where
it releases. Where it changes rhythm. Because
those are the moments the airplane is telling
you something happened. And once we anchor that
visually with the red template, Then Ed can bring
in the next template and show you how BFO and
BTO work together. Not as separate lines, but
as a matched pair. Timing and frequency, distance
and behavior, outside measurement and inside
reaction. So that's the handoff. Red template
first, because it teaches your eyes how to read
the system. Then we build the full picture from
there. Because the internet is full of signals
that look scientific, but they don't all behave
the same way. From here on out we're comparing
two worlds BFO BTO which is a closed handshake
record versus WSPR which is an open field inference.
First we lock in definitions. BTO is timing,
range, distance. It gives you an arc constraint.
BFO is frequency offset, motion trend. It's Doppler
sensitive and it tells you whether the aircraft
is moving toward or away from the satellite line
of sight. The key is these two measurements come
from the same SATCOM handshake cycle. That's
why they pair together. One anchors distance,
the other anchors motion. Point at gold side,
timing range measurement BTO. Blue side, frequency
offset measurement BFO. Emphasize paired constraints,
same event loop. On screen micro tag, optional,
BTO, where, range, BFO, how, motion trend.