Standard Operating Procedure: Response to Unidentified Anomalous Phenomena / Unidentified Aerial Events

This Standard Operating Procedure (SOP) establishes a standardized, practical framework for city and county government preparedness, response, documentation, safety, interagency reporting, and public communication regarding reports of Unidentified Anomalous Phenomena (UAP), Unidentified Aerial Events (UAE), unidentified drones, unusual aerial objects, transmedium observations, hazardous debris, unexplained environmental effects, or similar incidents.

The purpose of this SOP is not to determine the origin, intent, or ultimate explanation of an event. The purpose is to ensure that the jurisdiction:

• Protects life safety and responder health
• Preserves evidence and documentation with forensic integrity
• Coordinates with appropriate local, state, and federal partners
• Documents reports consistently using neutral, professional terminology
• Avoids speculation about cause, origin, or intent
• Provides timely, verified public information when needed

By adopting an all-hazards doctrine, this SOP ensures the jurisdiction is equipped to manage the critical first hours of an incident—mitigating public safety risks, occupational hazards, and data collection gaps—while serving as a well-prepared first link in the national reporting chain [1][2].

This SOP closes identified preparedness gaps without creating new bureaucracy, new capital expenditures, or assuming any specific cause, origin, or intent of observed phenomena. It is a no-regrets, low-cost measure that integrates into existing emergency management systems.

It is the policy of [City/County Name] that all good-faith reports of unidentified aerial or anomalous events shall be handled professionally, neutrally, and without ridicule.

Personnel shall use existing emergency management, 911/dispatch, law enforcement, fire/EMS, HazMat, public health, airport/aviation, public works, public information, and legal systems to manage the consequences of an event. UAP-related reports shall not create a separate emergency response structure. All events shall be handled through ordinary all-hazards doctrine, ICS/NIMS principles, established evidence procedures, medical privacy protections, and lawful referral pathways [3].

Personnel shall not certify, speculate on, or publicly declare the origin of an unidentified event unless such determination is made by a competent authority and approved for release.

Planning Statement: We will not speculate about origin. We will use normal incident command, protect the public, preserve evidence, coordinate with appropriate agencies, and provide timely, verified information.

Non-Punitive Reporting — Mandatory Protection Clause

Personnel who submit or forward a good-faith UAP/UAE incident report shall be protected from ridicule, unwarranted psychological referral, or career penalty. This protection is equivalent to that applied to hazardous materials incident reports, aviation near-miss reports, and suspicious activity reports [4]. Eliminating professional stigma is essential to ensure data integrity, promote accurate reporting, and prevent the loss of operationally significant data.

This SOP Applies To

All city/county personnel, including:

• Emergency Management staff
• 911 Dispatch / Communications / PSAP operators
• Law Enforcement (Police / Sheriff) — patrol and supervisory units
• Fire / EMS personnel and HazMat teams
• Public Information Officers (PIOs)
• Public Health and Occupational Health officials
• Public Works / Utilities personnel
• Airport / Aviation liaisons
• City/County Attorney / Legal Counsel
• City/County Manager / Administrator
• Other personnel designated by the Incident Commander or Emergency Management Director

This SOP May Apply to Reports Involving

• Unidentified aerial objects, lights, or effects
• Suspected drones or UAS with no readily apparent operator
• Balloons, aircraft, or aviation anomalies
• Unusual lights or objects near critical infrastructure
• Transmedium observations (e.g., air-to-water transitions)
• Reports of electromagnetic interference or equipment disruption
• Suspected hazardous debris of unknown origin
• Unusual burns, eye irritation, neurological symptoms, disorientation, or other possible exposure complaints
• Public concern or rumor surge related to unusual aerial events

Scope Exclusions — This SOP Does Not Apply To

• Routine aircraft noise complaints
• Ordinary drone complaints with no safety concern
• Fireworks reports
• Known astronomical observations (e.g., planets, meteor showers, satellite passes)
• Media inquiries that do not involve a public safety, documentation, or coordination requirement

Exception: A responsible supervisor may determine that documentation is appropriate for any excluded category based on professional judgment.

This SOP operates under the authority of the jurisdiction's Emergency Operations Plan (EOP) and integrates into existing all-hazards annexes. It is consistent with the following federal and national frameworks:

Federal Authorities

Authority	Relevance
National Incident Management System (NIMS), 3rd Edition (2017) [3]	National standard for incident management; provides ICS, Unified Command, and JIS frameworks
FAA Order JO 7210.3 / FAA Notice N 7110.800 [5][6]	FAA procedures for UAP reporting; replaces "UFO" with "UAP" in air traffic directives
FAA Notice N 7210.970 [7]	FAA UAP activity notification procedures
AARO Mission and Reporting Framework [1][8]	DoD's All-domain Anomaly Resolution Office; centralized UAP analysis and reporting
50 U.S.C. § 3373	Statutory requirement for UAP reporting across the federal government
FY2023 NDAA — Whistleblower Protections [4]	Protections for government personnel reporting UAP-related information
UAP Disclosure Act of 2025 (FY2026 NDAA Amendment) [9]	Mandates UAP Records Collection at the National Archives and a Records Review Board
Robert T. Stafford Disaster Relief and Emergency Assistance Act [10]	Statutory authority for emergency management activities
Implementing Recommendations of the 9/11 Commission Act of 2007 [11]	Good-faith reporting immunity for suspicious activity reports
DHS UAS Best Practices [12]	Guidance on privacy, civil liberties, and response to unmanned systems
FEMA State and Local Guide 101 (SLG 101) [10]	Guidance for developing state and local emergency operations plans

Professional References

• FEMA NIMS Basic Guidance for Public Information Officers [13]
• Major Cities Chiefs Association UAP Reference Guide
• Standard HazMat response protocols and Comprehensive Emergency Management Plans [14][15]
• FAA Aeronautical Information Manual, Chapter 7 [16]
• FAA Facility Operation and Administration, Chapter 4 [17]

Unidentified Anomalous Phenomena (UAP): Any observed airborne, submerged, or transmedium object, light, effect, or incident that cannot be readily identified after initial review and may involve aerial, submerged, transmedium, environmental, sensor, or physical effects. This term officially replaces "UFO" across federal and air traffic control directives [5][6].

Unidentified Aerial Event (UAE): A neutral operational term for an observed airborne object, light, effect, or incident not immediately identified and potentially relevant to public safety, aviation safety, responder health, critical infrastructure, or situational awareness.

UxS / UAS Family: A broad operational category encompassing unmanned aerial systems (UAS), small UAS (s-UAS), unmanned aerial vehicles (UAVs), unmanned underwater vehicles (UUVs), remotely piloted vehicles (RPVs), drones, and similar systems.

Transmedium Movement: Observed characteristics showing transition between environments, such as moving from air into water or vice versa, or moving through solid barriers.

Deconfliction: The process of checking a report against known aircraft activity, airport operations, authorized drone activity, public safety aviation, military or industrial activity, weather, astronomical sources, utility work, scheduled events, and other known explanations.

Exposure Concern: A report involving possible injury, illness, burns, eye irritation, neurological symptoms, disorientation, unusual heat, radiation-like effects, electromagnetic effects, unknown odor, unknown material, or other atypical environmental condition potentially associated with a UAP/UAE event.

Evidence/Reporting Lead: The person designated by the Incident Commander or supervisor to coordinate documentation, digital media preservation, physical evidence handling, reports, and chain of custody for a UAP/UAE incident.

All-domain Anomaly Resolution Office (AARO): The centralized Department of Defense office responsible for synchronizing efforts across the U.S. government to detect, identify, and attribute anomalous phenomena, established by Congress within the DoD [1][8].

Domestic Events Network (DEN): The FAA's national security communication system used by the National Tactical Security Operations (NTSO) Air Traffic Security Coordinator (ATSC) for airspace-related security events, including UAP reports [7][17].

The jurisdiction shall use the following principles in all UAP/UAE operations:

Principle	Application
Observe	Collect neutral facts without interpretation
Protect	Prioritize life safety, responder safety, scene control, airspace awareness, and public protection
Coordinate	Use local, county, state, federal, airport, fusion center, public health, and critical infrastructure channels as appropriate
Communicate	Use plain language, verified facts, and no speculation

Guiding Standards

• All-hazards posture: Respond to consequences, not to the unknown origin of an event [3].
• First link, not final investigator: Local government is the first link in the national reporting chain, not the final investigative authority [1][16].
• Data quality matters more than witness certainty: The documentation mission focuses on preserving objective, measurable data regardless of subjective interpretation.
• Assess the patient, not the story: Medical personnel evaluate clinical findings based on symptoms and examination, not assumptions about cause.
• No new bureaucracy required: This SOP is a protocol, documentation, and training enhancement that operates within existing systems.

Local government is not the definitive scientific investigator. It is the well-prepared first link in a unified state and federal reporting chain. The following table summarizes the multi-tiered coordination framework:

Agency / Tier	Primary Local Role	Interagency Routing Pathway
911 Dispatch & Local Law Enforcement	First point of contact. Triages calls using standard intake script, logs CAD event, manages scene safety and life preservation.	Routes incident logs to local command and enters data into the records management system (RMS).
County/City EOC & Fire/EMS	Activates if an event escalates. Handles local HazMat containment, perimeters, and occupant medical care.	Coordinates directly with local public health, utility operators, and county/city leadership.
State / Regional Fusion Center	Serves as the regional intelligence hub to correlate local data with neighboring jurisdictions and radar anomalies.	Aggregates local reports and escalates established patterns to federal bodies.
FAA / Air Traffic Control (ATC)	Manages immediate flight safety, runway proximity hazards, and temporary airspace restrictions.	Routes air traffic security issues through the NTSO Air Traffic Security Coordinator team via the Domestic Events Network (DEN) [7][17].
All-domain Anomaly Resolution Office (AARO)	Centralized DoD clearinghouse for long-term federal analysis, case resolution, and attribution [1][8].	Local role is strictly limited to referring civilian reporters to AARO's public reporting portal at aaro.mil.
FBI / Federal Law Enforcement	Leads investigation if national security, criminal activity, or unknown craft crash is confirmed.	Local law enforcement contacts regional FBI field office; command may transition to federal lead [3].
CISA / DHS	Supports response if critical infrastructure, UAS incursion, or homeland security equities are involved.	Local contacts through existing DHS/CISA liaison or fusion center channels [12].

See Appendix E for the full multi-agency routing pathway.

8.1 Emergency Management

Emergency Management shall serve as the lead coordinating department for this SOP. Responsibilities include: maintaining this SOP, coordinating the UAP-related annex within the Emergency Operations Plan, maintaining interagency contact lists, coordinating exercises and training, supporting EOC activation, ensuring after-action review, and designating a liaison to monitor evolving FAA/AARO guidance.

8.2 911 / Dispatch / Communications

Dispatch shall receive reports, use the approved intake questions (Section 11 and Appendix A), enter the correct CAD/RMS category, screen for urgent hazards, advise callers not to approach or pursue unknown objects or debris, and notify supervisors according to this SOP.

8.3 Law Enforcement

Law enforcement shall provide scene security, initial threat assessment, witness identification, crowd control, traffic control, evidence protection, and coordination with appropriate aviation, fusion center, state, or federal partners when indicated.

8.4 Fire / HazMat

Fire and HazMat personnel shall manage unknown materials, debris, fire, smoke, odor, contamination, radiation or chemical indicators, unusual heat, electrical hazards, and responder protective measures. Fire departments typically assume the lead for HazMat control at scenes involving unknown materials [14].

8.5 EMS / Public Health

EMS shall assess and treat patients based on symptoms and clinical findings, not on assumptions about the cause of the event. Public Health shall support cluster tracking, exposure consultation, privacy protection, and coordination with hospitals, poison control, radiation control, or other specialty resources when appropriate.

8.6 Public Works / Utilities

Public Works and utilities shall assess impacts to roads, water, sewer, power, traffic signals, SCADA systems, communications, public facilities, and other infrastructure. They shall preserve relevant utility and SCADA data as potential evidence when directed by the Incident Commander.

8.7 Public Information Officer (PIO)

The PIO shall coordinate all public messaging, media responses, rumor control, elected-official briefings, website/social media updates, and Joint Information Center (JIC) activity if activated. All external messaging shall follow the guidelines in Section 20 and Appendix F.

8.8 City/County Attorney / Legal Counsel

Legal counsel shall advise on records, privacy, public statements, liability, evidence handling, interagency agreements, airspace-related authorities, and any release of sensitive information.

8.9 Standing Working Group

The jurisdiction shall authorize a standing cross-functional working group composed of representatives from Emergency Management, Dispatch, Fire/EMS, Law Enforcement, Public Health, Airport/Aviation Liaison, and PIO. This working group shall meet at least semi-annually to review SOP currency, exercise results, federal guidance changes, and interagency coordination. This group does not create new bureaucracy; it uses existing personnel in an advisory capacity.

Each department shall complete the following readiness measures:

1. CAD/RMS Category: Add or verify a dedicated CAD/RMS event type such as "Unidentified Aerial Event," "UAP/UxS Report," or equivalent to prevent miscoding under generic categories.
2. Standardized Report Form: Maintain the standardized report form (Appendix C).
3. Dispatch Intake Script: Maintain the approved dispatch intake script (Appendix A).
4. Supervisor Notification Criteria: Maintain written criteria for supervisory notification and escalation.
5. Contact List: Maintain a current contact list for: Emergency Management, Police Command, Fire/HazMat, EMS/Public Health, Airport Operations, FAA/Aviation Liaison, State/Regional Fusion Center, Utility Contacts, PIO, Legal Counsel, City/County Administration, FBI Field Office, CISA/DHS Liaison.
6. Training: Train dispatchers, patrol supervisors, fire/EMS supervisors, emergency management staff, PIOs, and command staff per Section 25.
7. Exercise Integration: Include a UAP/UxS scenario in the jurisdiction's annual exercise cycle per Section 25.
8. PIO Templates: Pre-approve holding statements, follow-up statement templates, and FAQ documents (Appendix F).
9. Annual Review: Review this SOP annually and after any significant incident, exercise, or change in federal guidance.

The jurisdiction shall use a four-tier response framework that scales incident management based on severity, scope, and consequence. Response is dictated by the consequences of the incident, not its unknown origin.

Level 1 — Information Only / No Immediate Hazard

Triggers: Event is no longer present; no injury or hazard reported; no critical infrastructure or aviation concern; caller only wishes to report the observation.

Actions:

• Document the report using the standardized form
• Provide non-emergency reporting guidance (e.g., AARO public portal at aaro.mil)
• Preserve media if relevant
• Forward report per local policy

Level 2 — Field Response

Triggers: Object is ongoing; multiple callers report the event; public concern exists; traffic disruption; possible drone activity; possible evidence; supervisor determines field assessment is appropriate.

Actions:

• Dispatch law enforcement or other appropriate unit
• Notify supervisor
• Begin deconfliction (Section 18)
• Document using standardized procedures
• Assign Evidence/Reporting Lead if warranted

Level 3 — Multi-Agency / Command Response

Triggers: Injury, illness, or exposure complaints; debris, fire, smoke, odor, or unknown material; critical infrastructure impact; airport/airspace concern; crowding; utility disruption; media surge; credible threat.

Actions:

• Establish Incident Command (ICS/NIMS) [3]
• Assign Safety Officer, Evidence/Reporting Lead, and PIO
• Dispatch Fire/HazMat and EMS as indicated
• Notify Emergency Management
• Establish perimeter and HazMat-first posture (Section 15)
• Begin appropriate external notifications (Section 19)
• Activate JIS/JIC if media/public interest warrants

Level 4 — EOC / Unified Command Activation

Triggers: Event affects multiple departments; creates major public concern; involves critical infrastructure; aviation disruption; hazardous materials; multiple patients; large crowds; major media attention; requires policy-level coordination; federal partner engagement.

Actions:

• Activate EOC or partial EOC [3]
• Establish Unified Command if multiple agencies have jurisdictional authority
• Activate Joint Information System / Joint Information Center [13]
• Brief city/county leadership and elected officials (Appendix D)
• Coordinate with county, state, and federal partners
• Consider requesting specialized assets (State/Regional HazMat Team, Civil Support Team, Bomb Squad) through appropriate channels

Dispatchers shall remain calm, neutral, and professional. Dispatchers shall not validate, ridicule, explain, or speculate about any report.

When safe and practical, dispatch shall obtain the following using the approved script (Appendix A):

1. Caller identity: Name, callback number, and current location.
2. Event location: Exact location by address, GPS coordinates, map pin, landmark, or cross street.
3. Status: Whether the event is ongoing.
4. Timing: Start time, end time, duration, and time zone if relevant.
5. Object count: Number of objects or effects observed.
6. Description: Shape, size impression, color, lights, sound, odor, altitude impression, attachments, emissions, dropped items, or released material.
7. Movement: Hovering, stationary, direction of travel, compass bearing if known, speed impression, abrupt acceleration, sudden direction change, descent, ascent, disappearance, or transmedium movement.
8. Proximity to critical infrastructure: Airport, helipad, public event, school, hospital, water facility, power facility, communications tower, government facility, military/defense facility, industrial site, or critical infrastructure.
9. Safety indicators: Injury, illness, burns, eye irritation, headache, disorientation, neurological symptoms, fire, smoke, crash, debris, odor, heat, electrical disturbance, power outage, vehicle malfunction, radio failure, GPS loss, phone/camera malfunction, or infrastructure impact.
10. Media preservation: Whether photos or videos exist. Instruct the caller to preserve original files and metadata; avoid editing, cropping, compressing, or posting the only original copy.
11. Additional witnesses: Whether other witnesses are present.
12. Obvious explanation check: Whether the caller has checked obvious possibilities (aircraft, drones, satellites, planets, weather, fireworks, known local activity) — only when doing so will not delay urgent response.

Dispatcher Safety Instruction (Read Verbatim When Applicable)

"Please do not approach, touch, disturb, or pursue the object or any debris. Move to a safe location. Keep others away if you can do so safely. Officers or responders will evaluate the situation."

CAD Entry Requirements

Dispatch shall create a CAD entry using the approved UAP/UxS or "Unidentified Aerial Event" category when a report involves an object, light, drone-like system, unexplained aerial event, transmedium report, unusual environmental effect, suspected debris, or exposure concern that is not immediately resolved.

The CAD entry shall include: incident number, date/time received, event location, caller location, whether ongoing, initial hazard indicators, responding units, supervisor notified, evidence indicators, public information sensitivity, referral or notification actions, and closure classification.

Closure Classifications

Code	Description
Known aircraft	Identified as conventional manned aircraft
Known drone / UAS	Identified as unmanned aerial system with known operator
Balloon	Identified as weather, commercial, or recreational balloon
Astronomical / weather	Identified as planet, star, meteor, satellite, atmospheric phenomenon
Fireworks / pyrotechnic	Identified as fireworks or pyrotechnic device
Hoax / unfounded	Determined to be false report or unfounded claim
Hazardous debris	Physical debris requiring HazMat assessment
Public safety drone incident	UAS event with public safety implications
Aviation safety concern	Event with aviation or airspace safety implications
Unresolved after initial review	Cannot be identified after initial field assessment
Referred to external agency	Forwarded to fusion center, FAA, FBI, AARO, or other agency
No response required	Informational report; no field response dispatched
Duplicate report	Same event reported by multiple callers

First-arriving personnel shall follow this 10-point protocol:

1. Size up from a safe distance. Do not rush toward an unknown scene.
2. Prioritize life safety. Address immediate threats to life before any documentation.
3. Do not approach, touch, disturb, or collect unknown material until hazards are assessed.
4. Establish a safe perimeter if debris, injury, unknown material, electrical effect, fire, smoke, odor, or unusual environmental condition is reported.
5. Keep bystanders away from any suspected hazard zone.
6. Request resources as indicated: Fire/HazMat, EMS, supervisor, airport/aviation liaison, public works, or utilities.
7. Identify witnesses and preserve original media. Instruct witnesses to retain original photos/videos without editing.
8. Record exact time, location (GPS), weather, direction of view, object movement, and apparent effects.
9. Assign or request an Evidence/Reporting Lead if the event requires documentation beyond routine CAD notes.
10. Avoid statements of origin, intent, or cause. All external communications go through the PIO.

The following flow provides an at-a-glance operational sequence for any UAP/UAE report. It is designed for quick-reference cards, training materials, and field guides.

[1. INTAKE] ──→ [2. SAFETY TRIAGE] ──→ [3. SCENE POSTURE] ──→ [4. EVIDENCE ARCHIVAL] ──→ [5. ROUTING]

Step	Action	Key Requirements
1. Intake	Dispatch receives report, uses standardized script, creates CAD entry under dedicated category.	Sections 11–12; Appendix A
2. Safety Triage	First-arriving units prioritize life safety, establish area control, isolate immediate hazards. Rapid deconfliction against known local activity (concurrent, does not delay protective actions).	Sections 13, 18
3. Scene Posture	If physical debris, ground impacts, fires, unknown materials, or unusual emissions are present → adopt HazMat-first posture. Establish standoff perimeter. Do not handle unknown materials without PPE and hazard assessment.	Section 15
4. Evidence Archival	Evidence/Reporting Lead preserves all data in original, unedited format. Logs timestamps, GPS, weather, flight dynamics, environmental/sensor anomalies. Secures body-cam, dash-cam, 911 audio, and user-submitted media with metadata intact.	Section 17; Appendix C
5. Routing	Complete standardized report form. Route to state/regional Fusion Center. Escalate aviation safety issues through FAA channels. Refer civilian reporters to AARO portal as appropriate. Notify per Section 19 triggers.	Section 19; Appendix E

When debris, unknown material, unusual heat, odor, emissions, burns, eye irritation, disorientation, neurological symptoms, equipment disruption, electromagnetic or microwave-like effects, or other exposure indicators are present, responders shall treat the scene as potentially hazardous until assessed [14][15].

Required Actions

1. Establish hot, warm, and cold zones as appropriate based on observed hazards.
2. Position personnel upwind, uphill, and upstream when relevant.
3. Limit personnel in the hazard area to essential operations only.
4. Use appropriate PPE based on known and suspected hazards.
5. Do not directly handle debris or unknown material. Observe and photograph from a safe distance.
6. Photograph items in place before any movement to preserve forensic context.
7. Request specialized resources as needed: HazMat team, radiation detection, gas monitoring, environmental health, public works, utility, or specialty resources.
8. Document instrument readings — including negative readings — with time and location of each measurement.
9. Maintain chain of custody for any collected item.
10. Consider decontamination procedures if contamination is suspected or indicated by instrument readings.

Electromagnetic / Microwave-Like Exposure Hazard

Close-proximity encounters with anomalous phenomena have occasionally been correlated with localized electromagnetic (EM) or microwave-like exposures rather than typical thermal heat. Responders and safety officers shall be alert to the following indicators:

• Skin burns or localized radiation-like erythema without an obvious heat source
• Eye irritation, corneal injuries, or temporary visual disturbance
• Nausea, severe headaches, disorientation, or acute neurological symptoms
• Equipment malfunction, compass deviation, or communication interference

When these indicators are present, increase standoff distance, limit exposure time, and ensure medical screening per Section 16.

EMS and medical personnel shall assess exposed persons according to ordinary medical standards. Assess the patient, not the story. Personnel shall not dismiss symptoms because the reported cause is unusual.

Clinical Assessment

Assessment should include, as clinically appropriate:

• Vital signs and mental status
• Skin findings, burns, or localized erythema
• Eye irritation, visual disturbance, or corneal findings
• Headache, dizziness, nausea, or weakness
• Numbness, tingling, or neurological symptoms
• Respiratory symptoms or chest pain
• Disorientation, confusion, or acute stress response
• Exposure history: distance from object/debris, duration of exposure, protective actions taken
• Whether other persons have similar symptoms (cluster identification)

Medical Procedures

1. Document clinical findings in protected medical records — separate from the tactical incident report to preserve patient privacy under applicable law.
2. Keep protected health information separate from operational reports except as legally permitted or required.
3. Encourage follow-up evaluation when symptoms persist or worsen.
4. Notify Public Health when multiple persons report similar symptoms (cluster surveillance).
5. Consult specialty resources when indicated: poison control, radiation control, occupational health, emergency department leadership.
6. Conduct follow-up health checks for exposed personnel at the start of their next shift, and again between 24–72 hours post-incident.
7. Brief local emergency departments and county health officials on the potential for atypical exposure presentations following a significant event.

Core Patient-Facing Message

"You are safe to report symptoms. We will evaluate medically and document carefully."

The Evidence/Reporting Lead shall coordinate all documentation. The goal is to preserve facts before they disappear. Data quality matters more than witness certainty.

Documentation Requirements

Category	Required Data Points
Time	Exact date and time in both local time and UTC. Time synchronization information for cameras, phones, body cameras, CAD, radio logs, and other systems.
Location	GPS coordinates or mapped location of observer, object, debris, and response units. Direction of view, compass bearing, elevation estimate, landmarks, and line of sight.
Environment	Weather conditions: visibility, cloud cover, precipitation, wind speed/direction, temperature. Moon phase and planet visibility if relevant.
Witness	Names, contact information, and neutral witness statements. Number of independent witnesses.
Object/Event	Description of object, light, sound, odor, motion characteristics, duration, and manner of disappearance.
Effects	Any associated injury, illness, equipment effect, power disruption, vehicle effect, radio/GPS issue, SCADA anomaly, or infrastructure impact.

Digital and Physical Evidence Preservation

All evidence shall be preserved in original form with metadata intact:

• Photographs and video (civilian and responder)
• Body-camera footage
• Dispatch audio recordings
• Radio traffic recordings
• CAD notes and logs
• ALPR or traffic camera records (if relevant and lawfully available)
• Facility security video (if relevant and lawfully obtained)
• Sensor, radar, drone-detection, utility, SCADA, or other technical data (if lawfully available)
• Chain-of-custody records for all physical and digital evidence

Critical Rule: Original media shall not be edited, cropped, compressed, renamed, overwritten, or transmitted in a way that destroys metadata. Original files must be preserved in their original form. Working copies may be created for analysis purposes.

As soon as practical — and without delaying urgent safety actions — the supervisor or designee shall conduct reasonable deconfliction to identify conventional explanations.

Deconfliction Checks

• Known aircraft (commercial, private, military)
• Airport operations and departure/arrival schedules
• Public safety aviation (police/medical helicopters)
• Authorized drone operations and UAS flights
• Temporary flight restrictions (TFRs)
• Public events (fireworks displays, celebrations, light shows)
• Utility work (line maintenance, tower lights, flares)
• Industrial operations (flares, steam, lighting)
• Weather balloons and radiosonde launches
• Satellites, planets, and astronomical events
• Weather phenomena (lenticular clouds, sundogs, ball lightning)
• Military or defense-related activity
• Nearby critical infrastructure operations
• Prior similar calls and social media reports
• Neighboring jurisdiction reports

Documentation of Deconfliction

Deconfliction shall be documented regardless of outcome. If a likely explanation is identified, the report may be closed under the appropriate CAD/RMS classification (Section 12), but the original report shall remain professionally documented and retained. Even a resolved case may contribute to pattern analysis.

The Incident Commander, supervisor, or Emergency Management Director shall determine notifications based on the incident type, severity, and applicable triggers.

Notification Contacts (as applicable)

Contact	When to Notify
Police / Sheriff Command	All Level 2+ events
Fire Command	Debris, fire, HazMat, environmental hazard
EMS Supervisor	Injury, illness, or exposure complaint
Emergency Management Director	All Level 3+ events
PIO	Public concern, media interest, social media activity
City/County Manager	Level 3+ events, elected official inquiries
Mayor / Elected Officials	Level 4 events, significant public concern (via City Manager)
City/County Attorney	Evidence, liability, records, or public release questions
State / Regional Fusion Center	All documented incidents for correlation analysis
Airport Operations	Any event in airport vicinity or affecting airspace
FAA / Aviation Liaison	Aviation safety concerns → ATC → NTSO via DEN [7][17]
FBI Field Office	Confirmed crash of unknown craft, national security concern, criminal activity
CISA / DHS	Critical infrastructure impact, UAS incursion, homeland security concern [12]
Public Health / Environmental Health	Multiple exposure complaints, cluster symptoms
Hospitals / Poison Control	Unusual exposure presentations
Utilities / Public Works	SCADA, power, water, or communications disruption
School District	Event near schools during operational hours
Neighboring Jurisdictions	Cross-boundary events or similar concurrent reports

Notification Triggers

Notifications shall be initiated when any of the following conditions exist:

• Injury, illness, or exposure complaint
• Debris or unknown material on the ground
• Fire, smoke, odor, or suspected contamination
• Airport or airspace concern
• Object near critical infrastructure
• Multiple independent reports of the same event
• Media interest or social media escalation
• Public panic or community concern
• Utility disruption or SCADA anomaly
• Radio, GPS, or electronic interference affecting operations
• Credible threat assessment
• Law enforcement safety concern
• Need for regional, state, or federal coordination

Role Clarification: The local role is to document, protect, coordinate, refer, and defer. Local agencies handle first response, perimeter, medical care, and documentation. State partners support correlation and analysis. Federal entities handle broader investigation and attribution.

A UAP incident will generate intense public and media interest. Public information vacuums are quickly filled by social media speculation and misinformation. The PIO shall manage external communications using a strategy of controlled transparency — relying exclusively on verified facts while avoiding speculation about origin, attribution, or intent [13].

PIO Objectives

1. Acknowledge reports when public concern exists.
2. State what is known.
3. State what is being assessed.
4. State what the public should do (safety actions, areas to avoid).
5. State where official updates will be posted.
6. Avoid speculation about origin, intent, or cause.
7. Protect witness, caller, patient, and responder privacy.
8. Correct misinformation and rumors when necessary.
9. Use accessible formats and major local languages when appropriate.
10. Coordinate messaging with partner agencies through JIS/JIC [13].

Joint Information System / Joint Information Center

For significant incidents (Level 3–4), a Joint Information Center (JIC) should be established — physically or virtually — to bring together PIOs from all responding agencies (local, state, federal) to coordinate and approve messaging. This ensures a "one message, many voices" approach [13].

Approved Templates

See Appendix F for:

• Initial holding statement
• Follow-up statement template
• Media FAQ template
• Social media response guidance

The jurisdiction shall maintain a non-punitive reporting environment for all personnel who make or forward good-faith reports of unidentified aerial events, equipment anomalies, exposure concerns, or witness statements.

Supervisory Standards

• Supervisors shall not ridicule, demean, retaliate against, or automatically refer personnel for psychological evaluation solely because they reported an unusual aerial event.
• This policy does not prevent normal supervisory review, fitness-for-duty processes based on objective safety concerns, false-report investigation, or other lawful personnel action when independently justified.

Leadership Message

UAP/UxS reports are handled with the same professional neutrality as hazardous materials reports, aviation near-misses, suspicious activity reports, or infrastructure safety concerns. The goal is documentation and safety, not ridicule or speculation.

Federal Context

Federal whistleblower protections established in the FY2023 NDAA protect current and former government employees, service members, and contractors from reprisal for authorized UAP disclosures to AARO [4]. This local non-punitive policy mirrors and extends that principle to municipal and county personnel.

Records shall be maintained according to the jurisdiction's records retention schedule, evidence policy, public records law, medical privacy law, criminal justice information policy, and legal counsel guidance.

Special Handling Categories

The following categories require enhanced privacy protections:

• Medical records and protected health information (PHI)
• Juvenile information
• Witness identities (when protection is warranted)
• Law enforcement sensitive information
• Critical infrastructure details and locations
• Security camera positions and capabilities
• Airport and aviation security information
• Proprietary utility or SCADA data
• Federal or state partner information marked as sensitive
• Evidence related to an ongoing criminal investigation

Records Retention

All incident data, sensor data, evidence records, and documentation shall be maintained under a dedicated, secure retention schedule sufficient for:

• Long-term trend and pattern analysis
• Federal reporting requirements
• Legal and administrative requirements
• After-action review and training purposes

Public Release

Public release of records shall be coordinated through the PIO and legal counsel in accordance with applicable public records laws and the privacy protections above.

Before demobilizing from any Level 2+ incident, the Incident Commander or supervisor shall complete the following 10-point closeout checklist:

#	Closeout Action	Verified
1	Life safety issues are resolved or transferred to appropriate authority	☐
2	Hazard zones are cleared, secured, or transferred	☐
3	All evidence and media are preserved with documented chain of custody	☐
4	Witness information is documented and contact details recorded	☐
5	All required notifications are complete	☐
6	Public messaging is updated or formally closed	☐
7	Medical follow-up is arranged for exposed personnel	☐
8	Equipment is checked, decontaminated, or flagged for replacement	☐
9	All reports are completed and submitted	☐
10	After-Action Review requirement is determined (mandatory for Level 3–4)	☐

For any Level 3 or Level 4 incident — or any incident designated by the Emergency Management Director — an After-Action Review (AAR) shall be completed within 72 hours when practical.

AAR Scope

The review shall address:

• Complete event timeline (call intake through demobilization)
• Dispatch coding accuracy and intake quality
• Response level appropriateness
• Scene safety and HazMat posture effectiveness
• Command structure and ICS implementation
• Evidence preservation and chain-of-custody integrity
• Medical issues and exposure tracking
• Public health coordination
• Deconfliction steps and results
• Notification completeness and timeliness
• Public information effectiveness and rumor control
• Elected official briefings and political management
• Partner agency coordination
• Legal issues and records management
• Operational gaps and resource shortfalls
• Corrective actions required
• Training needs identified
• SOP updates recommended

AAR Outputs

Findings shall be used to update: SOPs, report forms, dispatch scripts, training curricula, exercise scenarios, contact lists, PIO templates, and records-retention practices.

Training Requirements

The jurisdiction shall provide periodic training to all affected personnel. Training topics shall include:

Topic	Target Audience
Dispatch intake procedures and CAD coding	Dispatchers, Communications Supervisors
Neutral terminology and non-punitive reporting culture	All personnel
Scene safety and HazMat-first posture for unknown debris	Fire, HazMat, Law Enforcement, EMS
EMS exposure screening and clinical documentation	EMS, Public Health, Hospital Liaisons
Evidence and metadata preservation / chain of custody	Law Enforcement, Fire, Evidence Technicians
Deconfliction procedures	Patrol Supervisors, Command Staff
Aviation and airport notification pathways	Emergency Management, Law Enforcement, Dispatch
Fusion center reporting and routing	Emergency Management, Law Enforcement
PIO messaging, rumor control, and JIS/JIC operations	PIOs, Emergency Management
Privacy protections and records management	All personnel, Legal Counsel
Elected official briefing and political management	Emergency Management, PIO, City/County Manager
Tiered response framework and ICS integration	All first responders, Command Staff

Exercise Requirements

At least once per year, the jurisdiction shall include a UAP/UxS inject in a tabletop or functional exercise. A practical 90-minute scenario should test:

• Multiple simultaneous 911 calls
• Social media video emergence and viral spread
• A possible exposure complaint from a witness or responder
• Airport proximity or airspace notification requirements
• Evidence handling and metadata preservation decisions
• PIO messaging under pressure
• Elected official briefing in real-time
• Interagency coordination (fusion center, FAA, state EM)
• Transition from Level 2 to Level 3 or Level 4

Integration with Existing Training

UAP/UAE procedures shall be integrated into existing all-hazards training, EOP updates, multi-agency exercises, and new-employee orientation as appropriate. No separate training infrastructure is required.

This phased implementation plan transforms this SOP from a document into an operational capability.

Phase 1: Days 1–30 — Foundation

Task	Responsible
Assign lead department and designate SOP coordinator	City/County Manager
Create standing working group (EM, Dispatch, Fire, LE, PH, Airport, PIO)	Emergency Management
Inventory existing SOPs, EOP annexes, and mutual aid agreements	Emergency Management
Draft dispatch intake script (or adopt Appendix A)	Dispatch / Communications
Create interagency contact list with current phone/email	Emergency Management
Identify airport, fusion center, public health, utility, and FAA contacts	Emergency Management
Brief city/county leadership on SOP purpose and scope	Emergency Management

Phase 2: Days 31–60 — Development

Task	Responsible
Draft EOP annex incorporating this SOP	Emergency Management
Create or finalize CAD/RMS event category and closure codes	Dispatch / IT
Finalize standardized report form (or adopt Appendix C)	Emergency Management / LE
Prepare PIO holding statements and FAQ documents (or adopt Appendix F)	PIO
Draft evidence and debris handling procedure	LE / Fire / Evidence Unit
Create supervisor training module (60-minute briefing)	Emergency Management
Coordinate with legal counsel on records, privacy, and liability	City/County Attorney

Phase 3: Days 61–90 — Activation

Task	Responsible
Conduct tabletop exercise using UAP/UxS scenario	Emergency Management
Complete after-action improvements from exercise	Working Group
Formally adopt EOP annex through appropriate approval authority	City/County Manager
Finalize and distribute field job aids (Appendices A–G)	Emergency Management
Brief elected officials using Appendix D guidance	Emergency Management / City Manager
Set annual review and exercise cadence	Emergency Management
Report implementation completion to governing body	Emergency Management

The following language is provided for use by the City Council, County Commission, Board of Supervisors, or equivalent governing body to formally authorize implementation:

RECOMMENDED ACTION:

Direct the Emergency Management Director [or appropriate designee] to incorporate the UAP/Unidentified Aerial Event reporting annex into the next Emergency Operations Plan revision cycle. Authorize brief training for dispatch and supervisors, approve standing PIO templates, and designate a liaison to monitor evolving FAA and AARO guidance.

This is a no-regrets, low-cost measure that positions [City/County Name] as a well-prepared first link in the national reporting chain. It requires no new bureaucracy, no new capital expenditure, and no assumption about the nature or origin of reported events. It ensures that our jurisdiction handles these reports with the same professionalism applied to any other public safety incident — protecting our residents, our responders, and our institutional credibility.

This script is designed to be read naturally. Not all questions will apply to every call. Dispatchers should use professional judgment and prioritize caller safety.

Opening:

"911, what is the address or location of your emergency?"

Immediate safety screen:

"Are you in immediate danger, injured, or seeing fire, smoke, debris, or a crash?"

Location:

"Where exactly is the object or event? Can you provide a map pin or GPS location?"

Timing:

"When did it start? Is it still happening?"

Description:

"What do you see? Shape, color, lights, sound, movement, direction, and number of objects?"

Proximity:

"Is it near an airport, school, hospital, event, power facility, water facility, tower, or government site?"

Effects:

"Are phones, radios, GPS, vehicles, lights, or power systems acting unusually?"

Media preservation:

"Do you have photos or video? Please preserve the original files and do not edit or delete them."

Safety instruction:

"Do not approach, touch, or pursue anything. Move to a safe location and keep others away if you can do so safely."

Close:

"Officers/responders will evaluate the situation. Is there anything else you'd like to report?"

Safety

• Size up from safe distance
• Establish perimeter if hazards present
• Use PPE appropriate to observed/suspected hazards
• Keep public and bystanders away
• Avoid handling unknown debris or material
• Position upwind, uphill, upstream from unknown materials

Medical

• Check for burns, eye irritation, headache, dizziness
• Check for nausea, neurological symptoms, disorientation
• Check for respiratory issues, anxiety, acute stress
• Document exposure history (distance, duration, protective actions)
• Arrange follow-up checks for exposed personnel

Documentation

• Record exact time (local + UTC) and synchronize devices
• Record GPS coordinates of observer, object, and debris
• Record weather conditions (visibility, cloud, wind, temperature)
• Obtain witness names, contact information, and statements
• Record direction of view, compass bearing, elevation, landmarks
• Describe object: shape, color, lights, sound, odor, motion, duration
• Record all associated effects (equipment, power, communications)

Evidence

• Preserve all original digital files with metadata
• Secure body-camera, dash-cam, and 911 audio
• Photograph items in place before any movement
• Label and log all physical items
• Restrict access to evidence area
• Document all evidence transfers (chain of custody)
• Record instrument readings — including negative readings

Notifications

• Supervisor
• Emergency Management
• Fire/HazMat (if debris/material present)
• EMS/Public Health (if exposure concern)
• PIO (if public/media interest)
• Airport/FAA liaison (if aviation concern)
• State/Regional Fusion Center
• Utilities/Public Works (if infrastructure impact)
• Legal counsel (if evidence/liability questions)
• City/County administration (Level 3+)

PIO

• Single official communication channel identified
• Holding statement prepared/issued
• Rumor log started
• Next update time established
• No speculation in any public messaging

Closeout

• Demobilize safely (10-point checklist, Section 23)
• Preserve all evidence and documentation
• Complete standardized report form
• Determine AAR requirement

The following fields comprise the minimum data set for any UAP/UAE report. Jurisdictions may add locally required fields.

Field	Data Required
Incident Number	CAD/RMS case number
Date / Time	Local time and UTC
Reporting Party	Name, agency/affiliation, contact information
Observer Location	Address, GPS coordinates, or landmark
Object/Event Location	Address, GPS coordinates, or estimated position
Start / End Time	Duration of observation
Number of Objects	Count of distinct objects or effects
Object Type (if apparent)	Drone, balloon, aircraft, light, unknown, other
Shape	Round, triangular, cylindrical, irregular, amorphous, other
Color	Observed color(s) and any changes
Lights	Color, pattern, intensity, flashing/steady
Sound	Humming, roaring, silent, pulsing, other
Odor	Chemical, metallic, burning, ozone, none, other
Movement	Hovering, linear, erratic, ascending, descending, transmedium
Speed Impression	Slow, fast, instantaneous acceleration, stationary
Direction / Bearing	Compass direction, bearing in degrees if known
Altitude Impression	Ground level, treetop, low, medium, high, orbital
Attachments / Features	Appendages, markings, exhaust, contrail, emissions
Dropped Items	Debris, material, liquid, none observed
Manner of Disappearance	Gradual, sudden, behind terrain, into water, unknown
Nearby Infrastructure	Airport, school, hospital, power plant, government facility, military site
Injuries / Symptoms	Type, number of persons affected, severity
Equipment Effects	Radio, GPS, phone, camera, vehicle, power, SCADA
Weather Conditions	Visibility, cloud cover, precipitation, wind, temperature, moon phase
Photos / Video Available	Yes/No; original media preserved?
Witnesses	Names, count, contact information
Deconfliction Performed	Checks completed and results
Notifications Made	Agencies and times notified
Evidence Collected	Items, digital files, chain-of-custody numbers
Supervisor Review	Name, date, disposition
Closure Classification	Per Section 12 codes

Recommended Posture: Serious, Calm, Transparent, Consequence-Based

Do:

• Use neutral language (e.g., "unidentified aerial event," "the reported incident")
• Support preparedness as a responsible public safety measure
• Ask staff for written escalation criteria and verified facts before making public statements
• Support public transparency about what is known and what is being assessed
• Defer technical conclusions to qualified investigators and federal authorities
• Emphasize the jurisdiction's professional, all-hazards approach

Do Not:

• Declare or speculate about origin, nature, or intent
• Ridicule witnesses, reporters, or responders
• Promise answers before an assessment or review is complete
• Direct personnel to take unsafe actions at a scene
• Release unverified information to the public or media
• Make statements that could compromise an ongoing investigation

Sample Elected Official Statement

"Our public safety team has documented the reported event and is coordinating with appropriate state and federal partners. We are focused on ensuring the safety of our community. We will provide updates as verified information becomes available. We take all public safety reports seriously and handle them with professionalism."

The following table outlines the scalable multi-agency response pathway for a significant UAP/UAE incident, from initial public report through potential federal transition of command [1][3][7][13][14][17].

Phase	Action	Lead Agency	Key Partners
1. Initial Report	Member of public calls 911 to report UAP sighting, low-altitude event, crash, or related threat.	911 Dispatch / PSAP	—
2. Initial Response	First responders dispatched. Arrive on scene, establish ICS, assess life-safety threats, secure perimeter. HazMat posture if debris present.	Local LE or Fire	Fire/EMS, Public Works
3. Airspace Coordination	If event is ongoing in the air or involves airport, IC notifies nearest FAA ATC facility.	Incident Commander	FAA ATC, Airport Ops
4. Federal Aviation Notification	FAA ATC notifies NTSO via Domestic Events Network (DEN). Event enters national security reporting.	FAA	NTSO, AARO (data sharing)
5. EOC & JIC Activation	Local EOC activated for resource coordination and information management. JIC established for public/media communications.	Local Emergency Mgmt	All responding agencies, PIOs
6. Specialized Response	If debris or physical evidence exists, IC requests specialized assets (HazMat team, Civil Support Team, Bomb Squad).	IC via Local EOC	State EM, National Guard
7. Federal LE / National Security	If confirmed unknown craft crash, national security concern, or criminal activity, local LE notifies regional FBI field office.	Local LE	FBI, DHS
8. Transition of Command	If federal jurisdiction is asserted, command transfers from local UC to lead federal agency. Local government transitions to support role.	Lead Federal Agency	Local UC (support)

Initial Holding Statement

"We are aware of the reports regarding an unidentified aerial event in the area of [Location]. Local public safety units have established a standard safety perimeter, documented the initial reports, and confirmed there is no immediate threat to neighborhood safety. The technical data has been referred to appropriate state and federal aviation authorities for further assessment. Official updates will be posted to [City Portal / Social Media Channel] as verified details become available."

Follow-Up Statement Template

"Public safety personnel have completed an initial assessment of the reported event near [general location]. The [City/County] has documented witness reports, preserved available information, and coordinated with appropriate partners. [Insert verified safety information only.] Anyone with original photos or videos should preserve the original files and contact [agency/method]. The [City/County] will provide additional updates if new verified information becomes available."

Frequently Asked Questions (Pre-Approved Responses)

Q: What did people see?

"We have received reports of an unidentified aerial event. We are documenting the reports and assessing the situation."

Q: Was it a UFO / alien craft / military experiment?

"We do not speculate about the origin or nature of unidentified events. Our focus is on public safety, documentation, and coordination with appropriate authorities."

Q: Is it safe?

"Based on our current assessment, [there is no immediate threat to public safety / we have established a safety perimeter as a precaution and residents should avoid the area of (location)]."

Q: Who is investigating?

"Our public safety team has documented the event and is coordinating with appropriate state and federal partners, including aviation authorities."

Q: Where can the public report a sighting?

"For emergencies, call 911. For non-emergency reports, contact [local non-emergency number]. The Department of Defense's All-domain Anomaly Resolution Office (AARO) also maintains a public information portal at aaro.mil."

Q: Will you release footage or evidence?

"Any release of records will follow applicable public records laws and will be coordinated through our public information office and legal counsel."

For use by EMS, emergency departments, occupational health, and public health personnel.

Screening Triggers

Conduct medical screening when any person (responder, witness, or civilian) reports or exhibits symptoms following proximity to a UAP/UAE event, including:

• Skin burns, redness, or radiation-like erythema
• Eye irritation, corneal injury, or temporary blindness
• Severe headache, nausea, or dizziness
• Disorientation, confusion, or cognitive impairment
• Numbness, tingling, or neurological deficits
• Respiratory distress
• Anxiety or acute stress reaction

Assessment Protocol

1. Triage using standard medical protocols. Treat symptoms as presented.
2. Document clinical findings thoroughly, including: vital signs, skin/eye exam, neurological status, exposure timeline, distance from event, duration of exposure, and protective actions taken.
3. Separate medical records from tactical incident reports. Protected health information must be handled per HIPAA and applicable state law.
4. Report clusters — if two or more persons present with similar symptoms from the same event, notify Public Health immediately.
5. Consult poison control, radiation health, or occupational medicine specialists as indicated by symptoms.
6. Follow up — mandatory check at next shift and at 24–72 hours post-exposure for all personnel with documented exposure.
7. Brief hospitals — provide advance notification to local emergency departments about the type of exposure presentations that may present following a significant event.

Clinical Reminders

• Assess the patient, not the story. Clinical evaluation is based on symptoms and findings, not the circumstances of the report.
• Do not dismiss unusual presentations. Atypical burn patterns, non-thermal radiation-like effects, and acute neurological symptoms without apparent cause warrant thorough evaluation and documentation.
• Patient reassurance message: "You are safe to report symptoms. We will evaluate medically and document carefully."

The following sources informed the development of this SOP. Numbers in brackets [#] throughout the document correspond to this reference list.

Ref	Source	URL
[1]	AARO — Submit a Report (reporting pathways and eligibility)	https://www.aaro.mil/Submit-A-Report/
[2]	AARO Mission Brief (2025)	https://www.aaro.mil/Portals/136/PDFs/AARO_Mission_Brief_2025.pdf
[3]	FEMA — National Incident Management System (NIMS), 3rd Edition (October 2017)	https://training.fema.gov/emiweb/is/is700b/handouts/national_incident_management%20system_third%20edition_october_2017.pdf
[4]	DoD — FY2024 Consolidated Annual Report on UAP (November 2024)	https://media.defense.gov/2024/Nov/14/2003583603/-1/-1/0/FY24-CONSOLIDATED-ANNUAL-REPORT-ON-UAP-508.PDF
[5]	FAA Notice N 7210.970 — UAP Activity Notification Procedures	https://www.faa.gov/documentLibrary/media/Notice/2025-09-25_Notice_N7210.970_Unidentied_Anomalous_Phenomena_(UAP)_Activity_FINAL.pdf
[6]	FAA Notice N 7110.800 — UAP Reports	https://www.faa.gov/documentLibrary/media/Notice/2025-09-12_Notice_N7110.800_Unidentied_Anomalous_Phenomena_(UAP)_Reports_FINAL.pdf
[7]	FAA Order JO 7210.3EE (Change 2, January 2026)	https://www.faa.gov/documentLibrary/media/Order/7210.3EE_Chg_2_dtd_1-22-26_Final.pdf
[8]	AARO — DD Form 3212 (UAP Program Report)	https://www.aaro.mil/Portals/136/PDFs/UAP_Program_Report/DD_3212.pdf
[9]	U.S. Congress — UAP Disclosure Act of 2025 (Senate Amendment 3111, 119th Congress)	https://www.congress.gov/amendment/119th-congress/senate-amendment/3111/text
[10]	FEMA — State and Local Guide 101 (SLG 101) / Stafford Act Authority	https://www.fema.gov/pdf/plan/slg101.pdf
[11]	Implementing Recommendations of the 9/11 Commission Act of 2007 (P.L. 110-53)	https://www.congress.gov/110/plaws/publ53/PLAW-110publ53.htm
[12]	DHS — UAS Best Practices (Privacy, Civil Rights, Civil Liberties)	https://www.dhs.gov/sites/default/files/publications/UAS%20Best%20Practices.pdf
[13]	FEMA — NIMS Basic Guidance for Public Information Officers (December 2020)	https://www.fema.gov/sites/default/files/documents/fema_nims-basic-guidance-public-information-officers_12-2020.pdf
[14]	Standard HazMat Response Protocols (Idaho OEM Reference Plan, 2013)	https://ioem.idaho.gov/wp-content/uploads/2022/04/HazMat-Plan-2013.pdf
[15]	FEMA — Developing and Maintaining Emergency Operations Plans (Comprehensive Preparedness Guide 101, v3, 2021)	https://www.fema.gov/sites/default/files/documents/fema_cpg-101-v3-developing-maintaining-eops.pdf
[16]	FAA Aeronautical Information Manual, Chapter 7, Section 7	https://www.faa.gov/air_traffic/publications/atpubs/aim_html/chap7_section_7.html
[17]	FAA — Facility Operation and Administration, Chapter 4, Section 7	https://www.faa.gov/air_traffic/publications/atpubs/foa_html/chap4_section_7.html
[18]	AARO — Historical Record Report, Volume 1 (2024)	https://www.aaro.mil/Portals/136/PDFs/AARO_Historical_Record_Report_Vol_1_2024.pdf
[19]	Congressional Hearing Transcript — House Oversight Subcommittee, UAP Witness Testimony (November 2024)	https://www.congress.gov/118/meeting/house/117721/witnesses/HHRG-118-GO12-Wstate-GallaudetPhDRearAdmiralUSNavyRetT-20241113.pdf
[20]	Congressional Hearing Record — 119th Congress, House UAP Hearing (CHRG-119hhrg61718)	https://www.congress.gov/119/chrg/CHRG-119hhrg61718/CHRG-119hhrg61718.pdf

Document Control

Version	Date	Author	Changes
1.0	[Insert Date]	[Emergency Management Director / Working Group]	Initial adoption

Next Scheduled Review: [Insert Date — 12 months from effective date]

This SOP is a living document subject to annual review and revision based on lessons learned, federal guidance changes, exercise outcomes, and operational experience. Questions regarding this SOP should be directed to the Emergency Management Director.

End of Document