Or someone could have switched the other GCS off, I expect human factors will play a big part sounds like the Fire Scout was having fun by itself, good job there were not any 2001' hills in the way.
@Dave: Hey! I take offense to that! (I'm a Navy engineer in Unmanned Systems, but the watery kind) If anything it's a Northrop Grumman product, I'd blame them first. I've worked with both navy built drones and contractor products, and it's a pain to use contractor products. No access to source, no ability to debug, no understanding of the quarks of the system. I bet all the time it was 'lost' was the time it took the Navy operators to get a Northrop Grumman engineer on the phone to tell them what to do since the craft wasn't responding to it's control GUI program.
This line "The Navy is calling the problem a “software issue” that foiled the drone’s operators. " makes me think it was 'Well, we hit the RTH (return to home) button and it didn't do it. now what? It's not our system'
"As Cmdr. Danny Hernandez, a Navy spokesman, put it: “When they lose contact with the Fire Scout, there’s a program that’s supposed to have it immediately return to the airfield to land safely. That did not happen as planned.”
It could have been over an unpopulated area & flown into a populated area if the RTL code failed. Our main concern with RTL code has always been a motor start on the bench.
Comments
Like, hacked!?
This line "The Navy is calling the problem a “software issue” that foiled the drone’s operators. " makes me think it was 'Well, we hit the RTH (return to home) button and it didn't do it. now what? It's not our system'
"As Cmdr. Danny Hernandez, a Navy spokesman, put it: “When they lose contact with the Fire Scout, there’s a program that’s supposed to have it immediately return to the airfield to land safely. That did not happen as planned.”
Atleast it was able to fly, and didn't just crash.
-
1
-
2
of 2 Next