RotorLab CTO says drone programs fail on logs and records
Original title: Drone program compliance: What a CTO says most agencies get wrong
He urges coarse public flight logs and warns raw GPS tracks can expose staging points and informants.
In a Help Net Security interview, RotorLab CTO Nick Donarski says public-safety drone programs often fail chain of custody and indexing for flight logs and video. He describes publishing routine civil flights while withholding tactical overwatch until cases clear, and favoring coarse itemized logs over raw GPS tracks. He also says unredacted transit video and missing flight logs create open-records and litigation problems, and he points to risks in ground control software and spreadsheet logs.
Unconfirmed: The FAA penalty case is mentioned only; the excerpt does not state the facts or outcome.
- He says clerks need a dispatch call number, the pilot, and the video.
- Insurers want maintenance logs, motor runtime, pack charge counts, and Part 107 status.
- He advises against publishing exact coordinates and track vectors.
- He says incidental transit footage can be public without a signed auto-delete policy.
- He references an FAA penalty case, but the excerpt does not describe the outcome.
From the original article
8 min read at helpnetsecurity.com
In this interview with Help Net Security, Nick Donarski, CTO at RotorLab, explains what councils, records clerks, insurers, and auditors expect from a public safety drone program, and where most programs fall short. He covers chain of custody for flight logs and video, how to publish drone activity without exposing sensitive operations, and common mistakes in open records handling.
By Mirko Zorz · helpnetsecurity.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.