Open water, public shorelines
Cruise berths, fuel farms, and cargo yards sit in plain view of beaches, parks, and causeways. Repeat flights become a security, safety, and tenant-relations problem at once.
Drone incursion exposure
Federal law reserves drone mitigation to federal agencies and certified state and local officers. A port, utility, or launch provider may detect, record, and report. What that record shows, and who acts on it, decides whether incursions keep happening.
What exposure looks like
Around Kennedy Space Center, every likely launch point is public land: a beach lot, a riverfront park, a boat ramp. Two recent cases started in parking lots. One came within a mile and a half of a launch pad.
Your site has the same pattern. An exposure analysis maps it from your own detection logs and public records:
The result is a sourced record your board, insurer, and counsel can use for budgets, coverage, and requests for protection.
Who this is for
Cruise berths, fuel farms, and cargo yards sit in plain view of beaches, parks, and causeways. Repeat flights become a security, safety, and tenant-relations problem at once.
Substations and treatment plants are easy to observe from a road shoulder. A detection log says a drone was there. It does not say why the same one keeps coming back.
Pads, payload processing, and test stands draw hobbyist flights, and can draw deliberate collection too. Telling the two apart takes a pattern, not a single sighting.
Underwriters asked to price drone exposure have little beyond incident reports. A mapped, sourced exposure record gives coverage terms and loss-control requirements a basis.
Video briefing
What a private operator can and cannot do under federal law, why incursions persist, and how a pattern analysis changes the conversation with leadership, insurers, and law enforcement.
Why incursions keep happening
Only federal agencies and certified police may take a drone down. A port or utility may only watch, so the value of detection depends on who receives it.
Beaches, parking lots, and causeways give a clear line of sight to sensitive assets, and most of that ground belongs to someone else.
Single incidents end in reports. Without a pattern, budget requests, insurance discussions, and airspace designation requests stall.
Alerts versus evidence
The method
Public launch points with line of sight to each asset.
Your detection logs, reviewed for timing, routes, and repeat flights.
Which agency holds authority at each point, and how to reach it.
Findings and options, written for leadership and the board.
Deliverables
Launch points, approach corridors, and responding authority by zone.
Repeat behavior drawn from your own detection logs and incident reports.
Which certified agency or federal partner responds, and what they need from you.
Sourced and graded for confidence, so they hold up with directors, insurers, and counsel.
What this work does not do. It does not sell, install, or recommend a specific product, and it never advises a private party to interfere with a drone. Every recommendation stays inside federal law.
Ways to engage
One site or campus, mapped and assessed, with findings in writing.
Built on your detection logs, to show what is repeating and when.
For litigation, boards, insurers, and legislators.
Every engagement starts with a written scope and a fixed fee or rate before any work begins. Law enforcement agencies: see counter-drone readiness.
Request a written scope
Describe the site, what you are seeing, and the decision ahead. The reply will include a few questions and a proposed scope.
Prefer direct contact? robert@rjgreenresearch.org or (321) 252-9283