Simulator Data from Computer of MH370 Captain: Part 1

Simulator path (red) and recent MH150 flights (colored circles). (Click on image to enlarge.)

Introduction

Within weeks after MH370’s disappearance on March 8, 2014, news stories revealed that Captain Zaharie Shah deleted data from his home flight simulator in the weeks prior to the disappearance, and FBI investigators at Quantico, Virginia, were assisting in recovering the data. Months later, new reports surfaced stating that the captain had used his home simulator to practice flights to the Southern Indian Ocean, and then deleted those flights from his home computer. Despite these reports, there was no official confirmation from Malaysia that suspicious data was found on the captain’s home computer.

We now know that the recovered data sets from the captain’s computer were included in a report compiled by the Royal Malaysian Police (RMP). The report was eventually obtained by several French media organizations, and large portions of the report were later made public.

On August 14, 2016, the MH370 Independent Group (IG) released a preliminary assessment of the simulator data contained in the RMP report. The data sets were created by Microsoft Flight Simulator (MSFS) software, and are in the form of fragments of “flight files”, which a user may create during a simulation session to record the state of the session for future reference or to resume the session at a future time. The particular flight files of interest were among hundreds of others found on the computer on several drives; however, the files of interest were deleted and recovered by investigators from a “shadow volume” on a single drive that was found disconnected from the computer. The grouping of the files in the shadow volume makes the set unique among the all flight files that were found.

The recovered flight files include flight and navigation parameters that are “snapshots in time”, and are associated with six unique coordinates. If these coordinates were all from a single simulation, it suggests that a user simulated a flight of a B777-200LR aircraft with a departure from Kuala Lumpur International Airport (KLIA), a climb and cruise over the Malacca Strait and then the Andaman Sea, followed by a turn to the south, and a termination from fuel exhaustion in the Southern Indian Ocean (SIO) near 45S 104E. The IG found  that if a great circle path that connects the final points is extended past the final point, the great circle would cross McMurdo Station, Antarctica. (McMurdo is the largest and most populated research station in Antarctica.) This raises the possibility that McMurdo was used as a final waypoint for navigation with the expectation that fuel would be exhausted in the SIO, well before reaching Antarctica.

The simulator data was found on what the Malaysian investigators refer to as drive MK25, where Microsoft Flight Simulator (MSFS) 2004, also known as FS9, was installed. (The main drive of the computer is referred to as MK26, where Microsoft Flight Simulator X, also known as FSX, was installed.)

The fragments of the flight files were found in a shadow volume dated February 3, 2014. A shadow volume is periodically created by the Windows operating system so that files can be restored to a particular date. This means that the file fragments found in the shadow volume were created on or before February 3, and then over-written on or after February 3.

Of the eight total flight file fragments that were recovered, three were for an aircraft on the ground at Kuala Lumpur International Airport (KLIA), and five were for an aircraft flying. Based on fuel levels and other indicators, the data sets in which the aircraft is flying can be related to one of the data sets for the aircraft at KLIA, i.e., six data sets appeared to be related to a single flight. The remaining two data sets at KLIA show fuel levels that are not consistent with the other data sets. These fuel levels may reflect intermediate values before the final takeoff fuel levels were selected.

There has been much discussion as to whether the six data sets are from a single simulation session, and whether the simulator was functioning normally when the data sets were saved. On November 29, 2016, I co-authored a paper with MSFS expert Yves Guillaume that investigated these and other aspects. To replicate the software used by the captain, Yves and I independently installed FS9 with the B777-LR model upgrade from Phoenix Simulation Software (PSS). After substantial testing, we discovered that:

  • The data points in the Andaman Sea share some of the same unique values as the data points in the SIO, suggesting the flight files came from the same simulated flight.
  • The parameters related to fuel and flight dynamics show that the position of the aircraft was manually changed along the flight path.
  • The data files were manually created and saved after certain parameters were manually changed.
  • The simulator appears to have been fully functional, and the rates of climb and other flight parameters after fuel exhaustion can be explained and repeated.

After this paper was published, I created a simulation that was initialized using the recovered values from the data set just after fuel exhaustion. I was able to show that it was possible to manually fly the plane for about 27 seconds and achieve the position, altitude, heading, pitch, and bank that were close to the values contained in the subsequent, final data set. This was further confirmation that the captain’s simulator was properly functioning when the data sets were created. Here’s a video of this short flight.

With the recent release of the ATSB’s report on the operational search, we have learned more about the simulator data found on the captain’s computer. Now three years and seven months after the disappearance, for the first time, the existence of the simulator data has been officially acknowledged in a public document. Although the ATSB does not speculate about whether the captain was responsible for the diversion, the report does reveal that in April 2014, the ATSB considered the simulator data as relevant evidence in defining the search area.

Date and Duration of the Simulator Session

From the ATSB’s report, we learned that on April 19, 2014, the Australian Federal Police provided the ATSB with the recovered simulator data. The report states that The simulator data was a partial reconstruction of a flight simulator session from 2 February 2014. Based on the February 3 date of the shadow volume, we already knew that the simulation was created on or before February 3. However, I was curious to know how the ATSB determined that the exact date of the simulation session was February 2 since the information about date and time was not included in the file fragments that were provided in the RMP report.

After some email exchanges with the ATSB, I was surprised to learn that the ATSB has additional data values from the recovered flight files that were omitted from the data sets that were provided in the RMP report. In particular, there is a section of the flight files in which the date and time of the simulation session are stored. These data values tie the date of the simulation to February 2, 2014. Also, the time values show that the chronological order of the data sets matches a flight departing KLIA, flying over the Malacca Strait, continuing past the Andaman Islands, turning to the south, and exhausting fuel in the SIO, in the same order that the progressively depleting fuel levels suggest. The time values also indicate that the flight session lasted for about one hour. This confirms that the position and fuel levels were modified during the simulation, just as Yves Guillaume and I had concluded in our paper.

The newly released information regarding the date and duration of the simulator session means that it is almost certain that the recovered data sets were from a single flight session.

However, as the signed date of this part of the RMP report is May 15, 2014, it remains a mystery as to why the Malaysians omitted important data values that were already available to the ATSB on April 19, 2014.

Simulated Flight Path

Using our previous notation, we refer to the identification of each data set by its latitude, i.e., as 2N, 3N, 5N, 10N, 45S1, and 45S2. The position of the first four coordinates are shown above in the figure, where the position for data set 2N is Runway 32R at KLIA.

After takeoff, the next coordinate is 3N, which is in the Malacca Strait on airway R467 between waypoints AGOSA and GUNIP. The altitude for 3N is 23,247 ft.

The next is coordinate 5N, which is between GUNIP and TASEK near airway B466. The exact position suggests the aircraft has already left airway B466; the track, which can be calculated from the components of the velocity presented in the 5N data set, is 317 deg, which is exactly towards waypoint VAMPI on N571. (The value for the heading is 315 deg, which differs slightly from the track due to wind.) The altitude at coordinate 5N is 32,246 ft.

The final point for the northwest portion of the path is coordinate 10N, at an altitude of 40,003 ft, and to the west of the Andaman and Nicobar Islands. The plane is at a heading of 256 deg, and is banked at 20 deg and turning left towards the south. The coordinates for 10N place it near airway N877 between waypoints LAGOG and DOTEN. The position suggests that the aircraft left the airway about 30 NM before DOTEN.

The final two coordinates, 45S1 and 45S2, are in the SIO near 45S, 104E, and are separated by a distance of about 2.5 NM. Despite the short distance, the altitudes at 45S1 and 45S2 are 37,561 ft and 4,000 ft, respectively. The data set for 45S2 shows unmistakable evidence that the altitude was manually changed from 37,654 ft to 4,000 ft just before the data set was saved, which is consistent with the large change in altitude over a short distance.

The track of 5N towards VAMPI on N571, and the proximity of 10N to airway N877, together suggest that in the simulation session, after taking off and flying to GUNIP, the aircraft joined N571 and followed the waypoints VAMPI, MEKAR, NILAM, IGOGU, LAGOG, and DOTEN. The great circle alignment of 10N, 45S1, and Pegasus Field (NZPG) at McMurdo Station, Antarctica, means the session might have simulated a great circle path towards McMurdo Station until fuel exhaustion was reached in the SIO. (Aircraft that are flying in LNAV mode follow great circle paths between waypoints.)

Similarities to Flight MH150

We know that the recovered simulator coordinates describe a flight departing KLIA that is not consistent with a flight to Beijing: the initial path of the simulation is to the northwest, flying over the Malacca Strait, and the initial path to Beijing is to the northeast, and flies above the South China Sea. I searched for whether there might be a scheduled flight that better matched the simulation coordinates 2N, 3N, 5N, and 10N. In particular, I searched for scheduled flights that had a departure that followed a route from KLIA to GUNIP, and then to either TASEK or VAMPI, and would require a fuel loading similar to the 68,424 kg that is inferred from data set 2N.

After considering the list of Malaysia Air’s departing flights from Kuala Lumpur, I discovered that MH150, from Kuala Lumpur to Jeddah, Saudi Arabia, met the fuel and path criteria. Next, I checked whether the captain had flown any MH150 flights in that time period. I was surprised to learn that he commanded MH150 on February 4, 2014, which appeared to be very close to the date that the simulation session was created. In November 2016, I privately communicated my findings to other independent investigators, although I thought it was still too speculative and controversial to present in a public forum. Months later, on April 30, 2017, I noted in a blog comment:

The flight might have been a simulation of a flight from KLIA to Jeddah with a diversion, as the fuel loading and SID are consistent with that. Also, Zaharie Shah was scheduled to captain MH150 to Jeddah on Feb 4, 2014. The Shadow Copy Set containing the deleted flight file fragments was dated Feb 3, 2014.

Now that we know that the exact date of the simulation session was February 2, 2014, the link between the simulation session and MH150 is less speculative. The authors of the recent ATSB report had similar thoughts:

On the day the simulation was conducted the PIC was on a rostered day of leave. The following day the PIC was rostered to fly from Kuala Lumpur to Denpasar, Bali and return the same day. On 4 February 2014 the PIC was rostered to fly from Kuala Lumpur to Jeddah, Saudi Arabia. The first three data points recovered from the simulator were consistent with the route from Kuala Lumpur to Jeddah. In the weeks between the Jeddah flight and the accident flight the PIC was rostered to fly return flights from Kuala Lumpur to Denpasar, Beijing, Melbourne and then Denpasar again.

I was curious to see just how close the path suggested by the simulator coordinates resembled previous paths taken by MH150. For the comparison, I used the ADS-B data available from FlightRadar24 for eight consecutive flights between Aug 17, 2017 and Sep 21, 2017. (The available data for all the flights end around waypoint LAGOG, probably due to the range limitations of the receivers in the vicinity.)  The MH150 flight paths are plotted above in the figure.

For seven of the eight flights, the aircraft departed KLIA and flew over waypoint GUNIP. For the seven flights that flew over GUNIP, six followed airway N571 towards VAMPI and continued to follow N571 towards LAGOG. One of the six that reached GUNIP, one flew towards TASEK on airway B466, but rejoined N571 near IGOGU. (Some of the flights show deviations from airways, which are probably weather related.). The similarity between typical routes taken by MH150 and the simulator data is evident.

We can only speculate as to why, just two days before he commanded MH150 from Kuala Lumpur to Jeddah, and five weeks before the disappearance of MH370, the captain used his home computer to simulate a flight of MH150 that was diverted to the SIO.

In Part 2, we further investigate the simulator data and how it may give us clues about MH370.

Updates on October 13 and 15, 2017. In the figure, the dates in the legend were corrected so that all refer to year 2017. Also, the label on the airway between LAGOG and DOTEN was corrected to be N877, and the label of the airway between GUNIP and TASEK was corrected to be B466. Thank you to Twitter handle @BKKDiet and blog contributors @Mick Gilbert  and @TBill for finding these errors.

Posted in Aviation | 554 Comments »

ATSB Releases Final Report on MH370

The Australian Transport Safety Bureau (ATSB) has released a report entitled “The Operational Search for MH370”. It is a long document (440 pages) that is meant to provide final documentation of all of the ATSB’s activities related to this incident. There are no new conclusions, although we can gain some new insights:

  • MH370 flew over or near IFR waypoints a cluster of waypoints near Kota Bharu called ABTOK, KADAX, and GOLUD and later PUKAR as it flew towards Penang. This implies that MH370 was following waypoints after the transponder stopped operating after the turn back.
  • The registration of the first officer’s cell phone on a tower on Penang Island is officially acknowledged for the first time. A footnote citation says, “This information was obtained by the Royal Malaysian Police and reported to the Ministry of Transport Malaysia. Though a formal report was not available to the ATSB, information relevant to the search was shared.” Of course, this begs the question as to why the ATSB only learned of this information after the RMP report was leaked.
  • The two sources of the primary surveillance radar (PSR) data revealed to be the civilian radar at Kota Bharu and the military radar on Penang Island on Western Hill. The military radar captures are described as “not continuous” with no further explanation.
  • After passing Penang Island, the report says the “Radar data shows the aircraft then headed to the northwest, eventually aligning with published air route N571 from IFR waypoint VAMPI. The validity of this section of the radar data was verified using the track of a commercial flight that followed N571 about 33 NM behind MH370.” This implies the radar captures shown to the NOK in Beijing on March 21, 2014, at the Lido Hotel, are valid. The performance of the military radar was verified by comparing the civil radar data to the military data as another commercial aircraft, likely to be EK343, trailed 33 NM behind MH370.
  • The data recovered from the captain’s home flight simulator is discussed for the first time in an official report. An overview of the data is presented, suggesting a flight from Kuala Lumpur up the Strait of Malacca, and then towards the Southern Indian Ocean (SIO), ending in fuel exhaustion. The flight path recovered from the simulator did not match the MH370 flight paths that were reconstructed from the Inmarsat satellite data.
  • The ATSB pegs the date of the simulator session as February 2, 2014. We know that the deleted file fragments were found in a Shadow Volume with the date February 3, 2014, so likely the session was created on or shortly before that date. It is not explained how the ATSB can be sure the session was created on exactly February 2, 2014, but this would be significant.
  • There is mention that the last data point in the SIO suggested there was a user input of an altitude of 4,000 ft. (The evidence that the simulator’s user manually changed the altitude and other parameters during the flight was first presented in a paper by me and Yves Guillaume.)
  • There is acknowledgement that the simulator data shows a beginning sequence that is similar to the flight the captain flew from Kuala Lumpur to Jeddah, Saudi Arabia, on February 4, 2014. (The significance of the similarities in path and timing between the simulator data and the captain’s flight MH150 to Jeddah was first discussed on this blog.)
  • Although the ATSB does not speculate that the captain was responsible for the diversion, and although the simulator data was not deemed useful for reconstructing possible flight paths of MH370, based on the presentation of this data in the report, it is clear that the ATSB considers the simulator data to be significant evidence.
  • Based on examination of the debris and a detailed study of the final BFO data, the ATSB believes that MH370’s flight ended in a steep, uncontrolled descent. This will serve to limit the distance from the 7th arc for future searches.
  • Although there was an attempt by the official investigators to discern information about the crash site from an investigation of the marine ecology attached to the recovered debris, all results were inconclusive.
  • No new drift analyses are presented. The ATSB reaffirms its belief that the most likely crash site is 35.6S, 92.8E, based on the drift analyses by CSIRO.

So, although there are no new conclusions in this report, there are some interesting new pieces of information. It is also important to note that Malaysia chose to omit key pieces of evidence from the Factual Information (FI) released in March 2015 that are presented in the new ATSB report. These pieces of evidence include details about the radar data, information regarding the simulator data found on the captain’s home computer, and the data related to the registration of the first officer’s cell phone as the aircraft flew near Penang. Although these omissions have been discussed in detail on this blog, perhaps with the release of the ATSB report, more will question why Malaysia chose to not disclose, and even deny the existence of, important evidence.

On a final note, the ATSB chose to acknowledge the contributions of some of the independent investigators, including many that comment here. The ATSB was kind enough to give a special recognition to Blaine Gibson:

The ATSB acknowledges the extensive contributions that many individuals and groups have made during the underwater search for MH370. Many contributors have provided credible, alternate and independent approaches and analysis of the limited data available. In particular, the ‘MH370 Independent Group’ comprised of scientists, researchers and individuals who have cooperated across continents to advance the search for MH370. The ATSB is grateful for their work collectively and individually including Duncan Steel, Mike Exner, Victor Iannello, Don Thompson, and Richard Godfrey. The ATSB also acknowledges the extensive and detailed contributions provided by Simon Hardy, Bobby Ulich and Robin Stevens.

The search for MH370 was significantly advanced after the first debris from the aircraft was found on La Reunion Island in July 2015. The subsequent efforts of Blaine Gibson in searching for and locating MH370 debris on east African coastlines did much to raise public awareness of the importance of the MH370 debris which led to many more items of debris being handed in. Mr Gibson met and communicated with ATSB during his 2015-2016 search expeditions and he is acknowledged for his outstanding efforts in communicating his debris finds to Malaysia, ATSB, the next of kin and the wider world.

Posted in Aviation | 462 Comments »

New Pieces Possibly from MH370; Blaine Gibson Threatened in Madagascar

Blaine Gibson (right) and Nick Connite (left) in Madagascar with two new pieces possibly from MH370.

In a newly released report, private investigator Blaine Gibson reveals details surrounding two new pieces that could be from MH370. The pieces were discovered by residents of Madagascar in September 2016, and delivered to Malagasy authorities on August 16, 2017.

Blaine writes that “for the protection of those involved, we decided not to make this report public until the debris was safely delivered to Malaysia.” That transfer was supposed to occur imminently. However, with the assassination of Hon Consul Zahid Raza, who served as a diplomat for Malaysia in Madagascar, the transfer has been delayed, and Blaine has decided to now release his report.

In the report, Blaine explains that “under the agreement between the two countries, debris is supposed to be collected by Hon. Zahid Raza, the Honorary Malaysian Consul in Madagascar, and delivered by private courier to Malaysia. On August 24 the Hon. Zahid Raza was assassinated in Antananarivo. The debris is still safely in the hands of the Madagascar Authorities. However new arrangements must be made for the collection and delivery of debris.”

Although not mentioned in the report, Blaine told me that during a trip to Madagascar, death threats were made to him and others for continuing to collect debris related to MH370. Blaine told me about these threats when I met with him on August 3, which was three weeks before Mr Raza was assassinated. The link between custody of the debris and the slain diplomat was first discussed in a previous post.

Blaine attributes the new discoveries to be the “result of the 370 families’ debris search and awareness efforts and travel to Madagascar.”

Twenty-seven photographs of the two pieces are available for download.

Of the two parts, the larger one was found on Maroantsetra Beach on Antongil Bay in September 2016. Blaine estimates the dimensions to be about 27 inches long, 12 inches wide, and 2 3/4 inches thick, and composed of a composite honeycomb structure. However, there is a 3 1/2-inch strip attached with fasteners that have not yet been identified as aviation related.

The two new pieces. The smaller piece (left) is more likely from an aircraft than the larger piece (right).

The smaller part was found on Antsiraka Beach around September 2016. Blaine estimates the dimensions to be about 12 inches long, 12 inches wide, and 3/8 inches thick, and composed of a composite honeycomb structure. This piece appears to have a higher possibility of being aviation related.

The pieces remain in the custody of Malagasy officials until new arrangements are made to transfer the pieces to Malaysia.

Blaine also has released new maps that show where it is in Madagascar that MH370 debris is predicted to wash ashore. The maps were created using computer models developed by Dr Charitha Pattiaratchi of the University of Western Australia. Blaine acknowledges that Dr Pattiaratchi and CSIRO’s Dr David Griffin have helped guide search efforts.

Location of MH370 debris as predicted by computer models (white) and where two new pieces were found (red).

The new report, debris photographs, and maps are available for download as a collection of files.

Update on Aug 29, 2017. The fasteners on the larger of the two pieces have been identified to be aviation related. Thank you to Annette Mansfield and Mike Exner for that information.

Posted in Aviation | 1,065 Comments »

Slain Diplomat Was Helping Get MH370 Debris to Malaysia

Malaysian investigator Aslam Khan (left), Blaine Gibson (center), and Consul Zahid Raza (right) at the Ministry of Transport in Antananarivo, Madagascar, in December 2016

On August 24, Zahid Raza, serving as the Malaysian consul to Madagascar, was killed in the Malagasy capital of Antananarivo. According to reports, he was shot multiple times while seated in the driver’s seat of his car. Mr Raza is reported to be of French-Malagasy nationality.

Last December, Reuters reported that Mr Raza assisted Blaine Gibson in transferring the custody of pieces believed to be from MH370 from Madagascar to Malaysia. At that time, six pieces were transferred. This has raised questions as to whether there was a link between those MH370 parts and Mr Raza’s death.

What makes a possible link to MH370 even more suspicious is that in the time period surrounding his death, Mr Raza was expected to visit the Malagasy Ministry of Transport, retrieve additional recovered pieces, and deliver those pieces to Malaysia. In a private communication from Blaine to me, he writes (repeated here with his permission):

On August 16 possible MH 370 debris was handed over to Madagascar authorities, and authorities in Malaysia were notified. Under the agreement between the two countries, debris is supposed to be collected by Hon. Zahid Raza, the honorary Malaysian Consul in Madagascar, and delivered by private courier to Malaysia.

On August 24 the Hon. Zahid Raza was assassinated in Antananarivo. At first we did not know if he had picked the debris up before this tragedy. We just learned that the debris is still safely in the hands of Madagascar authorities. However new arrangements must be made for the collection and delivery of debris.

Our thoughts and prayers are with the family of the Hon. Zahid Raza.

In the aftermath of Mr Raza’s death, there seems to be conflicting stories about his background. He appears to be of French-Malagasy nationality, with family living in France and in the French Reunion Island. In one report, he is referred to as the “former” consul, but other reports imply he held the title of Honorary Consul at the time of his death. There is a report linking Mr Raza to a group associated with the kidnapping of residents of Indo-Pakistani descent that are living in Madagascar. (Madagascar does not grant automatic citizenship to  those born on Malagasy soil. As a result, some Indo-Pakistani residents are from families that have lived in Madagascar for over a century.) The association of Mr Raza with the kidnappers has not been confirmed, and could be disinformation. Hopefully, the facts surrounding this will surface.

Surprisingly, the assassination of Mr Raza has been met with stony silence from both Malaysia and France, despite his ties to both countries.

I join Blaine in expressing my sincere sympathy to Mr Raza’s family.

Posted in Aviation | 58 Comments »

Ocean Infinity CEO Discusses MH370 Search Offer

Oliver Plunkett, CEO of Ocean Infinity

I had the opportunity to converse with Oliver Plunkett, who is the CEO of Ocean Infinity (OI). My goal was to learn more about OI’s offer to search for MH370 in the Southern Indian Ocean (SIO). Although Mr Plunkett would not disclose the details of the confidential negotiations with Malaysia, he did provide information that is helpful to understanding the general terms of OI’s proposal.

First, OI’s offer is structured such that OI assumes 100% of the economic risk for the search. OI will NOT receive any payment if the wreckage is not found. So it would appear that if the success fee that OI is proposing is less than what Malaysia would have spent in conducting the search using conventional techniques, this is an extremely attractive offer.

I learned a bit more about the recent sea trials that Ocean Infinity recently conducted in the North Atlantic. The tests demonstrated that the underwater autonomous vehicles (AUVs) could be successfully launched and recovered. Each AUV also demonstrated that it could independently scan the seabed. Mr Plunkett said he was pleased with the results so far. Further work is planned at deeper depths and over a wider range of conditions. Mr Plunkett also explained that although the unmanned surface vehicles (USVs) could not be used in the roughest of sea states, the search for MH370 could nonetheless occur over a wide range of conditions. This is because the mission is to scan the seabed and identify the wreckage rather than to generate precise maps.

I inquired about the window of opportunity for completing the negotiations with Malaysia and starting the search. (We know from previous underwater search efforts that the search season in the SIO runs approximately from December to March.) Mr Plunkett is optimistic that Malaysia and OI will reach an agreement in a time frame that allows for adequate time to prepare for a search that begins this season.

Finally, I asked whether OI had already determined the specific area to search. Mr Plunkett explained that OI intends to complement its internal resources with input from other organizations and other outside experts to help define the search area. OI has already had some interaction with the ATSB, which he believes is completely committed to finding the wreckage. I don’t expect that OI’s search area will be very different than what we have been discussing here.

Over the course of our discussion, it became apparent that Mr Plunkett was aware of the many posts and discussions that appear on this blog.

With such a favorable offer on the table from an innovative and qualified firm, I remain optimistic that the seabed search will re-start. However, for the search to begin this season, the window of opportunity to complete the negotiations is narrowing. It is imperative that Malaysia not miss this opportunity.

Update on Aug 16, 2017

In a story appearing the New Straits Times, Malaysia’s Department of Civil Aviation (DCA) reveals that the OI proposal to restart the subsea search is one of several proposals that are under review. The proposals will be brought to the attention of Australia and China for their views.

Update on Aug 17, 2017

Voice370, representing the MH370 families, released this statement today which questions the delay in re-starting the search in light of the confidence expressed by CSIRO in identifying a probable impact site.

Posted in Aviation | 260 Comments »

Seabed Explorer Ocean Infinity Offers to Search for MH370

Ocean Infinity’s technology uses multiple underwater drones and surface vessels with a single host vessel

Yesterday, a support group for MH370 families released a statement claiming that a private entity has offered to resume the seabed search for the aircraft with the understanding that it would collect a fee only if the aircraft wreckage was found. Today, through Grace Nathan, a Malaysian lawyer whose mother was a passenger on MH370, we learn that the private entity is a US-based firm called Ocean Infinity.

Readers here are already familiar with Ocean Infinity. In a recent post entitled Advanced Underwater Drones May Help Find MH370, I highlighted the innovative research at Virginia Tech in developing underwater autonomous vehicles (AUVs) that could collaboratively scan the ocean floor. In an update to the article, I stated:

I was recently in a discussion that included a well-known ocean explorer who happens to be a judge in the Ocean Discovery XPrize competition.  We were having a general discussion about searching for MH370 and ways to scan the ocean floor at high resolution, and he told us about the capabilities of Ocean Infinity. Like the team at Virginia Tech, their approach is to employ a team of AUVs. From their website:

Six HUGIN autonomous underwater vehicles (AUVs) are capable of operating in 6,000 m water depth collecting high resolution data at record breaking speeds. Our AUV fleet is accompanied by six unmanned surface vehicles (USVs) to ensure precise position and constant communication.

With multiple autonomous vehicles working simultaneously utilizing innovative technology, we are able to survey huge swaths of the seabed, quickly and with outstanding accuracy. We can operate in shallow waters but excel in extreme depths, working in dynamic environments ranging from the tropics to the Arctic ice.

Because of the size and complexity of each AUV/USV pair, the capital cost of the technology from Ocean Infinity would greatly exceed the capital cost of Virginia Tech’s technology, which uses small AUVs with innovative navigation systems. On the other hand, both approaches benefit from having a single host vessel supporting multiple underwater vehicles, which offers significant operating cost and scan rate improvements compared to the conventional towfish technology.

Ocean Infinity’s seabed exploration system is commercially available today, including underwater and surface vehicles, on-board support equipment, and the host vessel. This is an exciting possibility for conducting the search for MH370 in the near future.

I can now say that the “well-known ocean explorer” was David Mearns. At the time that I posted the article, I was not aware that Ocean Infinity had any interest in searching for MH370, although I was hoping they did. The prospect of exploiting Ocean Infinity’s technology in the near future is great news.

That means that Malaysia, Australia, and China need to make a decision: Either the tri-partite countries should provide funds to re-start the search; or, the countries should fully cooperate with Ocean Infinity and other qualified entities that are interested in re-starting the search. Any other action is unacceptable.

Posted in Aviation | 274 Comments »

Sea Explorer David Mearns Wants to Search for MH370

In a TV interview with Australia’s Studio 10,  shipwreck hunter David Mearns reveals that he would like to mount a privately-funded search for MH370.

From the interview:

“But since the search has been suspended, which I think is basically an unacceptable thing to have happened, I’ve been working with some families and some experts to see if we could actually mount a privately-funded search for the plane, because it’s inexcusable that that wreckage isn’t located, because it can be found. They just have to look in the right place.”

“It can be found. The technology is there to find it. They just need to be able to look in the right place.”

“And they’re narrowing the areas. The next search will be smaller than what’s been already done.”

“And everybody should be concerned about this, because until that black box is found, and we recover the black boxes, we don’t know what happened.”

When asked if they are looking the right place, he responded, “No, because they have  not found it. When they look in the right place, they will find it. And it can be done. I’m here to tell people that it can be done.”

“And that’s the other key thing. Technology has moved on, so now that we can search much faster than before.”

When asked if he thinks he can find MH370, he responded, “I never guarantee these things, but I believe it is definitely worth doing. There’s an area that can be searched in an efficient way, and I believe we don’t just owe it to the families. But I think, internationally, it’s an important thing to do.”

“This will be the first time a major aircraft like this has been lost without any resolution or any lessons learned about why it crashed. And that is not only unacceptable, it’s inexcusable for the authorities not to be able to continue to do something.”

I should add that David Mearns has had extensive discussions and meetings with some members of the MH370 Independent Group (IG), in which many of our analyses and findings have been shared. I hope that collaboration continues.

Posted in Aviation | 138 Comments »

Some Insights from the Unredacted Satellite Logs

Global coverage of Inmarsat’s I3 network, showing the overlap region of the IOR and POR satellites

Last month, we published the complete logs for all communications that occurred on March 7 and 8, 2014, between the SATCOM unit aboard airframe 9M-MRO and the Inmarsat satellite network. (All times and days refer to UTC.) This includes communications before and during MH370 as well as the previous flight, MH371, between Beijing and Kuala Lumpur. Now that we’ve had a chance to investigate the logs for several weeks, I’ve summarized some of the findings. I’ve attempted to give proper credit to the individuals that worked on various aspects. If I have inadvertently omitted an individual, just let me know.

Observation: The log-on requests at 18:25:27 and 00:19:29 both had low carrier-to-noise-density (C/No) ratios, but normal receive power levels, indicating high noise levels. Similarly low (C/No) ratios were observed several times during MH371 under normal conditions. (Mike Exner)

Inference: The low (C/No) ratios at 18:25:27 and 00:19:29 were not likely due to abnormal aircraft maneuvers or attitudes.

Observation: When MH371 was traveling in a region of overlapping satellite coverage of the IOR and POR satellites, there were multiple automatic log-offs and log-ons with no indication of problems. (Many)

Inference: The multiple log-off and log-ons seen during MH371 are not indicative of a problem with the SATCOM.

Observation: An in-flight log-on does not produce abnormal values of BFO unless the log-on was part of power up sequence following an extended period during which the SATCOM was powered down. (Many)

Inference: This increases the likelihood that the SATCOM was unpowered for an extended period of time prior to the log-on at 18:25, and increases the likelihood that the abnormal BFOs during the log-on at 00:19 were due to an increasingly high rate of descent.

Observation: Abnormally high BTO values for a log-on request burst can be corrected with an offset of 4600 μs. (Many)

Inference: The corrected value of the BTO at 00:19:29 is 23000 – 4600 = 18400 μs, as previously suggested by Inmarsat. An adjustment to the position of the 7th arc does not seem to be warranted.

Observation: Abnormally high BTO values for a log-on acknowledge burst can be corrected with an offset of N*S, where N is an integer between 1 and 5, inclusive, and S=7812.5 μs. The value of S=7812.5 μs corresponds to the width of a slot, where a frame of 500 ms is comprised of 64 slots. (Don Thompson)

Inference: The corrected value of the BTO at 00:19:37 is 49660 – 4*7812.5 = 18410 μs, which statistically agrees with the corrected value of 18400 μs at 00:19:29. Again, an adjustment to the position of the 7th arc does not seem to be warranted.

Observation:  Maintenance messages were generated after MH371 landed in Kuala Lumpur. However, no ACARS maintenance messages were generated during the flight. (@Andrew)

Inference: If a serious condition had arisen during MH371, it would have generated an ACARS message. Therefore, no serious condition arose during MH371.

Observation: When a 2nd log-on request message occurs one second after the first, it is related to initialization of the In-flight Entertainment System (IFE), and the message does not contain information about the Flight ID. If a 2nd log-on request does not occur, it suggests the IFE was not available at that time, possibly because the IFE has not yet completed its power up sequence. (Don Thompson)

Inference: This increases the likelihood that the IFE was unpowered prior to the log-on at 18:25 and unpowered prior to the log-on at 00:19.

Observation: During a log-on sequence, the SATCOM transmits a value for the “Prev Sat ID”. If the log-on occurs after a log-off request, or after a power interruption, the previous satellite value is cleared and a value of 63 (077) is transmitted. This value was transmitted for the log-on at 18:25 and the log-on at 00:19. There may be other causes for 63 to be transmitted that did not occur during MH371. (@el-gato, Don Thompson, and Richard Godfrey)

Inference: Since no log-off request was recorded prior to the log-ons at 18:25 and 00:19, it is likely that a power interruption preceded each of these log-ons.

Observation: Fuel flow data extracted from the ACARS reports for MH371 showed that the right engine burned fuel about 3.3% faster than the left during cruise. (Mike Exner, Don Thompson, Richard Godfrey)

Inference: If there was no fuel rebalancing by a pilot, the right tank for MH370 would have run dry about 15 minutes before the left tank.

Observation (preliminary): The measured values of BTO and BFO for MH371 agree with the BTO and BFO models that were used to reconstruct the flight path for MH370. (@sk999, Richard Godfrey)

Inference: The measured values of BTO and BFO for MH370 can be used to disqualify hypothetical paths with predicted values of BTO and BFO that do not match the measured values, as the ATSB and independent investigators have assumed.

In summary, the previous flight MH371 seems to have been normal in all respects. Using the satellite data from MH371, we have a higher level of confidence that for MH370, power was interrupted to the SATCOM prior to the log-ons at 18:25 and 00:19, and also higher level of confidence that the aircraft was in an increasingly steep descent at 00:19.

Considering that the newly available data generally supports the conclusions of the official investigators, it remains a mystery as to why Malaysia withheld the data for so long, and why it chose to release the data at this time.

I hope everybody is enjoying today, the Fourth of July, including Americans celebrating Independence Day.

Posted in Aviation | 688 Comments »

The Unredacted Inmarsat Satellite Data for MH370

Inmarsat’s Mark Dickinson holding the satellite data in an interview with CNN

Since we first learned of its existence, we’ve been asking for the complete record of the communications data between MH370 and Inmarsat’s satellite network. In May 2014, Malaysia released satellite data logs, but they were incomplete: fields of data were missing, and only a small number of data records from before the flight was made available. When pressed for the complete logs, Inmarsat and Malaysia both claimed the data had to be released by the other.

We now have what we believe is the complete record of communications between airframe 9M-MRO and the Inmarsat satellite network, from March 7, 2014, at 00:51 UTC, until March 8, 2014, at 01:16 UTC. This time period includes the previous flight from Beijing to Kuala Lumpur.

The satellite data was shared with me by a relative of a Chinese passenger on MH370. The data was given to him by Malaysia Airlines with the following email text:

Please find attached the Inmarsat data, for your info. Please note that these are raw data as you have requested. The authorities agree to release the data, on condition that:

  1. We will not translate the data into any meaningful information as the data is proprietary to Inmarsat. The Malaysian Investigation team does not have any experts to translate these data into any meaningful information.
  2. We will not translate the data into any other language, including Mandarin.
  3. These data are complete and obtained from Inmarsat. Please do not manipulate the data.

I know, by having these data, you will have more questions, but I have to say that we are providing these data to satisfy your request, but we cannot answer any questions on the data because we too, cannot understand it. Only the experts from Inmarsat can.

 Hope you understand.

 Thank you

I suspect the data will confirm some assumptions, and will raise even more questions. I hope the data can help us learn more about the disappearance.

Posted in Aviation | 523 Comments »

MH370 End-of-Flight with Banked Descent and No Pilot

Introduction

Boeing recently conducted end-of-flight simulations for MH370 with the assumption that there was no pilot input. The results were released in November 2016 by the ATSB as part of a report entitled MH370 – Search and Debris Examination Update. Boeing observed that in simulations where the aircraft experienced a descent rate consistent with the values and timing of the last two BFO data points, the aircraft impacted the water within 15 NM of the 7th arc. However, the details and the likelihood of the configuration that caused the high rates of descent were not discussed.

In order to better understand the conditions leading to the descent rates suggested by the final BFO values, and to estimate the distance MH370 might have traveled after crossing the 7th arc,  simulations were conducted using the PMDG 777-200LR model add-on to Microsoft Flight Simulator X (FSX). After making adjustments for differences between the PMDG 777 model and MH370, the flight characteristics were recorded under various conditions.

Modeling the End-of-Flight Using FSX

9M-MRO was a B777-200ER and the PMDG 777 model is a B777-200LR. The main differences are:

  • Weight: The 777-200ER has a maximum take-off weight (MTOW) of 297.6 MT, while the 777-200LR has a MTOW of 347.5 MT, so the 777-200LR is in general a heavier aircraft. In the simulations, the zero-fuel weight (ZFW) was set to 174.4 MT to be consistent with MH370.
  • Engines: 9M-MRO’s version of the 777-200ER has Trent 892-17s with 41,768 kgf (90,000 lbf) of thrust, while the PMDG 777-200LR has GE90-110B1s with 50,285 kgf (110,760 lbf) of thrust. Since only the results from the simulation after fuel exhaustion are used, the difference in engine thrust is not important.
  • Wings: The 777-200LR version has a wing area about 2% greater area than the 777-200ER due to raked wingtips, which decrease the wing loading and reduce drag in cruise. The small difference in aerodynamic performance from the raked wingtips would produce little if any difference in the end-of-flight scenarios considered here, and are ignored.

In order to get realistic results from the FSX simulation, it is also important to recognize and compensate for other inaccuracies of the PMDG 777 model. In particular, it was found that the behavior of many systems when components have failed is not correct. Nonetheless, the basic aerodynamic model of the PMDG 777, when not at envelope limits such as stall conditions and transonic speeds, should be sufficiently accurate to model the flight characteristics of the B777. (Even a Level D simulator is not guaranteed to be accurate outside of the aircraft’s certified flight envelope.) The details of the flight dynamics model as incorporated into FSX are described by Yves Guillaume.

To model the flight behavior after fuel exhaustion, the simulation was conducted with the following initial conditions and programmed events:

  • Initial conditions are stable flight at 220 KIAS and FL350, which is representative of flying with one engine inoperative and decelerating from the dual engine cruise speed, but still holding altitude.
  • At t = 0, following events occur:
    • The fuel level is set to zero. In addition to shutting down the engines, this prevents the APU from starting.
    • The two fuel cut-off switches are set to OFF. Although it may not seem necessary to set the fuel level to zero AND employ the cut-off switches, in the PMDG model, the windmilling action of the engine shafts continues to supply electrical and hydraulic power if the cut-off switches are not employed.
    • The primary flight computers (PFC) are programmed to degrade to “secondary” control law.  Although the loss of power to the left and right transfer busses removes heat to the pitot sensors, which should automatically degrade the control law from “normal” to “secondary”, in the PMDG 777 model, the control law remains in normal mode without programming this failure. In normal mode, yaw compensation and envelope protection would be available, while they are not available in secondary law.

Implications of the BFO Values on Flight Dynamics

The last two values of BFO were 182 Hz at 00:19:29 and -2 Hz at 00:19:37. Assuming a BFO bias of 150 Hz and a nominal position at (30S, 98E), a groundspeed of 385 kn, and a track of 172°T, the corresponding descent rates are 4,000 fpm and 14,400 fpm. This represents an increase of 10,400 fpm over 8 seconds. After conducting studies of the various flight conditions that might cause these descent rates, the following observations are offered:

  1. If the aircraft has perfect lateral trim, i.e., the ailerons and rudder are positioned to perfectly remove any lateral (side-to-side) asymmetry of the aircraft about its longitudinal axis, the aircraft will fly relatively straight with no pilot input. The aircraft will also develop a phugoid flight pattern consisting of a damped-sinusoid vertical speed component superimposed on the quasi-steady vertical speed component. The quasi-steady vertical speed would correspond to a descent angle of about 3°, and a glide distance of greater than 110 NM is possible. However, the amplitude of the phugoid would be smaller and the period of the phugoid would be longer than the descent rates suggested by the BFO values. The case of a straight flight with a phugoid descent is therefore not studied here as it does not match the BFO values.
  2. If the aircraft is flying straight with little or no bank, the descent rates can match or exceed the descent rates suggested by the BFO values if the pilot commands a single nose-down input. The aircraft would correspondingly impact the ocean close to the 7th arc.  It is also possible that the steep descent could be arrested with a subsequent nose-up input, and the aircraft could be piloted to glide some distance (> 100 NM) from the 7th arc before the aircraft impacts the ocean.  Other than noting that with pilot input, the impact point could vary greatly in distance and direction from the crossing point of the 7th arc and still match the BFO values, this scenario is not considered here.
  3. If the aircraft has lateral (side-to-side) asymmetry about the longitudinal axis that is not removed by the appropriate positioning of the ailerons and/or rudder, the plane will enter a bank with a roll rate determined by the magnitude of the lateral asymmetry. As the bank angle increases, the descent rate also increases. With sufficient lateral asymmetry, the descent rates can match or exceed the descent rates suggested by the BFO values. This case is the case studied here.

Simulation of Banked Descent and No Pilot Input

After fuel exhaustion, the control wheel was turned about 4.5 units to the left in order to match the BFO values by introducing lateral asymmetry. (With the “no-pilot” assumption, the position of the control wheel in MH370 likely stayed in the neutral position. In the simulation, the control wheel was turned to reproduce lateral asymmetry resulting from other sources.) The control wheel input induced a roll rate of about 3.6 deg/s. As the bank angle increased, the descent rate correspondingly increased. In the simulation, the increase of descent rate from 4,000 fpm to 14,400 fpm required about 9 s, while the measured BFO corresponding to these descent rates are spaced at about 8 s. The lateral asymmetry caused by the rotation of the control wheel is therefore judged to be about equal to the lateral asymmetry of MH370 after fuel exhaustion.

A video showing the view from the cockpit during the simulated descent is included below. The aircraft rolls past 180° and impacts the water at a pitch angle that is almost vertical. During the descent, the speed reaches about Mach 1.1, and the descent rate approaches 60,000 fpm (593 kn). Although these speeds are outside of the performance envelopes that can be accurately modeled by the PMDG 777 model, it demonstrates that the BFO measurements are consistent with a very high speed impact.

 

Another video below is an outside view of the aircraft during the descent, showing how the increasing bank leads to increasing pitch down.  At about 14 s, the deployment of the ram air turbine (RAT) can be seen and heard.

 

The figure below shows the trajectory of the aircraft. The position is adjusted so that the path crosses the 7th arc when the descent rate is about 4,000 fpm. There is only about 50 s between the time the descent rate reaches 4,000 fpm and the time of impact, and the impact is about 4.8 NM from the crossing of the 7th arc.

 

No wind is included in the simulation. However, considering that the aircraft impacts the water in about a minute and the winds were to the east, the effect of wind on the distance from the 7th arc should be small.

Possible Causes of the Lateral Asymmetry

The lateral asymmetry that induces the roll and the banked descent can be caused by a number of factors, including:

  1. Geometrical asymmetries (“bend”) that would cause yaw and bank when the control surfaces are in their neutral position. Normally, this would be compensated by a pilot by adjusting rudder and aileron trim. However, the amount of trim might not exactly balance the asymmetry so there would be residual out-of-trim.
  2. Asymmetric position of control surfaces caused by differences in hydraulic pressure that is supplied to the control surfaces on either side of the aircraft after fuel exhaustion.

After fuel exhaustion and without the APU operating, the main source of hydraulic pressure is from the RAT, which supplies pressure to the “center” hydraulic system. As can be seen below in the synoptic displays for the flight control surfaces and the hydraulic system, when the RAT is deployed, only the right flaperon has hydraulic pressure, and the left flaperon is “bypassed”, so that the flaperon moves freely. If the position of the right flaperon is positioned slightly down compared to the left flaperon, the result would be a roll to the left.

 

In fact, we have an indication that this would occur. In the Aircraft Maintenance Manual (AMM) for the B777, in the section on the Ram Air Turbine System, there is this note that was found by Don Thompson:

Training Information Point

When the RAT is extended and hydraulics off, the airplane rolls left. Two to three units of right control wheel rotation are necessary to hold the wings level.

In the simulation, 4.5 units of rotation were added to simulate the banked descent. Based on the note in the AMM, it appears that this level of wheel rotation causes asymmetric flaperon positions that are similar to what would be expected when the hydraulic pressure is supplied by the RAT.

The RAT would be deployed within seconds of the second engine flameout. However, the log-on request at 00:19:29 is believed to occur about two minutes after the second engine flameout. (One minute is required to start the APU and one minute is required for the SATCOM to request a log-on after power-up.) Therefore, there is a two-minute delay between deployment of the RAT and the roll. In fact, the pressure to the left and right hydraulic systems might decay over some period of time, as determined by the consumption of hydraulic fluid by various systems as well as the limited flow that is available as the engines windmill and the engine-driven pumps operate at reduced capacity. These factors might contribute to the two-minute delay before the aircraft entered into the banked descent.

Conclusions

The BFO values at 00:19:29 and 00:19:37 suggest that MH370 was descending at an increasingly high rate. With the assumption that there were no pilot inputs, the descent rates suggest the aircraft was in a roll as it was descending. According to Boeing documentation, when the hydraulic pressure is supplied by the ram air turbine (RAT), the aircraft banks to the left, which may have been the cause of the rolling during the descent. Using the PMDG 777 model add-on to FSX, simulations were performed for a banked descent that matched the descent rates suggested by the BFO values. In the simulation, the aircraft impacts the water at speeds around Mach 1 and with nearly vertical nose-down pitch. The distance of the impact point from the crossing of the 7th arc is less than 5 NM.

Posted in Aviation | 277 Comments »