# Kinematic Threat Brief

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

| Field | Value |
| --- | --- |
| Collection cutoff | 31 October 2007 |
| 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

October made Reaper a public combat and coalition fact: the Air Force announced Afghanistan operations that began 25 September, and the RAF declared an in-service date of 31 October for three unarmed UK Reapers—the same airframe, two flags, one Nevada-linked C2 schoolhouse.

### Key judgments

1. **[Assessment — high confidence]** Air Force Historical Foundation records that early Reaper missions (first 25 September) were not public until 11 October; later Air Force News (search-indexed) stated 12 missions since 25 September, about one sortie per day, weapons not yet expended.
2. **[Assessment — high confidence]** General Atomics / MoD text dated 8 November states the first of three British Reapers arrived in Afghanistan in early October and that the in-service date was 31 October 2007; the UAV was then unarmed.
3. **[Inference — moderate confidence]** OSD’s October UAS Task Force recharter (GAO-dated) is the department’s alternative to an Air Force executive agent—joint paper, not joint ownership.

### 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. Air Force announces Reaper in Afghanistan — first public hunter-killer combat line

*Event / publication dates: missions from 25 September; public 11 October.*

**Verified record — [Fact — A1]** Air Force Historical Foundation: first operational mission 25 September; “These early missions were not reported publicly until 11 October.” https://afhistory.org/september-25-2007/ The live 11 October af.mil article was access-denied this filing; open-indexed Air Force News text attributes to Gen. T. Michael Moseley a “hunter-killer” characterization and states the Reaper had completed 12 missions since 25 September, averaging about one sortie per day, and that operators had not yet been called to drop weapons. Those indexed sentences are treated as B1 pending recovered HTML.

**Threat landscape.** A bomb-capable unmanned aircraft is now an announced combat system. The physical change is persistence-plus-payload over Afghanistan; the C2 pattern remains remote split from Creech.

**Intelligence assessment.** [Assessment — high confidence] Public announcement is 11 October; first mission is 25 September. [Inference — moderate confidence] Weapons will follow once ROE and sensor-shooter confidence match Predator practice. [Uncertainty] Recovered HTML of the 11 October release was not obtained.

**Opportunity.** Recover the 11 October Air Force News HTML.

**LRRK relevance.** Watch: October is the public Reaper-combat month. Control Fabric: same SATCOM trust boundary as Predator.

**Confidence.** High on the 25 September / 11 October dates; moderate on the indexed 12-mission / no-weapons sentences.

## 02. RAF Reaper in-service 31 October — coalition hunter-killer, still unarmed

*Event / publication dates: early October arrival; ISD 31 October; GA/MoD release 8 November.*

**Verified record — [Fact — A1]** General Atomics, 8 November 2007, reprinting MoD facts: “The first of 3 British Reapers arrived in Afghanistan in early October.” “Reaper’s first flight was not publicised until the in service date (31 October 2007) was reached.” Sir Glenn Torpy: major milestone for RAF surveillance and reconnaissance. Gen. Moseley: interoperability and faster fielding. 39 Squadron; training by USAF; No. 1115 Flight continues Predator A. “The Reaper UAV is currently unarmed. It is capable of being armed and the MoD is investigating arming options.” 15 months from requirement to theater. https://www.ga.com/reaper-takes-to-the-air

**Threat landscape.** A second flag now flies the same airframe from the same Creech schoolhouse. The trust boundary is exportable C2 and whether London will arm.

**Intelligence assessment.** [Assessment — high confidence] Three UK Reapers, ISD 31 October, unarmed. [Inference — moderate confidence] Arming will be a 2008 political decision (later MoD text dates armed use to May 2008). [Uncertainty] UK GCS location split (Creech vs. UK) is not fully specified in the fetched release.

**Opportunity.** MoD 31 October ISD notice (the GA reprint is the fetched primary).

**LRRK relevance.** Passport: first coalition Reaper. Control Fabric: Combined Predator Task Force as the interoperability path.

**Confidence.** High on ISD, three airframes, unarmed status.

## 03. UAS Task Force rechartered — no executive agent

*Event / publication dates: October 2007 (GAO-09-175).*

**Verified record — [Fact — A1]** GAO-09-175: after declining an Air Force executive-agent bid, DepSecDef directed USD(AT&L) in September 2007 to convene a task force; “the Undersecretary of Defense for Acquisition, Technology, and Logistics rechartered the UAS Planning Task Force in October 2007 as the UAS Task Force.” Near-term focus: combine Sky Warrior and Predator. https://www.gao.gov/assets/a283275.html

**Threat landscape.** Joint management is a task force, not a single accountable owner—the gap GAO-07-836 named in July.

**Intelligence assessment.** [Assessment — high confidence] October recharter is GAO-recorded. [Inference — moderate confidence] The task force will not solve JFACC/tactical visibility. [Uncertainty] October charter text not fetched.

**Opportunity.** FOIA the October 2007 recharter.

**LRRK relevance.** Control Fabric: OSD chose coordination over ownership.

**Confidence.** High on the GAO dating; moderate on unpublished charter.

## 04. ER/MP still SDD — merger memo does not field Block 1

*Event / publication dates: September 2007 merger memo; 2005 SDD.*

**Verified record — [Fact — A1]** ER/MP SDD: 17 aircraft, mid-2009. https://www.ga-asi.com/general-atomics-aeronautical-systems-and-its-team-warrior-partners-awarded-major-u-s-army-contract September memo: single contract by October 2008. https://www.gao.gov/assets/a283275.html

**Threat landscape.** Army organic hunter-killer remains a 2009-class SDD.

**Intelligence assessment.** [Assessment — high confidence] No October Block 1 combat line. [Inference — moderate confidence] Block 0 / Alpha will keep filling 2008. [Uncertainty] October Alpha orbits unpublished.

**Opportunity.** Army October SAR extract.

**LRRK relevance.** Lab: merger is contractual, not operational.

**Confidence.** High.

## 05. Fire Scout / UCAS-D / REMUS — sea portfolio unchanged this month

*Event / publication dates: prior-month primaries still governing.*

**Verified record — [Fact — B1]** Fire Scout Milestone C (31 May); UCAS-D $635.8 million (6 August); Hydroid REMUS $26 million (15 May). No October Navy operational employment primary fetched.

**Threat landscape.** Sea unmanned remains production/demo.

**Intelligence assessment.** [Assessment — high confidence] Continuity. [Inference — low confidence] Payload flights “this fall” (Murphy, 31 May) may slip. [Uncertainty] October flight-test results unpublished.

**Opportunity.** NAVAIR October test note.

**LRRK relevance.** Sense-Move-Act at sea: still pre-operational.

**Confidence.** High on continuity.

## Forward indicators

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

1. First Reaper weapons employment (US or UK).
2. Athens MTCR plenary, 7–9 November.
3. Unmanned Systems Roadmap 2007 issuance.
4. Sky Warrior Block 0 / Afghanistan notices.
5. ACC Reaper IOC declaration.

> **Collection integrity.** Fetched: AF Historical Foundation; GA 8 November UK Reaper reprint (used for October arrival and 31 October ISD); GAO-09-175. The 11 October af.mil HTML was blocked; indexed sentences graded B1. Refused: later fact-sheet “IOC October 2007” applied as if an October ACC memorandum had been fetched—it was not.

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