Posts by user "BraceBrace" [Posts: 8 Total up-votes: 0 Pages: 1]

BraceBrace
June 18, 2025, 17:52:00 GMT
permalink
Post: 11905425
Originally Posted by M.Mouse
Was that using the same aircraft weight, same flaps, same ambient temperature and with the same de-rate(s) as the accident flight? Presumably he had inside information to find the appropriate numbers?
Just run a performance calculation with different flaps and compare V2 values. It\x92s not going to kill you with 2 working engines.

Last edited by BraceBrace; 18th June 2025 at 18:04 .

Subjects (links are to this post in the relevant subject page so that this post can be seen in context): V2

BraceBrace
June 19, 2025, 09:42:00 GMT
permalink
Post: 11905873
Originally Posted by TBC Retired
Contrary to something I read in the other closed thread, the 787 FMS doesn't perform takeoff calculations; in fact the code which does that was removed prior to initial certification.
The 787 relies on takeoff data computed by dispatch or in the EFB (Electronic Flight Bag), both provided via datalink to the FMS.
The latter can be subject to all manner of erroneous crew inputs if they're careless and aren't doing a good job of cross checking.
Garbage in, garbage out as the saying goes.
It's funny to watch posts like these and the "discomfort" when somebody else has to do these calculations. Dispatch can do erroneous inputs as well so we have to verify those numbers every single time. The few times I've had to ask dispatch to perform calculations, I wasn't feeling very comfortable as in my company they do not have the habit and there is a lot more chance of "garbage in, garbage out". There is always a procedure that calculations need to be done by 2 different persons, if dispatch has to do that there is no control over that procedure from my side, the guy who in the end is responsible for those numbers.

I have been using EFB all my life and can only confirm that every company has very strict procedures. And history has shown that if they are not followed, the end result is usually a tailstrike, not a stall inflight. As thrust can be increased on the spot, flaps influence (as long as not up) is highly overrated (as is in this thread) as there isn't that big of a difference between the V2 values of different flap settings.

The Air India crash is a obvious case of loss of thrust on both engines. The flight trajectory resembles a typical "too high and held off flare" that happens many times on training flights which with low time ab-initio's, that without correct re-input of thrust, leads to tailstrike. The nose up attitude, tail impact first shows engines were idle or out up to impact. Both engines to be clear, otherwise the aircraft would start to roll due to reduced rudder efficiency at low speed and higher thrust on one side. That's just pure physics, and physics can't be changed.

Subjects (links are to this post in the relevant subject page so that this post can be seen in context): V2

BraceBrace
June 20, 2025, 13:06:00 GMT
permalink
Post: 11906966
Originally Posted by Capn Bloggs
Having done many a takeoff sitting with the nose pointed skyward after liftoff, you just know that if both engines stopped, you would almost immediately stop going up. When you lose only one you have to be quick getting the nose down to keep the speed. If you lost both, you're not going much higher.
During a flameout it takes a while before the fan has slowed down sufficiently. As long as it rotates, thrust is generated.

With full reverse thrust you know that when de-selecting reverser from idle reverse, you have to give the engines plenty of time to slow down otherwise you would get the little "kick in the back" as during deceleration you would generate instant forward thrust when the reversers are stowed.

Subjects: None

BraceBrace
June 20, 2025, 19:56:00 GMT
permalink
Post: 11907263
Originally Posted by Sailvi767
The fan never stops rotating in a normal engine loss. Having been through a catastrophic engine failure in a 767 I can tell you that trust stops almost instantly. Certainly no more than 2 seconds. It also needs to be understood that thrust is not linear to engine speed in a jet. Very little thrust is generated below 70% RPM and thrust increases rapidly above 85%.
You are using explanations that are correct but with wrong appreciation for the values and how much thrust is available and what it is used for. Yes, the relation is not linear, far from, but the thrust required at low altitudes is for the initial climbout and acceleration, aka against gravity.

70% is not "very little", it is almost the required thrust in level flight with intermediate flaps out and gear down at those altitudes (depending on the weight). Without the gear, 60% is enough to keep level flight. If you want to descend, 55% is enough to keep speed with flaps full landing configuration and gear down on a 3\xb0 glide. So even at 55% N1, the aircraft wouldn't stall, it would gradually descend if the pitch would be correct.

It is what is between 70 and max rated that is needed for the initial climbout and that thrust is "excess" as it is there needed for the second segment in case of engine out. Considering the fact that the climb only lasted 10 seconds, 2 seconds is 20% of that time where the engines were still pushing. It is not because it is "significantly less" that it is nothing (that's why when you apply full reverse and don't let the engines slow down with idle selected, you will feel the kick forward.)

If you look at the takeoff video, you will see that the aircraft does a very rotation that some pilots prefer to avoid tailstrike: first initial rotation, constant pitch to allow the aircraft to become airborne avoiding tailstrike, second increase in pitch at which point the rate of climb quickly disappears. At that point, the "parabolic" maneuver with constant nose up is created, very typical for a loss of thrust (loss of airspeed with constant pitch).

Which begs the question why they never lowered the nose...

Last edited by BraceBrace; 20th June 2025 at 20:11 .

Subjects (links are to this post in the relevant subject page so that this post can be seen in context): Engine Failure (All)

BraceBrace
July 10, 2025, 15:53:00 GMT
permalink
Post: 11919101
Originally Posted by Magplug
Notwithstanding what it says in the B787 FCOM and FCTM, I don't think Boeing ever envisaged the dual engine failure procedure being required 10 seconds after rotate.
I think the correct Boeing reply would be: "it is not part of the certification process". So yes, loss of thrust on both engines during the takeoff phase is not really countered for in the procedures.

That does not mean that the pilots "out of habit" would have reverted to the procedure. Who would not? But in that case, the fuel control switches would be found in the RUN position post crash (if anything was left). So did they find the switches in the cutoff position, or did the action of switching got "stored" somewhere in FDM (not a specialist on these things, only to hear many times in the past that "maintenance is already aware" if we had an issue and called maintenance post flight)

Subjects (links are to this post in the relevant subject page so that this post can be seen in context): Dual Engine Failure  Engine Failure (All)  FCOM  Fuel (All)  Fuel Cutoff Switches  RUN/CUTOFF

BraceBrace
July 12, 2025, 18:54:00 GMT
permalink
Post: 11920749
Originally Posted by Hedge36
Question:
What messages, if any, are displayed on-screen when the fuel cutoff switches are re-positioned (especially to OFF)? I'm wondering if the pilot who asked about the shutoff SAW the other pilot manipulate the switches or if he was alerted by a message... or perhaps he looked down at rollback and realized they were in the OFF position.
I've had an all electrical black-out during single engine taxi, and I can assure you, it takes a while to go through all possible scenario's, one scenario being my FO had accidently switched off both engines. You just can't see those switches, so you have to look to the side and down to see those switches.

I believe (long time ago experience) there is an EICAS alert popping up when the fuel control switches are moved to cutoff. However, Boeing has a philosophy of "inhibits" below 400ft the aural alert indicating an EICAS has popped up is one of them. So as PF you would have to look at the EICAS during rotation, read the alert, then look down at the switches instantly.

Subjects (links are to this post in the relevant subject page so that this post can be seen in context): EICAS  Fuel (All)  Fuel Cutoff  Fuel Cutoff Switches

BraceBrace
July 12, 2025, 19:23:00 GMT
permalink
Post: 11920770
Originally Posted by Eutychus
This video takes the trouble of going through the preliminary report in some detail, and picks up on the inclusion of a psychologist in the investigation team, which I don't think has been mentioned here yet.

Is there anything professional pilots would take exception to in the explanation by the pilot in this video?
Not sure if it's the first time. Peer support is fairly new in the world of pilots, that is true, which is why he probably picked it up. But we do need such programs to become active sooner rather than later, and we can only hope this crash isn't going to be a case study to promote such programs. Only time will tell. Some companies still struggle with the idea, in a not so long distant past, pilots from a large national carrier went straight into a fight and the reports got leaked. Many of us still wonder how the hell - after years of CRM talks - that could happen. It still is world governed by "male dynamics"... slowly changing. I would suspect Air India to be similar in dynamics.

Subjects (links are to this post in the relevant subject page so that this post can be seen in context): Preliminary Report

BraceBrace
July 13, 2025, 00:27:00 GMT
permalink
Post: 11920960
Originally Posted by TBL Warrior
CVR should have recorded the beeper too, inhibits are for ground only.
Sure? Caution bell and light is inhibited up to 400ft RA or 20 seconds after lift-off, whichever comes first on a 777. Would expect the 787 to have the same inhibit.

Subjects (links are to this post in the relevant subject page so that this post can be seen in context): CVR