This website uses certain Blogger and Google cookies, including use of Google Analytics and AdSense cookies, and other data collected by Google. By remaining on this site, your consent is implied.

January 16, 2017: Just as I predicted would eventually happen (back on December 16, 2014), the Australian Transport Safety Bureau (ATSB) has ended their search for the MH370 plane crash wreckage in their search area without ever finding MH370 in it: Underwater search of 120,000 square-kilometre area in the southern Indian Ocean completed. Wreckage of Malaysia Airlines flight MH370 not found there. Malaysia, China and Australia announce decision to suspend the underwater search. "Paul Kennedy, the project director of Fugro – the Dutch company leading the search – acknowledged on Thursday [July 21, 2016] that, if the plane was not found there, "it means it's somewhere else"."

Translate

Showing posts with label VAMPI. Show all posts
Showing posts with label VAMPI. Show all posts

Monday, June 23, 2014

Hypothetical MH370 flight path to Perth, Australia via Cocos Keeling Island

Hover over image to open it in a larger view.

I created a picture to show a hypothetical flight path to Perth, Australia, via Cocos Keeling Island, that MH370 might have flown. This should be my last follow up to my posts here and here.

The Investigators insist MH370 could only have flown south. Their diagrams show MH370 flying close to Cocos Keeling Island and then continuing southeast after that. But with no explanation whatsoever, they use extremely slow estimated speeds for MH370, ranging from 325 kts to 350 kts.

Coincidentally, those slow speeds prevent MH370 from reaching the outer detection range of JORN until close to the time of MH370's final communications with the Inmarsat satellite.

However, MH370 and UAE343 were near each other at 18:22 UTC. Therefore MH370 would have been able to travel the same approximate distance as UAE343 had by 00:19 UTC. (UAE343 was near its destination of Dubai International Airport in the United Arab Emirates at that time.)

The only way MH370 could've gotten from its last known transponder location near IGARI/BITOD at 17:21 UTC to WMPK (Penang/Butterworth) and then to VAMPI/MEKAR by 18:22 UTC, which is the path Investigators say it flew, is if it was flying at a minimum speed of approximately 470 kts.

So why would whoever was in control of MH370 suddenly decide to start flying at a slower speed, as the Investigators claim?

And how did whoever was in control of MH370 keep the rest of the passengers and crew subdued during this more than 6 hour flight diversion?

If MH370 did fly south, which one of these stories is more plausible, knowing that the person in control of MH370 took deliberate actions to evade detection while MH370 was flying:

1) The person in control of MH370 flew south to the middle of nowhere to commit suicide, rather than doing a nose dive immediately in the location where the transponder went off.
2) The person in control of MH370 flew south to the middle of nowhere to land on the runway of a remote island.
3) The person in control of MH370 flew south to commit a 9/11 style attack on Australia, which was reachable.

Notes:
1) I am not saying MH370 did fly toward Perth for a 9/11 style attack. I am only saying that it was possible. (See my previous posts for more details on that topic.)
2) Australia has never said whether or not JORN detected MH370.
3) I used the following to plot the course shown in the picture:

Flight Path:
WMKK WMKN IGARI BITOD IGARI WMCK WMKP VAMPI
MEKAR NILAM VIROT UPROB YPCC MERIB YPPH

That flight plan and speed can be plotted on SkyVector.

Approximate times based on 470 kts:

MEKAR 18:22 UTC
NILAM 18:26 UTC
VIROT 18:38 UTC
UPROB 19:16 UTC
YPCC  20:58 UTC (Cocos-Keeling Island)
MERIB 23:55 UTC
YPPH  00:21 UTC (Perth)

Wednesday, June 18, 2014

MH370's final location could be near S35.672 E92 (if one believes the Investigators)

Hover over image to open it in a larger view.

I used Inmarsat's 7th Arc image to estimate that the radius of their circle was 2629.4 nmi (nautical miles).

I now estimate that the intersection of the due south flight path is near S35.672 E92, if one believes the Investigators. This latest image is an update to my original post on this topic, which can be read here.

Inmarsat has stated:
"We can identify a path that matches exactly with all those frequency measurements and with the timing measurements and lands on the final arc at a particular location, which then gives us a sort of a hotspot area on the final arc where we believe the most likely area is," explained (Chris) Ashton. (Source: The Guardian)

Yet despite Inmarsat's certainty of their precise final location of MH370, and despite all of the Investigators hailing Inmarsat's analysis as accurate and verified, the Investigators didn't go to that location. Instead, the Investigators chose to waste 8 weeks searching an area where they detected underwater pings that were outside of the specification for a Black Box. Being the experts, they would've known immediately that those signals weren't from MH370.

China determined that the underwater signal that they had detected wasn't from MH370, within a day or so. So how is it Australia failed to do the same with the signals they detected?

Note: I am only posting this to update my original estimate of where MH370's final location might be, based on what the Investigators have stated as facts in this case, and based on my estimate of the Inmarsat 7th Arc Timing Ring. At this point, for me, there are too many discrepancies for me to believe the Investigators.

Wednesday, June 11, 2014

MH370's final location could be near S32 E92 (if the Investigators' assertions are correct)

Hover over image to open it in a larger view.

If the Inmarsat Timing Rings are accurate, and if the Investigators' implication that MH370 flew by waypoints is true, and if the Investigators' insistence that MH370 could only have flown South is correct, then MH370's final location could be near S32 E92, assuming it flew due South after reaching waypoint KETIV.

I estimated the radii of the Inmarsat Timing Rings, then looked for any airplane that might have a correlation with the circle at 22:41 UTC.

SIA352 correlated with their 19:41, 21:41, and 22:41 UTC circles, flying North. I plotted SIA352's distances to the satellite, then mirror flipped and rotated those distances, to estimate where MH370 would be, heading South.

I made the further assumption that if MH370 flew South, as the Investigators insist, and if MH370 flew along waypoints, then I assumed it flew along these waypoints (to avoid land):

VAMPI MEKAR NILAM VIROT NIXUL KETIV S32E92

(I added S70E92 to extend the path down to the South Pole.)

That path correlated with the estimated 18:22 UTC radius, and the 21:41 and 22:41 UTC radii (in the Southern direction).

The 00:11 UTC circle (and 00:19 UTC circle, which isn't shown) intersect with the due South flight path near S32 E92.

Note: I am not saying this is in fact where MH370 is. I am presenting this as one possibility, based on what the Investigators have stated as facts in this case, and based on my estimates of the Inmarsat Timing Rings. Inmarsat has failed to provide the radii of their circles.

Thursday, May 22, 2014

Airplane Traffic at 18:22 UTC (Last Air Defense Radar Point of MH370)

Hover over image to open it in a larger view.

I captured a screen shot of all of the airplane traffic at 18:22 UTC on FlightRadar24, and used the Preliminary Report Map Showing MH370’s Flight Path to add the flight path and approximate locations for MH370 at18:01:49 UTC and 18:22 UTC.

I also added certain waypoints and airplane call signs, as well as MH370's last approximate transponder location at 17:22 UTC.

At 18:22 UTC, UAE343 was flying at 34,000 feet in close proximity to where they identified MH370 as being at that same time.