jump to navigation

Iran claims it has decoded the U.S. stealthy RQ-170 Drone Intel but provides unsubstantiated evidence to prove it. April 22, 2012

Posted by David Cenciotti in Captured Stealth Drone.
Tags: , , , , ,
4 comments

Iran has decoded the U.S. stealthy drone intel?
What? oh, umm…yeah…sure

According to a FARS News Agency article published on Apr. 22, Iran has just finished deconding the intelligence gathering sensors and the internal hard disks of the U.S. stealthy RQ-170 Sentinel drone that was captured by Iran in December 2011.

Speaking to FNA, Commander of the Islamic Revolution Guards Corps (IRGC) Aerospace Forces Brigadier General Amir Ali Hajizadeh revealed some data taken from the aircraft’s intelligence system to deny claims by the Pentagon according to which the Iranians would not succeed in decoding the spy drone’s memory and intelligence devices.

To provide four cues to let the US know how deep Iranian engineers could penetrate into the secrets of the drone Hajizadeh stated that

The drone parts had been transferred to California for technical works in October 2010, adding that the drone was later transferred to Kandahar, Afghanistan in November 2010 and had a flight in there.

The commander said that the drone had experienced some technical flaws in its Kandahar flight in November, but the US experts failed resolve the problems at the time.

Hajizadeh added that the RQ-170 was then sent back to an airfield near Los Angeles in December 2010 for tests on its censors and parts, adding that the drone had a number of test flights in there.

As a forth cue to prove Iran’s access to the drone’s hidden memory, the commander mentioned that the spy drone’s memory device has revealed that it had flown over Al-Qaeda Leader Osama bin Laden’s hideout in Pakistan two weeks before his death.

According to Haiizadeh,  “Had we not accessed the plane’s soft wares and hard discs, we wouldn’t have been able to achieve these facts”.

Although it is possible that the RQ-170′s internal memories were not successfully wiped out following the loss of satellite link with the drone giving the Iranians the chance to decypher some of the data collected by the drone the four “cues” provided by the Iranian General are not solid.

The same information could be retrieved, if not on the Internet (the fact that the “Beast of Kandahar” has tanken part to the Operation Neptune’s Spear to kill Osama Bin Laden was very well known since May 2011) with a little of OSINT (Open Source INTelligence) and some spying.

Aviation magazines have published pictures of the RQ-170 at Kandahar showing some modifications (obviously applied in the US) and by simply observing the drone at Kandahar before and after the new equipment was installed could be a sign of stateside work.

Hence, unless something more solid emerges, I think it’s quite unlikely that the internal memory contained useful information:  they were (probably) automatically erased as a consequence of the loss of control procedure and data will never been recovered. However, the circuitry, lenses, memories and sensors are still there and can be evaluated, tested and copied. And, maybe, improved, with the help of some interested third parties (Russia and China).

Airspace violations – Episode 8 January 30, 2012

Posted by David Cenciotti in Airspace violations.
Tags: , , , , , , , ,
2 comments

Previous episodes: Archive

The following episode took place about 24 years ago. However, it occurred  in the Strait of Hormuz, saw the direct involvement of U.S. warships operating in the 5th Fleet Area Of Operations amid heightened tensions, and involved also an Iranian F-14 (one of those has recently crashed during a mysterious night scramble).

Hence it is also quite topical since it gives an idea of what the above mentioned contributing factors can produce.

U.S. – Iran war games…24 years ago

(Iran Air Flight 655 shot down by USS Vincennes)

On Jul. 3, 1988, an Airbus A-300 (registration EP-IBU) operating as Iran Air Flight 655 from Tehran Bandar Abbas to Dubai was shot down by two ground-to-air missiles fired by the USS Vincennes, a Ticonderoga-class warship that was cruising in the Persian Gulf waters to keep a closer eye on the bloody and consuming war that involved Iraqi and Iranian armed forces.

Both missiles struck the fuselage, breaking off part of the tail and one wing and causing the death of all 290 people on board.

Background

During the Iran-Iraq war in the ’80s, the U.S. presence in the region was significant in order to protect oil tankers threatened by both countries. Just one year before this incident, in May 1987, the guided missile frigate USS Stark was attacked by an Iraqi Mirage F-1 jet and 37 American sailors perished during the clash. Further  investigation led Captain Glenn Brindel to be blamed not to have defended its frigate against the attack.

Therefore, the U.S. Navy agreed that new and more strict rules of engagement (ROE) were needed in order to allow Captains to get a more powerful right to defend themselves and “fire before being fired upon”.

These premises constitute the roots which gave birth to the root causes of the tragedy.

The event

On Jul. 3, 1988, three U.S. ships were patrolling the Persian Gulf: USS Vincennes, USS Montgomery and USS Sides. Suddenly, the second one reported enemy fire coming from small boats belonging of theIRGC (Iranian Revolutionary Guard Corps).

Responding the request of support from the USS Montgomery, the Captain of USS Vincennes ordered to step in the battlescene and engaged some IRGC boats for half an hour.

In a few minutes, some missiles were also launched and shortly after an Iranian F-14 was shot down in a great ball of fire.

In the meantime, in the more peaceful but busy environment of the Bandar Abbas airport, the doomed Airbus A-300 was ready for a short flight to Dubai, United Arab Emirates.

After take-off, flight 655 was instructed by the ATC to activate the transponder (on the Airbus, the transponder ‘squawks Mode III’ identified the aircraft as neutral and civilian) and was requested to reach an altitude from 7,000 to 12,000 feet.
At the same time the USS naval ships in the Strait of Hormuz got another warning signal on their radar devices and identified it as a possible and serious threat.

During the seven minutes between take-off of of flight 655 and the launch of missiles, the U.S. naval units made several attempts to get in contact with the Iran Air A300: USS Vincennes tried to use the military radio channel of frequency 243.00 MHz used for emergency purposes and four other attempts on the civil channel at 121.5 MHz.

So how this incident occurred if many attempts to communicate were made?

First of all ICAO final investigation report proved that the A-300 was not able to receive communication on the military emergency frequency 243MHz with onboard radio equipment.

Instead, dealing with the attempts made on the civilian radio frequency 121.5MHz, the board of inquiry ascertained that the Iran Air crew did not pay the due attention during the first phases of the flight or did not realize to be a possible target of naval units.

The crew was in continuous communication with ATC and was therefore unable to hear the warnings issued on the civil aviation distress radio frequency. ICAO also determined that of the four warnings issued on this distress frequency, only one was considered clear enough to be recognizable by the flight crew as directed to them.

Forty seconds past this last recognizable transmission, the USS Vincennes crew fired the missile.

More in details ICAO stated that:

  1. The aircraft weather radar was probably not operating during the flight nor would normal procedures have required its operation in the prevailing weather conditions.
  2. The radio altimeters were probably functioning throughout the flight;
  3. Apart from the capability to communicate on the emergency frequency 121.5MHz, United States warships were not equipped to monitor civil ATC frequencies for flight identification purposes.
  4. Four challenges addressed to an unidentified aircraft (IR655) were transmitted by United States ships on frequency 121.5MHz.
  5. There was no response to the four challenges made on 121.5MHz, either by radio or by a change of course. This indicated that the flight crew of IR655 either was not monitoring 121.5MHz in the early stages of flight, or did not identify their flight as being challenged.
  6.  The aircraft was not equipped to receive communications on the military air distress frequency 243MHz. There was not coordination between United States warships and the civil ATS units responsible for the provision of air traffic services within the various flight information regions in the Gulf area.

Final statement summarised that: “The aircraft was perceived as a military aircraft with hostile intentions and was destroyed by two surface-to-air missiles.

After stating that the environment on board the civilian plane contributed to the incident, the ICAO inquiry led to a more bewildering truth on the chaos and strain that reigned onboard the US naval units.

During the seven minutes between the take-off and the shot down of flight 655, excited communcation were made among the Captains of US naval units in the area, clearly stating the doubtfulness of identifying the approaching aircraft.

The US Department of Defense admitted that “…there was growing excitement and shouting in the Combat Information Centre of the USS Sides about a commercial flight.”

In the very first moments the radar operator of USS Vincennes identified the radar track as “unknown-assumed enemy” as the “Combat Information Center” of the same unit identified it as an enemy F-14 fighter jet.

Two minutes later the Captain of USS Sides, assumed the non-threating nature of the aircraft but a minute later USS Vincennes Captain ordered the shot down.

The Aftermath

The US Navy never blamed its crew for the incident and excused it with the need of defending the crew itself and their ships from any possible threats.  On the same day of the incident, US President Ronald Reagan stated that USS Vincennes followed all the requirements for the interception of foreign aircraft and that the Captain on duty ordered the launch of missiles only for defense purposes.

On Jul. 13, 1988, Vice-Secretary Williamson declared before the ICAO Counsel how high the level of danger was during the event. He noted that on Jul. 3 all the US naval units were engaged on a large operation of pursuit against Iranian vessels and it could have been considered a real war theatre.

On the extraordinary session of ICAO Counsel (Jul. 13-14, 1988), the ICAO President stated that: “…fundamental principle that States must refrain from resorting to the use of weapons against civil aircraft must be respected by each State”.

Representatives agreed to blame the U.S. act and some pushed for a rapid approval of Article 3bis of Chicago Convention – at that time not yet ratified. In particular, USSR and Nigeria blamed the US to lead a barbaric and brutal campaign against free and innocent people.

At the end of the technical investigation, on Mar. 17, 1989 the ICAO Counsel adopted the following Resolution:

“THE COUNCIL…
Having considered the report of the fact-finding investigation instituted by the Secretary General…and the subsequent study by the Air Navigation Commission of the safety recommendations presented in that report;
Recalling that the 25th Session (Extraordinary) of the Assembly in 1984 unanimously recognized the duty of States to refrain from the use of weapons against civil aircraft in flight;
Reaffirming its policy to condemn the use of weapons against civil aircraft in flight without prejudice to the provisions of the Charter of the United Nations;
Deeply deplores the tragic incident which occurred as a consequence of events and errors in identification of the aircraft which resulted in the accidental destruction of an Iran airliner and the loss of 290 lives;
Notes the report of the fact-finding investigation instituted by the Secretary General and endorses the conclusions of the Air Navigation Commission on the safety recommendations contained therein;
Urges States to take all necessary measures to safeguard the safety of air navigation, particularly by assuring effective co-ordination of civil and military activities and the proper identification of civil aircraft.”

“Deplores”, “Notes”, “Urges”: nothing really effective to avoid repeating the incident.

24 years later the tension between US and Iran is at its highest peak ever. Let’s hope we are not going to witness another similar episode in the Persian Gulf. For sure, we would not feel very comfortable flying across the Strait of Hormuz these days.

© David Cenciotti & Simone Bovi

Above image credit: Irandefense.net