2023 Titan submersible incident
Lua error in package.lua at line 80: module 'strict' not found.
Lua error in package.lua at line 80: module 'strict' not found. Lua error in Module:Infobox at line 199: malformed pattern (missing ']').
On 18 June 2023, Titan, a submersible operated by OceanGate, went missing in international waters in the North Atlantic Ocean off the coast of Newfoundland, Canada.[2] The submersible with five persons on board was on a tourist expedition to view the wreck of the Titanic. Communication was lost with the submersible 1 hour and 45 minutes into its dive to the wreck site; authorities were notified when it did not resurface at its scheduled time later that day.[3][4]
On 22 June, after nearly 80 hours of searching, a remotely operated underwater vehicle (ROV) discovered a debris field containing parts of the Titan approximately 488 m (1,600 ft) from the bow of the Titanic. The pressure vessel is believed to have imploded only hours after Titan began descent, killing all on board instantly.[5][6][7]
Concerns about the safety of the vessel had previously been raised.[8] Search and rescue efforts were carried out by an international team led by the United States Coast Guard, United States Navy, and Canadian Coast Guard.[9] Aircraft from the Royal Canadian Air Force and United States Air National Guard, a Royal Canadian Navy ship, and several commercial and research ships and ROVs also assisted in the search.[10][11][12]
Contents
Background
OceanGate
OceanGate is a private company founded by Stockton Rush and Guillermo Söhnlein in 2009. Since 2010, it has transported paying customers in commercial submersibles off the coast of California, in the Gulf of Mexico, and in the Atlantic Ocean.[13]
Rush realized that visiting shipwreck sites was a way to get media attention, and in 2016 the company transported customers to a shipwreck for the first time, utilizing their submersible Cyclops 1 to visit the Andrea Doria wreck site. In 2019, Rush told Smithsonian magazine "There's only one wreck that everyone knows [...] If you ask people to name something underwater, it's going to be sharks, whales, Titanic."[13]
Titanic
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
RMS Titanic was a British ocean liner that sank in the North Atlantic on 15 April 1912, after colliding with an iceberg. In 1985, the wreckage was discovered on the ocean floor around 400 nautical miles (740 km) from the coast of Newfoundland.[14] The wreck lies at a depth of about 3,810 metres (12,500 feet; 2,080 fathoms).[15]
Titan submersible
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
Titan was a five-person submersible vessel operated by OceanGate, Inc. The 6.7-metre-long (22 ft), Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). vessel was constructed from carbon fibre and titanium.[16] The entire pressure vessel consisted of two titanium hemispheres, two matching titanium interface rings, and the 142 cm (56 in) internal diameter, 2.4-metre-long (7.9 ft) carbon fibre wound cylinder.[17] One of the titanium hemispherical end caps was fitted with a 380 mm-diameter (15 in) acrylic window.[18] In 2020, OceanGate CEO Stockton Rush stated that the hull had been downgraded to a depth rating of 3,000 m (9,800 ft) after demonstrating signs of cyclic fatigue. In 2020 and 2021, the Titan was rebuilt.[19][20]
Titan's steering controls consisted of a Logitech G F710 (a wireless game controller) with modified analogue sticks.[21][22][23] It would move at up to 3 knots (5.6 km/h; 3.5 mph) using four electric thrusters, arrayed two horizontal and two vertical.[24]
OceanGate claimed on its website as of 2023 that Titan was "designed and engineered by OceanGate Inc. in collaboration [with] experts from NASA, Boeing, and the University of Washington" (UW). A 1⁄3-scale model of the Cyclops 2 pressure vessel was built and tested at the Applied Physics Laboratory (APL) at UW; the model was able to sustain a pressure of 4,285 psi (29.54 MPa; 291.6 atm), corresponding to a depth of approximately 3,000 m (9,800 ft).[25] After the disappearance of the Titan in 2023, UW claimed the APL had no involvement in "design, engineering, or testing of the Titan submersible." A Boeing spokesperson also claimed Boeing "was not a partner on the Titan and did not design or build it." A NASA spokesperson said that NASA's Marshall Space Flight Center had a Space Act Agreement with OceanGate, but "did not conduct testing and manufacturing via its workforce or facilities".[26]
According to OceanGate, the vessel contained monitoring systems to continuously monitor the strength of the hull.[16] The vessel had life support for five crew members for 96 hours.[16] There was no on-board navigation system; the support ship, which monitored the position of Titan relative to its target, sent text messages to Titan providing distances and directions.[27]
According to OceanGate, the Titan had seven backup systems intended to return the vessel to surface in case of emergency, including ballasts that could be dropped, a balloon, and thrusters. Some of the backup systems were designed to work even if all aboard the submersible were unconscious; there were sandbags held by hooks that dissolved after a certain number of hours in the water to release the sandbags, ideally letting the vessel float to the surface.[28][29] An OceanGate investor explained that if the vessel did not automatically ascend after the elapsed time, those inside the vessel could help release the ballast either by tilting the ship back and forth to dislodge it or by utilizing a pneumatic pump to loosen the weights.[30]
Expeditions to the Titanic
The Titan made its first dive to the Titanic in July 2021.[31] It made additional dives in 2022 and 2023.[32]
Each dive typically had a pilot, three paying passengers, and a guide on board.[33] Once these people were inside the submersible, the hatch would be bolted shut and could only be reopened from the outside.[34] The descent from the surface to the Titanic typically took three hours,[35] with the full dive taking approximately eight hours.[33] Throughout the journey, the submersible was expected to emit a safety ping every 15 minutes to be monitored by the above-water crew.[14] The vessel and surface crew were also able to communicate via short text messages.[36]
Customers who travelled to the Titanic with OceanGate, referred to as "mission specialists" by the company,[37] spent US$250,000 to be involved in the eight-day expedition.[33][38]
OceanGate intended to conduct multiple expeditions to the Titanic in 2023, but because of poor weather in Newfoundland the company had only launched a single expedition in 2023.[33][35]
Safety and concerns
Safety
Because the Titan operated in international waters, it was not subject to any safety regulations. The vessel was not certified as seaworthy by any regulatory agency or third-party organization.[39] Reporter David Pogue, who completed the expedition in 2022 as part of a CBS News Sunday Morning feature,[40] stated that all passengers who enter the Titan sign a waiver confirming their knowledge that it is an "experimental" vessel "that has not been approved or certified by any regulatory body, and could result in physical injury, disability, emotional trauma or death."[41] Television producer Mike Reiss, who has also completed the expedition, noted that the waiver "mention[s] death three times on page one."[42]
A 2019 article published in Smithsonian magazine referred to OceanGate CEO Stockton Rush as a "daredevil inventor".[13] In the article, Rush is described as having said the U.S. Passenger Vessel Safety Act of 1993 "needlessly prioritized passenger safety over commercial innovation".[13][43] In a 2022 interview, Rush told CBS News, "At some point, safety just is pure waste. I mean, if you just want to be safe, don't get out of bed. Don't get in your car. Don't do anything."[44]
Prior concerns
In 2018, OceanGate's director of marine operations, David Lochridge, composed a report documenting safety concerns he had about the Titan. In court documents, Lochridge said that he had urged the company to have the Titan assessed and certified by an agency, but OceanGate had declined to do so, citing an unwillingness to pay.[8] He also said that the transparent viewport on its forward end was only certified to reach a depth of 1,300 m (4,300 ft), only a third of the depth required to reach the Titanic.[45] Lochridge was also concerned that OceanGate wouldn't perform nondestructive testing on the vessel's hull before undertaking manned dives, and alleged that he was "repeatedly told that no scan of the hull or Bond Line could be done to check for delaminations, porosity and voids of sufficient adhesion of the glue being used due to the thickness of the hull".[45][19][46]
OceanGate said that Lochridge, who was not an engineer, had refused to accept safety approvals from OceanGate's engineering team, and that the company's evaluation of the Titan hull was stronger than any kind of third-party evaluation Lochridge thought necessary.[8] OceanGate sued Lochridge for allegedly breaching his confidentiality contract and making fraudulent statements. Lochridge countersued, stating that he had been wrongfully terminated as a whistleblower for bringing up concerns about the Titan's ability to operate safely. The two parties settled a few months later.[47][45][48]
Later in 2018, the Marine Technology Society wrote a letter to Rush expressing "unanimous concern regarding the development of 'TITAN' and the planned Titanic Expedition", indicating that the "current experimental approach [...] could result in negative outcomes (from minor to catastrophic) that would have serious consequences for everyone in the industry".[49] A signatory of the letter later told The New York Times that Rush had called him after reading it to tell him that he believed industry standards were stifling innovation.[8]
Earlier incidents
Lua error in Module:Infobox at line 235: malformed pattern (missing ']'). The Titan had made three previous expeditions to the Titanic wreck site, the first of which was in July 2021.[50] In 2022, reporter David Pogue was onboard the surface ship when Titan became lost and could not locate the Titanic during a dive.[32][51] Pogue's December 2022 report for CBS News Sunday Morning, which questioned Titan's safety, went viral on social media after the submersible lost contact with its support ship in June 2023.[52] In the report, Pogue commented to Rush that "it seems like this submersible has some elements of MacGyvery jerry-rigged-ness". He noted that a $30 Logitech F710 Bluetooth game controller with modified control sticks is used to steer and pitch the submersible, and that construction pipes were used as ballast.[53]
In a 2022 dive to the Titanic, one of the thrusters on the Titan was accidentally installed backwards and the submersible started spinning in circles when trying to move forward near the sea floor. As documented by the BBC documentary Take Me to Titanic, the issue was bypassed by steering while holding the game controller sideways.[54][55] According to November 2022 court filings, OceanGate reported that in a 2022 dive the submersible suffered from battery issues and as a result had to be manually attached to a lifting platform, causing damage to external components.[56][57]
Incident
Timeline of events
Syntax error
<maplink zoom="5" latitude="<strong class="error"><span class="scribunto-error" id="mw-scribunto-error-16">Lua error in package.lua at line 80: module 'strict' not found.</span></strong>" longitude="<strong class="error"><span class="scribunto-error" id="mw-scribunto-error-17">Lua error in package.lua at line 80: module 'strict' not found.</span></strong>" text="[Full screen]">
[
"features": [
"geometry": {"type": "Point", "coordinates": [Lua error in package.lua at line 80: module 'strict' not found.,Lua error in package.lua at line 80: module 'strict' not found.] }, "properties": { "title": "June 16", "description": "Departure from St. John's, in Newfoundland", "marker-symbol": "-number", "marker-size": "medium", "marker-color": "#B80000" } } , { "type": "Feature", "geometry": {"type": "Point", "coordinates": [Lua error in package.lua at line 80: module 'strict' not found.,Lua error in package.lua at line 80: module 'strict' not found.] }, "properties": { "title": "June 18", "description": "The expedition arrives at the area where RMS Titanic sank", "marker-symbol": "-number", "marker-size": "medium", "marker-color": "#B80000" } }
|
MV Polar Prince departed St. John's, Newfoundland (1) on 16 June, and arrived at the dive site (2) on 17 June, where the Titan was deployed and began its descent the day after. |
On 16 June, the expedition to the Titanic departed from St. John's, Newfoundland, aboard the research and expedition ship MV Polar Prince. The ship arrived at the dive site on 17 June, and the dive operation began the following day on Sunday, 18 June at 9:30 a.m. Newfoundland Daylight Time (NDT; UTC−02:30) (12:00 UTC).[58][59] For the first hour and a half of the descent, the Titan communicated with the Polar Prince every 15 minutes, but communication stopped after a recorded communication at 11:15 a.m. (13:45 UTC).[58] The vessel was expected to resurface at 4:30 p.m. (19:00 UTC).[58] At 7:10 p.m. (21:40 UTC) the U.S. Coast Guard was notified of the missing vessel.[60] The submersible had up to 96 hours of breathable air supply for its five passengers when it set out,[50] which would have expired on the morning of 22 June 2023 if the submersible had been intact.[61]
A U.S. Navy acoustic detection system designed to locate military submarines detected a sound consistent with an implosion hours after Titan submerged.[7]
People aboard
- Shahzada Dawood was a Pakistani-British[62][63] businessman (of the Dawood Hercules Corporation), and trustee at the SETI Institute.[64] He was one of the wealthiest people in Pakistan.[62]
- Suleman Dawood, the 19-year-old son of Shahzada Dawood, was a student at the University of Strathclyde.[65][41]
- Hamish Harding was a British businessman, aviator, and space tourist.[66][38] He had previously descended into the Mariana Trench, broken the Guinness World Record for a circumnavigation of the Earth, and flown into space.
- Paul-Henri Nargeolet was a former French Navy commander, diver, submersible pilot, member of the French Institute for Research and Exploitation of the Sea (IFREMER),[35][38] and director of underwater research for E/M Group and RMS Titanic, Inc.,[67] which owns salvage rights to the wreckage site.[68] Nargeolet led more than 35 expeditions to the wreck,[69] supervised the recovery of thousands of artifacts, and was "widely considered the leading authority on the wreck site" according to The Guardian.[67]
- Stockton Rush was an American submersible pilot and businessman. He was the chief executive and founding member of OceanGate.[70]
Search and rescue operations
The United States Coast Guard, United States Navy, and Canadian Coast Guard led the search and rescue efforts.[9] Aircraft from the Royal Canadian Air Force and United States Air National Guard, a Royal Canadian Navy ship, and several commercial and research ships and remotely operated underwater vehicle (ROVs) also assisted in the search.[10][11][12] The search involved both a surface search and an underwater sonar search.[41] As of 22 June, the agencies are continuing efforts to map debris and understand what happened.[71]
Timeline of operations
All dates are in Newfoundland Daylight Time (NDT; UTC−02:30) unless otherwise noted.
19 June
Crews from the Northeast Sector of the United States Coast Guard, based in Boston, launched search missions 900 nautical miles (1,700 km) from the shore of Cape Cod, Massachusetts.[72][73] Joint Rescue Coordination Centre Halifax reported that a Royal Canadian Air Force Lockheed CP-140 Aurora aircraft and CCGS Kopit Hopson 1752 were participating in the search in response to a request for assistance by the Maritime Rescue Coordination Center in Boston made on 18 June at 9:43 p.m. (00:13 UTC).[10][74] The search on 19 June involved three C-130 Hercules aircraft, two from the United States and one from Canada;[75] a P-8 Poseidon aircraft from the United States, and sonobuoys.[76] Search and rescue was hampered by low visibility weather conditions, which cleared the next day.[77]
The U.S. Coast Guard indicated that the search and rescue mission was difficult because of the remote location, weather, darkness, sea conditions, and water temperature.[78] Rear Admiral John Mauger stated that they were "deploying all available assets".[38] While many submersibles are equipped with an acoustic beacon which emits sounds that can be detected underwater by rescuers, it is unknown if the Titan had such a device.[78]
Neither the U.S. nor Canada has underwater vessels capable of easily assisting in the search and rescue missions.[78] The U.S. Navy has one deep-submergence rescue vehicle, although the vessel cannot reach the depths at the search site. The Navy also has ROVs, but these vessels would take days to reach the disaster site.[78]
20 June
The pipe-laying ship Deep Energy, operated by TechnipFMC, arrived on site on 20 June 2023, with two ROVs and other equipment suited to the seabed depths in the area.[12] As of 10:45 a.m. (13:15 UTC), the U.S. Coast Guard had searched 10,000 square miles (26,000 km2).[79] An Air National Guard C-130 also joined in the search and rescue mission, with plans for two more to join by the end of the day.[11]
According to an internal American government memo, a Canadian CP-140 Aurora's sonar picked up underwater noises while searching for the submersible.[80][81] The U.S. Coast Guard officially acknowledged the sounds early the following morning, but reported that early investigations had not yielded results.[80] Rear Admiral John Mauger of the U.S. Coast Guard said the source of the noise was unknown and may have come from the many metal objects at the site of the wreck.[82] A Canadian CP-140 Aurora plane had previously spotted a "white rectangular object" floating on the surface. A ship sent to find and identify the object was diverted to help find the source of the noise.[83] The noises were later described by the U.S. Coast Guard as being apparently unrelated to the missing vessel.[84]
21 June
CCGS John Cabot arrived in the morning of 21 June, bringing additional sonar capabilities to the search effort. Commercial vessels Skandi Vinland and Atlantic Merlin also arrived that day, as did a Coast Guard C-130 crew.[85] As of approximately 3:00 p.m. (17:30 UTC), five air and water vehicles were actively searching for the Titan, and another five were expected to arrive in the next 24–48 hours.[86] Search and rescue assets included two ROVs, one CP-140 Aurora aircraft, and the C-130 aircraft.[86]
The U.S. Navy's Flyaway Deep Ocean Salvage System (FADOSS), a ship lift system designed to lift large and heavy objects from the deep sea, arrived in St. John's, though no ships were available to carry the system to the wreck site.[87][88] Officials estimated it would take around 24 hours to weld the FADOSS system to the deck of a carrier ship before it can set sail to the search and rescue operation.[88]
Despite rising concerns about depletion of air supplies on the Titan if it were intact, a U.S. Coast Guard spokesperson stated at a press conference that "This is a search and rescue mission 100%", rather than a wreckage recovery mission.[89]
22 June
An Odysseus 6k ROV from Canadian-flagged offshore tug MV Horizon Arctic reached the sea floor and began its search for the missing submersible.[90][91][92] The French RV L'Atalante also deployed its ROV Victor 6000 , which can reach depths of up to 6,000 m (20,000 ft) and transmit images to the surface.[93]
At 1:18 p.m. NDT (15:48 UTC) the U.S. Coast Guard's Northeast Sector announced that a debris field had been found near the wreck of the Titanic.[94][95][96] The debris, located by the Horizon Arctic's Odysseus 6k remotely operated vehicle five hours into its search, was later confirmed to be part of the submersible.[97] At an afternoon press conference, the U.S. Coast Guard confirmed the loss of the submersible due to the pressure chamber imploding, and stated that pieces of the Titan had been found on the sea floor approximately Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). from the bow of the Titanic.[1] The Coast Guard stated that they suspect the implosion of the pressure vessel to have likely occurred while the craft was traversing the water column, and that the implosion likely occurred prior to any rescue operations commencing, because the highly sensitive sonar buoys did not pick up any acoustic signal indicative of an implosion throughout their deployment.[98] Rear Admiral Mauger said, however, he did not have an answer on whether the bodies of the five men on board were likely to be recovered.[71] OceanGate issued a statement regarding the deaths of the people aboard.[97]
Debris
The debris that has been located and confirmed as belonging to the Titan submersible consists of the nose cone (not part of the pressure vessel) as well as the forward and aft end bell — both part of the pressure vessel that protects the crew from the ocean environment. According to the U.S. Coast Guard, the debris field is concentrated in two areas, with the aft end bell lying separate from the front end bell and the nose cone.[99] The debris is around 500 meters from the bow of the Titanic.[100]
Assets involved
Country | Asset | Status | Arrival date | Ref. |
---|---|---|---|---|
Canada | MV Polar Prince (research vessel that brought the Titan to the Titanic wreck location) | Arrived | 17 June | [75] |
Canada | CP-140 Aurora (Royal Canadian Air Force aircraft) | Arrived | 19 June | [74] |
Canada | C-130 Hercules (Royal Canadian Air Force aircraft) | Arrived | 19 June | [75] |
Canada | Kopit Hopson 1752 (Canadian Coast Guard ship) | Arrived | 19 June | [74] |
United States | P-8 Poseidon (U.S. Navy aircraft with undersea search capabilities) | Arrived | 19 June | [75][101] |
United States | C-130 Hercules (United States Coast Guard aircraft) | Arrived | 19 June | [72][75] |
United Kingdom | MV Deep Energy (pipe-laying ship with two ROVs and other deepsea equipment, operated by TechnipFMC) | Arrived | 20 June | [12] |
United States | C-130 Hercules (three Air National Guard aircraft) | Arrived | 20 June | [11] |
Canada | Atlantic Merlin (commercial vessel) | Arrived | 21 June | [85] |
Canada | John Cabot (Canadian Coast Guard ship with sonar capabilities) | Arrived | 21 June | [85] |
Canada | Skandi Vinland (commercial vessel with ROV) | Arrived | 21 June | [85] |
United States | C-130 Hercules (United States Coast Guard aircraft) | Arrived | 21 June | [85] |
United States | Flyaway Deep Ocean Salvage System (FADOSS) (United States Navy ship lift system) | Arrived in St. John's | 21 June | [87][88] |
Canada | Horizon Arctic (ship with Odysseus 6k ROV capable of reaching Titanic depths) | Arrived | 22 June | [90][92] |
France | L'Atalante (research vessel with Victor 6000 , a ROV that can reach depths of up to 6,000 m (20,000 ft) and transmit images to the surface, operated by Ifremer) | Arrived | 22 June | [93][102] |
Canada | Ann Harvey (Canadian Coast Guard ship) | En route | [85] | |
Canada | HMCS Glace Bay (Royal Canadian Navy patrol ship carrying medical personnel and a mobile decompression chamber) | En route | [85] | |
Canada | Terry Fox (Canadian Coast Guard ship) | En route | [85] | |
United Kingdom | Magellan ROV | En route | [85] | |
United States | C-130 Hercules (Air National Guard aircraft) | En route | [85] |
Reactions
Discussing the scale of the search and rescue response, Sean Leet, co-founder and chair of Horizon, the company that owns the Polar Prince, said, "I've been in the marine industry since a very young age and seen a lot of different situations, and I've never seen equipment of that nature move that quickly [...] The response from the U.S. Coast Guard, the U.S. Military, folks at the airport, the people here, various companies who were involved in the mobilization of that equipment [...] it was done flawlessly."[103]
The scale of the search and rescue efforts and media coverage compared to the 2023 Messenia migrant boat disaster on 14 June has sparked criticism.[104] Ishaan Tharoor of the Washington Post noted that Pakistani internet users compared and contrasted the Pakistani victims in both incidents.[105] The search likely cost millions of dollars of public funds.[106] The Messenia disaster involved a fishing boat carrying an estimated 400 to 750 migrants, with nearly 100 people confirmed dead,[107] another 100 rescued,[108] and several hundred more still missing.[109] Search and rescue efforts for the Messenia disaster were conducted by the Hellenic Coast Guard and military.[110]
According to David Scott-Beddard, CEO of the Titanic exhibition company White Star Memories Ltd, the possibility of conducting future research at the Titanic wreck has decreased due to the disappearance of the Titan submersible.[111]
Parks Stephenson, director of the USS Kidd Veterans Museum and Titanic researcher, commented early on about the disappearance of the Titan: "No matter what you may read in the coming hours, all that is truly known at this time is that communications with the submersible have been lost and that is unusual enough to warrant the most serious consideration." He added: "I am most concerned about the souls aboard."[112] Stephenson is experienced in deep-sea explorations such as the Titan's, having previously dived to view the Titanic on five occasions.[112][113] Stephenson later added that the divers "wouldn't be out there if it wasn't for the public demand for information regarding this wreck".[114]
See also
- List of submarine incidents since 2000
- Rescue of Roger Mallinson and Roger Chapman, the deepest such rescue in history
References
<templatestyles src="Reflist/styles.css" />
Cite error: Invalid <references>
tag; parameter "group" is allowed only.
<references />
, or <references group="..." />
External links
Media related to Lua error in package.lua at line 80: module 'strict' not found. at Wikimedia Commons
- ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 8.0 8.1 8.2 8.3 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 10.0 10.1 10.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 11.0 11.1 11.2 11.3 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 12.0 12.1 12.2 12.3 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 13.0 13.1 13.2 13.3 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 14.0 14.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 16.0 16.1 16.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 32.0 32.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 33.0 33.1 33.2 33.3 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 35.0 35.1 35.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 38.0 38.1 38.2 38.3 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 41.0 41.1 41.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 45.0 45.1 45.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 50.0 50.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 58.0 58.1 58.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 62.0 62.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 67.0 67.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 71.0 71.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 72.0 72.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 74.0 74.1 74.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 75.0 75.1 75.2 75.3 75.4 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 78.0 78.1 78.2 78.3 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 80.0 80.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 85.0 85.1 85.2 85.3 85.4 85.5 85.6 85.7 85.8 85.9 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 86.0 86.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 87.0 87.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 88.0 88.1 88.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 90.0 90.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 92.0 92.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 93.0 93.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 97.0 97.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 112.0 112.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- Pages with reference errors
- Articles with short description
- Wikipedia pages with incorrect protection templates
- Use Canadian English from June 2023
- Articles with invalid date parameter in template
- All Wikipedia articles written in Canadian English
- Use dmy dates from June 2023
- Pages using infobox event with unknown parameters
- Pages with broken file links
- Articles containing OSM location maps
- Interlanguage link template link number
- 2023 in Newfoundland and Labrador
- Disasters in the Atlantic Ocean
- June 2023 events in Canada
- Maritime incidents in 2023
- Maritime incidents in Canada
- Ships lost with all hands
- RMS Titanic
- United States submarine accidents
- Pages with broken graphs