Listening now to an NCAA women's basketball game, Arkansas Razorbacks at SMU Mustangs broadcast live over Tunein. I'm counting on this game to help me relax and unwind from a rather stressful afternoon trying in vain to access my social security account online.

And the adventure continues.

Introduction

In my previous post “Was Flight MH370 Teleported?”, I broke down two viral videos that appear to show MH370 being surrounded by glowing orbs before vanishing in a flash of light. Whether you believe those videos are real or fake, one thing is clear: they sparked renewed interest in alternative theories about what happened to Flight 370.

But here’s the thing: whether those videos are real or not, there should be physical evidence. An event violent enough to make a Boeing 777 disappear or crash would almost certainly generate acoustic signatures detectable by underwater sensors.

The Comprehensive Nuclear-Test-Ban Treaty Organization (CTBTO) operates a network of highly sensitive underwater hydrophones throughout the world's oceans. These hydrophones are designed to detect nuclear explosions, but they can also pick up aircraft impacts, underwater explosions, and other violent events.

So what did those hydrophones record on March 8, 2014?

The answer is complicated. They recorded something. But more importantly, they recorded nothing during a critical 25-minute window at the station closest to Diego Garcia.

The Players: CTBTO Hydrophone Stations

The CTBTO operates hydroacoustic monitoring stations throughout the Indian Ocean. Three are particularly relevant to MH370:

Station	Location	Code
HA01	Cape Leeuwin, Western Australia	H01W
HA08	Diego Garcia, British Indian Ocean Territory	H08S/H08N
HA04	Crozet Islands, France	H04S

Each station consists of three hydrophones arranged in a triangular configuration, allowing researchers to determine both the bearing and approximate distance of acoustic events.

Diego Garcia is the location of HA08. It is also a remote coral atoll hosting a major U.S. military installation, Naval Support Facility Diego Garcia, which is shrouded in secrecy. The island has a 12,000-foot runway capable of handling any aircraft in the world.

Remember from Part 1: the coordinates embedded in the “satellite” video are approximately -8.834301, 93.19492, which places the supposed event south of the Nicobar Islands. Diego Garcia sits at approximately 7.3°S, 72.4°E. The distance between these two points is roughly 2,300 km.

Anomaly #1: The 25-Minute Data Gap

What Happened

At 03:07 UTC on March 8, 2014, all three hydrophones at the Diego Garcia station (HA08s) simultaneously stopped recording. They remained offline for exactly 25 minutes.

This is documented in a peer-reviewed paper by Dr. Usama Kadri of Cardiff University, published in Scientific Reports (Nature):

“A fifth signal appears at 3:07... This signal probably indicates restarting the system after it was shutdown for 25 minutes, i.e. there is missing data in these specific CTBTO recordings.”

Kadri, U. (2019). Effect of sea-bottom elasticity on the propagation of acoustic-gravity waves from impacting objects. Scientific Reports, 9, 912.

Why This Matters

Dr. Kadri explicitly addresses the suspicious nature of this gap:

“Due to the sensitivity of the recorded data, it is unlikely that the three hydrophones on HA08s had a simultaneous technical failure and the reason behind the shut down is to-date unknown.”

He then offers a possible explanation:

“A violent nearby activity (including impact, explosion) could have resulted in a shutdown of the system.”

Let that sink in. A scientist publishing in one of the world's most prestigious journals is stating on the record that:

1. A simultaneous failure of all three hydrophones is “unlikely”
2. The shutdown remains “unexplained” by the CTBTO
3. A violent nearby event, such as an aircraft impact or explosion, could cause such a shutdown

The Timeline and the Videos

The official narrative places MH370's final satellite communication at 00:19 UTC on March 8, 2014, with the crash estimated to have occurred shortly after, when the plane ran out of fuel.

Here is where it gets interesting. If you plot MH370's trajectory based on the coordinates in the video (-8.834301, 93.19492), the plane would have been in that area sometime between 00:30 and 01:30 UTC. At ~2,100 km distance, the primary acoustic signal would reach Diego Garcia in roughly 10-25 minutes depending on propagation path (sea-bottom waves travel faster at ~3,350 m/s; water column waves at ~1,500 m/s). That means any acoustic signature from the event would have been recorded by Diego Garcia's hydrophones sometime between 01:10 and 01:55 UTC – well before the 03:07 data gap.

Time (UTC)	Event
18:22, March 7	Last radar contact with MH370
00:19, March 8	Final satellite handshake (Final satellite handshake (crash estimated shortly after))
~00:30-01:30, March 8	Estimated time at video coordinates (if direct flight from last radar)
01:58, March 8	Signal HA_32 detected at Diego Garcia (military bearing)
03:07, March 8	All three Diego Garcia hydrophones go offline
03:32, March 8	System comes back online
03:47-03:55, March 8	Three signals detected at nearly identical bearings (~170°)

So what happened at 03:07? If the acoustic signal had already arrived and been recorded around 01:30-02:00 UTC, the data gap doesn't represent missing evidence – it represents evidence that may have been deleted. You don't preemptively shut down a recording system before incriminating data arrives. You shut it down after you realize what's been captured. The 25-minute window – just enough time to review and scrub recordings – looks less like a technical failure and more like a cleanup operation.

The data gap starts at 03:07 UTC. Right in the middle of that window.

Coincidence?

Anomaly #2: Diego Garcia Data “Dismissed” as Too Noisy

The Convenient Excuse

When the U.S. Los Alamos National Laboratory (LANL) analyzed CTBTO hydrophone data for MH370, they focused almost exclusively on the Cape Leeuwin (HA01) station. The Diego Garcia data? Dismissed.

From the official LANL report:

“Analysis of the data from these stations shows... large amplitude repeating signals at H08 that obscure any possible arrivals.”

Stead, R.J. (2014). Seismic and hydroacoustic analysis relevant to MH370. Los Alamos National Laboratory, LA-UR-14-24972.

The “noise” was attributed to seismic survey ships operating in the region. This explanation has been accepted uncritically by most researchers.

Dr. Alec Duncan's Assessment

Dr. Alec Duncan of Curtin University, who led the Australian acoustic analysis effort, also found the Diego Garcia data “unusable”:

“Duncan also analysed data from the other [station], off Diego Garcia island in the middle of the Indian Ocean, but found nothing. The data were too polluted by noises from seismic surveys, he says.”

Butler, D. (2014). Sound clue in hunt for MH370. Nature, 510, 199-200.

The Signal That Pointed Northwest

Here is what makes this dismissal suspicious. Duncan did find a promising signal at Cape Leeuwin, one that pointed to a location northwest of the official search area:

“The sound is believed to have originated somewhere along a strip running to the northwest of the Indian Ocean. That is out of the range of the current search.”

Curtin University's refined location estimate (September 2014) placed the signal origin at 2.11°N, 69.31°E, west of the Maldives, much closer to Diego Garcia than to the 7th arc search area.

This location is roughly 1,100 km from Diego Garcia. And it is within the general region suggested by the video coordinates.

This finding was dismissed as “inconsistent with other data about aircraft position,” meaning the satellite handshake data that forms the entire basis for the southern search.

Anomaly #3: Military Activity Detected During the Critical Window

What the Hydrophones Recorded

Kadri's 2019 paper documents military activity detected by the Diego Garcia hydrophones during the critical timeframe:

“Analyses of signals recorded at station HA08s... were more challenging, partially due to disturbances in the recordings that are believed to have been caused by military action in the region.”

The military signals were detected at two specific bearings:

• 219.2° from HA08s (southwest toward Mauritius/Madagascar)
• 309.7° from HA08s (northwest toward Maldives/India)

These signals were recorded “intermittently” between 23:00 UTC on March 7 and 04:00 UTC on March 8, precisely the window when MH370 would have been in the area.

The Signals from Table 3

Signal	Time (UTC)	Bearing	Distance	Location	Notes
HA_30	11:57 (Mar 7)	247.4°	585±276 km	9°34'S, 67°36'E	Closest to Diego Garcia
HA_31	12:11 (Mar 7)	170.9°	2,300±250 km	28°08'S, 76°20'E
HA_32	01:58 (Mar 8)	241.3°	2,860±900 km	19°05'S, 48°32'E	Within military bearings
HA_34a	03:47 (Mar 8)	170.9°	—	—	Immediately after restart
HA_34b	03:50 (Mar 8)	173.0°	—	—	Immediately after restart
HA_34c	03:55 (Mar 8)	170.9°	—	—	Immediately after restart

Notice the sequence immediately after the system came back online: three signals at nearly identical bearings (~170°) detected within 8 minutes. What did the hydrophones capture the moment they resumed recording?

Kadri notes:

“Note that bearings of signals HA30 and HA32 fall within the military action bearings, so it is also possible that the signals are associated with the military action.”

Connecting to the Videos

In Part 1, I discussed how the videos appear to show military surveillance footage, specifically what looks like Gorgon Stare imagery from an MQ-9 Reaper drone. The second “drone” video shows the same event from a different angle.

If the U.S. military was operating surveillance drones in that area, and if something happened to MH370 that they witnessed (or caused), the “military action” detected by the hydrophones could be related.

Anomaly #4: Cocos Keeling Infrasound Data Never Released

The Silent Witnesses

Cocos Keeling Island sits in the Indian Ocean between the Maldives and Australia. It hosts an array of eight infrasound recorders (station IM.I06) that were continuously collecting data during MH370's disappearance.

This data has never been made public.

From 370Location.org:

“There is an array of eight infrasound recorders at Cocos Keeling West Island that was continuously collecting data during the flight of MH370. That data has been unavailable to the public.”

Two days after MH370 disappeared, the head of the CTBTO noted during a press briefing that their infrasound monitoring stations “would be most suitable for detecting an explosion or impact of the aircraft.” One day later, they released a report claiming no infrasound detections were found.

The Convenient Data Cutoff

In 2017, the CTBTO began releasing infrasound and hydrophone data to public seismic networks, including data from prior years.

For the Cocos Island array, that dataset starts on April 4, 2014.

MH370 disappeared on March 8, 2014.

The publicly released data begins exactly 27 days after the plane vanished. Everything before that remains classified.

The Time Zone Error That Invalidated the Analysis

In May 2014, Lawrence Livermore National Laboratory (LLNL) produced a poster report examining whether the Cocos Island infrasound array could detect aircraft. Their approach was sound: check whether the twice-daily A320 flights to and from Cocos Island airport were detectable on the infrasound array located just a few kilometers from the runway.

They found no infrasound events matching the known aircraft activity. This negative finding became the basis for dismissing further inquiry into the Cocos data.

There was just one problem: they made a time zone error.

From 370Location.org's detailed analysis:

“Ultimately, a simple time zone error flawed the analysis. While the poster listed the correct offsets for local time, UTC+6:30 for Cocos CCK and UTC+7:00 for Christmas CXT, those offsets were erroneously added instead of subtracted from local time to get UTC. The result was that the infrasound was being examined for expected flight traffic in the middle of the night when the airport was closed.”

Let that sink in. The analysis that was used to dismiss the Cocos Island infrasound data was looking at the wrong time window entirely. They were searching for aircraft signatures at 2 AM when no planes were flying.

Terminal departures from Cocos are scheduled for 13:43 and 15:59 local time, which is 07:13 and 09:29 UTC. The LLNL poster incorrectly listed these as 22:37 and 00:50 UTC, off by nearly 12 hours.

The Array Can Detect Aircraft

Independent researcher Ed Anderson later proved that the Cocos Island infrasound array absolutely can detect jet aircraft. Using publicly available data from April 2019 (after the March 2014 data was conveniently excluded), he demonstrated successful detection of commercial flights:

“This is firm confirmation that the Cocos Island infrasound array is capable of picking up jet traffic details.”

The 2019 analysis showed the array detecting:

• Jet engine throttle-up on the runway
• Aircraft movement down the runway
• Takeoff bearing and heading
• Approaches from 25 km away

The Signal at 22:22:22 UTC

Here is where it gets interesting. Despite the flawed official analysis, independent examination of available seismometer data from Cocos Island (station II.COCO) revealed something:

“The seismometer shows that there were no other significant acoustic events there besides the 22:22:22 candidate during the time between the fourth and fifth pings.”

A higher resolution sample from one of the infrasound sensors published in the LLNL poster shows a signal peak at 22:46:40 UTC.

This timing closely matches when MH370 would have crossed near Cocos Island if it flew toward Diego Garcia rather than south toward the 7th arc.

From 370Location.org:

“The Cocos Island infrasound array appears to be perfectly viable for detecting a flyby and confirming the nature of the event detected by the island seismometer.”

Why This Matters for the Videos

Remember: if MH370 flew toward the coordinates shown in the videos (-8.834°S, 93.195°E), it would have passed near Cocos Keeling Island. The flight path from last radar contact to the video coordinates runs almost directly over Cocos.

The infrasound array would have detected the aircraft's engine noise. A Doppler shift in the signal would indicate direction of travel.

If the raw infrasound data from March 7-8, 2014 showed MH370 heading northwest toward Diego Garcia rather than south toward the 7th arc, it would directly contradict the official narrative.

Instead, we have:

• Data conveniently classified until April 4, 2014
• An official analysis invalidated by a basic time zone error
• Independent proof that the array CAN detect aircraft
• A suspicious signal at 22:22-22:46 UTC that was never properly investigated

Source: 370Location.org: Cocos Island Infrasound May Be Key to Locating MH370

The Pattern of Suppression

When you step back and look at the acoustic evidence holistically, a troubling pattern emerges:

Data Source	Status	Official Explanation
Diego Garcia (HA08) hydrophones	Dismissed	"Too noisy from seismic surveys"
25-minute data gap	Unexplained	None provided by CTBTO
Cocos Keeling infrasound	Classified	"No evidence found" (methodology flawed)
Crozet Islands (HA04)	Never Analyzed	Not addressed
Military activity signals	Unexamined	Attributed to exercises
Curtin University signal	Dismissed	"Inconsistent with satellite data"

Every piece of evidence that could point toward Diego Garcia has been either dismissed, classified, or left unexplained.

The “Javanomaly”: A Strong Unexplained Signal

Independent researchers have identified additional signals that warrant investigation. One of the most compelling is what 370Location.org calls the “Javanomaly”:

“A very strong MH370 candidate signal was reported here a year ago, arriving at the Diego Garcia H08 hydrophone array from the direction of Java. The T-wave arrival is far stronger than a later M4.4 quake near Java and four times stronger on local seismometers than a nearby M4.1 quake.”

What makes this signal suspicious:

“Despite the stronger signals, this event was not included in earthquake catalogs like the others. Analysis of nearby seismometers places the origin as 8.36S 107.92E directly on the 7th Arc at 1:15:18 UTC, almost an hour after the expected impact time.”

Source: 370Location.org: A Strong Anomalous Acoustic Event on the Seventh Arc near Java

Tying It Together: What the Hydrophone Data Means for the Videos

If the videos fromPart 1 are real, they show MH370 being surrounded by orbs and disappearing in a flash of light. Such an event would generate multiple types of acoustic signatures:

1. The initial event: Whatever energy was released when the orbs activated would create a pressure wave
2. Aircraft impact/displacement: The sudden movement or destruction of a 200-ton aircraft would generate acoustic signals
3. Possible implosion: If parts of the aircraft sank to depth, implosion of pressurized compartments would create additional signals

The timeline fits uncomfortably well:

Theoretical Event	Time (UTC)	Supporting Evidence
"Teleportation" event at video coordinates	~01:00-01:30	Video timestamp, flight path calculations
Acoustic signal recorded at Diego Garcia	~01:15-01:55	2,100 km at 1,500-3,350 m/s
Signal HA_32 detected at Diego Garcia	01:58	Detected at military bearing (241.3°)
Diego Garcia hydrophones shut down	03:07	25-minute gap begins - data scrubbed?
System restarts	03:32
Three signals at ~170° bearing	03:47-03:55	Captured immediately after restart

The acoustic evidence would have already been recorded by the time the system went offline. The data gap occurs not when evidence was arriving, but potentially when it was being erased.

What Would Prove or Disprove This Theory?

Several pieces of evidence could definitively address the connection between the videos and the hydrophone data:

1. The Missing 25 Minutes

The CTBTO should release whatever diagnostic data exists from the HA08s station between 03:07 and 03:32 UTC. If the system was truly “shutdown” by a violent event, there should be evidence of what caused it.

2. Cocos Keeling Infrasound Data

If MH370 flew toward the video coordinates (near the Nicobar Islands), infrasound would have detected it. Release the data.

3. Full Diego Garcia Recordings

Not just the data that was deemed “too noisy,” but all recordings from 23:00 March 7 to 04:00 March 8, with proper signal filtering applied.

4. HA04 Crozet Islands Cross-Reference

A third station could triangulate any signals and provide much more precise location data. This analysis has apparently never been done.

5. Raw Satellite Footage

If the U.S. military was operating Gorgon Stare surveillance in the area (as the videos suggest), they have the original, uncompressed footage. Release it.

Conclusion: The Sound of Silence

The hydroacoustic evidence surrounding MH370's disappearance is characterized not by what was detected, but by what was silenced.

In Part 1, I laid out the evidence for and against the authenticity of the videos showing MH370 surrounded by orbs. I noted the extraordinary technical details, the suspicious “debunks” that seemed planted, and the connections to Diego Garcia.

Now we have another piece of the puzzle: 25 minutes of missing data from the hydrophone station closest to Diego Garcia, occurring exactly when acoustic evidence of a violent event would be expected to arrive.

Dr. Kadri's peer-reviewed research explicitly states that the simultaneous shutdown of all three hydrophones is “unlikely” to be a technical failure. He suggests a “violent nearby activity (including impact, explosion)” could cause such a shutdown.

The question is not whether the evidence exists. The question is why it has been systematically dismissed, classified, or erased.

If those videos are real, if MH370 was intercepted by some form of advanced technology, the hydrophone data gap is exactly what you would expect. Not evidence of what happened, but evidence of a cover-up.

Ten years after MH370 vanished, 239 families still have no answers. Perhaps those answers lie not in the depths of the southern Indian Ocean, but in the 25 minutes of silence from a hydrophone station in the shadow of a secret military base.

---

Sources & Further Reading

Primary Scientific Sources

1. Kadri, U. (2019). Effect of sea-bottom elasticity on the propagation of acoustic-gravity waves from impacting objects. Scientific Reports, 9, 912.

   • DOI: 10.1038/s41598-018-37626-z
   • Direct link: https://www.nature.com/articles/s41598-018-37626-z

2. Kadri, U. (2024). Underwater acoustic analysis reveals unique pressure signals associated with aircraft crashes in the sea: revisiting MH370. Scientific Reports, 14, 10102.

   • DOI: 10.1038/s41598-024-60529-1
   • Direct link: https://www.nature.com/articles/s41598-024-60529-1

3. Stead, R.J. (2014). Seismic and hydroacoustic analysis relevant to MH370. Los Alamos National Laboratory, LA-UR-14-24972.

   • OSTI: https://www.osti.gov/biblio/1136454

4. Stead, R.J. (2014). How Common are Noise Sources on the Crash Arc. Los Alamos National Laboratory, LA-UR-14-28179.

   • OSTI: https://www.osti.gov/biblio/1160107

5. Butler, D. (2014). Sound clue in hunt for MH370. Nature, 510, 199-200.

   • Direct link: https://www.nature.com/articles/510199a

Independent Research

1. 370Location.org – Flight MH370 Acoustic Location
   • Main site: https://370location.org/
   • Javanomaly analysis: https://370location.org/2018/02/a-strong-anomalous-acoustic-event-on-the-seventh-arc-near-java/

---

Read Part 1: Was Flight MH370 Teleported?

---

Check my other posts

Why Is Skinny Bob Still Blinking at Us?

A look at the “Skinny Bob” alien footage, where I break down why it's so strangely convincing, what's likely fabricated, and why the videos still spark debates years later.

Did a 2024 Forgotten Languages Post Foreshadow The Nordic Drone Crisis?

A breakdown of a cryptic Forgotten Languages post about a supposed drone strike simulation off New Jersey, and how its details later echoed the real drone shutdowns across Denmark, Norway, and Germany.

Carlos Díaz: The UFO with the Glowing Molten Skin

A detailed look at the Carlos Díaz “Ships of Light” UFO: the molten amber craft he photographed over Ajusco, how it seemed half-machine, half-alive, and why the visuals still rank among the most striking UFO images ever captured.

Best UFO Photos of All Time

A collection of some of the best and most famous UFO photos ever taken.

Follow me on X for more updates.

Tried to go on my usual morning walk today, but it was too damn cold. Made it to my car, sat in it to try and warm myself up for a bit, then it was back to the office. No walking on the trails around the office today. Outside temp was not even below 40F; it was 47F. But damn 10 mph wind gusts made it feel way colder. My vest was not enough to keep me warm. Should have brought a full jacket.

On the bright side, the Screamo mix that Spotify generated today is fire!

Going back to the car I sat in today. It was the Mazdaspeed3 that I drove to work today. I also drove it to work last Monday and Tuesday. I've noticed I've been driving it to the office more than the Mazda 3 Turbo. It's not that it's a better car than the newer Mazda 3; the Mazda 3 is a better daily driver. It's simply because I don't want to rack up miles on the newer car, especially when the Speed3 is still perfectly capable of driving me to work and back.

The Speed3 might already have 145K miles on it, but it still drives well, still looks good (from afar LOL) and can still haul ass when I need it to.

The Mazda 3 on the other hand just crested 16K miles and I'm cringing already. I want it to gain miles slower than the current rate it is gaining miles at. I'm trying to save it for longer drives like road trips, and for drives where I know I will be stuck in stop and go traffic. It doesn't help that the wife tries to drive it every chance she can get. She is literally addicted to driving this car because of how good it drives, the swell of low-end torque and the ease at which it can pass other cars on the highway. Oh and did I mention, there's no wheel spin when I floor it from a stop. Not even in this colder and sometimes rainy weather.

I understand that to some, this might seem like a luxury. Every morning I get to pick which car I want to drive to work in. In a sense, it is a luxury to have that option. On the other hand, none of the two cars I have are “luxury” cars. One is an old beater that happens to be a hot-hatch from a bygone era. — (Now that's a blog post for another day, making your own beater car.) — The other, is just a Mazda 3 with a turbo engine, though the interior is really quite... I'm not gonna say luxurious, but I will say... premium.

Regardless if its a luxury or not, I can tell you how I achieved such a feat. I pay off my cars and keep driving them, instead of trading them in for a new one right after paying it off. You save so much money by not having a monthly car payment. And if you save enough of that money, you can then buy another car in the future, and still keep your old car as backup.

#Journal #Cars #Mazda #Mazdaspeed3 #Mazda3Turbo #PersonalFinance

Here are some quick takeaways of some books I read this year.

Million Dollar Weekend – Noah Hagan

• Nice lessons: Always ask for what you want. Quantity > Quality. Visualize. A nice book to be put into a productive gear.

Sapiens – Yuval Noah Harari

• Sample theses: Physical communities are being replaced by virtual communities. Natural religions (nationalism, capitalism, moral frameworks, etc.) are replacing traditional deities. Real peace is the implausibility of war.
• In the last chapter, Harari describes Sapiens as god-like, but also perpetually dissatisfied and irresponsible. It’s less of a history textbook and more of a book using history to justify commentary on human behavior.

Zero to One – Peter Theil

• This is a book for the contrarian. What important truth do very few people agree with you on? Some main ideas are (1) Competition is bad. (2) Start small and don’t disrupt. (3) The power law – hedge in winners.
• I have reread this book once every few years. I can think about recent changes (AI, tech companies, competition, etc.) within the context of some simple ideas provided by this book.

The Best American Essays 2023 – Vivian Gornick

• This is basically an anthology of eclectic voices (e.g. a doctor treating an unusually unstable drug addict, a young adult in maximum security prison turned writer due to solitude, a girl finding out her mom is gay at the very end of her mom’s life through old photos, etc.)

Creating Database and Tables! This one is a bit “harder” because I have to plan the data model correctly. For the auth, I can reuse the Supabase auth tables, so the focus will be on the tables.

For the application I need 3 tables and a many-to-many table. For now this is enough to get the app going.

After creating the tables in the Supabase UI, I used the Supabase CLI to generate the types and applied them. Additionally, I added some API functions to be more prepared for the next day.

That was Day 04. ✅

---

62 of #100DaysToOffload
#log #AdventOfProgress
Thoughts?

The silver full moon shines even through the clouds; illuminating them on the brownish blue night sky.

!!

And the frozen slush of molten dirty snow is blank and slippery — against the sky, however, it looks like it glimmers with gold.

And in the car it’s warm. And the dogs are warm.

And I have my family with me.

My whole world in this dark warm car.

Isn’t that something?

#poetry