It's always been drummed into me the importance of a range check before any maiden flights. I took my FT3D to the field today to do its maiden flight. I checked and adjusted everything the night before. Down at the field, I showed off my new plane to the other guys there, and I got a bit distracted by the discussion. I was just doing the pre-flight checks on the strip, when it suddenly came to me that I hadn't done the range check, so a rather embarrassing return to the pits and the range check was done with no problems. Back to the strip, preflight checks, and all clear for take off. Up goes the plane, a little wobbly at first, then everything smoothed out as I gain control and start doing my first circuit to trim it out. After about 50 meters, WTF, my nice new plane spiralled down with no control and hit the ground hard. When I reached the somewhat damaged plane, everything was still working so I was a bit confused as to why it happened, then I looked in despair at my transmitter: It was still in range check mode!
Oh well, you live and learn. I don't suppose I'm the first to have done that. I guess I'm still getting used to the 2.4gHz way of doing things. I never made that mistake with the old 35mHz aerial up and down method.
Oh well, you live and learn. I don't suppose I'm the first to have done that. I guess I'm still getting used to the 2.4gHz way of doing things. I never made that mistake with the old 35mHz aerial up and down method.