Knowledge base · Rural property security
Using sighting history after an incident
Build a responsible timeline without treating a detection as proof of wrongdoing.
Record the problem first
Note what was discovered, where and when. Preserve camera footage, gate records and observations from workers.
Review the relevant period
Look for identified and suspected detections before, during and after the likely incident window.
Compare, do not assume
Matching times or locations can identify useful lines of enquiry, but correlation alone does not establish intent or responsibility.
Report responsibly
If theft, trespass or unsafe flying is genuinely suspected, preserve the available information and contact the appropriate authority. Never interfere with an aircraft.
How to use this guide
Apply the guidance to the actual property rather than treating it as a universal rule. Terrain, buildings, aircraft behaviour, operational routines and local conditions all affect the result.
Keep identified and suspected activity separate
An identified aircraft can provide usable broadcast identity and flight information. Suspected activity is an unknown signal consistent with possible drone operation and may provide no telemetry. Never treat the second as though it were the first.
Build context around the event
Compare the detection with expected contractors, workers, neighbouring activity, cameras, gates and operational records. A detection cannot determine intent, but an accurate timeline can help explain what happened and direct attention to the right evidence.
Respond responsibly
Do not jam, disable, pursue or attempt to take control of an aircraft. Preserve relevant information and contact the appropriate authority where activity appears unsafe or connected with an offence.
Need help with your property?
DroneDingo customers can open a support ticket with the property layout, installation questions and relevant observations so advice remains attached to their account.