The shootdown occurred during theIran–Iraq War, which had been ongoing for nearly eight years.Vincennes had entered Iranian territorial waters after one of its helicopters drew warning fire from Iranian speedboats operating within Iranian territorial limits. The reason for the downing has been disputed between the governments of the two countries.
According to the United States,Vincennes's crew misidentified the aircraft as anF-14 Tomcat, a US-made fighter jet part of the Iranian inventory, despite it transmitting civilianidentification codes. They assert thatVincennes and other warships repeatedly contacted the aircraft on both civilian and militaryair distress frequencies, but received no response. Bandar Abbas acted as a joint civil/military airport, and Flight 655 had departed behind schedule. The Iranian government maintains that the US recklessly shot down the aircraft, violatinginternational law, after repeatedly provoking the Iranian forces. Some analysts blamed the overly aggressive attitude ofVincennes's captain,William C. Rogers III, while others focused on more widespread issues and miscommunications on board.
The United States was criticized for the downing, especially in its initial response. While not issuing a formal apology, American presidentRonald Reagan issued a writtendiplomatic note to Iran, expressing deep regret. In 1996, both governments reached asettlement in theInternational Court of Justice in which the US agreed to payUS$61.8 million (equivalent to $124 million in 2024) on anex gratia basis to the families of the victims. As part of the settlement, the US did not admit liability for the shootdown.
After a US oil tanker struck a mine in the Persian Gulf, additional warships were dispatched to the area; by late 1987, US forces had challenged and launched missiles at two Iranian fighter jets.[3] In April 1988, the US engaged inOperation Praying Mantis in retaliation for mines,[4] bringing significant damage to Iranian oil infrastructure and its military.[5]
In response to the pattern of attacks on shipping, the USJoint Chiefs of Staff issued a 'Notice to Airmen' (NOTAM) on 8September 1987, warning all Persian Gulf countries that civilian aircraft must monitor theInternational Air Distress frequencies and be prepared to identify themselves to US Navy ships and state their intentions;[6] Iran disputed the validity and accuracy of these notices.[7]
On the day of the incident, USSVincennes, alongsideUSS Sides andUSS Elmer Montgomery, had been assigned to take part in an escort traveling through theStrait of Hormuz.[8]Vincennes was aTiconderoga-class guided-missile cruiser, commissioned four years earlier, fitted with the then-newAegis Combat System. With a crew of 400, it was under the command of CaptainWilliam C. Rogers III at the time of the shootdown. The Aegis system was capable of tracking multiple mobile targets simultaneously, both naval and airborne, and more importantly allowed rapid dissemination of information between different levels of the crew. Its crew was inexperienced in actual conflict, but had performed well in training scenarios.[9]
At its narrowest point, the Strait of Hormuz is 21 nautical miles (39 km; 24 mi) wide. As a result, to traverse the strait, ships must stay within sea lanes that pass through theterritorial waters of Iran andOman.[10] It is normal for ships, including warships, entering or leaving the Persian Gulf to transit Iranian territorial waters. During theIran–Iraq War the Iranian forces frequently boarded and inspected neutral cargo ships in the Strait of Hormuz in search ofcontraband destined for Iraq. While legal under international law, these inspections added to the tensions in the area.[11]
Flight 655's scheduled flight path through the A59 air corridor, which it was within (purple), and the route tracked by USSVincennes (red)[12]
The plane, anAirbus A300 (registered as EP-IBU), was under the control of 38-year-old Captain Mohsen Rezaian[b], a US-educated veteran pilot with 7,000 hours of flight time, including over 2,000 in an Airbus A300.[13] Thefirst officer was 31 years old and theflight engineer was 33 years old. All had at least 2,000 flight hours.[14]
Flight 655 leftBandar Abbas at 10:17 Iran Standard Time (UTC+03:30), 27 minutes after its scheduled departure time due to an immigration issue. It should have been a 28-minute flight.[15] Before takeoff from runway 21, it was directed by the Bandar Abbas tower to turn on itstransponder and proceed over thePersian Gulf.[16] The flight was assigned routinely to commercialair corridor Amber 59, a 20-mile-wide (32 km) lane on a direct line to Dubai airport.[17] The short distance made for a simple flight pattern: climb to 14,000 feet (4,300 m), cruise, and descend intoDubai. The airliner was transmitting the correct transponder "identification, friend or foe" (IFF) code typical of a civilian aircraft (mode 3) and maintained radio contact in English with appropriate air traffic control facilities throughout the flight (see§ Radio communication).[18]
On the morning of 3 July 1988,Vincennes was passing through the Strait of Hormuz, returning from an oil tanker escort duty. A helicopter deployed from the cruiser reportedly received small arms fire from Iranian patrol vessels as it observed from high altitude.Vincennes moved to engage the vessels, in the course of which both sides violated Omani waters and left after being challenged by aRoyal Navy of Oman patrol boat.[19][20]Vincennes continued to pursue the Iraniangunboats, entering Iranian territorial waters.[21] Two other US Navy ships,Sides andElmer Montgomery, were nearby.[22]
In the meantime, Flight 655, proceeding along its scheduled route, was on an ascending flight path towardsVincennes.[23] In the time that followed (the details of which are debated, see below),Vincennes incorrectly assumed the aircraft to be hostile and issued 10 challenges to the airliner, seven on the Military Air Distress (MAD) frequency, and three on theInternational Air Distress (IAD) frequency.Sides additionally made one challenge on the civilian frequency after those ofVincennes. The aircraft was not equipped to receive military transmissions, and the civilian challenges received no responses. Subsequently, the crew ofVincennes commenced the process to engage the aircraft.[24] Flight 655 made its final transmission at 10:24:11 to acknowledge ahand-off from Bandar Abbas approach controllers:[25]
10:24:07 – Bandar Abbas Approach: "Iran Air 655 roger, contact Tehran Control 133.4, have a nice flight." 10:24:11 – IR655: "Thank you, good day."[26]
Part of the collected remains of Flight 655; much of the wreckage was never recovered
Eleven seconds later, at 10:24:22, with the aircraft at a range of 10 nautical miles (19 km; 12 mi),Vincennes fired twoSM-2MRsurface-to-air missiles. The first missile intercepted the airliner at 10:24:43 at a range of 8 nautical miles (15 km; 9.2 mi), and the second missile intercepted the airliner shortly after.[27] The plane exploded, and immediately disintegrated into three pieces (cockpit, wing section, and the tail section) and soon crashed into the water.[28] None of the 290 passengers and crew on board survived.[29] Much of the wreckage, including the cockpit voice recorder and flight data recorder, was never recovered.[30]
The officialInternational Civil Aviation Organization (ICAO) report stated that 11 attempts were made to contact Iran Air Flight 655 fromVincennes andSides, seven on military frequencies and four on commercial frequencies, addressed to an "unidentified Iranian aircraft" and giving its speed as 350 knots (650 km/h; 400 mph), which was the ground speed of the aircraft their radar reported.[35] Flight 655's crew, however, would have seen a speed of 300 knots (560 km/h; 350 mph) on their cockpit instruments, which was theirindicated airspeed, possibly leading them to conclude thatVincennes was talking to another aircraft.[36] BothSides andVincennes tried contacting Flight 655 on several civilian and military frequencies. The ICAO concluded that Flight 655's crew assumed the three calls they received before the missiles struck must have been directed at an IranianP-3 Orion, which was also taking off from Bandar Abbas.
The crew likely were monitoring the civilian international air-distress (IAD) frequency at the time of the shootdown.[37][38] In its report, the ICAO found, according to TheNew York Times, that "American warships in the Gulf had no equipment that allowed them to monitor civilian air traffic control radio frequencies", and had they had such capabilities air traffic control transmissions would have identified the flight.[39] In its ICJ statement, Iran disputed this by claiming that the Department of Defense's report explicitly mentioned theVincennes'sVHF radio equipment that would have allowed it to monitor civilian air traffic control frequencies, as well as other US surveillance activities in the Persian Gulf region that would have alerted them of the aircraft's nature.[40] The US objected to this claim, saying that most of its military vessels were only equipped with VHR radios capable of listening to the IAD frequency.[38]
The aircraft was carrying 290 people: 274 passengers and a crew of 16. Of these 290, 254 wereIranian, 13 wereEmirati, 10 wereIndian, six werePakistani, six wereYugoslavian, and one wasItalian.[41] 65 of the passengers were children.[29]
According to the US government, Flight 655 was first detected immediately after take-off byVincennes, transmitting IFF mode 3 (civilian).[42] As the flight had originated at Bandar Abbas, which served both as a base for IranianF-14 Tomcat operations and as a hub for commercial flights, all departing aircraft were by default "assumed hostile".[43][44] When the identification supervisor responsible,Petty Officer Andrew Anderson, interrogated the aircraft again soon after with his IFF radio, he neglected to reset the range and received a short IFF mode 2 transmission (indicative of a military aircraft), likely from unrelated ground aircraft taking-off at Bandar Abbas.[45] As a result, Flight 655 was erroneously tagged by Anderson with this military classification andsquawk code. The mistagged squawk code corresponded to an F-14 that had flown out of Bandar Abbas a week before, leading the crew ofVincennes to believe the airliner was an Iranian fighter jet.[46][47] For the entirety of its journey Flight 655 solely squawked civilian IFF codes.[48] Due to the flight's slight delay, the dark environment of the Combat Information Center (CIC), and confusion over time zones, Anderson missed Flight 655 in commercial flight listings.[49][50]
Escalations began whenVincennes's helicopter received warning fire after approaching close to Iranian gunboats, in contravention of the US rules of engagement at the time.[19] According to the US, the gunboats had been following merchant ships in an aggressive manner and the helicopter had been deployed after they had been sighted byMontgomery.[51] WhileVincennes engaged with the gunboats, it entered Iranian territorial waters, with sharp turns causing disruption inside.[52] In what the US government later termed "scenario fulfilment" – a form ofconfirmation bias in which personnel carry out a training scenario, believing it to be reality – information was erroneously communicated that not only was the aircraft squawking military codes, but that it was also descending on an attack profile.[20][53] The Aegis system continued to correctly record the aircraft as climbing past 12,000 feet (3,700 m), instead, and this was reflected on the CIC's numerical displays.[54] Captain Rogers had earlier acknowledged a remark that the aircraft was "possible COMAIR [commercial aviation]".[52] Following the misidentification and unreciprocated radio challenges, the aircraft was shot down (see§ Flight and shootdown).[55]
Department of Defense (DoD) officials initially said thatVincennes had shot down an Iranian F-14, but issued a retraction within hours and confirmed Iranian reports that the target was instead a civilian Airbus.[56][57] According to the DoD,Vincennes mistakenly identified the airliner as an attacking military fighter and misidentified its flight profile as being similar to that of an F-14A Tomcat during an attack run; however, the cruiser's Aegis Combat System recorded the plane's flight plan as climbing (not descending as in an attack run) at the time of the incident.[58] Alongside the vague nature of the challenges issued byVincennes, confusion may have arisen as the hailed speed stated in the transmissions was theground speed, while the pilot's instruments displayedairspeed, a 50-knot (93 km/h; 58 mph) difference.[59]
In 1992, journalists fromNewsweek obtained a full copy of the DoD's internal report which included a map and coordinates ofVincennes. They concluded thatVincennes was about 4 kilometres (2.5 mi; 2.2 nmi) inside Iranian territorial waters at the time of the shootdown.[33] This was admitted in a report by Admiral William Fogarty, entitledFormal Investigation into the Circumstances Surrounding the Downing of Iran Air Flight 655 on 3July 1988 (the "Fogarty report").[60] The Fogarty report stated, "The data from USSVincennes' tapes, information from USSSides and reliable intelligence information, corroborate the fact that [Iran Air Flight 655] was on a normal commercial air flight plan profile, in the assigned airway, squawking Mode III 6760, on a continuous ascent in altitude from takeoff at Bandar Abbas to shoot-down.".[61][62] The Fogarty report also claimed, "Iran must share the responsibility for the tragedy by hazarding one of their civilian airliners by allowing it to fly a relatively low-altitude air route in close proximity to hostilities that had been ongoing."[63]
The crew of USSSides – which issued one final challenge after the 10 ofVincennes – indicated that they had from take-off identified Flight 655 as a commercial flight, according to the ICAO. UnlikeVincennes, its operators recalled that they had never observed the IFF Mode 2 squawk that initially identified the flight as a military aircraft.[64] Of the 11 challenges, only the one made bySides identified the aircraft's squawk code.[65]
According to the Iranian government, the shootdown was both intentional and unlawful. Even if a mistaken identification was made – which Iran never accepted – it argued that this constituted negligence and recklessness amounting to an international crime, not an accident.[66]
In particular, Iran expressed skepticism about claims of misidentification, noting that the cruiser's advanced Aegis radar correctly tracked the flight and its IFF mode 3 beacon; two other US warships in the area,Sides andMontgomery, also identified the aircraft as civilian; and the flight was well within a recognized international air corridor. It also noted that the crew ofVincennes were trained to handle simultaneous attacks by hundreds of enemy aircraft.[67] Iran found it more plausible thatVincennes was looking for an opportunity to use its force, and that it had been predisposed to treat Iran as hostile, citing a statement by David Carlson,commander of the USSSides, published in the September 1989 issue ofProceedings in which he stated thatVincennes "hankered for an opportunity to show its stuff".[68]
The US had previously issued a NOTAM, warning aircraft that they were at risk of "defensive measures" if they had not been cleared from a regional airport and if they came within 5 nautical miles (9.3 km; 5.8 mi) of a warship at an altitude less than 2,000 feet (610 m). Iran stated that Flight 655 had been cleared from a regional airport and was well outside those limits when it was shot down.[69] The crew of the Vincennes had been incorrectly briefed that F-14s had been supplied to Iran withair-to-ground ordnance,[70] when in reality they were only capable of air-to-air.[71] Even if the plane had truly been an Iranian F-14, Iran argued that the US would not have had the right to shoot it down, as it was flying within Iranian airspace and did not follow a path that could be considered an attack profile, nor did it illuminateVincennes with radar.[72] Prior to the incident,Vincennes had entered Iranian territorial waters and was inside these waters when it launched its missiles.[73] Even had the crew of Flight 655 made mistakes, they stated, the US government should remain responsible for the actions ofVincennes's crew, under international law.[74]
Iran pointed out that in the past, "the United States has steadfastly condemned the shooting down of aircraft, whether civil or military, by the armed forces of another State" and citedEl Al Flight 402,Libyan Arab Airlines Flight 114, andKorean Air Lines Flight 007, among other incidents.[75] Iran also noted that when Iraq attacked the USSStark, the US found Iraq fully responsible on the grounds that the Iraqi pilot "knew or should have known" he was attacking a US warship.[76] Speaking to theUnited Nations Security Council,Ali Akbar Velayati, Iran'sminister of foreign affairs, called the shootdown the "most inhuman military attack in the history of civil aviation", caused by a "reckless and incompetent naval force".[77]: 5–7
In 1989, prior to the public exposure ofVincennes' position inside Iranian waters onNightline by Admiral William Crowe, Professor Andreas Lowenfeld of the editing board of theAmerican Journal of International Law criticized the official US position that the US was not legally liable for the incident:[78][79]
I do not understand Maier's argument at all... But the correct legal principle, I am clear, is not as Sofaer and Maier would have it—no legal liability to victims of airplane disasters without proof of fault beyond a reasonable doubt, and no fault in combat zones—but rather liability regardless of fault, so long as the cause is established, as it clearly was in the case of Iran Air 655, as in the case of Korean Air Lines 007. I would have hoped that those who spoke for the United States about the tragedy of 3 July 1988, from the President on down, would have recognized this principle, so essential for the safety of civil aviation, as other spokesmen for the United States and its allies have done when other states' military (whether or not on orders from on high) brought down civilian aircraft that may have strayed off course.... That principle, it is clear, was breached by the United States in the case of Iran Air 655, and it follows that the United States is responsible. To say that is not to condemn the United States or even to find fault. It is simply to state that responsibility flows from the action itself.
Lowenfeld also pointed out that the amount of compensation paid for Iranian victims was one-tenth the amount demanded from Iraq for American dead aboard the USSStark.[80]
One legal scholar noted in theYale Journal of International Law: "The downing of Flight 655 should not be deemed lawful merely because theVincennes' commanding officer reasonably mistook the situation as presenting an integrated surface and air attack. Reconceptualizing the incident as a mistake problem does not excuse theVincennes from liability."[81]
In an article published inNewsweek on 13 July 1992, John Barry and Roger Charles argued that Rogers behaved recklessly and without due care. TheNewsweek article also accused the US government of a cover-up;[82][83] Admiral Crowe denied any knowledge:[84] An analysis of the events by theInternational Strategic Studies Association described the deployment of an Aegis cruiser in the zone as irresponsible and felt that the value placed on Aegis cruisers by the US Navy had played a major part in the setting of a low threshold for opening fire.[85]Vincennes had been nicknamed "RoboCruiser" by crew members and other US Navy ships, in reference to both its Aegis system and the supposed aggressive tendencies of its captain.[35][86]
The International Court of Justice case relating to "the Aerial Incident of July 3, 1988" (Islamic Republic of Iran v. United States of America), was dropped on 22 February 1996 following settlement and compensation by the United States.[87]
Three years after the incident, Admiral Crowe admitted on American television showNightline thatVincennes was inside Iranian territorial waters when it launched the missiles,[34] contradicting earlier Navy statements. The ICAO report of December 1988 placedVincennes well inside Iran's territorial waters.[35]
Commander David Carlson, commanding officer of USSSides, the warship stationed nearest toVincennes at the time of the incident, is reported to have said that the destruction of the aircraft "marked the horrifying climax to Captain Rogers's aggressiveness, first seen four weeks ago".[88] His comment referred to incidents on 2June, when Rogers had sailedVincennes too close to an Iranianfrigate undertaking a lawful search of a bulk carrier, launched a helicopter within two to three miles (3.2 to 4.8 km) of a small Iranian craft despite rules of engagement requiring a four-mile (6.4 km) separation, and opened fire on small Iranian military boats. Of those incidents, Carlson commented:
"Why do you want an Aegis cruiser out there shooting up boats? It wasn't a smart thing to do."
He said that Iranian forces he had encountered in the area a month prior to the incident were "pointedly non-threatening" and professional.[89] At the time of Rogers's announcement to higher command that he was going to shoot down the plane, Carlson is reported to have been thunderstruck:
"I said to folks around me, 'Why, what the hell is he doing?' I went through the drill again. F-14. He's climbing. By now this damn thing is at 7,000 feet."
Carlson thought theVincennes might have more information and was unaware that Rogers had been wrongly informed that the plane was diving.[88] Carlson is reported to have written in theUS Naval Proceedings that he had "wondered aloud in disbelief" on hearing ofVincennes' intentions. In speculating on the "climate" that led up to the incident, Carlson stated that the crew ofVincennes "felt a need to prove the viability of Aegis in the Persian Gulf, and that they hankered for the opportunity to show their stuff."[90]
TheAegis System software at that time reused tracking numbers in its display, constituting auser interface design flaw. The Aegis software initially assigned the on-screen identifier TN4474 to Flight 655. BeforeVincennes fired, the Aegis software switched the Flight 655 tracking number to TN4131 and recycled Flight 655's old tracking number of TN4474 to label a fighter jet 110 miles away. When the captain asked for a status on TN4474, he was told it was a fighter and descending.[91][92][93]Scientific American rated it as one of the worst user interface disasters.[94]
Apsychological evaluation of the crew, requested by Admiral Fogarty, concluded thatstress and inexperience of the crew in warfare resulted in misjudgment and unconscious distortion of data, which played a significant role in the misinterpretation of the data of the Aegis system.[93]
The ship's crew did not efficiently consultcommercial airliner schedules, due to the darkness of their working space and confusion over to whichtime zone the schedules referred—the scheduled flight times used Bandar Abbas airport time, whileVincennes was on Bahrain time. The airliner's departure was 27 minutes later than scheduled. TheCombat Information Center was dark, and its lights flickered every timeVincennes fired at thespeedboats. Petty Officer Andrew Anderson, who first picked up Flight 655 on radar and thought it might be a commercial aircraft, is said to have missed the flight as he was searching in the navy's listing of commercial flights.[95]
An Iranian P-3 Orion was in the area some time before the attack, and some reports explained why no radar signals were detected from Iran Air Flight 655.[96] Other reports state that the Airbus was immediately detected after takeoff by the cruiser'sAN/SPY-1 radar at a range of 47 miles (76 km).[11]
According to Capt. Richard McKenna (surface commander of Capt. Will Rogers),Vincennes was initially authorized to send a helicopter to investigate the situation with the gun boats. Later on, when he realized thatVincennes had turned north and swapped positions withMontgomery, he commandedVincennes to leave the helicopter in place and return immediately. According to an interview after his retirement, Capt. McKenna believed that he felt the situation was not initially out of control and maybeVincennes was looking for trouble. He said "my own personal opinion is it really did feel that they were looking for action when they went to see theElmer Montgomery, um my own feeling is that the situation was not out of control, it was really my call and yet even though they were assigned another station, they took it upon themselves to be there and to that extent I feel that you know, I mean that's that's where the general feeling and not not just my own, comes that maybe they were looking for trouble."[97]
The psychology and mindset after engaging in a battle with Iranian gunboats. Claims were made thatVincennes was engaged in an operation using a decoycargo ship to lure Iranian gunboats to a fight.[98] These claims were denied by Fogarty inHearing Before The Investigation Subcommittee and the Defense Policy Panel of the Committee on Armed Services, House of Representatives, One Hundred Second Congress, Second Session, 21 July 1992. Also, the initial claims ofVincennes being called for help by a cargo ship attacked by Iranian gunboats have been ruled out.[98] That leads to claims that the Iranian gunboats were provoked by helicopters inside Iranian waters, not the other way around.[99]
This is a burden I will carry for the rest of my life, but under the circumstances and considering all the information available to me at the moment, I took this action to defend my ship and my crew.
I and I alone am fully responsible for any actions taken by theVincennes.
The event sparked an intense international controversy, with the US criticized for its account.[101] In mid-July 1988, Iranian Foreign MinisterAli Akbar Velayati asked theUnited Nations Security Council to condemn the United States, saying the attack "could not have been a mistake" and was a "criminal act", a "massacre", and an "atrocity".[77]: 5–7 George H. W. Bush, then-vice-president of the United States in theReagan administration, defended his country at the UN by arguing that the US attack had been a wartime incident and the crew ofVincennes had acted appropriately to the situation.[102] The Soviet Union asked the US to withdraw from the area and supported efforts by the Security Council to end theIran–Iraq War. Most of the remainder of the 13 delegates who spoke supported the U.S. position, saying one of the problems was that a 1987 resolution to end the Iran–Iraq war had been ignored.[103] Following the debate,Security Council Resolution 616 was passed expressing "deep distress" over the US attack and "profound regret" for the loss of human lives, and stressing the need to end the Iran–Iraq War as resolved in 1987.[104]
Iranian postage stamp issued 11 August 1988
Inside Iran, the shootdown was perceived as a purposeful attack by the United States, signaling that the US was about to enter into a direct war against Iran on the side of Iraq.[105][further explanation needed] A day of mourning was declared by the authorities, coinciding with the AmericanIndependence Day.[15]
In February 1996, the US agreed to pay Iran US$131.8 million in settlement to discontinue a case brought by Iran in 1989 against the US in the International Court of Justice relating to this incident, together with other earlier claims before theIran–United States Claims Tribunal.[87] US$61.8 million of the claim was in compensation for the 248 Iranians killed in the shootdown: $300,000 per wage-earning victim and $150,000 per non-wage-earner.[106] As part of the settlement, the US agreed to send Iran twoAirbus A300-600s, the first Western planes to be supplied to the country since 1980 (after the 1979Iranian revolution). They remained Iran's newest Western aircraft until some sanctions were lifted in 2017.[107]
The US government issued notes of regret for the loss of human lives, but never formally apologized or acknowledged wrongdoing.[108] On 5July 1988, President Ronald Reagan expressed regret; when directly asked if he considered the statement an apology, Reagan replied, "Yes."[109] George H. W. Bush, then vice-president of the United States, commented on another occasion, in a televised recording, while addressing a group of Republican ethnic leaders during the1988 presidential campaign: "I will never apologize for the United States—I don't care what the facts are... I'm not an apologize-for-America kind of guy."[110] The quote, although unrelated to the downing of the Iranian airliner and not in any official capacity, has been attributed as such.[111][112]
The incident overshadowedIran–United States relations for many years. FormerCIA analystKenneth M. Pollack wrote: "The shoot-down of Iran Air Flight 655 was an accident, but that is not how it was seen in Tehran."[113] Following the explosion ofPan Am Flight 103 five months later, the United States government initially blamed thePFLP-GC, aPalestinian militant group backed bySyria, with assumptions of assistance from Iran in retaliation for Flight 655.[114][115] The distrust generated between the US and Iran as a result of the downing of Iran Air Flight 655 was a challenge in the development of theJoint Comprehensive Plan of Action (JCPOA), also known as the Iran Nuclear Deal, which was agreed to on 14 July 2015.[116]
Newsweek covers for 12 September 1983 (left) and 18 July 1988, illustrating theKAL007 and Iran Air incidents, respectively. The caption "Murder in the Air" framed the KAL incident as a deliberate act of war, whereas "Why It Happened" framed the Iran Air incident as a tragic mistake.[117]
In 1991, political scientistRobert Entman ofGeorge Washington University comparedUS media coverage of the incident with the similar shootdown ofKorean Air Lines Flight 007 by the Soviet Union five years earlier by studying material fromTime,Newsweek,The New York Times,The Washington Post, andCBS Evening News. According to Entman,framing techniques were used to frame the Korean Airlines incident as sabotage, while framing the Iran Air incident as a tragic mistake,[117] stating "the angle taken by the US media emphasized the moral bankruptcy and guilt of the perpetrating nation. With Iran Air 655, the frame de-emphasised guilt and focused on the complex problems of operating military high technology."[118][c] By "de-emphasizing the agency and the victims and by the choice of graphics and adjectives, the news stories about the US downing of an Iranian plane called it a technical problem while the Soviet downing of a Korean jet was portrayed as a moral outrage." Entman included polling that appeared to show that theunbalanced coverage swayedpublic opinion against the Soviet Union and Iran.[119]
In July 2014, whenMalaysia Airlines Flight 17 was shot down over easternUkraine by Russian-backed insurgents, some commentators noted the discrepancy between the US official position and media coverage of the two similar incidents.[90][120][121]
Despite the downing of the plane, the crew of USSVincennes were awardedCombat Action Ribbons for completion of their tours in a combat zone. The air warfare coordinator on duty received theNavy Commendation Medal, butThe Washington Post reported in 1990 that the awards were for his entire tour from 1984 to 1988 and not for his actions relating to the surface engagement with Iranian gunboats.[122] Rogers was awarded theLegion of Merit "for exceptionally meritorious conduct in the performance of outstanding service as commanding officer [...] from April 1987 to May 1989". The award was given for his service as the commanding officer ofVincennes from April 1987 to May 1989. The citation made no mention of the downing of Flight 655.[123]
The events of Flight 655 were featured in "Mistaken Identity", aseason 3 (2005) episode of the Canadian TV seriesMayday (calledAir Emergency andAir Disasters in the US, andAir Crash Investigation in the UK).[97]
In the 2024 novelMartyr! byKaveh Akbar, the main character's mother dies on Flight 655.[124]
^The termframe here and in this[118] cited supporting source refers toEntman, Robert M. (December 1991). "Framing US coverage of international news: Contrasts in narratives of the KAL and Iran Air incidents".Journal of Communication.41 (44):6–27.doi:10.1111/j.1460-2466.1991.tb02328.x.S2CID53817259.. That article examines what it describes "as contrasting news frames employed by several important US media outlets" in covering the downings of the KAL-007 and Iran Air 655 airline flights.
^Berni, Ivan (5 July 1998)."AMERICANI, MALEDETTI!" [AMERICANS, CURSED!].la Repubblica (in Italian).Archived from the original on 4 November 2020. Retrieved8 September 2020.
^Wilson, George C. (4 July 1988)."Navy Missile Downs Iranian Jetliner".The Washington Post.Archived from the original on 12 January 2020. Retrieved12 January 2020.The Pentagon declaring... the Vicennes had shot down an attacking Iranian F14
^Carlson, David R. (September 1989)."The Vincennes Incident (letter)"(PDF).US Naval Institute Proceedings. 115/9/1039:87–92. Archived fromthe original(PDF) on 29 February 2008. Retrieved29 February 2008.
^abChomsky, Noam (24 August 2014)."Outrage".ZNetwork.Archived from the original on 4 September 2014.There was little reaction at the time: no outrage, no desperate search for victims, no passionate denunciations of those responsible, no eloquent laments by the US Ambassador to the UN about the 'immense and heart-wrenching loss' when the airliner was downed. Iranian condemnations were occasionally noted, but dismissed as 'boilerplate attacks on the United States' (Philip Shenon, New York Times).
^Roberts, Dotterway; Nancy C., Kristen Ann (1995). "The Vincennes incident: Another player on the stage?".Defense Analysis.11 (1):31–45.doi:10.1080/07430179508405642.
^abGiles, David (2003).Media Psychology.Routledge. pp. 214–215.ISBN978-0-8058-4049-0.OCLC872957625.Who was responsible for the incident? Coverage of the KAL disaster left little doubt in readers' minds of who the culprits were.Newsweek's cover page screamed: "MURDER IN THE AIR..." The IA disaster was accompanied by soul searching and questioning. "WHY IT HAPPENED" wasNewsweek's cover line... In short, the KAL incident was framed as deliberate sabotage by a nation—an act of war—whereas the IA incident was framed as a tragic mistake.
^abHalimi, Serge; Rimbert, Pierre (1 August 2019)."US and Iran, short memories".Le Monde diplomatique.Archived from the original on 12 November 2019. Retrieved20 November 2019.
^June, Sophia (1 February 2024)."InMartyr! Kaveh Akbar Is Thinking About Eternity".Nylon. Retrieved3 March 2025.Cyrus, for example, is a life-long orphan after his mother's flight is shot down by the U.S. army, based on the real-life Iran Air 655 flight.
Barry, John; Charles, Roger (13 July 1992)."Sea of Lies".Newsweek. Vol. 120, no. 2. pp. 29–39. Retrieved5 May 2021. Also available atnewsweek.com, without page numbers.
Alternatively, in order to access the report, visitthe ICAO website, pressQuery in the header followed byExecute. Enter "01/01/1988" as value one and "01/01/1989" as value two and press OK. Press the view icon to see the report.
United States of America (4 March 1991).Aerial Incident of 3 July 1988 (Islamic Republic of Iran v. United States of America) – Preliminary Objections submitted by the United States of America. International Court of Justice. (uses non-bracketed page numbers)
Rochlin, Gene I. (1997).Trapped in the Net: The Unanticipated Consequences of Computerization. US: Princeton University Press.ISBN0-691-01080-3.
Rogers, Sharon, (1992)Storm Center: The USSVincennes and Iran Air Flight 655: A Personal Account of Tragedy and Terrorism, U.S. Naval Institute Press,ISBN1-55750-727-9