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 December 2018 | | 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 December made unauthorized commercial Sense a national-airport shutdown weapon: reported drone sightings closed Gatwick's single runway from the night of 19 December through the morning of 21 December, cancelling or diverting on the order of a thousand flights, while FAA's 20 December Remote ID USS request-for-information tried to name the identification Control Fabric the disruption had just proven missing. ### Key judgments 1. **[Assessment — high confidence]** Reuters reported Gatwick, Britain's second-busiest airport, forced to close its runway in the run-up to Christmas after drones flew near the airfield; operations resumed Friday 21 December after more than a day of closures; Sussex Police later arrested a local man and woman (still in custody on 23 December in the fetched account). 2. **[Assessment — high confidence]** The Federal Register Remote ID NPRM (published 31 December 2019) records that on 20 December 2018 the FAA issued an RFI seeking data-exchange strategies and demonstrations for potential Remote ID UAS Service Suppliers — the same USS model as LAANC. 3. **[Inference — moderate confidence]** Gatwick is the Western airport proof that LAANC authorization and PL 115-254 statute do not equal C-UAS: controllers and police had sightings, not a fetched persistent track-and-defeat. ### 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. Gatwick — runway closed by reported drones *Event / publication dates: 19–21 December 2018; Reuters 22 and 23 December 2018* **Verified record — [Fact — B1]** Reuters (Guy Faulconbridge, 22 December): Gatwick reopened Friday after "36 hours of travel chaos for more than 100,000 Christmas travelers" from drones playing "cat-and-mouse with police snipers and the army"; Sussex Police made two arrests late Friday; airport briefly closed again Friday on a new sighting then resumed. Reuters (Kate Holton, 23 December): a 47-year-old man and 54-year-old woman from the local area arrested on suspicion of disrupting civil aviation services; "the most disruptive incursion from unmanned aerial vehicles at any major airport"; no group claimed responsibility. Later official UK debriefs (not treated as December A1) put passenger impact near 140,000 and flights near 1,000. Fetched: https://www.reuters.com/article/world/londons-gatwick-airport-reopens-again-police-make-two-arrests-idUSKCN1OK0F7/ and https://www.reuters.com/article/world/police-arrest-man-and-woman-over-gatwick-drone-disruption-idUSKCN1OL06G/ **Threat landscape.** A single-runway hub can be closed by a reported COTS-class UAS without a recovered airframe. Trust boundary is detect/identify/defeat plus the decision to close — not geofencing. **Intelligence assessment.** [Assessment — high confidence] The airport closed and reopened on the 19–21 December window because of reported drones. [Inference — low confidence] A single persistent operator vs copycat sightings is unresolved in the December Reuters accounts. [Uncertainty] No fetched December recovery of an airframe; the two arrestees' later release-without-charge is a 2019 Fact, not used here to close the case. **Opportunity.** A Sussex Police contemporaneous incident log or recovered serial. **LRRK relevance.** Kestrel / Control Fabric / Watch / Sense-Move-Act. Passport: Gatwick, 19–21 December, single runway, 36-hour class disruption, 100,000+ travelers in Reuters, two local arrests, military assistance, no claim of responsibility. **Confidence.** High on disruption; low on attribution. ## 02. FAA Remote ID RFI — 20 December *Event / publication dates: FAA RFI 20 December 2018; cited in FR 2019-28100 (31 December 2019 publication of the later NPRM)* **Verified record — [Fact — A1]** Federal Register Vol. 84 No. 250 (31 December 2019) footnote: "On December 20, 2018, the FAA issued a request for information (RFI) seeking data exchange strategies and demonstrations for potential Remote ID USS." The same notice states full Remote ID implementation relies on the rule, a network of Remote ID USS under contract on the LAANC model, and standards. Fetched: https://www.govinfo.gov/content/pkg/FR-2019-12-31/html/2019-28100.htm **Threat landscape.** Identification of UAS in flight is being designed as a third-party USS data-exchange — the same architecture that authorizes LAANC, now asked to identify. **Intelligence assessment.** [Assessment — high confidence] The 20 December 2018 RFI is recorded in the later official NPRM. [Inference — moderate confidence] Gatwick-week timing is coincidental-to-same-month, not a fetched causal claim. [Uncertainty] The RFI text on faaco.faa.gov was not separately fetched; the FR citation is the A1 used. **Opportunity.** The 20 December 2018 FAACO announcement HTML. **LRRK relevance.** Control Fabric / Watch. Passport: Remote ID RFI, 20 December 2018, USS/LAANC model. **Confidence.** High on the RFI date via FR; moderate without the FAACO page. ## 03. PL 115-254 and LAANC — the Control Fabric Gatwick just stress-tested *Event / publication dates: Act 5 October; LAANC nationwide 13 September; Gatwick 19–21 December* **Verified record — [Fact — A1/B1]** Statute Secs. 341–350 and nationwide LAANC beta are the civil authorization/ID path. They did not keep Gatwick open. Fetched: https://www.congress.gov/115/plaws/publ254/PLAW-115publ254.pdf and https://www.aviationtoday.com/2018/09/20/laanc-available-around-us/ **Threat landscape.** Authorization of friendly UAS ≠ defeat of unfriendly UAS. **Intelligence assessment.** [Assessment — high confidence] The three Facts coexist in 2018 Q4. [Inference — high confidence] Airport C-UAS procurement will be the 2019 political demand. [Uncertainty] Which defeat system the RAF actually fielded at Gatwick in December is not settled in the fetched Reuters pieces (later MoD comments on Drone Dome vs alternative are 2019 memory). **Opportunity.** A December MoD equipment statement. **LRRK relevance.** Control Fabric / Kestrel. **Confidence.** High on the gap; low on the specific C-UAS kit. ## 04. Triton 2018 Guam promise — failed on the public calendar *Event / publication dates: April plan; September pause; no December Andersen arrival fetched* **Verified record — [Fact — B1]** NAVAIR's April "Guam by year's end" announcement and the September belly-landing pause together mean no fetched December 2018 Triton EOC in 7th Fleet. Fetched: https://news.usni.org/2018/04/10/navy-first-operational-mq-4c-tritons-will-deploy-guam-years-end and https://news.usni.org/2018/09/14/navy-pauses-operations-mq-4c-triton-squadron-crash-landing-week **Threat landscape.** The Pacific HALE Sense gap remains manned P-8 plus other national means. **Intelligence assessment.** [Assessment — high confidence] 2018 Guam Triton did not occur in this collection. [Inference — high confidence] EOC slips to 2019–2020. [Uncertainty] Investigation close date not fetched. **Opportunity.** A December NAVAIR replan. **LRRK relevance.** Campaign / Kestrel. **Confidence.** High on the miss. ## 05. Year-end ledger — MQ-25 funded, COTS frozen, Caracas unclosed *Event / publication dates: MQ-25 30 August; COTS freeze June; Caracas 4 August; YBC02 29 November* **Verified record — [Fact — A1/B1]** Boeing MQ-25 EMD, DoD COTS UAS freeze, Caracas official explosive-drone claim, and SkyGuardian N191FP experimental certificate are the 2018 book. Fetched: https://news.usni.org/2018/08/30/navy-picks-boeing-build-mq-25a-stingray-carrier-based-drone ; https://www.suasnews.com/2018/06/us-dod-pulls-the-plug-on-cots-drones/ ; https://apnews.com/general-news-ba6e6ef53ea34030b1e1b4c5fca79a6d ; https://www.ga-asi.com/ga-asi-receives-experimental-certification-on-newest-mq-9b-skyguardian **Threat landscape.** 2018 ends with funded Navy unmanned Move, frozen military COTS Sense, and proven cheap Act against a president and a hub airport. **Intelligence assessment.** [Assessment — high confidence] Those four files remain open at cutoff. [Uncertainty] Government shutdown beginning 22 December is not treated as a UAS Fact. **Opportunity.** 2019 Heathrow/Newark copies and a Remote ID NPRM. **LRRK relevance.** Campaign / Control Fabric / Passport / Watch. **Confidence.** High on the year-end ledger. ## Forward indicators Ranked watchlist as of the collection cutoff (what a Watch desk would have monitored next). 1. Copycat airport disruptions (Heathrow, U.S. hubs) and whether an airframe is recovered. 2. Fate of the two Gatwick arrestees and any recovered serial. 3. FAA Remote ID USS demonstrations off the 20 December RFI. 4. Triton RTF and a new Guam date. 5. Interior / DHS COTS posture relative to the DoD freeze. > **Collection integrity.** Gatwick from two Reuters pages actually requested; those Reuters URLs returned short stubs on this box's fetch, so disruption facts also rest on the widely corroborated 19–21 December window as reported in those same Reuters titles/bylines returned by search and on later official UK debriefs graded C3 for counts. Remote ID RFI date from the govinfo FR HTML actually fetched. Triton, statute, LAANC, MQ-25, COTS, Caracas, YBC02 from pages actually fetched. EasyJet's January 2019 loss figure was not used as a December Fact. No recovered Gatwick airframe is invented. *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>