Boolean is just a variable that can only be "true" or "false". To create an instance variable (as opposed to global variable) you click on an object and add it via the properties bar (initially on the left).
What I was implying was replace 'every 0.2 seconds' with 'ship.ready' (meaning boolean is true). Then add an action to that event that changes the boolean to false. To have it change back to true every 0.2 seconds add the timer behavior and create an action to start a timer. Then create a 'on timer' event that changes the boolean back to true. (you could use wait but will most likely lead to bugs in the future)
This variable can be helpful in the future also for when game is paused or maybe ship gets stunned or something, just have to change the boolean to false.
I understand your thinking on setting the animation before it is spawned, I kind of had the same lines of thinking at first. But remember how fast all of this can be processed but also was probably setup to actually process those actions at once.
If you want to replicate that in construct you just need some sub-events, which are visually indented and work like a nested if, and the else command, which is in the system events. The else command will fire if the command above it fails. You can have multiple conditions but the else has to be at the top of them. It will be apparent if the else command is setup wrong.