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

ScanEagle goes to war with I MEF this month as a contractor ISR service, and Hurricane Charley pulls CRASAR into a domestic disaster tasking that is still a test, not a confirmed rescue-UAV first. The access change is dual: a commercial fishing-spotter airframe over Anbar, and a university robot team on a Florida storm — both outside programs of record.

### Key judgments

1. **[Assessment — high confidence]** Boeing (28 February 2006): ScanEagle deployed with I MEF in August 2004.
2. **[Assessment — moderate confidence]** USF/CRASAR (7–8 September 2005 release) states CRASAR “has been focusing on developing and testing small UAVs since being called up by Florida Task Force 3 during Hurricane Charley in 2004.” That is a 2005 recap of a 2004 call-up; it does not, in the fetched text, claim a completed Charley UAV rescue sortie.
3. **[Inference — moderate confidence]** Domestic disaster UAV use is now a live FAA/COA problem, the same problem OSD named in March.

### 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. ScanEagle with I MEF — first month in Iraq

*Event / publication dates: August 2004 deployment (Boeing 28 February 2006).*

**Verified record — [Fact — A1]** “Since being deployed with the First Marine Expeditionary Force in August 2004, ScanEagle has completed 8,900 combat flight hours in Iraq” (that hour total is a February 2006 figure, not an August 2004 figure). July 2004 contract for two MDUs. Four-foot UAV used as a forward observer for enemy concentrations, vehicle and personnel movement, buildings and terrain. Source: https://boeing.mediaroom.com/2006-02-28-Boeing-ScanEagle-UAV-Surpasses-10-000-Combat-Flight-Hours

**Threat landscape.** Persistent low-altitude stare under Marine tactical control, flown by a Boeing/Insitu team. Airspace deconfliction with Pioneer, Dragon Eye, and helicopters is now a Marine problem in the same month the bird arrives.

**Intelligence assessment.** [Assessment — high confidence] August 2004 is the deployment month. [Uncertainty] August hours are not separately published. [Inference — moderate confidence] Range-extension “operational concepts” Boeing later says tripled range are not yet a public August fact.

**Opportunity.** I MEF August ISR summaries.

**LRRK relevance.** Watch / Control Fabric. First month of a COCO orbit over Marines.

**Confidence.** High on month; low on August hours (8,900 is a 2006 cumulative).

## 02. Hurricane Charley: CRASAR called up — test, not a claimed first rescue flight

*Event / publication dates: Hurricane Charley makes Florida landfall 13 August 2004; CRASAR call-up recited 7 September 2005.*

**Verified record — [Fact — B2]** University of South Florida / ScienceDaily, 8 September 2005: “CRASAR has been focusing on developing and testing small UAVs since being called up by Florida Task Force 3 during Hurricane Charley in 2004.” Robin Murphy: “We learned that seeing whether people were trapped on their roofs just beyond sight along a flooded road was critical.” The same release calls Katrina (2005) “the first known use of small UAVs for an actual disaster.” Source: https://www.sciencedaily.com/releases/2005/09/050908081119.htm

**Threat landscape.** A domestic UAV over wreckage hits FAA COA, radio failure, and the absence of a see-and-avoid rule — the 7610.4 problem Lamartin named in March.

**Intelligence assessment.** [Assessment — high confidence] CRASAR was called up for Charley. [Uncertainty] The fetched 2005 text does not prove a completed Charley UAV sortie; it says “developing and testing” since that call-up. [Inference — moderate confidence] Charley taught the roof-beyond-the-flooded-road requirement that Katrina will fly.

**Opportunity.** Florida TF-3 after-action; do not upgrade Charley to “first disaster UAV” against CRASAR’s own later wording.

**LRRK relevance.** Watch / Lab. Domestic sense-move-act under emergency law.

**Confidence.** High on call-up; low on flight logs.

## 03. Ground-act continues: EOD robots, not SWORDS, in Iraq

*Event / publication dates: continuing post-Avon Park.*

**Verified record — [Fact — B1]** July Avon Park was a demo. No August 2004 SWORDS deployment notice exists in fetched sources. TALON/PackBot EOD remains the fielded ground-act layer. Source: https://www.globalsecurity.org/military/systems/ground/talon.htm

**Threat landscape.** IED tempo in Iraq is the demand signal. Proprietary OCUs remain the control-fabric debt.

**Intelligence assessment.** [Assessment — high confidence] EOD robots stay; armed UGV does not ship this month.

**Opportunity.** CENTCOM EOD monthly stats (if released).

**LRRK relevance.** Kestrel.

**Confidence.** High.

## 04. MQ-9 / Predator B: still SDD, fifth airframe just completed

*Event / publication dates: fifth completed June 2004; no August fielding.*

**Verified record — [Fact — A1]** Development continues. No August 2004 ASC IOC or combat-deployment notice on the fetched program page. Source: https://www.globalsecurity.org/military/systems/aircraft/mq-9-program.htm

**Threat landscape.** Analytic error risk: calling Predator B operational because five exist.

**Intelligence assessment.** [Assessment — high confidence] Not IOC.

**Opportunity.** SDD flight-test notices.

**LRRK relevance.** Watch.

**Confidence.** High.

## 05. Pioneer sustainment vs ScanEagle insertion — two Marine ISR models

*Event / publication dates: Pioneer sustain-through-2010 (March testimony); ScanEagle arrives August.*

**Verified record — [Fact — A1]** Marines now have a 1986-era organic UAV (Pioneer) and a 2004 contractor service (ScanEagle) in the same theater. Source pairing: http://www.globalsecurity.org/military/library/congress/2004_hr/04-03-17lamartin.htm ; https://boeing.mediaroom.com/2006-02-28-Boeing-ScanEagle-UAV-Surpasses-10-000-Combat-Flight-Hours

**Threat landscape.** Two control systems, two frequency plans, two maintenance cultures. Interoperability is not the purchase order.

**Intelligence assessment.** [Assessment — high confidence] Dual stack is now real. [Inference — moderate confidence] ScanEagle will eat Pioneer’s persistent-stare mission before Pioneer’s 2010 sunset.

**Opportunity.** Compare Pioneer vs ScanEagle tasking in I MEF August FRAGOs.

**LRRK relevance.** Control Fabric / Passport.

**Confidence.** High on coexistence; moderate on the substitution path.

## Forward indicators

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

1. QinetiQ–Foster-Miller announcement (September).
2. Shadow 10,000-hour mark (mid-August, reported September).
3. Second Fallujah planning ISR.
4. Hezbollah UAV.
5. Navy UUV master-plan completion (late 2004).

> **Collection integrity.** Charley is filed as a call-up and test origin, not as the first disaster UAV flight — CRASAR’s own 2005 wording reserved that claim for Katrina. ScanEagle August hours were not invented from the 2006 cumulative.

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