Ever since Blaine Alan Gibson first crossed my radar screen, half a year before he found “No Step,” I’ve struggled to understand this eccentric character. In the media, he styled himself after Indiana Jones, always wearing a brown fedora. He portrayed himself as an inveterate adventurer and world traveler who before MH370 had pursued any number of quixotic international quests, including an attempt to find the lost ark of the covenant and an expedition to the site of the Tunguska explosion in Siberia. His was a wonderfully appealing persona. After I wrote about him in New York magazine, TV producers started getting in touch with me, hoping I could hook them up with him to pitch reality shows about his life.

He quickly became a central feature of the MH370 story, ubiquitous in media coverage the crash. But who, really, is this man of mystery? As with so many other aspects of this case, the more layers you peel away, the stranger things appear.

This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.deepdivemh370.com/subscribe

Last episode we talked about the surge of MH370 debris that started turning up in the western Indian Ocean in early 2016, and how search officials were optimistic that all this new data would help them understand where the plane went down. We focussed on drift modeling, and how the timing and location of the finds could have helped pin down the location of the crash through a process called reverse drift modeling. Today, we’re talking about other clues that the authorities were able to derive from the collected debris, namely the marine fauna found living on them. And to help us understand, we’re bringing in Jim Carlton, the world’s leading expert in marine invertebrates.

This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.deepdivemh370.com/subscribe

If there was one piece of debris, there should have been a lot more. Yet month after month went by without any further discoveries. Then in February of 2016 an independent researcher named Blaine Alan Gibson accomplished something no one ever had before: He set out to find a piece of MH370 debris, and he found one. In the months that followed, other people also found pieces of the plane. Blaine Gibson himself went on to find many more. For some, this influx of additional evidence only confirmed the conclusion that the plane had indeed crashed somewhere in the southern Indian Ocean. But in looking closer, I saw the same kinds of inconsistencies that have characterized every aspect of the case.

This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.deepdivemh370.com/subscribe

At 8.30am on July 29, 2015, on the northeastern shore of Réunion Island, a cleanup crew was working its way along a stretch of pebbly beach when a worker named Johnny Begue spotted an unfamiliar-looking object at the edge of the surf. Roughly rectangular and about six feet long, it somewhat resembled a stubby airplane wing encrusted with marine life. Soon gendarmes were on the scene, along with local news photographers. The piece was quickly identified as a flaperon, a part of a 777 wing’s trailing edge. Close examination revealed that it was indisputably a piece of MH370. Here at last, was physical evidence that the missing airliner really had crashed in the southern Indian Ocean.

But was that conclusion inescapable? In today’s episode we discuss how, once again, the evidence in this case looks stranger the closer you examine it.

This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.deepdivemh370.com/subscribe

For this episode, we’re trying something different. Until now we’ve spent each episode diving into a particular aspect of the mystery. This time, we’re pulling back to look at the mystery from a global perspective in order to address the question: What is this case like?

Just as every person has a unique character, a mystery can have a personality of its own, and MH370 certainly does. The dominant feature of that personality is strangeness. Time and again, a piece of evidence emerges which changes what we understand about the case – but then it turns out the evidence itself contains mysteries that themselves need to be elucidated.

In today’s episode, we look at five of the most striking examples of this phenomena. Together, they raise the question: why is the MH370 like this? Is it just a matter of coincidence, or is there some underlying aspect of the case that keeps pulling it toward the unexpected?

This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.deepdivemh370.com/subscribe

In our last episode, we talked about the search of the seabed, which started in October 2014. By that time the plane had been missing for 8 months. And while the seabed search was everyone’s best hope for finding the black box and solving the mystery, people hadn’t forgotten about floating debris.

You’ll recall that in the first month after the disappearance, there had been an extremely extensive search of the ocean surface by ships and airplanes from many nations, and they hadn’t spotted anything.

When Australia called off the surface search for Malaysia Airlines Flight 370 on April 28, Prime Minister Tony Abbot explained that “It is highly unlikely at this stage that we will find any aircraft debris on the ocean surface. By this stage, 52 days into the search, most material would have become waterlogged and sunk.”

But would the debris really have sunk? Modern aircraft are made of metal, composites, and plastic, materials that do not get waterlogged. If, as the Australian Transport Safety Board (ATSB) believed was most likely, MH370 ran out of fuel and then crashed, it would have been moving at hundreds of miles per hour when it hit the sea. Much of the resulting debris would have settled down through the water column, but innumerable pieces would have remained afloat. After Air France Flight 447 went down in the middle of the Atlantic in 2009, searchers found some 3,000 pieces of debris scattered across the surface.

Given that no debris from MH370 had been spotted from the air, a lot of people thought that the first hard proof of the plane’s fight might well take the form of flotsam washing up on a beach somewhere.

The question was, where would it wash up?

This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.deepdivemh370.com/subscribe

As the southern spring of 2014 approached the search authorities prepared to undertake a search of the seabed where their calculations indicated MH370 had gone. They hired a Dutch marine survey company called Fugro, which dispatched three ships to the area: Fugro Discovery, Fugro Equator and Fugro Supporter. The area they were going to search had been defined by the probability density function we’ve described earlier. It stretched about 600 miles long and covered water that was about three miles deep. One Australian politician declared that they were 97 percent confident that they would find the plane’s wreckage. Needless to say, it didn’t work out that way.

This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.deepdivemh370.com/subscribe

On July 17 Jeff was in his kitchen when the phone rang. It was a producer from CNN asking if he could go on air to talk about the Malaysia Airlines 777 that had just gone down over Ukraine. He’d spent so much time thinking about Ukraine and MH370 that it took him a moment to realize that she was talking about a completelely different airplane.

The details were still sketchy, but it seemed that in the late afternoon, Ukraine time, Malaysia Airlines Flight 17 had been flying from Amsterdam to Kuala Lumpur when it had exploded in midair. Initial reports suggested it might have been shot down by a surface-to-air missile while flying over territory held by Russia-backed rebels.

A Malaysia Airlines 777. Ukraine. Russia. The echoes seemed too overwhelming to ignore. Boeing 777s are among the most reliable airplanes in the world; none had ever been lost mid-flight before. There were 15 Malaysia Airlines 777s at the start of 2014, out of some 18,000 registered aircraft in the world, and two had come to grief under mysterious circumstances in less than five months.

But on air at CNN, all the other aviation analysts agreed that of course the destruction of MH17 so soon after the loss of MH370 could only be a freak coincidence. What connection could there possibly be?

It was soon established that the plane had been shot down by a surface-to-air missile. A 150-pound shrapnel-laced warhead had torn open the aluminum airframe, scattering passengers and crew into the 500 mph slipstream. In most airplane crashes, the question is: what happened? This time, it was: who did it, and why?

This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.deepdivemh370.com/subscribe

This week we look at where the plane could have gone if it didn’t go into the remote southern Indian Ocean. According to the Inmarsat data, it would have flown to the northwest, but that raises another question: if it flew over mainland Asia, why wasn’t it picked up by anyone’s military radar?

As you’ll recall, when Australian scientists applied the technique of Bayesian inference to the BTO data, they found that it indicated that the plane might have taken one of two flight paths, one to the north, one to the south:

In today’s episode we look at where exactly this route went, and whether we would expect that military radars would have picked it up.

This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.deepdivemh370.com/subscribe

Once the scientists at CSIRO had generated the probability distribution for the plane’s last known location on the 7th arc, the next question they had to answer was: how far did the plane travel from that point before it impacted the water?

As we discussed earlier, their goal was to define a search box within which the plane was likely to be found. The plane’s location along the 7th arc defined the length of the rectangle, and the distance it could have traveled from the 7th arc would define the width of the search box.

So the question of how far the plane could have flown after the last transmission depends on what the investigators thought was going on with the plane at that moment. You’ll recall that the plane took off at 16:42 heading from Kuala Lumpur, Malaysia to Beijing, China.. A flight that normally takes 5 1/2 hours but it was carrying enough fuel to keep it flying until around 00:12, in case it needed to divert somewhere else and needed extra fuel.

The inmarsat data showed the plane transmitting signals on a regular schedule — either in response to phone calls from the ground, or an hour after the last exchange. The last exchange in his sequence took place at 0:11 universal time. (That’s 8.11am Kuala Lumpur time, but to keep things simple let’s stick to Universal Time from here on out.)

Then at 0:19, the plane sent a request to Inmarsat to log in again. In many ways this request is similar to the one that was made at 18:25 — the SDU had logged itself off because it had powered down, and then tried to log on after getting turned back on again.

As you’ll recall, no one has a very good answer for why the SDU was turned off and back on again at 18:25. It’s a very unusual thing to happen in flight. But investigators had a very good idea about why the SDU might have turned on again at 0:19. They knew that by this time the plane would have been very close to running out of fuel. And once that happened, the engines would stop running, and the plane would lose electrical power. It would start to lose speed and/or altitude. And the satcom would disconnect.

But then an emergency situation a backup system would kick in. A device called a Ram Air Turbine, or RAT, would deploy—it’s a propellor that pops out into the slipstream to generate electricity like a windmill. This would generate enough electricity to start up a powerplant in the back of the airplane called the Auxiliary Power Unit, or APU. Its generatorwould return power to the plane’s electrical system, including the satcom. This is why the plane reconnected to the satellite.

The process from fuel exhaustion to logon would take 3 minutes 40 seconds. So the plane presumable ran out of fuel around 00:16, or about 5 minutes after the previous handshake at 0:11.

At 0:19 the plane had been out of fuel for almost four minutes, which meant the engines hadn’t been providing power. At first the ATSB assumed that the most likely scenario was that the plane had flown on a ghost flight, and after losing power had fallen into a descending spiral. Based on previous accidents they estimated that it would have fallen into the ocean within 30 nautical miles of the 7th arc.

Later they looked more closely at the BFO data, and they realized that there was a simple explanation for the seemingly strange values recorded at the time. Since the SDU’s doppler precompensation algorithm doesn’t account for vertical velocity, the BFO data could be explained if the final transmissions were made in a steep and accelerating dive.

This dive would be so steep that it could only be accomplished by a pilot who was actively pushing the plane’s nose down into a deliberate steep suicidal dive.

That being the case, the plane’s wreckage should be found very close to the 7th arc. Perhaps no more that 5 or 10 miles away. But, to give themselves a bit of leeway, the authorities decided to define an initial search area that was 400 miles long and 58 miles wide.

They had every reason to be confident, based on what they knew, that the plane would be within these 23,000 square miles.

Spoiler alert: it wasn’t.

This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.deepdivemh370.com/subscribe