CJHjrAlt+left-arrow to return from a link
Violent international countermeasures
Documents
by Charles Judson Harwood Jr.
Americans don’t trust details. They only trust headlines.
Gene Hackman, as Senator Keeley, in Birdcage (1996) (Elaine May, writer; Mike Nichols, director)
If he’s not talking about you, then you’ve found the right webpage. –CJHjr
We hear about this (‘Lockerbie’: Pan Am 103, Dec. 21 1988, 270 victims):
“Lawyers representing the families of the victims of the Pan Am 103 bombing struck a deal with Libyan officials last year involving a $10 million payment to each victim’s family. An initial $4 million would be paid once U.N. sanctions have been formally lifted. An additional $4 million would be paid once the United States lifts its sanctions. The final $2 million would be delivered if Libya is removed from the State Department’s list of states allegedly sponsoring terrorism.”
Colum Lynch, “Deal Reached With Libya on Pan Am Bombing” {pf} (The Washington Post, August 12 2003, page A17).
But we don’t hear about this, less than 6 months earlier (‘the other Lockerbie’: Iran Air 655, July 3 1988, 290 victims):
“The survivors of each victim of the Iran Air shootdown will be paid $300,000 (for wage-earning victims) or $150,000 (for non-wage-earning victims).”
Bill Clinton, U.S. President (Jan. 20 1993-2001 Jan. 19), “Developments Concerning the National Emergency with Respect to Iran” (May 16 1996).
British and American news editors rarely report that one Anglo/American is worth 33 “rag-heads”.
An American child or student or housewife or elder are each worth 66 of their Muslim, Hindu, and other lesser counterparts.
Or, 10,000 Afghanis, at $1000 each. (It’s cheaper to kill them all than to bother with them).
Adolph Hitler had a forthright label for such people.
And you can be certain, that nearly every Arab, every Muslim, and the rest of the world’s Untermenchen know these ratios and understand their significance.
Why do people hate America?
This webpage is in progress:
This a documented analysis of the negligence, gross negligence, reckless negligence, and intentional torts by the United States Military, being the proximate cause of its ambush of the civilian airliner Iran Air 655 (July 3 1988, 290 victims); the subsequent lies (including material omissions) by U.S. Military Officers; the wrongful refusal by U.S. Officers to admit wrongdoing and pay damages, or else consent to litigation; the foreseeable consequences of their decision, being the bombing of the civilian airliner Pan Am 103 (Dec. 21 1988, 270 victims); the resulting crime, being involuntary manslaughter by those U.S. Officers responsible for lying about Iran Air 655 and for the willful decision by United States Officers to not accept responsibility for U.S. wrongdoing; thereby legalizing the foreseeable resulting bombing of Pan Am 103, an apparent international countermeasure by law enforcement officers (the bombers), if they were acting for Iran. The fruitless lawsuits by the victims of Iran Air 655 in U.S. Courts which refused to hear their case. Iran’s lawsuit in the United Nation’s International Court of Justice, in the teeth of President Reagan’s extensive efforts to prevent all victim-nations of U.S. wrongdoing access to that Court. President George H.W. Bush’s partial, restricted settlement offer without apology to induce Iran to drop its case. Clinton’s eventual settlement to preempt that Court’s ruling. The law of violent international countermeasures (a species of self-defense).
First, was the ambush of Iran Air Flight 655 by U.S. Military Officers lawful, or unlawful?
–CJHjr
The Flight
I believe that the actions of Iran were the proximate cause of this accident.
William J. Crowe Jr.
(Admiral, Chairman, J.C.S.), DoD Report, Endorsement, p.3, ¶ 3 (Aug. 18 1988)
On July 3 1988, a Sunday morning, an Iranian airliner took-off from Tehran on a round-trip flight to Dubai, with a stopover at Bandar Abbas, on Iran’s Gulf coast, where it landed normally at 8:40 a.m local time (05:10 UTC). This was a regular passenger service, on a published schedule, which Iran Air had operated twice a week for 20 years, on Sundays and Tuesdays.
Iran Air Flight 655 was scheduled to depart Bandar Abbas at 9:50 a.m. (06:20 UTC) and arrive Dubai at 11:15 Dubai time (07:15 UTC), gate to gate. It was a short hop across the Strait of Hormuz, only 130 nautical-miles, requiring only 28 minutes in the air. A passenger’s immigration problem at the gate delayed the flight 15 minutes, and the pilot requested engine-start at 10:05 a.m. (06:35 UTC).
No other aircraft had taken-off from Bandar Abbas airport that morning. Iran Air Flight 655 was the only airliner from Bandar Abbas scheduled to depart that morning and the only one scheduled to cross the Gulf that day.
The IR655 flight plan, filed with the region’s Air Traffic Control authorities 8 hours 40 minutes earlier, requested a cruising altitude of 16,000 feet (“pressure altitude,” flight level 160). But the pilot changed his request to 14,000 feet, in his initial radio contact (flight level 140), perhaps thinking to pick-up lost time that way. The winds aloft were the same at both altitudes: a 15-knot tail wind for his course (205°) (14,000 feet: 090°/18 kt, 18,000 feet: 080°/25 kt, at 0700/10:30 a.m.). ICAO Report, ¶ 1.7.3, p.4.
And, he likely took account of the low air pressure that day (QNH 998 hPa), his density altitude calculations, and the high temperature (35°C) and humidity (65%) on his engine performance. His actual altitude that day would be roughly 500 feet higher than his flight-level pressure altitude (QNE 1013.25 hPa), i.e. he would be at roughly 14,500 feet at flight level 140.
The pilot was Mohsen Rezaian, a 38 year old veteran with 7000 hours, including 2057 in an AirBus A-300. He had flown this route for the previous two years. ICAO, ¶ 1.5, pp.2-3.
When its door closed at Bandar Abbas airport that morning, at 10:05 a.m. (06:35 UTC), Iran Air Flight 655 had 290 people on board from 6 countries, 274 passengers and 16 crew: 254 were nationals of Iran, 13 of the United Arab Emirates, 10 of India, 6 of Pakistan, 6 of Yugoslavia, and 1 of Italy. 57 were children and 8 were infants. It was an AirBus A300B2-203, tail number EP-IBU. (Sister photo). ICAO, ¶ 1.2.1, p.2, ¶ 1.1.1, p.1; p.D-14, D-15.
All of the pilot’s conversations on the radio, and all of the responses he received, were in the English language, as required by ICAO on international flights, except for a few incidental exchanges. These broadcasts were all on the worldwide standard, published, civil aviation frequencies (VHF: 116.000-139.975 MHz).
Anyone in the area who tuned-in heard this:
| Time | |||
| UTC | Local | Talker | Transcript |
| Bandar Abbas Tower (BND TWR) 118.1 MHz | |||
| 06:34:50 | 10:04:50 | IR655 | Tower, IranAir 655 |
| 06:34:56 | 10:04:56 | BND TWR | IranAir 655, Tower; go ahead |
| 06:34:59 | 10:04:59 | IR655 | * Request start up clearance |
| 06:35:06 | 10:05:06 | BND TWR | 655, say again please |
| 06:35:08 | 10:05:08 | IR655 | Start up clearance |
| 06:35:10 | 10:05:10 | BND TWR | Roger; standby; confirm 160 Dubai |
| 06:35:15 | 10:05:15 | IR655 | Flight level 140 if possible |
| 06:35:16 | 10:05:16 | BND TWR | 140 |
| 06:35:17 | 10:05:17 | IR655 | Okay |
| 06:38:00 | 10:08:00 | IR655 | * Tower, 655 |
| 06:38:05 | 10:08:05 | BND TWR | * 655, go ahead |
| 06:38:06 | 10:08:06 | IR655 | * Request start up for taxi |
| 06:38:10 | 10:08:10 | BND TWR | Cleared to start, temperature 35 {Celsius} |
| 06:38:14 | 10:08:14 | IR655 | 655; thank you |
| 06:40:21 | 10:10:21 | IR655 | Tower, 655; request taxi |
| 06:40:26 | 10:10:26 | BND TWR | IranAir 655, taxi to holding point, runway 21, via Tango 05; wind calm; QNH 998 {barometric pressure in millibars}; time is 0640 {UTC} |
| 06:40:37 | 10:10:37 | IR655 | IranAir 655 cleared taxi for runway 21, taxiway 5; 998 |
| 06:41:17 | 10:11:17 | IR655 | * Confirm taxiway 5 is open |
| 06:41:20 | 10:11:20 | BND TWR | * Yes, it is open |
| 06:41:22 | 10:11:22 | IR655 | (Microphone click) |
| 06:41:44 | 10:11:44 | BND TWR | * 655, caution; construction work in progress at the entrance of taxiway 5 |
| 06:41:50 | 10:11:50 | IR655 | (Microphone click) |
| 06:41:59 | 10:11:59 | IR655 | * Tower, can we use taxiway 7 |
| 06:42:08 | 10:12:08 | BND TWR | * Continue taxi via parking area to taxiway 7. Caution construction work on both sides |
| 06:42:20 | 10:12:20 | IR655 | (Microphone click) |
| 06:43:19 | 10:13:19 | BND TWR | IranAir 655, copy your ATC clearance |
| 06:43:24 | 10:13:24 | IR 655 | Go ahead |
| 06:43:25 | 10:13:25 | BND TWR | IranAir 655 is cleared to destination Dubai via flight plan route 1 ; climb and maintain flight level 140 {14,000 feet, pressure altitude}; after take off follow simulated MOBET 1 BRAVO departure 2 {a straight ahead climb}, squawking ALPHA 6760 {transponder ID code} |
| 06:43:41 | 10:13:41 | IR 655 | IranAir 655 cleared destination flight planned route; flight level 140; simulated MOBET 1 BRAVO; and squawk 6760 |
| 06:43:53 | 10:13:53 | BND TWR | Squawk 6760, IranAir 655; that is correct; call when ready for departure |
| 06:43:59 | 10:13:59 | IR 655 | Call you for departure |
| 06:45:30 | 10:15:30 | IR 655 | Tower, IranAir 655 ready for take off |
| 06:45:34 | 10:15:34 | BND TWR | IranAir 655 cleared for take off runway 21; wind calm; after departure contact approach 124.2; have a nice flight |
| 06:45:43 | 10:15:43 | IR 655 | 655 cleared for take off 21; after take off, with approach; thank you very much; good day |
| Bandar Abbas Approach Control (BND APP) 124.2 MHz | |||
| 06:49:18 | 10:19:18 | IR 655 | Good morning; IranAir 655 airborne out of 3550 {feet, actual**} |
| 06:49:24 | 10:19:24 | BND APP | IranAir 655, good morning to you; continue as cleared; next report at MOBET {30 n.miles from the VORTAC navigation radio, at the center of the airport} * and standing by for your estimate |
| 06:49:33 | 10:19:33 | BND APP | Roger; estimate MOBET time 52 {10:22 local time}, FIR 58 {10:28}, destination 0715 {11:15 Dubai time} {FIR refers to DARAX, 69 n.miles from the center of the airport, the next waypoint after MOBET, and the Flight Information Region boundary between Tehran ACC (Area Control Centre) and Emirates ACC} |
| 06:49:43 | 10:19:43 | BND APP | IranAir 655, roger |
| Iran Air Company frequency 131.8 MHz | |||
| 06:50:00? | 10:20:00? | IR 655 | {No transcript}: “On reaching 1000 ft altitude the flight would have commenced flap retraction and transition from initial climb to enroute climb followed by the after take-off checks. During this time the call was made to the Iran Air office at Bandar Abbas with a departure message.” ICAO, ¶ 2.10.9, p.16 |
| Tehran Area Control Centre (THR ACC) 133.4 MHz | |||
| 06:50:54 | 10:20:54 | IR 655 | ...(unreadable)... |
| 06:50:59 | 10:20:59 | THR ACC | Station calling Tehran |
| 06:51:04 | 10:21:04 | IR 655 | IranAir 655 from Bandar Abbas to Dubai; out of level 70 {7,525 feet actual**} for 140; estimating FIR 58, Dubai 0715 |
| 06:51:20 | 10:21:20 | THR ACC | Roger; report maintaining 140 and passing DARAX |
| 06:51:26 | 10:21:26 | IR 655 | Roger |
| 06:51:28 | 10:21:28 | THR ACC | Confirm you are squawking 6760 |
| 06:51:30 | 10:21:30 | IR 655 | Affirmative |
| Bandar Abbas Approach Control (BND APP) 124.2 MHz | |||
| 06:54:00 | 10:24:00 | IR 655 | 655, position MOBET, out of 120 {12,525 feet, actual**} |
| 06:54:07 | 10:24:07 | BND APP | IranAir 655, roger; contact Tehran Control 133.4; have a nice flight |
| 06:54:11 | 10:24:11 | IR 655 | Thank you; good day |
_____
Source: ICAO Report, pp.B-2,3,4 (Nov. 7 1988, derestricted Dec. 7 1988), text {in braces} added. These transcripts are omitted from portions of the ICAO report published at 28 I.L.M. 896 (1989). Accord: U.N. Doc. S/PV.2818, pp.11-15 (U.N. Security Council, July 14 1988) (without time stamps).
* Translation from Farsi.
** See below for the difference between actual altitude and the flight-level pressure altitude broadcast by the aircraft’s transponder.
__________
Just as Mohsen Rezaian, the Iran Air pilot, reported reaching MOBET and 12,500 feet (flight level 120) (06:54:05) — more than 12 miles inside Iran’s own territory — William C. Rogers III, Commander of the USS Vincennes, 12 miles away, in the center of the airway (A59W), and also inside Iran’s territory, turned his firing key (06:54:05). DoD Report, ¶ (8)(a), p.37; Crowe Endorsement, ¶ d, p.5.
14 seconds later, following a confirmation and a faulty effort by one crew member to press the right buttons, the Missile System Supervisor (MSS) pressed the “Firing Authorize” button (06:54:19). 3 seconds later the first missile launched (06:54:22), and 1 second later the second, at a speed of Mach-2.5 (1,650 knots, 1,900 mph). DoD, p.38, ¶ (n); Senate Hearing, p.12; House Hearings, p.94; ICAO, p.18, ¶ 2.11.5.
32 seconds after Rezaian’s final “good day,” as Iran Air 655 reached 13,500 feet and still climbing, 1,000 feet below his assigned flight-level 140, two surface-to-air SM-2 missiles — each with passive homing (radar echo), a proximity fuse, and a high-explosive warhead wrapped in 6,000 steel ball-bearings — exploded (06:54:43, 44) (ICAO, p.1, ¶ 1.1.5 (time); DoD, p.39, ¶ (bb)), 21 seconds after launch — shredding the bodies of those on board and blowing off the tail and the left wing. More than 2-1/2 miles high, and still climbing at 380 knots, Iran Air 655 plunged 82 seconds, into the sea (06:56:05). ICAO, p.22 (time). “Few of the bodies recovered were complete”:
“1.12.3. One of the large pieces of engine cowling showed external damage, some 15-20 penetrations, 1-10 cm in size and in a horizontal direction in a 45 degree angle from behind. The cowling originated from the aft left side of one of the engines. The penetrations were consistent with missile detonation beneath the aircraft, between the wing and the tail.”
“1.13.1. The bodies of the flight crew had not been recovered by 1 October 1988. By early August 1988 the remains of some 192 victims had been recovered. Few of the bodies recovered were complete. Some 180 victims were identified, many based on circumstantial evidence.”
ICAO, ¶ 1.12.3, ¶ 1.13.1, p.7.
_______________
Part Two
U.S. Military Officers did what they always do when they get caught, doing something wrong.
They lied.
You can say anything you want during a debate, and 80 million people hear it.” If “anything” turns out to be false and journalists correct it, “So what. Maybe 200 people read it, or 2,000 or 20,000.
Peter Teeley, Press Secretary to George H.W. Bush (Oct. 1984), quoted by John R. Macarthur
This, on the principle well articulated by George H.W. Bush’s Press Secretary, that lies, at the time the news breaks, will reach tens or hundreds of millions of people, and mold their opinions and their memories.
And years later, when some nobody journalist patiently dissects their deceit, it’s history, not “news”. And, if any news editor does bother to report it, on a slow news-day, s/he’ll put it at the bottom of page-32 of some newspaper and “So what. Maybe 200 people read it, or 2,000 or 20,000.”
The national myth remains intact. Mission accomplished.
For many hours, the Commander of the Vincennes huddled with his fellow commanders and his fleet commander and, presumably, by phone with higher commands and the Joint Chiefs of Staff in the States. And finally — after 9-1/2 hours — he made his agreed Operation Report of the incident (July 3 1988, 16:30 Zulu/UTC/GMT, 12:30 p.m. EDT), which the DoD report concealed, but summarized:
“Vincennes OPREP-3 031630Z Jul 88 was readdressed by the CJTFME {Commander, Joint Task Force, Middle East} under the same DTG {dating} providing a timeline for both surface and air engagement and reconfirming altitude as 7800 feet and descending, speed 455 kts, Mode II, 1100 {military transponder squawk-code}, ID as F-14, and that the aircraft had ignored MAD {Military Air Distress} and IAD {International Air Distress} warnings. Additionally: TN 4131 {Track Number, the computer-assigned display label}, Bearing/Range 005T/9NM; Mode III, 6675 {civilian transponder squawk-code}, course 185T, and CBDR {Constant Bearing, Decreasing Range} amplifying data was supplied.”
DoD, ¶ (2)(e), p.42.
This report asserts, as unassailable fact, information which, in 9-1/2 hours, the author of the report, William C. Rogers III, Commander of the USS Vincennes (CG-49), had ample opportunity — and the duty — to discover was erroneous. And equally, his commander at Fifth Fleet headquarters, Bahrain, Anthony A. Less (CJTFME), who endorsed this false report by submitting it to the Pentagon.
During this 9-1/2 hours, David R. Carlson, the Commander of the USS Sides (FFG-14) — only 18 n.miles away, nearer the airport (but outside the airway), in real-time data-link with the Vincennes (Link-11) — who tracked the whole incident on his radar, was certainly consulted and reported what he and his officers saw, which bore no resemblance to this false report. DoD, ¶ 2, p.8; ¶ i, p.28; ¶ i, p.33; ¶ c-e, p.36; ¶ m, p.37. Even as John James Kearley, Commander of the USS Elmer Montgomery (DE-1082), was also consulted — the third member of the 3-ship squadron and an eye-witness to the explosion and descent of the aircraft into the sea (DoD, ¶ cc, p.39), but without his aircraft radar switched on at the time (DoD, ¶ i, p.31). Additionally, during this 9-1/2 hours, the Commander of the Vincennes had ample opportunity to rerun his computer tapes of the incident which recorded nothing resembling his false report. This he apparently did, judging from the DoD summary of his concealed report, because he provided a time-line, “and CBDR amplifying data was supplied”.
The U.S. criminal law requires United States Officers to file truthful reports. 18 U.S.C. § 1001. If, in addition to the actual facts of the incident, the officers wish to also include their erroneous view, in the heat of the moment, of the actual facts, then their erroneous view is also a suitable topic to report, provided what they claim to believe is a truthful account of what they actually believed.
But it’s a criminal lie to conceal the actual facts, and to conceal conflicting views of the actual facts, and, instead, to assert as unassailable fact their erroneous view of the actual facts. And this is what the Commander of the Vincennes apparently did and his commander as well (CJTFME), who surely was not so incompetent, and derelict of his duty, as to omit to confer with his Commander of the USS Sides and to order the Vincennes tapes to be reviewed prior to the report.
On the basis of this (concealed) false report, William J. Crowe Jr., Chairman of the Joint Chiefs of Staff, held a press conference later the same day, at the Pentagon, about 10-1/2 hours after the ambush (1:30 p.m. EDT, 17:30 UTC, AP880703-0071):
Navy Missile Downs Iranian Jetliner
By George C. Wilson
Washington Post Staff Writer
Monday, July 4, 1988
A U.S. warship fighting gunboats in the Persian Gulf yesterday mistook an Iranian civilian jetliner for an attacking Iranian F14 fighter plane and blew it out of the hazy sky with a heat-seeking missile, the Pentagon announced. Iran said 290 persons were aboard the European-made A300 Airbus and that all had perished.
“The U.S. government deeply regrets this incident,” Adm. William J. Crowe Jr., chairman of the Joint Chiefs of Staff, told a Pentagon news conference.
The disaster occurred at mid-morning over the Strait of Hormuz, when the airliner, Iran Air Flight 655, on what Iran described as a routine 140-mile flight from its coastal city of Bandar Abbas southwest to Dubai in the United Arab Emirates, apparently strayed too close to two U.S. Navy warships that were engaged in a battle with Iranian gunboats.
The USS Vincennes, a cruiser equipped with the most sophisticated radar and electronic battle gear in the Navy’s surface arsenal, tracked the oncoming plane electronically, warned it to keep away and, when it did not, fired two Standard surface-to-air missiles.
Navy officials said the Vincennes’ combat teams believed the airliner to be an Iranian F14 jet fighter. No visual contact was made with the aircraft until it was struck and blew up about six miles from the Vincennes; the plane’s wreckage fell in Iranian territorial waters, Navy officials said.
Iranian vessels and helicopters searched for survivors, but there was no indication last night that anyone survived what apparently is the sixth worst aviation disaster. Iranian television broadcast scenes of bodies floating amid scattered debris.
It was the first time any U.S. military unit had shot down a civilian airliner. It occurred almost five years after a Soviet fighter pilot shot down an off-course Korean Air Lines Flight 007, killing 269 people.
Iran accused the United States of a “barbaric massacre” and vowed to “avenge the blood of our martyrs.”
President Reagan in a statement {1:30 p.m. EDT, 17:30 UTC} said he was “saddened to report” that the Vincennes “in a proper defensive action” had shot down the jetliner. “This is a terrible human tragedy. Our sympathy and condolences go out to the passengers, crew, and their families ... We deeply regret any loss of life.”
Reagan, who was spending the Fourth of July holiday at Camp David, said the Iranian aircraft “was headed directly for the Vincennes” and had “failed to heed repeated warnings.” The cruiser, he said, fired “to protect itself against possible attack.”
News of the downing of the plane began with sharply conflicting accounts from Iran and from the Defense Department of what had transpired in the Persian Gulf. Early yesterday, Tehran broadcast accusations that the United States had downed an unarmed airliner.
The Pentagon at first denied the Iranian claims, declaring that information from the fleet indicated that the Vincennes, equipped with the Aegis electronic battle management system, had shot down an attacking Iranian F14 jet fighter. But after sifting through more detailed reports and electronic intelligence, Reagan directed the Pentagon to confirm there had been a tragic case of mistaken identity in the war-torn gulf.
Crowe, in his hastily called news conference at the Pentagon, also backed up the skipper of the Vincennes and faulted the Iranian airline pilot. Crowe said the Airbus had flown four miles west of the usual commercial airline route from Bandar Abbas to Dubai and that the pilot ignored repeated radioed warnings from the Vincennes to change course.
Why and how the Vincennes mistook the bulky, wide-bodied Airbus A300 for a sleek, supersonic F14 fighter plane barely a third the transport’s size will be the subject of “a full investigation,” Reagan promised. A military team under the command of Rear Adm. William N. Fogarty of the U.S. Central Command will leave this week to begin that investigation, Defense Department officials said.
The shootdown of the Airbus represents the biggest loss of life on the strategic waterway since the U.S. warships began escorting Kuwaiti tankers in and out of the Persian Gulf last July. Pentagon officials then said the increased U.S. naval presence would have from a “low to moderate risk” of provoking confrontations with Iran.
But in the past year, although the United States and Iran are not in a formal state of war, there have been a series of brief but fierce sea battles in the gulf between the two countries’ military forces. Vigilance and readiness among U.S. forces intensified after the near-sinking of the patrol frigate USS Stark by an Iraqi fighter-bomber on May 17, 1987, in a missile attack that killed 37 sailors.
Yesterday started out as another sea battle, and ended with what the Vincennes Commanders misinterpreted as a “Stark profile” attack on the high-tech cruiser. Crowe in his briefing and other Navy and Defense Department officials offered a detailed version of how the shoot-down occurred.
At 2:10 a.m. EDT, the Pentagon said, three Iranian Boghammar gunboats fired on a helicopter that had flown off the Vincennes on a reconnaissance mission. The helicopter flew back to the cruiser unscathed. The Vincennes and a smaller warship, the frigate USS Elmer Montgomery, a half-hour later closed on the gunboats and put them under fire with 5-inch guns, sinking two and damaging the third.
At 2:47 a.m. EDT, the Iranian Airbus with almost a full load of passengers took off from Bandar Abbas, a big Iranian naval base on the northern coastal elbow of the Strait of Hormuz. The field at the base is used by civilian and military aircraft and recently had become the center for Iran’s dwindling force of F14s, a twin-engine, two-place fighter that the United States sold to Iran during the rule of the shah.
Two minutes after the Airbus took off, the far-reaching radars of the Vincennes Aegis cruiser saw the plane was coming its way. The skipper of the ship, operating under liberalized rules of engagement that call for U.S. captains in the Persian Gulf to fire before being fired upon to avoid another Stark disaster, warned the approaching aircraft to change course, according to the Pentagon.
The Vincennes and most airliners are equipped with identification of friend or foe (IFF) electronic boxes that query each other across the sky to establish identities. The Vincennes’ IFF questioned the Airbus IFF via telemetry, but received no response. A response would come in radio pulses that would be deciphered and displayed as an identifying number on the ship’s combat information center consoles.
Failing to raise the Airbus by IFF, the Pentagon said, the Vincennes broadcast its warnings by voice radio, using the emergency UHF and VHF channels that aircraft crews would hear if they followed standard practice of monitoring those frequencies. Crowe said three warnings were sent over the civilian emergency channel and four over the military one, called “Guard.” The Pentagon said the Vincennes could have issued the warning over the Air Traffic Control channel but did not.
“The suspect aircraft was outside the prescribed commercial air corridor,” Crowe told reporters. Defense Department officials said later that the Airbus was four miles west of commercial air corridor. “More importantly,” Crowe continued, “the aircraft headed directly for Vincennes on a constant bearing at high speed, approximately 450 knots.”
Without becoming specific, Crowe said there were “electronic indications on Vincennes” that led the U.S. crew to conclude the approaching airliner was an F14. “Given the threatening flight profile and decreasing range, the aircraft was declared ‘hostile’” at 2:51 a.m. EDT. The airliner at that crucial moment was on a course of almost due south, 185 degrees, and descending toward the Vincennes from an altitude of 7,800 feet, according to Crowe. Visibility was no more than five miles, Crowe said.
Three minutes later, at 2:54 a.m. EDT, the Vincennes launched two Standard surface-to-air missiles from its deck. The missiles whooshed toward the twin-jet airliner, which was nine miles away and not visible to the naked eye because of the haze hanging over the gulf. The Standard missiles homed in on the heat of the quarry’s engines and at least one of them exploded when it pulled abreast of the Airbus. Such a missile hit usually slices an aircraft apart and turns it into a fireball of burning fuel.
“At least one hit at an approximate range of six miles,” Crowe said. “We do have some eyewitness reports {USS Elmer Montgomery} that saw the vague shape of the aircraft when the missile hit, and it looked like it disintegrated.”
Asked if the Vincennes’ skipper had been prudent or impetuous by firing at a plane he could not see, Crowe replied: “The commanding officer conducted himself with circumspection and, considering the information that was available to him, followed his authorities and acted with good judgment at a very trying period and under very trying circumstances ... Not only was he following this aircraft and concerned about it,” but he also “was engaged on the surface with Iranian units.”
Crowe said it was “logical” for the skipper to assume an aircraft that was coming down from the sky at high speed and would not respond to radio warnings was putting the Vincennes “in jeopardy.”
At another point in the news conference Crowe broadened his defense of the Vincennes skipper, declaring “the No. 1 obligation of the commanding officer of a ship or units are the protection of his own people. We deeply regret the loss of life here, but that commanding officer had a very heavy obligation to protect his ships, his people. We’ve made that clear throughout the Persian Gulf mission ...”
Crowe, who used a chart of the Strait of Hormuz that displayed the approximate positions of the vessels and the route of the airliner, said he did not have enough data to explain fully why the multiple kinds of detection gear aboard the Vincennes mistook a wide-bodied jetliner for a fighter.
But he noted that the Vincennes’ radar was focused on a plane coming at it head-on, reflecting a smaller dot on the console screens than would be the case from a side view. Also, he said, no Air Force Airborne Warning and Control System (AWACS) or Navy Hawkeye sentry planes were aloft over the Strait of Hormuz to provide additional identification data to the Vincennes at the time of the shootdown.
Navy leaders said Iranian commercial aircraft had flown over U.S. warships in a threatening manner at least eight times before the Stark was hit by two French Exocet missiles fired by an Iraqi jet. Ever since the Stark attack, skippers in the gulf have been less tolerant of such apparent threats.
Asked if the skipper of the Vincennes would have held his fire under the interpretation of the rules of engagement followed before the Stark was attacked, Crowe replied: “I don’t know. Certainly the rules of engagement would not have been as specific as the authorities granted him.” He said another review of the rules of engagement would be part of the general investigation of the shootdown.
Crowe said there were “fundamental differences” between the actions of United States in this incident and the Soviet Union in the downing of Korean Air Lines Flight 007, which strayed into Soviet airspace on the night of Sept. 1, 1983, during a flight from Alaska to Japan. The Soviet airspace was not a war zone like the Persian Gulf, Crowe said, “and there was not combat in progress” as was the case yesterday. “It was at very high altitude” and no Soviet warnings were issued.
“In the Persian Gulf,” Crowe said, there is very little time or maneuver room when ships are put at risk. “We’re fighting in a lake.”
Staff writer Molly Moore contributed to this report.
© Copyright 1996 The Associated Press
This Sunday afternoon press briefing, broadcast on TV and radio, gripped a worldwide audience of hundreds of millions of people, live and in later news broadcasts.
It was the day of the 1988 Wimbledon men’s tennis final. Interrupted by rain, with news reports of the ambush filling some of that time. Concluded the next day, a U.S. national holiday, and a day of more such news, and rebroadcasts of this press briefing.
SSR/IFF: Transponder squawk-code
Crowe stated the aircraft did not broadcast a civilian transponder squawk-code:
“Question: Was the airliner squawking, as it should be, with its IFF? ...
Admiral Crowe: ... You’re asking me about IFF. We did have some electronic emanations, but I really can’t say any more than that.
Question: He didn’t identify himself as a commercial?
Admiral Crowe: No, he did not.
Question: He was squawking something but not the recognizable “I am an airliner?”
Admiral Crowe: Well, it led us to believe that it was a military aircraft.
Question: How come?” {unanswered}
William J. Crowe Jr. (Admiral, Chairman, Joint Chiefs of Staff), Press Briefing, July 3 1988.
This was a bold, powerful, persuasive lie. A lie of Crowe’s own personal fabrication, independent of events thousands of miles away.
Persuasive, because the absence of a civilian SSR/IFF transponder squawk code is very fishy. Every airliner broadcasts a squawk-code (as required by binding international Air Traffic Control regulations), to identify its digital data-block, and its pressure altitude (flight level), displayed on radar screens equipped to decode Air Traffic Control data — like the ones on board the USS Vincennes, in its Combat Information Center, the Commander’s cockpit.
Bold, because other U.S. Officers had also seen what Crowe had, in his possession, and knew, for a fact, that Crowe was lying:– The Operation Report from the Vincennes Commander which, though false in most respects, nevertheless disclosed receipt of the aircraft’s IFF civilian transponder squawk-code. But, senior U.S. Military Officers well know that lying is part of their duty, and they can be certain that if they don’t keep quiet when their colleagues lie, and themselves lie on orders, their career prospects are doomed. At this Press Briefing, Crowe was modeling for all senior U.S. Military Officers, and their junior aspirants, what it takes to reach the top of the pile in this powerful United States Government institution, operating in secret and largely outside the rule of law, an essential character quality for leadership:– bold deceit.
The Mode III IFF of 6760 and increasing altitude seen in the data tapes from USS Vincennes were corroborated by testimony and statements from USS Sides.
William M. Fogarty, CentCom, DoD Report, p.28, ¶ i (July 28 1988)
A lie, because Crowe also had, in his possession, an account of what the Commander of the USS Elmer Montgomery saw. And, if he had that, then he certainly also had a account — later disclosed in the DoD report — of what the officers of USS Sides saw (the third member of the 3-ship squadron). The Sides officers absolutely refuted the Vincennes Commander’s false report, and themselves saw the aircraft’s IFF civilian transponder squawk-code, and no other IFF signal of any sort, with no equivocation.
Information [{redacted}] further corroborated that TN 4131 was squawking Mode III-6760.
William M. Fogarty, CentCom, DoD Report, p.28, ¶ j (July 28 1988)
A lie, because Crowe surely also had, in his possession, the very same “electronic intelligence” the President had, and later mentioned in the DoD report (¶ 2, p.8; ¶ j, p.28), doubtless reporting the aircraft’s civilian transponder broadcasts — squawk-code (mode A) and pressure-altitude (mode C). And, convincingly, a tape recording and transcript of the radio broadcasts between the pilot and Air Traffic Control, and the supposed “warnings” broadcast by U.S. warships. And an account of the radar flight-profile (high and climbing, in the middle of the airway).
Senator Carl Levin: On page 6 of your report, paragraph 4, you indicate that Flight 655 was directed by the Bandar Abbas tower to begin a normal climb to an assigned altitude of 14,000 feet, to squawk Mode III code, et cetera. How do we know that?
Admiral Fogarty: Sir, I have to talk to that in closed session. I cannot discuss that at this level.
William M. Fogarty, CentCom, Senate Hearing, p.25 (Sept. 8 1988), referring to DoD Report, p.6, ¶ D.4. (July 28 1988).
These redacted intelligence sources were, presumably, Naval/NSA signals intelligence officers onboard the Vincennes itself at the time with the Naval Security Group Command (NSGC) in charge of the Ship’s Signals Exploitation Space (SSES); the NSA/DIA on-shore listening/radar station in Oman, on the Musandam Peninsula (at 2,000 feet elevation, with line-of-sight to Bandar Abbas airport, 45 n.miles north); the Hawkeye crew aloft nearby at the time above the Northern Gulf of Oman; the AWACs crew aloft at the time above the Northern Persian Gulf; British Intelligence; British/Italian warships; etc. (several of these).
“Surely,” because that would be the first thing any competent officer in Crowe’s position would ask for. He had many hours to get it. And, naturally, the President apparently also wanted it. And got it.
CBDR: Constant Bearing, Decreasing Range
The suspect aircraft was outside the prescribed commercial air corridor. More importantly, the aircraft headed directly for Vincennes on a constant bearing at high speed.
William J. Crowe Jr. (Chairman, J.C.S.), Press Briefing, July 3 1988
Crowe listed among his reasons — that the Vincennes Commander “acted with good judgment” in deciding to attack — that Iran Air 655 was “headed directly for the Vincennes,” “coming its way,” “headed directly for Vincennes on a constant bearing,” “coming at it head-on”.
Duh! is the expression which now leaps to mind – an exasperated: “So what”.
But it did not leap to the minds of the hundreds of millions of TV viewers of his press briefing, because Crowe concealed the whereabouts of the Vincennes — dead-center in the airway — one of those material omissions referred to in 18 U.S.C. § 1001 which denominate a “materially false statement” (a prima facie “lie”). And, he elaborated his deceit by asserting that the Vincennes was “outside” the airway, claiming the “suspect aircraft” (which was headed directly for the Vincennes) was four miles “outside the prescribed commercial air corridor”. Very, very fishy.
Like his transponder lie, this too was a deceit of Crowe’s own personal fabrication (in conspiracy with his complicit staff), independent of events thousands of miles away.
Crowe had, in his possession, the Operation Report from the Vincennes Commander. And, his staff had been on the phone for many hours investigating this incident. Certainly, this report, and those investigations, specified the geographical coordinates of the Vincennes at the time of the attack, a normal part of an Operation Report, a preoccupation of all naval officers dealing with charts, a direct read-out from the display of the warship’s laser-gyro inertial navigation system, recorded continuously and time-stamped as the log of the warship’s movements, and no doubt broadcast automatically every minute or so via satellite to the Pentagon, charting in real-time the position of all U.S. warships at sea. Crowe produced a chart at his Press Briefing showing the (supposed) position of the Vincennes.
And, Crowe certainly had a published chart of the public airway — which itself is defined by geographical coordinates 1 — showing its 20-mile width. Yet, that airway chart would have provoked questions at the press briefing and exposed his deceit. So, he concealed that as well:
“Admiral Crowe: This is sort of a simplistic chart, we’re trying to keep it simple.”
William J. Crowe Jr. (Admiral, Chairman, Joint Chiefs of Staff), Press Briefing, July 3 1988.
_______________
Judging from his bold lies at his Press Briefing, I wonder if Crowe was complicit in consenting that the Commander of the Vincennes could file a false report in the first place (a criminal act), to enable Crowe to supplement his own lies at his Press Briefing with details from that false report.
I would expect this, from a chain of command conducting an unlawful secret offensive war against Iran, as a Belligerent, which had already offensively attacked and destroyed much of Iran’s Coast Guard fleet in offensive secret acts of war, not to mention other tactical military support to Iraq, in further aid of Iraq’s war of aggression against Iran (1980-1988), rendering the United States a co-Belligerent with Iraq in willful violation of the U.S. Constitution (without a vote by Congress).
Such bold lies are routine by senior U.S. Military officers, to cover-up their unlawful actions, and their President’s unlawful actions. This President had made secret unlawful offensive wars, a violation of his oath of office, the hallmark of his Presidency, beginning with launching a secret offensive war against Nicaragua (1981-1990). And lying about them when discovered. Such labelling the bombing of the U.S. Marine Corps barracks in Beirut (Oct. 23 1983) a “terrorist” act. What was, instead, plainly, a prima facie lawful military operation in a complex war Reagan had secretly, and unlawfully, directed (Sept. 11 1983) the U.S. Military to enter offensively, as a Belligerent. Which they promptly did, 6 weeks before the bombing, well knowing what they were doing was offensive warfare which Congress had not authorized.
Rogers’ (concealed) Operation Report, submitted 9-1/2 hours after the event (12:30 p.m. EDT, 16:30 UTC), looks to be one of the most carefully crafted criminal lies in the history of the U.S. Navy (and there have been many). Criminal lies on orders are never prosecuted by the U.S. Government.
Crowe certainly lied at his Press Briefing, to the worldwide public in their hundreds of millions, Members of Congress amongst them, a routine way to lie to Congress without risking criminal prosecution.
And I wonder if Crowe also lied privately to his Commander-in-Chief (the President) (a criminal act) and to his other political masters (Secretary of Defense, Secretary of State, National Security Advisor, Vice President, White House Chief of Staff) (a criminal act).
But, looking over the cast of characters in the conference telephone call with the President (and they talked variously with each other earlier), and judging from the bold, confident audacity of Crowe’s lies, my guess is they all agreed for the Vincennes Commander to file a false Operation Report and for Crowe to lie at his Press Briefing.
National myth-making, a Reagan/Bush speciality.
It wouldn’t be the first time that U.S. Military Officers lied, in a criminal conspiracy, on the criminal orders of a U.S. President, as Ward Boston, to his credit, eventually confessed (Oct. 9 2003) (USS Liberty, June 8 1967).
The White House was alerted to the shooting early Sunday. National Security Adviser Colin Powell called the President at 4:52 a.m. {08:52 UTC} Reagan received a written update from Powell’s deputy, John Negroponte, at 8:14 a.m. {12:14 UTC}
But it wasn’t until 9:50 a.m. {13:50 UTC} that Negroponte called Reagan and said it appeared it was a civilian plane that had been shot down—not an Iranian fighter.
The President, at Camp David, was on a conference call with Vice President George Bush and other top White House officials at 1 p.m. {17:00 UTC} Twenty minutes later, press secretary Fitzwater issued the President’s statement of regret. {17:20 UTC}
Timothy J McNulty, U.S. Downs Iranian Jetliner, 290 Aboard, © Chicago Tribune, July 4 1988, p.1.
In on the call were Vice President George Bush, Secretary of State George P. Shultz, Defense Secretary Frank Carlucci, Crowe, Powell and White House chief of staff Kenneth Duberstein, {White House spokesman Marlin} Fitzwater said.
Fred Kaplan, 290 Killed as US Cruiser’s Missile Downs Civilian Iran Jet Over Gulf, © Boston Globe, July 4 1988, p.1.
AP880703-0044, AP880703-0055, AP880703-0071.
It’s no defense to a criminal indictment, that the President, Secretary of Defense, and Members of Congress may consent to be lied to. Their consent does not render a criminal report lawful. Likewise, Crowe and his subordinates in the U.S. Military do not have the legal capacity to legalize a criminal report by their subordinates. If they authorized the Commander of the Vincennes to file a false report, they are simply complicit with him, and equally guilty with him, in their collective criminal act (18 U.S.C. § 1001) — gang members, henchmen, aiders and abetters, co-principals (18 U.S.C. § 2), united in a criminal conspiracy (18 U.S.C. § 371).
This is an offense against the United States of America. The President is not the United States of America, nor any other U.S. Officer. The United States of America does not consent to be lied to. 18 U.S.C. § 1001.
Though, it’s the apparent secret policy of the U.S. Department of Justice to not prosecute U.S. Government Officers who lie on orders of the U.S. President.
_______________
If you park your car in the middle of the railroad tracks, then any train which happens along will be CBDR your position (Constant Bearing, Decreasing Range).
So too, if you race down the middle of an airway in your warship: Any civilian aircraft which happens along will be CBDR your position.
Hence, if you’re in the middle of an airway, it is not a marker of hostile intent that an aircraft is “coming your way,” “heading directly for you,” “coming at you head on” — thus explaining Crowe’s decision to lie about the whereabouts of the Vincennes.
And a U.S. warship commander is therefore not entitled to take that factor (CBDR) into account in evaluating a target. Precisely the opposite of Crowe’s deceitful pretense.
If the warship commander doesn’t have the stomach to be overflown by aircraft in an environment rich with civilian overflights, then he’s unfit for that command. And, until he is relieved from duty, his commanders have the duty to ensure that he avoids civilian airways so that his unsuitable temperament does not imperil innocent lives.
But, as we shall see, Rogers did not attack because of a queasy stomach.
ATC frequencies
Crowe simply lied that the aircraft was warned seven times.
And the power of this lie lingered, after other of Crowe’s deceits were slowly exposed, one by one, in subsequent days. It proved to be the most persuasive influence on public opinion inside the US, which was desperate for any excuse to blind themselves to the proposition that their armed forces could act so recklessly and so ruthlessly, and their Commanders could lie so boldly.
If you ask anybody today inside the U.S. (the willfully deceived viewers) who watched these events, as they unfolded on TV in 1988 — smothered in TV coverage of the 1988 Presidential election campaign, Arms for Hostages, Iran/Contra, and other sleaze in the Reagan/Bush Administration — my guess is that 10 out of 10 them will, still today, cite their memory of these supposed warnings as justifying the U.S. ambush of Iran Air 655.
The simple truth is, the U.S. Military did not warn the aircraft a single time. And this decision by U.S. Military Commanders to not warn civilian aircraft is the third-most proximate cause of the killing (there were several).
Crowe began his warning lie with the truth, that the Vincennes broadcast its supposed warnings on two distress frequencies, MAD (243.0 MHz UHF) and IAD (121.5 MHz VHF).
For the pilots in Crowe’s audience, this straight-away marked the first glimmer of understanding how this killing came to be. But not for the rest of the hundreds of millions watching Crowe’s press briefing on TV. And Crowe managed to confound the pilots still, with his transponder lie and his airline route lie. Crowe’s entire audience was united in perplexity; just the way Crowe intended.
The warship officers did not broadcast on the frequencies the aircraft was certain to be listening to, as required by international civil aviation Air Traffic Control regulations, binding on all countries in the world, including the United States. It’s as simple as that. The warship radio-talker broadcast supposed warnings into the ether, but not into the radio receiver on board his postulated civilian target, which U.S. Military Officers could be certain was switched on, with the volume turned up.
All U.S. Navy commanders and officers know what those frequencies are. And if they don’t know, it’s because they don’t need to know, but they know how to find it out should their duties change and require them to. Or — as in the case of the Vincennes Commander and his officers, and their higher commands — it’s because they were recklessly indifferent to their duty to know.
This frequency information is available from any pilot, including the crews of the two helicopters on board the Vincennes itself, the flight centers on board all U.S. Navy aircraft carriers, the Air Traffic Control personnel on board all U.S. AWACs and Hawkeyes aloft, from the United States National Flight Center at Washington DC, the U.S. military’s own flight centers, any Air Traffic Control authority at any airport, including the Bahrain ACC, the home base of the U.S. Gulf Squadron for 40 years. And it’s published on all aircraft charts of the region. And how many thousands of those were in the hands of the thousands of pilots and navigators on U.S. Navy aircraft carriers and Air Force bases in the Gulf region, and onboard the Vincennes itself, boggles the mind to contemplate.
Yet, the Vincennes Commander paid this no mind; nor did any of his fellow commanders and officers or higher commanders.
And this I classify as “reckless negligence,” because the commanders responsible for deciding to not warn civilian aircraft could foresee the deadly consequences of their decision to violate their duty. And this includes the fleet commanders, and higher commands, responsible to design the protocol for antiair warfare in fleet operations.
But it also includes the individual warship commanders with authority to kill, and their subordinate officers whose conduct and decisions inform and influence the commander’s decision to kill. It’s the duty of all such killers to apply their minds to their separate and joint tasks and ensure that their operational protocol is suited to its purpose — the first of which is to not target civilians.
This reckless negligence by these senior U.S. Military Officers — a primary proximate cause of the wrongful killing of 290 people — deserves an award of prison time, for involuntary manslaughter (18 U.S.C. § 1112), arson (18 U.S.C. § 81, § 3559(c)(3)(B)), and criminal neglect (18 U.S.C. § 1115), exactly as the Iranians claimed, not the Legion of Merit.
This reckless negligence by these senior U.S. Military Officers did not occur in the heat of battle, and did not occur in the fog of war. It occurred days, weeks, and months earlier, in calm surroundings, when they decided to not do what their duty required them to do; namely, to apply their minds, to design and implement a protocol for talking to civilian aircraft, and to gather information into the Combat Information Center, on each of their warships, necessary to implement and operate that protocol.
Crowe’s lie about the warnings, is another deceit of Crowe’s own personal fabrication (and his complicit staff), independent of events thousands of miles away. It’s a compound lie, a false assertion coupled with a material omission.
Here’s the false assertion: The Iran Air crew would have heard the warnings “if they followed standard practice of monitoring those frequencies”. There is no such standard practice, as explained below, unless you’re over a vast ocean. And, as to four of the supposed warnings, the airliner could not possibly have been “monitoring those frequencies,” because no airliner is equipped with a military UHF transceiver (243.0 MHz UHF).
Here’s the material omission: There is a standard practice of what frequencies to broadcast on if you want to talk to a civilian aircraft which is not over a vast ocean. And this standard practice senior U.S. Military Officers violated when they decided to order their warship crews to broadcast warnings on the wrong frequency. This, Crowe didn’t mention in his press briefing.
This material omission, coupled with his “standard practice” assertion, is Crowe’s lie:– willfully inducing his audience to wrongly believe that the U.S. Military did what they were supposed to do, if they wanted to kill somebody.
A separate, additional, Crowe warning lie — falsely characterizing the broadcasts as “warnings” — is so pernicious that it’s discussed separately, below.
As evidence of Crowe’s willful deceit (that he understood the significance of his warning lie), the U.S. — after the ambush — changed its antiair warfare protocols to require U.S. Military Officers to monitor civilian Air Traffic Control frequencies — as their duty required them to do before the ambush — and to broadcast warnings on those frequencies, as a condition to targeting. And, they also changed their radio-talker script to conform (partially) to the binding international Air Traffic Control protocol on how to address an aircraft in flight (additional reckless negligence by Vincennes officers, and their higher commanders, discussed below).
NOTAMs
Crowe listed the failure of the aircraft to respond to the supposed seven warnings as a marker of hostile intent, which the warship commander was entitled to take into account in evaluating the target. This, too, President Reagan emphasized in his written statement approving the Vincennes ambush of Iran Air 655, which “failed to heed repeated warnings.” And his Vice President, George H.W. Bush, among his lies to the United Nations Security Council: “After seven — I want the Council to be sure to understand this — seven unanswered warnings, the captain did what he had to ...” And U.S. Military Officers in subsequent sworn lies to Congress.
To support his assertion, Crowe fabricated yet another deceit (together with his complicit staff), independent of events thousands of miles away. And, like his warning lie, this too is a compound lie.
Here’s the false assertion: That a U.S. NOTAM required civilian aircraft to respond to a warning, “to identify themselves and to state their intentions”:
“Admiral Crowe: ... In September 1987, as a result of the attack on the USS Stark and other incidents, the United States issued a Notice to Airmen, locally known as a NOTAM, which advised all aircraft in the Persian Gulf region that U.S. Navy ships were taking additional precautions, and of the need to identify themselves and to state their intentions.
Additionally, they were advised that {‘}failure to respond to requests for identification and intentions, or to warnings, and operating in a threatening manner could place the aircraft at risk by U.S. defensive measures{’}.”
William J. Crowe Jr. (Admiral, Chairman, Joint Chiefs of Staff), Press Briefing, July 3 1988.
Here’s the material omission: Nobody, ever once, asked the pilot to reply to a “warning,” to identify himself and state his intentions. And this Crowe certainly knew because he certainly had the text of the warnings and undoubtedly several copies, one from the Vincennes and the rest from at least three separate electronic intelligence sources.
Though Crowe misrepresented what the NOTAMs required, and lied about the text of the supposed “warnings” (below), I’m sure Mohsen Rezaian, the Iran Air pilot would have happily replied, had anybody asked him to (which nobody did). He was trained by Boeing in the USA, and his brother and sister-in-law lived there, now in Salt Lake City.
Yet, the NOTAMs nevertheless did not require civilian aircraft to respond to U.S. warships — contrary to Crowe’s claim, even if asked to reply — if they complied with the NOTAMs’ simple safety rule: Be higher than 2,000 feet within 5 miles of a U.S. warship, and don’t be “operating in a threatening manner”.
To reinforce it’s promise of safety, the United States included in its NOTAM (which Crowe cited) this reassurance (which Crowe concealed), that aircraft could overfly U.S. warships:
“The measures will be implemented in a manner which does not unduly interfere with the freedom of navigation and overflight.”
NOTAM, FAA FDC 052/87.
Bandar Abbas airport is on the Gulf coast, but it’s 42 miles inside Iran’s territory along airway A59W (and 47 miles along IR655’s route), due to its geography, at the base of a deep territorial bight, an indentation of the shoreline, like a bite out of a sandwich. Hence, any civilian aircraft departing Bandar Abbas airport is quickly above the NOTAMs’ 2,000 foot safety limit within a couple miles of the airport, more than 40 miles from where any U.S. warship might be. Departure is under Air Traffic Control. And climbing to altitude is not a threatening maneuver:
“Aircraft at altitudes less than 2000-feet AGL {above ground level} which are not cleared for approach/departure to or from a regional airport are requested to avoid approaching closer than 5-nm {nautical miles} to U.S. naval forces.
It is requested that aircraft approaching within 5-nm of U.S. naval forces establish and maintain radio contact with U.S. naval forces on 121.5-MHz VHF {civilian} or 243.0-MHz UHF {military}.
Aircraft which approach within 5-nm at altitudes less than 2000-feet AGL whose intentions are unclear to U.S. naval forces may be held at risk by U.S. defensive {ie: offensive} measures.”
NOTAM, 112119 KFDC, italics and text {in braces} added.
Crowe omitted to mention this NOTAM. And this NOTAM is so fatal to the pretense by U.S. Officers that the United States committed no wrong, that the DoD report-writers also decided to conceal it, from their deceitful report. But they weren’t content to simply conceal it, a prima facie criminal lie by material omission (18 U.S.C. § 1001). They went further and fabricated a blatant prima facie criminal lie (18 U.S.C. § 1001), pretending that their other NOTAM replaced all previous NOTAMs, notwithstanding they both appeared together in every weekly edition of the International Notices to Airmen (U.S. FAA):
“As a result of the attack of the USS Stark, the JCS {Joint Chiefs of Staff} issued an up-dated Notice to Airman (NOTAM) for the Persian Gulf, Strait of Hormuz, Gulf of Oman and North Arabian Sea dated 8 September 1987, which notified all Persian Gulf countries of additional defense precautions which U.S. warship would be exercising.”
William M. Fogarty (Rear Admiral, U.S. Navy, Director of Policy and Plans, U.S. Central Command), DoD Report, p.15, ¶ (17), italics added. This statement contains two blatant lies. The second, that the NOTAM disclosed what it concealed, is explained below (criminal Rules of Engagement).
Crowe, besides concealing the 2000 foot safety-rule NOTAM, quoted part of another NOTAM, also in effect at the time, which added an additional threat to aircraft above 2,000 feet. But only if the pilot did two things: fail to respond to requests (if asked to respond) and operate in a threatening manner:
“Failure to respond to requests for identification and intentions, or to warnings, and operating in a threatening manner could place the aircraft at risk by U.S. defensive {ie: offensive} measures.”
NOTAM, FAA FDC 052/87, italics and text {in braces} added.
The full text of both U.S. NOTAMs is quoted below. U.S. radio-talkers on the civilian frequency never once asked the radar-contact “to respond to requests for identification and intentions,” as the U.S. NOTAM required them to do.
And this, Crowe concealed, at his deceitful press briefing.
Taking both NOTAMs together, if you take off and climb normally, and stay above 2,000 feet, the NOTAMs do not require civilian aircraft pilots to respond to any radio contact from a U.S. warship, even if U.S. warship radio-talkers asked them to, even if they broadcast on the correct frequency, and even if they managed to speak correctly so that the pilot could know who the warship is trying to talk to.
None of these three things did the Vincennes civilian radio-talker do.
Hence, the failure of a pilot to respond (above 2,000 feet, and climbing normally) can not be taken as a marker of hostile intent (as Crowe asserted), there being no notice to pilots that they might be targeted if they do not respond.
Accordingly, a U.S. warship commander is not entitled to take that factor into account (failure to respond) in evaluating that target. Precisely the opposite of Crowe’s deceitful pretense.
By contrast, the IR655 pilot complied with the NOTAMs, in marked contrast to the U.S. warship commander. IR655 took off, and climbed steadily, on a steady course, to 12,500 feet, and was climbing still, when the Commander of the Vincennes — 12 n.miles away — turned his firing key (06:54:05), in blatant violation of the firm formal published written promise by the United States of America to not attack, as plainly stated in the U.S. NOTAMs — the precise opposite of Crowe’s pretence.
As evidence of Crowe’s willful deceit (that he understood the significance of what he quoted, and what he chose to conceal), the U.S. quickly, but quietly, revoked the 2,000 foot safety rule and issued a single replacement NOTAM (August 13 1988) — after the ambush (July 3), and before releasing the DoD Report (July 28) to the public (August 19) — changing the “and” to an “or,” in the bit Crowe quoted, to license themselves to attack a plane which does not respond even if it’s not also operating in a threatening manner. Though, to actually do so would be a text-book war-crime, under the targeting laws of war, and murder (18 U.S.C. § 1111) or manslaughter (18 U.S.C. § 1112), arson (18 U.S.C. § 81, § 3559(c)(3)(B)), and criminal neglect (18 U.S.C. § 1115), under the laws of peace:
“Failure to respond to requests for identification and intentions, failure to accept recommended headings, failure to respond to warnings, or continuing to operate in a threatening manner could place the aircraft (fixed wing and helicopters) at risk by U.S. defensive {ie: offensive} measures. Illumination of a U.S. naval vessel with a weapons fire control radar will be viewed with suspicion and could result in immediate U.S. defensive {ie: offensive} reaction.”
NOTAM, FAA FDC 056/88. Source: Photocopy of “Foreign Notices, Persian Gulf,” International Notices to Airmen, February 23 1989 (U.S. Department of Transportation, Federal Aviation Administration), originally issued August 13 1988 via AFTN (Aeronautical Fixed Telecommunication Network), italics and text {in braces} added.
IAD: 121.5 MHz VHF
Instead of themselves complying with obligations binding upon them — international flight rules concerning how to contact aircraft in flight — U.S. Military Officers arrogated unto themselves authority, which they did not possess, to impose upon civilian aircraft in foreign lands (where the United States has no such jurisdiction) an obligation, they did not have, to monitor 121.5 MHz. And, to license U.S. Military Officers to kill people who do not obey that unlawful order. And this we see daily, today, on the streets of Baghdad, just as we have seen on the streets of the USA as well, at Kent State University, for example:– U.S. Military Doctrine in action: Obey, or die.
Aircraft are obligated by international flight rules to monitor 121.5 MHz in only one instance:– when they are over a vast ocean and out of reach of their Air Traffic Control station. (VHF range is line-of-sight). This, to assist ships and boats and aircraft in distress.
And, ICAO recognizes that you can’t have two conversations at the same time and, so, you’re not obliged to monitor 121.5 MHz, even then, when you’re talking on another frequency:
“Guard of VHF Emergency Frequence
Pilots should remember that there is a need to continuously guard the VHF emergency frequency 121.5 MHz when on long over-water flights, except when communications on other VHF channels, equipment limitations, or cockpit duties prevent simultaneous guarding of two channels. Guarding of 121.5 MHz is particularly critical when operating in proximity to flight information region (FIR) boundaries; for example, on Route R220 between Anchorage and Tokyo, since it serves to facilitate communications with regard to aircraft which may experience in-flight emergencies, communications, or navigational difficulties.
Reference– ICAO Annex 10, Vol. II, Paragraphs 5.2.2.1.1.1 and 5.2.2.1.1.2.”
International Flight Information Manual, “Oceanic Long-Range Navigation Information” (Federal Aviation Administration, U.S. Department of Transportion).
If an aircraft is intercepted in flight by a military aircraft, then, at that time, “the pilot of the intercepted aircraft shall attempt radio contact with the interceptor aircraft on 121.5 MHz”. International Flight Information Manual, “International Interception Procedures” (FAA). Accord: “Interception of Civil Aircraft,” {66 kb html} § 5 (Action by intercepted aircraft), being Attachment A to ICAO Annex 2 {395 kb pdf}, International Standards: Rules of the Air (Ninth Edition, March 12 1990), to the Convention on International Civil Aviation, quoting Annex 2, Appendix 2, § 2.1(c).
In recent years, the U.S. FAA has ordered a listening watch on this frequency in the near vicinity of about 19 named large airports inside the U.S., where the United States does have jurisdiction to impose such a requirement.
In all other circumstances, 121.5 MHz is a frequency which a pilot, at his or her option, can choose to broadcast on, in an emergency, though pilots are recommended instead to contact the Air Traffic Control frequency they are then monitoring, where help is sure to be listening. In special circumstances (e.g., at low altitude, offshore, in remote areas, near boats, emergency ground personnel, or known rescue stations, and such), the pilot might feel s/he has a chance to find a closer listener on 121.5 MHz and s/he’s free to try that frequency if s/he wants to.
One of the two U.S. NOTAMs “requested” a listening watch on 121.5 MHz only if the aircraft was within 5 n.miles of a U.S. warship. Iran Air Flight 655 was never within 5 n.miles of any U.S. warship. The Vincennes Commander attacked (turned his firing key) when IR655 was more than 12 n.miles away.
The second U.S. NOTAM was not precise about when a pilot “should maintain a listening watch on 121.5 mHz” (“aircraft operating in these areas,” “within the Persian Gulf, Strait of Hormuz, Gulf of Oman, Arabian Sea”). In addition, the U.S. left in place its 5 n.mile rule, and this provides a gloss on what this second NOTAM means.
Iran Air Flight 655 was never itself within the Strait of Hormuz or the Persian Gulf. When the Vincennes radio-talker started his first warning broadcast, IR655 was 30 n.miles from the Strait of Hormuz, 7,000 feet above Iranian soil, and busy talking to Air Traffic Control on another (published) frequency. When he started his second (and final) warning broadcast, IR655 was 22 n.miles from the Strait of Hormuz, at 10,000 feet, paralleling Iranian soil less than 1 n.mile offshore. And the radio-talker, in that broadcast, never asked the pilot to do anything or to reply to the broadcast.
The pilot was probably one minute away from turning up the volume on his backup radio, which he may have already tuned to 121.5 MHz. He had just that moment finished his obligatory final report to Bandar Abbas Approach Control, that he had reached MOBET, exiting the Terminal Control Area (TCA) under the jurisdiction of Approach Control. At precisely that moment, when Rogers turned his firing key, the pilot had only two further immediate ATC radio obligations: First, to immediately switch frequencies from Approach Control (124.2 MHz) to the Tehran Area Control Center (131.8 MHz), his new ATC controller, beginning at MOBET. And secondly, to make his obligatory report, to Tehran ACC, upon reaching his assigned flight level 140, which he was then approaching at 1,500 feet per minute, about 1 minute away, about as long as it takes to read this paragraph.
Following that report to the Tehran ACC, still some 8-10 n.miles distant from the Strait of Hormuz, and that far inside Iranian territory, the pilot would then expect no further ATC conversations for the next 39 miles. He could then be free to listen to both his ATC frequency (131.8 MHz) and, on his backup radio, to 121.5 MHz, until he reached DARAX, about half-way to Dubai, where his next obligatory report was due, to both Tehran ACC and, immediately following yet another frequency change, to the Emirates ACC.
U.S. Military Officers did not possess authority, nor the United States jurisdiction, to impose a listening watch on aircraft in other lands. But they did possess authority, and the United States jurisdiction, to impose a listening watch on their own warship crews, to stand watch on relevant Air Traffic Control frequencies.
The ATC radio obligations on the pilot richly demonstrate why U.S. Military Officers were so extremely recklessly negligent in failing in their duty to require their radio-talkers to monitor the Air Traffic Control frequencies. This reckless negligence, by senior U.S. Military Officers, is the second-most proximate cause of the unlawful ambush of Iran Air 655 and the unlawful killing of its 290 innocent souls on board.
Had they done their duty, U.S. Military Officers would never have ordered their warship crews to broadcast on 121.5 MHz in the first place. Monitoring would have immediately revealed to the warship officers that the aircraft was an airliner, long before MOBET. And no broadcast to the pilot would have even been necessary. But if they wanted to broadcast a warning, then only a reckless fool would broadcast on 121.5 MHz to a pilot the fool knew was talking and listening on another, ATC, frequency.
The Vincennes Commander attacked in violation of his own NOTAM:
“Unidentified aircraft, whose intentions are unclear or who are approaching U.S. naval vessels, will be contacted on these frequencies and requested to identify themselves and state their intentions as soon as they are detected.”
The Vincennes civilian radio-talker never once asked the radar-target “to identify themselves and state their intentions,” contrary to Crowe’s repeated deceitful claim. And this can only mean, in the mind of the pilot, even if the radio-talker had broadcast on the right frequency, that the aircraft’s intentions were not unclear and the pilot was not approaching a warship.
Here is the full text of both U.S. NOTAMs, exactly as they appear on the page, in the FAA weekly publications prior to the ambush:
“Iran – Persian Gulf
In response to the recent attack on the USS Stark and the continuing terrorist threat in the region, U.S. naval vessels operating within the Persian Gulf, Strait of Hormuz, Gulf of Oman, and the Arabian Sea, north of 20 degrees north, are taking additional defensive precautions. Aircraft (fixed wing and helicopters) operating in these areas should maintain a listening watch on 121.5 mHz VHF or 243.0 mHz UHF. Unidentified aircraft, whose intentions are unclear or who are approaching U.S. naval vessels, will be contacted on these frequencies and requested to identify themselves and state their intentions as soon as they are detected. In order to avoid inadvertent confrontation, aircraft (fixed wing and helicopters) including military aircraft may be requested to remain well clear of U.S. vessels. Failure to respond to requests for identification and intentions, or to warnings, and operating in a threatening manner could place the aircraft (fixed wing and helicopters) at risk by U.S. defensive measures. Illumination of a U.S. naval vessel with a weapons fire control radar will be viewed with suspicion and could result in immediate U.S. defensive reaction. This notice is published solely to advise that measures in self-defense are being exercised by U.S. naval forces in this region. The measures will be implemented in a manner which does not unduly interfere with the freedom of navigation and overflight. (FAA FDC 052/87)
U.S. Naval Forces in the Persian Gulf, Strait of Hormuz, Gulf of Oman, and Arabian Sea (North of 20 Degrees North) are taking additional defensive precautions against terrorist threats. Aircraft at altitudes less than 2000-feet AGL which are not cleared for approach/departure to or from a regional airport are requested to avoid approaching closer than 5-nm to U.S. naval forces.
It is requested that aircraft approaching within 5-nm of U.S. naval forces establish and maintain radio contact with U.S. naval forces on 121.5-mHz VHF or 243.0-mHz UHF. Aircraft which approach within 5-nm at altitudes less than 2000-feet AGL whose intentions are unclear to U.S. naval forces may be held at risk by U.S. defensive measures. This is a joint USCINCPAC and USCINCCENT NOTAM affecting operations within their respective area of responsibility. (112119 KFDC)”
Source: Photocopy of “Foreign Notices, Iran–Persian Gulf,” International Notices to Airmen, June 30 1988 (U.S. Department of Transportation, Federal Aviation Administration), italics, text {in braces}, and highlighting added. ICAO, p.F-4. NOTAM FAA FDC 052/87 was originally issued Sept. 8 1987. DoD, ¶ (17), p.15. NOTAM 112119 KFDC was originally issued in 1984. ICAO, ¶ 2.2.1, p.10. Both NOTAMs appeared like this in every weekly edition of FAA NOTAMs, and both were in force on the day of the ambush.
Secret 13 n.mile killing zone
He had to act quickly to defend his ship and crew before the contact got much closer than 10 miles (in order to give himself fire depth and to stay outside of {redacted: Maverick} range).
William J. Crowe Jr. (Chairman, J.C.S.), DoD Report, Endorsement, p.4, ¶ 4 (Aug. 18 1988)
U.S. Military Officers, in their NOTAMs, induced the public to believe, that a U.S. warship would not regard an aircraft to be a threat unless it closed within 5 n.miles at less than 2,000 feet and, above 2,000 feet, if it did not “operate in a threatening manner”.
But, U.S. Military Officers maintained secret Rules of Engagement ordering its commanders to attack an aircraft approaching from Iran, before it closes within 13 n.miles, and regardless of its altitude (up to maybe 25,000 feet), and regardless of its flight profile (climbing at 1,500 feet per minute); i.e., even if the aircraft did not “operate in a threatening manner”. And, even if the aircraft broadcast a civilian transponder squawk code:
“IV. Opinions ...
E. Air Engagement ...
“1. ... Unless an aircraft can be visually identified as a non-threat, any aircraft approaching a U.S. Navy ship could be considered a threat. However, an aircraft at high altitude (above 25,000 ft) will likely not be evaluated as a threat.”
“4. Any aircraft, including commercial aircraft, could be used in a suicide mission role, therefore, Commanders cannot disregard an aircraft squawking Mode III, IFF, flying on a commercial air corridor, and on a CBDR to his ship.”
William M. Fogarty (Rear Admiral, U.S. Navy, Director of Policy and Plans, U.S. Central Command), DoD Report, pp.48-49, ¶ E.
The secret Rules of Engagement were a blatant violation of the U.S. NOTAMs, both of which senior U.S. Military Officers themselves drafted and issued.
Attacking, in the teeth of these NOTAMs, on the basis of those secret Rules of Engagement, is the war-crime of “perfidy”: