News for hackers. Stuff that matters.
Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @11:55AM (#39526356)
Author here. Did not expect to see this on HN at all. Just an engineering war story I shared.
Re:Testing the F-35C Tailhook by tra3 on Tuesday February 27, 2024 @12:03PM (#39526449)
This is really cool, thanks for sharing. What's wild to me is that the program started in the late 90s and only now is the F35 fleet up to originally specified? operational capacity.

Since then I graduated high school, got a degree, got married etc etc. The time span is mind boggling. Would be interesting to see how continuity is maintained for so long. In software it feels like if a project is more than 6 months old, we throw it out and rewrite it.

Re:Testing the F-35C Tailhook by tekla on Tuesday February 27, 2024 @12:13PM (#39526577)
You write shit down and you have career engineers that enforce continuity

It's trendy in software to complain about doing annoying work like writing reports and documenting things. But most hard tasks require writing reports and documenting things.

Re:Testing the F-35C Tailhook by eitally on Tuesday February 27, 2024 @01:32PM (#39527679)
And this isn't limited to aerospace. My wife has spent a career in pharma (drug save & pharmacovigilance specifically) and it's the same way there. People complain about rigidity and sluggishness in these industries but there absolutely is an ingrained attitude of documentation and process compliance that pervades. At one point -- and this was just last year -- my wife took over running a monthly safety report that involves manipulating a bunch of data in Excel. Even that has a 9 page instruction guide, and since she now owns the output she also owns maintaining the manual.

Too often in the land of software we underestimate the potential negative impact the traditional "move fast and break things" approach to product development can have when it comes to real world use in mission critical systems.

Re:Testing the F-35C Tailhook by trhway on Tuesday February 27, 2024 @01:58PM (#39528056)
On the other side this unwillingness and mental non-acceptance of those reports/manuals/etc. as a wasteful activity frequently comes from the understanding that there are more efficient ways of doing things, and that drives the "software eating the world" effect. While I naturally don't know the details of the case you mention and pharma is far from the domains I've been in, yet in many business/enterprise situations the software approach is to code the many-page guide into business logic, including ETL-ing the data instead of manual import, etc.

Move fast and break things brings you to the Moon in a decade using primitive tech, where is total process compliance can't do that even in 50 years using much more advanced tech.

Re:Testing the F-35C Tailhook by falcolas on Tuesday February 27, 2024 @03:08PM (#39529088)
So, an amusing anecdote related to your second paragraph - one reason it's taking so long the second time around is everything has to be repeated. They lost the knowledge of how to make rocket stages and engines of that size, and had to re-learn those lessons.

It's also quite important to remember how many lives were lost (or nearly lost) because of "breaking things" in the Apollo program. Something that's not nearly as acceptable today than it was at the height of the cold war. Something that directly implies moving more slowly and being more sure that everything works the first time, every time.

Re:Testing the F-35C Tailhook by inamberclad on Tuesday February 27, 2024 @07:08PM (#39532072)
Seconded. People burned alive until we learned. Surely there is a middle ground that will let us speed up while staying fairly safe, but it's important to remember that outside of software, many rules are written in blood.
Re:Testing the F-35C Tailhook by doctor_eval on Tuesday February 27, 2024 @09:58PM (#39533405)
I don’t hold a strong opinion either way - in terms of process and documentation versus freestyling it - but that fire was predicted, and I think the concerns were documented.

It can and did happen again, twice, on the shuttle project. Both the O rings and the ice damage were documented.

Ultimately, any process (or lack of process) can be subverted by a bad culture. And unreasonably excessive process - as perceived by the participants - can damage culture as much as not enough.

The problem is that culture is ineffable, so we try to nail it to the ground with whatever we can think of.

Re:Testing the F-35C Tailhook by red-iron-pine on Wednesday February 28, 2024 @11:44AM (#39540472)
a lot of people died in germany, the ussr, and the us making those rockets work. and in exchange for that we planted a flag there and have a handful of rocks in a glass viewing box.

move fast and break things worked real well for the folks who got literally creamed while they were viewing the titanic.

Re:Testing the F-35C Tailhook by hanche on Wednesday February 28, 2024 @02:36AM (#39535113)
Heck, even maintaining my computers at home requires documenting things! I have lost count of the number of hours I’ve lost trying to rediscover how or why I set things up the way I did.
Re:Testing the F-35C Tailhook by roughly on Tuesday February 27, 2024 @03:10PM (#39529105)
> In software it feels like if a project is more than 6 months old, we throw it out and rewrite it.

I think that would be a bad way to operate, but what's worse is what we _actually_ do, which is write the project like it's gonna be replaced in 6 months and instead keep that poorly-documented untested duct-tape contraption around for a decade as the central load-bearing component of critical infrastructure.

Re:Testing the F-35C Tailhook by Jenk on Tuesday February 27, 2024 @08:33PM (#39532777)
A decade is infancy in that scenario. The world's economies are running on stuff way, way older, for example.
Re:Testing the F-35C Tailhook by xattt on Tuesday February 27, 2024 @07:22PM (#39532206)
> In software it feels like if a project is more than 6 months old, we throw it out and rewrite it.

“The Phoenix pay system is a payroll processing system for Canadian federal government employees, provided by IBM in June 2011 using PeopleSoft software, and run by Public Services and Procurement Canada… By July 2018, Phoenix has caused pay problems to close to 80 percent of the federal government's 290,000 public servants through underpayments, over-payments, and non-payments.“

https://en.wikipedia.org/wiki/Phoenix_pay_system

Re:Testing the F-35C Tailhook by tempestn on Tuesday February 27, 2024 @11:03PM (#39533834)
That situation was (is?) absolutely mind-boggling. I personally know government employees that were being underpaid with no recourse for months on end because the software wasn't working and the government apparently had no alternate way to pay. Some people weren't getting paid at all. And as you quoted, it affected 80% of the workforce, hundreds of thousands of people.
Re:Testing the F-35C Tailhook by dj_gitmo on Wednesday February 28, 2024 @12:43AM (#39534458)
Someone should get fired for choosing IBM in this case
Re:Testing the F-35C Tailhook by nradov on Wednesday February 28, 2024 @12:44PM (#39541288)
Ironically, many of the agile development practices which are widely used today were pioneered in the Chrysler Comprehensive Compensation (C3) payroll application. It was never able to produce an accurate payroll for Chrysler and couldn't replace the legacy system, although the project was considered at least a partial success in other ways.

https://wiki.c2.com/?ChryslerComprehensiveCompensation

Re:Testing the F-35C Tailhook by k12sosse on Wednesday February 28, 2024 @08:54PM (#39545753)
My employer still had the balls to pay IBM after the Phoenix snafu to come in and tell us how we could become more efficient and guess what? It was basically word for word what the frontline employees had been screaming for for YEARS that management ignored. And guess what? They ignore the consulting report and did nothing anyways. #MunicipalLife
Re:Testing the F-35C Tailhook by jonp888 on Tuesday February 27, 2024 @07:30PM (#39532287)
I work on software that has a lifetime once installed of about 30 years, and if a safety critical error is found during that time, ideally it needs to fixed with a minimal patch, so we have to maintain the capability to do so.

I guess the ethos is quite different to top tech company. We don't get the pay or perks that you would get in Silicon Valley, but we are unionised, and it's a viable option to spend your entire career just on one project so it's very stable.

Partly it depends on documentation, but also on thinking long term. There are certain people who are the technical authority for a particular area, and they know that about 5 years before they retire or move on they need to find someone who can take on their role for at least the next decade, to keep their knowledge rolling forward.

Re:Testing the F-35C Tailhook by tra3 on Tuesday February 27, 2024 @09:41PM (#39533266)
That's fascinating. Is it possible for you to share more details? Industry? Tech stack?

If your project started 30 years ago, that means DOS, or Network or maybe one of the IBM behemoths?

Then the maintenance includes pacing OS updates and dependency changes?

Re:Testing the F-35C Tailhook by HeyLaughingBoy on Tuesday February 27, 2024 @10:03PM (#39533442)
Not OP, but I work on medical devices. One product at my last job had an expected service life of 20 years. FDA requires that the manufacturer maintain the ability to support and service a medical device for, IIRC, 5 years after market exit.

In the 10 years after release that I was on that project, we went through multiple OS upgrades from Windows NT to XP Embedded, to Windows Embedded Industry (replacement for XP Embedded) and a number of replacement x86 CPU boards had to be qualified as one manufacturer after another exited the market. Since the device is validated as a complete system, we often had to buy a year or two stockpile of existing product to give us time to start the Validation process for replacement hardware.

You usually have plenty of warning from a supplier that a product (Windows or a CPU board) is going EOL at a certain point, so you need to start validating whatever the next replacement will be well ahead of time.

Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @09:17PM (#39533105)
The F-35 contract was awarded on October 26, 2001. I was in my freshman year of undergrad, 18 years old.

I started on the program in August, 2010. I was 26 years old.

The program has just completed its Initial Operational Test & Evaluation, including its runs for score in the Joint Simulation Environment. I am 40 years old.

Re:Testing the F-35C Tailhook by wazokazi on Tuesday February 27, 2024 @12:17PM (#39526639)
Was there ever any consideration given to building a "testing harness" to physically simulate the F35 landing? Something like the "dead load" testing that the EMALS undergoes. Just in reverse. Anyway, that was great read.
Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @12:30PM (#39526800)
There was a lot of static load testing done, and things like a drop test [0] of a full scale article. But to my knowledge, the only way to test the dynamics of a carrier arrestment is to actually do an arrestment. We do them on land; NAS Patuxent River and NAS Lakehurst (among others) have a full set of Mark 7 arresting gear like you would find on a Nimitz class. Lakehurst also has the advanced arresting gear present on the Ford class.

[0] https://www.youtube.com/watch?v=lGPseVNfZO0

Re:Testing the F-35C Tailhook by fatbird on Tuesday February 27, 2024 @12:53PM (#39527123)
How much of a difference is there between dry land arresting and carrier arresting? I would guess some since the carrier represents a somewhat dynamic surface, and flight conditions might likewise vary. Is there enough that a second round of carrier based testing is required that might trigger significant changes?
Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @01:09PM (#39527328)
All of this was done as a work up to a carrier deployment. In software terms, trying the arrestments on land is deploying to test, doing them on a carrier is production. There were three separate developmental test deployments to carriers for the F-35C. Each deployment sought to expand the understood envelope and and handling procedures. The hook redesign happened before the first deployment. The hard landing story in the post happened during the work up to the third and final deployment.
Re:Testing the F-35C Tailhook by dotancohen on Wednesday February 28, 2024 @09:02PM (#39545787)
Had the hard landing occurred on a carrier, how would the gentle, flared landing be accomplished? Try to reach an airport on land, ditch the plane in the water, maybe catch the plane with the net on the deck? Our just do a normal carrier landing and hope for the best?
Re:Testing the F-35C Tailhook by whartung on Tuesday February 27, 2024 @04:19PM (#39530124)
I don’t know if it’s significant but on the carrier the arresting system is going 25-30 mph. The ship is moving.

Again, maybe not enough to really matter, but enough to at least take into consideration.

Re:Testing the F-35C Tailhook by doctor_eval on Tuesday February 27, 2024 @10:02PM (#39533429)
I imagine it means that the arresting system is being tested to greater limits on the ground than at sea, all else being equalish?

Since the relative speed of the aircraft to the ship will be reduced.

Re:Testing the F-35C Tailhook by ahartmetz on Wednesday February 28, 2024 @10:08AM (#39538897)
That is all correct. I have flown gliders and studied physics :)
Re:Testing the F-35C Tailhook by psunavy03 on Tuesday February 27, 2024 @01:09PM (#39527338)
The Navy developmental test community does carrier suitability testing of every new airframe, and there's a whole program of nominal and off-nominal arrestments they have to test in order to prove the jet can recover in all expected scenarios.
Re:Testing the F-35C Tailhook by superjan on Tuesday February 27, 2024 @12:26PM (#39526740)
Isn’t there a normally a mechanism that lifts the wire after the landing gear has crossed it?
Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @12:39PM (#39526929)
Yes, there are pendants that are supposed to keep the wire above the deck, but the short space between the F-35C main landing gear and the tail hook point means that there's not enough time for the pendants to raise the wire above the deck in the manner that the original (erroneous) wire dynamics model would have suggested.
Re:Testing the F-35C Tailhook by LorenDB on Tuesday February 27, 2024 @12:30PM (#39526798)
Hey, would you mind adding an RSS feed to your blog?
Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @12:32PM (#39526831)
I am but a grunt who mostly programs radar models, I didn't know Quarto blogs could do that until just now. Yeah, sure, I'll add it.
Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @12:40PM (#39526939)
Done!
Re:Testing the F-35C Tailhook by LorenDB on Tuesday February 27, 2024 @12:46PM (#39527028)
Thank you!
Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @12:53PM (#39527125)
Quarto made that really easy. Very cool.
Re:Testing the F-35C Tailhook by idontwantthis on Tuesday February 27, 2024 @01:22PM (#39527527)
Sorry, it’s been so long that I’m afraid to ask. What will you do now that it has an RSS feed?
Re:Testing the F-35C Tailhook by LorenDB on Tuesday February 27, 2024 @01:29PM (#39527638)
Uh, put it in my feed reader? What else is there to do with RSS feeds?
Re:Testing the F-35C Tailhook by dylan604 on Tuesday February 27, 2024 @01:38PM (#39527758)
If you're Googs, you deprecate them
Re:Testing the F-35C Tailhook by iab on Tuesday February 27, 2024 @12:53PM (#39527124)
Are you actually euler_angles, or are you really tait_bryan_angles
Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @09:54PM (#39533371)
Deep down I am indeed tait_bryan_angles
Re:Testing the F-35C Tailhook by iab on Tuesday February 27, 2024 @10:14PM (#39533511)
I appreciate your candor (and your article)
Re:Testing the F-35C Tailhook by tiahura on Tuesday February 27, 2024 @01:00PM (#39527231)
Instead of a lot of modeling and testing, wasn't Northrop just allowed to inspect an F18 and measure?
Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @01:02PM (#39527250)
The F-18 tailhook geometry is far different than the F-35 tailhook geometry. F-18 hooks are much farther back from the main landing gear, and are also much longer.
Re:Testing the F-35C Tailhook by jtriangle on Tuesday February 27, 2024 @01:28PM (#39527621)
Why exactly did they redesign the tail hook? Surely they could have just used one off any number of other aircraft with some modification?

Or are all of those tail hooks bespoke designs because reasons?

Re:Testing the F-35C Tailhook by wbeckler on Tuesday February 27, 2024 @01:59PM (#39528072)
It could be related to the fact that they didn't have much space for a normal size tailhook, as stated in the article.
Re:Testing the F-35C Tailhook by jtriangle on Tuesday February 27, 2024 @02:12PM (#39528290)
I mean more the design of the hook itself, though, I don't know if that design is even atypical to be honest.
Re:Testing the F-35C Tailhook by mech987987 on Tuesday February 27, 2024 @02:17PM (#39528361)
Even if two different aircraft have the same space constraints for the hook (which is a pretty big if), they have different mass and deceleration characteristics (i.e. minimum and maximum approach velocity) during landing- changing the force exerted on the hook. Designing a lighter hook for the lower loaded aircraft is VERY desirable for high tech fighter jets- every ounce saved is better range, better agility, etc.

As far as the little lip at the very tip of the hook- it looks to me like the initial design was trying to minimize any risk of digging into the flight deck and causing damage- this is just a guess though.

Re:Testing the F-35C Tailhook by cwillu on Wednesday February 28, 2024 @02:13AM (#39534974)
“After the LSO finished what he had to say and left the ready room my B/N allowed that he might fly with me again. Me, I was still shaking inside.

The next morning I went up on the flight deck before flight ops started and walked to the aft edge of the deck. I was looking for something and found it.

About one foot from the end, there was a single, shiny, brand new, solitary hook imprint in the deck.”

https://thelexicans.wordpress.com/2013/09/10/one-foot/

Re:Testing the F-35C Tailhook by wolverine876 on Tuesday February 27, 2024 @03:04PM (#39529038)
Due to the planes and to the rest of the tailhook (the shank, etc.), they could hit at different angles, speeds, etc. That's just a guess, however.

Each plane costs ~$100 million and the entire program will cost over $1 trillion when it's done. Performance needs are extreme: They need to land in all sorts of adverse, imperfect conditions - damage to the plane, the carrier, the wire, the personnel; bad weather; bullets and missiles flying around. It seems worthwhile to design the highest-performing tailhook for this plane, rather than to save a few bucks.

Also, IME people doing something this sophisticated don't miss those really simple, obvious issues that we happen to be able to observe and grasp from the outside.

Re:Testing the F-35C Tailhook by tharkun__ on Tuesday February 27, 2024 @07:35PM (#39532339)
The article goes into that.

The model provided by the manufacturer stated that the cable will bounce up after having been hit by the landing gear. Thus the hook design made sense. The cable jumps up and over the hook. Plane arrested.

Instead, again as the article states, the cable is actually being pressed tightly against the flight deck and the elevated hook nose makes the entire hook get thrown up in the air when drawn over the tight cable, back towards the plane and would even destroy some parts of the monitoring mechanisms, so violently did that happen.

They also provide the new design, which is basically the old design and that is also why the techs that saw the new hook for the very first time (and know about the cable I presume) instantly said "That ain't gonna work!".

It's all in there.

Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @08:13PM (#39532628)
Minor correction, the wire dynamics model was provided by Naval Air Systems Command (NAVAIR), the Navy engineering organization in control of research, development, test, evaluation, and sustainment of Navy aircraft.
Re:Testing the F-35C Tailhook by tharkun__ on Tuesday February 27, 2024 @09:02PM (#39532993)
Thanks! Corrected my comment.

I would actually love to know if someone on the hook design team questioned the model. I guess we won't know but I also it doesn't hurt to ask.

Like did someone go: odd, why would that cable go up and not tighten when waves are sent through it towards the outward attachments? But was inevitably shut down and didn't have "access to the customer" to ask/verify.

Like one of the first things to ask for when having to design this that comes to my mind is: I want high speed camera footage of current arrestor in action at the customer site!

Re:Testing the F-35C Tailhook by imglorp on Tuesday February 27, 2024 @02:25PM (#39528486)
They designed for the F-35B as the "baseline" with carrier requirements secondary. Also, the engineers knew but, "their concerns would have just as likely been ignored." This reference was 2012, when they knew it was a problem but before OP was fixing it.

https://www.f-16.net/f-35-news-article4494.html

Re:Testing the F-35C Tailhook by sufficer on Tuesday February 27, 2024 @10:49PM (#39533745)
Have you seen an f14 in person? An f35?

Wildly different. For one the f14 is massive! And it's tail hook is like the size of a medium man

So yeah tail hooks vary wildy

Re:Testing the F-35C Tailhook by awhitby on Wednesday February 28, 2024 @03:35PM (#39543147)
A more interesting question is do the cables (size, positioning, tension) vary by aircraft? Can any carrier-capable aircraft land on any carrier in the US fleet?
Re:Testing the F-35C Tailhook by mlekoszek on Tuesday February 27, 2024 @01:35PM (#39527714)
Glad you did.
Re:Testing the F-35C Tailhook by aidenn0 on Tuesday February 27, 2024 @02:03PM (#39528155)
> “Boss,” he says to me, “This fucker ain’t gonna work. Look at this thing. It’s short, it’s too close to the wheels, and look at this dumbass hook shoe they got on it. If the wire don’t hit it exactly right, it’s just gonna go under the hook and you’ll bolter.”

Did nobody with practical experience with arrested landings look at the arresting hook design prior to this? Obviously computer models can and do predict extremely novel solutions to existing problems, but it's worth double-checking the model when someone with practical experience says "it will never work"

In this case, it seems like a simple slow-motion video of an arresting wire going under the wheels of an F-18 would have been enough to debunk the model.

Re:Testing the F-35C Tailhook by the_af on Tuesday February 27, 2024 @03:20PM (#39529273)
Random thought: this is a case where someone's intuition matched what actually happened, making us think "why don't they listen to people with common sense?".

But what about the many other cases where someone with "common sense" said "this fucker ain't gonna work" but the thing worked as predicted by simulations? Surely they must have happened too.

Re:Testing the F-35C Tailhook by aidenn0 on Tuesday February 27, 2024 @04:41PM (#39530394)
My point is that when models predict counterintuitive results (which they often correctly do; See e.g. Eurisco in the Traveller TCS championship, or the shape of the F-117 compared to contemporary stealth aircraft), it's worth double-checking.
Re:Testing the F-35C Tailhook by MadnessASAP on Tuesday February 27, 2024 @04:00PM (#39529866)
Unfortunately, my decade plus as a military aircraft tech has taught me that no, practical knowledge does not make it through the system nearly as fast as engineering "expertise".
Re:Testing the F-35C Tailhook by mechhacker on Tuesday February 27, 2024 @06:51PM (#39531895)
Same, but different industry. Lots of re-engineering of the wheel after the original designers give their warnings and recommendations, but everyone's too smart to try the simple thing that already works first.
Re:Testing the F-35C Tailhook by icegreentea2 on Tuesday February 27, 2024 @02:59PM (#39528956)
> Did nobody with practical experience with arrested landings look at the arresting hook design prior to this?

I mean... it's very likely that the answer is no. The last new carrier aircraft made was the Super Hornet - and that design was basically done by 1995 (the F-35 tests in question were in 2011/2012). That expertise would also be at McDonald Douglas/Boeing. Northrop Grumman has a long history of carrier aircraft development, but it would have been long dormant by that point.

I'm sure there's all sorts of reasons the model's inaccuracy wasn't caught before hand, but sometimes... if you're given a model that's someone says that's been V&V'd, and it produces a result that's only a little weird, you just go with it. There are only so many things you can add extra testing onto in a project. Sometimes you choose wrong.

Anyhow, consider that the model results were probably exactly what they were expecting. Remember that the designers would be honing in on the shorter tailhook. You can imagine their mental model going - "ok on legacy aircraft, we have flatter tailhooks because there's enough time for the cable to settle". And then going "ok, with a shorter tailhook, there won't be enough time to settle". And then their model comes out and say "ya, with the shorter tailhook, it won't have enough time to settle - it'll be UP IN THE AIR". Whereas reality is "ya, with the shorter tailhook, it won't have enough time to settle - it'll still be displaced DOWN".

Re:Testing the F-35C Tailhook by throwanem on Tuesday February 27, 2024 @06:10PM (#39531493)
The name "ham-peas" might be familiar. If so, how've you been keeping lately? Been a minute!
Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @06:19PM (#39531574)
I have not forgotten your user name here, ha. Yep, been a minute. I should hit you up via email.
Re:Testing the F-35C Tailhook by throwanem on Tuesday February 27, 2024 @06:38PM (#39531786)
I wouldn't mind that at all. If you don't still happen to have the address, the one in my profile here's good too.
Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @06:42PM (#39531818)
I actually still have your personal email address. Expect something from me soon. It took a few years but I work as a developer now (C++, electronic warfare simulator)
Re:Testing the F-35C Tailhook by throwanem on Tuesday February 27, 2024 @11:00PM (#39533822)
That's great to hear! I'll keep an eye out, and hoping all's well in the meantime.
Re:Testing the F-35C Tailhook by kevin_thibedeau on Tuesday February 27, 2024 @09:37PM (#39533240)
Hope you have proof that the diagrams aren't export controlled. Otherwise you're going to receive some unexpected visitors soon.
Re:Testing the F-35C Tailhook by euler_angles on Tuesday February 27, 2024 @09:49PM (#39533330)
They all came out of a book that anyone can buy called "F-35: From Concept to Cockpit". That book is a compilation of papers presented at an AIAA conference in 2018.
Re:Testing the F-35C Tailhook by egorfine on Wednesday February 28, 2024 @04:54AM (#39535957)
First of all, thank you for the super interesting read!

Now, as a Ukrainian I do have a philosophical question of sorts. What we have seen here in a real full-scale combat is that some of the modern machines are way too delicate for actual operations on the ground. For example, I have heard some feedback about the Abrams tank: way too finicky for real use, not durable, not reliable. The same goes about many other western items. (Some hardware demonstrated exceptional reliability, like Bradleys and HIMARS)

My question is about modern fighter jets like F-35.

Does that level of engineering and the amount of delicate electronics somewhat limit the durability and reliability of the airplane compared to much simpler designs?

Re:Testing the F-35C Tailhook by nradov on Wednesday February 28, 2024 @02:46PM (#39542628)
The F-35 was never really intended to be durable or reliable for ongoing use in long wars of attrition. It was designed to be survivable on penetrating strike missions against near-peer adversaries. Essentially to "kick the door in" and destroy high value targets such as air-defense systems during the first few days of a conflict. War games and simulations have shown that simpler designs can't accomplish that mission anymore so concerns over F-35 durability and reliability are somewhat misplaced (although there is certainly room to improve mission readiness rates).

No one is even remotely contemplating sending F-35s to Ukraine. Besides and costs and security risks, the Ukrainians unfortunately have nowhere near the infrastructure and logistics to sustain such a complex platform.

Re:Testing the F-35C Tailhook by egorfine on Thursday February 29, 2024 @06:30AM (#39548079)
Ah, so in that case it looks like reliability and durability are not exactly important or desired features for that kind of missions. Did I get it right?