06.01.2013 Views

Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...

Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...

Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

UAS ROADMAP <strong>2005</strong><br />

3. The integration, interoperability, and information assurance required to support mixed<br />

manned/unmanned force operations.<br />

4. Secure, robust communications capability, advanced cognitive decision aids, and mission planning.<br />

5. Adaptive autonomous operations and coordinated multi-vehicle flight.<br />

Strike, persistent strike and armed reconnaissance missions may be against heavily or a lightly defended<br />

targets. The level <strong>of</strong> threat determines which UA attribute is most influential in the design. If the<br />

requirement is to engage and defeat lightly defended targets, then a conventionally designed UA would<br />

stress payload and aero performance to achieve the most efficient “kill” capability. The ability to provide<br />

a persistent threat against adversaries will stress endurance as a design feature in the lower threat<br />

environments. If prosecution <strong>of</strong> highly defended targets is required, then a design stressing survivability<br />

is paramount, and <strong>of</strong>ten will trade away payload and aerodynamic performance to achieve greater<br />

certainty <strong>of</strong> success against highly defended targets. This trade is required to ensure “anti-access” targets<br />

(targets that deny use <strong>of</strong> conventional joint force assets) are eliminated early in a campaign so the Joint<br />

Force Commander can use the full range <strong>of</strong> forces at his disposal and achieve desired effects as swiftly as<br />

possible. (Strategic Planning Guidance: “Swiftly defeat adversaries in overlapping military campaigns<br />

while preserving for the President the option to call for a more decisive and enduring result in one <strong>of</strong> the<br />

two.”)<br />

UA would be used against heavily defended targets for two reasons. First, a UA can theoretically achieve<br />

levels <strong>of</strong> survivability that manned aircraft cannot. Signature control without the need for human<br />

caretaking becomes less difficult, and maneuverability could be increased beyond human tolerances<br />

should that be required to enhance survivability. The design driver for this case is survivability, however<br />

it is achieved. If such survivability measures fail, the use <strong>of</strong> a UA removes the risk <strong>of</strong> losing a human life.<br />

Previously, DoD has tended toward multi-mission configurations where one platform would accomplish<br />

both/many missions (e.g., the multi-mission platform). It should be noted that a UA designed to be cost<br />

effective for both lightly and heavily defended targets would be <strong>of</strong> sufficient size that it would no longer<br />

be a low cost solution. A trade analysis would be required to determine if one multi-mission UA should<br />

be procured, or if a range <strong>of</strong> separate UA for each mission is a better value.<br />

If a UA are to reduce the numbers <strong>of</strong> manned strike assets required, it will have to <strong>of</strong>fer a weapons<br />

compatibility mix similar to that <strong>of</strong> manned strike assets in order to keep overall armament development<br />

and support costs low. Additionally, UA must be examined for every opportunity to further reduce<br />

operations and support costs. Operational data is available for many UA as a result <strong>of</strong> OEF and OIF.<br />

Analysis is required to determine where savings can be achieved, or how they could be achieved if proper<br />

Doctrine, Organization, Training, Materiel, Leadership, Personnel and Facilities (DOTMLPF) is applied.<br />

J-UCAS should conduct such an analysis as part <strong>of</strong> its Operational Assessment to ensure the program<br />

implements these lessons learned during its system development and demonstration phase.<br />

SEAD may be analyzed as two different types <strong>of</strong> missions. The first is pre-emptive SEAD, in which a<br />

pathway is cleared prior to the ingress <strong>of</strong> strike aircraft. The other type is reactive SEAD, in which the<br />

SEAD asset must react rapidly to “pop-up” enemy air defense threats during the execution <strong>of</strong> a strike.<br />

Since closing with that threat will be required, the survivability <strong>of</strong> the vehicle must be assured through a<br />

combination <strong>of</strong> speed, stealth technology, and/or high maneuverability.<br />

Execution <strong>of</strong> both the pre-emptive and the reactive SEAD mission imply several critical design criteria<br />

for the UA platform and mission control system. These attributes would be similar to those <strong>of</strong> a UA in a<br />

strike roll against heavily defended targets. UA accomplishing pre-emptive SEAD missions would also<br />

be expected to possess the following system characteristics:<br />

� Extremely high mission reliability, as follow-on force assets (many <strong>of</strong> which will be manned) will<br />

depend upon the protection <strong>of</strong> a SEAD UA asset.<br />

APPENDIX A – MISSIONS<br />

Page A-5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!