Anatomy of May 5 Predator Crash in Kandahar

The unmanned aircraft had been in the air for close to five hours before its mission crew realized that something was wrong.

The oil temperature in the plane’s turbocharger, they noticed, had risen into the “cautionary” range. An hour later, it was worse, and it just kept rising as the minutes wore on. While the crew desperately ran through its “engine overheat” checklist trying to figure out the problem, the engine oil temperature, too, began skyrocketing. By now, they had a full-blown in-flight emergency on their hands. “We still have control of the engine, but engine failure is imminent,” the pilot announced over the radio.

Almost two hours after the first signs of distress, the engine indeed failed. Traveling at 200 meters per minute, the drone clipped a fence before crashing. The crash occurred in Afghanistan – Kandahar, to be precise – in May of this year. It went unreported at the time and involved an MQ-1 Predator, a workhorse hunter/killer machine of the Afghan war.

A document detailing a US Air Force investigation of that Predator crash sheds light on the lifecycle and flaws of drones – just what can go wrong in unmanned air operations – as well as the system of bases and units scattered across the globe that keep those drones constantly in the skies as the US becomes ever more reliant on remote-controlled warfare. That report and striking new statistics obtained from the military offer insights into under-examined flaws in drone technology.

According to statistics provided by the US Air Force, Predators have flown the lion’s share of hours in America’s drone wars. As of October 1st, MQ-1’s had spent more than 1 million hours in the air, 965,000 of those in “combat”, since being introduced into military service. The newer, more heavily armed MQ-9 Reaper, by comparison, has flown 215,000 hours, 180,000 of them in combat. (The Air Force refuses to release information about the workload of the RQ-170 Sentinel.) And these numbers continue to rise. This year alone, Predators have logged 228,000 flight hours compared to 190,000 in 2010.

An analysis of official Air Force data conducted by TomDispatch indicates that its drones crashed in spectacular fashion no less than 13 times in 2011, including that May 5 crash in Kandahar. About half of those mishaps, all resulting in the loss of an aircraft or property damage of $2 million or more, occurred in Afghanistan or in the tiny African nation of Djibouti, which serves as a base for drones involved in the US secret wars in Somalia and Yemen. All but two of the incidents involved the MQ-1 model, and four of them took place in May.

In 2010, there were seven major drone mishaps, all but one involving Predators; in 2009, there were 11. In other words, there have been 31 drone losses in three years, none apparently shot down, all diving into the planet of their own mechanical accord or thanks to human error.

Other publicised  crashes, like a remotely-operated navy helicopter that went down in Libya in June and an unmanned aircraft whose camera was reportedly taken by Afghan insurgents after a crash in August, as well as the December 4 loss of the RQ-180 in Iran and an even more recent crash of a MQ-9 in the Seychelles, are not included in the Air Force’s major accident statistics for the year.

The May 5 Predator crash about a 400 meters short of a runway at Kandahar air field drives home just how diffuse drone operations have become, with multiple units and multiple bases playing a role in a single mission.

That Predator drone, for example, was an asset of the 3rd Special Operations Squadron, which operates out of Cannon Air Force Base in New Mexico, and ultimately is part of Air Force Special Operations Command, based at Hurlburt Field in Florida. When it crashed, it was being flown by an in-country pilot from the 62nd Expeditionary Squadron at Kandahar Air Field, whose parent unit, the 18th Reconnaissance Squadron, makes its home at Creech Air Force Base in Nevada, ground zero for the military’s drone operations. The crewman operating the sensors on the drone, on the other hand, was a member of the Texas Air National Guard based at Ellington Field in Texas.

The final leg of the doomed mission – in support of elite special operations forces – was being carried out by a pilot who had been operating Predators for about 10 months and had flown drones for approximately 51 hours over the previous 90 days. With less than 400 total hours under his belt, he was considered “inexperienced” by Air force standards and, during his drone launch and recovery training, had failed two simulator sessions and one flying exercise. He had, however, excelled academically, passed his evaluations, and was considered a qualified MQ-1 pilot, cleared to fly without supervision.

His sensor operator had been qualified by the Air Force for the better part of two years, with average or above average ratings in performance evaluations. Having “flown” a total of 677 hours – close to 50 of them in the 90 days before the crash – he was considered “experienced.”

The fact that the duo were controlling a special operations drone highlights the increasingly strong and symbiotic relationship between America’s two recently ascendant forms of warfare: raids by small teams of elite forces and attacks by remote-controlled robots.

During the post-crash investigation, it was determined that the ground crew in Afghanistan had been regularly using an unauthorized method of draining engine coolant, though it was unclear whether this contributed to the crash. Investigation documents further indicate that the drone’s engine had 851 hours of flight time and so was nearing the end of the line. (The operational lifespan of a Predator drone engine is reportedly around 1,080 hours.)

Following the crash, the engine was shipped to a California test facility, where technicians from General Atomics, the maker of the Predator, carried out a forensic investigation. Significant overheating had, it was discovered, warped and deformed the machinery.

Eventually, the Air Force ruled that a cooling system malfunction had led to engine failure. An accident investigator also concluded that the pilot had not executed proper procedures after the engine failure, causing the craft to crash just short of the runway, slightly damaging the perimeter fence at Kandahar Air Field and destroying the drone.

Source: Asia Times

Leave a Reply

Your email address will not be published. Required fields are marked *