LC-1 · Kinematic Threat Briefs
Kinematic Threat Brief
Source-imported record. This page is not a QSVFF-sealed filing or a verification certificate.
# Kinematic Threat Brief **LRRK Watch / Open-Source Intelligence** — Five current signals across systems that sense, move, and act. | Field | Value | | --- | --- | | Collection cutoff | 31 July 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 July put a ground robot into a shooting war — PackBot into caves and a building complex at Nasarat, Afghanistan — and took a second Global Hawk out of the Afghan pairing, the July crash that CRS later attributes to engine failure, while Dragon Eye operator evaluations closed. ### Key judgments 1. **[Assessment — high confidence]** Col. Bruce Jette’s Rapid Equipping Force later stated on the record that PackBot’s first combat use was July 2002 at Nasarat, examining caves and a building complex. 2. **[Assessment — high confidence]** A second Global Hawk loss in July 2002 (CRS: engine failure; flight-test ops temporarily halted) ended the AV-3/AV-4 47-flight pairing run. 3. **[Inference — moderate confidence]** Sending a 40-pound robot into a cave before a soldier is the land analogue of the armed Predator: sense, then act, with the human off the X. ### 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. July 2002 — PackBot first combat, Nasarat, Afghanistan *Event / publication dates: July 2002, Nasarat* **Verified record — [Fact — B1]** Army News Service, 22 April 2003 (opened): Col. Bruce Jette, director of the Rapid Equipping Force, said PackBot was first used in combat in July 2002 to examine caves and a building complex in Nasarat, Afghanistan. NASA Spinoff 2005 (opened): first military deployment to Afghanistan in July 2002 to help clear caves and bunkers, search buildings, and cross live anti-personnel mine fields; prompted after the Army Vice Chief of Staff, Gen. Jack Keane, saw soldiers clearing caves with grappling hooks. Sources opened: http://www.globalsecurity.org/wmd/library/news/iraq/2003/iraq-030422-army-packbots.htm and https://spinoff.nasa.gov/Spinoff2005/ps_1.html **Threat landscape.** A flipped-over-capable, stair-climbing robot with IR/optical cameras moves first entry off the soldier. The trust boundary is a wireless controller and a helmet-mounted eyepiece. **Intelligence assessment.** [Assessment — high confidence] July 2002 is the dated first combat use. [Inference — moderate confidence] REF, not a program of record, is how the robot got to the cave. [Uncertainty] Number of hulls and any combat damage this month were not fetched. **Opportunity.** After-action on RF interference, flip-over recoveries, and soldier acceptance. **LRRK relevance.** Sense-Move-Act / Lab. First opened ground-robot combat employment in this archive. **Confidence.** High on month, place, and REF attribution; low on unpublished hull counts. ## 02. July 2002 — second Global Hawk combat loss *Event / publication dates: July 2002* **Verified record — [Fact — B1]** CRS RL31872: two Global Hawks lost since missions started in Afghanistan, one crash in December 2001 and the other in July 2002; flight-test operations temporarily halted after each crash; 2002 crash attributed to engine failure, 2001 crash to an improperly installed bolt. Air Force Magazine: AV-3/AV-4 pairing completed 47 flights by July. Smithsonian: Afghanistan ops continue until 28 September 2002, implying a residual jet after the July loss. Sources opened: https://www.everycrsreport.com/files/20030425_RL31872_089a1bc2a3f353e69de4557e6614bc453e2049b2.html and https://www.airandspaceforces.com/article/1103eyes/ and https://www.smithsonianmag.com/air-space-magazine/send-in-the-global-hawk-8601982/ **Threat landscape.** Engine failure on an ACTD HALE jet is a second quality/reliability tax on a fleet counted on one hand. **Intelligence assessment.** [Assessment — high confidence] A July 2002 loss occurred. [Inference — moderate confidence] Temporary halt after each crash is now a pattern. [Uncertainty] Tail number and exact day in July were not in the opened CRS extract. **Opportunity.** Engine-failure message and the residual-jet employment decision. **LRRK relevance.** Supply / Watch. HALE fragility, second data point. **Confidence.** High on July 2002 loss and engine-failure attribution as CRS states; low on day-exact. ## 03. Dragon Eye operator evaluations close *Event / publication dates: June–July 2002 window ends* **Verified record — [Fact — B1]** JFCOM: evaluations June–July 2002, twenty systems. Designation-Systems: mid-2002 field evaluation; first operational use OIF 2003; production prime to AeroVironment in November 2003. Source opened: https://web.archive.org/web/20041017053912/http://www.jfcom.mil/about/experiments/mc02/concepts/drageye.htm and https://designation-systems.net/dusrm/app2/q-14.html **Threat landscape.** Eval close is a downselect input, not yet a production contract. **Intelligence assessment.** [Assessment — high confidence] The eval window ends this month. [Inference — moderate confidence] Both BAI and AeroVironment hardware were scored; the winner is a 2003 story. [Uncertainty] July scorecards not fetched. **Opportunity.** The eval report to MCSC. **LRRK relevance.** Lab / Supply. **Confidence.** High on the window; low on unpublished scores. ## 04. Raven Pathfinder ACTD — 2002 development year *Event / publication dates: 2002 Pathfinder ACTD (Flashlight flew October 2001)* **Verified record — [Fact — B2]** Designation-Systems Raven page: Flashlight further developed into Raven in 2002 under the Army’s Pathfinder ACTD; prototype hand-built, not mass-producible; Block I LRIP first delivered May 2003. July 2002 is inside that ACTD year. Source opened: https://www.designation-systems.net/dusrm/app2/q-11.html **Threat landscape.** A half-size Pointer with a portable GCS is being productized while SOF is buying Pointers for OEF. **Intelligence assessment.** [Assessment — moderate confidence] Pathfinder work is a 2002 fact. [Inference — moderate confidence] Pointer urgent buys and Raven ACTD are complementary, not competitive, this year. [Uncertainty] No July 2002 Army Pathfinder release opened. **Opportunity.** Pathfinder test points and GCS weight. **LRRK relevance.** Lab / Supply. AeroVironment lineage. **Confidence.** Moderate on 2002 as the ACTD year. ## 05. UOES REMUS — month sixteen *Event / publication dates: continuing* **Verified record — [Fact — A1]** Clegg/Peterson. Source opened: https://doi.org/10.1109/oceans.2003.178069 **Threat landscape.** Unchanged: two eval hulls, special-clearance team. **Intelligence assessment.** [Assessment — high confidence] Continuing. [Inference — moderate confidence] October Bahrain test will be the next dated event. [Uncertainty] July 2002 location not fetched. **Opportunity.** Mid-late UOES configuration freeze. **LRRK relevance.** Lab. **Confidence.** High on continuity. ## Forward indicators Ranked watchlist as of the collection cutoff (what a 2001–2011 Watch desk would have monitored next). 1. Global Hawk residual employment through 28 September. 2. PackBot follow-on cave tasks and any REF buy. 3. Hunter BAT drop (later 11 October). 4. REMUS Bahrain accuracy test (later mid-October). 5. Whether a second theater (Yemen, Iraq no-fly) gets an armed Predator. > **Collection integrity.** Opened Army News (April 2003) for the July 2002 Nasarat date, NASA Spinoff, CRS for the July Global Hawk loss, JFCOM/Designation-Systems for Dragon Eye. Day-exact Global Hawk crash not found. No how-to on cave clearing. *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>