Attachment 03 MQM-170 Performance Specification.pdf

MIS-PRF-56674

CAGE Code 18876

25 April 2013 PERFORMANCE SPECIFICA nON

SYSTEM SPECIFICATION

FOR THE

Aerial Remotely Piloted Vehicle Target (RPVT) System

Prepared for:

U.S. Army Aviation and Missile Life Cycle Management Command

R~dstone Arsenal, Alabama 35898-5000

Prepared by:

Targets Management Office

Building 3211, Hercules Road

Redstone Arsenal, Alabama, 35898·7458

SUBMITTED BY:

APPROVED BY:

V~

Brian K: Whitaker Project Director, Air Defense Targets

PEO STRI, PM ITTS

Targets Management Office

OJLv6- Alvin V. Brown Director, PEO STRI, PM ITTS

Targets Management Office

DATE:

.2SAp",' ,2$/3

I HAVE READ THE CONTENTS OF MIS-PRF-56674 RELATIVE TO ACQUISITION

REFORM AND CERTIFY THAT THE SPECIFICATION IS A PERFORMANCE

BASED DOCUMENT.

James B. Lackey AMCOM and PEO A vi Standards Executive

APPROVED FOR USE AS

A FUNCTIONAL

BASELINE BY: ~StiL

Tony Stilf"O'

DATE: 4-'/)(" II)

r' Chief Engineer

PEO STRI, PM ITTS

Targets Management Office

FSC 1550

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Page ii

Page iii

REVISION HISTORY

CHANGE RECORD

This sheet is a record of each issue of this document.

When the revised document is issued, the previous issue is automatically superseded.

Version Date Configuration

Management Pages Changed

Reason for Change

Original

Change 1

Change 2

Change 3

06/15/2008

09/05/2008

09/23/2008

04/25/2013

Brian Whitaker

N/A

Pages 16, 17 and 23

Pages 1-29

N/A update of requirements update of requirements update of requirements and update IAW MIL-STD-961E, w/CHANGE 1, Department of Defense Standard Practice, Defense and Program – Unique Specifications Format and Content, 2 April 2008

PERFORMANCE SPECIFICATION, SYSTEM

SPECIFICATION FOR THE REMOTELY PILOTED

VEHICLE TARGET SYSTEM AND SERVICES

Document Number:

Page iv

Table of Contents

Paragraph/Section Title Page

1. SCOPE

1.1 Scope

1.2 Program Objectives

1.3 System Description

1.4 System Definition

1.5 Mission Objective

1.6 Operational Strategy

1.7 Supportability Strategy

1.8 Characteristics

2. APPLICABLE DOCUMENTS

3. REQUIREMENTS

3.1 System Components

3.2 Reliability, Availability, and Maintainability (RAM)

3.3 Air Vehicle (AV)

3.4 Ground Control Station (GCS)

3.5 Ground Support Equipment (GSE)

3.6 Mission Payload Equipment (MPE)

3.7 Identification and Markings

4. VERIFICATION

4.1 Methods of Verification

4.2 Class of Verification

4.3 Conformance Inspection

4.4 Verification Matrix

5. PACKAGING

6. NOTES

6.1 Acronyms

6.2 Definitions

1. SCOPE

1.1 Scope

This specification establishes the performance requirements for the acquisition of an aerial Remotely Piloted Vehicle Target (RPVT) and related equipment. The Targets Management Office (TMO) has a requirement to provide a RPVT system to the United States Army Air and Missile Defense (AMD) community and other Department of Defense (DOD) services to support training and Research, Development, Test and Evaluation (RDT&E) missions at DOD ranges and other military/non-military installations worldwide. It is expected that the RPVT system requirements are achievable with Commercial Off-The-Shelf (COTS), modified COTS and Non-developmental Items (NDI). This specification will include RPVT Air Vehicles (AV), to include specified payloads, and Ground Support Equipment (GSE).

1.2 Program Objectives

The primary program objective is to provide a RPVT system to the United States Army that can meet current training requirements. In addition to the U.S. Army, the TMO will provide the RPVT system to other customers including the Navy, Air Force, USMC and Foreign Military Sales (FMS). The RPVT system GSE will be useable over an anticipated five year life cycle with only minor repair and upkeep.

1.3 System Description

The RPVT is an aerial target that is used for weapon systems training in countering airborne threats. The U.S. Army’s current, interim and future forces will use the RPVT to train Soldiers and where appropriate, test new weapon systems and procedures to counter asymmetric threats (see 6.2) including unmanned aircraft systems (UAS). The RPVT will permit livefire (see 6.2) engagements by AMD units and will provide an expendable threat representation of a UAS for emerging weapon system development and testing. The RPVT system will be transported to and operated in varying environments worldwide, and shall be operated during periods of daylight and darkness and in climatic conditions ranging from Hot-Dry to Cold-Wet.

1.4 System Definition

The RPVT system is defined as all equipment necessary to meet the requirements section of this RPVT system performance specification. An RPVT system consists of these basic elements:

RPVT Air Vehicle (AV), Ground Control Stations (GCS), Ground Support Equipment, and Mission Payload Equipment (MPE). The exact configuration, quantity, and functional capability of these basic elements will depend on deployment scenarios and on design concepts used to meet the mission objectives.

1.5 Mission Objective

The purpose of the RPVT System is to provide aerial target threats for livefire training and testing. The MPE supports various test and training requirements. The RPVT AV must be interoperable with a variety of MPE. It is anticipated that the MPE requirement will be met through a versatile set of physical, electrical, and data interfaces. The RPVT system is intended to be a Government Owned - Contractor Operated (GOCO) training system throughout its lifecycle. The RPVT system is not intended to be integrated into Table of Distribution and Allowances (TDA) or Table of Organization and Equipment (TO&E) organizations.

1.6 Operational Strategy

The RPVT system will be operated, maintained and managed by a single entity. The hardware manufactured for RPVT system requirement will be turned over as Government Furnished Equipment (GFE) back to the prime manufacturer of the RPVT system to provide support services. The RPVT system will be operated in the same environments as those in which the U.S.

Department of Defense Soldiers train, and where weapon system testing is conducted.

1.7 Supportability Strategy

The RPVT system will be of a modular nature that will facilitate reconfigurations to install or remove subsystem components and MPE. Field installation and removal will be limited by the resources available at support locations and the operating environment on the ranges. Industry best practices will be considered.

1.8 Characteristics

The RPVT system performance characteristics delineated in Section 3 represent the performance characteristics of the system.

2. APPLICABLE DOCUMENTS

2.1 General

The documents listed in this section are specified in sections 3, 4, or 5 of this specification. This section does not include documents cited in other sections of this specification or recommended for additional information or as examples. While every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet all specified requirements of documents cited in sections 3, 4, or 5 of this specification, whether or not they are listed here.

2.2 Government Documents.

2.2.1 Specifications, standards, and handbooks. The following specifications, standards, and handbooks form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.”

Title MIL-STD-1366 - Interface Standard For Transportability Criteria

2.2.2 Other government documents, drawings, and publications.

The following other government documents, drawings, and publications form a part of this document to the extent specified herein.

Title Federal Aviation Regulation (FAR) 23.1385, Part 23 Airworthiness Standards: Normal, Utility, Acrobatic, and Commuter Category Airplanes, Position light system installation Army Regulation – AR 70-38 Research, Development, Test and Evaluation of Materiel for Extreme Climatic Conditions

Copies of the Federal Aviation Regulation (FAR) 23.1385, Part 23 Airworthiness Standard, are available from the following website:

Federal Aviation Administration (http://rgl.faa.gov/) / Click on Airworthiness Directives or direct page link is:

http://rgl.faa.gov/Regulatory_and_Guidance_Library/rgFAR.nsf/0/1f344d1f7df924c7852566870 072238a!OpenDocument

Copies of the Army Regulation – AR 70-38 Research, Development, Test and Evaluation of Materiel for Extreme Climatic Conditions are available from the following website:

http://www.army.mil/usapa/epubs/70_Series_Collection_1.html

2.2.3 Non-Government standards and other publications.

None

2.3 Order of precedence.

In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3. REQUIREMENTS

3.1 System Components

The RPVT System shall consist of the following components: Air Vehicle (AV), Ground Control Stations (GCS), Ground Support Equipment (GSE), Mission Payload Equipment (MPE) and Scoring Portable Ground Control System (PGCS). (See 6.2).

3.2 Reliability, Availability, and Maintainability (RAM)

Out of 100 target operations (see 6.2), the RPVT system shall provide not less than 95% satisfactory flight IAW with the definition below.

NOTE: A satisfactory flight shall be defined as a flight that is successfully launched on schedule, meets all of the requirements for the scheduled task, and successfully follows the prescribed flight path/profile for the designated mission, and is either destroyed by livefire engagement or recovered at the end of the mission.

3.3 Air Vehicle (AV)

3.3.1 AV Physical Characteristics

The RPVT system AV shall be a fixed wing AV and shall conform to the following physical characteristics:

a) Length: Shall be from no less than 2.286 m (7.5 feet) to no more than 3.81 m (12.5 feet).

b) Wingspan: Shall be from no less than 3.2 m (10.5 feet) to no more than 5.944 m

(19.5 feet).

c) Payload Bay: The RPVT AV shall provide a payload bay for the MPE, with a volume that is adaptable to the payloads and payload combinations IAW Table 1. The payload bay shall provide a 15% excess volume capacity over the most stringent MPE combination IAW with Table 1 for potential growth.

3.3.1.1 Power Plant

The RPVT AV shall include an engine with performance to satisfy the AV performance characteristics of this specification.

3.3.2 AV Performance Characteristics

3.3.2.1 AV Range

The RPVT AV shall have a control range of 0 kilometers (Km) (0 statute miles [sm] ) to no less than 3 Km (1.864 sm), in manual control mode, 0 Km (0 sm) to no less than 25 Km (15.534 sm) using the Beyond Visual Range (BVR) control system, and 0 to range limited only by the fuel endurance of the air vehicle in the Over the Horizon (See 6.2) BVR control system.

3.3.2.2 AV Endurance/Flight Times

3.3.2.2.1 The RPVT AV required flight time shall be at least 1 hour (60 minutes), as calculated from the launch through landing.

3.3.2.2.2 The RPVT AV shall allow the field installation of auxiliary fuel to extend the AV flight time to 2 hours (120 minutes) from launch through landing.

3.3.2.2.3 Objective: The ability to install auxiliary fuel to extend the AV flight time to 6 hours (360 minutes) is desired.

NOTE: Flight endurance shall be conducted at the most economical cruise power setting for the air vehicle. Flight profile after launch and climb out shall be conducted at 1,524 m (5,000 ft).

pressure altitude.

3.3.2.2.4 The RPVT AV shall perform to the specified endurances IAW 3.3.2.2.1 and 3.3.2.2.2 using the following flight profile:

The RPVT AV engine shall operate at:

95 percent RPM for 50 percent of the flight time

100 percent RPM for 10 percent of the flight time

And at most economical cruise for the remaining 40 percent flight time.

3.3.2.3 AV Service Ceiling (Altitude)

The RPVT AV shall operate according to the requirements of this specification, at altitudes from 0 to 3,046 m (0 to 10,000 ft) above mean sea level (MSL), with a minimum climb rate of 30.48 m (100 ft) per minute at 3,046 m (10,000 ft) MSL.

3.3.2.4 AV Performance With Payload

The RPVT AV shall perform according to the requirements of this specification while carrying any one of the five MPE/fuel combinations IAW Table I.

Table I. AV Payload Combinations

AV/Mission Payload Equipment (MPE) Options Combinations

1 2 3 4 5 Multiple Integrated Laser Engagement System (MILES) Payload x

Beyond Visual Range (BVR) Payload x Over the Horizon BVR Payload x Infrared Signature Payload (ISP) x x x x x Laser Reflective Payload (LRP) x x Smoke Generator Payload (SGP) x x x Acoustic Scoring Payload (ASP) x x Radar Scoring Payload (RSP) x x Lighting Kit Payload (LKP) x x x x x 60 minutes additional fuel (for a total of 120 minutes endurance) x x x x x

3.3.2.5 AV Visibility

The RPVT AV shall be visible with unaided 20/20 vision at a minimum range of 3 Km (1.864

sm) during mid-day with a minimum surface visibility of 4.828 Km (3 sm) and a ceiling not less than 304.8 m (1,000 ft) above ground level.

3.3.2.6 AV Color

The RPVT AV shall be painted with a color scheme that allows the operator to maintain visual contact with the AV and facilitate situational awareness of the AV attitude. Two individual colors shall be used to create contrast.

3.3.2.7 AV Construction

The RPVT AV shall be constructed such that it is operable for a minimum of twenty flights (including launch and recovery), when not rendered irreparable by live fire engagements.

3.3.2.8 AV Deployability

3.3.2.8.1 The RPVT AV, including the support system, (See 3.1) shall be deployable (able to be set up and ready for operation) in no more than 30 minutes by no more than 3 personnel, after arrival at the launch point.

3.3.2.8.2 The RPVT system shall support no less than four (4) successive RPVT AV launches at 5 minute intervals (30/5 minute launch requirement) using a standard three person crew and using pre-assembled AVs.

3.3.2.9 AV Speed

The RPVT AV shall launch and sustain level stable flight (See 6.2) at all flight speeds between

80.467 Kilometers per hour (kph) (50 statute miles per hour [mph]) and 193.12 kph (120 mph) Indicated Air Speed (IAS) at an altitude of no less than 1,524 m (5,000 ft) MSL, with the required mission payloads IAW Table 1 and fuel to meet specified endurances IAW 3.3.2.2.1 on standard day conditions.

NOTE: A standard day model of the atmosphere shall be defined as sea level altitude, temperature of 15 Celsius (C) (59 Fahrenheit [F]), and barometric pressure of 29.92 inches of mercury (HG).

3.3.2.10 AV Environmental Conditions

The RPVT AV and system components, (See 3.1) shall operate according to the requirements of this specification during and after exposure to the following environmental conditions, and shall operate in climatic conditions of Hot-Dry to Cold-Wet as defined IAW Army Regulation 70-38.

3.3.2.10.1 Temperature

The RPVT AV and system components, (See 3.1) shall meet its specified performance in the following temperature ranges:

Operating: -17.778 C (0 F) to + 51.667 C (125 F)

Non-operating/storage: -17.778 C (0 F) to 60 C (140 F)

Non-operating/transportation: -17.778 C (0 F) to 60 C (140 F)

3.3.2.10.2 Precipitation

The RPVT AV and system components, (See 3.1) shall fly in conditions of at least .0762 centimeters (cm) (.03") per minute of falling rain or snow, for at least 5 minutes; and at least .038 cm (.015") per minute of falling rain or snow for the remainder of the flight, until such time as the target can be landed IAW Recovery/Landing as specified below (3.3.2.14).

3.3.2.10.3 Day/Night Operations

The RPVT AV shall perform IAW the requirements of this specification at any time during any 24-hour period of day or night, over land or bodies of water.

3.3.2.10.3.1 The RPVT AV shall be equipped with the internal wiring and power connections to facilitate field installation of the external lighting fixtures IAW the external lighting fixtures defined in the Lighting Kit Payload (LKP) requirements of this specification.

3.3.2.10.4 Wind Speed

The RPVT AV shall launch, fly and recover in winds of up to 30 knots (35 mph).

NOTE: Separate cross wind limitations shall not be considered a factor since the AV launcher shall be aligned with the prevailing winds.

3.3.2.11 Survivability

The RPVT AV shall operate according to the requirements of this specification, after sustaining impacts from ten or more small caliber projectiles of no less than 50 caliber each, in non-vital areas (vital areas shall be defined as the engine, fuel tanks, fuel lines, electronics, servo actuators, servo linkages, control linkages, and control surfaces).

NOTE: The purpose of the survivability requirement is to allow for the recovery of the damaged AV for repair.

3.3.2.12 Maintainability

The RPVT AV shall provide a means for a field operator to repair/replace/maintain the RPVT components under field conditions for at least 70% of failures and damage anticipated, including but not limited to the following: propeller breakage, spark plug fouling, ignition system damage, skin damage to fuselage and control surfaces, minor damage to structural components, engine replacement, MPE replacement, antenna replacement, wiring repair, control servo replacement, wing replacement, control surface replacement, and fuel system repair and replacement.

NOTE: Field conditions shall be defined as test and training ranges typically used by DOD and allied services worldwide.

3.3.2.13 Simultaneous Flights

The RPVT AV shall provide a means for the GSE to operate, at a minimum, two RPVT AVs in flight simultaneously - one AV utilizing manual GCS and the other AV utilizing a BVR GCS.

3.3.2.14 Recovery/Landing

The RPVT AV shall be recoverable on unimproved surfaces (See Note below) designated for that purpose on military training and test livefire ranges.

NOTE: Surfaces will range from level sod fields, through rutted, hard-packed dirt roads; to lava rock covered sloping terrain, depending on the individual range location and conditions.

3.3.2.14.1 The RPVT AV shall be serviceable and ready for return to flight within 15 minutes of a landing at least 90 times out of 100 flight operations, with the following exceptions: (1) AVs impacted by live fire engagements; (2) AVs recovered using the Flight Termination System (FTS) described below; or (3) AVs landed more than 1.609 Km (1 sm) from the RPVT launch site.

3.3.2.15 AV Manual Control

The RPVT AV shall provide a manual control onboard receiver that receives instructions from the manual GCS to control the AV and MPE.

3.3.2.16 Flight Termination System

The RPVT AV and control systems shall provide a Flight Termination System (FTS) IAW the GCS/Navigation Control System section of this performance specification.

3.4 Ground Control Station (GCS)

The RPVT AV shall be controllable by three methods; a manual control system, BVR system allowing for longer range operations, and an Over The Horizon GCS.

3.4.1 Manual Navigation GCS

The RPVT manual GCS shall include the components such as a hand held control transmitter, power supplies/amplifiers, batteries, antennas, binoculars, and storage/transport cases to operate and control the RPVT AV during manual flight operations.

3.4.1.1 The RPVT manual GCS with its AV components (See 3.3.2.15) shall provide a minimum of two auxiliary channels: one discrete and one proportional, with resolution greater than or equal to the command channels, in addition to those for AV control.

3.4.1.2 The RPVT manual GCS shall allow the operator to control the RPVT AV from the ground, with a visual line of sight (LOS) to a minimum range of 3 Km (1.864 sm).

NOTE: The use of visual aids such as binoculars mounted on a tripod, chair or other device for improving visual line of sight shall be acceptable.

3.4.1.3 The RPVT manual GCS shall be programmable to permit change of operating frequency in the field for ground transmitter and AV receiver.

3.4.1.4 The RPVT manual GCS shall be deployable within 30 minutes/5 minute recycle launch requirements.

3.4.1.5 The RPVT manual GCS shall include an FTS that reduces engine power to idle, and places the AV into either a spiral dive (descending turn) or neutral flight (flight surfaces set to neutral position) as selected by the operator prior to launch.

3.4.1.5.1 The RPVT FTS shall automatically terminate the flight within 10 seconds after losing the radio link with the GCS, and within 1 second upon command from the GCS.

3.4.2 BVR Navigation GCS

The RPVT BVR navigation GCS system shall consist of a ground station, system support software installed in both the ground station and AV control components, AV on-board components, GCS/AV data link, AV position reporting system, associated cabling, antennas and hardware.

3.4.2.1 The RPVT BVR GCS shall control the RPVT AV by using programmable way-point navigation to control the airspeed, altitude, and direction of the AV.

3.4.2.1.1 The RPVT BVR GCS shall provide secondary control of the RPVT AV using a manual control interface for launch and recovery of the AV.

NOTE: An automatic auto-launch and auto-land capability shall be acceptable.

3.4.2.2 The RPVT BVR GCS shall provide, at a minimum, AV position, target altitude, speed, pitch, roll and throttle RPM as a display on the BVR GCS.

3.4.2.2.1 The RPVT BVR GCS shall provide AV location and status in near real time, defined as not more than a 1-second delay for communication between the AV and the BVR GCS.

3.4.2.2.2 The RPVT BVR GCS shall provide a mission flight profile that shall consist of a series of segments from waypoint to waypoint (See 6.2).

3.4.2.2.3 The RPVT shall provide data link connectivity between the AV and GCS continually during a BVR controlled mission.

3.4.2.2.3.1 If the datalink is lost for a period of less than 10 seconds, the RPVT AV shall remain on its last programmed waypoint.

3.4.2.2.3.2 In the event of the loss of the datalink for more than 10 seconds, the RPVT AV shall automatically follow the lost link procedures programmed into the control system prior to launch.

3.4.2.2.3.2.1 The RPVT BVR GCS shall provide lost link procedures which are operator programmable into the control system prior to launch. RPVT BVR GCS lost link procedures shall include operator options of 1) immediate flight termination as described under Manual Navigation GCS (See 3.4.1.4) with optional engine shut off; 2) flight to a programmed waypoint (recovery waypoint) and execution of a programmed activity including a) loitering for a specified time, and b) flight termination including engine shut off.

3.4.2.2.3.2.2 If the data link is reestablished during the lost link procedure prior to flight termination, the RPVT BVR FTS shall resume the original mission plan from the point the data link is re-established. With link reestablished, the RPVT BVR GCS shall provide the operator the option to divert the air vehicle from resuming the original flight path.

3.4.2.2.3.2.3 The RPVT BVR GCS system shall display a confirmation of the recovery waypoint data that are stored on the BVR GCS prior to AV launch.

3.4.2.2.3.2.3.1 The BVR GCS shall display a warning message or shall limit the selection of a recovery waypoint that is outside the AV system range parameters.

3.4.2.2.3.2.4 The BVR GCS FTS shall provide a manual override at the GCS to allow the operator to command flight termination as described under Manual Navigation GCS (see 3.4.1.4) with optional engine shut off.

3.4.2.3 The BVR GCS shall provide pre-mission planning, mission monitoring and real time mission flight profile redirects. The RPVT BVR GCS shall display the terrain over which the mission is being flown, the AV flight position, and AV state information such as AV airspeed, altitude, attitude, engine status, and data link status automatically and continuously.

3.4.2.4 The RPVT shall display an image of the flyover area on the BVR GCS, with the actual AV location superimposed on the AV planned flight path.

3.4.2.5 The RPVT BVR GCS shall display mission waypoints.

3.4.2.5.1 The RPVT BVR GCS shall provide a means for an operator to modify the mission way-points during flight.

3.4.2.5.2 The RPVT BVR GCS shall provide a means for the preprogrammed waypoints to be changeable by the operator during the mission to accommodate user needs.

3.4.2.5.2.1 The RPVT BVR GCS, along with its AV MPE, shall control the AV from one waypoint to the next waypoint by turning, climbing or descending as necessary to arrive at the next waypoint’s position at the selected altitude and airspeed.

3.4.2.6 The RPVT BVR GCS shall store mission flight data on the BVR GCS and provide a means for the data to be transferred to storage media.

3.4.2.6.1 The RPVT BVR GCS shall provide the means to replay, upon operator request, the flight mission within 30 minutes of mission completion.

3.4.2.7 The RPVT BVR GCS shall perform BVR flights out to a minimum slant range of 25 Km (15.534 sm), assuming radio line of sight between the AV and the BVR GCS.

3.4.2.8 The RPVT BVR GCS shall control a minimum of one (1) RPVT AV.

3.4.2.9 The RPVT BVR GCS shall control and navigate the AV during any 24 hour time period regardless of weather conditions.

3.4.2.10 Mission Planning

The RPVT BVR GCS shall provide the means to plan a target mission flight profile.

3.4.2.10.1 The RPVT BVR GCS mission planning function shall display the operator selected waypoints on a map display.

3.4.2.10.2 The RPVT BVR GCS shall display data to allow the operator to ensure that the flight profile resulting from the chosen waypoints can be executed over the range terrain and within the flight envelope of the RPVT, considering flight path intercepts with the terrain, range safety constraints, and radio line of sight.

3.4.3 Over the Horizon BVR GCS.

The Over the Horizon BVR GCS shall perform IAW Section 3.4.2 of this specification, but shall not be limited to direct line of sight communications between the AV and the GCS.

NOTE: A BVR GCS (See 3.4.2) that provides continuous communications between the AV and the GCS when direct line of sight is not available would meet 3.4.3 requirement.

3.4.4 Radio Control Frequency and Data Link

The RPVT shall provide a radio control system and data link, for the AV and GCS components to operate within 360 to 400 MHz frequencies.

NOTE: A radio control frequency and data link that operates across the entire 225-400 MHz UHF spectrum shall be acceptable.

3.4.4.1 The RPVT radio control system and data link shall be tunable across the 360-400 MHz band with a standard of 25 KHz (12.5 KHz acceptable) increment spacing between channels and a minimum of 400 channel options.

3.4.4.2 The RPVT radio control system shall use a fixed frequency set, and shall not use frequency agile and frequency hopping radios.

3.4.4.3 The RPVT radio control system and data link shall provide a means to shield the radio control system from the effects of electronic noise in the environment that includes radio frequency (RF) noise generated by radar emissions, radio communication, radio control equipment, electrical generating systems, and electronically produced high ambient noise of unknown sources or a combination.

3.4.4.4 The RPVT radio control system and data link shall operate from a range of 0 m (0 sm) up to and including 3 Km (1.864 sm) minimum under manual control, and 0 m (0 sm) up to and including 25 Km (15.534 sm) minimum, when using the BVR control system.

3.4.4.5 The RPVT radio control system and data link shall allow operators to change frequencies in the field without the use of specialized test and calibration equipment (does not preclude the use of external channel changing equipment).

3.5 Ground Support Equipment (GSE)

The RPVT system GSE shall consist of an AV launcher, scoring portable ground control stations, special tools and equipment for RPVT operations, maintenance, and transportation, IAW the following requirements:

3.5.1 The RPVT GSE shall comply with the RPVT AV 30-minute setup and 5-minute recycle launch requirement.

3.5.1.1 The RPVT GSE shall be transportable utilizing commercial and military land, air, and sea vehicles. MIL-STD-1366 may be used as guidance.

3.5.2 AV Launcher

The RPVT GSE shall include a launcher that shall provide non-pyrotechnic zero ground run launches of the RPVT AV.

3.5.3 Scoring Portable Ground Control System (PGCS)

The RPVT shall include a scoring PGCS (see 6.2) that provides scoring information in near real-time (within 1 second) to an operator on the ground.

3.5.3.1 The RPVT PGCS shall provide scoring data from the AV to an operator, indicating the passage of projectiles by the AV or direct AV hits.

3.5.3.2 The RPVT system shall employ an Acoustic PGCS and a Radar PGCS to control the miss distance indication payload (See 3.6.7) and record scoring results.

NOTE: The RPVT may provide a single PGCS that performs both Acoustic and Radar functions.

3.5.3.3 The RPVT PGCS shall provide a function for storing scoring data for post mission processing and after action reviews.

3.5.3.4 The RPVT PGCS shall provide the scoring data formatted to facilitate printing an After Action Report (AAR) for each target engagement and consolidated report.

3.5.3.5 The RPVT PGCS shall provide an AAR, when requested by the operator.

3.5.3.6 The RPVT PGCS shall provide a telemetry link to transmit and receive data from the AV from a Miss Distance Indication (MDI) payload at a distance of from 0 Km (0 sm) to no less than 3 Km (1.864 sm).

3.6 Mission Payload Equipment (MPE)

The RPVT shall provide a means for the MPE for a mission to be installable or un-installable within the 30 minute setup time for the AV, IAW requirement 3.3.2.8.

3.6.1 Multiple Integrated Laser Engagement System (MILES) Payload The RPVT shall include a MILES payload system that shall be installable in the field.

3.6.1.1 The RPVT MILES payload installed on the AV, shall function with the smoke generator payload, IAW this specification, to provide a visual laser hit indication.

3.6.1.1.1 The RPVT AV shall provide MILES sensors that are installed at various points on the RPVT AV for laser detection at varying angles.

3.6.1.1.2 The RPVT AV shall provide a means to transfer the decoded MILES signal indicating a kill or near miss to the smoke generator payload.

3.6.1.1.3 The RPVT MILES payload shall accept laser codes from the U.S. Army Basic MILES, MILES 2000, and MILES XXI.

3.6.1.1.4 The RPVT MILES payload shall detect a laser signal from weapon systems equipped with U.S. Army MILES transmitters simulating a livefire engagement with the target at ranges of up to 2500 m (8202.1 ft).

3.6.2 BVR Payload

The RPVT BVR payload shall pass control messages from the BVR GCS to the AV, translate the BVR GCS messages for implementation on the AV, and transmit AV state data (altitude, airspeed, position) to the BVR GCS.

3.6.2.1 The RPVT BVR payload shall be installable and removable in the field within a 30 minute setup time.

3.6.3 Over the Horizon BVR Payload

The RPVT Over the Horizon BVR payload shall pass control messages from the BVR GCS to the AV, translate the Over the Horizon BVR GCS messages for implementation on the AV, and transmit AV state data (altitude, airspeed, position) to the BVR GCS.

3.6.3.1 The RPVT Over the Horizon BVR payload shall be installable and removable in the field within a 30 minute setup time.

3.6.3.2 The Over the Horizon BVR payload shall perform IAW paragraph 3.6.2 but shall not be limited to direct line of sight communications between the AV and the GCS.

NOTE: A BVR payload (See 3.6.2) that provides continuous communications between the AV and the GCS when direct line of sight is not available would meet 3.6.3 requirement.

3.6.4 Infrared Signature Payload (ISP)

3.6.4.1 The RPVT ISP shall generate a minimum energy intensity of 15 Watts (W) per steradian (See 6.2) in the mid-band of the infrared (IR) spectrum (3-5 microns), across a surface of +/- 20° in elevation and +/- 20° in azimuth, about a line in the horizontal plane and normal (90°) to the line of flight of the RPVT in straight and level flight.

Objective: Specified IR signature in 360 degrees around the AV in all aspects shall be acceptable.

NOTE: Straight and level flight shall be defined as a flight in which a constant altitude and heading are maintained.

3.6.4.2 The RPVT ISP shall operate according to the requirements of this specification while the AV is in flight, traveling at a speed of at least 86.9 knots (100 mph) IAS, on a 90° crossing flight path (right to left and left to right) perpendicular to the measurement axis.

NOTE: In order to meet this IR intensity, the IR device shall have to maintain a temperature of approximately from 750- 800 C (1382-1472° F).

3.6.4.3 The RPVT ISP IR signature centroid shall be situated on the airframe of the AV such that it is surrounded by at least 20.32 cm (8”) diameter of material to assure missile strike and subsequent detonation.

NOTE: Requirement can be met by providing an attachable surface for the RPVT ISP, providing the attachment does not reduce RPVT AV performance below the specified requirements of this specification.

3.6.4.4 The RPVT ISP shall operate according to the requirements of this specification throughout the duration of the AV flight.

3.6.4.5 The RPVT ISP shall employ non-explosive or non-hazardous materials (See 6.2) such that personnel can transport it without using special packaging and handling.

3.6.4.6 The RPVT ISP shall not employ the use of flares to satisfy the requirement for IR signature.

3.6.5 Laser Reflective Payload (LRP)

The RPVT shall include an LRP that shall reflect laser energy illuminating the target (Avenger Laser Return Finder - LRF) out to 3000 m (9,842.5 ft) from the laser source, +/- 30°of a line perpendicular to the 90° crossing aspect of the AV.

3.6.6 Smoke Generator Payload (SGP)

The RPVT AV shall include an SGP that shall provide a smoke emitting system that can be command activated from either the manual or BVR GCS, for visual target acquisition or automatically when used with the MILES payload.

3.6.6.1 The RPVT SGP shall be installable, maintainable and removable in the field.

3.6.6.2 The RPVT SGP shall emit at least 6 minutes of continuous smoke, as commanded from the GCS, with density to be seen by the unaided eye at up to 3000 m (9,842.5 ft).

3.6.6.3 When used with the MILES payload, the RPVT SGP shall provide 3 short (1 to 2 second) bursts of smoke when cued from the MILES system to indicate a MILES code for near miss, and 1 long (10 to 15 second) stream of smoke when cued from the MILES system to indicate a hit.

3.6.7 Miss Distance Indication (MDI) Payload

The RPVT MDI payload shall measure the proximity that a projectile passes the AV.

3.6.7.1 The RPVT MDI shall be transmitted via a telemetry link between the MDI Payload on board the AV and the scoring PGCS.

3.6.7.2 The RPVT shall require two types of MDI, Acoustic Scoring Payload and Radar Scoring Payload, as indicated in the following requirements:

3.6.7.3 Acoustic Scoring Payload (ASP)

The RPVT Acoustic Scoring Payload MDI shall measure the amplitude of the shock wave generated by projectiles traveling above the speed of sound (1224.7 kph /761 mph at sea level), this method of MDI being suitable for anti aircraft gunnery practice, ground-to-air and air-to-air.

3.6.7.3.1 The RPVT ASP shall provide the following performance requirements:

3.6.7.3.1.1 ASP Performance Characteristics

3.6.7.3.1.1.1 The RPVT ASP shall provide a scoring distance (radius around target from center) of at least 5 m (16.4 ft).

3.6.7.3.1.1.2 The RPVT ASP shall measure the MDI of the projectile with an accuracy of within +/- 15% of the actual distance that the projectile is from the AV.

3.6.7.3.1.1.3 The RPVT ASP shall score projectiles at a firing rate of from a single shot to not less than 2000 rounds per minute.

3.6.7.3.1.1.4 The RPVT ASP shall score in calibers of 7.62 mm and up to 25 mm (only supersonic).

3.6.7.3.1.2 ASP Physical Characteristics

The RPVT ASP shall be installable in the AV without degrading the AV performance as specified in this specification.

3.6.7.3.1.3 Electrical/Electromagnetic Interference (EMI)/Radio Frequency (RF) The RPVT ASP shall operate according to the requirements of this specification without producing electrical, EMI and RF interference with the RPVT AV avionics and other MPE (See 3.6).

3.6.7.3.1.4 The RPVT ASP shall be installable and removable in the field.

3.6.7.3.1.5 The RPVT ASP shall operate within the launch, flight and recovery environment of the AV as specified in this specification.

3.6.7.3.1.6 The RPVT ASP shall create no interference with the ASP functions of another RPVT AV ASP, when two RPVT AVs are operated simultaneously, with no less than 152.4 m (500 ft) between each AVs ASP antenna.

3.6.7.3.1.7 The RPVT ASP shall have a telemetry link to transmit and receive data from the AV from a Miss Distance Indication (MDI) payload at a distance of from 0 m (0 ft) to at least 3 Km (1.864 sm).

3.6.7.3.1.8 The RPVT ASP shall provide scoring for a minimum of 120 minutes.

3.6.7.4 Radar Scoring Payload (RSP)

The RPVT shall provide a Radar Scoring Payload MDI that uses Doppler shift measuring techniques to measure projectile miss distances.

3.6.7.4.1 Performance Characteristics

The RPVT RSP shall have a scoring distance (radius around target from center) of at least 5 m (16.4 ft) for projectiles up to 7.62mm; 10 m (32.8 ft) for projectiles of .50 caliber; and 25 m (82.02 ft) for missiles and 20mm and 25 mm projectiles.

3.6.7.4.1.1 The RPVT RSP shall provide coverage to include nulls, voids, bulges, and target shading that are standard in signal propagation from an RF antenna.

3.6.7.4.1.2 The RPVT RSP shall measure the MDI of the projectile with an accuracy of within +/- 15% of the actual distance of the projectile from the AV.

3.6.7.4.1.3 The RPVT RSP shall score projectiles at a firing rate of from single shot to not less than 2000 rounds per minute.

3.6.7.4.1.4 The RPVT RSP shall score in calibers of 7.62 mm and up to 25 mm, including missiles.

3.6.7.4.2 Physical Characteristics

The RPVT RSP shall be installable to the AV, without interfering with the flight performance of the AV as defined in this specification.

3.6.7.4.2.1 Electrical/Electromagnetic Interference (EMI)/Radio Frequency (RF) The RPVT RSP shall produce no electrical, EMI and RF interference with the RPVT AV avionics and other MPE (See 3.6).

3.6.7.4.2.2 The RPVT RSP shall be installable and removable in the field.

3.6.7.4.2.3 The RPVT RSP shall operate within the launch, flight and recovery environment of the AV as defined in this specification.

3.6.7.4.2.4 The RPVT RSP functions shall operate without interference between the scoring payloads when two or more AV are operated simultaneously, with no less than 152.4 m (500 ft) between each one, measured from one AV RSP antenna to the RSP antenna on the second AV.

3.6.7.4.2.5 The RPVT RSP shall have a telemetry link to transmit and receive data from the AV from a Miss Distance Indication (MDI) payload at a distance of from 0 m (0 ft) to at least 3 Km (1.864 sm).

3.6.7.4.2.6 The RPVT RSP scoring shall provide scoring data to the scoring PGCS for a minimum of 120 minutes.

3.6.8 Lighting Kit Payload (LKP)

The RPVT shall provide an LKP, that when installed on the AV, assists the operator with visual cues.

3.6.8.1 The RPVT AV shall include a lighting system IAW the following requirements:

3.6.8.2 The RPVT LKP shall provide lighting using the guidance from the FAR 23.1385 (See 2.2.2), for the position light system installation for AV wing tips, fuselage and tail.

NOTE: The primary purpose of the lighting system is to assist the AV operator in navigation and not to provide collision avoidance for other aircraft.

3.6.8.3 The RPVT LKP shall be installable, maintainable and removable in the field.

3.6.8.4 The RPVT LKP shall provide illumination of the AV during launch through flight and landing.

3.6.8.5 The RPVT LKP shall be operator activated and deactivated while the AV is on the ground and in the air.

3.6.8.6 The RPVT LKP shall provide visual cues such that the operator can manually control the AV from 0 m (0 ft) to at least 3 Km (1.864 sm) at night.

3.7 Identification and Markings

The RPVT system components (See 3.1) shall have an alphanumeric exterior identification marking at least 5.08 cm (2”) high located on the fuselage and on the removable major AV components (wings, tail surfaces).

3.7.1 The RPVT system components’ (See 3.1) markings shall be located and applied such that they do not interfere with operation and maintenance of the AV.

3.7.2 The RPVT system components’ (See 3.1) markings shall contain a unique AV serial number, in block lettering, expressed in both alphabetical and numerical text.

3.7.3 The RPVT system components’ (See 3.1) markings shall not be located or applied on the fuselage, such that spillage or seepage of fluids, engine emissions, accumulations of grime, and areas subject to wear shall obscure the view of the markings from the operator.

3.7.4 The RPVT system components’ (See 3.1) markings shall be of a weather-resistant material, and the letters and numbers shall not rub off or lose their integrity.

3.7.5 The RPVT system components’ (See 3.1) markings shall remain affixed to the equipment to which they are applied.

4. VERIFICATION

Section 4 establishes the verifications of section 3 requirements. The methods of verification are included in the Verification Cross Reference Matrix (VCRM) Table II. The procedures of verification shall be contractor proposed and Government approved.

4.1 Methods of Verification

The following methods shall be utilized to accomplish the verification of requirements:

1 – Analysis 2 – Demonstrations 3 – Examinations

4.2 Class of Verification

The RPVT system shall be subject to a final verification inspection as shown in the VCRM, Table II.

4.3 Conformance Inspection

Conformance inspection shall include the analyses, examinations and demonstrations as outlined in Table II, Verification Cross Reference Matrix.

4.4 Verification Matrix

Table II. Verification Cross Reference Matrix

VERIFICATION METHOD VERIFICATION CLASS (VC)*

N/A - NOT APPLICABLE A - Final Inspection

1 - ANALYSIS

2 – DEMONSTRATION

3.- EXAMINATION

SECTION 3 VERIFICATION

METHOD

VC* SECTION 4

REQUIREMENT N/A 1 2 3 A VERIFICATION

3.1 System Components X X

3.2 Reliability, Availability, and Maintainability X X X

3.3.1 AV Physical Characteristics X X

3.3.1.1 Power Plant X X

3.3.2.1 AV Range X X

3.3.2.2 AV Endurance/Flight Times X X

3.3.2.2.2 Auxiliary Fuel Installation X X X

3.3.2.2.3 Extended Auxiliary Fuel (Objective) X X X

3.3.2.2.4 Fuel Endurance X X

3.3.2.3 AV Service Ceiling (Altitude) X X

3.3.2.4 AV Performance with payload X X

3.3.2.5 AV Visibility X X

3.3.2.6 AV Color X X

3.3.2.7 AV Construction X X

3.3.2.8 AV Deployability X X

3.3.2.9 AV Speed X X

3.3.2.10 AV Environmental Conditions X X

3.3.2.10.1 Temperature X X

3.3.2.10.2 Precipitation X X

3.3.2.10.3 Day/Night Operations X X

3.3.2.10.4 Wind Speed X X

3.3.2.11 Survivability X X

3.3.2.12 Maintainability X X

3.3.2.13 Simultaneous Flights X X

3.3.2.14 Recovery/Landing X X

3.3.2.14.1 Recovery, Preparation and Launch X X

3.3.2.15 AV Manual Control X X

3.3.2.16 Flight Termination System X X

N/A - NOT APPLICABLE A - Final Inspection

1 - ANALYSIS

2 – DEMONSTRATION

3.- EXAMINATION

SECTION 3 VERIFICATION

METHOD

VC* SECTION 4

REQUIREMENT N/A 1 2 3 A VERIFICATION

3.4 Ground Control Station (GCS) X X

3.4.1 Manual Navigation GCS X X

3.4.1.1 Manual Navigation GCS Auxiliary Channels X X

3.4.1.2 Manual Navigation GCS Range X X

3.4.1.3 Manual Navigation GCS Frequency Setting X X

3.4.1.4 Manual Navigation GCS Set-up X X

3.4.1.5 Manual Navigation GCS FTS Option Selection X X

3.4.1.5.1 Manual Navigation GCS FTS Timing X X

3.4.2 BVR Navigation GCS X X

3.4.2.1 BVR Navigation GCS Programmable Way Point Navigation X

3.4.2.1.1 BVR Navigation GCS Secondary Control X X

3.4.2.2 BVR Navigation GCS Display X X

3.4.2.2.1 BVR Navigation GCS Display Timing X X

3.4.2.2.2 BVR Navigation Waypoints X X

3.4.2.2.3 BVR Navigation Datalink Connectivity X X

3.4.2.2.3.1 BVR Navigation Loss of Datalink < 10 Sec X X

3.4.2.2.3.2 BVR Navigation Loss of Datalink > 10 Sec X X

3.4.2.2.3.2.1 BVR Navigation Lost Link Programmability X X

3.4.2.2.3.2.2 BVR Navigation Regained Link X X

3.4.2.2.3.2.3 BVR Navigation Recovery Waypoint Confirmation X X

3.4.2.2.3.2.3.1 BVR Navigation Recovery Waypoint Limits X X

3.4.2.2.3.2.4 BVR Navigation Manual Override X X

3.4.2.3 BVR Navigation GCS Display Contents X X

3.4.2.4 BVR Navigation GCS Display AV Location X X

3.4.2.5 BVR Navigation GCS Display Waypoints X X

3.4.2.5.1 BVR Navigation GCS Enroute Waypoint Change X X

3.4.2.5.2 BVR Navigation GCS Enroute Route Change X X

3.4.2.5.2.1 BVR Navigation GCS Enroute AV Control X X

3.4.2.6 BVR Navigation Mission Data Storage X X

3.4.2.6.1 BVR Navigation Mission Data Replay X X

N/A - NOT APPLICABLE A - Final Inspection

1 - ANALYSIS

2 – DEMONSTRATION

3.- EXAMINATION

SECTION 3 VERIFICATION

METHOD

VC* SECTION 4

REQUIREMENT N/A 1 2 3 A VERIFICATION

3.4.2.7 BVR Navigation GCS Datalink Range X X

3.4.2.8 BVR Navigation GCS AV Capacity X X

3.4.2.9 BVR Navigation GCS 24 Hour Operations X X

3.4.2.10 BVR Navigation GCS Mission Planning X X

3.4.2.10.1 BVR Navigation GCS Mission Planning Display X X

3.4.2.10.2 BVR Navigation GCS Route Analysis Capability X X

3.4.3 Over the Horizon BVR GCS X X

3.4.4 Radio Control Frequency and Data Link X X

3.4.4.1 Radio Control Frequency, Channel Spacing, and Channels X X

3.4.4.2 Radio Control Frequency Fixed Channels X X

3.4.4.3 Radio Control Frequency Electronic Noise Susceptibility X X

3.4.4.4 Radio Control Frequency Range X X

3.4.4.5 Radio Control Frequency Channel Selection X X

3.5 Ground Support Equipment (GSE) X X

3.5.1 GSE Set-up X X

3.5.1.1 GSE Transportation (ground, air and sea) X X X Demonstrate ground, Analyze air and sea

3.5.2 AV Launcher X X

3.5.3 Scoring Portable Ground Control System (PGCS) X X

3.5.3.1 Scoring PGCS Data Transmission (AV to Operator) X X

3.5.3.2 Scoring PGCS Acoustic and Radar Capability X X

3.5.3.3 Scoring PGCS Data Storage X X

3.5.3.4 Scoring PGCS AAR X X

3.5.3.5 Scoring PGCS AAR Availability X X

3.5.3.6 Scoring PGCS Telemetry Link Range X X

3.6 Mission Payload Equipment (MPE) X X

3.6.1 MILES Payload X X

3.6.1.1 MILES Payload Hit / Near Miss Indication X X

3.6.1.1.1 MILES Sensor Installation X X

3.6.1.1.2 MILES Payload / SGP Connectivity X X

N/A - NOT APPLICABLE A - Final Inspection

1 - ANALYSIS

2 – DEMONSTRATION

3.- EXAMINATION

SECTION 3 VERIFICATION

METHOD

VC* SECTION 4

REQUIREMENT N/A 1 2 3 A VERIFICATION

3.6.1.1.3 MILES Payload Compatibility with MILES Systems X X

3.6.1.1.4 MILES Payload Range X X

3.6.2 BVR Payload X X

3.6.2.1 BVR Payload Field Installation X X

3.6.3 Over the Horizon BVR Payload X X

3.6.3.1 Over the Horizon BVR Payload Installation X X

3.6.3.2 Over the Horizon BVR Payload non-line of sight connectivity X X

3.6.4.1 Infrared Signature Payload (ISP) Output X X

3.6.4.2 ISP Coverage X X

3.6.4.3 ISP / AV Physical Size X X

3.6.4.4 ISP Duration X X

3.6.4.5 ISP Non-Explosive/Non-Hazardous Material X X

3.6.4.6 ISP No Use of Flares X X

3.6.5 Laser Reflective Payload (LRP) X X

3.6.6 Smoke Generator Payload (SGP) X X

3.6.6.1 SGP Installation X X

3.6.6.2 SGP Duration/Visual Range X X

3.6.6.3 SGP with MILES Payload X X

3.6.7 Miss Distance Indication (MDI) Payload X X

3.6.7.1 MDI Telemetry Link X X

3.6.7.2 MDI Types X X

3.6.7.3 Acoustic Scoring Payload (ASP) X X

3.6.7.3.1.1.1 ASP Scoring Radius X X

3.6.7.3.1.1.2 ASP Accuracy X X

3.6.7.3.1.1.3 ASP Rate X X

3.6.7.3.1.1.4 ASP Caliber X X

3.6.7.3.1.2 ASP Installation Impact on AV Performance X X

3.6.7.3.1.3 ASP EMI/RF Interference X X

3.6.7.3.1.4 ASP Field Installation and Removal X X

N/A - NOT APPLICABLE A - Final Inspection

1 - ANALYSIS

2 – DEMONSTRATION

3.- EXAMINATION

SECTION 3 VERIFICATION

METHOD

VC* SECTION 4

REQUIREMENT N/A 1 2 3 A VERIFICATION

3.6.7.3.1.5 ASP Operational Environment X X

3.6.7.3.1.6 ASP Interference with Another AV ASP X X

3.6.7.3.1.7 ASP Telemetry Link Range X X

3.6.7.3.1.8 ASP Operational Duration X X

3.6.7.4 Radar Scoring Payload (RSP) X X

3.6.7.4.1 RSP Performance Characteristics X X X - Demonstrate .50 caliber

- Analysis for 7.62mm, missiles, 20mm and 25mm

3.6.7.4.1.1 RSP Antenna Pattern X X

3.6.7.4.1.2 RSP Scoring Accuracy X X

3.6.7.4.1.3 RSP Rate X X

3.6.7.4.1.4 RSP Caliber X X

3.6.7.4.2 RSP Installation on AV Performance X X

3.6.7.4.2.1 RSP EMI/RF Interference X X

3.6.7.4.2.2 RSP Field Installation and Removal X X

3.6.7.4.2.3 RSP Operational Environment X X

3.6.7.4.2.4 RSP Interference with Another AV RSP X X

3.6.7.4.2.5 RSP Telemetry Link Range X X

3.6.7.4.2.6 RSP Duration X X

3.6.8 Lighting Kit Payload (LKP) X X

3.6.8.2 LKP Light Color and Location X X

3.6.8.3 LKP Field Installation and Removal X X

3.6.8.4 LKP Operation from launch through landing X X

3.6.8.5 LKP Activation and Deactivation X X

3.6.8.6 LKP Range X

3.7 Identification and Markings X X

3.7.1 Marking Locations (non-interference) X X

3.7.2 Marking Content and Format X X

3.7.3 Marking Wear X X

3.7.4 Marking Weather-resistance X X

N/A - NOT APPLICABLE A - Final Inspection

1 - ANALYSIS

2 – DEMONSTRATION

3.- EXAMINATION

SECTION 3 VERIFICATION

METHOD

VC* SECTION 4

REQUIREMENT N/A 1 2 3 A VERIFICATION

3.7.5 Marking Permanency X X

5. PACKAGING

For acquisition purposes, the packaging requirements shall be specified in the contract. When actual packaging of materiel is to be performed by DoD or in-house personnel, these personnel need to contact the responsible packing activity to ascertain requisite packing requirements.

Packing requirements are maintained by the packing activity.

6. NOTES

This section contains information of a general or explanatory nature that may be helpful, but is not mandatory.

6.1 Acronyms

AMD Air and Missile Defense ASP Acoustic Scoring Payload AV Air Vehicle BVR Beyond Visual Range cm Centimeters EMI Electromagnetic Interference FAA Federal Aviation Administration FAR Federal Aviation Regulation FMS Foreign Military Sales FTS Flight Termination System COTS Commercial Off-the-Shelf GCS Ground Control Stations GPS Global Positioning System GSE Ground Support Equipment IR Infrared Km Kilometers LKP Lighting Kit Payload LOS Line of Site LRP Laser Reflective Payload LRF Laser Range Finder MDI Miss Distance Indication MILES Multiple Integrated Laser Engagement System MPE Mission Payload Equipment

MSL Mean Sea Level NDI Non-Developmental Items PGCS Portable Ground Control System RCS Radar Cross Section RF Radio Frequency RPVT Remotely…