Artemis: The Hunt for MH370

Unmanned Systems Maritime Search and Rescue    

On 8 March 2014, a Boeing 777-200ER commercial airliner operated by Malaysia Airlines lost contact with air traffic control and disappeared from radar tracking systems. The regularly scheduled international flight (MH370) originating from Kuala Lumpur, and bound for Beijing, failed to reach its destination. The loss of all 227 passengers and 12 crew members prompted what has been the largest, and most expensive, multi-national search effort in aviation history (Pearlman, 2014). On 21 March 2014, the U. S. Navy dispatched Phoenix International Holdings, Inc. (Phoenix) to conduct undersea search services as part of a Naval Sea Systems Command (NAVSEA) support contract (LeHardy & Moore, 2014). Phoenix deployed a Bluefin 21 autonomous underwater vehicle (AUV) as part of the effort to locate the submerged wreckage (LeHardy & Moore, 2014). While the aircraft’s data recorders have not been located, the employment of the AUV did lead to successful collection of data at extreme depths. This paper will examine the platform used by Phoenix and respond to questions posed in Module 2.4 as they relate to the system.

Figure 1. Phoenix International’s ‘Artemis’ Bluefin-21 Autonomous Underwater Vehicle (AUV) image as published on http://www.phnx-international.com/phnx/phoenix-equipment/auv/

Bluefin Robotics, now a General Dynamics subsidiary, developed the Bluefin-21 (see Figure 1) as a modular platform capable of employing multiple sensors and payloads designed to function underwater autonomously. The range of applications include offshore survey, archaeology & exploration, oceanography, mine countermeasures (MCM), unexploded ordnance (UXO), and as demonstrated by Phoenix, search & salvage (Bluefin-21, 2017). The system specifications of the Phoenix operated Bluefin-21, affectionately known as ‘Artemis’, are listed in Table 1.

Table 1

Artemis AUV Specifications

AUV
Max Operating Depth	5,000 meters
Diameter	21 inches / 0.53 meters
Length	17.7 feet / 5.38 meters
In-Air Weight	1,764 pounds / 800 kg (approximate)
Speed	2 to 4 knots
Estimated Endurance	~20 hours, @ 3 knots
Manufacturer	Bluefin Robotics Corporation
AUV Subsystems
Navigation
Inertial Navigation System	Kearfott Custom KN-6053
ADCP/Doppler Velocity Log	Teledyne RDI Workhorse Navigator 300kHz
Ring Laser Gyro	Kearfott T24 Monolithic RLG
Acoustic Positioning System	Lodestar Gyro USBL [8084]
Depth Sensor	Paroscientific 8CB7000-I
GPS	Thales/ Ashtech DG14
Sound Velocity Sensor	Valeport Mini SVS
Backseat Control Architecture	Bluefin Robotics
Communications
Acoustic Modem	Sonardyne AvTrak 6 [8220]
RDF Beacon	Bluefin - RDF
RF Serial Link	Freewave FGRMT
Iridium Satellite Modem	NAL 9601-D-1
Ethernet Direct	Cirexx CPU1232 Ethernet
Acoustic Payload
Multibeam Echosounder	Reson 7125 (400 kHz)
Side Scan Sonar	EdgeTech 2200-M (120 / 410 kHz)
Sub-bottom Profiler	EdgeTech DW2-16 (2-16 kHz)
Optical Payload
Camera	Proscilica GX1920
Sensor	Sony ICX674
Resolution	1936 x 1456 pixels
Geophysical Payload
Magnetometer	Honeywell HMR2300 3-axis magneto-resistive
Self Potential Sensor	Ultra Electronics (Ag-AgCl)
CTD	AML Oceanographic SmartX
Multibeam Echosounder	Reson 7125 (bathymetry & backscatter)

Note. Artemis specifications as published by Phoenix International Holdings, Inc. (Artemis Specifications, 2016)

Phoenix’s efforts to conduct autonomous search for the wreckage of MH370 with Artemis began after a suspected acoustic beacon signal was traced with towed pinger locators (TPL) to an area of interest in the Indian Ocean. The AUV was programmed to conduct seafloor survey with side scan sonar at the maximum designed operating depth (LeHardy & Moore, 2014). Autonomous search operations were conducted with the system for 70 days covering an area of 860 square kilometers (LeHardy & Moore, 2014). The aircraft was not located, however the high-resolution data collected by Artemis allowed analysts to conclude the wreckage was not located in the search area with a high level of confidence. A wide scale subsurface search of such a large area would have proven much more difficult and costly without the assistance of the Bluefin-21 AUV.

What proprioceptive and exteroceptive sensors does the system have that are specifically designed for the maritime environment?

The Bluefin-21 is designed to operate underwater autonomously, and therefore has many sensors that contribute to its ability to function in the maritime environment. It shares many sensors commonly found on unmanned systems designed to operate in various environments. The proprioceptive subsystems that contributes most directly to subsurface marine operation are the inertial navigation system, the acoustic position system, the depth sensor, and the sound velocity sensors. All of the systems contribute data necessary to navigate in an environment with restricted radio frequency transmissivity. The exteroceptive subsystems that enable the platform to scan below the surface so effectively are the multi-beam sonar, side scan sonar, and sub-bottom profiler. Without those, searching and mapping at the depth the vehicle is designed to operate, would not be feasible.

What is one modification that could be made to the existing system to make it more successful at search and rescue operations?

Phoenix was able to employ the vehicle at its maximum designed operating depth for extended duration missions. During the time of operation, software changes were made to allow for operators to monitor battery status (LeHardy & Moore, 2014). Though a minor adjustment, the change contributed to a significant increase over the originally designed operating endurance; from 20 hours originally, to a record 27 hours and 9 minutes (LeHardy & Moore, 2014).

There is an implied urgency with the mission of search and rescue. With that in mind, any modification to the system that would improve the speed of search could directly contribute to a higher potential for rescue. If a change is made to the sensor payload, any improved sonar capability that increases the sweep width could, in turn, reduce the number of passes required to search an area.

How can maritime unmanned systems be used in conjunction with unmanned aerial systems (UAS) to enhance their effectiveness?

For larger volumes of data, radio frequency (RF) transmission is a well established method. RF transmission in the maritime environment can be challenging for over the horizon communications from surface to surface at greater distances. Unmanned aerial systems could easily act as an airborne repeater to relay data over greater distance. This would most likely require the AUV to surface to do so, however.

What advantages do unmanned systems have over their manned counterparts? Are there sensor suites that are more effective on unmanned systems?

The most significant advantage AUVs have over manned submersibles is operating depth. An unmanned system can more easily be designed to operate at extreme depths because life support subsystems are not required. Additionally, manning a submersible vehicle is less beneficial. For search operations, a submersible is largely reliant on non-visual sensors like sonar. For those reasons, one could argue that it is far less advantageous to use manned submersibles as a sensor platform if unmanned options are available.

References

Artemis Specifications. (2016). Phoenix International Holdings, Inc. Retrieved fromhttp://www.phnx-international.com/phnx/phoenix-equipment/specifications/artemis-specifications/

Bluefin-21 Autonomous Underwater Vehicle (AUV). (2017). General Dynamics Mission Systems. Retrieved from https://gdmissionsystems.com/bluefinrobotics/vehicles-batteries-and-services/bluefin-21

LeHardy, P. K., & Moore, C. (2014). Deep Ocean Search for Malaysia Airlines Flight 370. Paper presented at the 1-4. doi:10.1109/OCEANS.2014.7003292

Pearlman, J. (2014, May 29). SMH370 Search Becomes Most Expensive Aviation Hunt in History, Yet Still No Clues. The Telegraph. Retrieved from http://www.telegraph.co.uk/news/worldnews/asia/malaysia/10863605/MH370-search-becomes-most-expensive-aviation-hunt-in-history-yet-still-no-clues.html