Merlin negative G cutout too quick?

Originally Posted by 41Sqn_Banks

There is way to much "feeling" in bugtracker issue. I think it should be possible to get the G force using a mission script to verify the values. It's possible to log the position (x, y, z), speed and the time, should be enough to calculate the G forces, shouldn't it?

Someone should collect the reference material to find out at which value the engine should cut. Someone else should test the implementation by doing flight test and calculate the G force.

Then we have something to compare and don't need to talk about feelings and opinions.

THANK you, Banks