I hear you. Normally I don't consider myself to be a law-and-order bible-thumper; I push things pretty far at times, but this really ticked me off when it happened. Flying in a situation where a malfunction puts unknowing bystanders at risk (in my opinion) is way out of bounds and should warrant a good swift smack. He's a "professional," he should have known better.
Stepping off my soap-box...
In the U.K. we have the 50m rule for flying near to the public/small groups or individuals not under the PICs control (30m during take off and landing), and a 150m rule for flying near to a crowd with 1000 people or more present. Further, a hobbyist can't fly within 150m of a 'congested' area (50 m if you are on a commercial job with a commercial permission)Don't fly over people without a waiver if they are clients and never over general public. It's a simple rule and plain common sense.
Sent from my iPhone using Tapatalk Pro
I would hope and think the guy feels pretty bad about the incident. I know i would and could expect many restless nights over the incident.That's a **** of it's own.
I think 30 days is a bit extreme. Perhaps 5 days would suffice.
Redundancies or safety features. I can think of a couple right off the bat.
You start with more than four motors in case one fails. The drone can maintain enough stability to at least land if not fly home.
That leads to the next thing... an autonomous feature to control the drone if there is a loss of signal or control disruption of some kind.
An Obstacle Avoidance system of some kind might be nice to have as well.
An interesting read at any rate...
Jmo thanks,
Jafo
We use essential cookies to make this site work, and optional cookies to enhance your experience.