AudioCyclist
New member
Greetings,
As I review and edit, I realized that this is also a review of the Sportsman S+. I encourage all who read this to respond with helpful suggestions and if I made mistakes, correction. I further encourage Horizon Hobby to respond (hello Mike), as I would enjoy their feedback. I greatly enjoy building and flying RC planes (and multirotors, but that is a whole other subject) and want to be the best pilot I can be.
As I am new to flying RC planes, I thought it advantageous to supplement my time on RealFlight, my Flite Test-based planes, and buddy boxing with some very experienced pilots in my RC club with the Sportsman S+.
The first flight experience was very, very disappointing.
I carefully went through the compass calibration set-up procedure outlined in the manual three times over the week before yesterday's first flight. One critical oversight on HH's part is not providing visual or auditory verification that the procedure was performed or completed correctly. The same expressly applies to setting the virtual fence: airfield. This lack of verification is just lazy design and engineering, not doing the right thing that ensures a great customer/pilot experience.
At the field, I powered the DX5 transmitter (yes, I bought the RFT because my DX6i cannot be made to take advantage of all of the S+'s functionality), then powered the plane, closed the battery compartment, righted the vehicle, and placed it on the edge of the runway perpendicular to its long axis. I then waited for the auditory GPS-link conformation tones. Once sounded, I picked up the plane and moved it to the centerline on the runway, pointed into the wind, and ran the throttle to full and back down to minimum (hopefully setting the takeoff/landing direction into memory). I then walked back to the edge of the runway, throttled up, and took off. (The runway runs from east to west, with the wind coming out of the west yesterday [as it does about 360 days a year].)
With the guidance of one of the experienced pilots, I did a couple of the simplest circuits possible around the field (big rectangles; during which I noticed strange VF behavior I will cover below). After completing these and headed into the wind west of the runway, I wanted to get the plane down safely, so I pressed the HP/AL button for the required three seconds, at which point the plane reacted and bank right to go downwind to the east end of the runway. It did go past the east end of the runway, banked right again while descending, and appeared to line up well with the runway (it seemed to duplicate the same position that I observed the experienced pilots using when landing their planes). However, this is where things started going very wrong. Instead of continuing straight down the runway and continuing its decent to land, it took a vector that sent it across the runway from left to right. When it passed me (I was to the left of the runway's mid-length [where the throttle was taken to full as described above], the plane was still about ten to fifteen feet above the ground. It end up smashing into a wire fence that is about twenty feet off the right side of the runway, opposite the pit area. This put two nasty divots in the wing and a large area of wrinkles in the fuselage's foam ahead of the wing's leading edge (caused by the wings twisting on impact).
With that unpleasant, disappointing, and frustrating experience, I picked up the plane, dusted off the dirt and weed fragments, repositioned the wing, and put it away. I went back to buddy-boxing with the experienced pilots that have adopting me as their student pilot.
Right now, I am seriously considering that instead of learning to fly on the $300+ Sportsman with its $38 dollar wing and $38 fuselage, I'll go back to building the Flite Test Tiny Trainer, Storch, and other FT planes and learn to fly with these. Even a catastrophic crash with one of these planes that results in a total loss of the entire airframe is only a $4 to $10 incident.
I do see myself flying the Sportsman in the future, but not relying on the GPS-based features. With my experience, and based on the similar comments of others and what has been observed in some videos on YT, it seems that the S+ features are not ready for public consumption.
The VF airfield did not function correctly. When banking around to come over the runway at the downwind (east) end, the plane would react to the VF (at a point that seemed to be near, but not at, the edge of the runway where GPS lock was made) and go into the holding pattern. Yet when flying to the west end of the runway and turning left, clearly going past the runway edge and toward the pits, the plane did not react with going into the holding pattern. Extremely inconsistent. And frustrating, since it left me wondering if I had indeed correctly setup everything properly before the flight.
And there are errors in the manual. One is the compass calibration. It instructs the pilot to power the receiver and then later to power the transmitter (steps 1 and 2 on page 15). This is just plain wrong. This is at least corrected on Mike's video that covers the calibration process. And there is no mention in the manual that the rate switch (at least) must be in the 100% position when using the sticks to set a function (the lower rate does not produce a count that is high enough for the receiver to recognize as a function select).
Overall, it seems that the plane was rush to release. Instead, another three to six months should have been spent refining the receiver's and GPS module's software. Additionally, visual indicators should be been designed and engineered to verify to the pilot that compass calibration and VF were performed and set correctly. Another DVT or PVT pre-production phase would have produced a more robust and user-friendly solution.
Thanks.
As I review and edit, I realized that this is also a review of the Sportsman S+. I encourage all who read this to respond with helpful suggestions and if I made mistakes, correction. I further encourage Horizon Hobby to respond (hello Mike), as I would enjoy their feedback. I greatly enjoy building and flying RC planes (and multirotors, but that is a whole other subject) and want to be the best pilot I can be.
As I am new to flying RC planes, I thought it advantageous to supplement my time on RealFlight, my Flite Test-based planes, and buddy boxing with some very experienced pilots in my RC club with the Sportsman S+.
The first flight experience was very, very disappointing.
I carefully went through the compass calibration set-up procedure outlined in the manual three times over the week before yesterday's first flight. One critical oversight on HH's part is not providing visual or auditory verification that the procedure was performed or completed correctly. The same expressly applies to setting the virtual fence: airfield. This lack of verification is just lazy design and engineering, not doing the right thing that ensures a great customer/pilot experience.
At the field, I powered the DX5 transmitter (yes, I bought the RFT because my DX6i cannot be made to take advantage of all of the S+'s functionality), then powered the plane, closed the battery compartment, righted the vehicle, and placed it on the edge of the runway perpendicular to its long axis. I then waited for the auditory GPS-link conformation tones. Once sounded, I picked up the plane and moved it to the centerline on the runway, pointed into the wind, and ran the throttle to full and back down to minimum (hopefully setting the takeoff/landing direction into memory). I then walked back to the edge of the runway, throttled up, and took off. (The runway runs from east to west, with the wind coming out of the west yesterday [as it does about 360 days a year].)
With the guidance of one of the experienced pilots, I did a couple of the simplest circuits possible around the field (big rectangles; during which I noticed strange VF behavior I will cover below). After completing these and headed into the wind west of the runway, I wanted to get the plane down safely, so I pressed the HP/AL button for the required three seconds, at which point the plane reacted and bank right to go downwind to the east end of the runway. It did go past the east end of the runway, banked right again while descending, and appeared to line up well with the runway (it seemed to duplicate the same position that I observed the experienced pilots using when landing their planes). However, this is where things started going very wrong. Instead of continuing straight down the runway and continuing its decent to land, it took a vector that sent it across the runway from left to right. When it passed me (I was to the left of the runway's mid-length [where the throttle was taken to full as described above], the plane was still about ten to fifteen feet above the ground. It end up smashing into a wire fence that is about twenty feet off the right side of the runway, opposite the pit area. This put two nasty divots in the wing and a large area of wrinkles in the fuselage's foam ahead of the wing's leading edge (caused by the wings twisting on impact).
With that unpleasant, disappointing, and frustrating experience, I picked up the plane, dusted off the dirt and weed fragments, repositioned the wing, and put it away. I went back to buddy-boxing with the experienced pilots that have adopting me as their student pilot.
Right now, I am seriously considering that instead of learning to fly on the $300+ Sportsman with its $38 dollar wing and $38 fuselage, I'll go back to building the Flite Test Tiny Trainer, Storch, and other FT planes and learn to fly with these. Even a catastrophic crash with one of these planes that results in a total loss of the entire airframe is only a $4 to $10 incident.
I do see myself flying the Sportsman in the future, but not relying on the GPS-based features. With my experience, and based on the similar comments of others and what has been observed in some videos on YT, it seems that the S+ features are not ready for public consumption.
The VF airfield did not function correctly. When banking around to come over the runway at the downwind (east) end, the plane would react to the VF (at a point that seemed to be near, but not at, the edge of the runway where GPS lock was made) and go into the holding pattern. Yet when flying to the west end of the runway and turning left, clearly going past the runway edge and toward the pits, the plane did not react with going into the holding pattern. Extremely inconsistent. And frustrating, since it left me wondering if I had indeed correctly setup everything properly before the flight.
And there are errors in the manual. One is the compass calibration. It instructs the pilot to power the receiver and then later to power the transmitter (steps 1 and 2 on page 15). This is just plain wrong. This is at least corrected on Mike's video that covers the calibration process. And there is no mention in the manual that the rate switch (at least) must be in the 100% position when using the sticks to set a function (the lower rate does not produce a count that is high enough for the receiver to recognize as a function select).
Overall, it seems that the plane was rush to release. Instead, another three to six months should have been spent refining the receiver's and GPS module's software. Additionally, visual indicators should be been designed and engineered to verify to the pilot that compass calibration and VF were performed and set correctly. Another DVT or PVT pre-production phase would have produced a more robust and user-friendly solution.
Thanks.