Go Back  PPRuNe Forums > Flight Deck Forums > Rumours & News
Reload this Page >

Indonesian aircraft missing off Jakarta

Wikiposts
Search
Rumours & News Reporting Points that may affect our jobs or lives as professional pilots. Also, items that may be of interest to professional pilots.

Indonesian aircraft missing off Jakarta

Thread Tools
 
Search this Thread
 
Old 19th Nov 2018, 22:13
  #1401 (permalink)  
gmx
 
Join Date: Nov 2018
Location: Brisbane
Posts: 25
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by infrequentflyer789
I'm not sure if I am totally barking up the wrong tree here, but there may be another possibility to consider as well:

What happens if MCAS and STS are both active? We have no information as to how they interact in that case, whether one system inhibits the other, whether outputs are summed or or-ed, whether the reactivation timers are identical and in-sync or not.

As I understand it, if speed (data) is increased STS will trim nose up, if AOA (data) is high MCAS will trim nose down, what if both? If the activation times are different the trim will be up then down, which might lead to a report of "sts trimming wrong way" in absence of knowledge of MCAS, no? So the pilot might be fighting an aircraft that is porpoising all on it's own. Note that this may not look like a classic "runaway trim" either, it isn't at this point running away in either direction.

Now if speed is reduced, will STS and MCAS (assuming indicated AOA remains high) both trim nose down, depending on the cyclic timing, possibly suddenly and at the same time (additive commands? - we don't know)?


But like I said, I may be totally barking up the wrong tree and have misunderstood STS/MCAS.
MCAS apparently only operates with AP disengaged. The fact that the EAD refers to the runaway trim procedure seems to indicate that the FDR indicated runaway trim. As I've mentioned elsewhere, if MCAS is implicated it means the pilots were flying by hand and counteracting MCAS auto-trim activity reasonably successfully up to a point. What happened to change that situation and trigger the horrific descent is very much unknown.
gmx is offline  
Old 19th Nov 2018, 22:51
  #1402 (permalink)  
 
Join Date: Aug 2007
Location: Ireland
Posts: 216
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by infrequentflyer789
There is some more info in earlierWSJ article on it. Seems they replaced both sensors as part of trouble shooting a fault where autothrust refused to engage (also replaced two others from ramp damage incidents). It then gets a bit confusing because the sensors were apparently found to be not the cause of the problem, but one or both was then repaired - make of that what you will I guess.
Might just be a system figure of speech. Sample:
A rotable is removed from an aircraft by a mechanic/engineer and is placed on the Unserviceable shelf.
An actual engineer from lets says tech services inspects the part and have 2 options:
Relase it back to service or send it for repair. If he is not absolutely certain of its status he/she selects to send it for repair.
When it comes back from repair, and it migh just have been tested/inspected to tolerances by a certified company, it is taken into stock with a tag as repaired.
In this sample it just means it went via the authorized repairer (this could be the manufacturer) instead of having been directly released back into stock by the tech services engineer.
vikingivesterled is offline  
Old 20th Nov 2018, 00:28
  #1403 (permalink)  
 
Join Date: Mar 2015
Location: North by Northwest
Posts: 476
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by vikingivesterled
Might just be a system figure of speech. Sample:
A rotable is removed from an aircraft by a mechanic/engineer and is placed on the Unserviceable shelf.
An actual engineer from lets says tech services inspects the part and have 2 options:
Relase it back to service or send it for repair. If he is not absolutely certain of its status he/she selects to send it for repair.
When it comes back from repair, and it migh just have been tested/inspected to tolerances by a certified company, it is taken into stock with a tag as repaired.
In this sample it just means it went via the authorized repairer (this could be the manufacturer) instead of having been directly released back into stock by the tech services engineer.
Wonder if the sensor PN for the Max is the same as for the NG (Bjorn Fehrm's write up would seem to suggest that)? Problem seemed to be compounded after the sensor change. Two prior segments - unreliable airspeed. Segment after change, unreliable airspeed and nose down. Last segment....

If SW changed a couple attempting to solve an autothrust fault wonder what the maintenance manuals say about AoA sensor false readings?
b1lanc is offline  
Old 20th Nov 2018, 03:32
  #1404 (permalink)  
 
Join Date: Mar 2014
Location: WA STATE
Age: 78
Posts: 0
Likes: 0
Received 0 Likes on 0 Posts
FWIW in seattle times re world wide conference call ..Boeing to hold global conference call with airlines that fly 737 MAX model that was involved in crash



Originally published November 19, 2018 at 6:19 pm Updated November 19, 2018 at 7:39 pm The conference call Tuesday will allow Boeing to field queries all at once from the group instead of having multiple individual conversations on the same points, said one of the people who asked not to be identified since the call is private.
CONSO is offline  
Old 20th Nov 2018, 04:00
  #1405 (permalink)  
 
Join Date: Sep 2018
Location: Laredo, TX
Posts: 133
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by gmx
MCAS apparently only operates with AP disengaged. The fact that the EAD refers to the runaway trim procedure seems to indicate that the FDR indicated runaway trim. As I've mentioned elsewhere, if MCAS is implicated it means the pilots were flying by hand and counteracting MCAS auto-trim activity reasonably successfully up to a point. What happened to change that situation and trigger the horrific descent is very much unknown.
Earlier in this thread or somewhere else, possibly in an AAL union pilots blog, there was either a Boeing or an AAL quote that intimated that if the cutout switches did not stop the "runaway" trim then you should hold the wheel as in the procedure. There was some skepticism about the success of doing that in the AAL blog. Someone else in this thread pointed out that the trim could still run away due to welded contacts and CB pulling would be required but I don't think that is relevant. I hope that Boeing did not engineer a MCAS circuit that bypassed the cutout switches but the "hold the trim wheel" verbiage makes me, and a few other posters, wonder. So if the crew fought the MCAS with trim and finally used the cutouts, would the MCAS still work and now they had to crank the trim wheel. But that doesn't explain why they let the birds airspeed get so fast.
jimtx is offline  
Old 20th Nov 2018, 06:15
  #1406 (permalink)  
 
Join Date: May 2007
Location: Western Pacific
Posts: 721
Likes: 0
Received 0 Likes on 0 Posts
I'm not sure if I am totally barking up the wrong tree here, but there may be another possibility to consider as well:

What happens if MCAS and STS are both active?
Correct me if I'm wrong, but doesn't the STS only operate with flaps extended & MCAS only with flaps up?
Oakape is offline  
Old 20th Nov 2018, 07:43
  #1407 (permalink)  
 
Join Date: Dec 2008
Location: the lake!
Posts: 25
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by cooperplace
is there someone with authority and detailed 737 knowledge who can explain to interested but uninformed nitwits like me whether any consensus as to cause of this tragedy is emerging?
I am not your knowledgeable authority figure but I have read the entire thread from the beginning and will be happy to summarize.

Before November 6th there was not much in the way of consensus as to a possible cause. Unreliable Air Speed (UAS) possibly due to the covers being left on the speed sensors was the talk of the day.

On November 6th Boeing issued a statement that changed the focus to the Angle Of Attack (AOA) sensor. Specifically that bad data from an AOA sensor could cause uncommanded nose down trim on the stabilizer (horizontal part of the tail).

Link to November 6th discussion: Indonesian aircraft missing off Jakarta

At some point Boeing disclosed the existence of a new feature named MCAS that was evidently not previously disclosed to pilots. MCAS is an anti-stall feature that was not required (or implemented) on older versions of the 737. When working properly with good AOA data MCAS trims the stabilizer to lower the plane's nose in an attempt to mitigate a stall. MCAS could have been a lifesaver under different circumstances, however...

MCAS along with faulty AOA data seems to be prevailing theory as to what might have been at least a contributing factor in the crash. The idea being that bad AOA data fed to MCAS caused the plane to be trimmed more and more nose down, ultimately leading to a crash.

Disclaimer: This is my interpretation of the speculation posted here by others. I could easily have goofed something up.
lakedude is offline  
Old 20th Nov 2018, 07:54
  #1408 (permalink)  
 
Join Date: Apr 2004
Location: near EDDF
Posts: 775
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by b1lanc
Wonder if the sensor PN for the Max is the same as for the NG (Bjorn Fehrm's write up would seem to suggest that)?...
Yes, same PN acc. IPC.
IFixPlanes is offline  
Old 20th Nov 2018, 07:58
  #1409 (permalink)  
 
Join Date: Jan 2008
Location: uk
Posts: 857
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by Oakape
Correct me if I'm wrong, but doesn't the STS only operate with flaps extended & MCAS only with flaps up?
Well, that is the sort of thing I was fishing for, but I don't think that's it.

I can find plenty of references that say MCAS only with flaps up, but looks like it is flaps up or down for STS (except on classics?)

-Flaps not up (737-300 & 500).
-Flaps up or down (737-400 & NG).
From: https://studylib.net/doc/8341353/boe...light-controls page 4.

No definite confirmation of conditions for MAX, but I haven't seen anything that says it is different.
infrequentflyer789 is offline  
Old 20th Nov 2018, 10:44
  #1410 (permalink)  
 
Join Date: Aug 2005
Location: EDLB
Posts: 362
Received 4 Likes on 3 Posts
After full three weeks they did not find the CVR in 30m deep water. Indonesia way of dealing with such desasters?
EDLB is offline  
Old 20th Nov 2018, 11:07
  #1411 (permalink)  
 
Join Date: Aug 2009
Location: Denmark
Age: 68
Posts: 401
Received 0 Likes on 0 Posts
Originally Posted by EDLB
After full three weeks they did not find the CVR in 30m deep water. Indonesia way of dealing with such desasters?
And a few tons of wreckage and who knows how many meters of mud.
sablatnic is online now  
Old 20th Nov 2018, 11:09
  #1412 (permalink)  
 
Join Date: Jan 2008
Location: Reading, UK
Posts: 15,810
Received 199 Likes on 92 Posts
Originally Posted by EDLB
After full three weeks they did not find the CVR in 30m deep water. Indonesia way of dealing with such desasters?
It's clearly not beneath just 30m of water, but also under an indeterminate depth of sea bed. What do you think they should be doing that they aren't ?
DaveReidUK is offline  
Old 20th Nov 2018, 11:11
  #1413 (permalink)  
 
Join Date: Aug 2008
Location: Moscow
Age: 44
Posts: 45
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by EDLB
After full three weeks they did not find the CVR in 30m deep water. Indonesia way of dealing with such desasters?
May well be muddy bottom or some other feature. Diving and underwater recovery is complicated, even in 30 ft of water.
AlexGG is offline  
Old 20th Nov 2018, 11:28
  #1414 (permalink)  
 
Join Date: Mar 2002
Location: Florida
Posts: 4,569
Likes: 0
Received 1 Like on 1 Post
It's clearly not beneath just 30m of water, but also under an indeterminate depth of sea bed.

If it near floats on the sea, it ought to take years for it to sink below the sea bed.
lomapaseo is offline  
Old 20th Nov 2018, 11:32
  #1415 (permalink)  
 
Join Date: Jul 2002
Location: Netherlands
Age: 71
Posts: 165
Likes: 0
Received 0 Likes on 0 Posts
Most likely the crew could not overcome the stab authority any more, in DC8 times known as "jackknifing".
If as a result the crooked negative camber of the stab/elev position, it might have stalled completely.
Similar to a plane that looses its complete stab, and we all know what happens then, don't we? With the CG in front of the Lift vector, the fuse will rotate DOWN. FAST.
A dramatic video about this phenomenon can be seen with the demise of some poor helpless chaps, note the wings indicating a dramatic "negative G"

Last edited by Double Back; 20th Nov 2018 at 11:50.
Double Back is offline  
Old 20th Nov 2018, 11:39
  #1416 (permalink)  
 
Join Date: May 2010
Location: UK
Age: 79
Posts: 1,086
Likes: 0
Received 0 Likes on 0 Posts
Not true for a soft silt bottom. Any heavy item reaching the bottom will kick up a large amount of silt which will re-settle to the bottom covering any debris.
The Ancient Geek is offline  
Old 20th Nov 2018, 11:42
  #1417 (permalink)  
 
Join Date: Jun 2006
Location: Brisbane
Posts: 265
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by lakedude
I am not your knowledgeable authority figure but I have read the entire thread from the beginning and will be happy to summarize.

Before November 6th there was not much in the way of consensus as to a possible cause. Unreliable Air Speed (UAS) possibly due to the covers being left on the speed sensors was the talk of the day.

On November 6th Boeing issued a statement that changed the focus to the Angle Of Attack (AOA) sensor. Specifically that bad data from an AOA sensor could cause uncommanded nose down trim on the stabilizer (horizontal part of the tail).

Link to November 6th discussion: Indonesian aircraft missing off Jakarta

At some point Boeing disclosed the existence of a new feature named MCAS that was evidently not previously disclosed to pilots. MCAS is an anti-stall feature that was not required (or implemented) on older versions of the 737. When working properly with good AOA data MCAS trims the stabilizer to lower the plane's nose in an attempt to mitigate a stall. MCAS could have been a lifesaver under different circumstances, however...

MCAS along with faulty AOA data seems to be prevailing theory as to what might have been at least a contributing factor in the crash. The idea being that bad AOA data fed to MCAS caused the plane to be trimmed more and more nose down, ultimately leading to a crash.

Disclaimer: This is my interpretation of the speculation posted here by others. I could easily have goofed something up.
That’s one way of surmising.

But the simple fact is that at this point, PPRuNe readers have no knowledge of what happened outside of FR24 data and what has been released in the media.

The only thing that has been released in the media is the Boeing AD regarding MCAS. It hasn’t been concluded that MCAS was the primary cause of the accident, however, given the publication of the AD, it has been the main subject of conjecture on this forum as a “contributing factor” (thank you lakedude).

Most accidents prove to have several “contributing factors”, and I’m sure this will be one of them.

I would suggest that the eventual analysis will include other contributing factors, including the quality of maintenance (given the evidence of the previous 3 sectors), and the quality of training (given that this event should have been survivable if indeed it was only an air data problem).

I don’t work for Boeing, but given the track record of this operator, I am really surprised at the outburst against Boeing on this thread. Boeing is not in charge of maintenance standards or training standards at customer airlines. If you want to buy a ticket to fly on a low cost airline, you carry a risk. Until the planes start crashing, low cost operators will continue to reduce standards. Eventually they will reach a point where the planes start crashing, and tragically, people will die. I will leave it to the community to decide when that point has been reached.

Last edited by Derfred; 20th Nov 2018 at 12:24.
Derfred is offline  
Old 20th Nov 2018, 12:09
  #1418 (permalink)  
 
Join Date: Jul 2008
Location: Dubai
Posts: 61
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by Oakape
Correct me if I'm wrong, but doesn't the STS only operate with flaps extended & MCAS only with flaps up?
Following from FCOM
B737 NG FCOM
STS operates most frequently during takeoffs, climb and go-arounds. Conditions
for speed trim operation are listed below:
• Airspeed between 100 KIAS and
Mach 0.5
• 10 seconds after takeoff
• 5 seconds following release of
trim switches
• Autopilot not engaged
• Sensing of trim requirement

B737 -300 (non-EFIS) FCOM
Flaps not up
Air speed 100-300 KIAS
N1 above 60%
(Rest of the conditions same as NG above)

MAX unknown. (some one in this forum can help)
Only Tristar_Drvr has mentioned he is flying the MAX in this forum. So he should know.
Hi_Tech is offline  
Old 20th Nov 2018, 12:27
  #1419 (permalink)  
 
Join Date: Dec 2006
Location: Florida and wherever my laptop is
Posts: 1,350
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by EDLB
After full three weeks they did not find the CVR in 30m deep water. Indonesia way of dealing with such desasters?
Originally Posted by AlexGG
May well be muddy bottom or some other feature. Diving and underwater recovery is complicated, even in 30 ft of water.
Nothing to do with Indonesia - it is the lackadaisical aviation industry way of dealing with disasters. There is no technical reason why CVR and for that matter DFDR data cannot be streamed into remote storage, the communication bandwidths available now are sufficient. Instead the aviation industry prefer to use barely 'survivable' recorders with cheap short range pingers with cheap short life batteries. Like the ELBs that never seem to work these recorders are antediluvian and need to be replaced. Just think if both DFDR and CVR recording had been retrievable from an online escrow system a lot of the current speculation would not have happened. And, either the 737 Max would be grounded or MCAS could have been completely exonerated within hours of the crash. MH370 would not be a mystery and AF447 would also have been properly investigated within a day or so rather than years. Billions of dollars could have been saved.
Ian W is offline  
Old 20th Nov 2018, 12:45
  #1420 (permalink)  
 
Join Date: Aug 2015
Location: The South
Posts: 304
Received 54 Likes on 21 Posts
Originally Posted by Ian W
Nothing to do with Indonesia - it is the lackadaisical aviation industry way of dealing with disasters. There is no technical reason why CVR and for that matter DFDR data cannot be streamed into remote storage, the communication bandwidths available now are sufficient. Instead the aviation industry prefer to use barely 'survivable' recorders with cheap short range pingers with cheap short life batteries. Like the ELBs that never seem to work these recorders are antediluvian and need to be replaced. Just think if both DFDR and CVR recording had been retrievable from an online escrow system a lot of the current speculation would not have happened. And, either the 737 Max would be grounded or MCAS could have been completely exonerated within hours of the crash. MH370 would not be a mystery and AF447 would also have been properly investigated within a day or so rather than years. Billions of dollars could have been saved.
Succinctly put.
Timmy Tomkins is offline  


Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.