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

Katrina makes landfall 29 August. CRASAR leaves Tampa 30 August for New Orleans, turns around short of the city, and will fly Mississippi in the first days of September. The access change is domestic: a university robot team is now a disaster ISR node, and the FAA COA problem OSD named in 2004 is no longer theoretical.

### Key judgments

1. **[Assessment — high confidence]** USF/ScienceDaily 8 September 2005: CRASAR deployed 30 August from Tampa at LSU FETI request; destroyed/flooded freeways forced a turnaround short of New Orleans city limits.
2. **[Assessment — high confidence]** Katrina landfall 29 August 2005 is the meteorological fact; UAV sorties over Pearlington are a 1–early-September event and will be filed next month.
3. **[Inference — moderate confidence]** Charley 2004 was the test call-up; Katrina is about to become the first claimed “actual disaster” small-UAV use — CRASAR’s own wording.

### 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. 30 August: CRASAR rolls toward New Orleans and is stopped

*Event / publication dates: deploy 30 August 2005; recounted 7–8 September 2005.*

**Verified record — [Fact — A1]** ScienceDaily 8 September 2005 (USF, dated 7 September): at LSU Fire Emergency Training Institute request, CRASAR deployed 30 August from Tampa to assist rescue just east of the French Quarter. “Because of destroyed or flooded freeways, and lack of secure surface roads, the team had to turn around just short of the city limits,” Robin Murphy. Source: https://www.sciencedaily.com/releases/2005/09/050908081119.htm

**Threat landscape.** The first Katrina unmanned mission fails on logistics, not on the air vehicle. Ground access is the trust boundary for a “portable” UAV team.

**Intelligence assessment.** [Assessment — high confidence] 30 August movement and turnaround are on the record. [Inference — moderate confidence] That failure drives the Mississippi retask.

**Opportunity.** TF-3 / FETI logs.

**LRRK relevance.** Watch / Sense-Move-Act. Domestic deployment, not combat.

**Confidence.** High.

## 02. ScanEagle: first full Navy month plus Marine continuation

*Event / publication dates: Navy since July 2005.*

**Verified record — [Fact — A1]** Continuing. $13M mod is September. Source: https://boeing.mediaroom.com/2006-02-28-Boeing-ScanEagle-UAV-Surpasses-10-000-Combat-Flight-Hours

**Threat landscape.** Gulf oil-platform stare during a U.S. Gulf hurricane is an unasked question in the fetched Boeing text.

**Intelligence assessment.** [Uncertainty] Whether ScanEagle Navy ops were affected by Katrina is unpublished.

**Opportunity.** ESG August/September.

**LRRK relevance.** Watch.

**Confidence.** High on continuation; low on Katrina interaction.

## 03. MTRS / EOD robots: wartime production, not a Katrina tool in fetched sources

*Event / publication dates: FRP in force; no August Katrina PackBot/TALON primary fetched.*

**Verified record — [Fact — B2]** No fetched August 2005 story puts MTRS robots on the Gulf Coast. CRASAR’s own history cites WTC 2001 for small ground robots and Charley 2004 for UAV testing. Source: https://www.sciencedaily.com/releases/2005/09/050908081119.htm

**Threat landscape.** Ground robots for disaster remain a CRASAR competence, separately from MTRS.

**Intelligence assessment.** [Assessment — moderate confidence] Katrina’s unmanned story this week is air, not MTRS.

**Opportunity.** Do not invent a PackBot-in-New-Orleans August fact.

**LRRK relevance.** Collection integrity.

**Confidence.** Moderate.

## 04. MQ-9 still SDD

*Event / publication dates: continuing.*

**Verified record — [Fact — A1]** No August 2005 IOC. Source: https://www.globalsecurity.org/military/systems/aircraft/mq-9-program.htm

**Threat landscape.** Unchanged.

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

**Opportunity.** SMS.

**LRRK relevance.** Watch.

**Confidence.** High.

## 05. Policy: FAA COA is now a disaster-response control

*Event / publication dates: Lamartin March 2004 FAA 7610.4 goal; Katrina is the test case.*

**Verified record — [Fact — B2]** Lamartin named file-and-fly as a top operational goal. CRASAR’s Katrina flights (next month) will occur under whatever COA they held. No August 2005 FAA Katrina UAV order was fetched. Source: http://www.globalsecurity.org/military/library/congress/2004_hr/04-03-17lamartin.htm

**Threat landscape.** Domestic UAV without a standing rule.

**Intelligence assessment.** [Assessment — moderate confidence] COA remains the gate.

**Opportunity.** FAA COA file for CRASAR/SSRRC.

**LRRK relevance.** Control Fabric.

**Confidence.** Moderate.

## Forward indicators

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

1. Pearlington / Bay St. Louis UAV flights (1–early September).
2. ScanEagle $13M mod (September).
3. LMRS Oklahoma City (September).
4. iRobot S-1 (30 September).
5. Whether any federal Predator flies Katrina (later claims exist; require a dated primary).

> **Collection integrity.** 30 August movement is A1 from the fetched USF release. Katrina UAV sorties are not back-dated into August. Later “Predator after Katrina” claims in tertiary papers were not used.

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