107
submitted 1 day ago* (last edited 1 day ago) by SeventyTwoTrillion@hexbear.net to c/news@hexbear.net

A reminder that as the US continues to threaten countries around the world, fedposting is to be very much avoided (even with qualifiers like "in Minecraft") and comments containing it will be removed.

Image is a map of Middle Eastern oil/gas production sites, which Iran has promised to strike in retaliation if their own energy infrastructure comes under attack.


My weekly preamble is in spoiler tags below.

preambleFor the weekend of August 1-2, Trump had once again promised major strikes on Iran, which would have included crossing the critical red line of striking their energy infrastructure. In response, Iran once again essentially promised to end the possibility of modern civilization as we know it throughout much of the Gulf States and, to a certain extent, the Zionist entity, with the economic impacts radiating outwards around the world from there. The frustrating part about these threats from Trump is that while he's reneged on them before, the consequences of them actually occurring are so dire that it's difficult to ignore them; rolling a dice with even a 5% chance for complete catastrophe will always be nerve-wracking.

Anyway, as we all know, these strikes did not occur, with the excuse this time being much the same as the previous times: our regional allies begged us not to (potentially true) and Iran called us and said they were willing to negotiate/surrender (untrue). The point of these threat displays is at least twofold: first, to see if Iran is genuinely going to flinch, or, at least, if internal elements that may or may not exist will be spooked into action against the IRGC; and second, to manipulate oil prices downwards by creating constant cycles of "relief" out of an otherwise relatively constant downward trend as Hormuz stays closed and oil reserves continue to ebb. I do say "relatively", of course, given that Ansarallah now appears to be delivering a boot up the ass of Saudi Arabia by taking offline quite a lot of its refinery infrastructure.

It is into this situation that Ukraine seems to want in. For those out of the loop, the situation over in Ukraine has largely the same overall attritional dynamics as previous years, but with a few added wrinkles. Ukraine started striking Russian infrastructure a while ago, and while their effectiveness is hotly debated and I don't want to dismiss them as totally ineffectual, it's clear that the psychological effects - such as they are - are greater than the material effects. Russia's retaliation strikes have been considerably more impactful, including strikes on Ukrainian Black Sea ports and vessels, and a campaign explicitly against gas stations across Ukraine, as well as some rather impressive and disruptive explosions at Ukrainian military fairs and production sites. Zelensky has admitted publicly that they are now basically out of Patriot missiles and that Russian missiles are now landing entirely unopposed (beforehand, they were just landing largely unopposed, given the lackluster performance of Western air defences in general). He seems to have considered a possible way out: linking together the Ukraine and Iran Wars to a united front against Russia and Iran, which would then grant Ukraine more munitions to keep fighting on.

Now, for all the fear I've seen of this occurring (and, don't get me wrong, the US and Russia being in non-proxy, direct conflict is a genuinely frightening prospect for continued life on Earth) how linking together two wars which the West is quite decisively losing into a single war would help at all is beyond me. At this moment, at least, US military planners appear to agree with me. Ukraine hit a Caspian Sea vessel going to Iran a while ago, but then seems to have quickly apologised after being given a stern talking to by the US. This shows just how willing the US is to grant Ukraine more aid, as their own interceptor stockpile is running very low due to Iranian strikes. One would almost feel sympathy for Zelensky if is wasn't for... well, everything that's happened. The path of Ngô Đình Diệm is a tough one to walk.


Last week's thread is here.
The Imperialism Reading Group is here.

Please check out the RedAtlas!

The bulletins site is here. Currently not used.
The RSS feed is here. Also currently not used.

The Zionist Entity's Genocide of Palestine

If you have evidence of Zionist crimes and atrocities that you wish to preserve, there is a thread here in which to do so.

Sources on the fighting in Palestine against the temporary Zionist entity. In general, CW for footage of battles, explosions, dead people, and so on:

UNRWA reports on the Zionists' destruction and siege of Gaza and the West Bank.

English-language Palestinian Marxist-Leninist twitter account. Alt here.
English-language twitter account that collates news.
Arab-language twitter account with videos and images of fighting.
English-language (with some Arab retweets) Twitter account based in Lebanon. - Telegram is @IbnRiad.
English-language Palestinian Twitter account which reports on news from the Resistance Axis. - Telegram is @EyesOnSouth.
English-language Twitter account in the same group as the previous two. - Telegram here.

Mirrors of Telegram channels that have been erased by Zionist censorship.

Russia-Ukraine Conflict

Examples of Ukrainian Nazis and fascists
Examples of racism/euro-centrism during the Russia-Ukraine conflict

Sources:

Moon of Alabama, which tends to have interesting analysis. Avoid the comment section.
Understanding War and the Saker: reactionary sources that have occasional insights on the war.
Alexander Mercouris, who does daily videos on the conflict. While he is a reactionary and surrounds himself with likeminded people, his daily update videos are relatively brainworm-free and good if you don't want to follow Russian telegram channels to get news. He also co-hosts The Duran, which is more explicitly conservative, racist, sexist, transphobic, anti-communist, etc when guests are invited on, but is just about tolerable when it's just the two of them if you want a little more analysis.
Simplicius, who publishes on Substack. Like others, his political analysis should be soundly ignored, but his knowledge of weaponry and military strategy is generally quite good.
On the ground: Patrick Lancaster, an independent and very good journalist reporting in the warzone on the separatists' side.

Unedited videos of Russian/Ukrainian press conferences and speeches.

Pro-Russian Telegram Channels:

Again, CW for anti-LGBT and racist, sexist, etc speech, as well as combat footage.

https://t.me/aleksandr_skif ~ DPR's former Defense Minister and Colonel in the DPR's forces. Russian language.
https://t.me/Slavyangrad ~ A few different pro-Russian people gather frequent content for this channel (~100 posts per day), some socialist, but all socially reactionary. If you can only tolerate using one Russian telegram channel, I would recommend this one.
https://t.me/s/levigodman ~ Does daily update posts.
https://t.me/patricklancasternewstoday ~ Patrick Lancaster's telegram channel.
https://t.me/gonzowarr ~ A big Russian commentator.
https://t.me/rybar ~ One of, if not the, biggest Russian telegram channels focussing on the war out there. Actually quite balanced, maybe even pessimistic about Russia. Produces interesting and useful maps.
https://t.me/epoddubny ~ Russian language.
https://t.me/boris_rozhin ~ Russian language.
https://t.me/mod_russia_en ~ Russian Ministry of Defense. Does daily, if rather bland updates on the number of Ukrainians killed, etc. The figures appear to be approximately accurate; if you want, reduce all numbers by 25% as a 'propaganda tax', if you don't believe them. Does not cover everything, for obvious reasons, and virtually never details Russian losses.
https://t.me/UkraineHumanRightsAbuses ~ Pro-Russian, documents abuses that Ukraine commits.

Pro-Ukraine Telegram Channels:

Almost every Western media outlet.
https://discord.gg/projectowl ~ Pro-Ukrainian OSINT Discord.
https://t.me/ice_inii ~ Alleged Ukrainian account with a rather cynical take on the entire thing.


you are viewing a single comment's thread
view the rest of the comments
[-] Tervell@hexbear.net 51 points 1 day ago

https://archive.ph/T7eU2

Key B-52 upgrades face cost, schedule risks: GAO

A new audit from the Government Accountability Office found concerns with the Air Force’s modernization of the B-52 Stratofortress, which is planned to fly through the middle of the century.

more

A host of upgrades meant to extend the life of the aging B-52 Stratofortress bombers face a number of cost and schedule risks, and officials aren’t properly using all tools at their disposal to shape the aircraft’s modernization, according to a new watchdog report. Collectively, the Air Force plans to spend roughly $21 billion on 13 different upgrades for the B-52, which will keep the Eisenhower-era bomber flying through the 2050s. But two key, expensive efforts — one to replace the aircraft’s eight engines, and another to swap out its radar — are “at risk for additional cost, schedule, and performance challenges,” the Government Accountability Office said in a report published today. The report found that the propulsion overhaul dubbed the Commercial Engine Replacement Program (CERP), which will switch out aging TF33 powerplants manufactured by Pratt & Whitney with modern Rolls-Royce F130 engines, is expected in 2033. That schedule is in line with previous estimates, but its expected cost has now swelled to $15.4 billion, approximately $400 million over the $15 billion projection previously shared by program officials. GAO notes that the cost growth for the CERP effort reflects an over 38 percent jump since 2018, which would normally have triggered a congressionally mandated notification known as Nunn-McCurdy — but didn’t in this case, because the program’s development has been delayed by nearly three years.

GAO found development is now slated to kick off in the third quarter of fiscal 2026, which ended in June. (In May, the Air Force announced CERP passed a critical design review, which typically comes after the start of development known in Pentagon parlance as Milestone B.) But GAO warned that CERP’s overall schedule is still at risk, especially as both engine production and developmental flight testing are set to begin in FY29. Doing both concurrently, the watchdog warned, could mean that unwelcome discoveries spur costly and time-intensive rework. The hasty schedule is largely driven by the need to replace the aircraft’s TF33 engines that will become increasingly difficult to sustain as years pass. Any further delays for the engine overhaul could have cascading effects, GAO noted. While the Air Force is expanding depot capacity, the service has not planned for CERP delays beyond 2031, which risks disrupting the careful choreography of regular maintenance work and various modernization efforts for the in-demand B-52 fleet. Additional CERP schedule slips could render the Air Force “unable to effectively sustain the current B-52 engines and could result in too few B-52s to support operational requirements,” GAO found.

Like with engines, the radar upgrade, dubbed the Radar Modernization Program (RMP) that will integrate an RTX sensor, has seen its own cost and schedule challenges. That program’s budget has ballooned 30 percent to over $2.9 billion — a number lower than a $3.3 billion estimate previously shared by officials, but still enough to previously trigger its own Nunn-McCurdy breach. Similar to prior schedule estimates, the Air Force anticipates RMP will be operational in the third quarter of FY30, three-and-a-half years later than originally expected. And it will come with its own risk of concurrency since production is planned to start with only two months of flight testing completed, out of 18 total planned. While the Air Force has implemented some cost and savings control measures, the service has also removed some unspecified performance requirements. GAO notes that “in this case, after contract award, the Air Force will receive less capability while paying more for the program.” The RMP effort also suffered a tragic setback in June when one of two flight test aircraft for the program crashed shortly after takeoff from Edwards Air Force Base in California, killing all eight crew on board. An Air Force official on Monday said that the program is focusing on supporting the mishap investigation, and will make schedule adjustments as necessary. Elsewhere, GAO noted that while some digital engineering is being used for the CERP program, the other 12 B-52 modernization efforts are not utilizing digital design tools in line with best practices. The dearth of digital engineering, GAO found, means “the Air Force may be missing opportunities to take advantage of efficiencies that digital engineering can provide, including avoiding future sustainment and supportability challenges.”

The watchdog identified organizational issues as well, including that the B-52 fleet is lacking one-third of the unique support equipment it needs. Compounding the problem, it said the Air Force lacks clear guidance on who exactly is responsible for the life cycle management of that equipment. Without that clarity, GAO warned “the Air Force will likely face additional maintenance challenges, which may, in turn, negatively affect the availability of B-52 for operational deployment.” Owing to woes like a lack of spare parts, the report notes that the B-52’s mission capable rates “have not improved” since a November 2022 assessment that found the aircraft was failing to meet benchmarks. However, GAO said in its report today that mission capable rates, schedules and availability for the B-52 were withheld since those details were deemed “sensitive” by the Defense Department. Today the Air Force did not respond by press time when asked for updates on the modernization schedule for the B-52. Both the CERP and RMP efforts are led by prime contractor Boeing, which also did not immediately respond to a request for comment. GAO issued a total of six recommendations, ranging from implementing digital engineering to figuring out who’s responsible for the B-52’s support equipment. The Air Force fully concurred with five, but only partially concurred with a recommendation to delay the CERP’s production decision until the service analyzes the impact of recent cost increases and schedule delays.

this post was submitted on 03 Aug 2026
107 points (100.0% liked)

news

24845 readers
598 users here now

Welcome to c/news! We aim to foster a book-club type environment for discussion and critical analysis of the news. Our policy objectives are:

We ask community members to appreciate the uncertainty inherent in critical analysis of current events, the need to constantly learn, and take part in the community with humility. None of us are the One True Leftist, not even you, the reader.

Newcomm and Newsmega Rules:

The Hexbear Code of Conduct and Terms of Service apply here.

  1. Link titles: Please use informative link titles. Overly editorialized titles, particularly if they link to opinion pieces, may get your post removed.

  2. Content warnings: Posts on the newscomm and top-level replies on the newsmega should use content warnings appropriately. Please be thoughtful about wording and triggers when describing awful things in post titles.

  3. Fake news: No fake news posts ever, including April 1st. Deliberate fake news posting is a bannable offense. If you mistakenly post fake news the mod team may ask you to delete/modify the post or we may delete it ourselves.

  4. Link sources: All posts must include a link to their source. Screenshots are fine IF you include the link in the post body. If you are citing a Twitter post as news, please include the Xcancel.com (or another Nitter instance) or at least strip out identifier information from the twitter link. There is also a Firefox extension that can redirect Twitter links to a Nitter instance, such as Libredirect or archive them as you would any other reactionary source.

  5. Archive sites: We highly encourage use of non-paywalled archive sites (i.e. archive.is, web.archive.org, ghostarchive.org) so that links are widely accessible to the community and so that reactionary sources don’t derive data/ad revenue from Hexbear users. If you see a link without an archive link, please archive it yourself and add it to the thread, ask the OP to fix it, or report to mods. Including text of articles in threads is welcome.

  6. Low effort material: Avoid memes/jokes/shitposts in newscomm posts and top-level replies to the newsmega. This kind of content is OK in post replies and in newsmega sub-threads. We encourage the community to balance their contribution of low effort material with effort posts, links to real news/analysis, and meaningful engagement with material posted in the community.

  7. American politics: Discussion and effort posts on the (potential) material impacts of American electoral politics is welcome, but the never-ending circus of American Politics© Brought to You by Mountain Dew™ is not welcome. This refers to polling, pundit reactions, electoral horse races, rumors of who might run, etc.

  8. Electoralism: Please try to avoid struggle sessions about the value of voting/taking part in the electoral system in the West. c/electoralism is right over there.

  9. AI Slop: Don't post AI generated content. Posts about AI race/chip wars/data centers are fine.

founded 6 years ago
MODERATORS