EdisonW1979
Second Officer
Flight distance : 1535679 ft
Canada
Offline
|
hallmark007 Posted at 2018-7-10 11:44
First off you have added 1 phantom log, and your right it doesn’t show any Yaw problems, if your aircraft moves a few feet from take off left right forward or backwards. This has nothing to do with Yaw problem, Yaw movement is left or right on its own axis or aircraft axis, sudden movements in any direction are nothing to do with Yaw .
They are more likely to be controls not being pushed up straight, most common, or problem with IMU , so all motors not running at the same speed will cause aircraft to veer or jump forwards or backwards left or right. Again this has nothing to do with Yaw.
See, I knew you would throw it back at me claiming no YAW problems! You're back to your old F'ing M-O, spin, twist and turn it around on the pilot! You're so predictable.
I have a feeling even if I was recording the takeoff with another camera to show the violent yaw move, you'd still say "oh this is fine, it's normal, nothing wrong here", or make the exact claim that it was probably the pilot moving the stick and not even knowing it...
Tell me, how would I be touching the controls during takeoff when I performed a precision takeoff, took my hands off the controls, and had finished re-calibrating the RC just that afternoon, and noted no input on the controls? Oh, that's right, cause I didn't touch the controls, and the MA went haywire during takeoff!
And you keep speaking as if you know it all, but you know NOTHING... I already said earlier that this is just the first of TWO I will be posting, and this one is ONLY the log of the takeoff which had Yaw issue, and IT IS a YAW issue.
BTW, with 18 locked satellites with 5 bars of signal strength, even by MA flight operators guide, this is enough to lock the aircraft in so tight onto the coordinate, there should be ZERO drift. On the old 0300 FW, the MA would take off and STAY in the same spot above the takeoff zone, even in wind, with no drift or deviation. The drift issue, along with the yaw issue, was introduced with 0400, as SO MANY here are reporting!
And the following issue I will be posting is ROLL issues, not YAW! You really try to twist and spin EVERYTHING and make yourself sound smart, but in reality, you sound stupid as a stump!
Regarding VLOS, how else is one to test something if you don't push it to the point of reported issues? Rather do the test over an open area to see what happens. And using augmented means to maintain VLOS for testing purposes is fine; as long as I can see it, that's VLOS still. And I will continue to harp on people not to take their drone out of VLOS simply because that's the prudent and safe thing to do under normal operating conditions, and to recommend otherwise is inappropriate. If I myself want to take the risk for testing, that is my choice and I will bear the responsibility for any consequences myself.
I'm gonna post the next set of data, but I DO NOT WANT to see your crap comments any longer. I'd much rather value some of the other captains and pilots here to view, cause I know all you do is be insulting, condescending and blame everything on pilot error, cause everyone here knows you like to blame the pilots and never acknowledge FW issues. |
|