NAME WITHHELD BY REQUEST
A sudden, sharp knock shattered the stillness of my hooch at Al-Asad Airbase, Iraq, hours after our Thanksgiving 2023 holiday meals had been cleared away. I flung open the door to find my standardization pilot (SP) standing in the dark, his face completely deadpan. "We’re scattering," he said. My sleep-fogged brain struggled to process his words. "Are you serious?" I asked, staring back and half-expecting a punchline. He did not blink. "I'm serious. Go!"
Adrenaline hit my system like a physical strike. I threw on my uniform, grabbed my flight gear as fast as humanly possible and sprinted toward the command post (CP) tent. We had rehearsed our aircraft scatter plans for situations exactly like this — imminent indirect fire or missile threats. The standard briefed protocol was simple. We would launch the CH-47s and head out to H1, a designated safe dispersal area miles away. But as I burst into the CP, I realized the script was being rewritten in real time. The order came down: Do not go to H1. Simply move the aircraft around the base.
The tactical situation was fluid, and leadership determined that keeping the assets inside the wire, dispersed across various ramps, was the safest immediate action. To save critical minutes, duties were delegated quickly. The pilots (PIs) were ordered to sprint to the flight line to begin emergency aircraft runup procedures immediately. Meanwhile, the pilots in command (PCs) held back at the tactical operations center (TOC) to receive a rapid intelligence brief before running out to join us.
I bolted from the tent, jumped onto my bicycle and pedaled harder than I ever had in my life. The cool night air whipped past my face as I navigated the darkened pathways to the CH-47 ramp. I threw my gear into our aircraft, strapped into the right seat and immediately initiated the runup process. My hands flew across the switches, executing the emergency startup flow as fast as the machinery would allow.
Before the engines were fully spooled up, my PC scrambled into the left seat, breathing heavily. He looked at the instruments and then at me, urgency bleeding into his voice. "Why isn't it started up yet?" I quickly relayed our position in the checklist and together we finalized the startup. Over the radio, we received our specific orders: move our aircraft to a large cargo ramp just down the road. We pulled pitch, brought the heavy Chinook into a hover and air-taxied through the dark across the base. We reached the cargo ramp, set down the wheels firmly and promptly initiated an emergency shutdown. Our singular goal was to secure the aircraft and reach hard cover as fast as possible.
As the rotors spun down and we stepped out into the night to secure the helicopter, a chilling sight caught my eye. Looking back toward the main flight line, I saw our sister ship — crewed by another PC and PI from our unit — lifting off. But instead of remaining on base, the aircraft pitched forward, accelerated eastbound and headed straight outside the wire. They were executing the old scatter plan, heading for H1.
Panic flared, but my training took over. I ripped my handheld VHF radio from my vest and keyed the microphone, frantically calling out to their aircraft. I instructed them to abort their outbound heading, turn around immediately and remain on base. Thankfully, the radio crackled back, and they banked the aircraft. I guided them back to our location, and they landed safely on the cargo ramp, parking a safe distance from our aircraft and the third helicopter in our chalk.
We later discovered the critical point of failure. The PC of that sister aircraft had been in the shower when the initial scramble was called. In the sheer chaos of the alert, he hurried to get dressed and sprinted straight to the aircraft, completely bypassing the TOC brief. He never received the updated orders to scatter around the base instead of flying to H1. He was executing the last valid plan he knew. Once the aircraft were secured, a tactical truck arrived and rushed all the crews to the large bomb shelter on base. We sat in the dim light for hours as our adrenaline slowly ebbed away, waiting out a missile attack that, fortunately, never came.
Lessons Learned
Sitting in that bunker, the gravity of the night's events washed over me, leaving our unit with several critical takeaways.
- Communication is the first casualty of chaos: The fact that a PC missed a critical mission update because he was in the shower highlights how easily the chain of information can break during an emergency. When plans change on the fly, we cannot assume everyone has the latest word. Redundant communication — whether it is a quick radio check before pulling pitch or a mandatory buddy system for briefs — is essential.
- The danger of the "standard" plan: We train to standard plans so they become second nature, but that muscle memory can become a liability if the plan changes and not everyone is informed. The sister crew did exactly what they were originally trained to do, but in this specific threat environment, leaving the base could have exposed them to a greater danger. We must always maintain the mental flexibility to accept that the briefed plan might not survive the first minute of execution.
- Situational awareness extends beyond your cockpit: Our responsibility doesn’t end when our own aircraft is shut down and secure. By keeping my head on a swivel and scanning the airspace as we egressed our aircraft, I was able to spot the sister ship making a critical error. Utilizing the handheld VHF radio to intercept them likely saved them from a highly dangerous and unauthorized flight outside the wire.
That chaotic Thanksgiving night at Al-Asad served as a masterclass in operational adaptability. We proved that we could improvise on the fly and maintain our cool. But we also learned that in the fog of a scramble, clear communication is the only thing keeping a coordinated scatter from becoming a scattered mess.