PDA

View Full Version : CSIRO says it knows where MH370 is


p.j.m
21st Apr 2017, 07:08
Be interesting if MH370 is found 1000klms North East of where the search was be performed in the southern part of the indicative crash area instead of the northern part of the area where the pings were heard.

The CSIRO said its new report, released on Friday, confirmed that the most likely location of MH370 was a new 25,000 sq km area, north of the original 120,000 sq km search area.https://au.news.yahoo.com/a/35114800/csiro-says-it-knows-where-mh370-is/#page1

https://i.imgur.com/Uc1QZLs.jpg


https://i.imgur.com/m7ZQJ2x.jpg

TWT
21st Apr 2017, 07:52
I wonder if they will be able to convince any agency or government to gamble millions of dollars for yet another 'maybe' search ?

I don't think so.

p.j.m
21st Apr 2017, 10:49
from the ATSB website

News: CSIRO releases new MH370 drift modelling report (http://www.atsb.gov.au/newsroom/news-items/2017/csiro-mh370-drift-modelling-report/)

download report
http://www.atsb.gov.au/publications/investigation_reports/2014/aair/ae-2014-054/

The new search area, near 35°S, comprises thin strips either side of the previously-searched strip close to the 7th arc

doesn't seem consistent, 35°S was within the previous search area.

cattletruck
21st Apr 2017, 11:20
Could it be just another case of CSIRO looking for more funding?

Honestly, I would like to take them to task and put their very own jobs on the line with the outcome.

It's the best way to put any self-indulgent speculation to an end.

Ixixly
22nd Apr 2017, 03:26
How would this really help them cattletruck? They give this information over the ATSB and they go hire a completely different company to do the search, doesn't seem like they'd really gain anything out of monetarily?

Octane
22nd Apr 2017, 03:35
So they are saying they think they've located the "haystack"? All 25000 sq km of it? Equivalent to a 500km strip 50km wide. That's going to need a lot of dollars...:sad:

Pinky the pilot
22nd Apr 2017, 11:52
I think I've asked this question before; Is there anyone else on these boards who like me, suspects that there are certain Governments/Bureaucracies etc who do not want MH370 to be found?

Not ever!:=

Square Bear
22nd Apr 2017, 12:43
A bit of a paraphrase, BUT..

Is there anyone else like me that thinks too much of Aussie taxpayers money has already been spent on the search, and can't fathom why people are suggesting more money should be spent!!

Ixixly
23rd Apr 2017, 05:40
Because we HAVE spent all that money Square Bear, to spend it all and then get this sort of information and ignore it seems ludicrous, like running 9/10 of a marathon and giving up with the finish line in sight!

Not to mention there's how many Boeing 777's out there with a potentially fatal flaw that we haven't got the slightest clue about?

What about the lives of all those people on board, how much do you value the peace of mind for their families at?

How about for the lessons that could be learnt for potential future searches like this around the world?

I'm sure there's a lot of other reasons that people could fathom to easily justify searching an area that is backed up by CSIRO Drift Models and the Inmarsat Data now and gives up our best chance to date.

Icarus2001
23rd Apr 2017, 05:53
Not to mention there's how many Boeing 777's out there with a potentially fatal flaw that we haven't got the slightest clue about?

Cough, cough...err no, those that NEED to know this already know that the aircraft is fine.

criticalmass
23rd Apr 2017, 07:46
If any more money is to be spent on a search, it ought to be Malayasian or Chinese money. There is a limit to what Australia needs to spend, and we've pretty much reached it already. At least we looked for it. Nobody else seemed to give a damn. The Chinese gave up PDQ. As for the Malaysians - where were they?

onetrack
23rd Apr 2017, 12:06
From the JACC website ....

The Australian Government has provided around (AUD)$90 million as part of Australia's contribution to the search for Malaysia Airlines flight MH370, including (AUD)$60 million towards the cost of the underwater search effort.

The total cost of the search is around (AUD)$200 million.

The People's Republic of China contributed around (AUD)$20 million in the form of funding and equipment.

Malaysia agreed to fund the balance of the costs, of around (AUD)$120 million, associated with searching the 120,000 square kilometre search area.

I think China's level of monetary contribution to the underwater search was pretty poor, seeing as the largest majority of the pax on MH370 were Chinese.
It's a fair indication that China cares little about loss of its citizens. To be expected, I guess, when you have so many billions of them.

Don't forget that Australia has gained some pretty extensive seabed knowledge of an area that was previously largely unexplored, and a big unknown.
I also have little doubt that a lot of undersea search experience was gained from the search, which would provide pretty useful guidelines and processes for future searches, for aircraft lost in remote areas of the seas.

The revised crash zone for MH370 by the CSIRO is indicative that all the JACC/ATSB calculations on distance travelled were wrong - despite vast amounts of input by so called "specialists" and "experts".
The indications are now that the aircraft was suffering from excessive drag, probably caused by some kind of damage to fuselage or wing panels, which led to increased fuel burn or a lower cruise speed.

MickG0105
23rd Apr 2017, 12:36
Cough, cough...err no, those that NEED to know this already know that the aircraft is fine.
Yes, cough, cough ... that's what they were saying about the Boeing 737 after United 585 crashed in 1991 - the aircraft is fine. They only had to crash another two jets and kill another 185 people to er, cough, cough, come to the conclusion that the aircfaft wasn't fine after all.

MickG0105
23rd Apr 2017, 12:56
The revised crash zone for MH370 by the CSIRO is indicative that all the JACC/ATSB calculations on distance travelled were wrong - despite vast amounts of input by so called "specialists" and "experts".
The indications are now that the aircraft was suffering from excessive drag, probably caused by some kind of damage to fuselage or wing panels, which led to increased fuel burn or a lower cruise speed.
The revised search area doesn't necessarily indicate that the DSTG/ATSB calculations on distance travelled were wrong at all; what it suggests is that their assumptions about the timing of the final major turn south and/or the speed flown on the final leg south were wrong. And we always knew that the timing of the final major turn was a best guess based on the BFO data associated with the 1840 UTC air-to-ground phone call.

And there's nothing to suggest an increased fuel burn; an increased fuel burn would have resulted in fuel exhaustion before 0017 UTC.

Icarus2001
24th Apr 2017, 01:38
To those that still believe that there is an issue with the aircraft that caused the loss please apply some logical and critical thinking. It is known that the aircraft turned off route and flew along an FIR boundary, transponder was turned off. That is not an aircraft fault.

Secondly the "authorities" have more information that is not in the public domain. I have this from a friend close to the action, there was no fault with the aircraft.

jack red
24th Apr 2017, 04:22
start searching the sea bed area where the aircraft was last positively identified. yes, two hours and ten minutes north of KL on the KL - Beijing track. Secondly the "authorities" have more information that is not in the public domain...... you've got that right.

Ushuaia
24th Apr 2017, 04:25
To those that still believe that there is an issue with the aircraft that caused the loss please apply some logical and critical thinking. It is known that the aircraft turned off route and flew along an FIR boundary, transponder was turned off. That is not an aircraft fault.

Secondly the "authorities" have more information that is not in the public domain. I have this from a friend close to the action, there was no fault with the aircraft.

Talk about "alternative facts". It is NOT known that the transponder was "turned off". What is known is that the transponder signal ceased. That could be because someone turned it off or because the system failed for some reason.

The same "alternative facts" stuff keeps getting applied to the ACARS system - that "someone" obviously "turned it off". Wrong. The only facts known there are that the ACARS was set up to send a burst of data every 30 mins. It sent a burst at 1700Z. The transponder signal was lost at 1722Z and then at 1730Z no ACARS data was received (I may have the exact times wrong; those numbers are to illustrate my point). That does NOT mean someone turned off the ACARS; again, a major fault at 1722Z may be the cause.

As for the "authorities" having more info than is in the public domain: you may be right but I am inclined to call "B/S" on that. I have a mate who happens to have been the Australian-appointed, accredited investigator to the MH370 search team. We've talked extensively about the data and the search. He has never told me about "secret info", info being withheld. Now either he hasn't been told everything (possible) or he isn't telling me everything (also possible). But: unlikely.

Yes, apply some logical and critical thinking, don't just go on what the media and the Byron Bailey's will excitedly say, and you will come the realisation that major technical failure/s cannot be excluded. Imagine, for example, a bomb in the MEC, taking out multiple COMM and NAV systems. And oxygen systems. Cannot exclude someone trying to get the aircraft back to terra-firma whilst blind and mute. And then succumbing.

Despite all of the above, I too, am not excluding the possibility of the whole thing being a deliberate act. However it's wrong to distort the KNOWN FACTS to bias towards such a scenario.

cattletruck
24th Apr 2017, 09:24
I have this from a friend close to the action

He/she is not Chinese by any chance :}

Seriously, I do believe the truth is already known, but we (collectively) are just not ready for it.

Capt Kremin
24th Apr 2017, 10:29
Here's two facts.

The Satellite Data Unit (SDU) stopped working and then started working again.

The track taken from the tip of Sumatra to the most likely search area was a straight line. If you measure the known distance of the flight prior to the turn south, and measure a straight line to the search area from the turn south to the search area, you ind the aircraft had fuel to accomplish that track, and no more.

So, why would the SDU go off and come back on again, and how do you accomplish flying a straight line in a Boeing without some input from someone who knows what they are doing?

Lead Balloon
24th Apr 2017, 11:18
When you say "straight line", what is your reference for "straight"?

MickG0105
24th Apr 2017, 12:39
The track taken from the tip of Sumatra to the most likely search area was a straight line.

There is no evidence to suggest that MH370's track on its final leg south into the Southern Indian Ocean had to have been a straight line. In fact, Dr Bobby Ulich recently published a paper Interpretation of MH370 18:25–18:41 Satellite Data that demonstrates that the curving path generated by having the final leg flown on a constant heading of 180T from near waypoint ANOKO at Best Holding speed produces an excellent fit to the BTO and BFO data. The flight path produced initially curves to the west and then to the east under the influence of the prevailing winds.

1a sound asleep
25th Apr 2017, 02:14
A 25Cent levy should be paid on every airline ticket and funds kept in trust for this type of SAR op. To say there is no money is like saying we dont care

neville_nobody
25th Apr 2017, 04:14
Talk about "alternative facts". It is NOT known that the transponder was "turned off". What is known is that the transponder signal ceased. That could be because someone turned it off or because the system failed for some reason.

Go and find the commentary from the CNN panel that happened after the event. The facts described are hardly 'alternative'. They were presented immediately after the event. Only when they didn't fit into the story that wanted to be presented that they became 'alternative'.

Ask your mate about the descent profile flown and tracking after it turned around.

Ushuaia
25th Apr 2017, 05:13
....the commentary from the CNN panel that happened after the event....

You're relying on MEDIA as your source of the facts? As opposed to the raw data being analysed and presented by the ATSB investigators? Says it all.

Ask your mate about the descent profile flown and tracking after it turned around.

I have. And at the end of the day nothing is absolutely clear-cut and nothing is conclusive. Problem is, media will turn that grey information into "facts" and they become self-perpetuating.

MickG0105
25th Apr 2017, 05:39
Go and find the commentary from the CNN panel that happened after the event. The facts described are hardly 'alternative'. They were presented immediately after the event. Only when they didn't fit into the story that wanted to be presented that they became 'alternative'.

Ask your mate about the descent profile flown and tracking after it turned around.

This is a reasonable example of the over-reliance on the media and the under-reliance on proper factual information and research that has plagued the discussions on MH370 pretty much since the get go.

The transponder stopped transmitting at 1720:36 UTC; the reason for that is unknown, it may have been a failure or it may have been turned off. It is worth noting that the right and left transponder circuit breakers are rated at only 5 amps, making them amongst the less heavily rated circuit breakers in the P11 Overhead Panel.

As for "the descent profile flown"; there wasn't one. Of the various primary radar traces for the airplane as it tracked back over the Malaysian peninsular, only three contain altitude data:

1. 17:30:35 - 17:35 UTC (01:30:35 - 01:35 MYT), the radar return was at a registered height of 35,700 ft.

2. 17:36 - 17:36:40 UTC (01:36 - 01:36:40), the radar return was at a registered height of between 31,100 and 33,000 ft.

3. 17:39:59 UTC (01:39:59 MYT) , the radar return was at a registered height of 32,800 ft.

Allowing for the vagaries of primary radar with regards to determining altitude over short traces, that data suggests an altitude, or band of altitudes in a tight range, just below the previously established cruise of 35,000 feet, possibly consistent with a decent to FL340 as appropriate for the new westerly heading. Contrary to some early media reports, there was no radar-evading, low level run across the Malaysian Peninsula. Subsequent to the loss of transponder signal the airplane executed a fairly standard diversion manoeuvre, initially towards the nearest airport, Kota Bharu (which was closed), and then towards the nearest suitable airport, Penang.

TWT
25th Apr 2017, 05:51
There isn't the money available to search every 'possible' crash site. We could search this 'new' 25,000 km3 area and still come up with nothing. Then the boffins would come up with another new area,and so on. The cost/benefit equation is not very promising.

If a wealthy person wanted to donate money to fund more searches,that would be good but I think it's time to let it go,accept that we'll never know what happened and move on.

neville_nobody
25th Apr 2017, 07:18
You're relying on MEDIA as your source of the facts? As opposed to the raw data being analysed and presented by the ATSB investigators? Says it all.

Except that the information presented by CNN at the time is very similar to what the ATSB has.

Other than the guessimates made on the Satellite links there hasn't been much more 'new' information.

What has changed is the rhetoric, and anyone who suggests hijack or military op is quickly shot down as being 'conspiracy' nut. Like it or not every option is still on the table until more evidence is found.

cattletruck
25th Apr 2017, 09:26
I suspect the reason China is not throwing big money into any future search is because they must already know something.

If we don't spend a single cent from this point on then a version of the truth will eventually wash up on a shore, guaranteed.

Ushuaia
25th Apr 2017, 11:06
What has changed is the rhetoric, and anyone who suggests hijack or military op is quickly shot down as being 'conspiracy' nut.

Nonsense. I'm not dismissing nefarious conduct or outside interference either. They are certainly possibilities.

Like it or not every option is still on the table until more evidence is found.

You are exactly correct. But that is precisely NOT some people assert. Read post #15, for instance. And red herrings, outright disinformation about "descent profiles" for example, are outright mischievious.

This is a reasonable example of the over-reliance on the media and the under-reliance on proper factual information and research that has plagued the discussions on MH370 pretty much since the get go.

Absolutely spot on, MickG0105. Your entire post, in fact, is spot on.

International Trader
25th Apr 2017, 11:34
I'm with Pinky on this one.

_Phoenix
26th Apr 2017, 02:53
Both CSIRO and the ATSB have been contacted by Guardian Australia for their response. Godfrey said he believed a crash at 30 deg S latitude, well north of the seabed search, “fit the available data” published by CSIRO as well as the timing and location of debris that had been found.
“A MH370 endpoint at 35 deg S latitude does not fit the fact that the underwater search has already discounted this location to a 97% level of certainty.”

I strongly presume that 97% level of confidence comes from assumption that MH370 flew at cruise altitude, also I guess there is kind of confidential notice :O 97% we didn't see it, hence it was not there period! Better never find it instead admitting that we didn't see it right under our nose"

Tankengine
26th Apr 2017, 04:26
To those that still believe that there is an issue with the aircraft that caused the loss please apply some logical and critical thinking. It is known that the aircraft turned off route and flew along an FIR boundary, transponder was turned off. That is not an aircraft fault.

Secondly the "authorities" have more information that is not in the public domain. I have this from a friend close to the action, there was no fault with the aircraft.

"transponder was turned off. That is not an aircraft fault"
Prove it! The transponder stopped transmitting, nobody knows why, therefore it COULD be an aircraft fault.

"I have this from a friend close to the action, there was no fault with the aircraft."
Your friend could only KNOW this if he/she was on board the aircraft, therefore speculation.

Icarus2001
26th Apr 2017, 04:42
"I have this from a friend close to the action, there was no fault with the aircraft."
Your friend could only KNOW this if he/she was on board the aircraft, therefore speculation.

This is simply untrue, you need to think a little more laterally.

Non so blind as those who will not see.

27/09
26th Apr 2017, 05:20
Icarus, the only lateral thinking I can come up with is if someone knows for certain it wasn't a problem with the aircraft why hasn't this been made public and why have they allowed the search charade to continue?

There's not much point in such an extensive search if there incontrovertible evidence the aircraft wasn't at fault.

Icarus2001
26th Apr 2017, 05:25
There's not much point in such an extensive search if there incontrovertible evidence the aircraft wasn't at fault

How much has Boeing contributed?

Tankengine
26th Apr 2017, 06:18
This is simply untrue, you need to think a little more laterally.

Non so blind as those who will not see.

Your second line is true.
The rest of your story is speculation, you call "facts".

It is a fact it crashed, there are alternative speculations as to why, and even where. ;)

Tankengine
26th Apr 2017, 06:21
How much has Boeing contributed?

Probably nothing?
They would not want it found if there is a chance it is their fault. ;)
Better to whisper "murder/suicide, nothing wrong with our aircraft" ;)

Chocks Away
26th Apr 2017, 10:44
Yeh right... Boeing was not at fault and you can guarantee they have been heavily consulted, behind closed doors (without Perth's flogga G.T.!) right from the very moment it "went off the screen" and a number of Gulstreams darted out of Diego Garcia & Guam into KL!
Let's keep to the know facts - the aircraft was deftly manoeuvred along the borders of Malay; Thai and Indo airspace right to a point above Bandah Aceh, both in altitude and headings. There were over a dozen "suitable" and capable airfields he flew past, he could have used, if they wanted to.
I personally thought he took the northern arc of "engine pings" to sneak up into the back of China with his "Cargo" but who knows?
What was on the Cargo manifest needs to be examined. Lips have been sealed over this part haven't they!
Herein lies the motivation for such a stunt, I contend.

Captain Nomad
26th Apr 2017, 11:27
It is a fact it crashed

Is it? Do we know that with certainty? :E

MickG0105
26th Apr 2017, 12:02
Let's keep to the know facts - the aircraft was deftly manoeuvred along the borders of Malay; Thai and Indo airspace right to a point above Bandah Aceh, both in altitude and headings.

Well let's start by replacing that media hype you're spruiking with the real known facts. The airplane most assuredly did not manoeuvre, deftly or otherwise, along the Malaysian-Thai FIR boundary. After turning back off its planned flight path near IGARI MH370 flew on a track that took it over, not along, a stretch of about 120 kilometers of the Bangkok (Thailand)‐ Kuala Lumpur (Malaysia) airspace boundary that traces the Golok River. Subsequently, MH370 remained firmly in the Kuala Lumpur FIR (Malaysian airspace) at all times until it was lost from radar.

The turnback from near IGARI is pretty much what would be expected in the case of an evolving inflight emergency with the flight crew commanding an initial diversion to Kota Bharu (WMKC) by selecting it off the FMC Alternate Page (WMKC would have been the No 1 “default” option) and commanding Divert Now, Execute followed a few minutes later by the choice of destination being amended to Penang (WMKP).

There is not a scintilla of evidence to support the notion that MH370 flew to a point above (over?) Banda Aceh; it disappeared off radar heading west-north-west about 80 nautical miles north-north-east of Banda Aceh and its final turn south would have brought it no closer than about 50 nautical miles to the west of Banda Aceh.

Tankengine
26th Apr 2017, 12:31
Is it? Do we know that with certainty? :E

OK, possibly not.:hmm:

The wreckage found on the beaches would indicate that as the most likely cause.
Conspiracy theories aside.;)

Capt Kremin
26th Apr 2017, 13:14
There is no evidence to suggest that MH370's track on its final leg south into the Southern Indian Ocean had to have been a straight line. In fact, Dr Bobby Ulich recently published a paper Interpretation of MH370 18:25–18:41 Satellite Data that demonstrates that the curving path generated by having the final leg flown on a constant heading of 180T from near waypoint ANOKO at Best Holding speed produces an excellent fit to the BTO and BFO data. The flight path produced initially curves to the west and then to the east under the influence of the prevailing winds.

The evidence for a straight line is that the ATSB's best guess as to where the flight ended is at a position that would have required a straight line to achieve due to the fuel considerations. Any other track to that point would have needed more fuel than was aboard.

Therefore, if the wreckage is ever found near this area, we can safely rule anything but deliberate action by a person knowledgeable in the navigation systems.

Speaking of which, Dr Ulrich's paper is deficient in such system knowledge.

A B777 reaching an End of Offset or End of Route point in LNAV would have reverted to the default AFDS modes of Magnetic heading hold and SPEED mode.

Airliners dont fly enroute in TRACK mode or with TRUE reference set (polar operations excepted), yet these are the selections that would have to have been made if the AFDS was flying the aircraft, to achieve that straight line as the default magnetic heading mode would have turned the aircraft in a gentle turn towards the Australian coast due to large changes in magnetic variation as the aircraft headed south

The only other way to do it is LNAV with a waypoint entered into the FMC. Either way it must be done via someone who knows what they are doing.

Mick I have read your scenario and consider that the series of cascading and coincidental events to be far-fetched. You really lost me when your scenario had a crew, still with some semblance of control, abandoning all hope and looking for somewhere to crash. To my knowledge no crew in history has ever done this.

With regards to the SDU, have you considered that perhaps the one reason to de-power the LH AC Bus was to deny the use of SATCOM communication to the Flight attendants for the period of time required to take them out of the equation?

Panasonic IFE systems retain the ability to make such calls even if the IFE has been switched off.

GBO
26th Apr 2017, 13:59
Contrary to what the Malaysians have said, the transponder was not "turned off" in the cockpit, nor did it climb to 44,700 feet (too heavy) or descend to 5000 feet (groundspeed would be too low).
Mode S was dropped from the radar (but when was it coasted?) around the time the aircraft was turning at Igari, then 37 seconds later, the secondary radar symbol disappeared. How can you just turn off Mode S from the cockpit? Even turning the selector to ALT RPTG OFF still transmits Mode S. It is more likely that the transponder had lost air data from the LEFT AIMS cabinet in the MEC.

Interestingly when the satcom did log on again at 18:25 the flight ID was missing. The flight ID is sent to the SDU only from the LEFT AIMS.

So, if the LEFT AIMS is damaged, that's a major problem, since it interacts with over 100 LRUs, switches and sensors! It's the left electronic brain.

The Audio Management Unit must be operational to make any radio call. The AMU uses the LEFT systems ARINC 629 bus.

The aircraft satcom had unique dual side mounted Ball Aerospace high gain antennas (HGA). If the LEFT AIMS is damaged, then there is no IRS data for the Left HGA mounted on the left side of the fuselage. However the right HGA would be operational since IRS data is from the Right AIMS. Amazingly at 1825, around the time when the right hga is first exposed to the satellite, as the aircraft rolls left at Nilam (but still heading northwest), for a diversion to Banda Aceh via Nilam-Sanob, the satcom logs on again! The Crew could have been incapacitated well before this time.

Then if the aircraft continues on over Banda Aceh it hits all the BTO arcs, meets the BFO requirements and ends at the Bayesian approach hotspot in the southern Indian Ocean. However, if it is still at FL350, then there is still fuel in the tanks at 0017:30. So, either the APU was on (meaning the aircraft is south of the hotspot beyond 40 nautical miles), or the left engine was still operating (Left GCU and backup converter inop) when the APU auto started and repowered the Satcom via the Left Mains AC bus.

If they want to find MH370 they should search the full 100 nautical mile radius from the Bayesian hotspot (approx 38S88E), not just to 40 nautical miles along the seventh arc.

If they want evidence, just ask them to release the withheld information: playback of secondary radar, Vietnamese ATC transcript of call with MH88, the FOs phone connection logs with Penang and Banda Aceh, playback of the multiple Indonesian Primary radars, Malaysian 10 sec primary radar, fuel report, etc

So what damaged the LEFT AIMS Cabinet? Most likely, the adjacent Crew oxygen bottle ruptured - it was topped up immediately prior to flight!

MickG0105
27th Apr 2017, 01:08
The evidence for a straight line is that the ATSB's best guess as to where the flight ended is at a position that would have required a straight line to achieve due to the fuel considerations. Any other track to that point would have needed more fuel than was aboard.

For fear of stating the blindingly obvious, the search of the area at the end of that straight line turned up bupkis. At least two curving flights path that terminate on the 7th arc to the north of the ATSB search area are both excellent fits for the BTO/BFO data and the fuel flow/exhaustion data.

Speaking of which, Dr Ulrich's paper is deficient in such system knowledge.

A B777 reaching an End of Offset or End of Route point in LNAV would have reverted to the default AFDS modes of Magnetic heading hold and SPEED mode.

Subsequently corrected by Dr Ulich after his hypothesis was tested in a level D full flight sim. However, that technical error in no way impacts the fact that curving flight paths can be excellent fits for both the BTO/BFO data and the fuel flow/exhaustion data.

Mick I have read your scenario and consider that the series of cascading and coincidental events to be far-fetched. You really lost me when your scenario had a crew, still with some semblance of control, abandoning all hope and looking for somewhere to crash. To my knowledge no crew in history has ever done this.

My research and hypothesis has no bearing on the fact that that curving flight paths can be excellent fits for both the BTO/BFO data and the fuel flow/exhaustion data, but since you raise it, it sounds like you may have read an early version of my work; I've made some changes to circumstances surrounding the final major turn relating to the exhaustion of the portable walk around oxygen supply.

In any event, I'm the first to admit that my hypothesis is purely speculative. In fact, I introduce it as exactly that by saying;

The following is entirely speculation on my part but it is guided to a large degree by research and precedent accidents. It provides an internally consistent narrative that offers possible and plausible explanations for all observed events; it explains the evidence but that does not mean that it is supported by the evidence.

To the extent that you think that the hypothesised sequence of events is far fetched, well, that's the way many aviation accidents have unfolded; a series of individually unlikely events coming together to bring down an airplane in an unexpected fashion.

While the chain of hypothesised events may strike you as unrealistically improbable, the hypothesised initiating event, a windshield heater fire, was most assuredly not unrealistically improbable. To the contrary, it is an indisputable fact that 9M-MRO belonged to a cohort of B777s that were statistically significantly over-represented in windshield heater related incidents. When adjusted for years of service, the rate of incidence of windshield heater fires/failures for B777s produced in 2002 was nearly 17 times higher than the incidence rate for the entire B777 fleet as at March 2014 and more than 100 times higher when compared to the remainder of the B777 fleet (ie the fleet excluding the 2002 sub-group).

Now, if I had produced some sort of psychological analysis that demonstrated that a flight crew member was more than 100 times more suicidal than the rest of his colleagues the rogue pilot theorists would have been all over that like Clive Mensink on cruise ship buffet breakfast.

With regards to the SDU, have you considered that perhaps the one reason to de-power the LH AC Bus was to deny the use of SATCOM communication to the Flight attendants for the period of time required to take them out of the equation?

Panasonic IFE systems retain the ability to make such calls even if the IFE has been switched off.

The Panasonic System 3000i IFE fitted to 9M-MRO did not have cabin voice telephony capability. Moreover, there were something like 90 spare drop down masks and 15 walk around bottles of oxygen in the cabin of 9M-MRO for a total of 36 hours and 45 minutes of oxygen after the initial drop of passenger oxygen was depleted after 22 minutes. Turning the comms back on after only an hour would have been dangerously precipitous for what was ostensibly such a meticulously planned operation, wouldn't it? On Helios 552 a cabin crew member managed to stay conscious for more than two hours after everyone else succumbed to hypoxia.

Capt Kremin
27th Apr 2017, 05:39
The Panasonic System 3000i IFE fitted to 9M-MRO did not have cabin voice telephony capability.

It did have the capability but it was disabled to the passenger seats. That does not mean that the SATCOM call capability from the Cabin Managers station was disabled. Qantas use a similar system and have the ability to make a SATCOM call from the CSM's station even though the seat capability is similarly disabled, even with the IFE switched off. In all probability so did MAS.

Re: the Oxygen. All the oxygen in the world will be useless at 35,000 feet if it is not delivered at a substantial pressure.

The oxygen generators supplying the drop down masks deliver 3.8 litres per minute for 7 minutes, after which the flow rate drops to 1.8 litres per minute till exhausted. These flow rates are not enough to maintain consciousness for any length of time at 35,000 feet.

In contrast the Flight deck system is required to deliver a minimum of 20 litres per minute, delivered at 100% with an emergency pressure if required. The cabin bottles have a maximum of 4 litres/min capacity, also not delivered with sufficient pressure to keep someone cogent and functioning.

Yes the Helios crew member survived at 34,000 feet but was unable to operate the radios despite being a CPL holder. Clearly the oxygen he was receiving was enough to keep him semi-conscious but he was he was not functioning. No-one else on the flight was able to remain conscious.

For fear of stating the blindingly obvious, the search of the area at the end of that straight line turned up bupkis.

The ATSB, for some unknown reason, models the "End of Flight" scenario on no-one being alive on the flight deck. If someone was, someone with the ability to balance the fuel difference and fly the aircraft in any manner they chose after both engines flamed out, then the area required to be searched widens considerably.

They chose that area for good reasons and discounted the curved flight paths. The straight flight path can only be achieved by someone with systems knowledge and deliberate intent.

However, that technical error in no way impacts the fact that curving flight paths can be excellent fits for both the BTO/BFO data and the fuel flow/exhaustion data. Not if it went into Speed Mode. The curved flight paths require a reduction in speed. Speed mode holds the current speed at the end of the route.

MickG0105
28th Apr 2017, 03:45
That does not mean that the SATCOM call capability from the Cabin Managers station was disabled. Qantas use a similar system and have the ability to make a SATCOM call from the CSM's station even though the seat capability is similarly disabled, even with the IFE switched off. In all probability so did MAS..

Okey doke, so just to be clear, based on how a different airline configured a different model Panasonic IFE on a different airplane type, you believe that "in all probability" 9M-MRO had a hitherto undisclosed and undocumented pax cabin SATCOM air-to-ground telephony capability? Seriously?

maggot
28th Apr 2017, 04:29
Alt.facts.wow

Capt Kremin
30th Apr 2017, 12:06
Okey doke, so just to be clear, based on how a different airline configured a different model Panasonic IFE on a different airplane type, you believe that "in all probability" 9M-MRO had a hitherto undisclosed and undocumented pax cabin SATCOM air-to-ground telephony capability? Seriously?

Absence of evidence is not evidence of absence.

The Factual Report has two statements regarding the two SATCOM calls made from the MAS IOC to MH370 that states, "This call would have been routed to the cockpit and....".

These are redundant statements if the calls could only go to the Flight Deck and implies the calls could have been routed elsewhere on the aircraft.. Its not proof that the capability was there, but its hardly a revolutionary capability and certainly not type specific.

I have attempted to verify if the capability was present but am yet to receive an answer

The fact also is that we dont know what was omitted from the Factual Report. The report already contains at least one glaring error when it states that the fuel burn difference between the left and right engines was 1.5T per/hour instead of per flight.

Ushuaia
30th Apr 2017, 23:37
..... and implies the calls could have been routed elsewhere on the aircraft..

You are grasping, Capt. It does NOT imply anything of the sort. It is a statement explaining to the reader where a call from the ground to the aircraft gets sent to, i.e. the cockpit.

Your argument is analogous to me telling you that if you turn a yoke to the left then the aircraft will roll to the left. And you then saying, well, it could also roll right because I didn't tell you it wouldn't roll right........

Read pg 49 of the report. It clearly explains what comms were available in the cabin, namely email and SMS only, through the IFE. The voice capability was seat-to-seat only on 9M-MRO. It's there in black & white unless you want to argue the report is presenting alternative facts; or that because the report doesn't explicitly exclude voice-out-of-aircraft capability that it might have been actually available?!

I'm not 100% sure but my understanding is that the cabin-crew station has the same capability as all the cabin, i.e. the IFE capability. I concede I am not sure of that, but again: the report does NOT state the ISM/CSM station had a voice-out capability so why do you suggest it might?

Yes - there was a SMS/email out capability and if you wanted to disable that then you disable the SATCOM system. But move on to pg 54. At 1825 there was a SATCOM logon from the aircraft. Normal SATCOM operation resumed, but with no data and no flight ID. The IFE also set up a connection for SMS/email. No data was ever sent, though, and another call from ground to aircraft went unanswered.

For what purpose would someone disable the SATCOM system around 1722Z and then about an hour later re-enable it but not use it at all?

Pg 53 also states that a GES would record a SATCOM log-off initiated from the cockpit. No such log-off was recorded, suggesting power interruption instead. Presumably that could be circuit-breakers... or something else. If someone pulled the CB's, they would have presumably had to reset them for the events at 1825Z to happen?

We simply don't know what happened. All this could be from nefarious actions OR a major technical problem. But distorting known facts and suggesting other "facts" by "implying" things to support your particular bias, when you really don't know, is just wrong.

MickG0105
1st May 2017, 05:43
Absence of evidence is not evidence of absence.


Sure, so get back to us when you have some actual evidence then.

The report already contains at least one glaring error when it states that the fuel burn difference between the left and right engines was 1.5T per/hour instead of per flight.


Okey dokey, for starters, the FI is simply quoting from what was written in 9M-MRO's Deferred Defect Log. The authors aren't stating anything, they're quoting what the MAS Maintenance Control Centre had in their records.

Second, do you really think that the right engine would use 1.5T more fuel than the left per flight!? Under what set of circumstances do you think 1.5T/flight could possibly make sense? It's not like a coin operated kiddies ride, the "flights" are all different durations.

It clearly didn't dawn on you that the MAS MCC made a typographical error and entered a "T" when the correct character should have been a "%"; the T (shift T) and % (shift 5) keys are adjacent to one another.

Capt Kremin
1st May 2017, 08:44
Sure, so get back to us when you have some actual evidence then.

Mick, you are clearly defensive of your hypothesis and why not, you put a lot of work into it.

However, considering the number of sweeping assumptions without evidence you made in your analysis, its a bit rich to make that statement.

Let me make one assumption akin to the many you made.

"The perpetrator, unsure if turning the IFE off from the flight deck would definitively eliminate all means of air-to-ground communications from the Cabin Managers station; de-powered the LH AC bus until such time as the effects of depressurising the aircraft could eliminate all possibility of such communication taking place."

Surely that is possible?

Note I said ""de-powered". Your constant reference to "isolating" the AC bus is in error. Isolating an AC bus doesn't de-power it, it simply removes it from the possibility of powering or interfering with other buses. All items powered by the bus remain powered.

MickG0105
2nd May 2017, 04:59
Mick, you are clearly defensive of your hypothesis and why not, you put a lot of work into it.


This discussion has got nothing to do with my defending my research and hypothesis; your contention about an unknown, undocumented comms capability really has no bearing on my hypothesis. And at the end of the day, it's just a hypothesis for goodness sake, it's not my first born son. It'll either be right, wrong or somewhere in between; as the Zen Master said, "We'll see."

In order to explain a crucially pivotal event you've suggested that 9M-MRO had a pax cabin SATCOM air-to-ground telephony capability and there is not a scintilla of evidence to support that contention. Is it possible that you are thinking of later versions of Panasonic IFEs such as the Panasonic eX2 IFE system?

That said, IF the airplane had this hitherto undocumented capability and IF turning off the IFE didn't shut it down completely then yes, shutting down the SATCOM at the SDU would make sense. Having done that though, why would you turn it back on after only an hour? Or even turn it back on at all?

Your constant reference to "isolating" the AC bus is in error. Isolating an AC bus doesn't de-power it, it simply removes it from the possibility of powering or interfering with other buses. All items powered by the bus remain powered.


Thanks, fair call. I'll look to amend that in the next version.

Capt Kremin
2nd May 2017, 06:23
Having done that though, why would you turn it back on after only an hour? Or even turn it back on at all?

Because flying with the LH AC bus off is not something you want to do if you dont have to.

In my view de-powering the bus may have been gold-plating the denial of comms scenario. Not to put to fine a point on it, an hour, maybe 80 minutes of depressurisation should have ensured it was no longer required to be un-powered.

As with you, the scenario is pure speculation on my part but this scenario is probably the simplest to explain technically. As to motive... I really can't explain it on the information available.

MickG0105
3rd May 2017, 12:12
I have attempted to verify if the capability was present but am yet to receive an answer


Mon Capitaine, I wasn't able to turn up much beyond some promotional material on the Panasonic IFE but someone smarter than me found Boeing Service Bulletin 777-24-0075 (Original Issue: August 21, 2003) ELECTRICAL POWER - General - Install the Passenger Compartment Electrical Power Isolation Switches (Complete). The reason for the SB is as follows;

The change described in this service bulletin will provide new switches on the flight deck than can remove power from the cabin systems if smoke or flames occur. Smoke and flames in the passenger cabin can cause injury to the passenger and damage the safety critical cabin equipments.

We have received numerous reports of smoke or flames in the passenger cabin related to the wiring for the passenger cabin in-flight entertainment system, cabin lighting and passenger seats. It is not easy to remove the electrical power to these systems to stop the smoke or flames. Two switches can be installed to remove power from some of the passenger cabin electrical systems.

When selected OFF, the IFE/PASS SEATS switch will remove power from all the components of the IFE (in-flight entertainment) system and the passenger seats (seat motor power, personal computer power outlets and telephones).
...

Among the IFE components that are to be depowered when the IFE/PASS SEATS switch is selected OFF are the Cabin Telecommunication Unit, the M1/M2 Galley Handsets and all the telephones, both seat and wall mounted.

Bearing in mind the timing, a couple of years after the final report on Swissair Flight 111 was handed down, you get the sense that this SB is meant to ensure, inter alia, that the IFE/PASS SEATS switch removes power from all IFE components including the phones. To that end the test procedure includes the following:

f. Do this test of the IFE/PASS SEATS switch.
(1) On the P5 panel, select the IFE/PASS SEATS switch to OFF.
(2) Make sure that all the IFE equipment in the purser work station or video control center
no longer has electrical power. Some components may have battery backup units. For
these components it may take several minutes before the electrical power is removed.
...
(7) For airplanes with wall mounted telephones, make sure that the telephone does not
operate. ...

I wouldn't necessarily call this slam-dunk definitive but it certainly strongly suggests that the IFE/PASS SEATS switch takes down all passenger cabin telecommunications.

Capt Kremin
4th May 2017, 01:11
it certainly strongly suggests that the IFE/PASS SEATS switch takes down all passenger cabin telecommunications.

I agree, however the aircraft I fly has the same switch and it doesn't cut off the Cabin SATCOM link.

The FI references the CPMU; the Cabin Passenger Management Unit, which provides an interface between the Panasonic IFE and the SDU, for any Data-3 SMS/e-mail messages.

It would be very interesting to find out more about the CPMU to ascertain if it is de-powered by the IFE switch.

I can see good reasons why it would not be, particularly if it also controls cabin lighting, cabin comms and PA functions. Unfortunately I cannot source a reference for what it does.

If it still works after the IFE is de-powered, and you can send SMS/Emails via the SATCOM with it, then that would be a reason to de-power the LH AC Bus.

.Scott
4th May 2017, 14:03
Malaysia has posted their analysis of MH370 debris - including structural notes on how the aircraft pieces were separated from the aircraft.

http://www.mh370.gov.my/phocadownload/3rd_IS/Debris%20Examination%20300417.pdf

None of the debris had been crushed or punctured during separation. A vertical tail piece suffered damage consistent with an overload of dynamic air pressure. A wing piece was pulled and twisted off. All other pieces were separated by being simply pulled from the aircraft.

The report itself provides analysis of each piece of debris, but provides no summary conclusions.

There is one piece, a plastic frame to a back-of-seat video screen which non-Malaysian analyst claim is more consistent with being torn from the seat by water flow than by the force of air flow.

Overall, it is 100% consistent with the aircraft breaking up in uncontrolled flight. I particularly noted bending damage to a vertical tail section.

Easy to imagine continued rapid acceleration downward with small sections of the craft tearing free from the heavier ones. And easy to imaging that this could be a problem for discovering the debris on the ocean floor. The most identifiable pieces, the engines and other heavy equipment, could have been stripped of lighter materials, thus impacted at very high terminal velocity.
This could have streamlined them for their watery descent and to partially bury themselves in silt on the ocean floor.

Of course, this is very consistent with the best satellite-based estimate of what happened in the final moments. That is, a very high rate of descent towards the ocean.

BuzzBox
5th May 2017, 03:28
Capt Kremin:

I agree, however the aircraft I fly has the same switch and it doesn't cut off the Cabin SATCOM link.

What type of aircraft is that; B777, or something else?

That does not mean that the SATCOM call capability from the Cabin Managers station was disabled. Qantas use a similar system and have the ability to make a SATCOM call from the CSM's station even though the seat capability is similarly disabled, even with the IFE switched off.

Again, which aircraft type?

It would be very interesting to find out more about the CPMU to ascertain if it is de-powered by the IFE switch.

I can see good reasons why it would not be, particularly if it also controls cabin lighting, cabin comms and PA functions.

The CPMU is part of the Cabin Passenger Management System (CPMS) that is used to manage cabin-related data such as audio/video program libraries, passenger lists, destination information, cabin crew flight reports, connecting flight information, flight arrival information, 'Airshow' information, etc. The CPMU is the main controller that transmits data to other CPMS components and also acts as an interface to other aircraft systems. Based on the description of the CPMU in the FI, it provides an interface between the IFE system and the SDU for SMS and e-mail messages.

The CPMU does not control functions such as cabin lighting, cabin interphone, PA, etc, which are all controlled by the Cabin Services System.

The Boeing Service Bulletin that MickG referred to in an earlier post required the engineers to check that power was available to the CPMU with the IFE/PASS SEAT switch selected ON. There was no associated check with the switch selected OFF, but it seems that the switch position might affect the supply of power to the CPMU.

Capt Kremin
6th May 2017, 02:07
Again, which aircraft type?

The SATCOM remains available in the cabin with the IFE switched off, on all Panasonic IFE systems fitted to the three QF longhaul types.

It's obviously a safety feature.

Therefore there may be good reason to believe the same thing happens on Panasonic systems on the B777

BuzzBox
6th May 2017, 04:16
Therefore there may be good reason to believe the same thing happens on Panasonic systems on the B777

Nope. We operate a large fleet of B777s with the Panasonic IFE. ALL telephone handsets in the cabin are disabled by the IFE/PASS SEATS switch.

Capt Kremin
6th May 2017, 07:06
Nope. We operate a large fleet of B777s with the Panasonic IFE. ALL telephone handsets in the cabin are disabled by the IFE/PASS SEATS switch.

So that's includes the Cabin managers station?

BuzzBox
6th May 2017, 07:13
Our aircraft don't have a handset at the cabin manager's station. There is a wall-mounted handset nearby - that handset and the one at the rear of the aircraft are both disabled by the IFE/PASS SEATS switch, together will the handsets at each passenger seat.

Also, none of the handsets in the cabin are capable of receiving calls via SATCOM. Incoming SATCOM calls are only routed to the flight deck.