During the scenario, as the team traveled down the corridor in a file formation (classic), the point man (hereafter referred to as “Pman”) began to work with his Wingman to slice a room. We simulated a multi shooter-threat scenario in which the shooters are escaping the assault team down a corridor with 20 doors.
Gecko speed stacks drivers#
Essentially it is a read and react kind of game, like driving your car down the road and reacting to the behavior of drivers in front.Ī few months ago I worked with a European SWAT team a very good one which was familiar with our CQB concepts. The same goes to the decision to commit to an entry, open doors, etc. Some instructors would tell you that the guy who picks up the pace so that he ends up leading the formation is the point man, and so now is “never wrong”. If the point man runs into the room to the center (as exists in some SOP's), then second shooter will have to pick up left or right followed by a third guy who will in turn do the opposite of the second guy.Īnother example would be movement down a corridor.
For example, if the stack is on the left and the point man crisscrosses to the right, then the shooter behind him will have to buttonhook to the left. “The point man is never wrong” principle, is that the point man's movement decision is never to be second-guessed. Therefore, unlike in the previous chapters, we will focus this entire piece on the following rule. The point man is never wrong – or is he? This is perhaps one of the most firmly entrenched, often repeated misconceptions to be found literally everywhere in CQB.
0 kommentar(er)
