7 ms·
Pentagon Report Faults F-35
- bliti 13y agoI took a tour of one of the factories where the F-35 is built (or one of the components of the airframe). It is the one located in Atlanta, Georgia. The scale of the place is just mind-numbing. There was a row of C-130 in different stages of assembly and next to them the production line for the their wings. On the F-35 side, there was this huge robot that looked like a flat toolbox. It moved the airframe part from one station to the next. Just amazing. The whole assembly line looks like something out of a movie. I was told that the F-35 had a lot of C++ code, and that is the reason it was not meeting deadlines. It was an interesting bit of gossip to hear, but I'm not entirely sure how that would come into play. I'm also not sure if C++ has been used before in this type of application. Given how ingrained Ada, C, and Fortran are in the industry.
- fus 13y agoIn the topic of C++ in industry: SpaceX is using C++ successfully in a similar type of application.
- vonmoltke 13y agoAda is dead for new development by fiat of the DoD. They finally figured out that having all their real-time code written in a language almost nobody outside of DoD uses is a bad idea. Fortran doesn't fly; that is, (almost)[1] no real-time code is written in Fortran. It is still used for simulations, but is steadily being replaced my Matlab since the latter integrates better with various engineering workflows. C is definitely still the winner for the embedded code, but is losing to C++ as time goes on. Java is also making inroads for implementing the interfaces on operator consoles. [1] I know of at least one program that deployed signal processing algorithms in a semi-operational state in Fortran.
- protomyth 13y agopage 3: "The current software generated too many nuisance warnings and resulted in poor sensor performance. Further work on software had been slowed by testing required to validate earlier fixes, the report said." "It said Lockheed had delivered F-35 jets with 50 percent or less of the software capabilities required by its production contracts with the Pentagon."
- greyfade 13y agoSounds like Lockheed needs to rethink its software development process. It has clearly failed.
- mikeash 13y agoI spent two months doing some side work for the NIH on some programming stuff, which was mediated through Lockheed. They were so disorganized and clueless than I'm amazed they are able to build a sandwich, let alone a jet fighter. For example, the onboarding meeting I had with their HR folks was roughly 90% about retirement benefits and health care plans, neither of which I was eligible for as a temporary part-timer. This still cost NIH two hours of my time even so. And it took them weeks to get me the right codes so I could actually log my hours in their system the way I was supposed to, on a project that was supposed to last two months in total. And in all of this, they provided not one shred of added value to the project that I could detect. Were it not for whatever bureaucratic rule required them as a middleman, I could have conceivably raised my rates 50%, cost the actual customer less, and been more productive without them.
- protomyth 13y agoStrangely, it seems the F-22 is doing ok these days.
- taspeotis 13y agoWhenever I read about software that needs to be perfect I think of this article [1]. > But how much work the software does is not what makes it remarkable. What makes it remarkable is how well the software works. This software never crashes. It never needs to be re-booted. This software is bug-free. It is perfect, as perfect as human beings have achieved. Consider these stats : the last three versions of the program -- each 420,000 lines long-had just one error each. The last 11 versions of this software had a total of 17 errors. Commercial programs of equivalent complexity would have 5,000 errors. [1] http://www.fastcompany.com/28121/they-write-right-stuff http://www.fastcompany.com/28121/they-write-right-stuff
- 13y ago
- GVIrish 13y agoThe Joint Strike Fighter program is a prime example of the military not learning anything from its failures in the past (like the F-111). Hell, they're not even learning from the failures they've had in the history of the JSF. If you've got 50 percent or less of the software capabilities in a system with 8 million lines of code, and it's supposed to be deployed in 18 months you're in deep shit. Yet, the program's backers blithely proclaim they're going to make their dates, ignoring the fact that the program is years overdue and 70% over budget. Not only has an enormous amount of good money been thrown after bad, the military has staked the future of air power on this one aircraft so no one wants to admit that it should be cancelled.
- pekk 13y agoThat sounds great and all, but cancelling doesn't exactly speed things up either...
- sliverstorm 13y agoWhat? Everyone knows that throwing everything out and starting all over from scratch (several times, if need be) is the fastest way to get done!
- TrainedMonkey 13y agoFrom what I understand main issue is that they are trying to build "transformer". Basically they want Navy, Marines, and Airforce to use same software/chassis. Obviously Navy, Marines, and Airforce all want different features, and requirement to the chassis renders it extremely frail (they had to cut a lot of weight for VTOL capability). So considering that, it actually might be good idea to stop completely, fire all top airforce/navy/marine brass involved and restart as 3 separate projects from scratch, albeit using all the technology already developed. Morale is already super low and it is hard to see bright future for something so overpriced, over budget, over engineered (in a bad way), and over politicized.
- GVIrish 13y agoSome say this is the most politically-engineered weapons system in history (along with being the most expensive). Production for the parts of this aircraft is spread over 45 states. So you can only imagine how difficult it would be to scrap or reduce the size of this project.
- skywhopper 13y agoI look forward to Philip Greenspun's reaction. Each one of these planes costs more than the year-long healthcare.gov maintenance contract he freaked out about.
- username223 13y agosigh. Perhaps it's time for Greenspun's 11th rule: never go full Libtard.
- Tloewald 13y agoThe software problems are bad enough. Then there's the hardware which is crippled by the marine corps's insistence on VSTOL which means that it will never be effective. The plane is all but an open joke within the air force.
- fnordfnordfnord 13y agoThe Chair Force decision makers aren't any better. The A10, one of their most successful programs ever, is/was also an open joke, it is the red-headed step-child of aircraft.
- deleted 13y ago[deleted]
- jfb 13y agoIt's not like the fast jet jocks who run the Air Force are really doing much to justify the decision to split out the Army Air Force, anyway.
- beloch 13y agoV/STOL capability was the one thing the marine corps absolutely insisted on, requiring the massive fan that makes the F-35's body so wide and high-drag. The decision to use a one-body-fits-all-applications approach means that even the non-V/STOL versions of the F-35 are fat pigs as far as military jets go. That's why these planes are so bloody slow by modern fighter standards and one reason why countries, such as Canada, that have no need for V/STOL variants of the plane are dropping out of the program. In short, the marines screwed this plane up for everybody but themselves. If even they are not happy with the result then the F-35 project is an utter flop.
- VladRussian2 13y agolooking back into history i'm wondering why F-35 VTOL didn't follow XV-5A, i.e. placing fans in the wings http://www.youtube.com/watch?v=1XkJXSoTTb4 http://www.youtube.com/watch?v=1XkJXSoTTb4 50 years ago plane looks more capable as VTOL than F-35. Modern powerful engines allow to drive the fans from the compressor shaft - as F-35 shows - and that would fix the main geometry issue with jet engine placement in XV-5A where fans were driven from jet exhaust.
- mapt 13y agoWe have created sufficient variety of failed VTOL plane concepts that there are certainly a number of types you've never seen. It is a recurrent trend - every engineering team thinks they have an answer which puts a novel spin on things and will fix them once and for all - and then it turns to shit. View the 'wheel of shame', as it's known in aeronautical engineering circles: http://vstol.org/ http://vstol.org/
- VladRussian2 13y agoseveral years ago spent a bunch of time going through the wheel, and in my view XV-5A and Bell X-22 were pretty good planes - there was nothing really wrong with them, and definitely not a "shame". Given the half-century improvements in hardware/electronics/aeronautical science i think if built today they would be much better than F-35 and V-22.
- larsmak 13y agoThey should have just incremented on the F-16, now that is an exellent fighter - so elegant and simple. One of the F-16 designers has some great insights on the F-35: http://www.youtube.com/watch?v=UQB4W8C0rZI http://www.youtube.com/watch?v=UQB4W8C0rZI
- branchan 13y agoThis guy is advocating that all aircraft should be designed for short range dogfighting when this aircraft most likely designed for beyond visual range combat. Of course it's gonna lack the maneuverability. Try comparing it to the F22.
- jfb 13y agoIt's not at all clear that fighter aircraft are going to be doing much in any future conflict with e.g. China regardless of how quickly they can shoot down 30 year old technology.
- WildUtah 13y agoYes. By the time the F-35 works, it'll be obsolete for most of its missions because cruise missiles and drones will have utterly surpassed its capabilities.
- Refefer 13y agoI think modern software engineering really needs to start banking on provable languages with strong type systems. Instead of hoping and testing with Monte Carlo sims, let's prove an algorithm once as correct and move on from there.
- Daniel_Newby 13y agoA lot of things, like nonlinear control systems, can only be verified by Monte Carlo methods. Subsystem failure tolerance is difficult to handle by any existing theorem prover. The JSF software organization uses static analyzers heavily. They are using theorem provers.
- mariusz79 13y agoOr in other words - we need to move from art to engineering
- dognotdog 13y agoEngineering is systematic approximations and best-guessing. The art of it is knowing when shortcuts are good enough. Only very small parts of software can be proven, especially for things like flight control, where the parameter space is huge, and exhaustive search or manual formal proofs are impossible. Not even speaking of the fact that the spec against which one could build a proof is never error-free to begin with.
- mariusz79 13y agoAnd what in your opinion is the difference between "systematic approximations and best-guessig" and "knowing when shortcuts are good enough"? For me engineering is using proven and tested solutions every time, even if the solution is not sexy, and art is just "swinging it" - just like using js for everything when they are better more mature solutions.
- dognotdog 13y agoSince you're not building the same thing every time, you don't have wholesale proven and tested solutions for everything. The engineering part is going about filling the gaps systematically, and figuring out what parts require closer inspection in the first place. In my opinion, this last part is the art, figuring out what to do when you tread a new path. A good engineer will find the critical parts, but that relies on as much intuition as process. A really good engineer will find the meta-mistakes in the process. The decision to "swing it" can be an engineering decision. If I am doing something I did before, and all the parts fit, I can swing it, and forego a tedious process. I have to balance the risk of implementation delays and bugs vs. spending time on simulation and paperwork. It's also perfectly possible to do everything by the book and still fail, if the process is a bad fit, or you run out of time because you're all caught up in following procedure instead of taking common sense shortcuts. So either swinging it or doing it by the book can be engineering or idiocy, depending entirely on the situation, and, in retrospect, the outcome.
- GVIrish 13y agoFor another source on the woes bedeviling the F-35, check out this article from Vanity Fair: http://www.vanityfair.com/politics/2013/09/joint-strike-fighter-lockheed-martin http://www.vanityfair.com/politics/2013/09/joint-strike-figh... Some of the highlights include: -DoD skimped on requirements and instead relied on the contractor to fill in the gaps. This led to the plane being designed without protection from lightning strikes which means it can't currently fly in bad weather -The plane was supposed to have 70 percent parts commonality between variants. It is now 25 percent -The plane couldn't do supersonic flight because Lockheed Martin didn't test the stealth coatings at the higher temperatures generated in supersonic flight -The DoD let Lockheed Martin skip a lot of real world testing in favor of computer modeling
- lettergram 13y agoGood god, talk about repair costs...
- a3n 13y agoGood god, talk about opportunity costs.
- fafner 13y agoAnother interesting article about the F-35: https://medium.com/war-is-boring/5c95d45f86a5 https://medium.com/war-is-boring/5c95d45f86a5
- datahipster 13y agoTIL that the $392 billion budget for the F-35 program could have funded NASA's annual budget from 1992-2012.
- 001sky 13y agoThe F35 procurement, would be a good sequel to this: https://www.youtube.com/watch?v=aXQ2lO3ieBA https://www.youtube.com/watch?v=aXQ2lO3ieBA
- jasonwatkinspdx 13y agoThere's both a RAND study and a wargame exercise that found the F-35 severely lacking. You can read more here: http://www.defenseindustrydaily.com/the-f-35s-air-to-air-capability-controversy-05089/ http://www.defenseindustrydaily.com/the-f-35s-air-to-air-cap...
- a8da6b0c91d 13y agoThese analyses seem to overlook the impact of MADL and multi-aircraft sensor fusion. The fire on remote capability, meaning you have a fix on a target that you haven't even detected yourself, plays out huge in stuff I've seen, and it seems believable.
- jasonwatkinspdx 13y agoUnfortunately that's not an advantage unique to Blue side in this analysis. The Su's have a networked co-operative radar as well. There are a few public lectures you can watch from the designers if you like. Su in general favors continuous upgrades of existing inventory so customers don't have to wait for production of a new jet to field it either. They're quite confident in their electronics gear, even to the point of claiming purely passive detection of the F-22 at 50km. Comparing feature bullet points is a pointless exercise. Neither of us being an actual expert on this stuff (I assume), it's most reasonable to take the pros at their word. Doubly so when they're being critical rather than cheer-leading.
- downer84 13y agoWhen bloated pork barrel projects claim center stage with a cacaphony of acrimony, I tend to just assume that it's a facade of staged red tape, designed to act as interference and cover for wherever the real money is being spent. You know, like when massive data centers in Utah are being built for... well... no reason at all!