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 | 30 June 2001 |
| 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

June closed the Phase II Hellfire window with mixed results, put a five-pound Dragon Eye into the hands of 3rd Battalion, 5th Marines at Kernel Blitz, and locked in the Counterterrorist Center’s preference to wait for an armed Predator rather than burn the summer weather window on unarmed ISR.

### Key judgments

1. **[Assessment — high confidence]** Kernel Blitz in June 2001 was the first operating-force familiarization with Dragon Eye — tactics, techniques, procedures, and DOTMLPF issues for a backpack UAV.
2. **[Assessment — high confidence]** Phase II shots through 7 June left fuzing and high-altitude launch performance unresolved; Flight International would later quote General Atomics that testing was “a mixed bag.”
3. **[Inference — moderate confidence]** The decision to withhold a summer unarmed redeployment traded a second Tarnak-Farms-style sighting for secrecy and host-nation patience — a choice that would look different after 11 September.

### 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. Kernel Blitz — Dragon Eye with 3/5 Marines

*Event / publication dates: June 2001, Kernel Blitz Experiment*

**Verified record — [Fact — A1]** The JFCOM Dragon Eye concept page (archive.org snapshot opened) states: “Initial experimentation occurred during the Kernel Blitz Experiment with 3rd Battalion, 5th Marines in June 2001, providing operating forces an early opportunity to gain familiarization with the small UAV concept; develop tactics, techniques and procedures; and identify potential doctrine, organization and training issues.” The air vehicle is battery-operated, fully autonomous after hand- or bungee launch, 45-inch wingspan, about five pounds, GPS waypoints, in-flight reprogrammable, color/low-light/IR video to 10 km LOS, 35 knots, one-hour endurance; GCS about 12 pounds. FY01 R&D $3 million. Source opened: https://web.archive.org/web/20041017053912/http://www.jfcom.mil/about/experiments/mc02/concepts/drageye.htm

**Threat landscape.** A rifle-company commander who can see over the next hill without a request to a UAV squadron changes the infantry fight. The trust boundary is a wireless modem and a one-hour battery.

**Intelligence assessment.** [Assessment — high confidence] June 2001 is the documented first troop experiment. [Inference — moderate confidence] DOTMLPF findings from Kernel Blitz will drive the June–July 2002 operator evaluations. [Uncertainty] Kernel Blitz after-action scores were not fetched.

**Opportunity.** Lost-link behavior, EW susceptibility, and whether imagery was recorded or only streamed should have been Kestrel fields.

**LRRK relevance.** Kestrel / Lab. First time a Marine battalion, not a lab, flew the small UAS stack.

**Confidence.** High on unit, month, and program description; low on unpublished TTPs.

## 02. Phase II window closes 7 June — mixed bag, 16 launches by late summer

*Event / publication dates: tests through 7 June 2001; later Flight International count of 16 launches 2,000–15,000 feet*

**Verified record — [Fact — B1]** CIA “Plan” compilation: tests 22 May–7 June, accuracy excellent, fusing questions unresolved on 11 September. Flight International 21 August 2001: late May and early June high-altitude stationary shots including a success from 5,000 feet; Christopher Dusseault, GA-ASI programme manager, declined to say how many missiles or from what altitude but said testing was “a mixed bag. We hit some, but missed some”; Brig. Gen. Henry Obering said there had been 16 Predator/Hellfire launches from 2,000 to 15,000 feet and that USAF wanted more Predators modified for weapons testing; “the jury is still out” on launching the 50 kg missile from 15,000 feet. Sources opened: https://globalsecurity.org/intell/ops/the-plan-predator.htm and https://www.flightglobal.com/fixed-wing/2001/08/armed-predator-gives-mixed-results/

**Threat landscape.** Sixteen test shots without a closed high-altitude envelope means the wartime shooter, if deployed, would be improvising.

**Intelligence assessment.** [Assessment — high confidence] By 30 June Phase II had flown and not closed. [Inference — moderate confidence] Obering’s request for more modified airframes is an industrial signal. [Uncertainty] The “16” figure is an August quote, not a 30 June scoreboard.

**Opportunity.** Shot log (altitude, fuse, hit/miss, MTS tracker behavior) is the single most useful missing primary.

**LRRK relevance.** Lab / Kestrel. Record the residual: fuse and 15,000-foot launch.

**Confidence.** High that the window closed in early June; moderate on the August totals applying backward; low on unpublished misses.

## 03. Wait-for-armed vs. fly-unarmed — CTC preference recorded

*Event / publication dates: summer 2001 interagency debate (CIA “Plan” compilation)*

**Verified record — [Fact — B1]** The compilation states that one issue occupying discussion was whether to deploy Predator early in the summer of 2001 in a purely reconnaissance mode to take advantage of good weather, or wait until the armed capability was ready and policy/legal questions resolved. The Counterterrorist Center argued for the latter: the 2000 experience showed that even a Bin Ladin sighting lacked a timely response; continued reconnaissance would undercut later armed operations because the Taliban would detect flights (as in 2000) and alert al-Qa’ida; reconnaissance would expose Predator to interception or anti-aircraft fire; and the host country was unlikely to tolerate extensive operations once the Taliban learned of its assistance. Source opened: https://globalsecurity.org/intell/ops/the-plan-predator.htm

**Threat landscape.** This is a collection-vs-action trade. The physical consequence of waiting is an empty summer sky over Tarnak Farms.

**Intelligence assessment.** [Assessment — moderate-high confidence] By the end of June the CTC argument was the institutional favorite, even if no final order is public this month. [Inference — moderate confidence] Host-nation politics, not just weather, was a veto. [Uncertainty] Whether DOD dissented in writing was not fetched.

**Opportunity.** The written CTC memo and any NSC tasker should have been the Campaign Passport.

**LRRK relevance.** Campaign / Watch. A June 2001 desk would have logged a negative: no second Afghan Eyes season this summer.

**Confidence.** Moderate-high on the later official description of the debate; low on the exact June decision date.

## 04. Oceans 2001 community — REMUS and BPAUV papers in the same forum

*Event / publication dates: 2001 Oceans conference papers (von Alt REMUS; Rish/Willcox BPAUV)*

**Verified record — [Fact — B1]** Two opened IEEE abstracts from the 2001 Oceans cycle document the U.S. undersea industrial pair: WHOI/REMUS as a complete minefield/hydrographic reconnaissance system with MEDAL compatibility in fleet battle experiments (von Alt, Allen, Austin, Stokey); Bluefin BPAUV as an ONR-sponsored shallow-water surveyor with Klein 5000 sidescan (Rish, Willcox, Grieve, Montieth, Vaganay). Sources opened: https://doi.org/10.1109/oceans.2001.968686 and https://doi.org/10.1109/oceans.2001.968688

**Threat landscape.** The scientific literature is itself a transfer path: sidescan techniques, navigation accuracy, and operator-interface lessons are now in the open engineering record.

**Intelligence assessment.** [Assessment — high confidence] Both vehicle classes were mature enough to publish operational-testing results in 2001. [Inference — moderate confidence] Allied navies reading these papers are a future export market — and a future copy risk. [Uncertainty] Conference date vs. journal posting was not independently calendared beyond the 2001 volume.

**Opportunity.** Author affiliation lists (WHOI, Bluefin, NSWC-CSS, ONR) are the supply-chain map.

**LRRK relevance.** Lab / Supply. Undersea sense-move-act is not a 2003 invention.

**Confidence.** High on paper existence and technical claims in the abstracts; moderate on June as the community’s “publication season.”

## 05. Predator B already in flight test — turboprop, more pylons

*Event / publication dates: Flight International August 2001: “the larger Predator B, which is in flight test”*

**Verified record — [Fact — B2]** Flight International’s 21 August piece, reporting on the spring/summer test season, states the larger Predator B, in flight test, is powered by the Honeywell TPE331 turboprop and “could carry up to 16 Hellfire missiles,” versus two AGM-114s on the RQ-1A. CRS later records that in 2001 the Air Force purchased two Predator B (MQ-9) UAVs for testing. Sources opened: https://www.flightglobal.com/fixed-wing/2001/08/armed-predator-gives-mixed-results/ and https://www.everycrsreport.com/files/20030425_RL31872_089a1bc2a3f353e69de4557e6614bc453e2049b2.html

**Threat landscape.** A turboprop hunter-killer with a larger payload is a different export and legal object than a two-missile ACTD.

**Intelligence assessment.** [Assessment — moderate confidence] By mid-2001 Predator B was flying, even if the August article is the opened public mention. [Inference — moderate confidence] Sixteen Hellfires is a contractor claim, not a certified load. [Uncertainty] First-flight day in 2001 was not fetched as a primary.

**Opportunity.** Engine ITAR classification (TPE331) and pylon structural limits should have been Lab fields.

**LRRK relevance.** Supply / Campaign. The Reaper lineage is already a 2001 flight-test fact.

**Confidence.** Moderate on “in flight test” as of the summer reporting; low on a June first-flight claim not made here.

## Forward indicators

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

1. July Dragon Eye preproduction awards (later reported to BAI and AeroVironment).
2. Written NSC/CIA decision on armed deployment remaining recon-only.
3. Phase II resumption against moving targets when the range reopened.
4. Host-nation position on weapons-capable aircraft.
5. UOES REMUS first overseas exercise report.

> **Collection integrity.** Kernel Blitz date is from a contemporaneous JFCOM program page preserved on archive.org. Phase II close and CTC wait-for-armed argument are from the later CIA-plan compilation, cross-checked with August Flight International. Predator B “in flight test” is an August article used cautiously for a June cutoff. No Arabic or Hebrew Kernel Blitz coverage was opened.

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