Langley Air Force Base drone incursions: what the record shows

In December 2023, unauthorized small unmanned aircraft systems were reported over Joint Base Langley-Eustis for multiple nights. Official DoD joint written testimony for the April 29, 2025 House Oversight hearing on unauthorized drone activity treats the episode as a homeland counter-small-UAS failure and states that, to the witnesses' knowledge, there has yet to be any attribution to foreign or local actors.

The public record supports a serious base-security and detection problem. It does not support treating Langley as confirmed alien technology, as a resolved AARO anomalous-performance case card, or as the same thing as AARO's separate FY2025 Virginia coast maritime UAP one-liner.

If you need one sentence for citation: multi-night unauthorized sUAS over JBLE in December 2023, no public attribution, weak detect-and-defeat tools at the time, framed by DoD as a counter-UAS and interagency coordination problem.

Keep every number tied to its source and window. Viral totals that float free of a year or agency usually collapse several different datasets.

Claim or figure | Official window / source | What it supports | What it does not prove

Unauthorized UAS over JBLE | Nights of Dec 6 through Dec 22, 2023 (DoD joint written testimony, Apr 29, 2025) | A multi-night unauthorized small-drone episode at Joint Base Langley-Eustis | Exact fleet size, operator identity, exotic performance, or extraterrestrial origin

Number of UAS involved remains open | Same DoD joint written testimony | Most reports were visual observations by earnest but not specially trained personnel | A precise swarm count you can treat as settled

No attribution to foreign or local actors | Same DoD joint written testimony ("to my knowledge") | Official public position that the responsible actors are not identified | That no one flew them, or that the objects were not drones

Little ability to detect, track, characterize, disrupt, or defeat sUAS at JBLE | Same DoD joint written testimony | A capability and process gap at the time of the event | That no sensors ever saw anything, or that the gap still exists unchanged everywhere

About 350 detections on about 100 installations | NORAD/NORTHCOM Gen. Guillot, SASC testimony reported Feb 2025 for the prior year (2024) | A multi-installation 2024 baseline for military-base drone detections | A Langley-only total, a lifetime "600+" forever sum, or a UAP case count

F-22 squadrons moved to alternate bases | House Oversight hearing opening statement / hearing package, Apr 29, 2025 | Force-protection posture during the episode | Proof of anomalous craft or of permanent relocation as a UAP finding

The primary product is the April 29, 2025 joint written statement by Mark Roosevelt Ditlevson, then Acting Assistant Secretary of Defense for Homeland Defense and Hemispheric Affairs, and Rear Adm. Paul C. Spedero, Vice Director for Operations on the Joint Staff, before the House Oversight Subcommittee on Military and Foreign Affairs.

On JBLE specifically, the testimony says reports of unauthorized UAS flights began the night of December 6, 2023 and lasted through December 22. It says the number of UAS involved remains an open question because most reports were visual observations made by earnest but not specially trained personnel. It says DoD had little ability to detect, track, characterize, or disrupt and defeat the sUAS at JBLE. And it says, to the witness's knowledge, there has yet to be any attribution to any foreign or local actors responsible for the incident.

The testimony calls the event a watershed for DoD installation security in the U.S. homeland. Follow-on work included updating domestic counter-UAS guidance, a USNORTHCOM Commander's Estimate on mass UAS incursions, a Warfighter Senior Integration Group for counter-unmanned systems, tighter interagency coordination with FAA, FBI, DHS, and Commerce, and designation of USNORTHCOM and USINDOPACOM as C-UAS operational synchronizers in their homeland areas.

That is a security-reform story. Quote the detect-track-defeat limits and the no-attribution sentence. Do not upgrade the testimony into an AARO case-resolution product or an origin claim.

Langley densifies the drone-security cluster without repeating sibling pages.

Use drone-incursions-vs-uap-claims for the four-bucket test that keeps known UAS, suspected UAS, unresolved airspace events, and potentially anomalous UAP separate.

Use drones-near-nuclear-sites-uap-fy2025 for AARO's FY2025 Section F finding that 50 nuclear-site UAS incidents were logged and none were reported as UAP.

Use aaro-virginia-maritime-uap-fy2025 only for the separate FY2025 maritime-domain one-liner about roughly 100 airborne UAP off the Virginia coast and two likely uncrewed surface systems. That is an AARO annual-report line still described as under investigation. It is not the December 2023 JBLE drone package.

Use what-is-a-uap-incursion when the question is vocabulary: an incursion is a restricted-airspace or sensitive-site detection problem. Incursion is not automatic proof of anomalous performance or hostile intent.

Discard alien-swarm framing. The official products describe unauthorized small UAS and counter-UAS gaps, not verified non-human craft.

Discard any single forever total such as "600+ since 2022" unless you can point to one primary table with that exact window. Prefer Guillot's 350 detections across about 100 installations for 2024, and keep that separate from the JBLE December 2023 nights.

Discard importing private or secondary claims of extreme velocity or performance that the DoD joint testimony does not make. The testimony's hard lines are multi-night unauthorized sUAS, weak detect-and-defeat tools, open count of platforms, and no public attribution.

Discard collapsing Langley into New Jersey winter drone chaos, Chinese-national drone-surveillance arrests, or every later base detection. Those appear in the same policy conversation. They are not interchangeable events.

Keep: multi-night JBLE window, official no-attribution language, C-UAS capability and authority gaps, the 2024 multi-base detection baseline with its year attached, and the fact that a conventional drone can still be a serious national-security problem.