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 April 2009 |
| 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

April’s new kinematic fact is industrial, not combat: General Atomics flew a company-funded jet Predator C Avenger at Gray Butte on 4 April, then again on 13–14 April, advertising a higher-threat, 400-plus-knot complement to MQ-1/MQ-9 on the same ground stations.

### Key judgments

1. **[Assessment — high confidence]** GA-ASI, 20 April 2009: first flight 4 April at Gray Butte Flight Operations Facility, Palmdale; landed without discrepancies; subsequent flights 13 and 14 April; IRAD funded by chairman Neal Blue.
2. **[Assessment — high confidence]** Company specs in the same release: 41-foot fuselage, 66-foot wingspan, Pratt & Whitney PW545B, over 400 KTAS, up to 60,000 feet; same materials/avionics/GCS as Predator B; Lynx SAR plus EO/IR.
3. **[Inference — moderate confidence]** Avenger is a manufacturer bet that the Air Force will want a faster, more survivable armed-reconnaissance jet without a new GCS family.

### 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. Predator C Avenger — first flight 4 April

*Event / publication dates: first flight 4 April 2009; company release 20 April 2009.*

**Verified record — [Fact — A1]** GA-ASI, San Diego, 20 April 2009: “The first flight of the new multi-mission jet-powered Avenger occurred on April 4 at the company’s Gray Butte Flight Operations Facility in Palmdale, Calif., with the aircraft landing without any discrepancies and ready to fly again once refueled. Subsequent flights were successfully executed on April 13 and April 14, with the test program now ongoing.” Thomas J. Cassidy Jr.: same IRAD pattern as the first two Predator B aircraft. Intent: “more survivable in higher threat environments” and “expanded quick-response armed reconnaissance.” Missions listed: wide-area surveillance, armed reconnaissance, border surveillance, time-sensitive strike, “quick response capability missions for use against conventional and asymmetric threats (e.g., terrorists, pirates).” Same proven materials and avionics as Predator B; “fully compatible with the standard GA-ASI Ground Control Stations.” “slightly larger than Predator B”; PW545B; “same mix of weapons as Predator B.” 41-foot fuselage, 66-foot wingspan, “over 400 KTAS,” “up to 60,000 feet.” Sensors: Lynx SAR; EO/IR; “A system based on Lockheed Martin’s F-35 FLIR is currently being evaluated.” Built “while concurrently developing Sky Warrior for the U.S. Army, adding new capabilities to MQ-9 Reaper… and satisfying high-volume/accelerating orders.” https://www.ga-asi.com/ga-asi-successfully-executes-first-flight-of-predator-c-avenger

**Threat landscape.** The trust boundary is a company-funded jet that reuses the combat GCS. Higher speed and altitude change the engagement timeline; they do not by themselves solve see-and-avoid or export-control Category I questions.

**Intelligence assessment.** [Assessment — high confidence] 4 / 13 / 14 April flights are company-primary. [Inference — moderate confidence] Cassidy is selling Avenger as the third node of a Predator/Reaper/Avenger family, not a new program of record. [Uncertainty] April DoD buy interest unpublished; no fetched USAF comment.

**Opportunity.** USAF April IRAD debrief or DTIC flight card.

**LRRK relevance.** Lab: April is the Predator-jet first-flight month. Passport: same GCS family = same ground-segment identity. Watch: whether Avenger becomes a program or stays IRAD.

**Confidence.** High on dates and published specs; low on unpublished government requirement.

## 02. Sky Warrior / Reaper — concurrent production, still the combat line

*Event / publication dates: Cassidy 20 April (concurrent development); prior combat dates.*

**Verified record — [Fact — A1 / B1]** Same 20 April release: Avenger flown “while concurrently developing Sky Warrior.” Block 0 first Iraq mission 18 April 2008 (company 12 June 2008). MQ-9 first combat 25 September 2007.

**Threat landscape.** Army diesel MALE and Air Force Reaper remain the hours-producing systems; Avenger is not yet one of them.

**Intelligence assessment.** [Assessment — high confidence] Combat stack unchanged. [Inference — moderate confidence] Avenger will not displace Reaper this year. [Uncertainty] April CAP unpublished.

**Opportunity.** ACC / Army April hours.

**LRRK relevance.** Watch: do not file Avenger as an operational CAP.

**Confidence.** High.

## 03. CTF-151 / ScanEagle — piracy UAS still the February fact

*Event / publication dates: 27 February StrategyPage; January official stand-up.*

**Verified record — [Fact — C3 / A1]** Mahan ScanEagle (C3); CTF-151 trio (A1). https://www.strategypage.com/htmw/htnavai/20090227.aspx https://www.africom.mil/article/6412/centcom-new-counter-piracy-task-force-established

**Threat landscape.** Cassidy’s 20 April release lists “pirates” among Avenger missions—an industrial claim, not a Horn of Africa deployment.

**Intelligence assessment.** [Assessment — moderate confidence] ScanEagle remains the only named Somali-coast UAS in the fetched set. [Inference — low confidence] April piracy events (including any Maersk-class case) are not tied to a fetched UAS primary here. [Uncertainty] No ScanEagle-on-Maersk fact was retrieved; none is invented.

**Opportunity.** Fifth Fleet April ScanEagle hours.

**LRRK relevance.** Watch: keep pirate-UAS claims to named airframes.

**Confidence.** Moderate.

## 04. Fire Scout — McInerney still the 2009 path

*Event / publication dates: later 5 May 2009 company text.*

**Verified record — [Fact — B1]** Northrop: embarked 10 December 2008; slated for the next counter-narcotics cruise; May autonomous flights are a May fact. http://globalsecurity.org/intell/library/news/2009/intell-090505-northrop-grumman01.htm

**Threat landscape.** Frigate VTUAV vs. destroyer ScanEagle: two shipboard unmanned paths, different recovery geometries.

**Intelligence assessment.** [Assessment — moderate confidence] April is still DT. [Inference — moderate confidence] SOUTHCOM counter-narcotics will be the first operational use, not LCS. [Uncertainty] April DT hours unpublished.

**Opportunity.** NAVAIR April DT note.

**LRRK relevance.** Watch: May autonomous recoveries.

**Confidence.** Moderate.

## 05. Pakistan campaign — still no April official list in the fetched set

*Event / publication dates: 23 January CNN.*

**Verified record — [Fact — B1]** Last fetched contemporaneous pair is 23 January. https://www.cnn.com/2009/WORLD/asiapcf/01/23/pakistan.missile/index.html

**Threat landscape.** Covert campaign continues beside a very public company first flight.

**Intelligence assessment.** [Assessment — moderate confidence] Continuity. [Inference — moderate confidence] A public CIA comment is the next political event. [Uncertainty] April named-strike primary not fetched.

**Opportunity.** Dated April Islamabad wire.

**LRRK relevance.** Watch: frequency.

**Confidence.** Moderate.

## Forward indicators

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

1. Fire Scout autonomous flights on McInerney.
2. First on-the-record CIA drone comment.
3. Avenger follow-on test points / any USAF interest.
4. Official ScanEagle hours on CTF-151.
5. Dated April–May Pakistan strike pair.

> **Collection integrity.** Fetched: full GA-ASI 20 April Avenger release. Refused: Maersk Alabama ScanEagle claims (no fetched UAS primary). NYT February–April campaign features 403 and are not cited.

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