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

March is the month the hunter-killer airframe physically arrives in the Nevada remote-split pipeline and the Joint Staff issues a UAS concept of operations—capability is moving from experiment toward a wing, while Iraq surge demand is already running ahead of published joint tasking.

### Key judgments

1. **[Assessment — high confidence]** Air Force public affairs later records that the first MQ-9 Reaper arrived at Creech AFB on 13 March 2007 after California test work, with training flights planned to begin 19 March—the first public beddown of the Reaper as an attack-squadron aircraft.
2. **[Assessment — high confidence]** GAO-07-836 records that DOD issued a Joint Concept of Operations for Unmanned Aircraft Systems in March 2007, the first joint operational paper of that title.
3. **[Inference — moderate confidence]** Remote-split operations (launch/recover forward, fly from Nevada) will become the C2 pattern for Reaper as they already are for Predator; the trust boundary is the satellite link and the crew pipeline, not the airframe.

### 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. First MQ-9 Reaper lands at Creech — hunter-killer enters the training line

*Event / publication dates: 13 March 2007 arrival (Air Force public affairs, later article); training planned from 19 March.*

**Verified record — [Fact — B1]** Air Force News later reported that the MQ-9 Reaper arrived 13 March at Creech AFB, Nevada, after initial testing in California, flown by Lt. Col. Jon Greene, 42nd Attack Squadron commander, with sensor operator Senior Airman Aaron Aguilar. Greene said the mission was to train MQ-9 crews and “fly combat by this summer.” Capt. Michael Lewis stated the Reaper can carry one and a half tons of ordnance, including Hellfire and GBU-12. The 42nd ATKS was to fall under the 432nd Wing by 1 May. The live af.mil article was blocked on fetch this filing; the dated facts above are taken from the Air Force News display as indexed in open search and are treated as B1 pending a recovered HTML copy.

**Threat landscape.** A larger, faster, bomb-capable unmanned aircraft is now on a U.S. training flightline. The physical change is payload and persistence, not a new C2 architecture—the same remote-split pattern as Predator.

**Intelligence assessment.** [Assessment — high confidence] Reaper is in the training pipeline, not yet in combat this month. [Inference — moderate confidence] “Combat by this summer” is a commander’s public target, not an IOC declaration. [Uncertainty] Public record this month does not state how many Reapers exist beyond the first Creech aircraft.

**Opportunity.** A 42nd ATKS press availability or a recovered af.mil HTML would lock airframe count and first-flight dates.

**LRRK relevance.** Watch: record 13 March as the Reaper’s first public home-station date. Control Fabric: same GCS family, heavier weapons, same satellite trust boundary.

**Confidence.** High on the 13 March arrival as Air Force-attributed; moderate until the original HTML is recovered; low on unpublished inventory.

## 02. Joint UAS CONOPS issued — paper tries to catch the fleet

*Event / publication dates: March 2007 (GAO-07-836).*

**Verified record — [Fact — A1]** GAO-07-836, issued 11 July 2007, states: “in March 2007 DOD issued its Joint Concept of Operations for Unmanned Aircraft Systems, which provides overarching principles, a discussion of UAS capabilities, operational views, and a discussion of UAS use in various operational scenarios.” The same report notes Multi-Service TTPs dated August 2006. https://www.globalsecurity.org/intell/library/reports/gao/d07836.pdf

**Threat landscape.** Joint paper now exists; joint tasking and bandwidth do not automatically follow. CENTCOM still lacks a DOD-wide advance-coordination rule for incoming ISR airframes.

**Intelligence assessment.** [Assessment — high confidence] A Joint CONOPS is now an issued document. [Inference — moderate confidence] It will not give JFACC visibility into unit-owned tactical UAS. [Uncertainty] The CONOPS text itself was not fetched this filing.

**Opportunity.** Retrieve the March 2007 Joint CONOPS PDF from DTIC or Joint Staff.

**LRRK relevance.** Control Fabric: first joint operational doctrine for UAS. Passport: note that doctrine and inventory are still on different clocks.

**Confidence.** High that the CONOPS was issued in March (GAO A1); low on its unpublished contents.

## 03. Surge demand versus February inventory — GAO’s later snapshot

*Event / publication dates: GAO cites “as of February 2007” inventory; report issued 11 July 2007.*

**Verified record — [Fact — A1]** GAO-07-836: “As of February 2007, DOD had more than 3,900 unmanned aircraft in its inventory compared to fewer than 50 in 2000. The majority of these aircraft are currently being used in support of ongoing operations in Iraq and Afghanistan.” UAS funding: $363 million FY2001 to $2.23 billion FY2007; $2.54 billion requested for FY2008. https://www.globalsecurity.org/intell/library/reports/gao/d07836.pdf

**Threat landscape.** Inventory growth is real and mostly theater-committed. The binding constraint GAO names is not airframes alone but allocation visibility, bandwidth, and the lack of advance coordination.

**Intelligence assessment.** [Assessment — high confidence] The fleet is already large and mostly at war. [Inference — moderate confidence] Reaper’s arrival does not relieve the small-UAS and Shadow/Hunter tasking fight. [Uncertainty] The 3,900 figure is a February snapshot published in July; March increment is unpublished.

**Opportunity.** Service-level March inventory tables.

**LRRK relevance.** Watch: the number that matters is not “how many UAS exist” but “who can see all of them on one tasking picture.”

**Confidence.** High on GAO’s February figure; moderate applying it as a March floor.

## 04. ER/MP and Warrior-Alpha — Army persistence still a patchwork

*Event / publication dates: 10 August 2005 SDD award; GAO-07-836 discusses Warrior Alpha coordination with CENTCOM as a 2006–2007 case.*

**Verified record — [Fact — A1]** ER/MP SDD remains the 2005 Team Warrior contract (17 aircraft, seven GCS, mid-2009). https://www.ga-asi.com/general-atomics-aeronautical-systems-and-its-team-warrior-partners-awarded-major-u-s-army-contract GAO-07-836 uses Warrior Alpha (JIEDDO-fielded, Army-operated IED hunt) as the example of why CENTCOM demanded 30-day advance notice: bandwidth and ramp space forced an alternate beddown. https://www.globalsecurity.org/intell/library/reports/gao/d07836.pdf

**Threat landscape.** Army persistence in Iraq is a mix of Shadow/Hunter, contractor I-GNAT/Warrior-Alpha, and borrowed Predators—not ER/MP Block 1.

**Intelligence assessment.** [Assessment — high confidence] Block 1 is still SDD. [Inference — moderate confidence] Warrior Alpha-class quick-reaction airframes will keep filling the gap through 2007–2008. [Uncertainty] March 2007 Warrior Alpha orbit count is unpublished.

**Opportunity.** JIEDDO or Army Aviation March posture statement.

**LRRK relevance.** Kestrel/Lab: the Army is buying persistence three ways at once. Passport: record which variant is actually in theater.

**Confidence.** High on SDD status and on GAO’s Warrior Alpha coordination story; low on March orbits.

## 05. Export-control quiet — Category I still the HALE brake

*Event / publication dates: standing MTCR; no March plenary.*

**Verified record — [Fact — B1]** No March 2007 MTCR plenary or EAR UAV amendment was fetched. Category I thresholds remain the public constraint on Global Hawk-class transfers.

**Threat landscape.** Coalition HALE ISR remains politically gated.

**Intelligence assessment.** [Assessment — high confidence] No public change. [Inference — moderate confidence] ROK/Global Hawk tension will surface in May press. [Uncertainty] March license actions unpublished.

**Opportunity.** Commerce/State March notices.

**LRRK relevance.** Passport: no change to the access control.

**Confidence.** High on continuity; low on unpublished licenses.

## Forward indicators

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

1. 1 May 432nd Wing activation (already flagged in the Creech Reaper story).
2. First public Reaper combat or IOC declaration.
3. Joint CONOPS text and whether it names a single tasking authority.
4. Army quick-reaction Warrior/ERMP Iraq notice.
5. Hydroid REMUS sustainment or HUGIN export awards.

> **Collection integrity.** Used: GAO-07-836 (Joint CONOPS date, February inventory, Warrior Alpha); 2005 ER/MP award; White House January text as background. The 13 March Creech arrival is Air Force-attributed but the live af.mil HTML was access-denied this filing—graded B1, not A1. Refused: later “Reaper IOC October” fact-sheet language applied backward as a March event; any invented airframe count beyond what Air Force News stated.

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