Raytheon Mulls KillerBee for FCS

Raytheon Mulls KillerBee for FCS

The Army will probably hear from Raytheon quite soon about adding an Unmanned Aerial System known as KillerBee to whatever replaces the Future Combat System.

KillerBee carries a modular payload, can fly for 15 hours, can be ground-launched and recovered with a net. In addition, Raytheon recently used the KillerBee to feed targeting information to an anti-tank weapon, making it possible for a crew to fire without exposing themselves to enemy fire. The company is offering the UAS to the Navy and Marines for the Small Tactical Unmanned Aircraft System.

During a presentation at the Paris Air Show about the system today, I was struck by how appropriate its capabilities seemed to some of the Army’s FCS missions so I asked the briefer, Mark Bigham, director of business development, if he thought the fit made sense.


“Great question!” he said (which is usually a sign the reporter has either missed the point or tossed a real softball). Then he surprised everyone in the room: “I think FCS would be a great user of this capability.” Then he said the company would probably pursue it.

One of the most compelling elements of the system is the Common Control System that Raytheon has developed. Peterson said its use has reduced collisions by 50 percent. The system uses collision-avoidance algorithms and automatically steers a UAS away from an obstacle.

Raytheon clearly thinks the KillerBee is a hot product, with Peterson noting that the UAS market is projected to grow from $4.4 billion to $8.7 billion over the next 10 years. “That’s a big market and a good place to be,” he said.

KillerBee Specifications
Payload Capacity: 5,800 in3
Payload Weight: 30+ lb
Flight Range: 100+ mi
Endurance: 15 hr
Wing Span: 10 ft
Flight Controller: STANAG 4586 compliant
EO/IR Payload: Daytime video, nighttime IR

Join the Conversation

There originally were 4 UAS classes associated with FCS. Only the small ducted fan Class I and larger Schweizer-based Class IV helicopter remain. Putting a laser on Class I has effectively filled the Class II void and in my opinion, the Shadow already fills the Class III requirement.

The KillerBee has appealing endurance and payload range. But is the Common Control System compatible with either the FCS data link or tactical common data links and Army’s standard GCS and remote video terminal?

That sounds like about 8+ x 8+ x 8+ inches of cubic area to squeeze payloads that must not weigh much if the thing has a 10′ wingspan and only weighs 30 lbs with 15 hours worth of gas.

Bottom line is it is around Class I UAS size but lacks its payload capabilities yet has far greater endurance and range. A major downside is it requires both a launcher and recovery system while Class I requires neither. The long range is somewhat irrelevant with so little quality payload. Class I is a company and below system and does not need 58 miles range like I read it was tested at.

The infantry is probably already complaining about the new larger size of the Class I T-Hawk ducted fan. The KillerBee has a 10′ foot wingspan so isn’t likely to fit in any backpack.;) It requires a launcher and a net, so this sure isn’t likely to replace Class I UAS (even if it could hover and stare and had a gimbaled payload) and it has nowhere near the capabilities of the 3000+ lb Class IV except endurance.

Considering how the Class I UAV is currently incredibly loud I think this is a worthy alternative to take a look out.

First we need to get together a new manned vehicle plan however.

I researched this thing some more and need to clarify my last comments.

First, it has more payload area and weight than I originally thought. The payload (if I could read) weight, not aircraft weight, is 30+ lbs. The overall aircraft may weigh as much as 100 lbs or more with fuel. It has more dimensional area for payload because my math-in-my-head attempt sucked. ;)

As Colin states, this UAS is in the running for the Navy/Marine STUAS Tier II RFP along with the Scan Eagle, an AAI product, and a General Dynamic team? It must be launchable and recoverable from a ship, so hence the launcher and net for recovery. They want it to be transportable by V-22 to get to shore but the launcher/recovery net also appear to be towed by HMMWVs.

Bottom line is this thing is probably way too big to replace the Class I UAV or Raven as a company sized UAS supporting light or mech infantry…but I agree that the current T-Hawk is far too loud. But apprarently they are working on that. As far as I have read, none of the FCS UAS are being killed off…just the manned ground vehicles.

Guess it can loiter at around 55 knots for 15 hours which is pretty superb. But will your typical infantry company stays in one place for that long because I doubt the ground control station works on the move. Although one big plus is the projected ability to control multiple Killer Bees from one GCS that perhaps you could put at Marine Expeditionary Battalion CP level.

*required

NOTE: Comments are limited to 2500 characters and spaces.

By commenting on this topic you agree to the terms and conditions of our User Agreement