I managed to dig an example in my telemetry records that shows how momentary 'No GPS Fix' causes horizon jerk. Here is portion of GPS Input data extracted to CSV:
date, Time, Sec since start, Connected, Data changed, .Latitude, .Longitude, .PDOP, .Satellites, .Status
2016-04-04, 14:39:59.422, 126.976, 1, 1, 425112365, 274762658, 1.5, 14, Fix3D
2016-04-04, 14:39:59.649, 127.203, 1, 1, 425112269, 274762389, 1.5, 14, Fix3D
2016-04-04, 14:39:59.799, 127.353, 1, 1, 425112177, 274762121, 1.5, 14, Fix3D
2016-04-04, 14:40:00.12, 127.566, 1, 1, 425112086, 274761853, 1.5, 14, Fix3D
2016-04-04, 14:40:00.199, 127.753, 1, 1, 425111996, 274761583, 1.5, 14, Fix3D
2016-04-04, 14:40:00.367, 127.921, 1, 0, 425111996, 274761583, 1.5, 14, Fix3D
2016-04-04, 14:40:00.429, 127.983, 1, 1, 425111907, 274761313, 99.98999786, 0, NoFix
2016-04-04, 14:40:00.812, 128.366, 1, 1, 425108864, 274763301, 1.709999919, 10, Fix3D
2016-04-04, 14:40:00.884, 128.438, 1, 1, 425108864, 274763301, 1.709999919, 10, Fix3D
2016-04-04, 14:40:01.12, 128.566, 1, 1, 425108802, 274762996, 1.649999976, 11, Fix3D
2016-04-04, 14:40:01.209, 128.763, 1, 1, 425108738, 274762696, 1.709999919, 10, Fix3D
2016-04-04, 14:40:01.357, 128.911, 1, 0, 425108738, 274762696, 1.709999919, 10, Fix3D
2016-04-04, 14:40:01.409, 128.963, 1, 1, 425108676, 274762414, 1.649999976, 11, Fix3D
2016-04-04, 14:40:01.579, 129.133, 1, 1, 425108616, 274762138, 1.649999976, 11, Fix3D
2016-04-04, 14:40:01.799, 129.353, 1, 1, 425108557, 274761859, 1.649999976, 11, Fix3D
And a screenshot of Scopes page while replaying the log in GCS.
Flying on gyros only at this moment so nothing unusual in AccelState scope but AttitudeState shows clearly the wrong estimation.