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 | 31 January 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

Theater demand for unmanned ISR and standoff EOD is already outrunning formal programs of record. The force in Iraq and Afghanistan is flying ACTD leftovers, COTS small air vehicles, and contractor-supported ground robots while Congress still treats UAVs as a procurement-management problem rather than a trust-and-access problem.

### Key judgments

1. **[Assessment — high confidence]** As of this cutoff, the public congressional picture of the U.S. unmanned fleet is still the April 2003 CRS inventory — Predator, Global Hawk, Pioneer, Hunter, Shadow — plus a stated FY04 request of $1.39 billion. That inventory understates what is actually flying at battalion and company level.
2. **[Assessment — moderate confidence]** Ground robots (PackBot, TALON) and hand-launched air vehicles are already the systems that change who must physically approach an IED or a compound. Their control links and payload bays are the real trust boundary this month, not the airframes.
3. **[Inference — moderate confidence]** Sole-source data rights on Predator-family aircraft and a thin UUV industrial base mean a later Watch desk would have had to treat manufacturer lock-in as a collection requirement, not a contracting footnote.

### 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. CRS still frames the unmanned inventory as five major air vehicles

*Event / publication dates: CRS RL31872 dated 25 April 2003; still the governing open congressional brief as of 31 January 2004.*

**Verified record — [Fact — A1]** The Congressional Research Service report *Unmanned Aerial Vehicles: Background and Issues for Congress* (RL31872, 25 April 2003) defines a UAV as a powered aerial vehicle that does not carry a human operator, uses aerodynamic lift, can fly autonomously or remotely, and can carry a lethal or nonlethal payload. CRS lists five major DOD UAVs — Air Force Predator and Global Hawk, Navy/Marine Pioneer, Army Hunter and Shadow — and records FY01 UAV investment of approximately $667 million, FY03 funding over $1.1 billion, and a Pentagon FY04 request of $1.39 billion. CRS notes a UAV accident rate 100 times that of manned aircraft and flags industrial-base and proliferation questions. Source fetched: https://www.everycrsreport.com/files/20030425_RL31872_089a1bc2a3f353e69de4557e6614bc453e2049b2.html

**Threat landscape.** The congressional picture treats unmanned systems as an acquisition category. The physical consequence in theater is already different: ISR and strike access without a pilot in the airframe, paid for by satellite bandwidth and ground-station trust.

**Intelligence assessment.** [Assessment — high confidence] RL31872 remains the best open baseline for what Congress thinks it is buying. [Inference — moderate confidence] The report’s own list of developmental systems (UCAV, VTUAV/Fire Scout, BAMS, Dragon Eye, Dragon Warrior) shows the inventory will fragment downward in size this year. [Uncertainty] CRS does not give a contemporaneous count of small UAVs or EOD robots already in Iraq.

**Opportunity.** A Passport record of every air vehicle type actually flying in CENTCOM — not just the five “major” systems — would have closed the gap between the Hill brief and the force.

**LRRK relevance.** Watch / Passport. A 2004 Watch desk would have needed to log CRS as the official inventory and immediately annotate it as incomplete for small UAS and ground-act systems.

**Confidence.** High on the CRS figures and program list; moderate that theater systems already exceed that list; low on unpublished CIA Predator holdings (CRS notes an “undisclosed number”).

## 02. Predator is already a multi-role hunter, not a reconnaissance leftover

*Event / publication dates: CRS RL31872 (25 April 2003) recounts Predator Hellfire use through early 2003; no newer official recap published this month.*

**Verified record — [Fact — A1]** CRS records Predator as the first DOD ACTD UAV to transition to military duty and the first UAV to fire offensive weapons. It records Hellfire use in Afghanistan and Yemen, two strikes in Operation Iraqi Freedom in March 2003 (an anti-aircraft vehicle and a TV satellite dish in Baghdad), and a reported March 2003 air-to-air engagement in which a Predator launched a Stinger at an Iraqi MiG before being shot down. Designation changed from RQ-1B to MQ-1 on 1 February 2002. Unit cost is given as $4.5 million per air vehicle and $30 million per system. Source: https://www.everycrsreport.com/files/20030425_RL31872_089a1bc2a3f353e69de4557e6614bc453e2049b2.html

**Threat landscape.** The trust failure is not the Hellfire. It is the satellite command link and the ground control station: whoever holds the GCS and the SATCOM path holds the kill chain.

**Intelligence assessment.** [Assessment — high confidence] Armed Predator is an established, publicly documented capability as of this cutoff. [Inference — moderate confidence] Reach-back from CONUS ground stations, already described in later March 2004 testimony as used in OIF, is the C2 architecture that will matter more than airframe count. [Uncertainty] CIA-operated Predator numbers and targeting authorities remain unpublished.

**Opportunity.** A contemporaneous collection requirement on Predator Primary Satellite Link availability and GCS redundancy would have been more useful than another airframe photo.

**LRRK relevance.** Control Fabric / Sense-Move-Act. Passport would have recorded MQ-1 as a remote-act system whose safety case lives in the datalink, not the airframe.

**Confidence.** High on CRS-documented strikes and designation; moderate on CONUS reach-back already being routine; low on unpublished CIA orbits.

## 03. PackBot and TALON are already the IED standoff layer

*Event / publication dates: continuing from 2003 Iraq/Afghanistan fielding; no new primary contract release this month. Later public recaps (iRobot S-1, Navy MTRS, GlobalSecurity TALON page) are used only to establish that the systems were already in theater before January 2004.*

**Verified record — [Fact — B1]** iRobot’s later S-1 (filed 30 September 2005) states the firm sold the U.S. military more than 200 PackBot tactical robots over the prior three years, “most of which have been deployed on missions in Afghanistan and Iraq.” GlobalSecurity’s TALON page records TALON in Bosnia from 2000, Afghanistan from early 2002, and Iraq “since the war started,” used for IED detection and removal. These are later recaps, not January 2004 originals; they are cited only to establish presence, not January quantities. Sources fetched: https://www.sec.gov/Archives/edgar/data/1159167/000095013505005611/b55709a2sv1za.htm ; https://www.globalsecurity.org/military/systems/ground/talon.htm

**Threat landscape.** The physical consequence is that an RF or fiber operator control unit now stands between a technician and an IED. Jamming, spoofing, or loss of that link returns the human to the device.

**Intelligence assessment.** [Assessment — high confidence] Both families are in theater as of this cutoff. [Inference — moderate confidence] Proprietary OCUs and non-interoperable radios will become a logistics and electronic-warfare problem as inventories grow. [Uncertainty] No contemporaneous January 2004 public inventory of PackBot or TALON in Iraq was located.

**Opportunity.** A Watch log of OCU frequencies, fiber vs RF employment, and which EOD teams held which chassis would have been the useful record.

**LRRK relevance.** Kestrel / Lab / Sense-Move-Act. Ground-act systems are already changing who dies at the device. Passport would have treated the OCU as the credentialed endpoint.

**Confidence.** High on pre-2004 presence; low on January 2004 counts (refused later memory numbers).

## 04. Undersea: REMUS-class AUVs are combat-proven, but the Navy still lives on the 2000 master plan

*Event / publication dates: 2000 Navy UUV Master Plan still in force; 2004 update not yet published. OIF Umm Qasr mine-clearance is the last public combat use.*

**Verified record — [Fact — B2]** GlobalSecurity’s UUV page records that during Operation Iraqi Freedom, UUVs worked with Marine Mammal Systems and coalition assets to clear mines from approach lanes to the Iraqi port of Umm Qasr. The same page and later NAVSEA public affairs state the 2000 master plan remained the governing document until a 2004 update (completed late 2004, approved for publication in January 2005). No January 2004 contract announcement for REMUS, HUGIN, or Bluefin was located in this reconstruction. Sources: https://www.globalsecurity.org/military/systems/ship/systems/uuv.htm ; https://www.marinelink.com/news/published-master-navy316972

**Threat landscape.** The undersea trust boundary is autonomy without a tether: a UUV that cannot be recalled or authenticated is a sensor and, later, a weapon the host submarine does not fully see.

**Intelligence assessment.** [Assessment — moderate confidence] Man-portable MCM AUVs are the only undersea unmanned class with a public combat pedigree this month. [Inference — low-moderate confidence] A new master plan is being staffed (chartered December 2003 per later plan text) but is not a public document this month. [Uncertainty] AN/BLQ-11 / LMRS status is not in an open January 2004 primary.

**Opportunity.** Collect the 2000 master plan text and any NAVSEA MCM after-action that names vehicle types used at Umm Qasr.

**LRRK relevance.** Watch / Control Fabric. A Passport for undersea systems would have started with “which vehicle class, which host, which comms path,” not with vendor marketing.

**Confidence.** High on OIF Umm Qasr UUV use as stated; moderate that the 2000 plan is still governing; low on named vehicle inventories this month.

## 05. Small-unit air: Dragon Eye selected, Raven already a SOF tool — the inventory CRS does not count

*Event / publication dates: Marine Corps competitive selection of Dragon Eye, November 2003; first FRP deliveries announced for spring 2004. Raven already with SOF in Afghanistan (OSD testimony 17 March 2004, describing the state as of early 2004).*

**Verified record — [Fact — A1]** Dr. Glenn F. Lamartin, Director of Defense Systems, USD(AT&L), told the House Armed Services Tactical Air and Land Forces Subcommittee on 17 March 2004 that the Marine Corps competitively selected Dragon Eye in November 2003 and that first full-rate production systems “deliver in the spring of this year,” with twenty prototype systems already deployed in OIF. He also stated Army SOF support operations in Afghanistan with the 4-pound backpackable Raven, and that the Army made a one-time COTS buy of 185 Raven systems (over 550 air vehicles) for regular units in Iraq. That testimony post-dates this cutoff by six weeks; it is used here only as a near-contemporaneous official description of a decision already taken in November 2003 and a buy already made. Source: http://www.globalsecurity.org/military/library/congress/2004_hr/04-03-17lamartin.htm

**Threat landscape.** Hand-launched electric air vehicles put a video link and a GPS autopilot into a rucksack. Frequency collision with other UAVs and with IED jammers is the emerging physical consequence.

**Intelligence assessment.** [Assessment — high confidence] Dragon Eye FRP and the Raven COTS buy are decided before this cutoff. [Inference — moderate confidence] Battalion-level custody of a “company” UAV will become the norm because larger UAVs are scarce. [Uncertainty] Exact January 2004 in-theater Raven/Dragon Eye counts are not in an open primary dated this month.

**Opportunity.** Log every small-UAS frequency and airspace block in CENTCOM before the low-altitude layer saturates.

**LRRK relevance.** Watch / Sense-Move-Act. Passport would have recorded small UAS as a separate class from the five “major” CRS vehicles, with a different C2 and a different loss model.

**Confidence.** High on the November 2003 selection and the 185-system buy as later officially stated; moderate that deliveries have not yet all arrived; low on January 2004 serial numbers.

## Forward indicators

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

1. First full-rate Dragon Eye deliveries (promised for spring 2004).
2. Whether Predator B / MQ-9 crosses a formal milestone (later recorded as Milestone B in February 2004).
3. Any public U.S. or Pakistani statement that attributes a Waziristan strike to an unmanned aircraft.
4. Navy publication of a UUV master-plan update (staffed since December 2003).
5. IED-driven emergency buys of additional PackBot/TALON variants and any move to arm TALON (SWORDS).

> **Collection integrity.** Used CRS RL31872 (fetched) as the January baseline. Used March 2004 HASC testimony only to describe decisions already taken (Dragon Eye selection, Raven buy) and labeled the date offset. Refused later-memory mission counts for TALON (“20,000 by end of 2004”) and iRobot’s 2005 S-1 “more than 200 PackBots” as January quantities. No contemporaneous January 2004 REMUS contract text was located; Umm Qasr is the last public combat use cited. Wikipedia and undated tertiary vendor pages were excluded.

*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>