Executive Summary

Medical helicopter operations and ground first responders increasingly share airspace with small unmanned aircraft systems (sUAS or “drones”). At hospital heliports and ad‑hoc landing zones (LZs) near accident scenes, unauthorized or uncoordinated drones can force go‑arounds, delay patient transport, and create unacceptable collision risk. Portable, field‑deployable drone detection—especially systems that decode FAA Remote ID (RID)—gives pilots, LZ officers, and incident commanders immediate situational awareness so they can hold, re‑route, or coordinate with law enforcement before an incident occurs.

Liability note: With fixed detectors now available under $10,000 and portable units well under $1,500, operators who forgo detection may face heightened liability exposure if an incident results in injury or loss of life (consult counsel and risk management).

Recent proof points: In Linn County, Oregon (Sep 4, 2024) a civilian drone prevented a Life Flight Network landing at a fatal I‑5 crash scene (EMS1). In Orangefield, Texas (Feb 9, 2025), a drone in the LZ delayed a medevac for a 3‑year‑old drowning victim; a misdemeanor charge followed in June 2025 (12NewsNow).

Key takeaways

• Heliports are uniquely vulnerable. Final approach/departure paths, safety areas, and protection zones must remain obstruction‑free; small drones are difficult to see and can penetrate these volumes unnoticed.
• Accident scenes attract drones. Bystanders, media, and hobbyists often launch near crashes and fires. That airspace also hosts medevac helicopters and agency sUAS—raising the risk of mid‑air conflicts.
• Portable detection closes the awareness gap. A go‑bag receiver at the LZ can confirm a “clear deck,” identify RID‑equipped aircraft, and highlight non‑compliant or unknown tracks that warrant a hold or police response.
• Standard operating procedures (SOPs) matter. Simple checklists, alert thresholds, and deconfliction roles reduce delays while protecting crews and patients.

1) Why Heliports Need Drone Detection

1.1 Heliport geometry leaves little margin

Hospital heliports incorporate a Touchdown and Liftoff Area (TLOF), Final Approach and Takeoff Area (FATO), Safety Area, and associated approach/departure surfaces. These volumes must be kept clear for safe operations. Small drones are hard to visually acquire, especially at dusk/night or against complex urban backgrounds. A quadcopter in the approach fan can force a go‑around or result in a rotor/airframe strike. Even a near‑miss elevates crew workload at the most critical phase of flight.

1.2 Urban and suburban siting increases exposure

Many hospital heliports sit atop rooftops or adjacent to parking structures, surrounded by residential and commercial buildings. Nearby balconies, parks, and parking lots become ad‑hoc drone launch points. Without detection, security teams and pilots often discover conflicts only after a drone is seen—sometimes too late to safely continue the approach.

1.3 Consequence of delay is clinical

If a medevac is waved off by a drone incursion, door‑to‑needle and scene‑to‑surgery times suffer. Minutes matter for trauma, stroke, and STEMI patients. Detection provides an objective basis to hold, clear, and resume operations quickly once the airspace is verified clear.

2) Why First Responders Need Portable Detection at Accident Scenes

2.1 Accident scenes have many drones in the air

Crash scenes and fire grounds draw attention. Curious hobbyists, freelance media, and well‑meaning bystanders frequently launch to capture footage. Simultaneously, public safety UAS may be overhead for overwatch, mapping, or search. Without coordination, drone‑to‑helicopter and drone‑to‑drone conflicts are likely.

2.2 LZ officers need objective airspace status

Before designating or activating a Landing Zone (LZ), incident command should verify a “cold” airspace (no unauthorized sUAS) within a practical scan radius (e.g., ~1,000‑ft) around the receiver. A portable detector confirms:

• Which drones are broadcasting RID (ID, location, altitude, pilot takeoff location where available).
• Which tracks appear non‑RID or unknown, supporting a temporary hold or law‑enforcement tasking.
• Trends (approaching/loitering) that indicate potential intent or ignorance of the hazard.

2.3 Protecting agency sUAS: “drones vs. drones”

At many scenes, responders themselves fly sUAS. Risks include: mid‑air collision (most small drones lack detect‑and‑avoid), loss of separation with medevac helicopters during approach/escape, and RF crowding/GNSS anomalies in dense urban RF or metallic debris fields. Real‑time detection helps the UAS coordinator deconflict agency aircraft from unknown drones and from the inbound helicopter.

Callout (Oregon, 2024): “It is a large safety risk we do not undertake.” — Life Flight Network spokesperson, after a civilian drone prevented an I‑5 crash‑scene landing (EMS1/OregonLive).

Callout (Texas, 2025): 12NewsNow reported a drone directly above the LZ delayed a medical helicopter during a rescue of a 3‑year‑old in cardiac arrest; a misdemeanor charge was later filed (Feb–Jun 2025) (12NewsNow explainer).

3) Risk Scenarios

1. Rooftop hospital heliport, urban dusk: Security reports a consumer drone near the ED entrance canopy as an HEMS flight turns final. Without detection, the pilot must go around and loiter; with detection, security can verify track movement and coordinate with police to clear the area.
2. Highway multi‑vehicle crash, rural night: Bystander launches from the shoulder; a Life Flight helicopter is inbound while a sheriff’s UAS maps skid marks. The LZ officer uses a portable detector to identify the bystander’s RID, hail them over PA, and hold the helo until the airspace is cold.
3. Wildland‑urban interface fire: Media drone launches into a TFR‑covered area, forcing fixed‑wing water drops to halt. A perimeter detection node alerts the Air Boss before aircraft enter the drop lane.

4) Operational Requirements for Heliport & Field Detection

• Rapid setup: Handheld or tripod‑mount unit; <2 minutes from power‑on to first detections.
• Coverage: Effective within at least 1–2 miles in urban settings (environment dependent); extended with elevated placement.
• RID decoding: Support for Standard RID and Broadcast Module messages; clearly flag non‑RID/unknown tracks.
• Precautionary note — RID band coverage: Many portable receivers decode Wi‑Fi/Bluetooth RID only on 2.4 GHz. A subset of aircraft (notably some Skydio models and DJI Avata 1) have been observed broadcasting RID on 5.8 GHz. Agencies procuring drones should verify that the aircraft’s RID transmits on 2.4 GHz so it will be detected by common field receivers.
• Alerting: Audible/visual alerts for proximity and approach vectors; configurable thresholds.
• Backhaul: Prefer LTE/FirstNet for out‑of‑band resilience.
• User roles: Simple LZ officer view; advanced security/dispatch console; exportable incident logs for after‑action review.
• Integrations: CAD/dispatch, incident management (ICS forms), EHR timestamping of LZ holds, and video walls.
• Privacy & compliance: Receive‑only; no jamming or interception of control links; adheres to federal/state privacy and spectrum rules.

5) Concept of Operations (ConOps)

5.1 Heliport (fixed installation + portable backup)

1. Pre‑launch check (originating base): Dispatch/security checks heliport detector status (“clear deck”).
2. En route: Dispatch monitors for incursions across the approach fan and notifies pilot if a new track appears.
3. Final approach: If unknown/non‑RID or converging track within practical scan area, initiate go‑around/hold; security/police engage.
4. Post‑landing: Note any incursions in the occurrence log; export data for security follow‑up.

5.2 Accident scene LZ (portable deployment)

1. Arrival: LZ officer powers on detector, selects incident, and sets an appropriate circular scan area for the receiver (e.g., ~1,000‑ft radius).
2. Scan & announce: If RID track detected, hail operator; if unknown/non‑RID persist, hold medevac and request law‑enforcement assistance.
3. Coordinate agency sUAS: Assign an Air Boss/UAS Coordinator; publish altitude blocks and orbit directions for agency drones.
4. Resume operations: Once airspace is cold, clear medevac to land. Log event automatically with times for after‑action review.

6) Policy & Training

• SOPs: Adopt simple checklists (see Appendix A) covering pre‑flight checks, alert thresholds, and decision trees for hold/approach.
• Training: Incorporate detection tools into quarterly LZ drills; rehearse radio phraseology and hailing scripts for RID operators.
• Public information: Post “No Drone Zone during Heliport Ops” signage; include RID/penalty education in community outreach.
• Interagency agreements: Clarify who acts as UAS Coordinator at scenes, who can order holds, and how to preserve digital evidence.
• Standards alignment: Align with NFPA public‑safety sUAS guidance and FAA UAS rules; ensure responders with sUAS operate under Part 107 or COA with proper waivers.

7) Procurement Guidance

• Risk-based prioritization when budgets are constrained: If funding cannot cover detectors for every heliport and every LZ kit, conduct a risk analysis (e.g., patient flight volume, approach/departure geometry and obstructions, proximity to likely drone launch points, history of incursions/complaints, and night/IFR operations). Equip the highest-risk facilities and first-due LZ kits first.
• Fixed + portable mix: Install a fixed detector at each hospital heliport (coverage of approach fans and Safety Area) plus one portable unit per LZ kit carried by first‑due agencies.
• Power & mounting: Rooftop mounts should prioritize clear line‑of‑sight to approach paths; provide UPS or PoE with backup.
• Backhaul: Prefer LTE/FirstNet for out‑of‑band resilience.
• Records: Ensure secure, immutable logs suitable for investigations and trend analysis.
• Lifecycle: Plan for firmware updates as RID standards evolve and to add vendor‑specific telemetry decoders where lawful.

8) Legal, Privacy, and Ethics

• Detection vs. enforcement: Detection provides awareness; only law enforcement should take enforcement actions. Do not jam or interdict RF links.
• RID and expectations: Many drones must broadcast RID in most airspace; some legacy or FRIA‑based operations may not. Unknown tracks should trigger caution, not assumptions of malice.
• Data minimization: Retain only the data needed for safety and post‑incident review, in line with hospital privacy policies and state law.
• Liability considerations (consult counsel): Current technology advances put fixed heliport detectors at under $10,000 and portable units at well under $1,500. If an incident results in injury or loss of life and the heliport operator had no drone‑detection capability in place, the organization may face heightened liability exposure. Engage legal counsel and risk management to assess obligations and document the rationale for procurement decisions.

9) Implementation Roadmap (90 Days)

1. Weeks 1–2: Site survey at heliports; choose mounts and power; identify approach fans and scan radius.
2. Weeks 3–6: Install fixed units; commission portable kits; integrate alerting to dispatch/security.
3. Weeks 7–8: Train pilots, dispatch, security, and LZ officers; run day/night joint drills with agency sUAS.
4. Weeks 9–12: Go‑live; measure KPIs (incursions detected, average LZ hold time, false alarms); tune thresholds.

10) Checklists (Appendix A)

Heliport “Clear Deck” (Security/Dispatch)

1. Check detector health (green).
2. Verify scan radius clear and approach fan.
3. If track present: note RID ID/operator location; notify pilot and secure area.
4. Log status change and times.

Accident Scene LZ (LZ Officer)

1. Power on portable detector; select incident.
2. Set an appropriate circular scan area for the receiver (e.g., ~1,000‑ft radius).
3. If RID track detected: hail operator; request they land and clear.
4. If unknown/non‑RID persists: hold medevac; request law‑enforcement response.
5. Coordinate agency sUAS altitude blocks/orbits.
6. Resume operations when airspace is cold; export log.

11) Conclusion

Drone detection is now a front‑line safety tool for hospital heliports and first responders. By pairing fixed heliport sensors with portable LZ kits—and embedding simple SOPs—agencies can prevent delays, reduce collision risk (helicopter and sUAS), and maintain the tempo of patient care.

Glossary

LZ — Landing Zone: A temporary, secured helicopter landing area established by responders at or near an incident or patient pickup site.