WEBVTT 00:00:00.000 --> 00:00:05.179 Welcome to Vanished Skies, MH370. Most stories 00:00:05.179 --> 00:00:07.839 about this flight start with opinions or end 00:00:07.839 --> 00:00:11.140 with assumptions. This one starts with a method. 00:00:11.960 --> 00:00:15.019 We work inside -outside, meaning we follow what 00:00:15.019 --> 00:00:18.239 the aircraft systems do on the inside and match 00:00:18.239 --> 00:00:22.179 it to what the world sees on the outside. Radar, 00:00:22.480 --> 00:00:26.039 satellite handshakes, timing, route logic, all 00:00:26.039 --> 00:00:29.370 treated like one single chain. Think of it like 00:00:29.370 --> 00:00:33.250 an outside black box, built from signals, not 00:00:33.250 --> 00:00:37.189 speculation. And once you see the pattern, it 00:00:37.189 --> 00:00:40.149 doesn't unsee. Ed, let me pick it up right there. 00:00:40.590 --> 00:00:43.229 Because this is the exact moment where the audience 00:00:43.229 --> 00:00:46.049 needs a new lens. Up to now, you've been explaining 00:00:46.049 --> 00:00:49.689 how we stopped looking at MH370 as only an outside 00:00:49.689 --> 00:00:53.390 story. Radar on one side, satellite on the other, 00:00:53.770 --> 00:00:55.929 and instead started treating the airplane like 00:00:55.929 --> 00:00:58.920 its own signal environment. a system that can 00:00:58.920 --> 00:01:02.240 be studied from the inside out. So now we're 00:01:02.240 --> 00:01:04.459 going to introduce something that becomes a visual 00:01:04.459 --> 00:01:08.319 language for that. This is the red BFO template. 00:01:09.000 --> 00:01:11.140 And before anyone thinks this is just another 00:01:11.140 --> 00:01:14.140 graph, it's not. The red template is more like 00:01:14.140 --> 00:01:17.019 a recorder surface, almost like flash paper. 00:01:17.799 --> 00:01:20.620 Think of it like this. Every time something changes 00:01:20.620 --> 00:01:23.060 in the system, power shifts, resistance shifts, 00:01:23.219 --> 00:01:26.780 a mode changes, there's a tiny burn in the signal. 00:01:27.069 --> 00:01:29.890 Not a flame you see, but a reaction you can measure. 00:01:30.469 --> 00:01:32.829 And when you lay those reactions out across time, 00:01:33.430 --> 00:01:36.689 what you get is a trackable pattern. That's what 00:01:36.689 --> 00:01:39.950 the red template is doing. It's taking the BFO 00:01:39.950 --> 00:01:42.849 line, the one most people treat like a simple 00:01:42.849 --> 00:01:45.269 Doppler number, and showing it as a behavior 00:01:45.269 --> 00:01:49.170 trace, a fingerprint, a timeline of how the system 00:01:49.170 --> 00:01:52.530 is reacting. Because in our approach, that BFO 00:01:52.530 --> 00:01:55.829 line isn't just a value. It's a record of effort. 00:01:56.079 --> 00:01:58.760 how much power is being pulled against resistance 00:01:58.760 --> 00:02:02.379 in the system. And here's the key. Once you can 00:02:02.379 --> 00:02:05.060 see it this way, you can stop treating the signal 00:02:05.060 --> 00:02:07.439 like a mystery and start treating it like a readable 00:02:07.439 --> 00:02:10.099 sequence. That's why this red template comes 00:02:10.099 --> 00:02:13.219 first. Because it sets you up for the next step, 00:02:13.620 --> 00:02:16.659 what Ed calls the barcode effect, where we take 00:02:16.659 --> 00:02:19.479 what used to look like one long continuous stream, 00:02:20.039 --> 00:02:23.379 like that big blue strip of ACARS activity, and 00:02:23.379 --> 00:02:26.439 we start rebuilding it into segments. We don't 00:02:26.439 --> 00:02:28.840 lose the big picture. We rebuild it with more 00:02:28.840 --> 00:02:32.759 resolution. So as you look at this red BFO template, 00:02:33.539 --> 00:02:37.199 don't look for the answer right away. Look for 00:02:37.199 --> 00:02:40.740 the structure. Where the signal tightens. Where 00:02:40.740 --> 00:02:44.539 it releases. Where it changes rhythm. Because 00:02:44.539 --> 00:02:46.500 those are the moments the airplane is telling 00:02:46.500 --> 00:02:49.520 you something happened. And once we anchor that 00:02:49.520 --> 00:02:52.620 visually with the red template, Then Ed can bring 00:02:52.620 --> 00:02:55.240 in the next template and show you how BFO and 00:02:55.240 --> 00:02:58.439 BTO work together. Not as separate lines, but 00:02:58.439 --> 00:03:02.060 as a matched pair. Timing and frequency, distance 00:03:02.060 --> 00:03:05.039 and behavior, outside measurement and inside 00:03:05.039 --> 00:03:08.639 reaction. So that's the handoff. Red template 00:03:08.639 --> 00:03:11.180 first, because it teaches your eyes how to read 00:03:11.180 --> 00:03:14.360 the system. Then we build the full picture from 00:03:14.360 --> 00:03:17.379 there. Because the internet is full of signals 00:03:17.379 --> 00:03:20.080 that look scientific, but they don't all behave 00:03:20.080 --> 00:03:23.550 the same way. From here on out we're comparing 00:03:23.550 --> 00:03:28.569 two worlds BFO BTO which is a closed handshake 00:03:28.569 --> 00:03:33.189 record versus WSPR which is an open field inference. 00:03:34.270 --> 00:03:37.889 First we lock in definitions. BTO is timing, 00:03:38.349 --> 00:03:41.729 range, distance. It gives you an arc constraint. 00:03:43.289 --> 00:03:47.729 BFO is frequency offset, motion trend. It's Doppler 00:03:47.729 --> 00:03:50.009 sensitive and it tells you whether the aircraft 00:03:50.009 --> 00:03:52.870 is moving toward or away from the satellite line 00:03:52.870 --> 00:03:56.349 of sight. The key is these two measurements come 00:03:56.349 --> 00:04:00.009 from the same SATCOM handshake cycle. That's 00:04:00.009 --> 00:04:02.669 why they pair together. One anchors distance, 00:04:02.810 --> 00:04:07.610 the other anchors motion. Point at gold side, 00:04:08.129 --> 00:04:13.569 timing range measurement BTO. Blue side, frequency 00:04:13.569 --> 00:04:18.769 offset measurement BFO. Emphasize paired constraints, 00:04:19.149 --> 00:04:23.279 same event loop. On screen micro tag, optional, 00:04:23.600 --> 00:04:28.720 BTO, where, range, BFO, how, motion trend.