Scott108
lvl.4
Flight distance : 314419 ft
United States
Offline
|
I know best practice is to set RTH to clear anything in flight area. But that wasn't the question -- because that best practice isn't always entirely practical.
I fly in hilly, mountainous terrain -- where 135 foot high trees are common and 200 foot high trees are not unusual. Let's say I take off in the valley, and ascend to 150' (which puts me above MOST the trees). Now I fly up a hillside that is 250' higher than my takeoff location, navigating around any taller trees, and maintaining 150' above ground level. So now I'm 400' above takeoff location (but still 150' above ground), and there are a few trees around that are 50' higher than that. I would need something like 475' "above home point" to clear every single tree in the proposed flight area.
To be clear, I'm not concerned about "manual" push-the-button RTH -- I don't use that. I'm concerned about the auto-RTH that could occur if the controller failed, or there was a communications failure. I wouldn't have any way to manually control (lower) the altitude during the RTH operation.
I could set RTH altitude to 475' before flight, as suggested above. But that would mean a "lost signal auto-RTH" would bust the 400' legal ceiling (I'm in the U.S.) during much of the return -- even if I was only 150' above takeoff location when auto-RTH occured.
Assuming I could rely on some obstacle avoidance for those taller trees, I could set RTH for 400' and be both safe and legal -- even with an auto-RTH.
Or would it make more sense to manually adjust RTH altitude during the flight, as the ground rises? I'd still end up with RTH set at 475' above "home point", but only for a portion of the flight.
|
|