LC-1 · Kinematic Threat Briefs

Kinematic Threat Brief

# Kinematic Threat Brief

**LRRK Watch / Open-Source Intelligence** — Five current signals across systems that sense, move, and act.

| Field | Value |
| --- | --- |
| Collection cutoff | 29 February 2004 |
| Platform | Quiet Systems |
| Data label | Open-source intelligence // LRRK analytic product |
| Handling | Public-source material. Image rights require separate verification before publication. |

## Executive read

### BLUF

MQ-9 crosses Milestone B this month as a hunter-killer development program, not as a fielded combat system. The access change is contractual and architectural: General Atomics keeps the data rights, and the Air Force is buying a larger, more armed orbit before the stores-management subsystem is mature.

### Key judgments

1. **[Assessment — high confidence]** February 2004 is the public Milestone B date for what will later be called Reaper. That is a development start, not IOC. IOC is not a 2004 event.
2. **[Assessment — high confidence]** The government does not own Predator-family technical data. Sole-source awards are already the acquisition method, which locks the C2 and air-vehicle stack to one manufacturer.
3. **[Inference — moderate confidence]** A Watch desk that dated MQ-9 as “operational” in 2004 would have been wrong. The honest record this month is a milestone and a data-rights problem.

### Analytic labels

- **Fact** — verified reporting or primary record
- **Assessment** — analytic judgment
- **Inference** — reasoned but not directly observed
- **Uncertainty** — unresolved information gap

### Source grades

- **A1** — authoritative primary record / directly confirmed
- **B1–B2** — generally reliable and corroborated
- **C3** — useful but requires caution

## 01. MQ-9 / Predator B enters system development (Milestone B)

*Event / publication dates: February 2004 Milestone B (recorded in later Selected Acquisition Reports and the GlobalSecurity MQ-9 program chronology compiled from Air Force notices).*

**Verified record — [Fact — A1]** Later DOD Selected Acquisition Reports, summarizing the program’s official milestone table, list Milestone B for MQ-9 as February 2004. The GlobalSecurity MQ-9 program page, compiled from Aeronautical Systems Center notices, states the Reaper “entered system development in February 2004” and that ACC had approved an MQ-9 Concept of Operations in June 2003. The first Predator B prototype flew 2 February 2001 from El Mirage; the fifth Predator B was completed in June 2004. This filing treats February 2004 as development start only. Source: https://www.globalsecurity.org/military/systems/aircraft/mq-9-program.htm

**Threat landscape.** A larger turboprop orbit with more hardpoints changes persistence and payload. The trust failure is concurrency: the Air Force will later produce aircraft before critical design review and before stores-management maturity.

**Intelligence assessment.** [Assessment — high confidence] Milestone B is the correct February 2004 event. [Inference — moderate confidence] Sole-source dependence on GA-ASI will survive every later production lot. [Uncertainty] No February 2004 public notice of an IOC date exists; any such date would be invented.

**Opportunity.** File the milestone letter and the data-rights clause. Do not file an IOC.

**LRRK relevance.** Passport / Watch. A 2004 Passport would have opened an MQ-9 card labeled “development, not fielded,” with a required annotation that IOC is not to be back-dated.

**Confidence.** High on February 2004 as Milestone B; high that IOC is not this year; low on unpublished internal ACC fielding hopes.

## 02. Sole-source data rights: the government does not own the Predator stack

*Event / publication dates: continuing; formalized in ASC sole-source notices (24 November 2003 SDD notice already on the record; 19 November 2004 four-ship notice still ahead).*

**Verified record — [Fact — A1]** ASC’s 24 November 2003 notice of intent (F33657-02-G-4035 0023) to award MQ-9A System Development and Demonstration to General Atomics Aeronautical Systems, Inc., states GA-ASI is the sole designer, developer, and manufacturer of the Predator system and the only firm with the necessary technical data. The later 19 November 2004 notice repeats that “the government did not own the data rights for the system” and cites 10 U.S.C. 2304(c)(1) / FAR 6.302-1. Source: https://www.globalsecurity.org/military/systems/aircraft/mq-9-program.htm

**Threat landscape.** Without data rights, no second source can maintain, patch, or independently assess the air vehicle, GCS, or satellite link. Supply-chain assurance is a single-vendor problem.

**Intelligence assessment.** [Assessment — high confidence] Data-rights lock-in is already official policy language. [Inference — moderate confidence] This will constrain every foreign military sale and every cybersecurity assessment of the stack for the rest of the decade. [Uncertainty] The precise data-rights schedule in the 2002 IDIQ is not in the public notices.

**Opportunity.** Collect the IDIQ data-rights clauses and any OSD exception memos.

**LRRK relevance.** Control Fabric / Campaign. Passport would have tagged GA-ASI as a single point of failure for medium-altitude UAS, not merely a contractor.

**Confidence.** High on the published sole-source rationale; moderate on how completely the government is locked out of internals.

## 03. Ground-act: IED demand is pulling commercial robots into a wartime production rate

*Event / publication dates: continuing Iraq/Afghanistan EOD use; no new FRP decision this month (MTRS FRP is May 2005).*

**Verified record — [Fact — B1]** TALON has been in Iraq since the start of the war; PackBot likewise. The later Navy MTRS announcement (22 June 2005) states that “last year” — i.e., 2004 — the EOD Program Office met CENTCOM’s requirements for small robotic systems against a burgeoning IED threat. That is a 2005 recap of 2004 demand, not a February 2004 quantity. Sources: https://www.globalsecurity.org/military/systems/ground/talon.htm ; https://www.globalsecurity.org/military/library/news/2005/06/mil-050622-nns02.htm

**Threat landscape.** Commercial EOD robots with proprietary radios are being asked to absorb blast so a technician does not. Link loss or RF fratricide with IED jammers is the near-term failure mode.

**Intelligence assessment.** [Assessment — high confidence] Demand is operational, not experimental. [Inference — moderate confidence] A down-select to two vendors will come; it has not come yet. [Uncertainty] February 2004 in-theater robot counts are not in an open primary dated this month.

**Opportunity.** Log vendor, OCU type, and whether control is RF or fiber on each EOD team.

**LRRK relevance.** Kestrel / Sense-Move-Act. The acting ground robot is already a combat system. Watch would have recorded it as such, not as a gadget.

**Confidence.** High on presence and demand; low on February quantities.

## 04. Shadow and Hunter remain the Army’s tactical ISR, not Raven

*Event / publication dates: continuing OIF employment from March 2003; Lamartin 17 March 2004 testimony describes the state the force is already in.*

**Verified record — [Fact — A1]** Lamartin’s 17 March 2004 HASC testimony — six weeks after this cutoff, describing current operations — states Shadow and Hunter have been in Iraq since 19 March 2003, have flown thousands of hours, and that Shadow is the first UAV fielded through the normal acquisition process (IOT&E May 2002; contract December 1999 to IOC in 32 months). As of his testimony the Army had fielded 12 Shadow systems, 8 to operational units, 4 directly supporting combat; FY04 procurement was being accelerated by 3 systems to 11. Source: http://www.globalsecurity.org/military/library/congress/2004_hr/04-03-17lamartin.htm

**Threat landscape.** Brigade-level video over a line-of-sight tactical datalink. Frequency interference is already a roadmap “top ten” goal (TCDL integration).

**Intelligence assessment.** [Assessment — high confidence] Shadow/Hunter, not the small UAS, are the Army’s formal tactical layer this month. [Inference — moderate confidence] Endurance and TCDL upgrades will be the 2004 hardware story. [Uncertainty] Exact February 2004 combat hours are not separately published.

**Opportunity.** Collect Shadow frequency deconfliction incidents and any convoy-overwatch TTPs.

**LRRK relevance.** Watch / Control Fabric. Passport would have distinguished Shadow (program of record, TCDL path) from Raven (COTS urgent buy).

**Confidence.** High on the official program facts; moderate applying March testimony backward 16 days into late February.

## 05. Undersea and export: no new public master plan, no new public REMUS award this month

*Event / publication dates: none new this month. Continuing 2000 UUV Master Plan; Hydroid–NAVSEA six-year ceiling contract is a 2004 event without a February public date in hand.*

**Verified record — [Fact — B2]** The Navy’s next UUV Master Plan is still unpublished (completed late 2004). GlobalSecurity records four future UUV classes and nine capabilities as the 2004 plan’s content, but that text is not a February 2004 release. A later Hydroid release states Hydroid and NAVSEA signed a six-year contract in 2004 with a $32 million ceiling for REMUS-based “Swordfish” VSW MCM systems; the month is not given in the fetched text, so this filing does not assign it to February. Sources: https://www.globalsecurity.org/military/systems/ship/systems/uuv.htm

**Threat landscape.** Without a published update, industry is still building man-portable MCM vehicles against a 2000 vision while the fleet’s real need is clandestine ISR and submarine-launched heavyweight vehicles.

**Intelligence assessment.** [Assessment — moderate confidence] Man-portable MCM remains the only fielded Navy UUV class. [Inference — low confidence] A 2004 Hydroid–NAVSEA vehicle contract exists somewhere this year. [Uncertainty] Month of signature unknown; LMRS/AN/BLQ-11 status unpublished this month.

**Opportunity.** FOIA the Hydroid–NAVSEA 2004 award notice and the draft master-plan staffing package.

**LRRK relevance.** Watch. Honest negative: do not invent a February undersea event.

**Confidence.** High that no February public UUV release was found; low on the unsigned month of the Hydroid ceiling.

## Forward indicators

Ranked watchlist as of the collection cutoff (what a 2004 Watch desk would have monitored next).

1. ASC or GA-ASI public notice of MQ-9 SDD contract actions.
2. 17 March 2004 HASC UAV/UCAV hearing (already scheduled in the committee calendar).
3. First Dragon Eye FRP deliveries (spring 2004).
4. Any public statement that a Waziristan missile was unmanned.
5. Foster-Miller or iRobot emergency IED robot awards.

> **Collection integrity.** Milestone B is taken from the official SAR milestone table as reported on the fetched GlobalSecurity MQ-9 chronology, not from a February 2004 press release (none was located). March 2004 Lamartin testimony is labeled as post-cutoff when used. The Hydroid $32M ceiling is not dated to February. Wikipedia Reaper IOC dates were excluded. No IOC is asserted.

*LRRK — security assurance for systems that sense, move, and act.*

<p align="right"><span style="opacity:0.35;letter-spacing:0.18em;font-size:0.8em">L-C1</span></p>