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 January 2002 |
| 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

January opened with a HALE gap: Global Hawk AV-5 was wreckage in the UAE desert, AV-3 was grounded, and the public argument was whether an ACTD crash would kill the program — while Predator kept flying, and losing, in the Afghan winter, and the Army’s Hunter was not yet the CENTCOM story it would become a year later.

### Key judgments

1. **[Assessment — high confidence]** Contemporaneous 1–8 January reporting treated the 30 December Global Hawk loss as a setback for a two-ship theater fleet, not as a reason to cancel the type.
2. **[Assessment — moderate confidence]** Predator winter attrition (icing, lost SATCOM link) was already a known operational limitation entering 2002, even if month-by-month loss tallies were not published this January.
3. **[Inference — moderate confidence]** Commanders who had used AV-5 for Tora Bora spot-mode would spend the next quarter without a HALE replacement.

### 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. Global Hawk crash aftermath — investigation, grounding, “probably not” programmatic

*Event / publication dates: crash 30 December 2001; LAT 1 January 2002; Aerospace Daily 8 January 2002*

**Verified record — [Fact — A1]** Los Angeles Times, 1 January 2002: RQ-4A crashed Sunday on a routine flight; rushed to theater in November; one of two in theater lost; several Predators also crashed in Afghanistan and Iraq since the war began. Aerospace Daily / GlobalSecurity, 8 January: Dec. 30 crash should not adversely affect the program, John Pike said “probably not”; Capt. Joe Della Vedova: some data recorders and navigational devices recovered; investigation in the next couple of weeks; Aviation Week: control-surface malfunction in landing sequence, data-link break, then flat spin as part of a self-destruct program when comms re-established; five air vehicles received, sixth due next month; two now destroyed or heavily damaged, two at Edwards, one still supporting Afghanistan. Air Force Magazine later: AV-3 grounded; return late March 2002. Sources opened: https://www.latimes.com/archives/la-xpm-2002-jan-01-mn-19398-story.html and https://globalsecurity.org/org/news/2002/020108-attack03.htm and https://www.airandspaceforces.com/article/1103eyes/

**Threat landscape.** A two-ship ACTD cannot absorb a quality escape. The trust failure is industrial (bolt orientation) plus a landing-mode C2 break.

**Intelligence assessment.** [Assessment — high confidence] January is investigation-and-grounding month. [Inference — moderate confidence] The “one still supporting Afghanistan” line in Aerospace Daily sits in tension with Air Force Magazine’s AV-3 grounding; the conservative reading is a HALE pause. [Uncertainty] Final fastener finding is later investigation language.

**Opportunity.** The safety-investigation message and the return-to-fly criteria for AV-3/AV-4 should have been Watch fields.

**LRRK relevance.** Supply / Watch. Reliability is now the HALE story.

**Confidence.** High on January press and grounding; moderate on the one-vs-zero still-flying seam.

## 02. Predator winter losses — icing and lost satellite link

*Event / publication dates: continuing OEF; CRS later compilation of Afghanistan shortcomings*

**Verified record — [Fact — B1]** CRS RL31872: real-world operations in Afghanistan revealed shortcomings; two UAVs crashed in Afghanistan due to wing icing caused by flying in clouds; other losses might have been caused by loss of satellite communications link, often difficult to reestablish; altitudes required to avoid weather or obtain imagery put the UAV in range of enemy air defenses; a 2001 DOT&E report concluded “As tested, the Predator UAV system is not operationally effective or suitable,” yet Predator teams were among the first dispatched after 11 September. Source opened: https://www.everycrsreport.com/files/20030425_RL31872_089a1bc2a3f353e69de4557e6614bc453e2049b2.html

**Threat landscape.** A remote shooter that ices up or drops SATCOM is a fair-weather hunter. January in the Hindu Kush is the stress case.

**Intelligence assessment.** [Assessment — moderate confidence] Icing and lost-link are January-relevant continuing facts, not a new 31 January shoot-down report. [Inference — moderate confidence] DOT&E’s “not operationally effective” finding and CENTCOM’s “most capable sensor” praise (Franks, November 2001, as later cited) can be true at once. [Uncertainty] No January 2002 loss tally primary was opened.

**Opportunity.** Icing-limit cards and SATCOM reacquisition timelines should have been Kestrel fields.

**LRRK relevance.** Control Fabric / Lab. The datalink and the wing are the winter vulnerabilities.

**Confidence.** High that icing/lost-link were documented OEF problems; low on January-specific hull losses.

## 03. Designation change incoming — RQ-1B to MQ-1 on 1 February

*Event / publication dates: 1 February 2002 (CRS); January is the last RQ-1 month*

**Verified record — [Fact — B1]** CRS RL31872: on 1 February 2002 the Air Force changed the Predator’s military designation from RQ-1B (reconnaissance unmanned) to MQ-1 (multi-mission unmanned) due to added laser-designation and missile-firing capabilities. Source opened: https://www.everycrsreport.com/files/20030425_RL31872_089a1bc2a3f353e69de4557e6614bc453e2049b2.html

**Threat landscape.** A designator letter is doctrine. “M” writes strike into the type’s name.

**Intelligence assessment.** [Assessment — high confidence] The change is a 1 February event; January is the staffing window. [Inference — moderate confidence] The letter change is how ACC claims a mission CIA still flies. [Uncertainty] The order text was not fetched.

**Opportunity.** The designation message and any CIA-inventory exception should have been Campaign files.

**LRRK relevance.** Campaign. Honest dating: the change itself is tomorrow’s file.

**Confidence.** High on the CRS date; the event is a forward indicator at this cutoff.

## 04. REMUS UOES — month ten, still a user eval, not a program of record

*Event / publication dates: UOES April 2001–April 2003*

**Verified record — [Fact — A1]** Clegg/Peterson Oceans 2003: six NSCT-1 operators, two WHOI REMUS, worldwide exercises, feeding an FY2005 procurement spec. January 2002 is inside that window. Hydroid’s 2001 founding means a commercial shop now exists to take a production order the UOES is writing. Sources opened: https://doi.org/10.1109/oceans.2003.178069 and https://www.whoi.edu/press-room/news-release/partnership-provides-autonomous-vehicles-to-enable-new-era-of-deep-sea-research/

**Threat landscape.** A forced-entry MCM plan written in January 2002 still rests on two eval hulls and marine mammals, not a REMUS squadron.

**Intelligence assessment.** [Assessment — high confidence] UOES continued. [Inference — moderate confidence] OEF’s air-centric first winter did not generate a public undersea surge. [Uncertainty] January 2002 exercise location not fetched.

**Opportunity.** UOES deficiency report #n would have been the Lab feed.

**LRRK relevance.** Lab. Keep undersea in a thin air month.

**Confidence.** High on continuity; low on January sorties.

## 05. Hunter still a Balkans winter bird — CENTCOM deployment is a 2003 fact

*Event / publication dates: annual winter stand-down practice; CENTCOM deployment dated January 2003 in later Army press*

**Verified record — [Fact — B2]** CRS: Hunter sent home from the Balkans each winter; cannot fly bad weather. Inside the Army, 20 January 2003 (as later cited by CRS): Hunter deployed to CENTCOM. That is not a January 2002 event. Source opened: https://www.everycrsreport.com/files/20030425_RL31872_089a1bc2a3f353e69de4557e6614bc453e2049b2.html

**Threat landscape.** The Army’s corps UAV is weather-limited and still in the Balkans rotation model.

**Intelligence assessment.** [Assessment — high confidence] No opened source puts Hunter in Afghanistan in January 2002. [Inference — low-moderate confidence] OEF’s UAV story remains USAF/CIA Predator plus a grounded Global Hawk plus Pointer. [Uncertainty] V Corps Germany fielding remains a 2003–04 item.

**Opportunity.** Winter redeployment orders and IAI/TRW sustainment status should have been supply fields.

**LRRK relevance.** Supply / Watch. Honest dates: do not steal January 2003.

**Confidence.** High on the negative (no 2002 CENTCOM Hunter primary opened).

## Forward indicators

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

1. 1 February MQ-1 designation.
2. Global Hawk return-to-fly (later late March).
3. Operation Anaconda planning and whether Predators will be tasked for CAS.
4. FY02 supplemental for Predator production acceleration.
5. Dragon Eye June–July 2002 operator evaluations.

> **Collection integrity.** Opened LAT and Aerospace Daily January 2002 crash coverage, CRS for icing/DOT&E/designation, UOES abstract, WHOI Hydroid note. Did not treat later fastener findings as a January 2002 official cause release. Refused undated “30 Predators lost” media tallies that CRS itself treats as less accurate than Safety Center figures.

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