Hijacking MH370: Difference between revisions

MH370 DECODED
Jump to navigation Jump to search
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 13: Line 13:




<p>Security Weaknesses</p>


<div style="text-align:center">
<div style="text-align:center">
<html>
<html>
<img src="https://cache.mh370wiki.net/image/Visio/Security-Cheese-Diagram-Crop.jpg"
<img src="https://cache.mh370wiki.net/image/Visio/Security-Cheese-Diagram.jpg"
     max-width: 80%; height: auto;
     max-width: 80%; height: auto;
     onContextMenu="return false;"> <!-- no right click -->
     onContextMenu="return false;"> <!-- no right click -->
Line 23: Line 24:




 
{{ShortLine}}
 
<h5>Sub-page List</h5>
 
<p>{{Special:PrefixIndex/{{FULLPAGENAME}}/}}</p>
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
<table class="tbl w75">
<tr style="padding:1.5em;">
    <td style="width:75%; text-align:center;"><b>Development Stage</b></td>
    <td style="width:25%; text-align:center;"><b>Link to each Topic</b></td>
</tr>
<tr>
      <td><p><b>Preamble</b>: A brief history of aircraft hijacking, improvements in aviation security, and a short overview of terrorism. Although 'who' is not known, this preamble suggests the kind of operative(s) involved.</p></td>
    <td><div style="text-align:center; margin-left 2em; margin-right:2em;"><html><a href="/Hijacking MH370/Preamble" class="nav-btn expand">Preamble</a></html></div></td>
</tr>
 
<tr>
      <td><p><b>Purpose</b>: A hijacking must have a purpose. Defining the purpose of the exercise is pre-requisite to targeting a type of aircraft. </p></td>
    <td><div style="text-align:center; margin-left 2em; margin-right:2em;"><html><a href="/Hijacking MH370/Purpose" class="nav-btn expand">Purpose</a></html></div></td>
</tr>
 
<tr>
      <td><p><b>Preparation</b>: Basically an information-gathering stage. Everything that needs to be known about a target aircraft, flight paths, timetables, and security controls.</p></td>
    <td><div style="text-align:center; margin-left 2em; margin-right:2em;"><html><a href="/Hijacking MH370/Preparation" class="nav-btn expand">Preparation</a></html></div></td>
</tr>
 
<tr>
      <td><p><b>Planning</b>: Synthesis of ideas and data to create a plan, identify a target flight, allocate responsibilities and finalise a sequenced action plan. </p></td>
    <td><div style="text-align:center; margin-left 2em; margin-right:2em;"><html><a href="/Hijacking MH370/Planning" class="nav-btn expand">Planning</a></html></div></td>
</tr>
 
<tr>
      <td><p><b>Practice</b>: Rehearse the communications and planned actions. Increase familiarity with aircraft components and controls. Identify flaws and improve processes.  </p></td>
    <td><div style="text-align:center; margin-left 2em; margin-right:2em;"><html><a href="/Hijacking MH370/Practice" class="nav-btn expand">Practice</a></html></div></td>
</tr>
 
<tr>
      <td><p><b>Performance</b>: Identify an actual flight and perform as planned to facilitate a successful hijack. </p><br /></td>
    <td><div style="text-align:center; margin-left 2em; margin-right:2em;"><html><a href="/Hijacking MH370/Performance" class="nav-btn expand">Performance</a></html></div></td>
</tr>
 
<tr>
      <td><p><b>Problems</b>: Evidence suggests that if MH370 had been hijacked the attempt was only partially successful. Hijackers would not have intended for the flight to end in the south Indian Ocean.</p></td>
    <td><div style="text-align:center; margin-left 2em; margin-right:2em;"><html><a href="/Hijacking MH370/Problems" class="nav-btn expand">Problems</a></html></div></td>
</tr>
 
<tr>
      <td><p><b>Postscript</b>: A collection of facts which, taken together, could indicate that a hijack was intended and did occur. </p></td>
    <td><div style="text-align:center; margin-left 2em; margin-right:2em;"><html><a href="/Hijacking MH370/Postscript" class="nav-btn expand">Postscript</a></html></div></td>
</tr>
<!-- <tr> <td colspan="2"><p>&nbsp;</p></td> </tr> -->
 
</table>
<br />

Latest revision as of 07:42, 25 October 2024

Hijacking MH370

"Without the benefit of the examination of the aircraft wreckage and recorded flight data information, the investigation was unable to identify any plausible aircraft or systems failure mode that would lead to the observed systems deactivation, diversion from the filed flight plan route and the subsequent flight path taken by the aircraft. However, the same lack of evidence precluded the investigation from definitely eliminating that possibility. The possibility of intervention by a third party cannot be excluded either."

Source: Safety Investigation Report MH370/01/2018 SECTION 3.2 – Conclusion (Emphasis added)


This Section accepts the possibility that Malaysia Airlines flight MH370 was hijacked, and explores how it could have been done.

Hijacking an aircraft is a terrorist act and a crime. In Malaysia that could lead to a death penalty; in other jurisdictions up to life in prison.

Hijacking any commercial passenger jet since the events of September 11, 2001 would not be easy. Prior to 9/11 the cockpit was often easily accessed and airline policy was generally to comply with a hijacker's demands. But all that has since changed.

So, if a Malaysia Airlines' Boeing 777 were the target of a hijacking attempt in 2014 what would be involved? There is no revealed plan, there are no informants, there were no named suspects, there is nothing substantial on which to build a case. So everything in this Section is like reverse-engineering: assume a hijack was attempted and, knowing that MH370 headed north-west over the Andaman Sea instead of going to China, devise a possible method.

This Section is divided into sub-pages each with a Topic representing a Stage in the planning and execution process. Each Topic is summarised below. The navigation buttons on the right link to relevant sub-pages.


Security Weaknesses




Sub-page List