Writing
Notes from the security side of drones
Technical writing on uncrewed aircraft security, flight-log forensics and records that hold up. Product news lives on rotorlab.app.
-
The FCC Covered List and your drone fleet: what’s settled and what’s pending
Foreign-produced drones and drone components have been on the FCC’s Covered List since December 2025. Here is what that entry actually restricts today, what it leaves…
-
What the FAA can ask to see, and how fast you can produce it
Part 107 asks for fewer records than most program managers assume, but it expects you to produce every one of them on request. Here is the…
-
Reading a Betaflight blackbox log after a crash
When a quad goes in, the flight controller has usually written down what it saw. Here is the order I read a Betaflight blackbox log in:…
-
What a FRIA means for a club flying field
An FAA-recognized identification area lets aircraft without Remote ID fly at a club field, but only inside the line and only while the pilot can see…
-
Your build sheet is already a record
FPV builders already keep the records commercial programs struggle with: a config backup before every flash, a parts list, a log from every flight. Treat them…
-
MAVLink message signing: what it proves and what it doesn’t
MAVLink 2 signing tells an aircraft that a command came from someone holding the key. It doesn’t hide anything, and it only helps if unsigned traffic…
-
What a penetration tester looks for in a drone’s flight log
A flight log is an evidence file. Read it the way you would read an attacker’s access logs: timestamps first, then what is missing.
Follow along
New posts go out by RSS and on LinkedIn. No newsletter, no tracking.