
After a day in port in Fremantle, Australia, to refuel and resupply, Armada 7806 is headed back to the MH370 search area. Based on an average speed of around 10 knots, it should reach there around 02:30 UTC on March 11.
There is a sign that this phase of the search will be shorter than expected: Armada 7806 is self-reporting through Automatic Identification System (AIS) marine tracking that its destination is Cape Town, South Africa. As this is considerably further from the search area than Fremantle, it would make no sense to travel to Cape Town and then return to the search area. A leg to Cape Town would also limit the time that Armada 7806 could spend in the search area, as the port-to-port time is typically less than four weeks.
So why might Armada 7806 be returning to Cape Town after visiting the search area. I offer three possibilities:
- During the last phase, something resembling a debris field was detected. If so, Armada 7806 might travel to this spot, launch one or more AUVs, and get better data, including possibly images. After a short time gathering this data, it might travel to Cape Town before it is reassigned a new mission. Another vessel with ROV capability would then be assigned to better document the debris field and perhaps recover some wreckage.
- There are ongoing contractual issues between OI and Malaysia and the search will be cut short even if no debris field is detected.
- The AIS destination is not correct, either due to an error or due to misdirection.
With the recent announcement by Malaysia saying that the search contract with Ocean Infinity is approved and the signing is imminent, it reduces the probability of (2). Once the contract is signed, we can almost completely eliminate this possibility.
If (3) is correct, we would expect that Armada 7806 would remain in the area for a number of weeks to collect more data and then return to Fremantle. If (1) is correct, the time in the search area will be short. So the length of time that Armada 7806 remains in the search area will tell us a lot.
It is difficult to assign relative probabilities to these three scenarios. Perhaps it is confirmation bias that I believe that (1) is most probable. In any event, we’ll know more in the coming days.
Steep Slope
We can zoom into where Armada 7806 is headed to see why this area might be interesting. Presently (and this could change), Armada 7806’s course is towards a steep slope that was searched with AUVs during the last phase of this search. This steep slope also lies within the areas scanned previously by GO Phoenix using a towfish during the ATSB-managed part of the previous search effort. Parts of this slope were also previously scanned by Ocean Infinity with the vessel Seabed Constructor and its team of seven AUVs. A return to this area once again highlights the difficulty in scanning terrain with steep slopes and other uneven topography, even with AUVs.

The part of the steep slope that seems to be the target is part of the same slope that we designated the High Priority Search Area (HPSA), but further south along that slope. At the time we identified the HPSA, we were not aware that so much more of the slope was not adequately scanned during OI’s last search. If the debris field is truly along this slope, our recommendation to fill-in the low quality data near the 7th arc before extending outwards from the arc was accurate. We said:
As the a) final BFO values, b) the lack of IFE log-on, and c) the end-of-flight simulations all suggest an impact close to the 7th arc, a high priority should be to scan the areas closest to the 7th arc that were either never scanned or have low quality data before searching new areas further from the 7th arc. However, with pilot inputs, it is possible that MH370 glided after fuel exhaustion beyond the areas that were previously scanned. Therefore, searching wider along the 7th arc should also be part of the search plan if areas closer to the 7th arc are unsuccessful in locating the debris field...A steep slope to the south of where UGIB predicts MH370 crossed the 7th arc happens to lie along the extended path of the reconstructed route, and much of this slope remains unscanned. For this reason, the unscanned area surrounding S34.52 E93.84 should be designated a High Priority Search Area.
Although we are speculating about what might take place next based on very limited information, the next several days could prove to be very interesting.