Mavic Air pilots, especially those who use Litchi, may find this KML file interesting. It shows how a Mavic Air performed on a course specifically set up to see if—and how far—the drone “overshoots” corners at various speeds.
Here's a snapshot of the course, marked for the direction of travel.
View media item 2638 I highly recommend using Google Earth Pro over any browser- or mobile device-based edition of GE.
I used Virtual Litchi Manager to plan the mission and export it to Google Earth. (If you’re unfamiliar with VLM, you owe it to yourself to look into it.) The following KML members come from VLM output:
The drone flies a series of right turns: first 30°, then 60°, then 90°, then 135°. Each turn employs a 20 ft smoothing curve and has a long, straight approach of ±160 ft (±49m).
Then it runs a quick Z-curve before executing a "tilted pseudo-orbit“ around a landmark. The orbit is defined by a series of equally spaced and equally smoothed Waypoints, and has a radius of about 56 ft (17m). It finishes with a 180° “full reverse” maneuver before coming home.
About the Flights
All three flights were taken in mild to moderate winds:
For example, the low-speed track (in green) is nearly true to the course, except in the final hairpin turn, and in the Z-curved approach to the orbit, where its maximum deviation is about 3.3ft (1m). High speeds tell a different story.
The first high-speed flight (in red) met the strongest winds near the point on the ‘orbit’ where the track shows a massive deviation of 18⅔ft (5.7m) off the course. Not only did the drone have to fight a 9mph headwind, the course also gains altitude at that point. Still, I'm a little surprised that the Mavic Air didn't have the reserves to better execute the maneuver; that’s a lot of drift! Also, I can’t explain the discontinuity opposite the point of maximum deviation in this flight. My best guess is a wind gust, but holy smokes, at 18mph it should take impact from an inbound pass to cause that kind of lurch. There are no logged events to suggest anything.
Most surprising to me was that all flights held true on the 135° corner, whereas they overran the course on lesser curves.
That’s particularly true, because I ran a prototype of this course the day before, at 17mph. That flight isn’t in this KML because parts of the course differed then, but the 30-60-90-135 section was nearly identical. In that preliminary test, the drone massively overshot the 135° turn, and took nearly the whole distance to the Z-curve to return to the course. (Even more dramatic than the deviation shown in the KML coming off the final hairpin turn in the red path.) The only difference was that in that version, the 135° turn had a 40 ft. smoothing curve, rather than 20 ft in this KML. The fact that requiring a sharper maneuver elicited far better performance is utterly baffling. Similarly, I expected a notable overrun on the “full reverse” maneuver near the end. Again, the drone seems to have “turned on a dime”, without overshooting the reverse-point in any significant degree.
Obviously I’m missing something, though the results are largely in line with what I’d expect.
Here's a snapshot of the course, marked for the direction of travel.
View media item 2638 I highly recommend using Google Earth Pro over any browser- or mobile device-based edition of GE.
I used Virtual Litchi Manager to plan the mission and export it to Google Earth. (If you’re unfamiliar with VLM, you owe it to yourself to look into it.) The following KML members come from VLM output:
- Waypoint Path (skeleton) : renamed component (Yellow path)
- Expected Track (smoothed WpP) : renamed “Smooth Flight Path” (Black path)
- Diagnostics folder and contents : standard components
- 20190121-8mph : Green path (13kmh)
- 20190121-18mph-1 : Red path (29kmh)
- 20190121-18mph-2 : Purple path (29kmh)
- Thus, the KML shows not only the desired flight path on this Waypoint Mission, but three instances of the actual, in the field, flight path.
The drone flies a series of right turns: first 30°, then 60°, then 90°, then 135°. Each turn employs a 20 ft smoothing curve and has a long, straight approach of ±160 ft (±49m).
Then it runs a quick Z-curve before executing a "tilted pseudo-orbit“ around a landmark. The orbit is defined by a series of equally spaced and equally smoothed Waypoints, and has a radius of about 56 ft (17m). It finishes with a 180° “full reverse” maneuver before coming home.
About the Flights
All three flights were taken in mild to moderate winds:
- 8mph flight : SW @ 3.0mph, gusting to 5.6mph (1.3m/s, 2.5m/s)
- 18mph flight 1 : NW @ 6mph, gusting to 9.5mph (2.7m/s, 4.3m/s)
- 18mph flight 2 : SW @ 5.3mph, gusting to 7.1mph, (2.4m/s, 3.2m/s)
For example, the low-speed track (in green) is nearly true to the course, except in the final hairpin turn, and in the Z-curved approach to the orbit, where its maximum deviation is about 3.3ft (1m). High speeds tell a different story.
The first high-speed flight (in red) met the strongest winds near the point on the ‘orbit’ where the track shows a massive deviation of 18⅔ft (5.7m) off the course. Not only did the drone have to fight a 9mph headwind, the course also gains altitude at that point. Still, I'm a little surprised that the Mavic Air didn't have the reserves to better execute the maneuver; that’s a lot of drift! Also, I can’t explain the discontinuity opposite the point of maximum deviation in this flight. My best guess is a wind gust, but holy smokes, at 18mph it should take impact from an inbound pass to cause that kind of lurch. There are no logged events to suggest anything.
Most surprising to me was that all flights held true on the 135° corner, whereas they overran the course on lesser curves.
That’s particularly true, because I ran a prototype of this course the day before, at 17mph. That flight isn’t in this KML because parts of the course differed then, but the 30-60-90-135 section was nearly identical. In that preliminary test, the drone massively overshot the 135° turn, and took nearly the whole distance to the Z-curve to return to the course. (Even more dramatic than the deviation shown in the KML coming off the final hairpin turn in the red path.) The only difference was that in that version, the 135° turn had a 40 ft. smoothing curve, rather than 20 ft in this KML. The fact that requiring a sharper maneuver elicited far better performance is utterly baffling. Similarly, I expected a notable overrun on the “full reverse” maneuver near the end. Again, the drone seems to have “turned on a dime”, without overshooting the reverse-point in any significant degree.
Obviously I’m missing something, though the results are largely in line with what I’d expect.
Last edited: