Malaysia Finds Manual Controls Diverted MH370 Before Ocean Crash

The Vanishing of Flight 370 — LEMMiNO

LEMMiNO

Official investigations establish that human hands intentionally severed communications and steered the Boeing 777 into the southern Indian Ocean, yet determining the true cause remains impossible until searchers locate the physical wreckage.

AI-assisted summary of The Vanishing of Flight 370 — original source. Check the original for full context.

Source published:

Key ideas

  • Malaysia Airlines Flight 370 vanished off civilian radar less than an hour into its flight to Beijing after its transponders ceased transmitting, initiating the most expensive search operation in aviation history. (0:34)
  • Military radar and satellite handshakes revealed the aircraft executed manual turns back across Malaysia and remained airborne for nearly six hours before fuel exhaustion in the southern Indian Ocean. (3:29)
  • Over 31 pieces of debris recovered along East African and Indian Ocean coastlines confirmed the aircraft went down at sea, yet extensive underwater sonar mapping covering over 120,000 square kilometers located no wreckage. (8:25)
  • The 2018 official safety report concluded the aircraft was diverted deliberately by human intervention, ruling out mechanical failure or autopilot error, but could not identify the perpetrator without the main wreckage and flight recorders. (21:14)

Detailed notes

## Background Published on YouTube by the documentary channel LEMMiNO on April 14, 2019, 'The Vanishing of Flight 370' examines the baffling disappearance of Malaysia Airlines Flight 370, which vanished during a routine flight from Kuala Lumpur to Beijing on March 8, 2014. According to the video description, the production explores the findings of the official investigation and evaluates the leading hypotheses behind one of the most perplexing mysteries in aviation history.

## TL;DR After abruptly dropping off civilian radar over the South China Sea, Malaysia Airlines Flight 370 executed an unexpected turnback across the Malaysian peninsula that was tracked only by military radar. Subsequent analysis of automated satellite handshakes traced the Boeing 777 to the remote southern Indian Ocean, where it flew for hours until fuel exhaustion, though years of exhaustive deep-sea acoustic and sonar mapping failed to locate the main wreckage. While physical debris later confirmed the ocean crash and hypotheses like in-flight fires or accidental hypoxia were systematically scrutinized, evidence of complex manual maneuvers pointed toward deliberate human intervention. Examining recovered flight simulator data from Captain Zaharie alongside crew profiles, the video reviews the 2018 official safety report's conclusion that while systems were manually manipulated, the exact motive and fate of the flight remain unresolved.

## Atmosphere & style The presentation is clinical, analytical, and deeply somber, utilizing a measured narrative style that eschews sensationalism in favor of meticulous, evidence-based scrutiny. A haunting, quiet tension permeates the storytelling, contrasting cold technical metrics—like burst time offsets and radar reflectance—with the eerie void of an advanced airliner vanishing silently into the night. It feels like examining an unsolved forensic dossier in real time, leaving the audience with an unsettling sense of isolation and unresolved tragedy.

## Bulletin - [00:34](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=34s) Malaysia Airlines Flight 370 vanished off civilian radar less than an hour into its flight to Beijing after its transponders ceased transmitting, initiating the most expensive search operation in aviation history. - [03:29](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=209s) Military radar and satellite handshakes revealed the aircraft executed manual turns back across Malaysia and remained airborne for nearly six hours before fuel exhaustion in the southern Indian Ocean. - [08:25](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=505s) Over 31 pieces of debris recovered along East African and Indian Ocean coastlines confirmed the aircraft went down at sea, yet extensive underwater sonar mapping covering over 120,000 square kilometers located no wreckage. - [21:14](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1274s) The 2018 official safety report concluded the aircraft was diverted deliberately by human intervention, ruling out mechanical failure or autopilot error, but could not identify the perpetrator without the main wreckage and flight recorders.

## Key takeaways - [00:34](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=34s) Flight 370 departed Kuala Lumpur with 239 people on board and abruptly vanished from secondary civilian radar screens over the South China Sea just after being handed off to Vietnamese air traffic control. - [03:29](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=209s) Primary military radar tracks demonstrated that the aircraft made a sharp course reversal back across the Malaysian peninsula and out into the Andaman Sea after transponder communication ceased. - [04:28](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=268s) The aircraft's satellite communications terminal powered back on over the Andaman Sea, responding to five automated hourly pings from a ground station in Perth and establishing the Seventh Arc in the southern Indian Ocean. - [07:17](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=437s) Acoustic signals detected by hydrophones were determined to be natural geological activity, and faint underwater locator beacon detections did not lead to wreckage recovery. - [08:25](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=505s) Physical evidence of the crash surfaced in July 2015 when a Boeing 777 flaperon washed ashore on Réunion Island, followed by more than 31 additional fragments recovered along the western Indian Ocean. - [11:32](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=692s) Initial suspicions regarding passengers using stolen European passports or hazardous cargo containing 11 metric tons of freight and lithium-ion batteries failed to explain why the aircraft flew silently for six more hours. - [13:19](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=799s) Hypoxia scenarios fail to account for the flight's deliberate navigation, as the bank angle of the initial left turn exceeded the mechanical limits of the Boeing 777 autopilot and required manual control. - [15:25](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=925s) Data recovered by police from Captain Zaharie's home flight simulator showed a path toward the southern Indian Ocean, though authorities noted the points were disconnected and did not conclusively prove premeditation. - [17:47](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1067s) Extensive background investigations into Captain Zaharie Ahmad Shah and First Officer Fariq Abdul Hamid revealed no financial distress, mental illness, or interpersonal conflicts that indicated motive. - [20:15](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1215s) A Penang cellular tower logged an automatic registration ping from the first officer's mobile phone as the jet skirted the island, refuting reports of an attempted emergency voice call. - [21:14](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1274s) The July 2018 final report established that the flight path was altered under direct manual control and the SATCOM terminal was deliberately de-powered, ruling out system failure. - [22:34](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1354s) Conspiracy theories such as remote ground cyber-hijacking or shootdowns near Diego Garcia lack technical merit, while alternative routes like an attempted emergency landing on Christmas Island remain unsearched in the deep sea.

## Detailed walkthrough ### [00:34](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=34s) Departure and Disappearance over the South China Sea

At Kuala Lumpur International Airport, Malaysia Airlines Flight 370—a Boeing 777 operating a routine daily passenger service between Kuala Lumpur, Malaysia, and Beijing, China—readied for departure. Clearance was issued at forty-two minutes past midnight. In the cockpit were Captain Zaharie Ahmad Shah and First Officer Fariq Abdul Hamid, accompanied by ten cabin crew members and 227 passengers, bringing the total complement aboard to 239 people.

```mermaid flowchart TD accTitle: MH370 Flight and Communication Timeline accDescr: Sequence of tracking events from takeoff at Kuala Lumpur to the flight path turnback and ultimate loss of contact over the Indian Ocean.

subgraph Leg1["Initial Flight Path"] A["Takeoff from Kuala Lumpur (00:42)"] --> B["Cruise at 35,000 ft over South China Sea"] B --> C["ATC Handoff to Ho Chi Minh; Transponders cease (01:21)"] end

subgraph Leg2["Military Radar Tracking"] C --> D["Subtle right turn, sharp prolonged left turn"] D --> E["Crosses Malaysian Peninsula & passes Penang"] E --> F["Heads northwest into Andaman Sea; leaves radar"] end

subgraph Leg3["SATCOM Link & Southern Route"] F --> G["SATCOM logs back on (3 min later)"] G --> H["5 hourly automated pings & 2 unanswered sat-phone calls"] H --> I["7th Arc: Fuel exhaustion over Southern Indian Ocean"] end ```

Less than an hour into the journey, the aircraft was cruising smoothly at an assigned altitude of 35,000 feet above the South China Sea beneath calm weather and clear night skies. As the airliner approached Vietnamese airspace, air traffic control in Kuala Lumpur instructed the crew to contact controllers in Ho Chi Minh City. The Malaysian controller bid the flight good night with no indication whatsoever that anything was amiss.

Merely one minute and forty-three seconds after that final transmission, Flight 370 abruptly vanished from air traffic control radar screens across Kuala Lumpur, Ho Chi Minh, and Bangkok. Because secondary civilian radar relies on signals emitted by onboard transponders, the aircraft's simultaneous disappearance across all monitoring stations pointed to an abrupt cutoff. As the narrator observed: “This form of positional tracking depends on a signal being emitted by one of two transponders aboard the plane, and so its disappearance would suggest both transponders ceased to function, or the system was manually deactivated by someone onboard.” All further attempts to contact the crew or pinpoint the jet's location failed. After failing to arrive in Beijing some four hours later, the aircraft was officially declared missing, initiating the most expensive search operation in aviation history.

- **Aircraft type**: Boeing 777 - **Flight route**: Kuala Lumpur International Airport (KUL) to Beijing Capital International Airport (PEK) - **Departure time**: 00:42 local time - **Flight complement**: 239 individuals (Captain Zaharie Ahmad Shah, First Officer Fariq Abdul Hamid, 10 cabin crew, 227 passengers) - **Cruising conditions**: Altitude of 35,000 feet over the South China Sea under calm, clear weather

[03:29](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=209s) Primary Radar and the Turnback Across Malaysia

The search for the missing airliner was initially concentrated around the South China Sea and the Gulf of Thailand, where civilian radar contact had first been severed. However, this search perimeter shifted radically when the Malaysian military disclosed primary radar records. Unlike civilian air traffic control systems, military long-range radar relies on direct reflectance rather than active transponder replies, allowing it to track aerial targets independently of onboard communications.

Reviewing the defense data revealed that immediately after contact was lost, Flight 370 deviated drastically from its scheduled course to Beijing. The aircraft executed a subtle turn to the right, immediately followed by a prolonged turn to the left, heading back southwest across the Malaysian peninsula. Passing near the island of Penang, the jet turned toward the right onto a northwesterly heading, flying out into the Strait of Malacca until it eventually slipped beyond the radar's operational boundary over the Andaman Sea. In response to this revelation, a multinational flotilla of ships and aircraft combed the waters of the Strait of Malacca, the Andaman Sea, and the Bay of Bengal, yet found no trace of debris.

- **Military tracking method**: Long-range primary radar utilizing raw physical reflectance rather than transponder telemetry - **Flight deviation maneuver**: A slight right turn followed by a sharp, sustained left turn reversing course back over mainland Malaysia - **Key waypoints**: Flew directly across the Malaysian peninsula, executed a right-hand turn near Penang Island, and tracked northwest over the Strait of Malacca - **Secondary search areas**: Strait of Malacca, Andaman Sea, and the Bay of Bengal

[04:28](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=268s) Satellite Handshakes and the Seventh Arc

While surface searches in Southeast Asia proved fruitless, investigators turned to the digital paper trail left by the aircraft’s satellite communications (SATCOM) terminal. Like all modern wide-body jetliners, Flight 370 utilized a SATCOM terminal to exchange automated operational data between the aircraft and the ground. Before takeoff, the terminal logged into the satellite network and established a connection with a dedicated ground station in Perth, Australia, which kept an exact log of all incoming and outgoing signal transactions.

Prior to the disappearance over the South China Sea, the logs indicated that all communications functioned normally. Shortly after the transponders stopped emitting, the SATCOM link was severed and the terminal ceased responding. Mysteriously, three minutes after the aircraft dropped off military radar over the Andaman Sea, the onboard terminal initiated a log-on request to rejoin the network. The SATCOM connection was reestablished and remained undisturbed for nearly six hours, until the jetliner is presumed to have run out of fuel and crashed. During this prolonged period, two ground-to-air satellite phone calls placed to the cockpit were acknowledged by the terminal but went completely unanswered, while the terminal systematically answered five hourly automated status pings sent by the Perth ground station.

``` +---------------------------------------------------------------------------------------------------+ | MH370 SATCOM SIGNAL TRANSMISSIONS | +--------------------------+---------------------------------+--------------------------------------+ | Transmission Type | Transmission Mechanism | Analytical Finding | +--------------------------+---------------------------------+--------------------------------------+ | Ground Station Handshake | Automated hourly ping if no | Log-on request confirmed terminal | | (5 automated requests) | activity logged within 60 min | powered back on over Andaman Sea | +--------------------------+---------------------------------+--------------------------------------+ | Satellite Voice Calls | Two telephone calls initiated | Signals reached terminal and routed | | (2 cockpit calls) | from ground to aircraft | to cockpit, but were left unanswered | +--------------------------+---------------------------------+--------------------------------------+ | Burst Time Offset (BTO) | Precise round-trip travel time | Produced 7 concentric distance arcs; | | Signal Analysis | of satellite transmissions | 7th arc identified as final resting | | | | zone in Southern Indian Ocean | +--------------------------+---------------------------------+--------------------------------------+ ```

Although these automated maintenance handshakes carried no GPS coordinates, specialists calculated the exact distance between the Inmarsat satellite and the aircraft at each exchange by measuring the precise round-trip travel time of the radio transmissions. This mathematical reconstruction generated seven concentric circles of possible locations across the Earth's surface. When factoring in the Boeing 777’s speed, cruising altitude, and fuel reserves, investigators concluded that the aircraft's seventh and final ping occurred along an arc deep in the southern Indian Ocean.

Because this remote expanse fell under Australia's search and rescue sphere, the Australian government took charge of the operation. Adjusting for oceanic drift and aerodynamic projections, international teams mounted an enormous air and maritime operation spanning more than 4,500,000 square kilometers. The location was so extraordinarily remote that search vessels took six days just to sail from port to the search zone, and despite weeks of sweeping the waters, no sign of Flight 370 was spotted.

- **Ground station location**: Perth, Western Australia - **SATCOM re-engagement**: Initiated by the aircraft three minutes after exiting military radar range in the Andaman Sea - **Cockpit satellite telephone calls**: 2 calls routed successfully to cockpit systems; 0 answered - **Distance calculation metric**: Signal round-trip propagation time used to generate the "Seven Arcs" - **Aerial/maritime surface sweep area**: In excess of 4,500,000 square kilometers

[07:17](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=437s) Hydrophones and Underwater Acoustic Beacons

Investigators explored whether the plane's high-speed impact with the ocean surface generated acoustic signatures captured by underwater listening arrays. Hydroacoustic monitoring stations operated by international monitoring networks were queried, and four separate stations recorded underwater sounds near the general time frame. However, while the timing and acoustic direction showed initial consistency with the final satellite handshake, further triangulation showed that the estimated epicenter of the noise did not align with the projected flight path. Scientists concluded that the recordings were almost certainly caused by natural undersea geological activity.

Attention then shifted toward the flight data and cockpit voice recorders, both fitted with underwater locator beacons (ULBs) engineered to emit high-frequency acoustic pulses for roughly 40 days before battery exhaustion. In early April 2014, just as the beacon batteries were expected to expire, search ships picked up faint acoustic signals matching the beacons' frequency at depths reaching 3,000 meters. An autonomous underwater vehicle was deployed to execute high-resolution sonar scans across the ocean floor where the sounds had been logged. The submersible spent weeks methodically surveying the abyssal seabed, but recovered no wreckage.

- **Acoustic monitoring**: 4 hydroacoustic stations detected sounds, later attributed to natural submarine geological shifts - **Beacon battery lifespan**: Approximately 40 days from the moment of water immersion - **Submersible search depth**: Up to 3,000 meters below the surface using autonomous submersibles

[08:25](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=505s) Marine Debris and Seafloor Searches

For more than sixteen months following the disappearance, no physical evidence of the aircraft was ever discovered. That silence broke on July 29, 2015, when beach cleaners on the island of Réunion—a French department situated east of Madagascar—discovered a barnacle-covered, two-meter-long piece of metal washed up on the shoreline. Aviation investigators identified the component as an aircraft flaperon, and internal serial numbers and production stamps confirmed that it belonged to the missing Malaysia Airlines Boeing 777.

As the narrator underlined regarding the significance of the find: “There was now tangible evidence that Flight 370 had crashed somewhere in the Indian Ocean.” Although Réunion lies roughly 4,000 kilometers west of the primary maritime search zone, extensive oceanographic reverse-drift modeling demonstrated that floating debris from the southern Indian Ocean would naturally drift across the basin toward southeastern Africa over that sixteen-month interval.

The discovery sparked a concerted debris-recovery campaign along East African coastlines and nearby island nations. More than 31 additional items of interest were recovered and analyzed:

- A section of the outboard flap from the right wing - An engine cowling segment - A partial door from the nose landing gear - A piece of the vertical stabilizer - A crushed internal casing from an in-flight passenger seatback entertainment monitor

Of the 32 total recovered items, 3 were positively confirmed as MH370 components, while 18 were categorized as either likely, highly likely, or almost certain to have originated from the aircraft. The remaining 11 items could not be conclusively linked. Forensic inspection revealed no signs of an explosive blast or shrapnel damage, nor any indicators of an in-flight fire, save for three small scorch marks found on a single unidentifiable fragment.

``` +---------------------------------------------------------------------------------------------------+ | MH370 PHYSICAL EVIDENCE BREAKDOWN | +--------------------------+-----------------------+------------------------------------------------+ | Debris Category | Quantity Recovered | Examples / Notable Characteristics | +--------------------------+-----------------------+------------------------------------------------+ | Confirmed MH370 Compo- | 3 items | Right wing flaperon (Réunion Island), | | nents | | outboard flap section | +--------------------------+-----------------------+------------------------------------------------+ | Highly Likely / Almost | 18 items | Engine cowling, nose gear door segment, | | Certain | | vertical stabilizer, seatback monitor frame | +--------------------------+-----------------------+------------------------------------------------+ | Unidentifiable / Uncon- | 11 items | Miscellaneous composite fragments; one piece | | firmed | | bore three small localized scorch marks | +--------------------------+-----------------------+------------------------------------------------+ ```

Earth observation satellites were also re-examined. Archival orbital imagery taken in March 2014 surfaced ambiguous shapes floating on or just beneath the ocean surface within the Southern Indian Ocean, but the resolution was insufficient to distinguish identification marks, and targeted sweeps never relocated the objects. Another satellite image captured hours after the final satellite handshake showed a linear white streak that appeared to be an engine contrail, but subsequent meteorological evaluation determined it was merely the shadow cast by a high-altitude linear cloud formation.

By early 2017, after mapping over 120,000 square kilometers of rugged seabed with deep-tow sonar, the joint international underwater search was suspended. In 2018, the private American marine salvage firm Ocean Infinity resumed the deep-sea hunt using advanced autonomous underwater vehicles on a "no find, no fee" contract, but after more than a year of scouring expanded priority areas, they also found nothing. The narrator reflected on the fundamental obstacle facing the investigation: “Unless the final resting place of Flight 370 can be located, it may be impossible to determine exactly why it crashed.”

- **Flaperon recovery date and location**: July 29, 2015, on Réunion Island (east of Madagascar) - **Distance from search grid**: Approximately 4,000 kilometers west of the Southern Indian Ocean priority zone - **Total coastline items analyzed**: Over 31 additional items examined (3 confirmed, 18 likely/almost certain, 11 unconfirmed) - **Official deep-sea sonar search coverage**: 120,000 square kilometers before suspension in early 2017

[11:32](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=692s) Passenger Scrutiny and Cargo Fire Hypotheses

In the absence of a wreckage site, investigators explored numerous hypotheses regarding human foul play and mechanical failure. On the morning of the disappearance, attention fixed on two Iranian passengers who had boarded the airliner using stolen Austrian and Italian passports, raising immediate fears of a terrorist hijacking. However, intelligence checks failed to link either man to any extremist group, and background inquiries quickly verified that they were young asylum seekers trying to reach Europe via Beijing under false identities. Similar concerns surrounded another passenger identified as a flight engineer, on the premise that he might have possessed the technical skill to override cockpit flight systems, though no evidence implicating him was ever uncovered.

Investigators also scrutinized the aircraft's cargo manifest. Alongside its 239 passengers and crew, Flight 370 carried nearly 11 metric tons of cargo, which included a large commercial consignment of lithium-ion batteries. Lithium-ion batteries carry known risks of thermal runaway; a pallet of such batteries had ignited and brought down UPS Airlines Flight 6 in Dubai in September 2010.

A related mechanical scenario involved an internal electrical fire, similar to the catastrophe that destroyed Swissair Flight 111 in September 1998, when arcing in the ceiling wiring above the cockpit sparked an uncontained blaze that disabled primary instruments, transponders, and avionics. A sudden catastrophic fire aboard Flight 370 could explain why transponders cut out simultaneously and why the pilots initiated a sudden turnback toward the Malaysian mainland in a desperate bid to reach the nearest suitable runway. Yet that theory ran into an insurmountable contradiction: rather than attempting an emergency descent or landing at nearby diversion airfields, the aircraft maintained its course across the peninsula, entered the open ocean, and flew on silently through the night. The narrator emphasized this central paradox: “Instead, Flight 370 kept going and remained aloft for another six hours.”

- **Stolen passports**: Two passengers traveled on stolen Austrian and Italian passports; cleared as non-extremist asylum seekers - **Suspicious passenger profile**: A flight engineer passenger was investigated for aeronautical expertise, but no wrongdoing was found - **Hazardous cargo**: Almost 11 metric tons of total cargo, including a large shipment of lithium-ion batteries - **Historical fire precedents cited**: UPS Airlines Flight 6 (September 2010, lithium-ion battery fire) and Swissair Flight 111 (September 1998, cockpit electrical wiring fire)

[13:19](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=799s) Hypoxia Theories and Flight Dynamics Anomalies

A leading hypothesis evaluated by investigators is that the crew and passengers may have been incapacitated by a sudden or gradual loss of cabin pressure. Such an event has precedent in aviation history: in August 2005, Helios Airways Flight 522 suffered a cabin pressurization failure, rendering the flight crew unconscious from hypoxia while the aircraft continued on autopilot for more than two hours until its fuel was completely exhausted. Commercial airline pilots are rigorously trained to handle depressurization, and modern airliners feature automated emergency systems that drop oxygen masks to supply breathable air while pilots execute an immediate descent to a safe altitude. While decompression at 35,000 feet followed by crew incapacitation would explain why Flight 370 remained airborne for hours until running out of fuel, it fails to account for the deliberate navigation maneuvers that followed the loss of communication.

The altitude readings registered by Malaysian military radar presented extreme anomalies that baffle investigators. According to the recorded radar track, the aircraft climbed more than 15,000 feet above its certified service ceiling before entering a steep dive of 50,000 feet in less than sixty seconds. These maneuvers are aerodynamically impossible for a Boeing 777 airframe. As the narrator explains, “Attempts to recreate these maneuvers on a flight simulator were unsuccessful, and thus the data was deemed inaccurate and unreliable.”

The critical challenge to the ghost-flight theory lies in the aircraft's subsequent changes in direction. Flight reconstruction models revealed that the sharp initial turn back to the west could not have been executed by the aircraft's automated systems. As the narrator observes, “Flight simulations have established the aircraft must have been under manual control during the initial left turn as the bank angle, or inclination, of that turn, was beyond the limits of the autopilot.” While later heading adjustments across the Strait of Malacca and toward the southern Indian Ocean could theoretically have been flown automatically, someone with technical knowledge would have had to manually input those waypoints into the flight management computer, leaving manual flight intervention as the only viable explanation.

```mermaid flowchart TD accTitle: Flight Control Hypotheses for MH370 accDescr: Flowchart illustrating the technical analysis of MH370's flight maneuvers, comparing autopilot behavior against manual inputs.

subgraph ManeuverAnalysis["Radar Track & Flight Dynamics"] Turn["Initial Sharp Turn Left"] Altitude["Radar Altitude Spikes (+15k ft / -50k ft dive)"] Subsequent["Subsequent Heading Changes"] end

subgraph Assessment["System Assessment"] SimFail["Simulator Testing: Aerodynamically Impossible"] ManualReq["Bank Angle Exceeds Autopilot Limits"] ProgOrManual["Requires Waypoint Entry or Stick Control"] end

subgraph Conclusion["Deduction"] RadarUnreliable["Military Altitude Data Deemed Unreliable"] HumanControl["Direct Human Intervention Required"] end

Turn --> ManualReq Altitude --> SimFail Subsequent --> ProgOrManual SimFail --> RadarUnreliable ManualReq --> HumanControl ProgOrManual --> HumanControl ```

[15:25](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=925s) The Captain's Flight Simulator and Leaked Police Files

By late June 2014, news reports surfaced alleging that special investigators had centered their suspicion on the flight's captain after forensic analysis of a home flight simulator seized from his residence revealed a suspicious flight path into the southern Indian Ocean. For nearly two years, official authorities maintained silence regarding this discovery; the extensive preliminary report published by the Malaysian government in 2015 made no mention whatsoever of simulator data. The silence was broken in 2016 when leaked confidential documents revealed that the Royal Malaysia Police had conducted an in-depth forensic investigation into the simulator as early as May 2014, confirming that the simulated route had indeed been identified and cataloged.

The recovered data consisted of seven specific coordinate points: two located around Kuala Lumpur, two in the Strait of Malacca, one in the Bay of Bengal, and two terminating in the remote reaches of the southern Indian Ocean. These data points had been automatically recorded in a cache file by the simulation software roughly a month prior to MH370's disappearance. While critics viewed this as clear proof of a premeditated suicide mission, investigators warned that the data points were disconnected remnants that may not have originated from a single continuous flight session. In their official assessment, the narrator highlights the cautious findings of the authorities, quoting the Royal Malaysia Police forensic examination: “No activity captured conclusively indicate any kind of premeditated act pertaining to the incident of MH370.”

Despite the lack of legal certainty, the simulator's coordinates closely matched the projected track of Flight 370 and heavily influenced the search strategy coordinated by Australian search authorities: - Investigators evaluated whether a pilot actively flying the aircraft might have executed an unpowered glide after fuel exhaustion, which could have extended the aircraft's range by up to an additional 200 kilometers. - Authorities also modeled the possibility of a pilot executing a controlled ditching onto the ocean surface before running out of fuel, which would conversely have shortened the final flight distance. - Although both deliberate-control ditching scenarios were eventually regarded as less probable than an unguided high-speed descent, they forced search teams to broaden their underwater search parameters.

[17:47](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1067s) Profiles of Captain Zaharie and First Officer Fariq

Scrutiny of Captain Zaharie Ahmad Shah yielded little evidence of motive or malice. At 53 years of age, Zaharie was a married father of three with an exemplary record spanning more than 18,000 flight hours. Inquiries into his financial records, bank accounts, and monthly expenditures revealed normal spending habits with no debts or irregularities. Psychological evaluations found no history of mental illness, personality changes, or unusual personal behavior leading up to the flight. While some theorists speculated that the flight path's turn southwest of Penang was a deliberate nostalgic gesture to catch a final glimpse of his native island, and others suggested political motives tied to his vocal support for an opposition leader imprisoned hours before departure, investigators found nothing concrete to validate these ideas. Unconfirmed media claims of domestic discord were directly disputed by family members and contradicted by official reports.

The final official report highlighted only one procedural irregularity attributed to the captain: his omission of the standard readback of the radio frequency during his final radio sign-off with air traffic control. The narrator emphasizes the breach in protocol, stating, “It would have been standard procedure to repeat the assigned frequency as the captain had correctly done a few minutes prior.” Apart from this minor error, Zaharie was widely regarded by colleagues as an affable and dedicated aviation enthusiast who routinely uploaded instructional community service videos online, featuring recordings where he cheerfully told viewers, “Hi everyone. This is a YouTube video that I've made as a community service.”

First Officer Fariq Abdul Hamid presented an even less suspicious profile. At 27 years old, Fariq was engaged to marry a fellow commercial airline pilot and held nearly 3,000 total flight hours, although he had logged only 39 hours in the Boeing 777. Background checks revealed no interpersonal conflict between the two crew members, nor any financial or psychological warning signs. Addressing skeptics who questioned how one pilot could commandeer an aircraft without a struggle, the video cites the February 2014 hijacking of Ethiopian Airlines Flight 702, where the copilot locked the captain out of the flight deck during a routine restroom visit and flew the plane to Switzerland to request asylum.

The leaked police documents confirmed one additional detail concerning Fariq: - A cellular tower on Penang briefly detected an automatic network handshake from an iPhone 5S belonging to Fariq as Flight 370 skirted the island. - Investigators verified that this signal was an automatic location ping generated by the phone attempting to register with the tower, refuting early media claims that the copilot had attempted to make an emergency voice call. - The rationale behind the Malaysian government's decision to suppress this cell tower data from public interim reports remains unknown.

[21:14](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1274s) The 2018 Final Report, Alternate Theories, and Unanswered Questions

The comprehensive safety investigation report released by the Malaysian government in July 2018 concluded that mechanical failure, electrical breakdown, or autopilot malfunctions could not account for the diversion or radio silence of Flight 370. The inquiry concluded that the aircraft's systems had been manipulated by human hands. Analysis indicated that the satellite data unit (SATCOM) had been taken offline by a deliberate disruption of electrical power before being reconnected and initiating an automatic log-on sequence, and the course corrections across the ocean were deemed the product of manual inputs. However, because the evidence was strictly circumstantial, the report refrained from assigning blame or officially classifying the event as a unlawful hijacking.

The investigative impasse is summarized by the consensus between maritime authorities: “Both the Malaysian and Australian government agree that Flight 370 crashed in the southern Indian Ocean but that the cause is indeterminable without a wreckage.” The inability to pinpoint the debris field over half a decade prompted a wave of speculative scenarios from outside commentators: - Conspiratorial claims asserted the airliner had been shot down near an American military installation on Diego Garcia in the Indian Ocean, with subsequent satellite pings fabricated to cover up the event. - Another fringe hypothesis claimed the aircraft turned toward Central Asia, flying undetected to Kazakhstan while physical debris was secretly planted across islands in the western Indian Ocean and the east coast of Africa. - Suggestions that the airliner was overtaken via remote cyber-hijacking from the ground were dismissed, as no commercial transport aircraft has ever been fitted with fly-by-wire remote override architecture.

A more grounded alternate flight path emerged in 2018 from an independent team of French investigators. They suggested the aircraft might have been attempting an emergency landing on Christmas Island, an Australian territory south of Indonesia. Under this model, an aborted approach or fuel exhaustion would place the crash site significantly farther north than the official high-priority search zones. Although naval vessels performed a brief surface sweep near Christmas Island during the first week of the search, the comprehensive deep-water sonar mapping campaign never extended to those northern coordinates. With official undersea searches suspended and discussions to resume operations yielding no definitive timeline, the disappearance of MH370 endures as one of aviation's most perplexing enigmas.

## Notable quotes > [08:25](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=505s) Unless the final resting place of Flight 370 can be located, it may be impossible to determine exactly why it crashed. — LEMMiNO

## Mentioned Boeing 777, Christmas Island, Diego Garcia, Ethiopian Airlines Flight 702, Fariq Abdul Hamid, Helios Airways Flight 522, Inmarsat, Kuala Lumpur International Airport, LEMMiNO, Malaysia Airlines, Malaysia Airlines Flight 370, Ocean Infinity, Perth Ground Station, Réunion Island, Royal Malaysia Police, Swissair Flight 111, UPS Airlines Flight 6, Zaharie Ahmad Shah

## Video description On the 8th of March, 2014, Malaysia Airlines Flight 370 vanished during a routine flight between Kuala Lumpur, Malaysia and Beijing, China. The case has since grown into one of the most puzzling mysteries in aviation history. In this video, I examine the findings of the official investigation and explore some of the leading theories.

𝐂𝐫𝐞𝐝𝐢𝐭𝐬, 𝐫𝐞𝐟𝐞𝐫𝐞𝐧𝐜𝐞𝐬, 𝐚𝐧𝐝 𝐦𝐨𝐫𝐞 https://www.lemmi.no/p/the-vanishing-of-flight-370

𝐒𝐮𝐩𝐩𝐨𝐫𝐭 𝐦𝐞 𝐨𝐧 𝐏𝐚𝐭𝐫𝐞𝐨𝐧 https://www.patreon.com/lemmino

𝐒𝐮𝐩𝐩𝐨𝐫𝐭 𝐦𝐞 𝐨𝐧 𝐘𝐨𝐮𝐓𝐮𝐛𝐞 https://www.youtube.com/c/lemmino/join

𝐒𝐨𝐜𝐢𝐚𝐥𝐬 Bluesky: https://bsky.app/profile/lemmi.no https://www.reddit.com/r/lemmino https://www.discord.gg/lemmino

[Source](https://www.youtube.com/watch?v=kd2KEHvK-q8)

中文简报

马来西亚调查指MH370坠海前曾遭人为操纵改道 官方调查确认有人蓄意切断通信并将波音777引向南印度洋，但在搜寻人员找到机体残骸前，仍无法确定真正的事故原因。 马来西亚航空370号班机在南中国海上空突然从民航雷达上消失后，出人意料地折返穿过马来半岛，该过程仅被军用雷达捕捉到。随后对自动化卫星握手信号的分析表明，这架波音777飞向了偏远的南印度洋，并在燃油耗尽前飞行了数小时；尽管多年来进行了详尽的深海声学和声呐测绘，但仍未能找到主要残骸。虽然实物残骸后来证实了客机坠海，空中起火或意外缺氧等假设也受到了系统性审查，但复杂的受控机动证据指向了蓄意的人为干预。通过结合机组人员背景审查从机长扎哈里处恢复的飞行模拟器数据，视频回顾了2018年官方安全报告的结论：尽管系统遭到人为操纵，但该航班的具体动机和最终结局仍未解开。 马来西亚航空370号班机在飞往北京的航程中起飞不到一小时应答机便停止发射信号，从民航雷达上消失，从而引发了航空史上耗资最高的搜寻行动。 (0:34) 军用雷达和卫星握手信号显示，该客机经人为操纵折返穿过马来西亚，并在南印度洋燃油耗尽前继续飞行了近六个小时。 (3:29) 在东非和印度洋沿岸收集到的31多件残骸证实客机已坠海，但在超过12万平方公里的水下开展的大范围声呐测绘未发现任何机体主要残骸。 (8:25) 2018年官方安全报告得出结论，客机系遭人为蓄意改道，排除了机械故障或自动驾驶仪失误，但在找到主要残骸和飞行记录仪之前，无法确认具体作案人员。 (21:14)

Reading summary

Official investigations and recovered marine debris confirm that Malaysia Airlines Flight 370 crashed in the southern Indian Ocean following deliberate manual intervention, yet the inability to locate the main wreckage leaves the ultimate motive and cause unresolved. Radar Anomalies and Evidence of Deliberate Control (3:29) Civilian transponder signals ceased abruptly at forty-one minutes past midnight over the South China Sea, less than two minutes after air traffic controllers handed the Boeing 777 over to Ho Chi Minh airspace. However, Malaysian military primary radar revealed that the aircraft executed an immediate turnback, conducting a slight right turn followed by a sustained left turn back across the Malaysian peninsula, passing near Penang and heading northwest into the Andaman Sea before slipping out of radar range. Flight simulation reconstructions established that this initial sharp turn was conducted under manual control, as the aircraft's bank angle exceeded the operational limits of the autopilot. While subsequent course changes over the Malacca Strait could theoretically have been flown automatically, they still required an operator with technical knowledge to manually program the waypoints into the flight management computer, ruling out an unguided drift from the initial point of communication loss. Satellite Telemetry, Drift Modeling, and Physical Evidence (4:28) Three minutes after vanishing from military radar, the jet's satellite communications terminal unexpectedly reconnected with a ground station in Perth, Western Australia. Over the next six hours, the terminal systematically replied to five automated hourly status pings and routed two ground-to-cockpit satellite phone calls that went completely unanswered. By calculating the round-trip radio propagation time—the Burst Time Offset—investigators generated seven concentric geographic arcs, determining that the flight ultimately exhausted its fuel along a remote corridor in the southern Indian Ocean. While extensive surface and underwater acoustic searches across millions of square kilometers failed to detect wreckage, physical evidence surfaced on July 29, 2015, when a wing flaperon washed ashore on Réunion Island, roughly 4,000 kilometers west of the priority search grid. Oceanographic reverse-drift modeling verified that debris from the southern Indian Ocean would naturally reach African shores over sixteen months. In total, 32 aircraft fragments were recovered across East Africa and nearby islands; 3 were definitively confirmed as MH370 parts, and 18 were deemed highly likely to have originated from the aircraft. Flaws in Fire and Hypoxia Hypotheses (11:32) Investigators closely examined mechanical disaster scenarios, including potential thermal runaway from a consignment of lithium-ion batteries among the plane's 11 metric tons of cargo—echoing the crash of UPS Airlines Flight 6—or an electrical fire similar to Swissair Flight 111. While an acute fire could explain why dual transponders failed simultaneously and why the crew initiated a turnback toward the mainland, it cannot explain why the airliner bypassed accessible diversion runways and continued flying silently across open ocean for another six hours. Depressurization leading to pilot hypoxia, comparable to the loss of Helios Airways Flight 522, was also evaluated as an explanation for an unresponsive ghost flight. Although severe decompression could leave passengers and crew incapacitated while the aircraft flew on until fuel exhaustion, it fails to explain the deliberate, complex navigational maneuvers executed immediately after radar contact was lost. Crew Scrutiny and Captain's Flight Simulator Findings (15:25) Background checks into First Officer Fariq Abdul Hamid and Captain Zaharie Ahmad Shah uncovered no financial stress, psychological instability, or links to extremism. The only documented operational deviation in Zaharie's record was omitting the standard radio frequency readback during his final transmission to air traffic control. Inquiries also resolved early suspicions regarding two Iranian passengers traveling on stolen European passports, identifying them as non-extremist asylum seekers. Attention focused heavily on Captain Zaharie after leaked police records from 2014 revealed that his home flight simulator contained a cached six-point flight path recorded a month prior to the event, which traced a route over Malaysia and into the southern Indian Ocean. While search teams utilized this data to model whether a pilot actively glided the aircraft after fuel exhaustion, the Royal Malaysia Police forensic report maintained that the disconnected coordinates did not conclusively prove a premeditated act. The Malaysian government's 2018 comprehensive investigation concluded that mechanical or electrical failures could not account for the disappearance, confirming that the flight path and communication systems had been manually altered. However, because deep-tow sonar surveys covering more than 120,000 square kilometers of seafloor were suspended without locating the flight data recorders, both Malaysian and Australian authorities concur that the definitive cause of the crash remains indeterminable.

精炼阅读摘要

根据LEMmNO发布的调查梳理，马来西亚航空MH370航班的失踪无法用单纯的机械故障或突发事故解释，现有飞行数据与卫星链路表明其偏航由机上人为操控所致；然而，因核心残骸始终未能寻获，官方最终调查报告仍无法给出确凿定论。 航迹异常与手动操控证据 (3:29) MH370在吉隆坡空管与胡志明市空管交接之际，应答机信号突遭中断，民用二次雷达随后失去该机踪迹。马来西亚军方一次雷达数据显示，飞机随即做出微幅右转，紧接着出现长时间的大角度左转，直接横穿马来半岛并掠过槟城，随后沿西北方向飞入安达曼海。飞行模拟测试表明，该机最初左转时的倾斜角已超出波音777自动驾驶仪的设计极限，证明当时处于手动操纵状态。尽管军方雷达记录曾显示该机剧烈爬升15,000英尺又在60秒内俯冲50,000英尺，但模拟证明客机在气动结构上不可能完成此类机动，相关高度数据被认定为不准确且不可靠；随后的多次航向修正同样需要具备专业知识的人员手动干预或向飞行管理计算机重新录入航路点。 卫星握手数据与第七弧线定位 (4:28) 在应答机关闭且飞机脱离军方雷达范围3分钟后，机载卫星通信终端（SATCOM）重新发起登录请求并恢复连接，并在其后近六小时内自动响应了珀斯地面站发出的5次整点寻呼，期间地面向驾驶舱拨打的2次卫星电话均成功接通机载设备却无人接听。专业人员通过测量无线电信号往返传输时间（BTO）推算出客机与卫星间的相对距离，在地球表面绘制出7条同心圆弧线。结合该机燃油储量与巡航速度，调查团队测算出客机在燃油耗尽前的最后一次卫星握手发生在南印度洋深处的“第七弧线”，这一计算使得搜救重心从最初的南海与马六甲海峡彻底转移至由澳大利亚主导的南印度洋海域。 海底声学盲区与海岸飘流残骸 (7:17) 在确定南印度洋搜索区后，水下水听器阵列虽记录到声学信号，但经三角测量判定属于自然海底地质活动而非客机撞击；而针对飞行记录器水下定位信标（寿命约40天）的搜寻，最终借助自主水下航行器下潜至3,000米深处扫描亦无斩获。直至客机失踪16个月后的2015年7月29日，法属留尼汪岛海滩才首次发现一件长达2米、附着藤壶的襟副翼，序列号证实其属于MH370，确凿证实飞机已坠毁于印度洋。逆向洋流漂流模型显示，南部印度洋的漂浮物在一年多时间内完全可自然漂移4,000公里至非洲东部。此后非洲海岸共回收分析了32件物品，其中3件确认为该机部件，18件被评估为高度可能或几乎确定来自该机，残骸法医检查未发现爆炸炸药痕迹、破片穿孔或飞行中起火的迹象。 机组调查、模拟器疑云与事故假说 (11:32) 针对劫机与机械故障的多项假说均被逐一排查。持被盗欧洲护照登机的两名伊朗乘客经查为偷渡难民；客机所载近11吨货物中包含大量锂电池，但若发生锂电池热失控或如瑞士航空111号班机般的机舱电线起火，无法合理解释客机为何没有就近迫降而在失联后继续飞行长达六小时；类似太阳神航空522号班机的高空失压缺氧假说，也无法解释客机随后执行的复杂主动变向。调查随后聚焦于机组人员：53岁的机长扎哈里（Zaharie Ahmad Shah）累积飞行超过18,000小时，其财务、心理及私人生活均无异常，仅在最后通话中遗漏了无线电频率复诵这一程序；27岁的第一副驾驶法里克（Fariq Abdul Hamid）个人背景同样干净。泄露的警方机密文件显示，扎哈里家中模拟机曾记录过飞入南印度洋的航线残骸坐标，但马来西亚皇家警察官方评估认为，这些散落的坐标数据无法确定是一次完整的连贯模拟，不足以推断存在预谋坠机行为。 马来西亚政府于2018年7月公布的最终安全调查报告正式排除了机械系统故障与自动驾驶故障导致偏航的可能，确认飞机系统遭受了人为操纵，包括SATCOM曾被人为切断电源后重新连接。然而，由于搜寻面积累计超过120,000平方公里的大规模水下声呐扫描以及后续私营公司的无成果搜索均告中止，在关键机体残骸与飞行记录器未被定位前，马来西亚与澳大利亚官方一致认同，MH370最终坠入南印度洋的确切致灾原因仍无法得出最终定论。

Detailed notes — zh

## Background 该视频由知名创作者 LEMMiNO 于 2019 年 4 月 14 日发布在 YouTube 平台上。视频简介指出，2014 年 3 月 8 日马来西亚航空 370 号班机在吉隆坡飞往北京的常规航线中失踪，演变成航空史上最难解的谜团之一，本片旨在梳理官方调查结果并探讨各种主流假说。 ## TL;DR 视频深入梳理了马航 MH370 航班从起飞、通讯瞬间中断、军用雷达捕获异常折返，再到依靠 SATCOM 卫星握手信号锁定南印度洋“第七弧”的完整失联轨迹。调查人员通过水下信标侦听、洋流漂移模型及法属留尼汪岛等地发现的襟副翼等真实残骸，确认飞机坠毁于南印度洋，但耗资巨大的深海声呐扫描始终未找到主残骸。全片进一步评估了机组失能、客舱起火、机长飞行模拟机坐标泄密以及可能的人为蓄意操纵等理论，最终指出在缺少黑匣子核心物证的情况下，这起现代航空史上最大的悬案依然无法给出确凿定论。 ## Atmosphere & style LEMMiNO 秉持其一贯极其克制、严谨且富有沉浸感的纪录片叙事风格，伴随低沉从容的旁白和冷峻幽暗的极简动态图表，营造出一种被无边深海包围的压抑与窒息感。情绪弧线从最初突发失联的困惑与震惊，逐渐过渡到漫长搜寻无果的虚无与挫败，最后在层层技术推演与人性动机的撕裂中归于深深的敬畏与唏嘘。整部影片没有任何耸人听闻的廉价惊悚，而是用冷酷精确的数据与无法合拢的逻辑缺口，让观众真切体会到文明技术面对苍茫大洋时的无力与深渊般的死寂。 ## Bulletin - [00:34](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=34s) 马来西亚航空MH370于2014年3月8日自吉隆坡起飞后在南中国海上空失联，随后大角度折返横穿马来半岛，最终推断耗尽燃油坠毁于南印度洋。 - [04:28](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=268s) 调查人员依据机载SATCOM终端与澳大利亚珀斯地面站的5次自动握手信号，通过往返延迟在地球表面推算出的“第七弧”锁定了南印度洋搜索区域。 - [07:17](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=437s) 2015年7月在法属留尼汪岛发现并确认属于MH370的襟副翼残片，提供了客机最终坠入印度洋的首个确凿物理物证。 - [21:14](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1274s) 马来西亚政府2018年安全报告认定通信中断、系统重启与偏航均系人为干预操纵所致，但受限于黑匣子及核心残骸未寻获，始终未将事件正式定性为劫机。 ## Key takeaways - [00:34](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=34s) MH370在交接给胡志明空管后仅1分43秒便从民航雷达消失，说明两台应答机同时停工或被人为手动关闭。 - [03:29](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=209s) 军用一次雷达记录显示飞机在失联瞬间向右微偏后进行大角度急剧左转，横穿马来半岛并掠过槟城上空飞向安达曼海。 - [04:28](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=268s) SATCOM链路在雷达盲区断开3分钟后主动请求重新登录并在线近6小时，期间两次地面卫星电话呼叫均未获应答。 - [04:28](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=268s) 多国部队在推算出的南印度洋第七弧展开了覆盖超450万平方公里的水面搜救与12万平方公里海底扫描，均未发现机体主体。 - [09:19](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=559s) 法属留尼汪岛及非洲东南部沿海共搜集到31件可疑物件，其中3件确认为MH370残片且未见机载爆炸或大火破坏痕迹。 - [13:19](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=799s) 军方雷达所记录的超限升降数据被模拟器测试推翻并判定不可靠，而最初的大坡度急转弯断定为人工操纵。 - [15:25](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=925s) 警方在机长个人飞行模拟机中恢复出终点深入南印度洋的7个坐标点，但司法取证结论认为不足以确证蓄意预谋。 - [17:47](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1067s) 机长扎哈里飞行经验超过1.8万小时且无财务或精神异常，副驾驶法里克在槟城上空时其iPhone曾被地面基站自动定位。 - [21:14](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1274s) 官方最终报告排除了机械故障致灾，认定SATCOM系统异常与变轨属于人为操纵断电并重连。 - [21:14](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1274s) 美军基地击落论、哈萨克斯坦迫降论及地面遥控论缺乏证据支持，法国调查组则推测客机可能曾试图备降圣诞岛而坠于更偏北海域。 ## Detailed walkthrough ### [00:34](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=34s) 午夜起飞与静默消失 在马来西亚吉隆坡国际机场，一架波音777客机正整装待发。这架执飞马来西亚航空370号班机（MH370）的飞机，原本执行的是一条日常客运航线，往返于马来西亚吉隆坡与中国北京之间。午夜零点42分，MH370获准起飞。机上载有机长扎哈里·艾哈迈德·沙阿（Zaharie Ahmad Shah）、副驾驶法里克·阿卜杜勒·哈米德（Fariq Abdul Hamid）、10名机组人员以及227名乘客，共计239人。 飞行进行了不到一小时，客机正在南中国海上空35,000英尺的高度平稳巡航。夜空晴朗，气象条件极佳。由于飞机即将进入越南领空，吉隆坡空中交通管制员指示MH370联络越南胡志明市的空管中心。吉隆坡管制员向机组道了晚安，没有任何迹象表明有任何异常。 然而，仅仅1分43秒之后，该机突然从吉隆坡、胡志明市以及曼谷三地的雷达屏幕上彻底消失。民航的位置追踪依赖机上两台应答机（Transponders）中的一台发射信号；飞机从民航空管雷达上瞬间消失，意味着两台应答机同时停止了工作，或者该系统被人为手动关闭。此后所有试图重新联络并确认客机方位的尝试全部落空，飞机仿佛凭空人间蒸发。在原定降落北京的时间过去约四个小时后，官方正式宣布MH370失联。随后，航空史上耗资最为极其庞大的搜救行动就此展开。 - 航班号：马来西亚航空370（MH370） - 机型：波音 777 - 起飞时间：午夜 00:42 - 机组与乘客：机长 Zaharie Ahmad Shah、副驾驶 Fariq Abdul Hamid、10 名乘务员、227 名乘客（机上共 239 人） - 失联空域：南中国海上空，高度 35,000 英尺，交接给胡志明空管后 1 分 43 秒即从雷达屏幕上消失 ### [03:29](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=209s) 军用雷达的转折与折返路径 最初的搜救行动主要集中在客机消失的区域，即南中国海与泰国湾之间。但不久之后，马来西亚军方公开了额外的情报，搜索范围随即大幅扩张。与空中交通管制依赖应答机信号的二次雷达不同，远距离军用一次雷达不依赖应答机，而是通过无线电反射来追踪空中目标的实体位置。 ```mermaid flowchart LR accTitle: MH370航向偏离示意图 accDescr: 描绘MH370从正常航线偏离后飞向安达曼海的航迹转折流程 subgraph Leg1["第一阶段：异常转向"] A["南中国海上空失联"] --> B["向右微偏后<br/>长时间大角度左转"] end subgraph Leg2["第二阶段：横穿半岛"] B --> C["折返横穿马来半岛"] C --> D["在槟城附近右转"] end subgraph Leg3["第三阶段：脱离覆盖"] D --> E["沿西北航向飞行"] E --> F["在安达曼海上空<br/>脱离军用雷达覆盖"] end ``` 军方对雷达数据的复盘显示，在MH370失联的瞬间，飞机就偏离了预定航线：先是向右产生轻微偏航，紧接着进行了一次长时间的大角度左转。随后，飞机折返横穿整个马来半岛，并在槟城（Penang）附近向右转向，沿着西北航向一直飞行，直到脱离马来西亚军用雷达的有效覆盖范围。在接下来的几天里，多国组成的搜救机队与船队对马六甲海峡、安达曼海以及孟加拉湾进行了地毯式排查，却依旧一无所获。 ### [04:28](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=268s) 卫星通信握手与南印度洋第七弧 在海面搜索毫无头绪之际，调查人员开始分析客机的卫星通信（SATCOM）记录。现代客机均配备卫星通信终端，用于地面与飞机间的数据传输。起飞前，MH370的SATCOM终端登录了卫星网络，并与位于澳大利亚珀斯的地面站建立了连接，该地面站完整记录了双方往来的所有数据流。 记录显示，在南中国海失踪前，机上所有通信均属正常。但在飞机折返的某段飞行过程中，SATCOM通信链路被切断，终端因不明原因停止响应。然而，就在客机消失在安达曼海雷达盲区的3分钟后，该终端又主动请求重新登录网络。卫星链路随后成功恢复，并一直保持在线近6个小时，直到飞机疑似因燃油耗尽坠毁。在这最后的6个小时里，地面曾两次尝试通过卫星电话呼叫客机，呼叫信号均被SATCOM终端接收并转接至驾驶舱，却“始终无人应答”。此外，地面站若超过一小时未收到客机数据，会自动发送状态请求以确认在线状态，该终端先后回应了5次自动握手信号。 这些握手信号虽不含飞机的经纬度信息，但调查人员利用信号往返所需的时间，计算出了每次传输时飞机与卫星之间的精确距离。这在地球表面投影出了7道同心圆环（弧线）。综合考量燃油消耗率、巡航速度及气象因素后，航迹推算显示最后一次通信最有可能发生在南印度洋的第七条弧线上。由于该海域属于澳大利亚管辖范围，澳大利亚政府随即接管了搜寻主导权。但这片南印度洋海域极为遥远，船只仅驶抵该区域就耗费了整整6天时间。多国机群与舰艇逐步覆盖了超过4,500,000平方公里的海域，客机依然杳无踪迹。 - 卫星通信终端（SATCOM）：连接澳大利亚珀斯地面站 - 链路异常：失联初期断开，3 分钟后在安达曼海上空重新上线握手 - 卫星电话呼叫：地面发起 2 次卫星电话呼叫，已接入座舱但均未获应答 - 自动握手与距离计算：5 次自动状态请求，结合信号延迟推算出 7 条空间距离弧线 - 最终推断：燃油耗尽终点指向南印度洋“第七弧”，海面搜救覆盖超 4,500,000 平方公里 ### [07:17](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=437s) 水下监听、水下信标与留尼汪岛襟副翼 如果飞机撞击海面的力量足够巨大，产生的声音有可能被名为水听器（Hydrophones）的水下监听设备所捕获。调查人员对这一线索进行了调取，发现有四个水下声学监测站确实记录到了一段信号。然而，尽管该声音的时间与方向与最后一次卫星信号基本吻合，但测算出的源头位置并不一致；最终分析认为该声音极大概率只是由地质活动引起的。MH370还配有两个水下定位信标（俗称“水下黑匣子寻标器”），其电池寿命大约为40天。在4月上旬电池寿命将尽的关键窗口期，搜救人员在深达3000米的水下探测到了数次脉冲和频率与信标特征相似的信号。自主式水下航行器随即在信号检出区域连续数周扫描海底，却同样未能发现任何残骸。 直到客机失踪16个多月后，线索才在印度洋的另一侧浮出水面。2015年7月29日，在马达加斯加岛以东的法属留尼汪岛（Réunion），一群正在海滩清理垃圾的人发现了一块长约2米、布满藤壶的金属残片。航空专家很快将其确认为飞机的襟副翼（Flaperon）。通过内部序列号、生产日期等编号比对，官方最终确认该襟副翼属于MH370。尽管留尼汪岛距离搜索区西侧约4,000公里，且事发已有一年有余，但这一漂流轨迹完全符合洋流模拟推演。这是第一件证实MH370在印度洋坠毁的确凿实物证据。 - 水下声学监测：4 个水听站捕获的声音最终被判定为海底地质活动 - 水下定位信标：40 天电池寿命期内曾在 3,000 米深处探测到疑似信号，海底扫描未果 - 襟副翼发现日期与地点：2015 年 7 月 29 日，法属留尼汪岛 - 残片特征：长 2 米，表面布满藤壶，内部零配件编码证实确系 MH370 部件 - 空间跨度：位于澳大利亚西侧搜索区以西约 4,000 公里，洋流漂移模型完全吻合 ### [09:19](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=559s) 残骸物证、海底深潜与主流假说 襟副翼的发现引发了在非洲东南部沿海的大规模海滩搜寻，随后共有至少31件可疑物品被发现并送检。其中包括： - 右机翼外侧襟翼的一块残片 - 两个发动机中其中一个的整流罩碎片 - 前起落架舱门的部分构件 - 垂直尾翼的一部分 - 机载座椅后背头枕显示屏的破损外壳 在送检物品中，有18件被评估为“可能”、“极有可能”或“几乎确定”来自MH370，但仅有3件得到了最终确认，另有11件无法查明归属。所有受检残骸均未发现爆炸痕迹，除了一块未确认构件上有3处微小烧痕外，也没有火灾残留。 与地面搜寻并行的还有卫星遥感：2014年3月的卫星图像曾拍到若干漂浮在南印度洋表面或潜于水下的疑似人造物体，但分辨率不足以分辨标识，多次搜寻也未打捞到实物；终点信号发出后数小时拍摄的卫星图像甚至拍到了疑似航迹云（Contrail），但后经研判只是线状云层的阴影。 由官方主导的海底打捞工作持续数年，排查了约120,000平方公里的海床，最终于2017年初暂停。美国民间打捞公司“海洋无限”（Ocean Infinity）随后接手继续搜索了一年多，同样空手而归。正如纪录片所指出的：“Unless the final resting place of Flight 370 can be located, it may be impossible to determine exactly why it crashed.” 即便如此，外界对失事原因的假说层出不穷： 1. **劫机与非法身份**：失踪当天两名持被盗护照登机的乘客曾引发劫机恐慌，但调查排除了恐怖嫌疑，查明其仅是寻求庇护的难民；另一名具备波音777专业飞行工程知识的乘客也曾受到怀疑。 2. **机载起火**：除客运外，MH370机腹货舱装载了近11吨货物，其中包括一批锂离子电池。这让部分人联想到2010年9月UPS航空6号班机因锂电池托盘起火而坠毁的惨剧。 3. **电气故障起火**：1998年9月瑞士航空111号班机因驾驶舱上方线路起火，烧毁并瘫痪了包括应答机和SATCOM在内的多项航电设备。 在关于火灾的理论中，通讯的瞬间中断与突然航向偏转被解释为机组应对机上火灾的应急处置，两名飞行员可能试图折返马来西亚就近紧急迫降。但令人困惑的是，机组从未执行任何迫降操作；“Instead, Flight 370 kept going and remained aloft for another six hours.” 飞机在空中继续盲目飞行了整整六个小时，将这场悲剧推向了更深不可测的谜团。 ### [13:19](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=799s) 机组人员失能假说与转向疑云 在调查初期，一种广为流传的假说是客舱因突然或逐渐释压导致机组人员陷入昏迷失能。这一设想并非没有历史先例：2005 年 8 月，太阳神航空 522 号班机（Helios Airways Flight 522）因增压系统设置错误导致机组迅速失去知觉，飞机在自动驾驶状态下如同“幽灵航班”般继续巡航飞行了两个多小时，直到燃油彻底耗尽才坠毁。通常情况下，民航飞行员都接受过针对座舱释压的严格训练，一旦出现失压，机上的自动供氧系统会弹出氧气面罩，为飞行员争取宝贵的时间操纵飞机紧急下降到氧气充足的安全高度。然而，马来西亚军方雷达所记录的飞行高度数据却极其反常且前后矛盾。 数据显示，该客机曾一度超越波音 777 的最大升限 15,000 多英尺，随后又在不到一分钟的时间内发生断崖式俯冲，高度骤降 50,000 英尺。波音 777 在物理机动极限上根本不可能完成如此极端的飞行姿态，调查人员随后在飞行模拟机上进行了多次尝试，均以失败告终，这批雷达高度数据因此被官方认定为不准确且不可靠。如果 MH370 确实在 35,000 英尺巡航高度遭遇客舱减压且机组迅速失能，这或许能够解释客机为何能在空中徘徊漫长的时间，但完全无法合理解释随后的航向剧变。飞行模拟测试表明，飞机在最初向左急转弯时的坡度（倾斜角）已经超出了自动驾驶系统的预设限制，这意味着飞机在转弯时必然处于人工手动控制之下。对于其后的数次转向，旁白强调道：“The only other alternative is that the aircraft was in fact under manual control.”（除此以外唯一的可能，就是飞机当时实际上正处于人工操纵之下。） ```mermaid flowchart TD accTitle: Flight 370 Turn Control Analysis accDescr: Analysis of manual vs automatic control during Flight 370 heading changes subgraph S1["最初向左急剧转弯"] A["剧烈倾斜大角度转弯"] --> B["超出自动驾驶限制"] B --> C["必定为人工手动控制"] end subgraph S2["后续航向修正与转向"] D["后续数次路径转向"] --> E{"操纵模式判断"} E -->|"自动驾驶模式"| F["需具专业知识者预先设定航线"] E -->|"手动操纵模式"| G["持续由人工手动控制飞行"] end ``` - 太阳神航空 522 号班机在 2005 年 8 月因失压致全员昏迷，在自动驾驶下飞行超过 2 小时直至燃油耗尽坠毁。 - 马来西亚军方雷达高度记录显示飞机曾超限爬升逾 15,000 英尺，并在 1 分钟内骤降 50,000 英尺，模拟器测试证实波音 777 无法实现此类机动，数据被判定失效。 - 最初的左转动作因坡度过大，断定为人工操纵；后续转向即使依赖自动驾驶，也必须有人为专业编程介入。 ### [15:25](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=925s) 机长模拟机记录与泄密文件 2014 年 6 月下旬，多家媒体披露特别调查已将 MH370 机长列为头号嫌疑人。警方在搜查机长住所时扣押了一台自制飞行模拟机，据称在其中发现了一条终点指向南印度洋的可疑飞行航线。然而，这一重磅消息在当时并未获得马来西亚官方的正面证实，甚至在马来西亚政府于 2015 年发布的厚达数百页的公开中期调查报告中也对此只字未提。直到 2016 年，一份来自马来西亚皇家警察于 2014 年 5 月完成的机密法医取证调查文件被泄露给媒体，外界才确凿得知，这条模拟飞行航线不仅被警方完整恢复，而且早已受到极其详尽的审查。 被恢复的数据实际上由 7 个离散的导航坐标点拼凑而成：2 个位于吉隆坡，2 个位于马六甲海峡，1 个位于孟加拉湾，最后 2 个则深入南印度洋腹地。这些数据提取自模拟软件在事故发生前一个月自动生成并保存的单个文件中。不过，调查人员指出，目前无法确认这 7 个坐标是否出自同一场飞行模拟过程，将它们直接连成一条连贯的自杀预演航线在法医学上并不严谨。马来西亚皇家警察在法医检查结论中明确写道：“No activity captured conclusively indicate any kind of premeditated act pertaining to the incident of MH370.”（捕获的活动均无法确凿证明存在任何与 MH370 事件相关的预谋行为。） 尽管官方结论保持克制，但模拟路线与失联客机推测航线之间惊人的相似性，直接左右了澳大利亚运输安全局的实际搜寻策略。调查人员不得不深入评估两种极端假设：一是有人在燃油耗尽后手动控制客机进行无动力滑翔，从而将航程向外延伸多达 200 公里；二是在燃油耗尽前进行受控海上迫降，提前终止飞行。虽然这两种假设最终被判定为概率极低，但它们极大扩展并改变了深海搜寻区的优先网格。 - 坐标分布详情：吉隆坡（2 个点）、马六甲海峡（2 个点）、孟加拉湾（1 个点）、南印度洋（2 个点）。 - 文件属性：由飞行模拟软件在事件发生前一个月自动记录保存。 - 搜寻修正考量：无动力受控滑翔可使飞机在断油后多滑行 200 公里，而受控迫降则会大幅缩短航程。 ### [17:47](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1067s) 飞行员背景调查与动机谜团 如果确实是机长操纵飞机背离航道，企图在南印度洋极度偏远的绝境坠海，那么他的犯罪动机便成了更大的谜团。机长扎哈里·艾哈迈德·沙阿（Zaharie Ahmad Shah）终年 53 岁，已婚并育有三个孩子，拥有超过 18,000 小时的丰富飞行经验与无懈可击的安全执飞记录。背景调查显示他财务健康，失踪前的每月开销毫无异常；无精神疾病史，近期也未表现出任何生活方式或行为举止上的反常征兆。扎哈里在槟城岛长大，这引发了部分观察者的诗意猜想——飞机向西南方向绕槟城的第二次转弯，或许是他对故乡山海的最后告别。 外界还提出了政治动机假说：扎哈里是马来西亚某民主反对党领袖的热心支持者，而该领袖恰好在航班起飞前数小时被法庭判处五年监禁。另有传闻称其婚姻触礁，但这些流言均被官方调查否认，并遭到了家属的坚决驳斥。最终安全报告中记录的唯一微小异常，是机长在完成最后一次空地语音通话时，漏掉了按标准程序复诵被分配的无线电频率，而他在几分钟前的通话中还完全遵守了这一规程。在互联网上，扎哈里展现出的是一位热情随和、极具专业热忱的资深航迷形象，他在社交媒体发布的家用维修与模拟机科普视频中亲切地向观众致意：“Hi everyone. This is a YouTube video that I've made as a community service.”（大家好，这是我为了社区服务而制作的一段 YouTube 视频。） 相比之下，27 岁的副驾驶法里克·阿卜杜勒·哈米德（Fariq Abdul Hamid）的背景更加无可挑剔。他当时正准备与同为飞行员的女友步入婚姻殿堂，累积飞行时间近 3,000 小时（尽管在波音 777 机型上的执飞时间仅为 39 小时）。法里克同样没有任何经济问题、心理隐患或人际纠纷，与机长之间也无任何矛盾迹象。关于一人作案时另一名飞行员为何未能阻止的疑问，历史上并不缺乏先例：2014 年 2 月埃塞俄比亚航空 702 号班机遭副驾驶劫持案中，副驾驶仅仅是趁机长去洗手间的间隙反锁防弹驾驶舱门，便独自将原定飞往意大利的客机强行改飞瑞士寻求庇护。关于副驾驶法里克最耐人寻味的线索是其手机——泄密机密文件证实了此前流传的传言：当 MH370 低空飞掠槟城上空时，当地一座地面基站曾与副驾驶的 iPhone 5S 手机短暂建立过握手连接。但调查人员澄清这仅仅是手机自动注册基站位置的寻呼信号，并非媒体渲染的拨打电话，至于该关键信息为何在早期公开通报中被隐瞒，至今仍是未解之谜。 - 机长扎哈里：53 岁，已婚有三子，18,000+ 飞行小时，起飞前数小时其支持的反对党领袖被判刑五年。 - 副驾驶法里克：27 岁，即将结婚，近 3,000 小时总飞行经历，其中波音 777 飞行时长 39 小时。 - 埃塞俄比亚航空 702 号班机先例：副机长在机长上厕所时锁闭舱门成功单独夺取飞机控制权。 - 副驾驶的 iPhone 5S 在飞机接近槟城岛时曾被地面信号塔记录到自动定位信号，但并未拨通电话。 ### [21:14](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=1274s) 调查结论、阴谋论与失踪之谜的延续 面对错综复杂的线索，人们陷入了证据与情理的撕裂：一方面，模拟机中恢复的南印度洋坐标散发着令人不寒而栗的预谋气息；另一方面，对两名飞行员生平巨细靡遗的剖析却很难找到任何实质性的人格瑕疵或自杀动机。劫机理论在技术证据链上最为严丝合缝，但核心物证的缺失令一切推论悬于半空。马来西亚政府在 2018 年发布的最终安全调查报告中明确排除了通信中断与航线偏离源于飞机机械或系统故障的可能，认定航向改变以及卫星通信系统（SATCOM）的异常断电与重启属于人为干预操作——有人蓄意切断了系统电源并在一段时间后重新通电引发终端重启。然而，受制于物证匮乏，报告措辞极度克制，自始至终未将事件正式定性为“劫机”，也未给出任何实质性的定论。关于两国官方的共识与困境，旁白指明：“Both the Malaysian and Australian government agree that Flight 370 crashed in the southern Indian Ocean but that the cause is indeterminable without a wreckage.”（马来西亚与澳大利亚政府均一致认同 370 号航班坠毁于南印度洋，但若没有残骸，坠毁原因便根本无法查明。） 在官方搜寻陷入僵局的同时，各类民间理论与阴谋论层出不穷。极端的说法认为客机未曾坠毁，而是在印度洋中心被美军迪戈加西亚海军基地击落，随后的 Inmarsat 卫星信标数据全系多国情报机构伪造掩盖；另有理论称飞机向右大转弯避开雷达向北穿越印度直抵哈萨克斯坦，东非海岸发现的襟翼残骸则是被蓄意丢弃伪造的；甚至有人猜测飞机遭遇了地面远程遥控劫持，但事实上全球没有任何现役商业客机配备允许地面完全接管飞行的系统。 在理性分析层面，部分独立研究团队指出官方的搜寻建模可能存在基础假设偏差——官方默认飞机在转向南印度洋后始终保持恒定速度直线飞行。2018 年初，由法国独立调查员组成的专家团队提出了全新假设：飞行员可能曾试图在圣诞岛（Christmas Island）实施紧急迫降，该尝试失败后客机坠海的位置应比官方锁定的深海搜区更为偏北。尽管失联一周后曾有船只对该偏北海域进行过粗略的表面搜寻，但耗时数年的高精度水下声呐扫描却从未覆盖到如此靠北的纬度。截至视频发布，跨国联合搜寻行动虽已被迫中止，关于重启搜索的讨论却从未止息，MH370 的终局仍被封印在印度洋万米深渊的死寂之中。 - 官方最终报告核心判定：排除机械故障；SATCOM 的失联与重启为手动断电再通电所致；变向为手动输入控制；但未正面定性为“劫机”。 - 涉及的阴谋论：美军印度洋海军基地击落论、哈萨克斯坦降落兼东非海滩抛植残骸论、地面远程无线电遥控劫持论。 - 法国独立调查团队假说：推测飞机曾尝试向圣诞岛备降，最终坠机点远在既定水下声呐搜寻区以北。 ## Notable quotes > [09:19](https://www.youtube.com/watch?v=kd2KEHvK-q8&t=559s) Unless the final resting place of Flight 370 can be located, it may be impossible to determine exactly why it crashed. ## Mentioned 马来西亚航空370号班机 (MH370), 波音 777, 扎哈里·艾哈迈德·沙阿 (Zaharie Ahmad Shah), 法里克·阿卜杜勒·哈米德 (Fariq Abdul Hamid), 马来西亚皇家警察, 澳大利亚运输安全局 (ATSB), 海洋无限 (Ocean Infinity), 太阳神航空 522 号班机 (Helios Airways Flight 522), UPS航空 6 号班机, 瑞士航空 111 号班机, 埃塞俄比亚航空 702 号班机, Inmarsat, iPhone 5S ## Video description On the 8th of March, 2014, Malaysia Airlines Flight 370 vanished during a routine flight between Kuala Lumpur, Malaysia and Beijing, China. The case has since grown into one of the most puzzling mysteries in aviation history. In this video, I examine the findings of the official investigation and explore some of the leading theories. 𝐂𝐫𝐞𝐝𝐢𝐭𝐬, 𝐫𝐞𝐟𝐞𝐫𝐞𝐧𝐜𝐞𝐬, 𝐚𝐧𝐝 𝐦𝐨𝐫𝐞 https://www.lemmi.no/p/the-vanishing-of-flight-370 𝐒𝐮𝐩𝐩𝐨𝐫𝐭 𝐦𝐞 𝐨𝐧 𝐏𝐚𝐭𝐫𝐞𝐨𝐧 https://www.patreon.com/lemmino 𝐒𝐮𝐩𝐩𝐨𝐫𝐭 𝐦𝐞 𝐨𝐧 𝐘𝐨𝐮𝐓𝐮𝐛𝐞 https://www.youtube.com/c/lemmino/join 𝐒𝐨𝐜𝐢𝐚𝐥𝐬 Bluesky: https://bsky.app/profile/lemmi.no https://www.reddit.com/r/lemmino https://www.discord.gg/lemmino [Source](https://www.youtube.com/watch?v=kd2KEHvK-q8)

Source quotes

[9:19] Unless the final resting place of Flight 370 can be located, it may be impossible to determine exactly why it crashed.

Source quotes

[8:25] LEMMiNO: Unless the final resting place of Flight 370 can be located, it may be impossible to determine exactly why it crashed.

Original transcript

[0:34] At Kuala Lumpur International Airport, a Boeing 777 is preparing for departure. [0:50] Malaysia Airlines Flight 370 is a daily passenger flight between Kuala Lumpur, Malaysia and Beijing, China. [1:07] Forty-two minutes past midnight, Flight 370 is given clearance to depart. [1:11] On board are Captain Zaharie Ahmad Shah, First Officer Fariq Abdul Hamid, [1:16] ten cabin crew members, and 227 passengers. [1:40] Less than an hour into the flight, the plane is cruising over the South China Sea at an altitude of 35,000 feet. [1:46] The night sky is clear and the weather is calm. [1:51] Flight 370 is then instructed to signal air traffic control in Ho Chi Minh, Vietnam [1:55] as it is about to enter Vietnamese airspace. [1:58] The flight controller in Kuala Lumpur says good night with no sign that anything should be amiss. [2:29] One minute and forty-three seconds later, the aircraft suddenly vanish from radar screens [2:34] at Kuala Lumpur, Ho Chi Minh, and Bangkok. [2:38] This form of positional tracking depends on a signal being emitted by one of two transponders [2:42] aboard the plane, and so its disappearance would suggest both transponders ceased to function, [2:48] or the system was manually deactivated by someone onboard. [2:53] All subsequent attempts to contact and ascertain the whereabouts of Flight 370 are unsuccessful. [2:59] The aircraft has seemingly vanished without a trace. [3:02] After missing its scheduled time of arrival in Beijing some four hours later, [3:07] Flight 370 is officially declared missing, and in the wake of that announcement, [3:11] the most expensive search effort in aviation history is about to commence. [3:29] The search was initially concentrated around the location of the flight's disappearance [3:33] between the South China Sea and the Gulf of Thailand. [3:37] The search area was soon expanded, however, after the Malaysian military disclosed additional information. [3:42] Unlike the radar system employed by Air Traffic Control, long-range military radar does not rely on transponders [3:48] but use reflectance to track the position of aerial targets. [3:52] A review of the data collected by the Malaysian military revealed that moments after contact [3:56] with Flight 370 was lost, the aircraft had deviated from its scheduled flight path [4:01] with a subtle turn to the right followed by a prolonged turn to the left. [4:05] The aircraft had then flown back towards and across the Malaysian peninsula [4:09] before turning right near the island of Penang. [4:12] It maintained this northwesterly heading until it escaped the radar's coverage. [4:16] Over the next few days, the Strait of Malacca, the Andaman Sea, and the Bay of Bengal [4:21] was scoured by a multinational fleet of aircraft and vessels, but there was no trace of Flight 370. [4:28] Meanwhile, investigators began to analyze the aircraft's satellite communication records. [4:33] Like all modern airliners, Flight 370 was equipped with a satellite communications terminal, [4:38] or SATCOM, to send and received transmissions to and from the ground. [4:44] Prior to departure, the SATCOM terminal had logged on to the satellite network [4:48] and established a connection with a ground station in Perth, Australia. [4:52] That station then maintained a detailed record of all the incoming and outgoing traffic [4:57] between it and Flight 370. [4:59] This is what it contained. [5:01] Prior to the flight's disappearance over the South China Sea, [5:04] everything appeared to be working as intended. [5:07] Then, at some point during this portion of the flight, the SATCOM link was severed. [5:12] For whatever reason, the terminal ceased to respond. [5:16] But three minutes after the flight vanished over the Andaman Sea [5:20] the terminal requested to log back on to the network. [5:23] The SATCOM link was successfully reestablished and was not disrupted again [5:27] until nearly six hours later when the flight is presumed to have crashed due to fuel exhaustion. [5:36] During these final hours, two attempts were made to contact the plane via satellite telephone. [5:41] Both calls were acknowledged by the SATCOM terminal and would've been routed to the cockpit, [5:46] yet they went unanswered. [5:49] The terminal had also responded to five automatic status requests. [5:53] In short, if the ground station had not heard from the aircraft in over an hour, [5:57] it would transmit a signal to confirm the terminal was still online. [6:01] While these transmissions did not contain any information about the flight's position, [6:04] investigators were able to measure the distance between the satellite and the aircraft [6:09] at the time of each transmission based on how long it took those transmissions [6:13] to be sent and received. [6:15] This generated seven rings of possible locations [6:19] from which seven of these transmissions are thought to have originated. [6:24] By taking fuel consumption, speed, and other factors into account, [6:28] flight path analysis indicated the most probable origin of the final transmission [6:32] to be somewhere along this arc in the southern Indian Ocean. [6:37] The search effort shifted accordingly, and as the region fell within the jurisdiction of Australia, [6:42] the Australian government took charge of the operation. [6:45] Over the next few weeks, the search area was progressively refined to account for oceanic drift [6:50] as well as improved estimations of the flight path. [6:53] But this part of the southern Indian Ocean is so remote it took six days just to get there. [7:00] A new fleet of aircraft and vessels gradually covered more than 4,500,000 km2 of ocean, [7:07] but Flight 370 was nowhere to be found. [7:17] If the impact with the ocean had been sufficiently forceful, it was possible the resulting sound [7:22] had been recorded by underwater listening devices known as hydrophones. [7:27] This possibility was investigated, and four hydroacoustic monitoring stations [7:31] had recorded something... [7:44] While the timing and direction of the sound were reasonably consistent [7:48] with the final satellite transmission, the estimated origin was not. [7:52] The sound was in all likelihood caused by nothing more than geological activity. [7:57] Flight 370 was also equipped with two underwater locator beacons [8:01] which had a battery life of some 40 days, and as the deadline approached in early April, [8:06] signals with a pulse and frequency somewhat similar to the signal emitted by the beacons [8:11] were detected at depths of up to 3,000 meters. [8:14] An autonomous submersible then spent weeks scanning the seafloor [8:18] where the signals had been detected, but no wreckage was ever found. [8:25] And nothing would be found until more than 16 months later when a discovery was made [8:29] on the opposite side of the Indian Ocean. [8:33] On the 29th of July, 2015, a group of people was cleaning up a beach in Réunion, [8:38] a small island to the east of Madagascar, when they stumbled upon this [8:42] 2-meter-long metallic object covered in barnacles. [8:46] Aviation experts quickly identified the object as a section of an aircraft wing known as a flaperon. [8:51] Upon closer inspection, internal markings, including dates and serial numbers, [8:57] conclusively ascertained the flaperon belonged to Flight 370. [9:02] Even though Réunion Island is some 4,000 km west of the search area, [9:06] and more than a year had gone by since the flight disappeared, [9:09] the location was consistent with simulations of debris dispersal patterns. [9:13] There was now tangible evidence that Flight 370 had crashed somewhere in the Indian Ocean. [9:19] The discovery of the flaperon prompted numerous searches [9:22] along beaches and shorelines of southeastern Africa, [9:25] and at least 31 additional items of interest have since been recovered and examined. [9:30] Some of these items include: [9:32] A section of the outboard flap from the right wing. [9:36] A piece of cowling from one of the two engines. [9:40] A partial door from the nose landing gear. [9:44] A section of the vertical stabilizer. [9:48] And a mangled casing from one of the embedded headrest monitors. [9:52] Eighteen of these items were identified as either likely, highly likely, or almost certain [9:57] to have originated from Flight 370, whereas only three could be confirmed. [10:02] The remaining eleven could not be identified. [10:05] There were no traces of an explosion found on any of the debris tested [10:08] nor was there any evidence of a fire except for three small burn marks on one of the unidentifiable items. [10:15] The search for debris was further aided by Earth observation satellites. [10:20] Analyses of satellite imagery from March of 2014 uncovered a number of images which appeared [10:25] to feature man-made objects floating on or just below the surface in the southern Indian Ocean. [10:31] However, the images were not nearly sharp enough to resolve any identifiable markings, [10:36] and multiple searches notwithstanding, this debris was never recovered. [10:41] A satellite image taken mere hours after the final transmission, [10:44] also captured what appeared to be a contrail some distance away from the search area. [10:49] A later analysis, however, concluded it was most likely a shadow [10:53] from a somewhat linear cloud formation. [11:01] The underwater portion of the search continued for months and eventually years [11:06] before it was finally suspended in early 2017. [11:09] By which point some 120,000 km2 of seabed had been scrutinized. [11:15] The search effort was then resumed by an American salvage company known as Ocean Infinity, [11:19] but after more than a year of searching, they too came up emptyhanded. [11:23] Unless the final resting place of Flight 370 can be located, [11:27] it may be impossible to determine exactly why it crashed. [11:32] Nevertheless, there has been no shortage of theories. [11:41] On the day of the disappearance, two of the passengers raised suspicion as they had boarded the flight [11:46] with stolen passports which immediately prompted concerns of a hijacking. [11:51] But investigators were unable to link the two men to any terrorist organizations [11:55] and soon determined they had traveled under false identities because they were seeking asylum, [11:59] not due to any nefarious intent. [12:02] Similar suspicions were raised when one of the passengers were identified as a flight engineer [12:06] who might have possessed the necessary expertise to take control of a Boeing 777. [12:11] Apart from the 239 persons onboard, Flight 370 carried nearly 11 metric tons of cargo. [12:18] Among the items listed on the flight manifest was a shipment of lithium-ion batteries, [12:22] which lead some to suspect a fire might have broken out mid-flight. [12:26] For instance, the crash of UPS Airlines Flight 6 in September of 2010 was the result of a fire [12:33] that was ignited by a pallet of lithium-ion batteries. [12:36] Another potential source of ignition would be an electrical malfunction. [12:40] The crash of Swissair Flight 111 in September of 1998 [12:44] is thought to have been caused by a fire within the electrical wiring above the cockpit. [12:48] The fire damaged and disabled multiple avionic systems, including the transponders and SATCOM. [12:55] In the case of Flight 370, the sudden loss of communication [12:58] and subsequent deviation from its scheduled flight path might have been a direct response to a fire. [13:04] The two pilots may have turned back towards Malaysia to attempt an emergency landing [13:08] at the nearest suitable airport. [13:10] But no such attempt was ever made. [13:13] Instead, Flight 370 kept going and remained aloft for another six hours. [13:19] Some have theorized the crew might have been incapacitated [13:22] by a sudden or gradual loss of cabin pressure. [13:25] For instance, when Helios Airways Flight 522 failed to pressurize in August of 2005, [13:31] the pilots quickly fell unconscious, yet the aircraft continued to fly on autopilot for more than two hours [13:37] until it ran out of fuel. [13:39] Airline pilots are of course trained for such an event. [13:42] In the event of cabin depressurization, an automatic system is designed to deploy oxygen masks [13:47] to give the pilots enough time to perform an emergency descent to a more breathable altitude. [13:52] The data recorded by the Malaysian military radar does indeed contain altitude information, [13:57] but it is highly inconsistent. [14:00] In fact, a Boeing 777 is incapable of performing the extreme altitude fluctuations recorded. [14:06] At one point the aircraft exceeded its maximum operating altitude by more than 15,000 feet [14:12] before making a 50,000 feet nosedive in less than a minute. [14:16] Attempts to recreate these maneuvers on a flight simulator were unsuccessful, [14:21] and thus the data was deemed inaccurate and unreliable. [14:26] If Flight 370 did loose cabin pressure at 35,000 feet [14:31] and the pilots were incapacitated before descending to a more oxygenated altitude, [14:35] it might explain why the aircraft remained aloft for as long as it did. [14:40] What is a bit more difficult to explain, however, are these alterations in heading. [14:45] Flight simulations have established the aircraft must have been under manual control [14:50] during the initial left turn as the bank angle, or inclination, of that turn, [14:55] was beyond the limits of the autopilot. [14:58] Subsequent turns, however, could have been either manual or automatic. [15:01] But for the autopilot to have made these course corrections, someone with the requisite knowledge [15:06] must have programmed it to do so. [15:09] The only other alternative is that the aircraft was in fact under manual control. [15:25] In late June of 2014, several news outlets reported that a special investigation [15:30] had identified the captain of Flight 370 as a prime suspect. [15:34] A search of the captain's home had uncovered a flight simulator [15:37] which supposedly contained a suspicious route which ended in the southern Indian Ocean. [15:43] At the time, there was no official acknowledgment that such a route had been recovered, [15:47] and a lengthy public report, issued by the Malaysian government in 2015, [15:51] made no mention of such a discovery. [15:54] Then, in 2016, confidential documents pertaining to a forensic examination [15:59] conducted by the Royal Malaysia Police in May of 2014 was leaked to the media. [16:05] These documents made it clear that such a route had not only been recovered but thoroughly examined. [16:10] Soon thereafter, the Malaysian government confirmed the existence of this simulated flight path [16:14] and this is what it looks like. [16:18] It should come as no surprise that many regard this as damning evidence of premeditation, [16:24] but according to investigators it is not quite so evident. [16:28] The data recovered consists of seven coordinates. [16:31] Two in Kuala Lumpur. [16:33] Two in the Strait of Malacca. [16:36] One in the Bay of Bengal. [16:38] And two in the southern Indian Ocean. [16:41] The data was reconstructed from a file that had been automatically generated and saved [16:46] by the simulation software a month before the incident. [16:49] However, it's not clear whether the coordinates originate from the same flight session. [16:54] In other words, it might not be correct to simply trace a continuous line [16:58] between these seven coordinates as they could be from separate sessions. [17:02] The forensic examination by the Royal Malaysia Police simply concluded: [17:06] "No activity captured conclusively indicate any kind of premeditated act [17:11] pertaining to the incident of MH370." [17:14] Even so, the similarities between this simulated route and the presumed route of Flight 370 [17:19] directly influenced the search operation. [17:22] Australian investigators considered the possibility of someone [17:25] deliberately extending the range of the flight by gliding the aircraft after fuel exhaustion. [17:31] If so, the plane could have traveled an additional 200 kilometers. [17:35] Alternatively, the range could have been reduced by a controlled ditching prior to fuel exhaustion. [17:40] While ultimately deemed unlikely, these two scenarios did affect the search effort. [17:47] If the captain steered Flight 370 off-course with the intention of crashing [17:51] in a remote part of the southern Indian Ocean, his motive is an even greater mystery. [17:57] Zaharie Ahmad Shah was 53 and married with three children. [18:01] He had more than 18,000 hours of flight experience and a spotless track record. [18:06] Investigators found no evidence of financial issues [18:09] and his monthly expenses before the disappearance indicated nothing unusual. [18:13] He had no history of mental illness nor had he displayed any recent changes [18:17] in lifestyle or behavior. [18:20] He was raised on the island of Penang which has led some to speculate [18:23] the flight's second turn to the southwest of Penang was the captain getting a final view of his hometown. [18:30] Some believe a hijacking could have been politically motivated [18:32] as Zaharie was an avid supporter of a democratic opposition leader [18:36] who was sentenced to five years in prison mere hours before Flight 370 took off. [18:41] Others point to unconfirmed reports of marital issues, but this is contradicted by the official investigation [18:47] and disputed by family members. [18:50] The only real inconsistency noted by the final report [18:53] is that the captain failed to repeat the assigned radio frequency during the last verbal communication. [19:06] It would have been standard procedure to repeat the assigned frequency [19:10] as the captain had correctly done a few minutes prior. [19:20] Whether this omission is indicative of anything but a mistake is anyone's best guess. [19:27] By all accounts, Captain Zaharie was an affable and well-respected pilot [19:31] who was passionate about aviation as evident by the photos and videos he shared on social media. [19:37] Captain Zaharie: Hi everyone. This is a YouTube video that I've made [19:42] Captain Zaharie: as a community service. [19:47] The copilot was found to be even less conspicuous. [19:50] Fariq Abdul Hamid was only 27 and due to marry a fellow pilot. [19:55] He had nearly 3,000 hours of flight experience, although only 39 hours in this type of aircraft. [20:01] Much like Zaharie, Fariq had no financial, mental, or interpersonal issues of note, [20:06] nor was there any evidence of conflict between the two of them. [20:10] Some question the plausibility of a pilot-instigated hijacking [20:13] due to the apparent lack of interference by the other pilot. [20:17] Well, when Ethiopian Airlines Flight 702 was hijacked by the copilot in February of 2014, [20:23] he did so by merely waiting for the captain to take a bathroom break [20:26] before locking the cockpit door behind him. [20:29] The copilot was then free to divert the Italy-bound flight to Switzerland to seek asylum. [20:35] The only noteworthy piece of evidence in regards to the copilot of Flight 370 is his phone. [20:41] You see, when the confidential documents were leaked, they also confirmed another long-circulated rumor. [20:47] Namely, that a cellphone tower had briefly established a connection with an iPhone 5S [20:51] belonging to the copilot as Flight 370 approached the island of Penang. [20:56] According to investigators, it was not a phone call, as has been widely reported by the media, [21:01] but merely an automatic location signal. [21:04] Why this information was omitted from public reports, we may never know. [21:14] So what is one to make of all of this? [21:16] On the one hand, the simulated flight path seems suspicions. [21:20] On the other, it is difficult to cast any substantial doubt on either of the two pilots' character. [21:26] It is equally difficult to deny a hijacking is consistent with the available evidence. [21:31] Then again, we're missing some quite major and literal pieces of evidence. [21:36] The final report issued by the Malaysian government in 2018 could not attribute the loss of communication [21:42] nor diversion of Flight 370 to a malfunction. [21:46] Instead, it is believed that someone manually manipulated the aircraft and its systems. [21:52] For instance, investigators believe SATCOM was manually disabled [21:56] by a sudden and prolonged interruption of power. [21:59] Then, once power was restored, the terminal simply rebooted. [22:04] Likewise, the alterations in heading are believed to be the result of manual inputs. [22:09] With that being said, the uncertainty of these findings are repeatedly emphasized [22:13] due to the limited evidence available, and the report does never explicitly state the flight was hijacked. [22:20] In fact, no real conclusion is reached. [22:23] Both the Malaysian and Australian government agree that Flight 370 crashed in the southern Indian Ocean [22:29] but that the cause is indeterminable without a wreckage. [22:33] The location of which has managed to elude some of the foremost aviation experts in the world [22:38] as well as an impressive arsenal of cutting edge technology for more than half a decade. [22:43] Authors, aviation experts, and independent investigators have all chimed in to offer their own [22:49] thoughts and theories as to the nature of the crash and the location of the wreckage. [22:54] Some believe there was no crash but that the aircraft was shot down by an American naval base [22:59] in the middle of the Indian Ocean. [23:01] The satellite transmissions where then supposedly forged as part of a massive cover up. [23:06] Others believe the aircraft turned right towards India and traveled as far north as Kazakhstan [23:11] completely undetected. [23:13] Debris was then supposedly planted along shorelines of southeastern Africa [23:17] as part of a massive cover up. [23:20] Another theory suggest the aircraft was remotely hijacked and controlled by someone on the ground. [23:26] While Boeing and other companies have experimented with technology [23:29] that would allow for an aircraft to be remotely controlled, [23:32] no commercial airliner is known to be outfitted with such a system. [23:39] On the less conspiratorial side, the assumption that Flight 370 flew in a straight line [23:44] and at a constant speed after turning left towards the southern Indian Ocean [23:48] might simply be incorrect. [23:50] In early 2018, a French team of independent investigators proposed an alternate flight path [23:57] whereby an attempted landing on Christmas Island lead to a crash site much further north [24:02] than the region identified by the official investigation. [24:06] While a surface search of this area was conducted about a week after the disappearance, [24:11] the underwater phase never reached this far north. [24:20] As of the making of this video, the search operation has been suspended, [24:24] but there have been talks of potentially resuming the search. [24:28] For now, it seems, the vanishing of Flight 370 will remain a mystery.