> Within the space of four seconds, the energy from the annulus gas flow accelerated the IP turbine past its critical speed, until centrifugal forces exceeded the ultimate strength of the nickel alloy disk. The red-hot, wildly spinning disk instantly fractured into several sections, which rocketed outward in multiple directions at incomprehensible speed.
The fact that it's assumed to have infinite energy when planning for this is crazy. Engineers saying yeah there is no material in the world that can stop it.
Maybe not stop it, but perhaps they can design it so that if it happens it's more likely to be directed away from the fuselage? Like with armor that does not block or absorb but deflect, which requires less energy. Perhaps even a small reactive armor strip? (dangerous as though that would be on a plane).
But then again I'm sure aviation engineers would have thought of this and rejected it for good reason.
I know we all like to hand wring about stuff like this but realistically it's "infinite" to prevent the same genius textbook engineers who cooked up the VMC procedure and the CMM procedure from cooking up equally half baked "with a plate of this thickness at this angle it will remove X energy from anything that penetrates it therefore we are good to put some super critical thing right in it's path" solution.
Infinite is a bit poetic there. For large enough n, n inches of (say) armor steel could stop it. But that suggestion got Sales talking about "commercially viability", and Finance sided with them, and we all know how that story goes.
It's not (purely) the sales and finance people, planes need to be able to get off the ground to be useful at all. I doubt even an A380 would still be able to lift off if you strap a dozen inches of armor plating to every part of the plane that could possibly be reached by shrapnel.
You'd put the containment armor directly around the engine. It wouldn't take dozens of inches. Whether you use Newton's rule of thumb (penetration ends when the mass of armor displaced equals the mass of the shell that hit it) or more modern rules - a failing turbine disk is neither a precision-engineered anti-armor weapon, nor a heavy battleship shell.
I'd bet the plane would still be able to take off, if it made it that far. But it never would - with the extra weight guaranteeing that no airline would buy it, Finance would never sign off on funding to even complete the design work.
(Yes, the reality behind my quips about Sales and Finance is more complex:)
Full containment is probably possible, but it would render the aircraft nearly useless, not just economically uncompetitive.
A 70kg chunk of nickel alloy is very dense, and at 800m/s , that’s 20 MJ. Thats about the same as 5kg of TNT, but focused on a small area.
For comparison, a modern 120mm artillery shell fired from a tank or similar field artillery has 10-20 MJ of kinetic energy.
A couple thousand kg of armour could likely contain that kind of energy, but it would also translate that energy to the engine mounts, wing, spar, and fuselage if it was not going to become a projectile itself. You could easily stop a fragment and critically damage a spar attachment, rupture a wing fuel tank, or end up with translational shock damage to any number of critical systems and structures. You’d probably have to double or triple your engineering margins of the entire aircraft, probably doubling the weight of the airframe.
So yeah, possible probably. But not on an aircraft designed to carry passengers or freight. It would be the biggest 6 seat aircraft ever built lol.
Interestingly, if you work backwards from that cargo capacity, you can arrive at a much smaller aircraft that could possibly feature full containment, because engine diameter and energy goes way down and containment starts to look much more practical. I would not be surprised if containment could be achieved in the small biz jet scale, with just significant sacrifices in cargo or range.
OTOH even the A10 warthog does not have full disk containment, and it’s probably the strongest candidate ever fielded for such a project… so, ymmv.
- which bear no resemblance to a failed turbine disk. And have about twice the muzzle velocity, which makes huge difference in penetrating a modern armour systems. Ditto their far greater density, vs. nickel alloy.
OTOH, your "A couple thousand kg of armour could likely contain..." seems too charitable. High-bypass jet engines are big. Beyond that, I'm more optimistic about mitigating shocks and such.
A critical parameter here - https://en.wikipedia.org/wiki/A380#A380F The freight variant was to have a 6,400 mile range carrying 150t of payload. So we could squander 25t per engine on disk containment and shock mitigation, and still have a 50t payload. Or a 3-digit passenger headcount.
Bottom line, there is no real-world difference between your "nearly useless" and my "disastrously uneconomical". Neither one will be designed, let alone built.
For the A10, I'd say military priorities would always block full disk containment - because every pound used for that is a pound they don't have for more weapons or munitions or range or armour or fuel or runway length or electronics or whatever. And over most of the 360 which disk fragments could exit a warhog's engines, there's nothing critical which they could hit.
Good counterpoints all, I think. I’m impressed that we could write off 50t and still have an airplane. That seemed so preposterous that I did not consider it, honestly. Turns out big stuff is big.
Now we can go to the running of the bulls with our respective napkin backs, and see who attracts the bull!
Yes but on the warthog the discs are very far away from the pilot. Or pretty much anything else that matters. The fuselage can take a lot of a beating.
“It goes without saying that if any of the turbine fragments had entered the passenger cabin, there would have been injuries, if not fatalities, even if the plane later landed safely.”
I haven't checked the 12 factors for a while but feel proud to have worked on systems probably for a long old while where most or all have applied. To the point I'd naturally do these things without consciously thinking.
I think that says a lot about good practices spreading than anything else. To not do these things: maybe a startup moving fast, or a very isolated company or just some old legacy COBOL type thing where you want the thing to still work as the main concern.
Hi. As you are deeply thinking about these sorts of things, I want to see what you think of my https://useorganizer.com which turns the todo idea on its head a bit by being timeline oriented.
Seems very cool! I like the concept. I am still designing a "project" sort of organization primitive myself, which would incorporate more time based views of progress.
Just from browsing around and playing with it a bit, it seems there's still a lot of polish needing to be done. Quite a few areas where data is leaking across UI boundaries and some of the hard problems like data management and retention are stubbed (export is nice but it's the floor imo)
That is an amazing idea. I can imagine this getting popular. It could be used for faster local dev loops and porting GHA to other servers. I imagine for data/compute residency, cost, performance, vm types etc.
Thanks! I'm glad it resonates. Still pretty beta, but I'm hoping this can be a good alternative when Github goes down, which unfortunately has been a bit too often, with as minimal of a lift from the user side. And of course, making it easier for agents to fully drive ci.
https://github.com/anthropics/fermats-last-theorem/blob/main...
reply