To locate missing flight MH370, I'm analyzing acoustic data. Detected sounds may be debris sinking right on the 7th Arc off Java, matching all factual evidence.
@VirginRadioUK Reanalysis of hydrophones and seismometers pinpoints a crash site directly on the 7th Arc, 39 miles off the coast of Java. Fitting all of the hard evidence, the anomalous loud noise is consistent with a large section of sinking #MH370 hitting the seabed.
https://t.co/zjjuozW8RQ
Lyne says he plans to publish his latest paper for peer review, but I can provide that here. Of 5,000 particles in his drift model, only a dozen outliers passed near Reunion. None arrived early and most arrived late. Another dozen matched the moist towelette. That is after tuning for Stokes drift and windage parameters. Geomar already showed that minor changes in those parameters can have the debris arriving from anywhere in the entire Indian Ocean.
No MH370 debris was found in Australia, even though beach cleanup https://t.co/2tunufjqOH and AMDI search volunteers were alerted to watch for #MH370 debris. The official stance on a single moist towelette is that it is a "common item with no unique identifier," that could not be conclusively or forensically linked to the missing aircraft.
Any new drift analysis should include at least the second piece of debris found, the Rolls Royce engine cowling fragment "Roy" found at Mossel Bay, South Africa in December, 2015. It traveled the farthest and fastest of any MH370 debris found. Its exclusion implies that it is not compatible with Lyne's drift analysis and starting point.
Lyne mentions that a UFL analysis of flaperon barnacles during drift indicated a warming period of drift in Feb 2015. It did not. The original data came from a 2016 French O2 isotope study that gave no timeline, and showed that growth began at the warm end of the barnacle's 18-26 C reproductive range. The UFL report suggests that the barnacles colonized the drifting flaperon en route in February, 1,500 km east of Reunion. Sea surface temperatures at Lyne's starting point were around 20 C, optimal for growth. He has no explanation for why there was no colonization in favorable conditions for 11 months.
Recently, detailed photos of the flaperon at Reunion show that young adult barnacles on the inboard leading edge were growing on top of deep abrasions that wore off the screw tops. That means the flaperon beached months before it was discovered. The growth temperature curves also match the sea surface temperatures from May through July, 2015. That gives the timeline for arrival at mid-April 2015. This is 14 weeks before it was discovered, and incompatible with Lyne's drift claims.
Lyne is also claiming that the 7th Arc location is incorrect because nothing was found, and that any scientific studies based on the 7th arc must be flawed. That's not how the scientific method works. He also says that experts incorrectly "regurgitate" other drift models in their investigations.
My area of focus has been the MH370 acoustics, where Lyne has made many past claims that are nonsensical. Like this drift study that tries to combine a confirmed debris find with dubious one in the opposite direction, he has in the past tried to combine every reported detection of a hydrophone signal in the Indian Ocean as arriving from his source location through convoluted and impossible paths, even when those detection reports have been debunked. His counter to the debunking is to dismiss a viable acoustic candidate in deep 3,400 m water on the 7th Arc 67 km off the coast of Java as dynamite fishing, when the original report studied events in water 50m deep which do propagate to hydrophones. He has published dozens of MH370 articles claiming an exclusive find, even though research ships have been to the Diamante Deep since 2014.
Lyne continues in this article claiming that the pilot was a brilliant mastermind intent on hiding the plane in the deepest remote location. He challenges his readers with puzzles and riddles. None of that was in the personality profile or computer forensics of the pilot, who instead shared various hobbies on Youtube, including leaky window seal repair and how to check the refrigerant in a heat pump to save money.
The @PopMech report you mention says nothing about the hydrophones. Their July #MH370 article did, but it pointed to an inconclusive 2016 report that Jeff Wise hadn't seen, not newer findings.
Previous hydrophone analyses saw a strong event near Java but dismissed it as a quake. Careful seismic analysis pinpoints an epicenter directly on the 7th Arc at 8.36S. The timing and depth of the source point to the seabed impact of a large section of sinking MH370, not a surface impact.
There is also new photo evidence on the flaperon barnacles, consistent with the Java site. See the current Independent Group blog post for details:
https://t.co/lX30BH63aB
p.s. Story corrections.
The turn considered too tight for autopilot was the initial turn at IGARI when all the signals dropped but it was still seen on primary radar, not the FMT (Final Major Turn) south after leaving radar. We won't know exactly when that turn happened or how tight it was until we find the flight Data recorder.
p.p.s. You say the ocean at the past search sites is "Unforgiven". I think you meant "Unforgiving". The ocean isn't asking for forgiveness, and it doesn't grant it.
The last @PopMech story on #MH370 was written by Jeff Wise about a new acoustic clue that could "Radically Change" the search. You also refer to Victor Iannello and Independent Group where the recent search zones were defined. Yet, you ignore Victor's current recommendation since March that the next search should include the very specific Java acoustic candidate directly on the 7th Arc at 8.36S.
https://t.co/lX30BH63aB
Your story before that was about the flaperon barnacles. Yet you left out key new photo evidence that the barnacles were growing on top of damage from beaching.
https://t.co/0nj7oReeyB
That finding and a match with the shell growth temperature sets a timeline four months earlier than assumed in the drift modeling you mention above. There is not enough time for the flaperon to drift from a cold water crash site to Reunion, or for the second piece found, the Rolls Royce cowling debris to travel the farthest and fastest to Mossel Bay South Africa.
Ocean Infinity vessel Armada 86-05 is heading to its home port in Singapore with a Nov 6 ETA. The new ship 86-06 is already there. Fingers crossed that both ships will soon resume the #MH370 search by starting where the 7th Arc intersects the coast of Java, and scan a single swath southward along the arc to where they plan to continue expanding the previous search zone.
Yes! Doppler acoustics could help locate #MH370. I saw the original Colsto vid recently that inspired a couple of open source packages to implement the technique:
https://t.co/peBVnepSaA
I left a comment in the vid inviting anyone to look deeper. The only public recordings that are relevant to MH370 in the SIO are the seismometers at Cocos Keeling Island and Christmas Island. Both have airports, and a tentative indication that MH370 made a flyby at both at the right time between the SATCOM BTO arcs.
https://t.co/QzRrfKAXUF
The difficult part is getting access to the CTBTO recordings from the 8 infrasound recorders in an array at Cocos. I was able track aircraft taking off and landing there with recent data, but the March 2014 recordings are still restricted to Universities and research centers with a CTBTO contract.
Something unique was recorded on the Cocos Island seismometer in the middle of the night, and I'm still working on advanced filters to isolate the infrasound motion. It appears that MH370 may have approached the atoll from the north, and departed to the east toward Christmas Island, where there was another brief detection.
Several authors claim to see evidence of #MH370 in the multibeam bathymetry, but the resolution is only 150m per pixel. Some even claim single hot pixels from sat images with 5+ km pixels. Upscaling methods that insert smaller pixels like the one above are more likely to be generating artifacts in the process. I'm trusting that the experts who pored over the sidescan data and sent down AUVs to investigate anything odd didn't miss the seabed debris field.
@VishweshIndia Only two of the panel who dominated and interrupted gave their speculative accusations. Thankfully Martin Dolan of the ATSB had the last word and confirmed that nothing can be said about intent without finding #MH370 and examining the evidence.
@TapestryReader@MOTMalaysia@Ocean__Infinity That contrast enhancement has removed all context. It's low resolution bathymetry far from the 7th arc. Have a closer look at the Geoscience Australia data layers centered on the same spot:
https://t.co/yqUee5bBLR
Unfortunately, that misinformation comes from inaccurate reports by Usama Kadri that sparked conspiracy theories. The HA08 recordings were corrupted from 0300Z and flat from 0335 to 0400, but that is one hour AFTER the last noise arrived from sinking debris hitting the seabed. It did not interfere with the analysis. The main clutter on H08 was properly analyzed in 2014 by Alec Duncan as reported in the news and later as ATSB 2018 MH370 Final Report appendix H. The noise was tracked from survey ship TGS Huzzas working in shallow water near Exmouth. Kadri never read any of that, and assumed it was military ops near Madagascar because he also miscalculates the azimuths in his reports. See:
https://t.co/T2JOK8QcX3
LANL also dismissed HA08 due to the clutter, but beamforming methods can null it out. H08 detected a very strong event near Java that was assumed to be a quake. It turns out to be a unique event directly on the 7th Arc at 8.36S, consistent with a large section of sinking #MH370 debris hitting the seabed there.
SOSUS is an old USN system utilized in the Atlantic, now retired. The modern term is IUSS for underwater surveillance, but mainly deployed as towed arrays and sonobuoys as needed. The USN put out a PR at the time of MH370 saying that their capabilities in the Indian Ocean are classified, as a way of not admitting that they had none.
Still, the CTBTO had two directional arrays listening at SOFAR deep sound channel depth, and there were an additional 9 known hydrophones that all triangulate on one of the loudest events of the day, originating from near the coast of Java. It was also detected weakly on 40 regional seismometers with an epicenter directly on the 7th Arc, 56 minutes after the last ping. This is consistent with a large section of sinking MH370 hitting the seabed.
The site is surprisingly a good match for all the *factual* evidence available, but is 800 miles from any MH370 searches. Some experts are now recommending that it be searched next because it is in calm tropical waters and specific enough to be searched in a single dive.
See: https://t.co/qdYeRt536o
And: https://t.co/SiXJ6cAzpO
I think you are confusing a surface search area with a seabed sonar search. 143 km² per day is the low end for the early Fugro towfish seabed search for MH370. In 2018, Ocean Infinity deployed up to 8 Hugin AUVs at a time to achieve 1,300 km² per day. Covering 8,000 km² per day with aerial and surface ships is not remarkable.
The latest OI searches utilize three Hugin 6000 AUV from their own new Armada vessels, rather than previously leasing the bigger ships. If MNDF can actually do AUV seabed searches, please consider scanning the MH370 Java anomaly site in passing, which is estimated to have a seismic epicenter less than 16 km².
https://t.co/qdYeRt536o
The hydroacoustic data for finding #MH370 may come as a surprise to many, but Jeff Wise is focusing on a 2016 report and omitting newer findings. While the analysis was useful, the actual OHASISBIO recordings have never been released. A deeper dive into the hydroacoustics and seismology without that data revealed a seabed epicenter directly on the 7th Arc that is under consideration for the next search. For an inside perspective, see:
https://t.co/jPDccBVOQj
When GEOMAR did the first #MH370 drift study on the flaperon in 2015 with their working drift model. It wasn't tuned for Stokes drift, or even specific to the 7th Arc. Still, their highest probability point on the 7th Arc was at the Java anomaly candidate site. Later, they did studies with more debris finds and found that Stokes tweaks made the origin range anywhere from the Maldives to Antarctica.
I don't expect any of the reverse drift reports will redone at this late date, but investigators should be aware that the early findings are now in doubt. Forward drift studies starting on the 7th Arc are different. I'll link to a custom animation that starts at the Java site.
https://t.co/4Sb2uvj66k
https://t.co/wapioKGWWW
JM, there is new #MH370 flaperon barnacle evidence that does indicate how long between when it beached and was discovered. Photos of the inboard leading edge show that the barnacles grew on top of deep abrasions from beaching.
Analysis of the shell growth gave a temperature curve that is a good fit for Reunion sea surface temps from May through July of 2015. That sets the timeline. The earlier arrival affects all but the first GEOMAR study of the drift.
Add some weeks for the earlier growth of the larger 36mm shell vs the largest analyzed 25mm shell. It also solves the paradox of barnacles beginning growth at the warm 25C threshold end of their reproductive range. Most found debris had no barnacles, consistent with never leaving tropical waters, indicating a crash site north of around 21S.
See the key photo and report here: https://t.co/0nj7oReeyB
@adipokijan The image was take 4/29/2026 so it cannot be MH370.
Look in the lower left corner of the Google Earth Pro image, not Google Maps:
https://t.co/nVhwouGvdZ
With this astounding success, many are hopeful that @DeepSeaVision, @AirSeaHeritage and @Discovery will next take an interest in a viable new #MH370 candidate on the 7th Arc near the coast of Java. It is in calm tropical waters and the detected seismic epicenter is specific enough to scan in a single dive with a Hugin 6000 AUV. Please see for details:
https://t.co/lX30BH5vl3
The 2016 MH370 Royer hydroacoustic report was well done and helpful, but the author chose not to make it public. Because he relied on propagation timing only and didn't utilize the accurate bearings from the two @CTBTO arrays, some of the candidates listed are incorrect.
You're referring to the Curtin Univeristy studies that were eventually published as appendicies to the 2018 ATSB final report. They were not discredited. They had excellent technical accuracy and correctly detected events that later studies did not. Unfortunately, both the Royer and Curtin studies dismissed an important event directlly on the 7th Arc near Java as a minor uncataloged quake near the Java Trench.
That event came 56 minutes after the last ping and is thousands of miles from any previous search, but is consistent with a large section of #MH370 hitting the seabed and is a surprisingly good fit for all the factual evidence.