Cargo planes bomb plot

From Infogalactic: the planetary knowledge core
(Redirected from 2010 cargo plane bomb plot)
Jump to: navigation, search
Cargo planes bomb plot
Location United States of America (target); East Midlands Airport and Dubai International Airport (discovered)
Date October 29, 2010 (discovered)
Target 2 planes
Attack type
 Bombing (failed)
Weapons two packages, each containing a printer cartridge packed with a bomb made from the plastic explosive PETN
Deaths 0
Injured 0
Perpetrator Al-Qaeda in the Arabian Peninsula

On October 29, 2010, two packages, each containing a bomb consisting of 300 to 400 grams (11–14 oz) of plastic explosives and a detonating mechanism, were found on separate cargo planes. The bombs were discovered as a result of intelligence received from Saudi Arabia's security chief. They were bound from Yemen to the United States, and were discovered at en route stop-overs, one at East Midlands Airport in the UK and one in Dubai in the United Arab Emirates.

One week later, al-Qaeda in the Arabian Peninsula (AQAP) took responsibility for the plot, and for the crash of UPS Airlines Flight 6.[1] U.S. and British authorities believed Anwar al-Awlaki of AQAP was behind the bombing attempts, and that the bombs were most likely constructed by AQAP's main explosives expert, Ibrahim Hassan al-Asiri.[2][3] The bombs were probably designed to detonate mid-air, with the intention of destroying both planes over Chicago or another city in the U.S.[4][5] Each bomb had already been transported on passenger and cargo planes at the time of discovery.

Locating the bombs

On October 28, Saudi Arabia's Deputy Interior Minister in charge of Counter-terrorism, Prince Mohammed bin Nayef, called John Brennan, the U.S. Deputy National Security Advisor for Homeland Security and Counterterrorism and former Central Intelligence Agency station chief in Riyadh to warn him of the plot.[6] The Saudis provided the U.S. and Germany with the tracking numbers and destinations of the packages, and told them to look for toner cartridges.[7][8] The packages had been dropped off by a woman at FedEx and UPS offices in Sana'a, Yemen, on October 27, and were scheduled to arrive in Chicago on November 1.[8][9]

Saudi Arabia had reportedly learned of the plot through Jabir Jubran Al Fayfi, a former Guantánamo Bay detention camp inmate who had been handed over to Saudi Arabia for rehabilitation in 2006. Al-Faifi had escaped in 2008 and re-joined AQAP, but turned himself in to Saudi authorities on October 16, 2010, and provided them with information about the plot.[10][11][12] Yemen officials suspected al-Faifi had not actually rejoined al-Qaeda, but had become a double agent.[12] They said his tip appeared to be based on more recent information than al-Faifi could access, and that the information must have come from a Saudi double agent in AQAP.[13]

England

East Midlands Airport in Leicestershire

The first package left Sana'a, Yemen, on a passenger plane, flying to Dubai, United Arab Emirates.[14] It then was next placed on a UPS cargo plane to Cologne/Bonn Airport in Germany, where UPS Airlines has a hub.[14][15] There, it was placed on UPS Flight 232, a Boeing 767 cargo plane bound for East Midlands Airport in Leicestershire.[16][17] From there, it was to fly to O'Hare International Airport in Chicago via Philadelphia, Pennsylvania.[3][16][18]

The UPS plane landed at East Midlands Airport at 2:13 AM local time on October 29.[19] British military and police explosives experts had been alerted to the existence of the bomb, and conducted an initial search of the plane's cargo in the airport's UPS parcels distribution depot.[20] Officers from the Scotland Yard Counter Terrorism Command joined them.[21]

U.S. authorities provided the precise tracking number of the package, and the printer was scanned with explosives detection equipment, x-rayed, subjected to chemical swabs, and sniffed by sniffer dogs. No explosives were detected.[22][23] Removing the suspect package for further examination, the authorities allowed the UPS plane to proceed to Philadelphia at 4:20 AM local time.[19][24] At 10 am the British gave the all-clear, and removed safety cordons from the airport.[9][25][26][27]

Later forensic examination indicated that the bomb was inadvertently disarmed by Scotland Yard explosive officers, who took the printer cartridge out of the printer during their examination that morning, around three hours before the bomb was due to explode at 10:30 AM (5:30 AM Eastern time) .[19][20][28] The officers were unaware when they took the device apart that it was a bomb.[21]

British officials continued to believe that there were not any explosives in the package,[19] but U.S. authorities insisted that the package be inspected again. British authorities then consulted with officials in Dubai, who had discovered a similar bomb in a computer printer cartridge, and MI6 spoke with the Saudi tipster. Scotland Yard explosives officers flew the printer and the cartridge in a police helicopter to the Defence Science and Technology Laboratory at Fort Halstead near London, and discovered the bomb at around 2 PM.[19][21][24][27]

Dubai

Cross-section of an Airbus A300 showing how cargo is positioned inside

Qatar Airways said that the package with the second bomb had been carried on two of its commercial passenger jets. The first was a 144-seat Airbus A320 that flew from Sana'a, Yemen, to Doha International Airport in Doha, Qatar, on October 28.[9] The second passenger plane was an Airbus A321 or Boeing 777 flying from Doha to Dubai. The seating capacity of the second plane was anywhere from 144 to 335, depending on which aircraft was used.[15][23][29][30][31]

The second package was discovered on a FedEx Express plane at the FedEx depot at the Dubai airport at around 9 am GMT on October 29.[32] The plane was scheduled to fly to Newark Liberty International Airport in Newark, New Jersey, and then on to O'Hare International Airport in Chicago.[33][34]

Bombs

Addresses

The packages were addressed to former locations of two synagogues in Chicago. Investigators believe the terrorists used outdated information that they found online.[35] One package was addressed to a church in Lakeview that had been once been the meeting place of Congregation Or Chadash, and the other had been sent to a closed synagogue in East Rogers Park.[2][35][36] Simon Calder observed in The Independent:

Yemen is not a natural provider of office supplies to organisations such as synagogues in the Chicago area. Therefore, you might fondly imagine that the staff in the parcels offices in the capital, Sana'a, might have checked the despatches more closely before allowing them anywhere near an aircraft, cargo or passengers. But they didn't.[37]

The packages were addressed to specific people at the addresses—the names used were those of historical figures from the Spanish Inquisition and the Crusades.[2][38] One package was addressed to Diego Deza, a Grand Inquisitor during the Spanish Inquisition. The other was addressed to Reynald Krak (Raynald of Châtillon), a French crusader who was beheaded in 1187 by Sultan Saladin of the 12th-century Muslim Ayyubid dynasty.[38]

Brian Fishman of the New America Foundation said the choice of names was an inside joke.[38] "The jihadis ... narrative is that non-Muslims are always on the attack, always trying to take Muslim lands. The jihadis like the narrative, because it justifies violence, since they claim that they’re only defending Islam," he said.[38] He felt the destination of Chicago may have had meaning as well, as the latest edition of Inspire (AQAP's online magazine) may have had a photo of Chicago on its cover.[38][39] Fishman points out that this parallels Osama bin Laden posing in front of a map of East Africa shortly before the 1998 United States embassy bombings.[38] U.S. and U.K. officials believed the planes, and not the addresses on the ground, were the targets.[40]

Contents

File:Toner Cartridge Bomb.jpg
A toner cartridge from one of the recovered bombs showing white powder and wiring

Each package contained a Hewlett-Packard HP LaserJet P2055 desktop laser printer. Inside each printer's toner cartridge was a sophisticated bomb.[41][42] The cartridges were filled with pentaerythritol tetranitrate (PETN), an odorless military-grade white powder plastic explosive.[33][41][42][43] The bomb found in England contained 400 grams (14 oz) of PETN, five times the amount needed to destroy a house.[41] The one found in Dubai contained 300 grams (11 oz) of PETN.[41] Hans Michels, professor of safety engineering at University College London, said that just 6 grams (0.2 oz) of PETN—around 2% of what was used—would be enough to blow a hole in a metal plate twice the thickness of an aircraft's skin.[44] The PETN was of "an extremely high concentration", according to British criminal investigators. German investigators felt the device's construction would require "logistics that only state facilities should have access to".[45]

The package intercepted in Dubai was shipped in a cardboard box that also contained souvenirs, clothes, compact discs, and several books written in English.[41][42][46][47]

The bomb found in England was sent to the Defence Science and Technology Laboratory at Fort Halstead in Kent,[27] and American technicians in the United Arab Emirates examined the other bomb.[48]

Detonation

Detonators

Each bomb was triggered by a cell phone alarm, which activated a phone battery to send power through a thin wire filament inside a syringe containing 5 grams (0.18 oz) of lead azide, a powerful chemical initiator.[30][33][45][49][50][51] Once hot, the lead azide would ignite, causing the PETN to detonate.[24][52][53][54][55] The device's wiring was set up so that all the printer components would appear to be correct if the device was x-rayed.[49] Features not relevant to the alarm timer function, such as the screen faces, had been removed to extend the battery life.[53] The device was reported to carry markings resembling a Bird D736 cell phone.[54][56]

There had initially been speculation that the bombs might be detonated by receipt of a telephone call or text message, but the SIM cards necessary to receive calls had been removed, rendering the phones unable to receive any communication, but increasing battery life.[29][41][53][57] U.S. officials said that the bombs were set to go off shortly before the planes landed.[9][53]

Mid-air capability

British Prime Minister David Cameron and officials in the U.S. believe that the bombs were designed to detonate as the planes were in flight, destroying the planes in mid-air.[49] Britain's Home Secretary, Theresa May, said British investigators concluded the U.K. device was a functional bomb powerful enough to bring down the aircraft, causing a "supersonic blast".[6][45] Brennan agreed with this assessment.[29]

Cargo vs. passenger planes

Brennan said it was not clear whether those attempting the bombing knew whether the packages would be carried on cargo or passenger planes.[49] Since Yemen does not have any regularly scheduled cargo flights, the perpetrators likely knew the bombs would end up on passenger planes.[14] Most of the air freight arriving in the U.S. is on passenger flights.[58] James Halstead, a consultant with Aviation Economics, said "In a worst case, it would stop world trade. UPS and FedEx would probably go bust. We'd have a full-disaster scenario."[8]

Detection

Like many explosives, PETN has a low vapor pressure. This makes it difficult to detect, because the chemical releases little vapor into the surrounding air.[42] Frank Cilluffo, the director of the Homeland Security Policy Institute at George Washington University, said: "It is evident that had we not had the intelligence, our security countermeasures would not have identified these improvised explosive devices."[59] Qatar Airways said that "the explosives discovered were of a sophisticated nature whereby they could not be detected by x-ray screening or trained sniffer dogs", and were only discovered after intelligence services received a tip.[30]

Both packages were x-rayed in Sana'a, and the one in Dubai was x-rayed there, without the bombs being spotted.[8] A spokesman for the German Federal Criminal Police Office, where the Dubai x-rays were reviewed, stated they would not have detected the bomb.[8] When X-rayed, PETN would resemble the cartridge's powdered ink,[9] and the timers resembled the normal printer cartridge electronics.[14]

Preparation

In mid-September 2010, U.S. intelligence intercepted three packages linked to AQAP that had been shipped from Yemen to Chicago.[21][41][60] They searched the packages, but did not find any explosives.[41] One of the packages included the 1860 novel The Mill on the Floss, by English novelist George Eliot, a woman who wrote under an assumed identity.[60] The packages, addressed to "random addresses" in Chicago, were not confiscated.[41]

Authorities surmised, after the October incident, that the September parcels may have been a test run.[41] The September packages may have been used as a way to test the accuracy of tracking information available online form carriers such as UPS,[29] information that could potentially be used to time the detonation of the October bombs.[41] Richard Clarke, former chief counter-terrorism adviser on the U.S. National Security Council, said: "The dry run is always important to Al-Qaeda. In this case they wanted to follow the packages using the tracking system."[61]

Responsibility

Al-Qaeda in the Arabian Peninsula

On November 5, 2010, al-Qaeda in the Arabian Peninsula (AQAP) took responsibility for the plot,[1] posting on a number of radical Islamist websites monitored by the SITE Intelligence Group and the NEFA Foundation. "We will continue to strike blows against American interests and the interest of America's allies," said the perpetrators. "Since both operations were successful, we intend to spread the idea to our mujahedeen brothers in the world and enlarge the circle of its application to include civilian aircraft in the West as well as cargo aircraft."[1][62][63][64] U.S. Secretary of Homeland Security, Janet Napolitano, British Home Secretary Theresa May, and Dubai police had noted that these types of explosives are "hallmarks" of AQAP, and had suspected they were behind the attack.[15]

AQAP also claimed responsibility for the crash of UPS Airlines Flight 6, a Boeing 747-400 cargo plane that crashed in Dubai on September 3. U.S. and United Arab Emirates investigators had said they had not found any evidence of an explosion or terrorist involvement in that incident, and were skeptical about the claim. They suggested it was probably an attempt by AQAP to bolster its image.[46][65] On September 10, the FBI and the U.S. Department of Homeland Security confirmed that the AQAP was not involved in the September 3 crash.[66]

On November 21, AQAP provided a detailed account of the plot, including photos of the printer bombs, in its English-language magazine Inspire. The article said that the mission was a success, because it caused a huge amount of disruption to the world's air traffic and security systems at the very low cost of $4,200.[67][68]

Anwar al-Awlaki

Anwar al-Awlaki, primary suspect of U.S. and U.K. officials

The Guardian reported that unnamed U.S. counter-terrorism officials suspected that Anwar al-Awlaki of AQAP was behind the plot. "Anybody associated with al-Qaeda in the Arabian Peninsula is a subject of concern," Brennan said.[69] The New York Times reported that "some analysts believe the [attempted Chicago bombing] may also be linked to Mr. Awlaki".[70] The Daily Telegraph reported that "U.S. and British security officials believe" al-Awlaki was behind the attack.[71] U.S. Ambassador to Yemen Gerald Feierstein said "al-Awlaki was behind the two ... bombs."[72]

Al-Awlaki had also been linked to the 2009 Fort Hood shooting, the failed 2009 Christmas Day bombing, the failed 2010 Times Square car bombing attempt, and other terrorist incidents,[69] and had been placed by U.S. President Barack Obama on a targeted killing list.[73] The American Civil Liberties Union and the Center for Constitutional Rights sued in an attempt to prevent his death.[74] Al-Awlaki was killed in a targeted killing in September 2011.[75]

Ibrahim Hassan al-Asiri

US officials suggested that Ibrahim Hassan al-Asiri, the main explosives expert for Al-Qaeda in the Arabian Peninsula, likely built the bombs. He has a history of creating explosive devices using PETN.[3][29][33][71] Brennan said that the evidence pointed to the bombs having been built by the same person who made the device worn by Umar Farouk Abdulmutallab, who attempted to detonate a bomb on a plane on Christmas Day 2009.[30] One of the detonators was almost identical to the one used in that attack.[76]

Al-Asiri had previously recruited his younger brother Abdullah as a suicide bomber, hiding a PETN bomb in his rectum in an attempt on the life of security chief Mohammed bin Nayef. Abdullah died in the attempt, but Nayef survived with minor injuries.[30][77]

Released suspect

On October 30, 2010, a 22-year-old female Yemeni engineering student was arrested in Sana'a, Yemen, on suspicion of having shipped the packages. Her mother was also arrested. Both were released the following day when it was determined that the woman's identification had been stolen.[49]

Responses

Political

Obama and his administration reacted quickly to the incident, making public statements that it was a "credible threat". A New York Times opinion piece suggested that the quick response would be well received politically for the 2010 U.S. elections.[73]

Security

Security alerts were triggered in the U.S., the U.K., and the Middle East.[33] An Emirates flight containing a package in transit from Yemen to the U.S. was intercepted by Canadian CF-18 and U.S. F-15 fighter jets and escorted to New York as a precaution.[9][78] Two FedEx planes containing packages originating from Yemen were also searched.[79]

The U.K., the U.S., Germany, France, and Belgium stopped accepting freight package cargo shipments from Yemen, and the Netherlands and Canada suspended all cargo flights from Yemen.[80][81] Germany suspended passenger flights from Yemen until November 15.[3][82][83] Britain and the U.S. stopped accepting air cargo from Somalia, and prohibited passengers from carrying certain printer cartridges on flights.[57] The Swedish government recommended that its citizens not travel to Yemen until further notice.[84][85]

FedEx, UPS, and Mideast-based shipper Aramex suspended their shipping operations in Yemen.[9][33] Emirates Airline and Air Arabia stopped carrying cargo from Yemen, and Abu Dhabi-based Etihad Airways stopped carrying cargo from Yemen and Somalia.[86]

The U.S. increased air passenger screenings and initiated a more detailed passenger search procedure.[87] American Civil Liberties Union counsel Chris Calabrese said that "Americans now must choose between a virtual strip search and a grope."[87]

Al-Awlaki

On November 2, four days after the bombs were discovered, al-Awlaki was charged in absentia in Sana'a with plotting to kill foreigners and being an al-Qaeda member in an unrelated matter.[88] On November 6, Yemeni Judge Mohsen Alwan ordered that al-Awlaki be caught dead or alive.[89]

See also

References

  1. ↑ 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 2.2 Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ 3.0 3.1 3.2 3.3 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ 8.0 8.1 8.2 8.3 8.4 Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ 9.0 9.1 9.2 9.3 9.4 9.5 9.6 Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ 12.0 12.1 Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ 14.0 14.1 14.2 14.3 Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ 15.0 15.1 15.2 Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  19. ↑ 19.0 19.1 19.2 19.3 19.4 Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ 20.0 20.1 Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ 21.0 21.1 21.2 21.3 Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  24. ↑ 24.0 24.1 24.2 Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ 27.0 27.1 27.2 Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ 29.0 29.1 29.2 29.3 29.4 Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ 30.0 30.1 30.2 30.3 30.4 Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ 33.0 33.1 33.2 33.3 33.4 33.5 Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ 35.0 35.1 Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ 38.0 38.1 38.2 38.3 38.4 38.5 Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  41. ↑ 41.00 41.01 41.02 41.03 41.04 41.05 41.06 41.07 41.08 41.09 41.10 Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ 42.0 42.1 42.2 42.3 Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ 45.0 45.1 45.2 Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ 46.0 46.1 Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ 49.0 49.1 49.2 49.3 49.4 Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ 53.0 53.1 53.2 53.3 Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ 54.0 54.1 Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  55. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.}.
  57. ↑ 57.0 57.1 Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ 60.0 60.1 Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  67. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  68. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  69. ↑ 69.0 69.1 Lua error in package.lua at line 80: module 'strict' not found.
  70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  71. ↑ 71.0 71.1 Lua error in package.lua at line 80: module 'strict' not found.
  72. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  73. ↑ 73.0 73.1 Lua error in package.lua at line 80: module 'strict' not found.
  74. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  75. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  76. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  77. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  78. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  79. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  80. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  81. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  82. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  83. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  84. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  85. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  86. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  87. ↑ 87.0 87.1 Lua error in package.lua at line 80: module 'strict' not found.
  88. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  89. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Cargo_planes_bomb_plot&oldid=706854066"