Well... Not sure what to say, other than to say that that sucks. Because that seriously does suck. This could be the problem with UAVs under testing. We haven't got anyone on board to de-discombooberate the system if something goes wrong.

This line "which caused the aircrafts automatic fail-safe flight termination mode to activate is cited by Lockheed Martin as the cause of the crash." It almost sounds like the plane has a fail safe that either brings it in for a controlled crash or self destruct etc. Times like this where I wish Intelgurl or Bios would chime in I'll have to try to U2U them etc. Come to think of it Intelgurl left in Dec and that may have been around the crash time? Is she connected to Lockheed in anyway? ahh too many questions have to see if I can contact Bios.

Update: Emailed Bios and waiting for reply.


[edit on 22/08/06 by Canada_EH]

wierd...

What was the point? Why type lines and lines of code, to instruct the aircraft to crash??? If you loose contact/control of the UAV...I'm pretty sure it will manage to crash all on its own...it doesn't need instructions for that.

But either way you look at it, thats bad news for lockheed. Who built this craft with money outta their own pocket, because they wanted to show Washington that they are on par with Boeing & Northrop as far as UAV's (mainly BWB's) are concerned.

Yes it does, in the event of a failure the UAV needs to be able to crash somewhere it won't cause damage on the ground. It's a safety measure.

What sort of senors on board does a UAV have to make a desion like that and how would it go about it. I remeber engine failure training and the practise I still do and man it sounds easy but sure as "heck" isn't. Not saying it isn't possible just very ummm professional to train a plane to control crash, how would you let the plane deside?

Having also gone through engine failure training, I concur completely that an engine failure is very much different than any other failures. Even when idling the engine provides a lot of power and a lot of pilots take the idling for granted- until they notice the difference when it ain't there. Now, I did my training first in a Cessna 172 and then in a double-prop of which I cannot remember the name. These two have pretty darn good glide rates, and the engine pales when put next to a jet. To have the engines on a fighter aircraft (Less related to aircraft and more related to rockets with really big fins on the sides ) conk out on you is probably a lot worse; Those aircraft rely a whole lot on the engines to stay up, astronomically more than any smaller aircraft. Now, because the BWB of the Polecat is very lifting, I don't think it's quite that problematic, but since one way or another the failure leads to the aircraft meeting the ground in some way, it still does present us with a bit of a poser. Just out of curiosity (I haven't read the whole article, haven't had a whole lot of time, so it may be a really stupid question. Sorry if it is.), has there been any specific cause as to what precisely forced the craft to crash (other than it was programmed to do so)?

The truly sucky thing about this is that it may push Lockheed and the others to put their projects back in the "dark". Lockheed took a risk by making polecat public. Now with the loss of that aircraft it's an embarrassment. At the very least it brings the technology under public scrutiny which is a real bad thing if you're trying to sell it.

Originally posted by looking4truth
The truly sucky thing about this is that it may push Lockheed and the others to put their projects back in the "dark". Lockheed took a risk by making polecat public. Now with the loss of that aircraft it's an embarrassment. At the very least it brings the technology under public scrutiny which is a real bad thing if you're trying to sell it.

well, yes and no.

I see what your saying, But Lockheed designed this craft from the get go, to not be some stealthy spy plane over Iran, But a tech demonstrator, basically showing the AF that they can make a stealthy BWB, and make it cost efficient.

Originally posted by Darkpr0
Just out of curiosity (I haven't read the whole article, haven't had a whole lot of time, so it may be a really stupid question. Sorry if it is.), has there been any specific cause as to what precisely forced the craft to crash (other than it was programmed to do so)?

Awww come on Darkpro I provided it for you for that reason lol Anyways no problem I'll be glad to sumerizes. It sounds like the problem actually was on the ground control station and their was a un reversable failure in the control system and due to that the Polecat has somesort of failsafe programe that took over and from what I understand terminated its flight. Muricelago brought up the idea of a code for the plane to follow in this situation.

I agree with you exerinces in engine failure training and also the fact that the polecat is a BWB (blended wing body) should create better the normal glide charactertics. I guess the problem as I brough up before is the plane handling itself when all the thrust is gone therefore changing the handling of the UAV. Hope that helps some Darkpro

Well I got the email and Natalie was able to answer it herself as it seems she was on some sort of break from the testing range. Its good with more answers then I could of hoped. Enjoy guys and gals

The Polecat did not represent any great technological strides other than the composites used in the manufacture of the Polecats airframe - it in no way represented a a step beyond the JUCAS/NUCAS efforts of Northrop & Boeing, particularly in software control systems and redundant backups.

I'm really not surprised about the loss as Lockheed actually has a record with such failings (Darkstar comes to mind - although they finally got a larger model in clandestine service during the opening of the Iraq war).

In my opinion Lockheed felt market & shareholder pressure to position themselves as a UAV systems provider, they rushed things and quite frankly reaped what they sowed - (you may recall when the Polecat was first publicized Lockheed's Dir of UAS's, Frank Mauro expounded on their ability to put the thing up in 18 months).
Let's face it, 18 months is waaay too quick to have a reliable system flying when the software required is so system and airframe geometry specific - you just can't plug a rehashed old Darkstar module in, write a patch and expect the thing to work flawlessly.

Let me get political for a moment;
Now that Rumsfeld is out of the picture I think we will see Northrop and Boeing having a greater influence and a greater, well deserved opportunity to grab some Pentagon aerospace contracts. My lord, Lockheed can't even supress contrails, Northrop's been doing it for over 15 years (ie: B-2 bomber)
(Lockheed's Polecat UCAV Demonstrator Crashes)
Aviation Week & Space Technology - Subscription service version
03/19/2007, page 44
(this article also discusses Lockheed's inability to supress contrails and their thwarted desire to use the polecat to experiment with contrail supression technology)

Natalie~

And there it is hopefully this enough for you guys but I know I have some more to chew on in order to fully wrap my thoughts around the failure and systems in place for it. Many thanks to Intelgurl again and we look forward to her return in the later months and wish her the best in her current endevors.

[edit on 22/08/06 by Canada_EH]

Weird! Does anyone else find it odd that it was the Flight control system's Fail-Safe that caused the crash?

Not to rag on Lockheed, but this sound erriely simular to the computer malfunction that caused the loss of a Darkstar UAV a few years back now. The drone took off from Edwards AFB and amalfunction in the failsafe caused the Darkstar to pich up sharply and yaw on take off.

Tim

Ok, I take it back! The Report sais there was a flaw in airframe design that caused Darkstar to crash. The Popular Science artical I have at home must have gotten it wrong. Thanks for the correction.

Tim

Originally posted by Murcielago
Why type lines and lines of code, to instruct the aircraft to crash???

The idea strikes me that if you have a state-of-the art long-range surveillance craft such as the Polecat, and that for whatever reason crashes in enemy territory, you'd want to make sure that all the onboard electronic hardware (sensor arrays, microprocessors etc) were disabled beyond use to the enemy.

Wouldn't there be some kind of redundant command written into the software that would fry the circuitboards and components to render them useless?

Originally posted by citizen smith

Originally posted by Murcielago
Why type lines and lines of code, to instruct the aircraft to crash???

The idea strikes me that if you have a state-of-the art long-range surveillance craft such as the Polecat, and that for whatever reason crashes in enemy territory, you'd want to make sure that all the onboard electronic hardware (sensor arrays, microprocessors etc) were disabled beyond use to the enemy.

I would agree except for the fact that the polecat was never designed to fly in enemy airspace as it was only a test vehicle that only made probably around 5 flights before crashing. I agree that it would have some sort of code writing to bring down the aircraft but you would think they would want in in one piece still.

[edit on 22/08/06 by Canada_EH]