Agree with assessments above but to stay out of trouble, set your missions up very conservatively at first until you become confident.
A little more detail on the " set up conservatively at first" thing:
1) -- Make you first circuit around a new Waypoint path looking forward to the next waypoint. That way you'll see approaching hazards that you might not see if you're looking at a POI, and your forward OA cameras are available to help keep you out of trouble.
2) -- to protect yourself from Google Earth errors regarding elevation changes, even when flying in terrain following mode from G.E., set your initial altitudes higher than you think you need, maybe by as much as 75 feet if the terrain physically looks relatively level. More if it looks hilly. Not everybody agrees, but I've found the G.E. elevations can be wrong by a bunch when it's looking at forest land. If it's looking at paved areas, it's pretty accurate.
3) -- walk the mission altitudes down in steps after you've initially validated the path as safe in the above steps.
4) -- only after you've qualified the mission parameters as safe to fly should you set up camera headings and pitch to get your shots. At this point you can safely look at POI's on the screen, fly sideways, etc while flying the path.
5) -- if your camera compositions need for you to move the path to get the right shot, treat it as a new path to be validated as safe restarting from the first step above. Note that if you adjust the path from a Google Earth view, depending on the zoom in/out scale that you're using, a small movement on the screen may be a large movement on the ground.
If you don't want to do the above, make sure that your early flights adjusting path and waypoint locations are made with you actually watching the craft throughout the flight, not the screen. If I'd done these steps, I'd be two Mavic's ahead of the game at this point.
Best of luck. LItchi and Virtual Litchi are remarkable. Hope you enjoy the journey................ R