UPDATE to the Update from AvWeekly aviationweek.com/commercial-aviation/faa-reviews-enhanced-max-flight-test-data?CPEN1000000907970&elq2=7b24c0887f88426098a9f69399830ffc%20FAA%20Reviews%20Enhanced%20MAX%20Flight-Test%20Data
On the 737-800 you flew, what was the procedure for powered on stalls. The reason why I ask is that I am trying to deduce true effects of the bigger engines and MCAS vs the hype. Can you simply pitch down to recover, or is the pitch induced thrust so great that you need the assistance of the stabilizer trim to recover? Mentour pilot hinted at this behavior in his video when he was in the 737/NG simulator (A good video to check out if you haven not. He flies out of Europe). [1] If the trim is needed, that's a scary thought, because if you have to cut out the pitch trim breaker for whatever reason, it means the airplane is pitch *divergent* during a powered on stall. There is no way to get out of it without reducing power first. I can't imagine any plane would pass certification with such nasty behavior. But if this is indeed true for the /800-NG, then I could absolutely see why the 737-MAX would have MCAS moving the trim so that when the pilot pushes the nose down to recover, the stab trim is already where it needs to be. There is no lag/delay while the jack screw is winding up and the plane is fully stalled. It will save a few vital seconds of spool time.
@@cabdolla " There is no way to get out of it without reducing power first." I watched that video, IIRC that is exactly what Mentour Pilot said. Is that correct?
I rewatched his video, and if you look carefully, he actually did a powered OFF stall, and he easssssed the power back in. That's very different from a powered ON stall where the engines would be producing maximum thrust and pitching the nose up. I kept carefully listening to his words over and over again, and I was not convinced he said the NG behaves that way, but instead that he was thinking the max might. It was not explicitly clear, but Juan would be able to know for sure. Also, Juan, you said in this video the MCAS would put the power full throttle when the MCAS turns on, that would not be true. As far as I know, the MCAS does not interplay with the throttle, and if it did, going full throttle would worsen the stall because of the pitch up tendency at full power. It would make more sense to cut the power to half and once the AoA is below the critical value ramp the throttle back in slowly to avoid a secondary stall. @@ediartiva
As a retired airline pilot and mechanic, I have to say this is the best and most complete explanation of the potential root of these accidents I've heard yet. This sounds like a simulator training session from hell. With pilots having multiple symptoms that they don't realize are related. Much of our simulator training serves to train our muscle memory to react instinctively to the most likely sudden events such as engine failures. When presented with a novel malfunction, we have to rely on our knowledge of systems to even know where to start looking in the manuals. Unless the aircraft annuncitates the nature of the problem, valuable time is lost trying to identify it. I spent most of my career in DC-9s, which didn't have the pitch up tendency when adding power. I learned about it on the 767.
FYI, Juan, you've managed to gain the respect of five former (all long-retired) avionics support engineers, and industrial engineers, myself included, all who've supported the production of avionics systems for at least ten years. Thank you for providing a well balanced, honest view of the situation. The news organizations would do well to adopt your methodology.
I just replied to another comment by someone dumping on the news media. Maybe I just don't go to the kinds of information sites that provide fake news. (I subscribe to the New York Times). If you wouldn't mind, could you please provide a few examples of unbalanced, dishonest reporting? (I mean from a reputable news source.) It should be easy to find, if what you say is true. Thanks. :-) I realize there are problems with misinformation on the internet, but I'm finding that the wrong people are being blamed for this.
Unfortunately there is a certain amount of fear in trying to understand complex things so when the news media does not understand they have a tendency to act surprised and fearful. Fear drives a lot of misinformation!
Juan, this has to be the most fact-filled and technical explanation of what happened to these two aircraft and you were able to put it out there in language everyone is able to understand. Even the NTSB couldn't do a better job. You are a truly gifted journalist. I eagerly await all of your reports. Keep up the excellent work.
40 years in the aviation business as a research and development aerodynamics engineer, airline operations engineer, and engineering test pilot on every category of aircraft from small bug-smashers to jumbo jets. While all of us can go on for hours discussing system design, operational details, and lack of pilot awareness and training, the fundamental underlying cause of these accidents was schedule and budget driven by short-term business goals and stock prices at the expense of comprehensive system design and testing, coupled with limited resources within the FAA. To avoid these kinds of accidents in the future, the FAA needs more resources and the manufacturer's ability to self-certify needs some serious critical analysis and oversight. Very nice video, sir. Well done!
G.K., I agree with you. Should Boeing have been left to self-certify? Not a chance! Boeing had an accident (I believe in the 1990s or maybe a little later, due to a rudder issue. The pilot correctly identified it, and handled it the way he'd been trained to do so - with catastrophic events. The plane clipped houses on Long Island before going into the water. Everyone on board died, as did some of the folks in the affected houses. (I'm going from memory here, so if I'm not totally accurate, I don't need to here about it). The point is, that Boeing knew about the problem and sent out a memo to be distributed to pilots. Simulator training all of the pilots on this would surely have been cheaper than the lawsuits. Fast forward 20 or so years, and here we are again, with another problem that Boeing could have paid the airlines the cost of simulator training, and once again Boeing chooses not to give that clear hands on practice. The pilots were being issued a one hour course on a tablet. Either not all had taken it, or not all had yet been given time to take it. Once again, with catastrophic results. I hope the FAA has learned it's lesson once and for all. People have blind spots. Organizations do too. A lot of people died needlessly because of this.
I found his channel a couple weeks ago after sifting through all of the garbage 1-2 minute long videos from big news media outlets. They care about nothing but sensationalism. Thanks Juan!
Not so. Based on my own experience, this is a false accusation. I have the NY Times delivered to my house daily, and have read essentially ALL OF the information provided in this video, in some cases weeks BEFORE the Ethiopian Airlines crash. In particular on Feb. 3, when the Times ran an expose on how and why Boeing had rushed the 737 Max into production while selling airlines on the fact that their flight crews wouldn't have to undergo extensive re-training to fly the Max (which was a major selling point to potential clients). check it out: www.nytimes.com/2019/02/03/world/asia/lion-air-plane-crash-pilots.html I'm weary of people dumping on the "mass media" as if they are all the same. I subscribe to the NY Times, because I want to know what is happening in the world, and have the highest regard for their journalistic standards. The Times and other news services have been labeled the Enemy of the People. I find such accusations dangerous. (My comments are restricted to responsible journals, with strict editorial standards, such as the Times, WaPo, and the major broadcast news network, but EXCLUDES networks who have the word "NEWS" in their name, but then say they are only "entertainment", not news. That said, I appreciate the efforts put in by First Officer Juan Brown to provide this information on his RU-vid Channel. The information has been carefully researched and presented, and verifies what I've read previously in the NYT.
MendTheWorld - Great point, and I should have clarified that I was referring to mass television media that quite frequently does not take the time to get the details right. There is absolutely still some great newspaper reporting on topics such as this. But I reread your comments and noticed your strong political biases which should have nothing to do with getting aviation stories correct.
@@TeachAManToAngle But MendTheWorld is correct and an entertainment outlet passing itself off as "news" has no value in providing information to any audience. Meanwhile, any respectable outlet's editorial board can likewise be tainted by ulterior motives just the same. Neither of these issues have any relation to the work done by the *actual journalists,* if any still remain, in the publications in question! Only journalism is, sadly, the one squeezed by financial difficulties while punditry pays leading to uncomfortable arrangements and juxtaposition. Painting journalists, and partisan political hacks and operatives with the same brush just because they have to share the same space in a publication or outlet is intellectually dishonest.
Having watched your videos on the MCAS. My first thought after I saw the news of the last crash was “that must have been a MCAS problem why didn’t they just turn off the trim stabilizers.” I am not a pilot. I learned that from you. You have by far the best technical explanations for complex problems that I have seen on you tube.
I'm genuinely impressed with your resume. I'm in a medical field and was under the impression that pilot hierarchy progression is fairly straight forward, however it is now obvious that i was wrong. Having to undergo training on such a variety of aircraft over the duration of your career is truly impressive.
I wish your analysis was more widely publicized. I realize mainstream media thinks us regular folks are stupid, but we're not. Again, many thanks for educating us in such detail.
The idea of a 3rd pilot in the jump seat having a "big picture" view of things is much like a coach watching his team play. They're dealing with specific things happening and their own involvement, but the coach tries to see the trends and thinks of adjustments to make. It's a pretty good analogy.
I made the point that the traditional flight engineer would have likely picked this up. Not only was he a 3rd set of eyes his background and job made sure he took a different approach to assessing problems that focuses on the system rather than flying the aircraft. One thing is for sure, a flight engineer would have been very acquainted with MCAS by nature of his job. Furthermore earlier MCAS disturbances would have been of enormous interest to collegiate flight engineers. They really would have given Boeing hell on this.
Thanks for the 'refresher' on engine placement on the strut. I can't believe they only used one AOA signal! Didn't know what MCAS was until your explanation. Excellent graphics. Well Done! Lousy way to review past training, but a great service none the less.
The umpire description of sitting in the cockpit is more accurate than I’d like to admit. Commuting for work at the airlines has taught me how important it is to take a step back and reevaluate my SA. I can’t even count how many things I’ve seen missed while sitting jumpseat, and it made me think of how much I’ve surely missed. And as far as startle factor goes, I couldn’t agree more. Being 2000 afe and having a trim run away is scary enough, let alone the wicked nature of what an mcas failure appears to be. I’d like to think that I wouldn’t be lawn darting in that situation but I think given the situation the odds are definitely stacked against the crew. Rip. Thank you for your updates, it’s increasingly rare to find a channel with such thoughtful coverage. You have earned my subscription!
Juan, being a former resident of Paradise with lots of family that still live there I originally started watching your channel because of your reporting on the Oroville Dam. Then you're excellent reporting on the Paradise camp fire, in your true Juan style it was absolutely excellent I may add. As a civilian with absolutely no pilot experience I wish to commend you for your professionalism, extensive experience as a pilot and your detailed approach to everything you do especially being a pilot. Before I retired I did spend a great amount of time for business as a passenger in my career. Always knew that the pilots were true Pros. You have to be in the top of your field. Thank you for providing us your extensive background as a pilot. Getting to know you on your channel the last year-and-a-half has truly been uplifting in everything that you report on. With so much fake news and bias in our news media you bring the true facts to an issue. Thank you Juan it is greatly appreciated.
@@blancolirio Moved before the fire. Son, daughter-in-law, grandson and in-laws still there. They were one of the few lucky ones, their homes made it. Most of the homes on my son's street are now gone. All other friends and family members lost their homes. Again thanks for your reporting on everything you made a big difference with us being out of state.
I started watching you on the Oroville disaster since then have followed you these air crashes that you explain do a lot for the people like me who are just normal people that are not in this feild , thank you for what you do will always read your comments very informitive.
At 11.25 sitting between the pilots on the centre jump seat -that's what we flight engineers did. It's a great overall picture. Bring back the third set of eyes!!!
Excellent presentation. I wish my ground school instructors had your linguistic and technical skills. Retired pilot - DC-9, B-727, B-757, A-320, A-330.
The jump seat pilot who prevented a crash reminds me of the late, great Denny Fitch in the Sioux City Iowa disaster. His presence was widely credited with the DC-10 landing well enough to save many lives. It is unfathomable that one Lion Air crew could save their jet from disaster yet not pass the information on to the next crew and indeed the rest of the fleet. If true, this is a cardinal sin. Of course Boeing deserves a ton of criticism for their bungling, too.
Boeing/Airbus automatically receive feedback of many vital signs of modern planes directly live through satellites. Letting that fresh new plane go back out after the 1st near crash was... not too professional.
@@sithus1966 Actually there's a really good source of authoritative information that loosely details this entire Lion Air crash and gives critical information even about the flight of that same 737 into Jakarta six hours earlier where the newly revealed hero saved the (day?) night actually. The saved flight landed just minutes before midnight. I can't seem to open the link today but I spent time on that website yesterday so I'm thinking it might go back online soon. reports.aviation-safety.net/2018/20181029-0_B38M_PK-LQP_PRELIMINARY.pdf
Sithus1966 it’s been a number of years since I flew in 135/121 operations, but I seem to recall a part of the preflight process is the captain has to review the maintenance logs to make sure all discrepancies are appropriately dealt with... either via maintenance to correct the issue or deferred via the MMEL as appropriate. The landing crew probably thought their issue was a one-off anomaly and wrote it up and let overnight maintenance deal with it.
The C-130 is an amazing aircraft. In 1998 I was stationed in Oman as part of a detachment flying C-130 supply missions across the theater for Operation Southern Watch. At one point we landed in Doha to unload a generator. When we got the go-ahead to return to Oman the metal gear on the starter for engine #2 snapped off. After waiting around for a few hours we eventually got approval from Headquarters to do a windmill start. I was a young ammo troop at the time and didn't know much about the C-130 so it was pretty scary. But it started right up about halfway down the runway without any issues. That's versatility!
Yet another excellent report, Juan! Keep up the great work! You provide a very good description of the tunnel vision when faced with handling an unexpected situation. I'd add that not only is one's "picture" restricted in lateral/subject scope, but also in time. One's time horizon collapses, so one cannot see very far down that tunnel! The first time I was faced with an aircraft malfunction, I experienced this effect. (Before that incident, everything that had gone wrong during my flying had been my fault!! So that was the first mental hurdle!) I'm a low hours (and now long lapsed) private pilot (350 hours in total, and less at that time). I had a pitch trim malfunction in a TB20 (Trinidad). It was not even a runaway, it had simply jammed. Even so, when climbing out, as I unthinkingly routinely cleaned up the aircraft, increasing forward control force was required to keep the speed from falling too low. Also routinely, my thumb was planted on the electric trim switches, but this was having no effect. As you describe, a pilot who is not flying maintains a broader perspective. Luckily my front seat passenger was an instructor and examiner, who immediately recognised that I had a problem. After we'd made a fairly quick diagnosis of the problem, he asked me whether I wanted to turn back, which I did. Later when we discussed the incident (which, by the way, was caused by a riding turn on the cable drum), he asked me about the decision to go back and whether I'd already thought about that. My response was that I had not thought that far ahead!! Before takeoff, my time horizon had been approximately the duration of the planned flight, about an hour and a half. That fault caused my time horizon to collapse, probably to less than ten seconds!!
What a resume! You can not believe how much I look up to you Juan! I myself: 26 years old, belgian, architect and lifelong aviation geek. Only a year ago I finally made the decision to start flying gliders, let’s see where this takes me. You have a fantastic channel and you are an amazing reporter. Thanks for sharing your knowledge!
As someone who designs and troubleshoots industrial automation control systems, I see 3 problems here, 1 of which doesn't seem to be directly mentioned very much, which is unreliable AOA sensors. None of these incidents would have happened if the AOA sensors were not faulty, so they need to find out why they are failing, and correct that issue, because this is an unacceptable rate of failure indicating a poor design or testing process. Second issue is lack of user training after a material change in the function of the system, because the scope of the change was underestimated. The third, and most important, and most egregious error is in making the control logic not fault tolerant. I run into this a lot when I am called in to correct a system that is misbehaving, and usually I find that the original programmer did not plan for faults, and assumed that all inputs and outputs would be reliable and within a certain framework. Basically, you have to remember that a logic control system is Infinitely creative. In other words, if you tell it to perform a certain function, you have to think of all the possible ways it could be triggered to perform that function, and program out all the ones that you don't want to have happen, and try to predict all the possible failure modes, and have a plan for them, because if you don't, the system is going to respond, because that's what logic systems do, they respond according to the inputs, with no regret. And if you simply do a textbook "if Switch A is activated by Part B, then perform Action C", how are you verifying that it is Part B that is being sensed, or that the machine is in a safe condition to perform Action C? For instance, one machine had a large frame that moved back and forth on a track, and it had a limit switch at each end. It was programed that if it sat on the extended limit switch for longer then 5 seconds, it would power it up to retract it to the safe home limit switch. This was done as some sort of fault recovery routine, with the designer probably thinking that he was really smart coming up with this to make sure that it would default to the home position. The problem was, he didn't look at anything else before acting.. The routine was simply that if the extended limit switch was tripped, the unit would retract. It didn't look at whether the machine cycle was active, or whether the Home limit switch was already tripped, or anything else. So every couple of days, the unit would randomly retract past the Home limit switch, and would over travel and get wedged in before things would trip. And then it took some disassembly to get it back where it should be. I set a camera up recording the input status on the controller, and the next time it happened I saw that while the system was idle with the home limit switch tripped, the Extended switch input would come on and crash the unit. After I found the routine mentioned above, I started testing switches and checking wires, but the switch was brand new, and I couldn't locate the intermittent short that I suspect was in the wiring, so I added a command that it would only run the routine if the unit wasn't already Home. (they were going to dig deeper and find the short in the wire, but the system never had that problem again because I had made it more aware of the rest of the inputs.) Another system I had fun on was an automatic truck wash (like a car wash, but for semi trucks, and more complicated!) It had been programed to assume that if a photo cell was blocked, that meant that a truck was that far through the wash, and would activate whatever components it controlled. This is great as long as everything is clean, but when soap scum or hard water deposits start building up on the sensors, residual spray from the 50 horsepower oscillating pressure wash nozzles is enough to trip a partially occluded sensor, activating stuff after the truck was gone, and sometimes it was the sensor that activated the spray, leading to a constant cycle. Fault tolerance was created by including the previous sensor in the logic, so that if the previous sensor had not been tripped, it would not activate, ensuring that things happened in the right order, and it would take multiple consecutive faults to cause unwanted behavior. In this case, it sounds like there was no thought to what would happen if the single sensor failed, so no checks of other plane systems, no checks of what the pilot input was, no comparison of redundant sensors, just a simple single line of code, "If AOA exceeds Angle A, then activate Stab Trim until Angle is less than A". Simple and stupid, and works great, as long as all of the inputs and outputs are trustworthy.... It almost sounds like it was a rushed afterthought, and it either was programmed by someone that didn't understand Fault Tolerance, or it was the first rough draft of the program, but the guy was put on something else, and no one completed it or it was rushed to production. They may have also justified it as not needing all that extra complexity, because if there was a fault, the pilot would know to shut off the Stab Trim because that was already a memory item, so it didn't need to be fault tolerant. If I were in charge of redoing it, based on the information I have, I would set it up kind of like how a lot of autopilots are, to fail neutral. So it would look at both AOA, and the pilot's input, and the Stabilizer position, and would take action based on which ones agreed the closest, and was the least severe control input. And then at the same time, would alert the pilots that there was a sensor failure and that they needed to take charge. For instance, if the right AOA was within normal readings, and the pilot's inputs matched the right AOA, and the stabilizer position matched both of them, but the left AOA said the world was ending and we are all going to die, then it would pat Marvin the Depressed Sensor on the head and give it a Valium, and fly according to the right sensor. Of course, a big part of fault tolerance for something like this, is training the pilots in how to respond to faults, how to recognize them, and give them the information they need to spot them. For instance, have an indicator so that they know that the plane thinks they are stalling, instead of just taking action without informing the pilots. I would be really interested to hear the story of how this ended up like this, who dropped the ball and what the reasoning was, but I suspect that will not be made public, unless it comes out in the lawsuits. But bottom line as a control system designer, this system was not properly designed and integrated into the system and flight crew, and that is the ultimate cause of these crashes, even with the aspect of the poor maintenance culture before the first one, and possibly bad training for the second one, because the technical side could have been so much better and taken those into account.
" Pat Marvin the depressed sensor on the head and give him a Valium" Lmao. That was a long read but well worth it. Yes Redundancy. I don't understand how they could use only one angle of attack sensor to run this system. Anyway... next time I'm troubleshooting any sensor related problem I'm going to use that quote.
re: "a control system designer, this system was not properly designed and integrated into the system and flight crew" bingo. it was clearly MCAS rev 1.0, it was not tested, not vetted, and the code was likely not even written by anybody who was a pilot. having fitted 2 AOA sensors, and then both data streams not being fed into the control logic is an obvious RED FLAG. and really there should be a 3rd sensor used of different type (think gyro) fed in as a check/tie breaker in the event of a DISAGREE between the 2 AOA vanes. that or if in the event of a disagree between just the 2, then the system throws a warning, disconnects, and the pilot then has to "hand fly" the plane, which he should be doing anyway during takeoff.
I was thinking the exact same thing when listening to Juan explain the MCAS. THEY MAKE IT DO THAT?!? Absolutely insane. Automating flight controls to the extent that a pilot can't overpower them WITH NO REDUNDANCY, self- checks or announcement begs for the crashes we have seen. Boeing really, really pulled a boner on this one. Glad I don't own company stock.
That was the most interesting thing I have probably ever read in a RU-vid comment haha. The video made clear how and why the system responds, why it was made, and how the pilots would handle it or react, but your comment was really fun to read, in what goes into making and designing a system like that. I do not have an engineering brain or even a clue about planes, but I completely understood what you were saying and I was made much more intelligent by your experience and insights.🤯
I found your channel back when you first started describing the Oroville Dam problem. Just wanted to say how much I have appreciated your very clear reports and your commitment to getting things right. These latest explanations of the 737 Max crashes and MCAS are excellent. Thank you for all you do to get good information out there for all of us. And, as a flying enthusiast, I love the way you've used the Mighty Luscombe in your channel. Keep it up!
I too subscribed to this channel just on the Orville Dam coverage, little did I know Juan was a commercial airline pilot which my dad was too and I fly as well so this channel is exponentially multifaceted. Love it, enjoy it and even under stand it, Juan you rock man and you're the best!
As a non pilot aviation enthusiast I have to say this is a brilliant explaination of the MCAS system and how it would appear to have caused the two 737 MAX crashes. I had picked up a lot of the information from several other places but this makes it clear and understandable to the layman. Thanks.
Thanks Juan...!! Just the FACTS Here..!! Since they found the jack shaft at the end of its travel, in the full nose down position, obviously the pilot and FO did not shut off the Stabilizer Trim system or manually override it. You can see there are switch lockouts at 1:13 that need to be pulled out and then you can turn off both switches. I bet this will be a huge lesson modification for pilots when doing annual Simulator Training for this kind of 737. as well as Boeing making software mods to the MCAS.
I am a retired biomedical/electrical engineer and I can say I've been there and done what I think you are describing-- fix a hardware issue with software. It can be done but you're on thin ice. As to why use one AOA sensor when two were available, words fail.
It pretty much depends on what sort of problem it is. A noisy switch can be de-bounced in the system software, but a noisy system power supply cannot be filtered by software!!! The lack of redundancy is strange, I guess they must have assumed that the one sensor was reliable enough ... but obviously NOT!...
What a tragedy. It takes just seconds for the pilot flying to call out "Stab trim cutout switches...CUTOUT" and the pilot monitoring to whack those switches. My company would probably listen to the CVR (they copy and archive 800 hours per plane, audited regularly) and give the pilots a rash of hassle if they don't call "QRH Runaway Stab Trim" first. As you say, that procedure doesn't fit an MCAS malfunction. Figuring out what's wrong delays remedial action enough for that trim jackscrew to go to the full nose down stop. That Lion Air jumpseater, who helped save the prior flight, should never have to buy his own beer for the rest of his life.
We couldn't get 1/1,000th that type of information on the mainstream news! Appreciate you taking the time to thoroughly explain this MCAS system. 👍👍 Sure makes me wonder if Boeing will be sued big-time by the families of crew and passengers of those lost thus far. From where I'm sitting, they engineered a death trap, especially by not FULLY explaining this system and how it functions. I recall not long after the Lion Air disaster, American pilots were asking alot of questions about this system, and weren't getting very many answers. Seems to be a trend in manufacturing today, where the manufacturer wants to keep everything secret. That may work for a while in land based machines, but there's no "do-overs" in aircraft at any altitude, especially lower. Thanks for the great insight! 🍻
I appreciate your updates. I’m a retired UAL B747-400 Captain, former US Navy pilot and FAA Aviation Safety Inspector. I have more than 22,000 hours of total flight time in the DC-10, B727, B737, B747-400, B757, B767, CE-500, SK-61. During my career at UAL I was Vice-Chairman of our ALPA Central Air Safety Committee and ALPA Chairman of our FSAP Committee. In that capacity I was part of the UAL Accident Investigation Team. I have one problem with this entire discussion. There has been no discussion of the basic lack of basic stick and rudder skills. We have all been taught to turn off all of the “magic”, autopilot and the autothrottles, and hand fly the aircraft when everything heads South. In the Ethiopian accident N1 was left at 94%. I wonder what would have happened if these pilots had reduced their thrust, turned off the autothrottles, autopilot and pitch trim and flown the aircraft manually? All of the “magic” will take you places you don’t want to go and fast! Keep the updates coming, they’re greatly appreciated. JH Schmitt
I've been a subscriber since the Oroville disaster and since then you have offered a front row seat to the spillway reconstruction, then Paradise fires last year, and now these airline disasters. Truly amazing commentary. I must say that this overview is providing an even more damning account of Boeing's pure neglect in the development of this aircraft than is being reported elsewhere, and the reports elsewhere are already pretty damning. They are in a LOT of trouble with these catastrophes, and the US government and FAA oversight comes out looking awful as well. Yikes.
I feel as though I have just been in the classroom of a very good professor. Thank you for the lesson sir. As far as I'm concerned, you deserve tenure. And a raise. ;-)
When Jaun was talking about the perspective of the pilot in the jump seat, it reminded me that one of the pilots in the jump seat of the 777 that crashed at SFO was the only one that expressed concern about low speed, prior to the crash, as I recall. I'd love to hear Juan talk about that crash! By the way... I'm always envious when I hear someone say that they knew what they wanted to do from an early age. I'm still trying to figure out what I want to do when I grow up!😊
I am just left mystified by the whole thing. The potential for stabilizer runaway events has been there since the advent of electric stab trim. The procedure for a runaway event, including two readily apparent, easily-accessed set switches, has not changed on the 737, so far as I know, for decades. Obviously the MCAS system needs some correcting, but the media frenzy over Boeing and the FAA seems to be missing the known facts entirely. If a crew of a MAX or a non-MAX airplane doesn't know how to stop a runaway event, and I do without ever having been rated on a 737, what does that strongly suggest the problem is? Maybe the same one that has attended developing-world airlines for decades, except this time it has proven to be true despite having new equipment as well?
@@UncleEarl97 Actually he saved that plane only about seven or eight hours before it crashed. It was a short midnight to six AM turnaround despite maintenance issues.
Thanks blancolirio, for explaining several points for which I needed clarification and explanation...! Re: Redundancy of AoA sensors: It is my understanding that Airbus uses 3 AoA sensors, so that in the event of a single sensor failure (the most common scenario) the flight control system will use input from either of the two sensors that AGREE with each other, as a failure of two sensors at once has the LEAST likely probability. However, two included sensors are enough if MCAS is not flight-critical, and if it shuts off if the two sensors disagree, to be repaired later on the ground. However, if the MCAS is critical to avoid stalls in the 737 MAX then 3 sensors installed with isolation circuits (so that a 2 sensor failure is least likely) would be the safest. At this point, we have to acknowledge the comments of Sully Sullenburger that it is still important that cockpit crews can fly aircraft manually when systems such as MCAS fail, and are trained thoroughly on how to disable non-functioning systems. Also, the Seattle times has pertinent information about the dialogue between the FAA and Boeing, with regards to the safety certification of the MCAS system, which is still relevant: www.seattletimes.com/business/boeing-aerospace/failed-certification-faa-missed-safety-issues-in-the-737-max-system-implicated-in-the-lion-air-crash/ and a rephrasing of the Seattle Times article article from nymag.com, regarding Boeing self-regulation: nymag.com/intelligencer/2019/03/report-the-regulatory-failures-of-the-boeing-737-max.html I hope Boeing gets it right before these planes fly again; not just for their bottom line, or for their shareholders, but for the 346 who will never fly again!
Excellent discussion of the facts to date. I've followed this closely being an engineer. The design process for the 8 and 9 Max, from all I've heard and read thus far, appears to have had a serious deficiency in the Single Failure Analysis, including software hazards analysis, and failure modes and effects analysis of the MCAS system design (hardware and software). No way a single failure (AoA sensor) should have led to a catastrophic loss of control of the aircraft. And someone decided in software that the pilots control input via the yoke should not defeat MCAS? And no one thought that MCAS action should be limited? Terrible, terrible design flaws in the software. And lets not forget that now there have been 2 failures of the angle of attack (AoA) sensors on the Max planes - that component almost certainly has a design flaw as well, but no ones talking about that, at least publicly. Another problem is the design itself - engine and engine mount changes. If you have to develop software to overcome an aircraft control issue for stable flight, you just might have a shitty design. And last but not least, these changes were significant enough to require training for the MCAS changes, and clearly addressed in the POH and quick reference. This should have been treated as a new type aircraft based on the handling characteristics of the re-design and the required training provided. But everyone wants to save money, so Boeing and the FAA determined it was not a type change.
Yeah they purposefully understated how much training was required so that it would seem more attractive against the a320 neo. And it worked they have over 5000 orders.
Excellent video, Juan. I am an experienced commercial/instrument pilot keeping up with industry developments. In your well paced, informative video I learned at least four new concepts relating to this MAX 8/9 situation, a rare grasping of knowledge for me from an Internet video. Congratulations for your fine service to the industry and flying public.
This has to be the best 737 MAX explanation video to date. Time to bring Boeing HQ back to Seattle and replace the bean counters with engineers; I say. Nice to hear your extensive flying background too; what a fascinating extensive career you've had. Thank you!
You're right. I was living in Seattle and can still recall my surprise when Boeing corporate moved to Chicago, where the firm builds no planes. I suspect one of the factors will turn out to be poor communication between the management and their engineers, separated by half the country.
This is the most thorough discussion of the whole problem I have seen yet. Thank you. I listened to the whole thing. One point of controversy still being discussed is whether putting these more powerful engines on an old airframe, requiring (for some reason) automated trim adjustment, is in itself a design error. I am sure that MCAS can be made safe, but should it have been done at all?
I'm really enjoying the level of information you are providing in these videos. I don't normally comment because it's already been said, but felt compelled after this video. Well done. I found your channel when you were talking about a KTM dirt bike, but I find this information very interesting. Thank you.
Hey!!! Thanks for the unexpected rundown of your resume! I was actually curious as you had mentioned Air Force, but I had never heard you elaborate. Best Wishes and Best Regards!
Great video and technical briefing Juan. Thx for your military service and your outstanding results of keeping all of us acqurately informed. Safe Travels to you and yours.
Juan, I have been looking all over for a comprehensive intelligent overview of MCAS system including engine history and finally you did it! Thanks so much, an outstanding job!
I have a full certification on a canoe, but,, I am very well read and have remained interested for a lifetime. Your description of cause and result I find faultless. I found and viewed this video because I already respected your skills and ability to explain. Thank you. And you did touch upon it,, the MCAS is more than just an assist and warning system. It is capable of over ruling a pilot if faulty data is entered, without redundancy. This touches upon exactly what I have been seeing/surmising. If I understand correctly, you will know, the original to the MCAS, the pilot could disconnect the system by pulling the yoke to full back,, a highly intuitive move that would simplify recovery and gain precious time. Time to then pull out the loose leaf book and run a check list while the plane is out of danger and flying under normal manual or autopilot. The MCAS is the first system I am aware of,, you likely know of more,, that can actively over ride a pilot and control the plane into something undesirable, dirt. The intuitive response of yank the yoke all the way back, was, and should be the the first line of disabling the system. Not just mute the system, or enter the redundancy of both AOA vanes, but cut out the stabilizer computer control,,, AT a minimum,, long enough to find and run a check list. MCAS is not a stick shaker, not an announced warning of "Too slow.",, or "Pull up.", it is not assistance or advisory. It is not a safety system. It IS a pilot cut out system. It stands between a pilot and his or her control of an aircraft. And that is fundamentally wrong. Even reprogrammed,, pilots should refuse to fly it.
Sailor376also Very good analysis! There is a news article saying almost exactly the same thing: A news article suggests that an important change to the control column stabiliser trim cutoff switch may have made recovery from a faulty MCAS activation more difficult: www.reuters.com/article/us-ethiopia-airplane-controls-explainer/change-to-737-max-controls-may-have-imperiled-planes-experts-say-idUSKCN1R322M
Thanks for that crystal clear explanation of the MCAS system. I'm frankly staggered by what seems to have been an inept implementation of this system. I thought that EVERY automatic system had to be redundant and also handle what to do in the case of conflicting sensor information. Doesn't Airbus have a 'best of three' for precisely this kind of situation? It looks like Boeing have really dropped the ball on this one by not only making a fragile system but allowing it sufficient power to overwhelm the pilot's inputs. It's hard to know how their customers will ever have confidence in this system. This is a big enough issue to cripple the company in my opinion.
I found you during the Oroville spillway crisis and have followed you ever since. Your excellent unbiased reporting, knowledge of the issue, and clear explanations are a rare combination that you have. I thoroughly enjoy your reports
Excellent Job! The wife and I understood it the first time. The Umpire seat has a different perspective also, good point. Very well explained to civilians.
Excellent video and great information. I am surprised that the computer controlling the automatic control system would not automatically shut off or decrease its adjustment when a pilot has reversed the automatic control adjustment two or three times in a row. Logic would prevail that the pilot should have the final control! Especially if there were two pilots making the same corrections against the automated system. Sometimes computers do not make the right decision because of bad input from instrumentation. I have 32 years of PLC programming experience developing automation controls for a crude oil pipeline.
Juan, an absolutely clear update on what is progressing on the 737 Max situation. As a former military pilot and instrument instructor, I can state your clarity on the issues is outstanding. Thank you.
Very interesting as usual Juan. You almost made me feel like I was in the cabin with the pilots. Thanks for telling us about your life too, lots of respect for you.👍
Great stuff, Juan. My wife and I are pilots, we sat down and talked about this one for an hour or more. I think we have it: To keep cost down, airline manufacturer company modifies a plane with new efficient engines that have the side effect of causing the plane to pitch up. To keep the plane flying as close to what it used to fly like, you add a little system (mcas) to counteract this pitch up issue. If you didn't keep the plane flying the same as it's previous model, it would cost a ton of money to retrain pilots because it could even be consider a new type aircraft. So they add this little "minor" trim device to counteract the extra pitch up so they don't have to label this plane as a new plane/type, essentially. RIGHT? Failure happens because of inaccurate information from the angle of attack indicator/electronics reading a high angle of attack relative to the wind and the jack screw positions the horizontal stabilizer to put the plane in a dive position. At this point, full movement of the elevators can not negate the effects of the horizontal stabilizer position. (and yeah, one fix of that could be just to limit how far it can pitch the stabilizer and still have the elevators be able to overcome that aerodynamic pitch) How did we do? We think that the extra pitch up issue must be significant because all pilots would know how to control the nose of an aircraft as you climb out. That is fundamentals of flying, day 1, climbing out - no new training needed. However, again, we think it must come back to keeping that plane's flight characteristics as close as they can to the previous model ..... to avoid a new type certificate.
We have a friend whose son joined the USAF following in his father's footsteps, had much the same career as you although he is still in the AF & flying C130's. Always enjoy your videos. Thanks for making a foreign subject seem simple & logical. ~ from Cut and Shoot, Texas, Richard.
do you think Boeing knew? ignored advice by engineers? the information I've been exposed to about the dreamliner makes me think so. I've just discovered your channel and I've gotta say, you have explained every aspect of all the angles, see what I did there? better than any other person tv show, reports and the ntsb. thank you so much.
I am surprised that the MCAS could overpower manual override without disabling the system. I would think that in an emergency, you may not have time, or the presence of mind, to flip the switches as you are trying to correct things, and to have the MCAS be all that powerful seems like a bad idea. Also, why is the system relying on one sensor without redundancy? That seems like a bad design choice also. Thanks for the outstanding explanation!
Thanks again Juan Juan, would you be interested in my recovery and survival of an total elevator disconnection at 50 feet after take of in a BE58..?? Hearing your thorough and comprehensive explanation has reminded me of the terrifying low altitude fight for survival that I went through for 45seconds and crashing 1.5 kms from takeoff.... Aircraft was totally destroyed but the cabin was intact and we all survived with no injuries.
GNX157 ......Hello, in Australia we don’t have NSTB just an incident or accident report. This incident happened in out-back Western Australia near Lenora July 1 1986.
Juan my background is Air Force flight engineer 22 years. 121ground instructor on the 737-200-300-900-max. 29 years. Everyone is talking about MCAS and then describing it to 800 SMYD system. My Manuel’s don’t even have a description of the MCAS system in it. I don’t know how the system actually works, I haven’t seen a schematic nothing on the max system. I can only compare to the SMYD system that is described in the 800 manual. How do I train pilots when I don’t have the the description of the max MCAS system. Thanks for your videos on the subject. As flight engineer that was my job to be the 3rd set of eyes in the cockpit and run the systems maybe we need that redundancy of the human kind.
Jesus. Non-aircraft controls engineer here. At the very least, a unique audio sound that you hear when MCAS is operating. (Adjustments being made). Whoop whoop or something like that. Oh, I know what that is. Or, stern voice MCAS MCAS MCAS. You know, like terrain. That schematic and flow chart could also be flashed up on the glass cockpit. Not static, but graphically active. Minus minus flashing, or plus plus flashing overlaid on the MCAS section. These are all pilot alert improvements. Fundamentally, you should need both sensors to agree. If the two sensors do not agree, MCAS dumps out, like autopilot dumps out when given conflicting sensor data. I also like dead simple disaster check cross sensors: If your angle of attack is truly that far out, hell, a bubble sensor will agree. It won’t tell you how many degrees to sub minute accuracy, but hey, yeah your pitch is “truly” that far out. Higher tech cross check sensors could be of the inertial type. (Popular for military applications before GPS.) Millimeter radar is extremely accurate. What is the altitude of the tail? What is the altitude of the nose? Again, you are not adjusting based on those sensors; you are disaster checking. Are we really that far out of our angle of attack envelope?
@@daviduschock1464 The bubble will work to inertial or gravitational pitch (I don't know what terminology to use, but I think you will get the idea), but not relative to air. Also, the spinning of the trim wheels right beside the pilot should be very obvious I think. They are large and noisy and have a high-contrast strip on them. Whatever the cause, it should have been obvious that the trim was being grossly adjusted. If I am wrong, please correct me here (pilots?)
I like the how question. But I have a why question. Why was Boeing so non-communicative with pilots regarding the MCAS system through the training manual(s), and perhaps other channels, from or before the very first deliveries of this new 787 model??? Care to speculate? It seems criminally negligent to me for Boeing not to have communicated to pilots what this system was all about. It blows my mind.
@@simian_essence I may be wrong but I believe the MCAS is designed to reduce pilot workload, not something that they should have needed to worry about coming on or off, just a system helping keep the nose down on throttle so you don't have to do it manually. If designed to work in the background I can see them not stressing training on that system, I imagine there are many things going on in a modern airplane that the pilots are unaware of the ins and outs of how it works.
Not sure if you could answer this but would the pilot have a visual indication of the readings the AOA sensor feeding MCAS or is that fed directly to the system with no instrument to compare against the other AOA sensor(s)?
Great videos - many thanks! Your comments about the "third seat" perspective remind me a lot of the unique help the jump seat pilot had on the 1989 Sioux City IA UA crash. His help wasn't the only thing that saved a lot of those folks, but it did help a lot (if I remember correctly, he was also a trainer). Coming at this from an old IT perspective (having worked in silicon valley and had friends who were programmers for Boeing back in the 90's), this is really a very sad situation. Getting feedback from only 1 sensor, no matter how well it's made? There's a lot here to be unhappy about. I remember reading professional software design journals back in the 90's that detailed software design errors that crashed a few aircraft of that era. Some were horrific losses of life like this.
I can see you were an awesome instructor. You told us everything thank you. Boeing will just have to admit the mistake and accept responsibility. Replace top management immediately and hope the customers that buy this Airplane forgive Boeing by not canceling anymore orders. Condolences to the families of the victims. Could not have come at a worse time for Boeing when Airbus is doing well with their new Airplane. The FAA is another story and should be held accountable.
Seems the real problem is the overall design of these new aircraft affecting the flight characteristic thus requiring the mcas system to control it. Not just the MCAS. Need to junk these aircraft and go back to the dwg board. Won’t happen though.
One of your best Juan, thank you. So good to get these factual reports from someone with the amount of flying experience you have. First thing I learned about when I got involved in avionics was something called dual redundancy. I was thus quite surprised to hear you confirm that Boeing took the input from only one AOA sensor. Interesting points you raised about the 3rd/4th pilots wider view too, that's something us non flyers would not have considered. Good to see the subscriber count zooming upwards - keep those wackadoodle trolls out, you're doing a grand job.
@@eugeniustheodidactus8890 We called the original engines "Salami" due to their appearance. They were long and relatively thin(non bypass JT8D) powerplants in comparison to the later engines on the "classics"(-300 and up).
Doesn’t or wouldn’t Boeing have experienced pilots working with the engineers who designed this system to brainstorm all the potential problems that could occur in flight before putting a system like this in the cockpit? ....man that was some wind and rain. Excellent analysis.
One would think so... It's one thing to do all design and testing with the assumption that all will go well ("What could possibly go wrong?") and quite a different thing to PROBE for design weakness and hidden assumptions. Search on "Red Team" or "Red Teaming."
Part of the problem Boeing seems to be having is in governance. The CEO is also the Chairman and also the President. This doesn't make sense for such a big company. Weak FAA oversight aside, there doesn't seem to be any oversight mechanisms either at Boeing to check final decision-making even at the very helm of the business.
You have done a superb job explaining these latest crashes which is a bonus. I originally started following your updates on the spillway and never realized your flying background, quite impressive I must say.
Thank you Juan. I appreciated Mr. Sullenberger's statements regarding the Boeing/FAA possible, (or likely) conflict of interest also. It's a nightmare situation, and I'm sure it's hard on most, if not all, commercial pilots. My best to you and your loved ones.
Excellent report as always Juan. Factual, informative and no "sky is falling" hypothesis statements. Wish the big news agencies had your level of professional journalism.
Started following you since Oroville Dam first cracked. I appreciate how informative you are about all these matters from airplanes to wildfires to infrastructure.
My dad's first plane was a Taylorcraft back in the late 70's. He loved that thing. Puts lots of hours on it and it was the first plane I ever flew. He finally sold it to buy a 172 and later a Bonanza for family flying but always regretted selling the Taylorcraft. He's 82 now and lost his medical because of a heart attack, but he knows exactly where the Taylorcraft lives. Has followed it around all these years. His health is good now and occasionally he'll talk about getting a sports license and buying it back. The owner doesn't want to sell and I'm not sure dad is all that serious about it. When he had the heart attack and subsequently sold the Bonanza, he had around 6,000 hours and I think some of the fun was gone at that point. But the passion returns occasionally now that he hasn't flown for some years. And it's the Taylorcraft that rekindles it. Great video and good recap on the update. Thanks for sharing!
Appreciate your "Pilot's Perspective" on this and the background on your years of experience. Seems like Boeing has made a ladder of mistakes that have added up to 2 disasters that could have been avoided. As always you tell complicated stories in a very clear and engaging manner, Keep up the great work.
Excellent very informative report Juan! You answered the simplistic thought I had of why didn’t the pilots simply cut off power with the Stab Trim Switches. You gave a good perspective on the nature of the urgency of what’s happening, the conflicting information they’re getting, and the limited time to react. Thank you. Keep up the great work.
Ron Grossjan Agree, similar to the portrayal in the move Miracle on the Hudson, if the simulator crew was told what the problem was beforehand, they could return to an airport, if they went through the full diagnostic process and time elapsed, the only correct choice was the Hudson.
Great perspective from a very experienced pilot. Mainstream media doesn't take the time to explain what a pilot will experience in such a situation so low to the ground. I flew out of Bole' on way to Cape Town a year ago on Ethiopian. Very experienced, professional crew. Taking off at 7,600 feet was interesting as well. The fatal Ethopian flight never got more than 1,000 feet off the ground. Imagine the responses and the physical exertion that the pilots had to go thru even if they knew how to shut off the stab trim. I explain it to folks by saying, "imagine if you are on a mountain road and you approach a left hand bend and when you turn left the car overrides you and turns right. And the harder you turn left the harder the car overrides to the right. The entire time the car automatically starts accelerating. Would that get you confused even though you know you simply need to turn the car off or hit the brakes?" Thank you.
Thank you for taking precious time to explain these unnerving accidents. For those of us, just civilians who have to fly time to time, you bring us some understanding ,peace and more confidence in our pilots.
Thanks ever so much for the most cogent analysis and explanation of the 737 Max issues that I've been able to find. As an old RC-135 guy I've always been partial to Boeing aircraft but the Max problems have shaken my "if it ain't Boeing I'm not going" opinion just a bit. Your latest update really clarified what's going on from a commercial pilot's 'no BS' perspective.
Juan, Started following you during the Orville dam spillway emergency, that was very informative, thank you. I have good mechanical knowledge both applied and theoretical thanks to my career as a industrial HVAC tech and through many hobbies. I've also had a lifetime interest in aviation and aerospace, although not a pilot , have had some Cessna seat time. That said: Your doing an outstanding job explaining the details and situations regarding these incidents. The average person should have a better understanding of whats really happening after watching your videos. The news media is generally clueless and just repeats talking points with no understanding of what there reporting. Thanks for great work your doing. I've made a few videos and know how much time and effort it takes. Again Thank You, Please keep them coming! -Dean
THANK YOU Juan, I'm amazed there is only one single analog AOA device, when an electronic accelerometer/gyro could be a quick, tiny, and easily installed backup. "Accelerometers in mobile phones are used to detect the orientation of the phone. The gyroscope, or gyro for short, adds an additional dimension to the information supplied by the accelerometer by tracking rotation or twist." I mentioned a software conflict before, and a redundant digital system could at least set off an alarm if there were conflicting input data, especially if the data were counter to pilot control(s) input. I'd also recommend such a conflict be programmed to immediately return control of the aircraft back to the pilot(s) in the event of such an alarm. Thanks again for a wonderfully detailed explanation, including the "Startle Factor" I bet few had realized would be a seriously significant factor in handling such an instantaneous control conflict, "This aircraft is NOT doing what we're telling it to do!" And, the 3rd seater saw the solution immediately, simply because he wasn't all that startled. Indeed, completely overlooked... (I'm not an engineer, but I play one on guitar.)
My son and I was watching your previous episode. I mentioned to him, If I ever needed a pilot I hope it's that guy. I knew you seemed so experienced and knew you had the right stuff. After the explanation today with your background. It solidified my opinion. Juan love the episodes and appreciate all your hard work.
It’s hard to visualize the terror the crew experienced when struggling with the MCAS. Fear definitely compounded the difficulty of coping with the emergency.
Thank you for providing more detail on the MCAS issue and explaining in greater detail what the pilot’s point of view is during the event as it certainly helps to answer some of my questions and addressed some of the aspects that had puzzled me.
Really glad that I came across your videos. Excellent presentation. Thank you for taking the time to help us understand the ongoing situation. Best, Andy K.
Great segment Juan! I'm an aeronautical engineering for almost 40 years and who works for a major Boeing competitor. This explains much more about MCAS, how it works, the evolution of the 737 and why Boeing thought they needed it on the newer variants. Keep your segments coming, they are definitely worth watching!
Wow, Juan. I usually try to stick to relevant questions & let other heap praise on your well done reports. But I'm just blown away by this one. To say it's a lot of very good information in one posting would be a gross understatement.
Really Really Really great work. Even for those of us who arent in aviation and only watch Air Crash Investigations/ Mayday religiously. I get it. I think this is the best explanation out there. Ps i was one of those who refered to the jackscrew and Alaska Air incident. I think we got what you meant about the trim.. its just we didnt get how the system fully pushed the nosedown and why pilots couldnt recover - which you explained soooo well here. I think for me, personally, that particular episode of Alaska Air, i felt, was the most traumatic, just the overwhelming helplessness of the pilots fighting and trying to save the plane... it was too sad. So my mind automatically went there when you said the word jacksrew - ofcouse knowing it wasnt the reason of the loss of flight of the Maxs. I hope that helps. Your series on explaining the Max was great :)) Thanks
Excellent explanation. Also, thank you for your service to our country. Like we we told in training, most air saftey regs were written in blood. From an old Navy aircraft mechanic.
My wife was very concerned about the 737 Max. Thanks to you, I was able to explain to her, what the possible problems were and why we would not be flying on that aircraft next week. My father was a aircraft accident investigator, during WWII and he helped me realize that in most accidents there is rarely one simple cause. You reminded me that accidents are usually the result of series cascading events. Thank You Randy p s Luscombe fly-by-wire = LoL