VLOS and Dronelink
Dronelink software allows fight paths that are beyond the capabilities of a human operator (at least at my skill level). I created a Dronelink flight to fly a look-down video recording over the condo complex where I live, at 115 m height and a max distance of 325 m. It is marginally possible to see the Mavic Mini drone at 325 m. A constant eastward orientation is maintained during the flight.
With the video feed I can monitor the flight and have a good sense of the physical location and orientation of the drone. And the flight path is determined because of the computation layer link through Dronelink.
I can't in truth, maintain visual sight of the drone. This flight won't meet the definition of VLOS. However, this seems to be proper control of a drone.
Does the Dronelink automated flight path and RTH fall back provide remote pilots any discretionary freedom to carry out a mission such as described?
Comments
3 comments
Using automation does not change the law.
And not only that, the laws won't change during any legal proceedings encountered or trial.
Dronelink isn’t responsible for maintain regulatory compliance - the RPIC is. That’s clear from the regulations themselves.
In the past, I’ve done mapping missions over rough terrain that required me to fly outside of VLOS from my takeoff point. I handled that by walking during the completion of the mission so I could keep the UAS in view while staying out of the photos. On a couple of occasions I’ve taken my Jeep from one side of a property to the other while controlling the UAS, to keep it in sight.
Also, don’t forget that you can get an FAA waiver for BVLOS if that is a requirement for the work you’re doing. If Dronelink tried to prevent the user from flying BVLOS that would cause an issue for those of us with waivers and I don’t think it’s a stretch to assume that waivers are primarily issued to professional operators, who are also the key demographic for Dronelink users.
Please sign in to leave a comment.