While the author’s (banker and a data scientist) experience is clearly valuable, it is unclear whether it alone is sufficient to support the broader claims made. Engineering conclusions typically benefit from data beyond individual observation.
Let me fill you in on a secret: one of the reasons behind US’s dominance is that even though “there are other countries” that could do the hard science, the US is one of the only ones that did. Now the US is at risk of becoming just another one of those “other countries“.
From the article: “ The White House, which was responsible for the assessments, said the information will be housed within NASA to comply with the law, but gave no further details.”
It doesn’t seem like the admin believes the reports are biased and need to be removed. Cool conspiracy though.
We do, broadly, have a problem in Canada with people blaming the federal govt for things that are not under its jurisdiction. We have a very federal system, and the provinces have a lot of power.
But in this case, yes, I think federal policy is directly implicated.
In this case, it's definitely Trudeau's administration fault by flooding the Canadian job market with immigrants, which lowers job compensation and increasing housing cost.
They've always been lower, but it was always 20%ish lower. Now it's like 50%.
And in the meantime, housing prices have gone up exponentially. Housing in greater Toronto is more expensive than the Bay Area, but the compensation is far far lower.
I'm not one to blame Trudeau personally, or even immigration per se. I think there's a multitude of factors. But it's best not to deny the situation, which is that in the last few years there's been... problems... in the Canadian SWE labour market.
It's not the quantity / size of pie. It's the fact that the Canadian labour market has explicit "escape valves" for "skilled labour is too expensive" built in as a policy plank in the form of the LMIA and TFW process.
They are tools that "industry" lobbied for expansion of, and got. Have persisted through both Conservative and Liberal governments for decades, but was expanded markedly under both Harper and (especially) Trudeau.
I hate the F Trudeau crowd almost as much as I hate Trudeau, but
Low compensation ranges here are in fact in part the fault of fed gov't policy. Industry freaked out about "labour shortage" and the government responded.
The database of LMIA (Labour Market Impact Assessment) applications is public. You can see for yourself how many thousands of software engineering jobs were filled this way. (Including by big "elite" tech companies like Apple, Google, Amazon, etc.) This was deliberate policy to bring in foreign talent from India, China, etc. in order to fill a "shortage" of us, which well, that shortage was less about "can't find someone" as "I can't find someone cheap enough."
In this case I don't actually blame Trudeau or the libs -- they're on the whole too stupid about our sector to understand that in fact these low compensation ranges harm our industry more than they help. I blame corporate interests who have the ear of the gov't and misled them into thinking that somehow this would make Canada "competitive" in information tech.
All it does is force good talent to leave the country, and encourage sweat shops to open up offering mediocre "IT" services.
We're subsidizing our own Canadian students to go through great schools like U Waterloo, etc. and then losing most of them the moment they graduate, as they go to the US on a TN1. And in exchange...
I've been in this industry long enough (25 years) to have seen things go up and down relative to the US a few times. This is the worst it's ever been. Especially because you can no longer make the argument that "I may get paid less but it costs less to live here" -- that ship sailed 10 years ago.
When I mentioned AirBus, I was thinking of this - that the Max crash is clearly due to corporate greed. I am not aware of any such scenario with AirBus. Not only that, according to the Netflix documentary, Boeing was trying to blame the pilots of the Indonesian and Ethiopian airlines initially. Then in turns out that the Indonesian pilot was an Indian who was trained in US, and the Ethiopian pilots followed Boeing's guidelines on MCAS failure properly.
I am looking at these blames on outsourcing from that perspective - that Boeing is trying to blame others to hide their greed.
> the Ethiopian pilots followed Boeing's guidelines on MCAS failure properly.
The Ethiopian pilots did not follow the procedure in the Emergency Airworthiness Directive distributed to all MAX pilots that says:
"Initially, higher control forces may be needed to overcome any
stabilizer nose down trim already applied. Electric stabilizer trim can be
used to neutralize control column pitch forces before moving the STAB
TRIM CUTOUT switches to CUTOUT. Manual stabilizer trim can be
used before and after the STAB TRIM CUTOUT switches are moved
to CUTOUT."
Thanks for the links. I am not trying to refute what you said above. But I don’t want anyone to think that I am spreading misinformation here. So I checked the Netflix Downfall documentary again. It says at 34:30 that the pilots did what Boeing instructed them to do.
The documentary talks about the Ethiopian crash from 32:00 onwards. The below excerpt is from 34:30 onwards. Name of the person talking is in '[]' brackets.
[Pasztor] Soon after the hearings got underway, we managed to get more information about what actually happened in the cockpit of the Ethiopian aircraft. We got the information from the FAA within hours after they received it from the Ethiopian investigators. It was very late at night, and we tried to put together the most comprehensive story we could. When it came out, this was the first story that revealed that the crew, in fact, realized that MCAS had kicked off. And they did what Boeing instructed them to do.
[Tajer] When the MCAS kicks in, it runs for ten seconds and pushes the airplane very powerfully nose-down. Runs for ten, off for five. Runs for ten, off for five.
[Cox] They’ve got this cacophony of stick shaker, master cautions, airspeed disagree, altitude disagree. All of these…these warnings going off. The captain, who’s flying the airplane, is trying to figure out what’s gone wrong.
[Tajer] The first officer called out, “Stab trim cutout switches, Captain.” I think he said it twice. He did what Boeing said. He turned off the MCAS system. I remember reading that, and I said, “Man, the kid got it right. The kid got it right”.
[Cox] The problem now is that the airplane is going too fast. And because of the force on the tail itself, they cannot manually trim the airplane to be able to recover.
That is not following the instructions in the Emergency Airworthiness Directive issued to all MAX pilots:
"Initially, higher control forces may be needed to overcome any
stabilizer nose down trim already applied. Electric stabilizer trim can be
used to neutralize control column pitch forces before moving the STAB
TRIM CUTOUT switches to CUTOUT. Manual stabilizer trim can be
used before and after the STAB TRIM CUTOUT switches are moved
to CUTOUT."
The airframe was changed significantly, creating the need for the whole MCAS solution — why? Because this was seen as a solution to avoid a recertification of the airframe, which would mean pilots had to re-train, which would mean airlines wouldn't buy, which means money would not flow.
Avoiding this recertification was the only reason MCAS was chosen instead of designing an airframe in such ways the now bigger engines actually have their center of gravity where it is expected to be.
This was ultimately a cost saving measure. Boeing could not be bothered to recertify the airframe purely for comercial reasons, not because it objectively made sense.
There is nothing wrong with making an airplane behave like the previous version. In fact, it enhances safety, as pilots can and do make errors when under stress they do the right thing for the wrong airplane. Making airplanes predictable and consistent with existing training is a safety enhancing practice.
I worked on the 757 design, which was designed concurrently with the 767. A lot of effort was made to make them behave in a common manner, even though they were quite different airplanes. This makes perfect sense.
It's the same reason the steering wheel and pedals on your car are laid out the same and do the same things across nearly all very diverse cars. And yes, carmakers adjust the handling characteristics to be predictable and not need the drivers to have additional training.
Boeing had originally proposed a new small aircraft (with carbon fiber), but the airlines did not want this as it would have higher operations costs to have two different types of aircraft, so Boeing had to come up with a new 737, and the MAX was it.
Boeing was claimed to have "known the FAA would not certify a dual sensor system without Level D simulator training".
This was from an insider at the time, and admittedly, I've not heard of an identity being put to them, but that signal was claimed to have been there.
There is also corroborating evidence that the Chief Technical Pilot actively dissuaded customers who asked for simulator time anyway, characterizing it as unnecessary. I don't have those at my fingertips right now, and unfortunately, my memory is failing me as to whether or not an "oh shit" moment was had at some point as to whether the Chief Technical Pilot had mischaracterized the system to regulators.
I just remember I thought it was awful convenient at the yime that this Chief Technical Pilot had all the hallmarks of a scapegoat for management to start piling blame on, and being glad he got independent counsel instead of relying on Boeing's General Counsel.
Thanks for that bit of information, I didn't know that. It sounds like it could be true. But being uncorroborated, and considering all the false information swirling around the issue, I'd want some confirmation.
I watch every episode of "Aviation Disasters". On more than one, the pilots would get some warning light and would ask each other what it meant. That implies that simulator training is not required for every warning light.
I figure we'll find out more if/when a criminal case is finally brought and prosecuted, until then, I consider anecdotally credible. Here's those texts and articles btw...
It seems they never leveraged anything more from this supposed whistleblower, so until more is seen, it's kinda moot. Still thought Forkner was a fall guy for bad management though.
That, of course, immediately raises the question of why, then, this was not done.
There is a proximate answer that still does not get us to root causes: An MCAS failure was rated as a Major condition as opposed to Hazardous, in which case the regulations allowed (but did not, of course, require) a single source of input.
This rating was arguably justifiable for the 737 MCAS in its original form, but its power had to be increased significantly after flight testing revealed the original version to be inadequate.
As it happens, the 737 MAX airframe was not the first use of MCAS: the KC-46 also has it. Despite the fact that this system is less powerful than that which was fitted to the initial production 737 MAXs, it uses two AofA sensors. There is clearly a strong and obvious engineering case for doing so, so simply observing that Boeing did not have to do so does not exhaust the questions that should be asked.
I have seen it stated in several places that using two AofA sensors would have required a warning in the case of their being in disagreement, which in turn would require it to be mentioned in the AFM, which might have prompted a reevaluation of the no-training decision, either directly or through a reevaluation of the risk classification. Unless a smoking gun has been found, Boeing can stonewall on whether the training concern suppressed a full and objective evaluation of the risks posed by MCAS (especially after its strengthening), and thereby improperly influenced design decisions (among other issues), but the concern is obvious to everyone except those who want to avoid considering it.
> That, of course, immediately raises the question of why, then, this was not done.
Which I raised in the antecedent post.
I did not write that Boeing "did not have to" have dual sensor input. I said if they did have dual sensor input, and had done the other changes to the software, in my not-so-humble opinion additional simulator training would have been entirely unnecessary.
The other question I have is why two sets of pilots did not understand what the STAB TRIM CUTOFF switch was for, despite it being in a very prominent position on the console and is supposed to be a "memory item", meaning the pilot should not have to look it up in an emergency. That indicates inadequate training, whether the airplane had MCAS or not.
Keep in mind that the first MCAS incident, which is never mentioned by the press, landed safely because the crew simply turned off the misbehaving trim system. That crew didn't even seem particularly concerned about it after they landed.
>> That, of course, immediately raises the question of why, then, this was not done.
> Which I raised in the antecedent post.
You did, in the sense that you wrote "I've never seen an explanation for why this mistake was made." That does not mean it is somehow wrong for me to also make that point as a prelude to continuing that line of thought.
> I did not write that Boeing "did not have to" have dual sensor input...
And I did not say that you did. I pointed out that this would not be a full answer to the question that both of us raised.
> ...in my not-so-humble opinion additional simulator training would have been entirely unnecessary.
I very much doubt that Boeing was at all concerned about what you or I think. It is rather more plausible that it was concerned about what the FAA might think, especially if the FAA also understood the extent to which MCAS's power had been increased.
And nothing else you have written here has any bearing on the possible motives behind Boeing making a decision that you yourself call a mistake - one which was made before these incidents.
> Give a person code, and you help them for a day. Teach them to code, and you frustrate them for a lifetime.