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 January 2010 | | 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 This month the United States treated remotely piloted aircraft as both a humanitarian sensor and a covert strike instrument, while civil-liberties litigators forced the legal basis of remote killing onto the public record — a split trust picture in which Sense was shared and Act remained classified. ### Key judgments 1. **[Assessment — high confidence]** High-altitude unmanned ISR was retasked from a combat theater to a disaster zone and used to produce unclassified imagery for relief organizations, showing that the same Sense stack could be declassified at the product layer without disclosing the platform’s combat C2. 2. **[Assessment — moderate confidence]** The CIA’s Pakistan missile campaign accelerated after the 30 December 2009 Khost bombing, with satellite-linked aircraft controlled from Virginia and launched from a base in Pakistan, tightening reliance on remote Act as Pakistani ground offensives slipped. 3. **[Inference — moderate confidence]** The ACLU’s 13 January FOIA on Predator “targeted killings” will become the month’s lasting Control Fabric marker: the public now has a docket demanding who may be killed, where, and on what legal theory, even as operators refuse to confirm the program. ### 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 retasked from Afghanistan to Haiti *Event / publication dates: 12 January 2010 earthquake; 14–15 January 2010 flights and public briefings* **Verified record — [Fact — A1]** An RQ-4 Global Hawk provided imagery of earthquake-damaged Haiti. Col. Bradley G. Butz, vice commander of the 480th Intelligence, Surveillance and Reconnaissance Wing, told a Department of Defense Bloggers Roundtable on 15 January that the aircraft had “pretty good coverage of the entire country,” flew 14 hours on 14 January, and produced between 400 and 700 images that day, operating daily from Naval Air Station Patuxent River, Maryland. He said this was the first use of Global Hawk in a Caribbean disaster-relief mission. U.S. Air Force Public Affairs published the account the same day, with stills of the National Cathedral and Presidential Palace. Wired’s Danger Room, citing the same roundtable via Aviation Week’s Ares, reported the airframe had been retasked from an Afghanistan mission and that SOUTHCOM would share unclassified images with NGOs. Fetched: https://web.archive.org/web/20170615125356/http://www.af.mil/News/Article-Display/Article/118014/global-hawk-collects-reconnaissance-data-during-haiti-relief-efforts/ ; https://web.archive.org/web/20100117143436/http://www.wired.com/dangerroom/2010/01/pentagon-shares-earthquake-images-from-high-flying-spy-drone/ **Threat landscape.** The trust boundary is classification and dissemination, not kinetic Act. A combat HALE sensor was used as a public damage-assessment tool. The physical consequence is better or worse aid routing; the political consequence is a preview of how unmanned ISR products can be stripped of combat markings and released. **Intelligence assessment.** [Assessment — high confidence] SOUTHCOM and the 480th treated declassified imagery as a relief commodity. [Inference — moderate confidence] Retasking a Global Hawk from Afghanistan implies orbit scarcity even for a high-priority disaster. [Uncertainty] Public reporting does not establish how much resolution was withheld before release. **Opportunity.** A contemporaneous log of which images were released, at what resolution, and to which NGOs would have let a Watch desk measure the declassification boundary. **LRRK relevance.** Sense-Move-Act / Watch / Passport. A January 2010 Passport would have recorded the first Caribbean Global Hawk relief orbit, the Patuxent launch node, and the decision to push unclassified product to non-military users. **Confidence.** High on the 15 January official briefing and 14 January flight hours; moderate on the Afghanistan retask (single contemporaneous press chain); low on withheld sensor settings. ## 02. CIA drone tempo after Khost *Event / publication dates: strikes from 31 December 2009 through mid-January 2010; New York Times / NBC report 22–23 January 2010* **Verified record — [Fact — B1]** Scott Shane and Eric Schmitt reported that after the 30 December 2009 suicide bombing that killed seven Americans at a CIA base in Khost, Afghanistan, the CIA conducted “the most intensive series of missile strikes from drone aircraft since the covert program began.” Beginning the day after Khost, the agency had carried out 11 strikes that Pakistani news reports said killed about 90 people suspected of being militants, including a 6 January strike on a mud fortress in North Waziristan and a later volley in South Waziristan. The piece said strikes were coming roughly every other day, versus about once a week the prior year; that aircraft were launched from a secret base in Pakistan and controlled by satellite from CIA headquarters in Virginia; and that an Obama administration official said the CIA expected to more than double its latest Reaper fleet to 14 from 6 by the following year. The CIA spokesman declined to comment on strikes. Fetched: https://www.nbcnews.com/id/wbna35027603 **Threat landscape.** Remote Act in a country where the United States is not officially at war, with a civilian agency on the trigger and a host government that denounces strikes in public. The physical consequence is missile effects in Waziristan compounds; the trust failure is the gap between public Pakistani protest and private facilitation. **Intelligence assessment.** [Assessment — moderate confidence] The post-Khost surge is real as a tempo change even if Pakistani casualty figures remain unverified. [Inference — moderate confidence] White House pressure after Khost and the 25 December 2009 Detroit airliner attempt is shaping target selection toward Pakistan-based external-operations nodes. [Uncertainty] Official U.S. confirmation of individual strikes is absent; civilian-casualty accounting is not in the U.S. record. **Opportunity.** A contemporaneous Pakistani military or FATA political-agent statement matching the 6 January and mid-January events would have reduced reliance on “Pakistani news reports” as the casualty source. **LRRK relevance.** Control Fabric / Watch / Kestrel. A Watch desk would have logged Virginia as the C2 node, Pakistan as the launch node, and Reaper fleet growth as a supply-chain indicator — without treating unofficial body counts as Fact. **Confidence.** High on the existence of a January tempo increase as reported by named U.S. correspondents quoting officials; moderate on the 11-strike / ~90 figure; low on precise identities of those killed. ## 03. ACLU FOIA on Predator targeted killings *Event / publication dates: 13 January 2010* **Verified record — [Fact — A1]** The American Civil Liberties Union announced a Freedom of Information Act request filed 13 January 2010 with the Department of Defense, Department of Justice (including the Office of Legal Counsel), Department of State, and the CIA. The request asked for the legal basis for using Predator drones to conduct “targeted killings” overseas, including when, where, and against whom strikes can be authorized, and how the United States ensures compliance with international law on extrajudicial killings. Jonathan Manes and Jameel Jaffer were quoted arguing the Obama administration had expanded the program without a public legal theory or civilian-casualty accounting. The release stated the administration had used unmanned drones to target individuals in Afghanistan, Iraq, Pakistan, and Yemen, from control centers thousands of miles away. Fetched: https://www.aclu.org/press-releases/aclu-requests-information-predator-drone-program **Threat landscape.** The trust failure is authorization opacity. Remote Act is already public as a news fact; the legal Control Fabric is not. The physical consequence of that gap is an un-auditable kill chain. **Intelligence assessment.** [Assessment — high confidence] The FOIA creates a durable public demand for the OLC theory and geographic limits. [Inference — moderate confidence] Naming Yemen alongside Pakistan in a January 2010 civil-liberties filing shows advocates already treat the program as extra-theater, not just Afghanistan/Iraq. [Uncertainty] The government has not, as of cutoff, released a legal memorandum. **Opportunity.** An official acknowledgment of which agencies hold targeting legal opinions would have converted this from a request into a mapped Control Fabric. **LRRK relevance.** Control Fabric / Passport / Watch. A Passport filed this month would have recorded the docket, the four addressees, and the specific questions (who, where, civilian count) as the public audit trail. **Confidence.** High on the filing date, addressees, and requested categories; low on whether any agency will answer in 2010. ## 04. Satellite C2 and the human cost of “no Americans at risk” *Event / publication dates: 22–23 January 2010 reporting on the post-Khost revision* **Verified record — [Fact — B1]** The same Shane/Schmitt account stated that strikes “have been expanded by President Obama and praised by both parties in Congress as a potent weapon against terrorism that puts no American lives at risk,” then immediately revised that calculation: Khost showed CIA officers in dangerous territory directing the strikes. An ACLU FOIA that month sought procedures for approving targets. John Arquilla of the Naval Postgraduate School was quoted warning that a campaign that “works” can still fail if Pakistani anger at sovereignty violations grows. Fetched: https://www.nbcnews.com/id/wbna35027603 **Threat landscape.** The advertised trust model — unmanned Act with no U.S. bodies at risk — is incomplete. Human sensors and controllers remain in the loop, some of them forward. The physical consequence is that the C2 chain includes vulnerable people, not only a Virginia terminal. **Intelligence assessment.** [Assessment — high confidence] Public praise of drones as risk-free is now contradicted by a named CIA loss event. [Inference — moderate confidence] Forward CIA presence is a necessary part of the current targeting loop, not an accident. [Uncertainty] The precise division of labor between Virginia operators, Pakistani basing, and Khost-type bases is not in the public record. **Opportunity.** A declassified diagram of launch, satellite path, and forward targeting cells would have let Watch separate platform risk from people risk. **LRRK relevance.** Control Fabric / Sense-Move-Act. The month’s lesson for Kestrel is that “unmanned” does not mean uninhabited C2. **Confidence.** High on the Khost fact and the Virginia-control statement as reported; moderate on Arquilla’s political-backlash claim; low on the full C2 topology. ## 05. Sentinel remains acknowledged but operationally opaque *Event / publication dates: continuing after the 4 December 2009 USAF acknowledgment; no new official Sentinel release this month* **Verified record — [Fact — B2]** The U.S. Air Force publicly confirmed in December 2009 that it was developing a stealthy UAS, the RQ-170 Sentinel, built by Lockheed Martin Skunk Works and operated by the 30th Reconnaissance Squadron at Tonopah, under the 432d Wing at Creech. No comparable official Sentinel release was located for January 2010. The Haiti and Pakistan stories this month used RQ-4 and Predator/Reaper families, not the Sentinel. This filing treats the Sentinel as a continuing known program whose flight activity is not in this month’s public primary record. **Threat landscape.** A low-observable unmanned ISR type is now a named inventory item, but its orbits, sensors, and tasking remain outside the public Sense picture. The trust failure is selective acknowledgment: existence yes, employment no. **Intelligence assessment.** [Assessment — high confidence] The December 2009 name-and-unit disclosure still stands. [Inference — low-to-moderate confidence] Absence of January Sentinel imagery or official updates is consistent with a classified orbit, not with program cancellation. [Uncertainty] No January 2010 official statement on Sentinel location or mission was fetched. **Opportunity.** A single official orbit or unit-deployment notice would have moved Sentinel from “named” to “located” on a Watch map. **LRRK relevance.** Watch / Kestrel / Sense-Move-Act. A January Passport would have carried forward the December 2009 unit and manufacturer data and marked January as a negative collection month for Sentinel employment. **Confidence.** High on the prior public acknowledgment; low on January activity. ## Forward indicators Ranked watchlist as of the collection cutoff (what a 2001–2011 Watch desk would have monitored next). 1. Whether SOUTHCOM continues daily Global Hawk Haiti orbits and whether Predators join the unclassified imagery push. 2. Whether the CIA Reaper fleet expansion (6 toward 14) appears in budget or manufacturer notices. 3. Agency FOIA responses to the ACLU’s 13 January request — especially any Glomar from CIA. 4. Pakistani public versus private posture if North Waziristan offensives remain delayed 6–12 months. 5. Any new official sentence on RQ-170 employment beyond the December 2009 acknowledgment. > **Collection integrity.** Used Air Force Public Affairs, Wired’s 15 January Danger Room contemporaneous post, NBC’s 23 January reprint of the Shane/Schmitt New York Times account, and the ACLU’s 13 January release. Long War Journal January pages were checked but returned a maintenance page and were not used as a primary. Did not treat later unofficial strike tallies as January Facts. Did not invent Sentinel January orbits. Excluded later-memory pieces that place RQ-170 over Abbottabad or Iran — those are not January 2010 public records. *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>