kmacht wrote:One thing that still sticks in my mind a bit is what about the conventional tail Sonex? ... The Sonex uses a very similar piece of angle to hold the front of the horizontal stabilizer down. It looks like they issued a service bulletin that beefed up the angle in that area by using a piece of solid block but they didn't do the same for the Sonex.
The following buildup presents a simplified example of loading to a V-tail structure while maneuvering. As can be seen, increasing the angle of attack (AOA) will increase the up load on the stabilizers. The up deflection of the ruddervators necessary to increase the AOA would decrease the up loading on the stabilizers. A yaw to the left would decrease the up loading on the left stabilizer and increase the loading on the right stabilizer. Pushing the right pedal would further lower the up loading on the left stabilizer and further increase the up loading on the right stabilizer. The step inputs incorporated into the calculations result in slightly higher than actual values since the AOA and yaw angles would be responding immediately to the start of the movement of the flight controls.
The build-up below follows a simple maneuver – pull the stick aft to increase the AOA, yaw left, followed by moving the stick forward and depressing the right pedal. In this case, the yaw and pedal input approximately double the load to the right stabilizer.
fastj22 wrote:It looks like the GPS track stopped during the climbout. Strange isn't it? What would cause that besides someone turning off the instrument?
fastj22 wrote:The retrieved the GPS track from some onboard system.
fastj22 wrote:It looks like the GPS track stopped during the climbout. Strange isn't it? What would cause that besides someone turning off the instrument?
fastj22 wrote:The retrieved the GPS track from some onboard system.
A review of radar and Garmin 510 Global Positioning System (GPS) data revealed that the airplane departed IIY about 1239, and the pilot began a gradual, climbing turn to the north. About 2 nautical miles (nm) northeast of IIY, the airplane was observed climbing in left-hand circular patterns until a peak altitude of 4,700 feet above mean sea level (msl) was reached. The airplane then continued on a westerly heading until the GPS stopped recording data. The last two recorded radar returns with altitude data were at 4,600 and 4,300 feet. Prior to the last radar return, the airplane was in a slight descent and accelerated to about 100 to 110 knots ground speed. The GPS did not capture the parameters when aircraft control was lost. The wreckage site was located about 0.11 nm north-northeast of the last radar return with altitude information.
fastj22 wrote:The Aera is a self contained unit with its own internal power source. So if the aircraft ran out of fuel and engine shut down, it would have no effect on the Garmin from continuing to record the flight path. And since the NTSB was able to recover some of the information up to a point, means the pilot either turned it off at that point or it failed. I doubt the Garmin failed. Or the NTSB haven't released the entire GPS log. Something isn't right here.
I say this because I want to know what happened. I have a very similar aircraft and need to know if overspeed was a factor. Or if he was just happily flying along at cruise and his aircraft broke up.
Users browsing this forum: No registered users and 7 guests