Stealth fighters hit by software crash


Recommended Posts

A software glitch forced 12 United States Air Force F-22A Raptor stealth fighters to cancel their first overseas flight.

The jets were flying from Hawaii to Japan when they were forced to turn back after suffering problems with their navigation systems.

Retired Air Force general Don Shepperd told CNN Television that the onboard navigation, communications and fuel systems crashed as the planes crossed the International Date Line.

The problem seems to have arisen not from the time change, but from the change in longitude from W179.99 degrees to E180 which occurs on the International Date Line.

The USAF refused to specify the cause of the issue saying only that the aircraft "experienced a software problem involving the navigation system en route from Hickam to Kadena".

For "operational security reasons" the USAF declined to discuss specific aircraft systems or locations.

The F-22A Raptors reportedly had to turn round and return to Hawaii using only visual contact with their tankers.

The $125m planes, the most expensive fighters ever built, returned safely, but the situation may have been disastrous if they had not been with their tankers or the weather had turned bad.

The Raptors have since made it to Kadena with more than 250 personnel from the 27th Fighter Squadron, Langley Air Force Base in Virginia, as part of a scheduled rotational assignment lasting 90 to 120 days.

http://www.vnunet.com/vnunet/news/2184227/...-software-crash

It's Skynet I tell you! It's finally gone online and Judgement Day is around the corner where all machines will rise to destroy the human race. The Terminator will come and try to save one of us from absolute destruction (or Arnold Schwarzenegger if that floats your boat).

:shiftyninja:

Scirwode

Geee. Kind of weird.

Wonder how sophisticated software they have. And why they don't do like russian or the others and use at least as backup already existing realiable, rudimentary technology. If you are a fighter pilot, shouldn't you be so elite to navigate by an old-fasshined altimeter, high-grade manual compass with a gryo or somethinfg like that?

Especieally taking into the price and work they put into the planes?

Or at least have two parallell independent systems running that are not build by the same standars i.e have a different set of possible bugs.

Well well. Good it all went well this time. Hope they debug this code.

Or... maybe they are running a MS system too. Vista Business would be my guess. I'm sure someone sneaked in some unsoppoerted software and the system didn't think it was safe enough.

Who knows.

:-D

You also gotta remember, pretty much all planes are kept in the air because of the electronics - Not because the pilots can't fly.

Well, true. forgot that those are like that. Forward swept wings and unstable aerodynamics. ^^

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop 'Google Chrome' is downloading without you agreeing to it. Fun right? Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!