Mission 1: Mid-action After Action Report
Posted: Tue Mar 31, 2009 9:42 am
It's in a situation like the one we are currently in that reminds me that it has been almost 20 years since my stint in the US Army (MOS 11B, 2/14th Infantry, 10th Mountain Div - 1988-1991). At least I can still remember the After Action Report tool that we employed to learn from our mistakes and successes. It's still a little early for that, so here is Malcom's Mid-action After Action Report for Mission 1.
From my perspective, we made the classic blunder of not utilizing the resources available to their best extent. Primarily, the camp plans and aerial photos. As my tagline says, I have way too much time on my hands, so I've been reviewing these resources and came up with a plan that is at least better then the one we've been using. I hope we can live to learn from this.
Error 1: Eyes. Using the Astrogation gear was a good first step, but we needed eyes on target longer and closer. The Aerial photos show high ground with concealed approaches to the west. If we had switched the Explorer out for an Aircar, we could have inserted a scout team about 1 click from the base (see modified photo). I would suggest this team to have been Sebastian (for Chatter-box and his nap-of-New-Pale flying skills), Leo, Gren, and a combat 'bot.
Error 2: Fire Support. Gren had a great idea in requesting a recoilless rifle. We should have got a second one for the combat bot going with the scouts. The scout position then becomes a fire support position as well, opening fire just before the insertion team lands. Also, depending on how bot computer links work, Leo might be able to use the combat 'droid's link to break into the base computer.
Error 3: Insertion. Mal requested only two para-wings, but should have requested one per team member. And at least three holo-screens programmed to camouflage in New Pale's sky. Mal, B'Looone, and 'Ting could then HALO (high altitude, low open) or HAHO (high altitude, high opening) jump from the Dart with Building A's roof as the landing zone. Each jumper should be equipped with an assortment of the tangler, smoke, and stun grenades that B'Looone requested. They use tanglers and smoke on the roof (and the spider bot that was there) just before (or after - Ref's decision) landing, continuing until the bot is immobilized. 'Ting and Mal move to the edge of the smoke and start shouting the shutdown code phrase while preparing stun grenades. This should put every OE bot in sight out of action. Meanwhile, B'Looone blasts a hole over room 21. In go the stun grenades followed by at least 'Ting and Mal. B'Looone could stay on the roof to deal further with the spider bot. Using stun and tanglers, the insertion team will take and hold rooms 21 and 22 (computer room). Sebastian and Leo zoom in from the scout position to join those in Building A. Maria should fly in close(<1000m) to provide further support with the pod laser. Once enough of the heavy weapons are out of commission, Maria inserts the remaining 'bots.
Leo will have to file this in the Dart's information storage program under 'Hindsight.20.20'.
From my perspective, we made the classic blunder of not utilizing the resources available to their best extent. Primarily, the camp plans and aerial photos. As my tagline says, I have way too much time on my hands, so I've been reviewing these resources and came up with a plan that is at least better then the one we've been using. I hope we can live to learn from this.
Error 1: Eyes. Using the Astrogation gear was a good first step, but we needed eyes on target longer and closer. The Aerial photos show high ground with concealed approaches to the west. If we had switched the Explorer out for an Aircar, we could have inserted a scout team about 1 click from the base (see modified photo). I would suggest this team to have been Sebastian (for Chatter-box and his nap-of-New-Pale flying skills), Leo, Gren, and a combat 'bot.
Error 2: Fire Support. Gren had a great idea in requesting a recoilless rifle. We should have got a second one for the combat bot going with the scouts. The scout position then becomes a fire support position as well, opening fire just before the insertion team lands. Also, depending on how bot computer links work, Leo might be able to use the combat 'droid's link to break into the base computer.
Error 3: Insertion. Mal requested only two para-wings, but should have requested one per team member. And at least three holo-screens programmed to camouflage in New Pale's sky. Mal, B'Looone, and 'Ting could then HALO (high altitude, low open) or HAHO (high altitude, high opening) jump from the Dart with Building A's roof as the landing zone. Each jumper should be equipped with an assortment of the tangler, smoke, and stun grenades that B'Looone requested. They use tanglers and smoke on the roof (and the spider bot that was there) just before (or after - Ref's decision) landing, continuing until the bot is immobilized. 'Ting and Mal move to the edge of the smoke and start shouting the shutdown code phrase while preparing stun grenades. This should put every OE bot in sight out of action. Meanwhile, B'Looone blasts a hole over room 21. In go the stun grenades followed by at least 'Ting and Mal. B'Looone could stay on the roof to deal further with the spider bot. Using stun and tanglers, the insertion team will take and hold rooms 21 and 22 (computer room). Sebastian and Leo zoom in from the scout position to join those in Building A. Maria should fly in close(<1000m) to provide further support with the pod laser. Once enough of the heavy weapons are out of commission, Maria inserts the remaining 'bots.
Leo will have to file this in the Dart's information storage program under 'Hindsight.20.20'.