Just catching up on forum posts while winding down my evening from a full FliteFest schedule. I was chatting with
@PsyBorg after a buddy box flight with my primary trainer plane and his friend Tom who's also a FliteCrew volunteer along with Bill. Tom is newish to the hobby and totally jumping in head first. Much like I did when I started. I really felt like Tom and my experience matches. When I started, I learned about FliteTest late and it coincided with the inaugural FliteFest event. After finally having some success in RC thanks to FliteTest instructional videos and easy build kits/plans, I just knew I had to attend. I was still uncomfortable with my skills, especially in airspace with more than one plane up, so I ended up volunteering more than flying. Well, that habit actually hasn't changed from 2014, but to get back to the point of this rambling note:
While I was buddy boxing with Tom, I became inattentive to how long we had been up in the air. At one point, I allowed the plane to get too low, and while I took back control, it seemed I just didn't have enough power to climb out and the plane landed fairly gently in the bean field. The only damage was the lost prop which was on a prop saver. One of two things immediately came to mind: I lost connection, and the receiver went to failsafe which would be to cut the throttle. I wasn't monitoring my battery, and it got too low.
While speculating this with Bill, he mentioned that he observed a lot of the outages/failsafes seems to occur on either Spektrum or FrSky equipped aircraft when the oil well pump at the West end of Furey field is running. He mentioned that he's aware of a wireless telemetry system on these pumps based on WiFi, which can run on 2.4GHz.
I think that this, coupled with the WiFi network setup for "FliteTest Info" which is a dedicated onsite network to allow people to view build videos without using their mobile data plan, as well as the FT Store and Registration WiFi and whatever other mobile WiFi access points people setup at their campsites and that neighbors in the area have all combines to make even the remote FliteFest location a fairly noisy environment for 2.4GHz.
At any rate, we were speculating on all this, but ultimately, when I returned to my gear, I put a voltage checker on the battery's balance lead and quickly identified the culprit to the "early" landing in my case was a 3S battery that was pushed down to about 10.0V
Here's some information on what oil wells have for wireless networks:
https://new.abb.com/network-managem...tworks/solutions/oil-gas-field-communications