Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Software Bug Halts F-22 Flight

Posted by kdawson on Sun Feb 25, 2007 06:35 PM
from the dare-you-to-cross-this-line dept.
mgh02114 writes "The new US stealth fighter, the F-22 Raptor, was deployed for the first time to Asia earlier this month. On Feb. 11, twelve Raptors flying from Hawaii to Japan were forced to turn back when a software glitch crashed all of the F-22s' on-board computers as they crossed the international date line. The delay in arrival in Japan was previously reported, with rumors of problems with the software. CNN television, however, this morning reported that every fighter completely lost all navigation and communications when they crossed the international date line. They reportedly had to turn around and follow their tankers by visual contact back to Hawaii. According to the CNN story, if they had not been with their tankers, or the weather had been bad, this would have been serious. CNN has not put up anything on their website yet." The Peoples Daily of China reported on Feb. 17 that two Raptors had landed on Okinawa.
This discussion has been archived. No new comments can be posted.
Software Bug Halts F-22 Flight | Log In/Create an Account | Top | 579 comments (Spill at 50!) | Index Only | Search Discussion
Display Options Threshold:
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • Real redundancy (Score:5, Interesting)

    by chriss (26574) * <chriss@memomo.net> on Sunday February 25 2007, @06:41PM (#18146946)
    (http://memomo.net/)
    As far as I remember the Space Shuttle not only has redundant computer systems, but also redundant software, i.e. the software has been developed twice to ensure that software bugs don't cause a catastrophe. I'd prefer to know that systems capable of carrying weapons which can kill hundreds of thousands of people were designed with the same safety in mind.
  • crash narrowly averted (Score:5, Funny)

    by User 956 (568564) on Sunday February 25 2007, @06:43PM (#18146982)
    (http://www.atomjax.com/)
    CNN television, however, this morning reported that every fighter completely lost all navigation and communications when they crossed the international date line.

    I've heard of a software glitch causing a crash before, but this is ridiculous.
  • I doubt they lost communication... by sonofagunn (Score:2) Sunday February 25 2007, @06:48PM
  • I would not want to be him. by m0biusAce (Score:1) Sunday February 25 2007, @06:48PM
  • Don't worry (Score:5, Funny)

    by Realistic_Dragon (655151) on Sunday February 25 2007, @06:49PM (#18147036)
    (http://www.realistic-dragon.co.uk/)
    We will happily sell y'all Eurofighters. Half the price, twice the bombs... and who the hell do you need stealth to fight anyway? Expecting the France to try and invasion any day now or something?
    • Re:Don't worry by Anonymous Coward (Score:1) Sunday February 25 2007, @07:08PM
    • Re:Don't worry by MSFanBoi2 (Score:2) Sunday February 25 2007, @07:17PM
      • Re:Don't worry by stevew (Score:3) Sunday February 25 2007, @08:07PM
        • Re:Don't worry (Score:5, Interesting)

          by MSFanBoi2 (930319) on Sunday February 25 2007, @08:17PM (#18147750)
          Actually the whole story is a lot more exciting that 5 on 1...

          The 27th Fighter Squadron (8 F-22s) at Langley AFB, Virginia fought against 33 F-15Cs and didn't suffer a single loss. The F-15's again didn't even detect the F-22's until they were all locked and targeted.

          Then some months later during Exercise Northern Edge F-22's reached a 144-to-zero kill-to-loss ratio against F-15s, F-16s and F/A-18s. Only 12 of the F-22's accounted for nearly 50% of all kills for the Exercise.
          [ Parent ]
        • Re:Don't worry by wjsteele (Score:2) Monday February 26 2007, @03:21AM
        • Re:Don't worry by dodobh (Score:2) Monday February 26 2007, @03:49AM
          • Re:Don't worry by stevew (Score:2) Monday February 26 2007, @10:58AM
            • Re:Don't worry by dodobh (Score:2) Monday February 26 2007, @12:01PM
              • Re:STFU MORON by dodobh (Score:2) Tuesday February 27 2007, @06:22AM
              • 1 reply beneath your current threshold.
          • Re:Don't worry by The One and Only (Score:2) Monday February 26 2007, @11:58AM
      • 1 reply beneath your current threshold.
    • Re:Don't worry by wirelessbuzzers (Score:1) Sunday February 25 2007, @07:27PM
      • Re:Don't worry by Martin Blank (Score:2) Sunday February 25 2007, @07:45PM
        • Re:Don't worry by devilspgd (Score:2) Sunday February 25 2007, @07:58PM
          • Re:Don't worry by Dun Malg (Score:2) Monday February 26 2007, @12:21AM
            • Re:Don't worry by devilspgd (Score:2) Monday February 26 2007, @12:28AM
              • Re:Don't worry by Martin Blank (Score:2) Monday February 26 2007, @09:31AM
          • Re:Don't worry by KDR_11k (Score:1) Monday February 26 2007, @05:21AM
      • Re:Don't worry by MSFanBoi2 (Score:1) Sunday February 25 2007, @07:47PM
      • Re:Don't worry by abradsn (Score:2) Sunday February 25 2007, @07:51PM
        • Re:Don't worry by stevew (Score:2) Sunday February 25 2007, @08:11PM
        • Re:Don't worry by Marcos Eliziario (Score:2) Sunday February 25 2007, @09:47PM
        • 1 reply beneath your current threshold.
      • Re:Don't worry by devilspgd (Score:2) Sunday February 25 2007, @08:01PM
        • Re:Don't worry by Marcos Eliziario (Score:2) Sunday February 25 2007, @09:51PM
          • Re:Don't worry by Dunbal (Score:2) Sunday February 25 2007, @11:29PM
            • Re:Don't worry by hardburn (Score:1) Monday February 26 2007, @01:30AM
              • Re:Don't worry (Score:4, Insightful)

                As shown in Vietnam and the current Iraq situation, America has great difficulty in fighting a loosely-organized resistance.

                      It's because we care about killing innocent civilians, and they are indistinguishable from innocent civilians.

                      If we can't identify the enemy, it's a good sign we shouldn't be there.

                  rd
                [ Parent ]
              • Re:Don't worry by CKW (Score:2) Monday February 26 2007, @06:38PM
            • Re:Don't worry by ggvaidya (Score:1) Monday February 26 2007, @05:10AM
          • Re:Don't worry by devilspgd (Score:2) Sunday February 25 2007, @11:29PM
            • Re:Don't worry by Marcos Eliziario (Score:2) Wednesday February 28 2007, @11:36PM
          • Re:Don't worry by Simon Garlick (Score:2) Monday February 26 2007, @01:45AM
            • Re:Don't worry by wirelessbuzzers (Score:2) Monday February 26 2007, @03:20AM
            • Re:Don't worry by devilspgd (Score:2) Monday February 26 2007, @12:23PM
              • Re:Don't worry by Marcos Eliziario (Score:2) Wednesday February 28 2007, @11:39PM
            • Re:Don't worry by Marcos Eliziario (Score:2) Wednesday February 28 2007, @11:41PM
        • Re:Don't worry by Dunbal (Score:3) Sunday February 25 2007, @11:23PM
        • Re:Don't worry by Sloppy (Score:2) Monday February 26 2007, @09:34AM
    • Re:Don't worry by Original Replica (Score:2) Sunday February 25 2007, @07:47PM
    • Re:Don't worry by TopSpin (Score:2) Sunday February 25 2007, @07:57PM
      • 1 reply beneath your current threshold.
    • Re:Don't worry by Rakishi (Score:2) Sunday February 25 2007, @08:41PM
    • Re:Don't worry by Realistic_Dragon (Score:2) Sunday February 25 2007, @07:10PM
      • Re:Don't worry by Dun Malg (Score:2) Monday February 26 2007, @12:12AM
    • Re:Don't worry (Score:4, Insightful)

      by Dunbal (464142) on Sunday February 25 2007, @11:45PM (#18149124)
      Not to mention that the only decent fighters Europe have ever created were all WWII era...

            I dunno, the Americans seemed to quite like the idea of the AV-8A Harrier [wikipedia.org], a British creation.
      [ Parent ]
    • 4 replies beneath your current threshold.
  • Source code... (Score:5, Funny)

    by alexhs (877055) on Sunday February 25 2007, @06:49PM (#18147042)
    (http://dr-tools.sourceforge.net/ | Last Journal: Tuesday January 23 2007, @10:27AM)
    That's the real reason why they don't want to give source code to foreign armies... They don't want to be covered in shame :)
    • 1 reply beneath your current threshold.
  • UTC (Score:3, Insightful)

    by Excelcia (906188) <kfitzner@excelcia.org> on Sunday February 25 2007, @06:50PM (#18147052)
    (http://excelcia.org/)
    The answer to all these problems is very simple. For any mission critical application, use UTC and only UTC. No time zones, no date line, no converting. If the software isn't even aware of the concept of date/time localization, then it's not going to run into problems.

    Oh, and while they're at it, standardize on metric too. Maybe we can save our interstellar probes at the same time we are saving our warplanes.
    • Re:UTC (Score:5, Informative)

      by Chmcginn (201645) <agburanar@gmail.c3.14om minus pi> on Sunday February 25 2007, @06:57PM (#18147112)
      (Last Journal: Saturday November 03, @10:54PM)
      They probably already do... When I was spending time in uniform, all our (non-workstation) computers did all their work in GMT, anyway. And considering it was the navigation systems that crashed, I think the "international date line" thing is spurious - the problem was more likely going from W to E, not today to yesterday.
      [ Parent ]
      • Re:UTC by Max Littlemore (Score:1) Sunday February 25 2007, @07:39PM
        • Re:UTC by Chmcginn (Score:2) Sunday February 25 2007, @08:06PM
          • Re:UTC by ColaMan (Score:2) Sunday February 25 2007, @09:46PM
        • Re:UTC by chgros (Score:2) Monday February 26 2007, @01:18AM
          • Re:UTC by Max Littlemore (Score:2) Monday February 26 2007, @05:37PM
        • 1 reply beneath your current threshold.
      • Re:UTC by ralphdaugherty (Score:2) Monday February 26 2007, @01:40AM
      • 1 reply beneath your current threshold.
    • Re:UTC by Dun Malg (Score:3) Monday February 26 2007, @12:28AM
      • Re:UTC by rbarreira (Score:2) Monday February 26 2007, @05:08AM
    • Re:UTC by leenoble_uk (Score:1) Monday February 26 2007, @08:07AM
    • 2 replies beneath your current threshold.
  • Reminds me of the Bismarck (Score:5, Interesting)

    by blind biker (1066130) on Sunday February 25 2007, @06:50PM (#18147054)
    (Last Journal: Sunday September 02, @06:01PM)
    The Bismarck battleship had a bug also: when the main turrets would fire, the aiming radars would be disabled. That's no joke when you're in the midst of a battle and everyone of those large caliber shells counts. As I understand, the radars would be disabled by the vibrations of the turret cannons firing. Not a software bug, but bug nonetheless, and you do wonder how did this battleship pass testing.
  • Gotta know your limitations... (Score:5, Informative)

    by TigerNut (718742) on Sunday February 25 2007, @06:51PM (#18147076)
    (http://members.shaw.ca/tsmit/index.html | Last Journal: Friday September 21, @08:24AM)
    When I worked at a high end civilian GPS equipment manufacturer, we had a test department where, among other things, a complete list of "special" dates and locations were kept on file. Any new position solution software release was regression tested against all previously known and guessed potential date/time rollovers, as well as making sure that motion across geographic coordinate boundaries didn't cause erratic behavior. Obviously whoever supplied the inertial navigation solution for the F22 hasn't quite gotten there yet... Testing in the lab is cheap. Burning a couple of tons of Jet-A and putting a bunch of people at risk is not.
  • by CardinalPilot (1057108) * on Sunday February 25 2007, @06:52PM (#18147078)
    The F-22 has a fly-by-wire control system. If there really were a crash of ALL on-board computer systems, communication and navigation would not have been the most immediate concerns!
  • Design? Lack of foresight? (Score:5, Insightful)

    by the_skywise (189793) on Sunday February 25 2007, @06:55PM (#18147092)
    Assuming it WAS a time issue upon crossing the International Dateline...

    Design problem? Why should navigation software require "local time"? They knew they were crossing the international dateline, so they must be linked to GPS timing systems... why not just use GPS' universal time? (Sure, you want local time eventually for your displays but that's a "view" calculation, not one intrinsic to the navigation software)

    Bug tracking problem? Did the testers not think of testing about a time zone change? Did they assume the above that everything would be on a universal time and therefore didn't see the need for crossing time zones?

    Why wasn't this a stock reusable code module in Lockheed Martin's labs?!?

    (And for a media look at this issue, check out the anime Geneshaft or the movie The Pentagon Wars)
  • Were they running Windows? (Score:5, Funny)

    by pestilence669 (823950) on Sunday February 25 2007, @06:56PM (#18147106)
    I just want to know if this is in any way connected to the nuclear subs that lost navigation after they switched to Microsoft Windows based software. Generally, when this kind of thing happens, some external vendor is to blame.
  • Ironically (Score:5, Funny)

    by mbrod (19122) on Sunday February 25 2007, @06:57PM (#18147114)
    (http://harun.abd.assami.googlepages.com/ | Last Journal: Thursday November 25 2004, @12:07AM)
    A few days ago reading up on good C++ coding techniques I came across Stroustrup's (creator of C++) page citing the coding rules used [att.com] when working on the Joint Strike Fighter [wikipedia.org]. Reading through the various rules used, this one caught my attention:

    AV Rule 25 (MISRA Rule 127)
    The time handling functions of library <time.h> shall not be used.

    I got to thinking if we had any decent alternatives (at least in C++). And yes there are alternatives and all of them looked equally bad to me. Looks like the F22 guys might have had the same problem finding and using a robust fault tolerant time library.

    • Re:Ironically by Alizarin Erythrosin (Score:3) Sunday February 25 2007, @07:34PM
    • Re:Ironically by macshit (Score:2) Monday February 26 2007, @02:08AM
    • Re:Ironically (Score:4, Informative)

      by julesh (229690) on Monday February 26 2007, @06:38AM (#18151240)
      A few days ago reading up on good C++ coding techniques I came across Stroustrup's (creator of C++) page citing the coding rules used when working on the Joint Strike Fighter. Reading through the various rules used, this one caught my attention:

              AV Rule 25 (MISRA Rule 127)
              The time handling functions of library shall not be used.

      I got to thinking if we had any decent alternatives (at least in C++). And yes there are alternatives and all of them looked equally bad to me. Looks like the F22 guys might have had the same problem finding and using a robust fault tolerant time library.


      Why would you need to use a library? The only format you're likely to need in such software is milliseconds offset from some suitable epoch. As long as your hardware can produce such a time value, you're fine.
      [ Parent ]
    • 1 reply beneath your current threshold.
  • I call bull... by flyingfsck (Score:2) Sunday February 25 2007, @06:59PM
  • Er what? (Score:4, Insightful)

    by chanrobi (944359) on Sunday February 25 2007, @07:05PM (#18147170)
    Are you telling me that the F-22 has no analog backup flight system? For gosh sakes even the F-16 has a similar system. A cursory google search that the F-22 is equipped with an "LN-100G Inertial Navigation System with Embedded GPS". It sounds incredible that the summary implies that the only way they would've made it home was via formation flying with a tanker? Can anyone with more detailed information on the F-22 clarify?
    • Re:Er what? (Score:4, Insightful)

      by Jerf (17166) on Sunday February 25 2007, @11:55PM (#18149172)
      (Last Journal: Saturday August 18 2001, @11:04AM)
      Before you go ballistic, bear in mind that unless you've got data sources beyond those cited in the Slashdot blurb, the most technical details come from CNN, which is about one step from priding itself on its ignorance of military matters, and has a less-than-distinguished history on the technical details front as well. Put the two together and the odds are low that you've got anything like an accurate view, let alone a complete one.

      You can trust the what and the when; I wouldn't trust their how or why any further than I could spit.

      (This isn't anti-CNN; this is anti-almost-everything news media. Journalists aren't required to learn squat about science or technology for their degree and it tends to show up in every last article they write with even a passing connection to science or technology. Any even cursory overview of stories on any technical subject you know about will reveal this. Remember that "multi-gear rocket" atrocity from a day or two ago?)
      [ Parent ]
      • Re:Er what? by gordguide (Score:2) Monday February 26 2007, @12:19PM
    • by igb (28052) on Monday February 26 2007, @02:11AM (#18149872)
      You can't fly planes like that manually, becuase they are inherently unstable. Even non-stealth aircraft have this property, in order to make them more sensitive in roll. A civilian plane will self-centre from small roll inputs, and you have to overcome that effect to actually roll. The stealth aircraft are such weird shapes, for which aerodynamics come second to radar cross-section, that the designers don't even have the choice.

      ian

      [ Parent ]
    • Why they train pilots by BanjoBob (Score:2) Saturday March 03 2007, @05:45PM
    • Re:Er what? by NeMon'ess (Score:1) Sunday February 25 2007, @10:59PM
      • Re:Er what? by AragornSonOfArathorn (Score:2) Sunday February 25 2007, @11:08PM
        • Re:Er what? by NeMon'ess (Score:2) Monday February 26 2007, @03:00AM
      • Re:Er what? by NMerriam (Score:2) Sunday February 25 2007, @11:46PM
        • Re:Er what? by NeMon'ess (Score:2) Monday February 26 2007, @03:06AM
        • Re:Er what? by zippthorne (Score:2) Monday February 26 2007, @01:40PM
    • 3 replies beneath your current threshold.
  • So... (Score:5, Funny)

    by WaZiX (766733) on Sunday February 25 2007, @07:08PM (#18147192)
    So, when is Service Pack 1 coming out?
    • Re:So... by Botia (Score:1) Sunday February 25 2007, @08:28PM
    • 2 replies beneath your current threshold.
  • Thanks to the foresight of the Eurofighters... by TransEurope (Score:1) Sunday February 25 2007, @07:09PM
    • 1 reply beneath your current threshold.
  • Actual dialog message... (Score:5, Funny)

    by Anonymous Coward on Sunday February 25 2007, @07:12PM (#18147218)
    You are flying to Japan, Cancel or Allow?
  • F16 Software had similar problems (Score:5, Interesting)

    by Anonymous Coward on Sunday February 25 2007, @07:22PM (#18147332)
    When F16s crossed the equator, the computer would roll the aircraft 180 degrees and fly inverted:

    http://catless.ncl.ac.uk/Risks/3.44.html [ncl.ac.uk]

  • Microsoft? (Score:5, Funny)

    by Yvan256 (722131) on Sunday February 25 2007, @07:29PM (#18147384)
    (http://www.yvan256.net/)

    every fighter completely lost all navigation and communications when they crossed the international date line.
    Where do you want to go today?

  • Correct Story? by shields020 (Score:2) Sunday February 25 2007, @07:29PM
  • I think by Headw1nd (Score:2) Sunday February 25 2007, @07:35PM
  • READ: Get Ready For More (Score:5, Interesting)

    by N8F8 (4562) on Sunday February 25 2007, @07:37PM (#18147462)
    I tried posting this on several sites but on March 11th [wikipedia.org], when the new daylight savings [wikipedia.org]regime kicks in for the first time there will probably be a lot of Java applications that will start having data issues because the latest Java version IS NOT BACKWARDS COMPATIBLE for several three character time codes that have bee removed. Several codes have been deprecated in a way that is not backwards compatible. I could be wrong about the severity, but for he last two weeks my software team has been dealing with this issue and the interaction between Oracle and Java.
  • Easy fix ..... by taniwha (Score:2) Sunday February 25 2007, @07:48PM
  • Google Maps related problem by sugarmotor (Score:2) Sunday February 25 2007, @07:53PM
  • I told them... (Score:5, Funny)

    ...not to run Windows on those machines. They HAD to upgrade to Vista because of all the cool 'features' the pilots would like to see. First we had to put more ram in and an extra video card, now this... I'm telling ya, next time Microsoft gives them a better deal because they're switching to Linux, they shouldn't accept.
  • Website by linux pickle (Score:2) Sunday February 25 2007, @08:03PM
    • Re:Website by uncleFester (Score:3) Sunday February 25 2007, @08:31PM
  • not the only problem I read... (Score:5, Interesting)

    by Bobzibub (20561) on Sunday February 25 2007, @08:34PM (#18147900)
    All complex systems have bugs that need to be ironed out....

    http://www.atimes.com/atimes/Middle_East/IB10Ak05. html [atimes.com]
    "Keys notes, however, that the electronic spectrum around Baghdad is polluted by the myriad jamming devices that coalition forces primarily employed to thwart remote detonations of the improvised explosive devices that have inflicted 70% of all US fatalities in that war." ...
    "The potential problem was discovered when the first F-22s were operating near US Navy ships off the Atlantic coast. Navy radars overwhelmed the F-22's automated sensors. Even now, larger, multi-station, purpose-built electronic-intelligence-gathering airplanes encounter difficulties around the Iraqi capital because of the extreme density of jamming devices."

  • It was that damn UAC again! by GFree (Score:2) Sunday February 25 2007, @08:38PM
  • Flight systems? by RealGrouchy (Score:1) Sunday February 25 2007, @08:42PM
  • Simple Solution by volpe (Score:2) Sunday February 25 2007, @08:45PM
  • WTF by DragonTHC (Score:1) Sunday February 25 2007, @09:00PM
  • Carry backup. (Score:4, Funny)

    by jo7hs2 (884069) on Sunday February 25 2007, @09:01PM (#18148108)
    My advice to F-22 pilots: 1) Superglue a handheld GPS into your cockpit. 2) Carry a backup radio. Superglue this to your cockpit. 3) Remove your cockpit, and superglue it onto an A-10. 4) Fly safe. Carry superglue.
  • by ross.w (87751) <rwonderley@nOSPAM.gmail.com> on Sunday February 25 2007, @09:01PM (#18148114)
    (Last Journal: Tuesday March 16 2004, @08:30PM)
    They wouldn't have made it here. I knew there was a good reason.
  • So who makes the Air Force's software? by JAB Creations (Score:1) Sunday February 25 2007, @09:11PM
  • What OS was the crashed CPU running? by Lost Penguin (Score:1) Sunday February 25 2007, @09:18PM
  • How to avoid US forces by Leemeng (Score:1) Sunday February 25 2007, @09:20PM
  • Y2Day by Overkill Nbuta (Score:1) Sunday February 25 2007, @09:39PM
  • Aero Glass (Score:3, Funny)

    by lord_sarpedon (917201) on Sunday February 25 2007, @09:43PM (#18148430)
    What's more, one pilot tried to turn off Aero Glass -- suddenly, he lost cabin pressure.
  • Frakking Toasters!!! by gijoel (Score:1) Sunday February 25 2007, @09:45PM
  • Simple Solution by Gerocrack (Score:1) Sunday February 25 2007, @10:58PM
  • Not all of the computers chrashed by Braedley (Score:1) Sunday February 25 2007, @11:55PM
  • Was it running Windows Embedded? by Taelron (Score:2) Monday February 26 2007, @12:52AM
  • Interesting question. by massivefoot (Score:2) Monday February 26 2007, @01:58AM
  • What programming language? what bug? by master_p (Score:2) Monday February 26 2007, @04:52AM
  • It's not a bug... it's a feature... by markfid (Score:1) Monday February 26 2007, @05:15AM
  • The software should have been layered by octogen (Score:1) Monday February 26 2007, @05:37AM
  • Show me the CNN report please by allmeta4 (Score:1) Monday February 26 2007, @05:43AM
  • SR1 by nmg196 (Score:2) Monday February 26 2007, @06:37AM
  • Funny. by Runefox (Score:2) Monday February 26 2007, @06:48AM
  • I call shenanigans! by rindeee (Score:2) Monday February 26 2007, @07:08AM
  • You go to war by gelfling (Score:2) Monday February 26 2007, @07:29AM
  • Division by zero? by Andrew5544 (Score:1) Monday February 26 2007, @09:19AM
  • Once again, don't trust computers for simple stuff by Catbeller (Score:2) Monday February 26 2007, @10:55AM
  • Same bug, different day by Cervantes (Score:2) Monday February 26 2007, @11:17AM
  • Ha ha? by BarnabyWilde (Score:1) Monday February 26 2007, @12:00PM
  • I call bullshit! by BarnabyWilde (Score:1) Monday February 26 2007, @12:05PM
  • I had this info a week ago... by noah716 (Score:1) Monday February 26 2007, @01:48PM
  • Bugs in the air... by owidder (Score:1) Monday February 26 2007, @05:07PM
  • I hate calendar code... is this story censored? by elstaqub (Score:1) Monday February 26 2007, @08:37PM
  • System Testing by infonote (Score:1) Saturday March 03 2007, @07:27AM
  • Re:Overflow by MindKata (Score:1) Sunday February 25 2007, @06:41PM
    • Re:Overflow by MindKata (Score:1) Sunday February 25 2007, @06:43PM
      • 1 reply beneath your current threshold.
    • Re:Overflow (Score:5, Interesting)

      by Dun Malg (230075) on Sunday February 25 2007, @11:09PM (#18148934)
      (https://addons.mozil...&application=firefox)

      just as well it wasn't in the fire a [missile] flag byte ... or worse still, the ejector seat flag byte.
      Yeah... uh... you know, in the same way they simply do not and never would have the navigation system connected to the In-Flight Entertainment system in an airliner [slashdot.org], likewise they would never slave the ejection system to anything other than the mechanical operation of that yellow handle between the pilot's knees.

      As for missiles? First, they fly unarmed on ferry missions because ammo is dead weight that reduces range; and second, even if they were armed, what do you really think would happen if an AMRAAM missile was free launched without being turned on, much less having had targeting info downloaded? Drop like a stone, it would, right into the pacific. Bloop. All gone.

      Say it's also a good thing water isn't flammable, otherwise fire trucks would show up to fires and only make the situation worse, right?
      [ Parent ]
      • Re:Overflow (Score:4, Funny)

        by Gospodin (547743) on Monday February 26 2007, @09:55AM (#18152784)

        As for missiles? First, they fly unarmed on ferry missions because ammo is dead weight that reduces range; and second, even if they were armed, what do you really think would happen if an AMRAAM missile was free launched without being turned on, much less having had targeting info downloaded? Drop like a stone, it would, right into the pacific. Bloop. All gone.

        So you say. But if you think sharks with frickin' lasers on their heads are scary, imagine sharks with fricking' AMRAAMs.

        [ Parent ]
        • Re:Overflow by alienmole (Score:2) Tuesday February 27 2007, @11:33AM
      • Re:Firetrucks by Gription (Score:1) Monday February 26 2007, @10:54AM
      • Re:Overflow by WNight (Score:2) Monday February 26 2007, @11:06AM
        • Re:Overflow by Bastard of Subhumani (Score:1) Monday February 26 2007, @12:13PM
          • Re:Overflow by WNight (Score:2) Monday February 26 2007, @09:47PM
            • Re:Overflow by Bastard of Subhumani (Score:1) Tuesday February 27 2007, @11:44AM
              • Re:Overflow by WNight (Score:2) Tuesday February 27 2007, @03:30PM
        • Re:Overflow by Littleman_TAMU (Score:2) Monday February 26 2007, @01:04PM
          • Re:Overflow by WNight (Score:2) Monday February 26 2007, @08:43PM
  • Re:I've been wondering... by Anonymous Coward (Score:1) Sunday February 25 2007, @06:43PM
  • Re:Overflow (Score:5, Insightful)

    by Anonymous Coward on Sunday February 25 2007, @06:48PM (#18147016)
    The problem probably isn't with the time change. Airplanes use GMT so the local time doesn't matter. The problem is probably related to the longitude going from W179.99 degrees to E180 degrees.
    [ Parent ]
  • Re:first post to say.. (Score:5, Funny)

    by alx5000 (896642) <alx5000@alx5 0 0 0 .net> on Sunday February 25 2007, @07:05PM (#18147162)
    (http://vistoenbp.net/)
    Sure, but it seems they turned Aero off..
    [ Parent ]
  • by sbaker (47485) * on Sunday February 25 2007, @07:10PM (#18147204)
    (http://www.sjbaker.org/)
    You'd think they'd have learned from this one:

            http://www.f20a.com/f20ins.htm [f20a.com]
    [ Parent ]
  • by kabloom (755503) on Sunday February 25 2007, @07:11PM (#18147208)
    (http://www.iit.edu/~kbloom1/)
    Yes. When Jews cross the dateline, we don't [star-k.org] know [koltorah.org] what day it is anymore, much to the consternation of those of us who may need to travel to Japan or Hawaii.
    [ Parent ]
    • Your point? by BluBrick (Score:2) Sunday February 25 2007, @08:07PM
    • 1 reply beneath your current threshold.
  • Fixed (Score:5, Informative)

    Well, whatever the issue - which is probably something similar to what you suspect - it's now fixed. Here's the transcript from CNN this morning. Since the F-22 is fly-by-wire, it's also worth pointing out that all systems didn't crash, else these F-22s would be sitting in the Pacific. I've no doubt it affected navigation, communications, and similar subsystems, and was probably related to physical location in terms of time, position over the Earth, or both, given the nature of the issue.

    >> 25 Years from development to deployment, the F-22 Raptor is the most advanced fighting machine in the air. It was no match for a computer glitch that left six of them high above the pacific ocean, deaf, dumb, and blind as they headed to their first deployment. So what happened? We turn to a man that's at home in the cockpit. Retired Air Force General Don Shepperd. Let me set the scene, Don. These F-22s, headed from the Air Force base in Hawaii to an Air Force base in Japan. They were approaching the international date line, pick it up from there.

    >> You got it right. You want everything to go right with the frontline fighter. $125, 135 Million a copy. The F-22 raptor is our frontline fighter, air defense, air superiority, and it can drop bombs. It is stealthy and fast. You want it to go right. On the international deployment to the pacific, it didn't. At the international date line, whoops. All systems dumped. When i say all systems I mean all systems, navigation, part of the communications, fuel systems, and they were -- they could have been in real trouble. They were with their tankers. The tankers -- tried to reset their systems. Couldn't get them reset. Tankers brought them back to Hawaii. This could have been real serious. Certainly could have been real serious if the weather had been bad. Turned out okay. Fixed in 48 hours. It was a computer glitch in the millions of lines of code; somebody made an error in a couple lines of the code and everything goes.

    >> This is almost like the feared Y2K problem that happened to these aircraft. We should point out, the computer problems in 2000. The computers absolutely went absolutely haywire and became useless?

    >> Absolutely. When you think of airplanes from the old days, with cables and that type of thing and connects between the sticks and the yokes and the controls -- not that way anymore. Everything is by computer. When your computers go the airplanes go. You have multiple systems. When they all dump at the same time, you can be in real trouble. Luckily this turned out okay.

    >> What would have happened if these brand-new $120 million F-22s had been going into battle?

    >> You would have been in real trouble in the middle of combat. The good thing is we found this out. Any time -- before, you know, before we get into combat with an airplane like this. Any time you introduce a new airplane, you are going to find glitches, and you are going to find things that go wrong. It happens in our civilian airliners. You don't hear much about it. These things absolutely happen. And luckily had time we found out about it before combat. We got it fixed with tiger teams in about 48 hours and the airplanes were flying again, and completed the deployment. This could have been real serious in combat.

    >> You had these advanced air -- not just superiority but air supremacy fighters in there, up there in the air, above the Pacific Ocean, not much more sophisticated than a Cessna 152 with a jet engine?

    >> You got it. They are on a 15-hour flight from Hawaii to Okinawa. When all their systems dumped, they needed help. Had they gotten separated from their tankers or weather gotten bad they had no reference and no communications or navigation. They would have turned around and could have found the Hawaiian Islands. If the weather had been bad on approach there could have been real trouble. You get refueling from your tankers and you don't run -- you don't get yourself where you run out of fuel. You always have enough fuel and refueling nine, ten, 12 times like this. Where you can get somewhere to land. But again, attitude reference and navigation are essential as this communication. In this case all of that was affected. It was a serious problem.

    >> The fact the computers run so much of the systems on the aircraft, is the -- is the military at risk of over-engineering here so if they did have a problem like that when they were going into a hostile situation they could be, as you said, repeatedly in real trouble?

    >> Well, you have redundant systems. It is the fact of life. In the modern computer age. By the way you are going to have the same problem coming up on your laptop computer as we conferred from -- from standard time from daylight savings time to standard time. Your program -- your computer is programmed for one thing and we have changed the dates and you are going to have a problem and it will have to be dealt with.

    >> Do me a favor. Make sure i'm not on my laptop computer when i'm flying in an F-22 on that day.

    >> Absolutely.

    >> Appreciate it. Thank you, sir.
    [ Parent ]
    • Re:Fixed by myowntrueself (Score:2) Sunday February 25 2007, @08:02PM
    • Millions of lines of code? by Gazzonyx (Score:1) Sunday February 25 2007, @08:25PM
    • Re:Fixed (Score:5, Insightful)

      by rbanffy (584143) on Sunday February 25 2007, @10:15PM (#18148628)
      (http://www.dieblinkenlights.com/)

      It is the fact of life. In the modern computer age.

      It sure doesn't need to be like that.

      Our desktop computers crash because we can tolerate crashes. There is some redundancy - if my notebook crashes, I reboot it and, in a couple minutes, I am back to work. If it breaks, I grab another computer and continue.

      A plane, on the other hand, should work at all times. When lives depend on some equipment, one should enforce much higher standards than we do on desktop or even mission-critical busines software. Nobody dies if your sales people have a 5 minute outage. Nobody dies if you can't create a patient record. People die when the computers a plane relies upon fail.

      It's completely unacceptable - and quite alarming - to see a plane malfunction like that on its first deployment.

      Things like that should have been exercised years ago. By now, the code should be rock-stable. Whant kind of quality assurance they did?

      [ Parent ]
      • Re:Fixed (Score:5, Insightful)

        by 0100010001010011 (652467) on Sunday February 25 2007, @11:55PM (#18149182)
        And even more people die when all systems work perfectly.
        [ Parent ]
        • 1 reply beneath your current threshold.
      • Re:Fixed by darkwhite (Score:2) Monday February 26 2007, @01:31AM
      • Re:Fixed by hador_nyc (Score:1) Monday February 26 2007, @10:40AM
        • Re:Fixed by Intron (Score:2) Monday February 26 2007, @12:15PM
          • Re:Fixed by hador_nyc (Score:1) Monday February 26 2007, @12:32PM
            • Re:Fixed by Intron (Score:2) Monday February 26 2007, @12:44PM
              • Re:Fixed by hador_nyc (Score:1) Monday February 26 2007, @12:50PM
        • Re:Fixed by rbanffy (Score:2) Monday February 26 2007, @01:39PM
          • Re:Fixed by hador_nyc (Score:1) Monday February 26 2007, @02:21PM
            • Re:Fixed by ralphdaugherty (Score:2) Monday February 26 2007, @10:09PM
            • Re:Fixed by rbanffy (Score:2) Wednesday February 28 2007, @07:14AM
      • Re:Fixed by rbanffy (Score:2) Monday February 26 2007, @01:06PM
        • Re:Fixed by sp3d2orbit (Score:2) Monday February 26 2007, @01:56PM
          • Re:Fixed by rbanffy (Score:2) Wednesday February 28 2007, @05:56AM
            • Re:Fixed by sp3d2orbit (Score:1) Wednesday February 28 2007, @08:51PM
              • Re:Fixed by rbanffy (Score:2) Thursday March 01 2007, @01:03PM
                • Re:Fixed by sp3d2orbit (Score:1) Friday March 02 2007, @01:15PM
      • 2 replies beneath your current threshold.
    • Do say! by qzulla (Score:1) Sunday February 25 2007, @10:16PM
      • Re: not so... by Cryptnotic (Score:2) Sunday February 25 2007, @10:54PM
      • 1 reply beneath your current threshold.
    • The post-incident report (Score:5, Informative)

      by DingerX (847589) on Monday February 26 2007, @03:00AM (#18150134)
      (Last Journal: Wednesday February 21 2007, @08:20AM)
      His comments are based on a post-incident report that's been making the rounds on teh intardnet. I'll just paste it in here, if anybody's still reading. I don't vouch for its authority, other than A) I got it off the net, and B) it came with a note saying it was unclassified. Oh yeah, and it matches what the talking head says -- the navigation system brought down all their avionics. it also states what the QA process was that led to the problem:

      Date: 12 Feb 07

      To: CC

      Info: CV, DS

      Narrative:


      1. A 1st Fighter Wing AEF 6-ship (Petro 91) departed Hickam AFB enroute to AEF location on 10 Feb. Approximately 4 hours into the mission and coincidental with crossing over the International Date Line, all six aircraft experienced a significant avionics failure including:

      Both GINS 1 and 2 Fail

      FLCS Degrade

      Radar Fail

      Fuel Degrade

      Loss of all attitude references

      Loss of Flight Path marker

      Loss of all navigation aides (TACAN, ILS, Computed, etc.)

      Loss of all heading indications

      2. Aircraft communications were available via backup radio only. Only navigation available was via cockpit airspeed and altitude indications (both deemed accurate). All other aircraft systems, to include engines, electrical system and air refueling, were nominal.

      3. Flight Lead, Lt Col Tolliver, initiated via the tanker a CONFERENCE HOTEL (CH) call with LM Aero. All CH team recommended workarounds (avionics restarts, date and time resets, etc.) did not resolve the problem.

      4. Lt Col Tolliver assessed pressing to the AEF location but decided to turn back and return to Hickam. He also directed the second deployment cell, a 2-ship approximately one hour behind him, to return to Hickam. NOTE: This 2-ship never crossed the International Date Line.

      5. Enroute back to Hickam, after crossing back over the International Date Line, avionics restarts were unsuccessfully attempted.

      6. All aircraft successfully recovered at Hickam, shut down (cold iron), restarted engines and all avionics malfunctions cleared.

      7. An F-22 Crisis Management Team (CMT) has convened. Two telecoms (1300 and 1700 EST) were conducted on 11 Feb. Participants included F-22 Program Office, LM, Boeing, NG and A8F personnel.

      8. The F-22 Program is working 24/7 to resolve this issue. Both F-22 avionics integration labs (RAIL and AIL) have successfully duplicated the problem. The problem resides within the GINS software when the aircraft transitions between East/West Longitude. NOTE: Most RAIL and AIL testing simulate GINS inputs and past testing discovered no issues with over flying the Dateline or Poles. It took testing this weekend using actual GINS hardware and software to duplicate this problem.

      9. A fix for this software problem has been developed at NG and currently is being evaluated in the RAIL. We should find out at our 1300 CMT telecom today if this fix works.

      10. This fix will require an OFP update to be loaded on the aircraft. Currently no IMIS OFP loading support is on-site at Hickam. 1 FW IMIS was previously deployed to AEF location.

      11. F-22 Program currently expects software fix, OFP loading hardware and LM support team in place at Hickam by mid-week. Aircraft possibly will be able to depart Hickam for their AEF location by the end of the week.

      12. Updates to this issue will be provided as additional information becomes available.
      Translation: The navigational system (Global Positioning Inertial Navigation Systems (GINS)) had never been physically tested crossing the date line, but only on simulated real-world inputs. When it crossed the date line for the first time, it crashed, as did the backup, bringing down with it all navigational systems and much of the aircraft's instrumentation, leaving them with backup systems reminiscent of a Cessna 172 (without the navigational stack).
      [ Parent ]
    • 1 reply beneath your current threshold.
  • Re:Overflow by nicknack (Score:2) Sunday February 25 2007, @07:19PM
  • Moderation? (Score:5, Insightful)

    by Anonymous Coward on Sunday February 25 2007, @07:44PM (#18147502)
    Why do you guys give +5 to someone who doesn't know for sure how the date line works, and who merely looked up which SI prefix was small enough to cause a 64-bit overflow? Most likely the bug has to do with overflow in position, not time. Even assuming this has to do with time overflow, modern GPS electronics can only measure signals to within 10 nanosecond. Using femtoseconds (10,000,000x smaller) is complete BS to make his argument work.
    [ Parent ]
    • Re:Moderation? (Score:4, Funny)

      by tigga (559880) on Sunday February 25 2007, @10:37PM (#18148746)
      Why do you guys give +5 to someone who doesn't know for sure how the date line works .. ?


      Because it's a Slashdot!

      Dumb vote for stupid ;)

      [ Parent ]
    • Re:Moderation? by femto (Score:1) Sunday February 25 2007, @11:07PM
    • 1 reply beneath your current threshold.
  • Re:No UHF backup? by devilspgd (Score:2) Sunday February 25 2007, @07:55PM
  • Cost Efficiency: EuroFighter vs. F-22 by reporter (Score:2) Sunday February 25 2007, @08:25PM
  • Re:Where Does The Article Mention the Underlying O by tftp (Score:2) Sunday February 25 2007, @08:28PM
  • Re:Overflow (Score:5, Informative)

    by Sinical (14215) on Sunday February 25 2007, @08:32PM (#18147886)
    Please stop. No one is using femtoseconds for uptime.

    Something more reasonable is that the nav system (presumably GPS) didn't like having the date change after aquisition. You'd think that'd be a fairly normal thing to have happen, but after the horrible crap I've seen happen with Rockwell Collins' receivers (they SUCK), it wouldn't be too surprising.

    To expand on the Rockwell Collins (they SUCK) theme, we eventually got them to admit to us how to retrieve their diagnostic info, including a register that counting up floating point exceptions (yay, divide by zero!). It had well and truly saturated. On a test flight of an, in part, GPS-guided missile, it once croaked right at launch. Since we never understood that we were moving, we never turned on the autopilot. However, rocket motors don't have much in the way of an off switch, so away we went without autopilot. Boink!

    So there are plenty of ways for nav systems to suck (especially if they are made by Rockwell Collins (they SUCK)) without needing something completely stupid like measuring data in femtoseconds.

    Hold up, I got a few more of these:

    Rockwell Collins (they SUCK)
    Rockwell Collins (they SUCK)
    Rockwell Collins (they SUCK)

    That is all.
    [ Parent ]
  • by EMB Numbers (934125) on Sunday February 25 2007, @08:40PM (#18147954)
    I have worked on Commercial and DoD avionics, and this type of thing is inexcusable.

    Commercial avionics software of the sort described is governed by a standard called DO-178B level A or level B. The process is so rigorous that the slogan is "no-one has ever died from software failure in a commercial airliner, yet." DO-178B level A is expensive. It is virtually impossible that a software error of the nature described could get into a certified aircraft.

    Having said that, the military is not obliged to follow commercial standards, but there is a trend toward using DO 178-B in military systems in part because the Europeans are starting to require commercial JAA/FAA certification for all aircraft that enter their air space. But even in the more lax military world, every line of code is typically formally reviewed and there are independent testers. The type of error described should have shown up in simulators before the first flight of the aircraft. Test flights should have stimulated the error long before a squadron ever attempted a transpacific flight.

    Even worse still, avionics systems are supposed to be isolated from each other. Navigation radios typically share nothing but power with GPS or with engine instruments etc. Great effort prevents one system from disturbing the power of another too. Aircraft typically have two or more separate primary navigation systems plus inertial guidance and old fashion compass + baring/vector navigation. Military aircraft need to survive both normal equipment failures and battle damage. Military radios (including navigation) need to be isolated from other systems for security reasons too. Those NSA guarded encryption systems can not be contaminated by software that has lower security classification (like navigation)without somebody going to federal prison for a long time.

    The bottom line is that something very very wrong, negligent, and illegal needed to happen for the described error mode to manifest. That makes me doubt the story.

    [ Parent ]
  • Re:I've been wondering... by SanityInAnarchy (Score:2) Sunday February 25 2007, @08:52PM
    • 1 reply beneath your current threshold.
  • Re:Where Does The Article Mention the Underlying O by PigIronBob (Score:1) Sunday February 25 2007, @09:02PM
  • Re:Do these fighters... by Farmer Tim (Score:2) Monday February 26 2007, @12:59AM
  • Re:Overflow by dosquatch (Score:2) Tuesday February 27 2007, @09:03AM
  • 17 replies beneath your current threshold.