{"id":34195,"date":"2019-02-13T20:45:35","date_gmt":"2019-02-13T20:45:35","guid":{"rendered":"https:\/\/one.sightlinemg.com\/airforcetimes\/uncategorized\/2019\/02\/13\/that-second-predator-crash-in-four-days-back-in-2017-was-due-to-signal-loss\/"},"modified":"2026-08-07T21:00:42","modified_gmt":"2026-08-07T21:00:42","slug":"that-second-predator-crash-in-four-days-back-in-2017-was-due-to-signal-loss","status":"publish","type":"post","link":"https:\/\/one.sightlinemg.com\/airforcetimes\/news\/your-air-force\/2019\/02\/13\/that-second-predator-crash-in-four-days-back-in-2017-was-due-to-signal-loss\/","title":{"rendered":"That second Predator crash in four days back in 2017 was due to signal loss"},"content":{"rendered":"\n

The loss of a satellite link <\/a>was the cause of the second MQ-1 Predator crash<\/a> over the course of a week back in 2017, according to an accident investigation board report released Wednesday.<\/p>\n\n\n\n

The drone was operating out of Incirlik Air Base, Turkey<\/a>, when it lost its connection and went down in the southeast part of the country on Aug. 21, 2017, at about 11:50 a.m.<\/p>\n\n\n\n

The incident was preceded by the crash of another MQ-1 shorty after takeoff on Aug. 17<\/a>. That accident was determined to have been caused by an electrical failure that sent the drone into an uncontrollable dive.<\/p>\n\n\n\n

During the second crash incident, the aircraft did not attempt to fly its emergency mission, which is the pre-programmed reaction the drone is expected to take in the event that a lost link occurs.<\/p>\n\n\n\n

At the time of the mishap, the drone was was operated by a pilot and sensor operator out of the 432nd Air Expeditionary Wing at Creech Air Force Base, Nevada.<\/p>\n\n\n\n

The two airmen permanently lost the ability to control their Predator while flying at a medium altitude of 13,000 feet, and about 90 minutes into the mission.<\/p>\n\n\n\n

Data logs and video analysis led an analyst with General Atomics, which built the MQ-1 Predator, to conclude the lost link was likely caused by an intermittent issue within the drone\u2019s primary control module or a failure of the internal circuit board.<\/p>\n\n\n\n

\"\"
An MQ-1B Predator from the 414th Expeditionary Reconnaissance Squadron sits on the flightline Feb. 14, 2012, at Incirlik Air Base, Turkey. Reactivated Nov. 23, 2011, the 414th ERS dates back to World War II when it was known as 414th Bombardment Squadron. (U.S. Air Force photo by Senior Airman Anthony Sanchelli\/Released)\r<\/figcaption><\/figure>\n\n\n\n

The General Atomics analyst said the primary control module damage was likely the result of improper handling during shipping or when the unit was in storage.<\/p>\n\n\n\n

That portion of General Atomics\u2019 report was disputed by the accident investigation board, however, which said that maintenance procedures cleared the aircraft for flight operations, and the successful flight for 90 minutes before the mishap indicates the primary control module wasn\u2019t damaged during shipping or storage.<\/p>\n\n\n\n

An interview with the senior technician who installed the primary control module also indicated that the damage didn\u2019t occur on the Air Force\u2019s watch, according to the investigation board.<\/p>\n\n\n\t