# Kinematic Threat Brief

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

| Field | Value |
| --- | --- |
| Collection cutoff | 30 June 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

The 17–18 June killing of Nek Mohammed in South Waziristan is the first time the public record in Pakistan has to wrestle with an unmanned-aircraft rumor — and the official line is a Pakistani helicopter and a spokesman calling local UAV reports “absurd.” The access change is not a confirmed CIA orbit. It is that remote-strike attribution has entered the tribal-area information space, while the fifth Predator B is completed as a factory fact.

### Key judgments

1. **[Assessment — high confidence]** Associated Press, 18 June 2004: Pakistani army says its helicopters killed Nek Mohammed; Maj. Gen. Shaukat Sultan calls local reports of an unmanned U.S. aircraft “absurd”; AP itself notes U.S. involvement is unclear and that Pakistan “sometimes receives technical help.”
2. **[Assessment — high confidence]** Later reconstructions (2013 NYT, 2014 TBIJ) call this the first CIA Predator strike in Pakistan. Those are post-cutoff sources and are not facts of June 2004.
3. **[Inference — moderate confidence]** A Watch desk in June 2004 should have logged a contested unmanned-attribution event, not a confirmed Predator campaign.

### 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. Nek Mohammed: official helicopter, local UAV rumor, U.S. role unclear

*Event / publication dates: strike late 17 June 2004; AP file 18 June 2004.*

**Verified record — [Fact — A1]** AP via NBC News, 18 June 2004, 11:42 AM EDT: Pakistani forces killed renegade tribal leader Nek Mohammed in a helicopter assault on a mud-brick fortress near the Afghan border. Six others killed. Maj. Gen. Shaukat Sultan: “We were tracking him down and he was killed last night by our hand.” A senior security official, anonymous, said he was tracked by an intercepted satellite phone. BBC had conducted at least two phone interviews with Mohammed in the past week. Sultan would not confirm the phone-trace method. AP: “It was not clear if the United States was involved.” Pakistan “is thought to lack the sophisticated satellite technology necessary for such phone intercepts and acknowledges that it sometimes receives ‘technical help’ from the Americans.” Sultan said local reports that an unmanned U.S. aircraft may have fired the missile were “absurd.” Funeral in Kaloosha 18 June. Source fetched: https://www.nbcnews.com/id/wbna5239580

**Threat landscape.** Whoever fired, the new public fact is that a militant leader talking on a satellite phone can be killed at dinner in South Waziristan, and that locals already have a vocabulary for “unmanned U.S. aircraft.”

**Intelligence assessment.** [Fact — A1] Pakistani official attribution is helicopter. [Fact — A1] Official denial of UAV. [Uncertainty] Weapon, platform, and U.S. role are unresolved in June 2004 open sources. [Inference — moderate confidence] The satellite-phone intercept plus “technical help” language is the collection clue a Watch desk would have circled.

**Opportunity.** Capture Pakistani press, BBC Pashto, and any CENTCOM denial on the same day. Do not wait for 2013 histories.

**LRRK relevance.** Watch / Passport. This is a contested remote-strike card. A Passport would have recorded “official: helicopter; local: UAV; U.S.: unconfirmed,” and forbidden a clean “first Predator in Pakistan” label in June 2004.

**Confidence.** High on the AP text; high that UAV is not confirmed this month; later-memory confirmation is out of scope.

## 02. Fifth Predator B completed — still not a combat orbit

*Event / publication dates: June 2004 (GlobalSecurity MQ-9 chronology).*

**Verified record — [Fact — B1]** “The fifth Predator B was completed in June 2004 and a sharp increase in output was expected afterwards. The configuration has a length of 36 feet and a wingspan of 68 feet.” Milestone B was February 2004. Source: https://www.globalsecurity.org/military/systems/aircraft/mq-9-program.htm

**Threat landscape.** Factory output is not IOC. The trust issue remains data rights and stores-management maturity (GAO will later say the fourth critical technology was not mature in 2004).

**Intelligence assessment.** [Assessment — high confidence] Five airframes exist as a production fact. [Inference — moderate confidence] Output increase will collide with SDD incompleteness. [Uncertainty] Which of the five is USAF vs NASA/Altair vs company-owned is not broken out in the fetched sentence.

**Opportunity.** ASC production logs.

**LRRK relevance.** Watch. Development, not fielding.

**Confidence.** High on “fifth completed in June 2004” as stated on the fetched chronology; moderate that the chronology correctly reflects an ASC fact.

## 03. Raven and small UAS: the battalion eye stays on after Fallujah I

*Event / publication dates: continuing 185-system buy (testified 17 March).*

**Verified record — [Fact — A1]** The 185-system Raven COTS buy and five-systems-per-deployed-battalion issue plan remain the last official public fielding facts. DID later records commanders finding IEDs on first Raven missions; those anecdotes are not dated to June 2004 and are not used as June facts. Source: http://www.globalsecurity.org/military/library/congress/2004_hr/04-03-17lamartin.htm

**Threat landscape.** Small electric UAS vs IED emplacers. Jammer fratricide is an emerging, still poorly documented, failure mode.

**Intelligence assessment.** [Assessment — high confidence] Raven remains the Army small-UAS solution of record this month. [Uncertainty] June issue quantities unpublished.

**Opportunity.** Battalion after-action on Raven vs IED.

**LRRK relevance.** Watch / Sense-Move-Act.

**Confidence.** High on the buy; low on June anecdotes.

## 04. EOD ground robots: 2004 is the year CENTCOM’s small-robot requirement is met

*Event / publication dates: continuing; 2005 Navy recap attributes the CENTCOM fill to “last year” (2004).*

**Verified record — [Fact — B1]** Navy NewsStand 22 June 2005: “Last year, the EOD Program Office successfully met the U.S. Central Command’s (USCENTCOM) requirements for small robotic systems to defeat the burgeoning IED threat in Afghanistan and Iraq.” That sentence, published a year later, is the closest official public statement that 2004 — including this mid-year — was the surge year. MTRS FRP is still eleven months away. Source: https://www.globalsecurity.org/military/library/news/2005/06/mil-050622-nns02.htm

**Threat landscape.** COTS robots, proprietary OCUs, no JAUS yet required. Interoperability is being sacrificed to get a gripper downrange.

**Intelligence assessment.** [Assessment — moderate confidence] Mid-2004 is inside the CENTCOM fill year. [Uncertainty] June 2004 on-hand numbers unpublished.

**Opportunity.** CENTCOM urgent-requirement messages.

**LRRK relevance.** Kestrel / Control Fabric. The OCU zoo is the long-term cost of this year’s speed.

**Confidence.** Moderate (2005 recap of 2004); not a June 2004 press release.

## 05. Undersea and policy: no public unmanned attribution doctrine for third countries

*Event / publication dates: 18 June AP file is also a policy signal.*

**Verified record — [Fact — A1]** The AP file shows a U.S. partner officially denying unmanned U.S. aircraft while acknowledging “technical help.” CRS RL31872 (2003) already listed technology proliferation as a congressional consideration. No June 2004 U.S. policy statement on UAV strikes in Pakistan was fetched — because none was issued. Sources: https://www.nbcnews.com/id/wbna5239580 ; https://www.everycrsreport.com/files/20030425_RL31872_089a1bc2a3f353e69de4557e6614bc453e2049b2.html

**Threat landscape.** Attribution opacity is now part of the weapon. A Watch desk that waits for an official U.S. UAV confirmation will miss the campaign’s start.

**Intelligence assessment.** [Assessment — high confidence] There is no U.S. public UAV-in-Pakistan policy this month. [Inference — moderate confidence] Partner-credited strikes with U.S. technical help will be the pattern if a campaign exists.

**Opportunity.** Parallel collection of Pakistani English and Urdu sources whenever a missile is reported in FATA.

**LRRK relevance.** Campaign / Watch. Political economy of remote strike: whose flag is on the shot.

**Confidence.** High on the absence of a U.S. public claim.

## Forward indicators

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

1. Any further Waziristan missiles and whether “unmanned” reappears in local reporting.
2. ScanEagle Marine contract (July).
3. Avon Park armed-TALON demo (14–17 July).
4. MQ-9 SDD contract actions.
5. Hurricane-season UAV experiments (Charley is in August).

> **Collection integrity.** June 2004 AP is the primary. 2013 NYT “secret deal” and 2014 TBIJ “first CIA strike” reconstructions were read in research and **refused** as June 2004 facts. They may be used in later-year briefs only as later memory, and even then only labeled as such. No Hellfire, no “Predator campaign begins” claim is made this month.

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