A Century of Anomaly Miscommunication

The public communication failures that accompanied the New Jersey drone incursions were not novel. They were the predictable product of four structural failures, each traceable to a specific historical origin.

Failure 1: No vocabulary for explicit uncertainty. The pattern was established early in multiple incidents, in which an anomalous aerospace event drew official attention and the institutional response was premature closure rather than honest uncertainty.¹Footnote 11 For example, at Roswell in 1947, the Army Air Field announced the recovery of a "flying disc" and then retracted it as a weather balloon within a day [47]. In the 1966 Michigan sightings, an Air Force consultant attributed a wave of credible reports to "swamp gas," a dismissive ruling that did not fit many of the accounts and that the investigator himself later disowned [48]. Since then, public UAP communication has often been forced into a false binary: either authorities know what something is, or they insist it poses no threat. Missing is a durable institutional vocabulary for the honest middle ground: we detected something, we do not yet know what it is, and we are still investigating. Many later communication failures stem from that gap.

Failure 2: Legacy stigma suppresses reporting. A declassified 1953 CIA scientific review recommended a formal campaign to stigmatize the topic and reduce public interest; the resulting social and professional penalty for reporting anomalous observations has persisted for seven decades (see Appendix I: Historical precedents in anomalous-event communication).

Failure 3: Missing/Dismantled inter-agency protocols. When the New Jersey drones appeared, the White House, FAA, DHS, FBI, and DoD each issued statements without a shared factual basis because no inter-agency protocol had ever been rebuilt. Similarly, the closure of the U.S. Air Force’s Project Blue Book; the program left no successor coordination mechanism and actively stigmatized the creation of one (see Appendix I: Historical precedents in anomalous-event communication). With no trusted official channel, civilian groups like MUFON and military whistleblowers filled the vacuum. Their reports accumulated in a gray zone: too persistent to ignore, but too stigmatized and institutionally unsupported to resolve with adequate rigor.

Officials can say ‘we know what it is’ or ‘there is no threat,’ but no institutional language exists for the honest intermediate: we have detected objects we cannot yet identify.

Failure 4: The information environment outpaced institutional capacity. The contemporary phase began in December 2017, when the New York Times revealed the Advanced Aerospace Threat Identification Program (AATIP), a Pentagon office tasked to study anomalous aerospace events [49]. Between 2022 and 2025, Congress held four public hearings on UAP, with classified sessions alongside. In 2025, the documentary The Age of Disclosure [6] featured 34 current and former government officials. Some described direct knowledge of recovered objects and reverse-engineering programs. Senator Marco Rubio offered more guarded framing: “We have people with very high jobs…that are either A: liars, B: crazy, or C: telling the truth.” The documentary’s contested reception—27% critics, 91% audience on Rotten Tomatoes—illustrates a credibility gap. Also, while the AARO office was set up to provide a factual account of the government’s history with UAP, its first historical report released in 2024 was widely criticized [50] as filled with mistakes and factual errors.

By the time the New Jersey incursions occurred, the information environment bore no resemblance to the one in which the Robertson Panel could plausibly manage public perception through institutional gatekeeping. The 1997 Phoenix lights took weeks to reach national awareness; a comparable event today goes viral within a day. The institutional communication cycle (investigation, interagency coordination, legal review, press clearance) operates on a timescale of days to weeks. By the time an official statement is issued, the narrative has been set by whomever spoke first, regardless of whether they had evidence.

The four structural failures traced above operated simultaneously during the New Jersey incident and the inter-agency gap was the most operationally visible. No standing protocol exists for inter-agency communication during anomalous aerospace events, analogous to protocols for natural disasters, disease outbreaks, or terrorist attacks [8]. Worse, the vocabulary gap compounds the coordination gap. Officials must choose between misleading certainty (“no threat”) and silence. Both erode trust. The New Jersey case, in which a retired counter-UAS specialist offered his expertise and was frozen out, demonstrates that a penalty structure created by the 1953 Robertson Panel remains active. Stigma reduces the volume and quality of reports reaching analysts; thinner reporting yields weaker detection and weaker identification; and officials are then asked to communicate around the silence their own system produced.

Unified Incident Command and Threat Planning

The Incident Command System (ICS) is the standard U.S. framework for organizing emergency response across agencies and jurisdictions. It is used for natural disasters, industrial accidents, terrorist attacks, search-and-rescue operations, cyberattacks, public-health emergencies, and major planned events. Its purpose is to reduce confusion by establishing clear command, standardized terminology, shared situational awareness, and defined responsibilities for operations, planning, logistics, finance, and public communication.

ICS begins with an Incident Commander, usually from the agency with immediate jurisdiction. As an incident grows, command can transfer or expand. When several agencies or jurisdictions have authority, ICS can form a Unified Command, allowing them to set common objectives while preserving their statutory roles. For large or geographically dispersed incidents, an Area Command or Emergency Operations Center can coordinate multiple incident commands and allocate resources.

The system is built to scale. A local emergency can remain local, while a major disaster may involve state emergency management, FEMA, the National Guard, and, if needed, U.S. Northern Command under Defense Support of Civil Authorities. Counterterrorism or mass-casualty events may bring together local police, emergency medical services, federal investigators, and intelligence agencies. These cases show that ICS can accommodate overlapping authority, sensitive information, and even classified channels when there is a recognized incident requiring organized response.

The New Jersey drone incursions fell into a more ambiguous category. Local officials, law enforcement, airports, military installations, and federal agencies all had stakes in the situation, but the events were not publicly treated as a confirmed emergency or credible threat. Federal messaging repeatedly stated that there was no evidence of a national-security or public-safety threat, and many sightings were later attributed to lawful drones, aircraft, or misidentifications. Because the incidents did not clearly become a declared emergency, terrorist incident, aviation disaster, or confirmed hostile drone operation, they did not trigger a visible full ICS/ National Incident Management System (NIMS) activation.

The response remained agency-specific. Local police gathered reports and handled public concern. State officials coordinated with law enforcement channels. The FBI collected tips and investigated possible criminal activity. The FAA managed airspace and safety restrictions. DHS and DoD provided assessment or technical support where appropriate. Military installations operated under separate force-protection authorities. But there was no clearly identified Incident Commander, Unified Command, Joint Information Center, or shared incident action plan for the overall event.

The result was a command-and-communication gap. Airspace authority sat largely with the FAA; investigation with the FBI and law enforcement; mitigation authority with limited federal actors; military bases under separate defensive authorities; and state/local officials left managing public concern without full control over relevant tools or information. In a hurricane, wildfire, chemical spill, or confirmed attack, these overlapping authorities would likely be integrated through ICS/NIMS. In the drone case, because the incursions were not officially treated as a credible threat, coordination occurred through ad hoc interagency channels rather than a formal emergency-response architecture.

The policy lesson is that major drone waves and ambiguous aerial incidents need clearer ICS/NIMS triggers. Even before hostile intent is confirmed, officials may need a scalable structure for reporting, evidence preservation, airspace coordination, classified-to-unclassified information sharing, public messaging, and escalation. The New Jersey episode therefore illustrates not a failure of ICS itself, but the absence of a clear playbook for applying ICS to ambiguous low-altitude aerial events.