Sinking of MV Sewol

From Infogalactic: the planetary knowledge core
(Redirected from Sinking of the MV Sewol)
Jump to: navigation, search
Sinking of MV Sewol
Korean Ferry Sewol Capsized, 2014.jpg
MV Sewol capsizing, as taken by the South Korean coast guard on 16 April 2014
Native name Hangul세월호 침몰 사고; hanja世越號沈沒事故
Time Around 9 a.m. to around 11:30 a.m. (KST)
Date 16 April 2014 (2014-04-16)
Location 1.5 kilometres (0.93 mi) off Donggeochado,[1] Jindo County, South Jeolla Province, South Korea
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Deaths 295 on-board[2]
2 rescue divers[3]
Missing 9[2]
Property damage Cargo: ₩200 billion[4]
Inquest 3 separate investigations[5]
Suspect(s) Captain and 14 crew members[6]
Charges Homicide (4 including the captain),[7] Fleeing and abandoning ship (2),[8] Negligence (9)[8]
Verdict Guilty
Convictions Life sentence (captain),[9] 10 years (chief engineer), 1.5–12 years (13 other crew)[10]
On board 476[11][12][13] (>300 Danwon High School students)[14]
Survivors 172[15] (171 excluding the subsequent suicide of the vice principal of Danwon High School)

The sinking of MV Sewol (Hangul세월호 침몰 사고; hanja世越號沉沒事故)[16] occurred on the morning of April 16, 2014, en route from Incheon to Jeju in South Korea. The ferry capsized while carrying 476 people, mostly secondary school students from Danwon High School (Ansan City).[17] The 6,825-ton vessel sent a distress signal from about 2.7 kilometres (1.7 mi) north off Byeongpungdo at 08:58 Korea Standard Time (23:58 UTC, 15 April 2014).[18] In all, 304 passengers and crew members died in the disaster.[19][20] Of the approximately 172 survivors, more than half were rescued by fishing boats and other commercial vessels that arrived at the scene approximately 40 minutes after the South Korean coast guard.[21]

The sinking of Sewol resulted in widespread social and political reaction within South Korea. Many criticized the actions of the captain and most of the crew of the ferry.[22] More criticized the ferry operator and the regulators who oversaw its operations.[23] Additional criticism was directed at the South Korean government and media for its disaster response and attempts to downplay government culpability.[24] On May 15, 2014, the captain and three crew members were charged with murder, while the other 11 members of the crew were indicted for abandoning the ship.[25] An arrest warrant was also issued for Yoo Byung-eun, the owner of Chonghaejin Marine, which operated Sewol, but he could not be found despite a nationwide manhunt. On July 22, 2014, police revealed that they had established that a dead man found in a field 415 kilometres south of Seoul was Yoo. Foul play was ruled out, but police say they have yet to establish the cause of Yoo's death.[19]

On the first anniversary of the disaster, as part of commemorations for the victims of the sinking of the Sewol, 4,475 people held electronic candles to form the shape of the ferry in an attempt to set a Guinness World Record for largest torchlight image.[26]

Background

At the time Chonghaejin Marine purchased the ship for 11.6 billion ($9.8 million) in 2012, the ship that would come to be known as the Motor Vessel (MV) Sewol was 18 years old and dilapidated.[27] The ship was built in 1994 by Hayashikane Dockyard, who had operated her in Japan for 18 years without a single accident.[28] She was named Ferry Naminoue during the time of operation and purchase.[29] The Korea Herald later quoted a shipping expert expressing the opinion that Sewol should have been scrapped, given that the average lifespan of a ship was 15 years at that time.[30] Soon after the purchase, Chonghaejin made extensive modifications[31] by adding a total of 240 passenger cabins to the third, fourth, and fifth decks.[32][33] This led to an increase in the passenger capacity from 804 to 921 and an increase in weight by 239 tons, resulting in a left-right imbalance.[34][35] The ship's Hanja name had a religious connotation and meant to go "beyond the world".[29][36][note 1] Investigators later noted that the modifications had been made illegally.[37]

File:Ferry Sewol 1.jpg
Sewol at a port in Incheon on March 2014, after modifications had been made

After the modification, Sewol had a legal capacity of 956 people including the crew, 180 vehicles, and 154 regular cargo containers.[38][39] She weighed a total of 6,825 tons, and had 46 rubber lifeboats, each with a capacity of 45.[40] She could travel at a maximum of 22 knots (41 km/h; 25 mph).[41] From October 2012 to February 2013, she was subject to a 5-month testing period by the South Korean Register of Shipping, after which the Register approved the modifications made.[34][42] However, the Register decreased the authorised cargo capacity by half to 987 tons and required 2,000 tons of water to serve as ballast in order to provide balance.[43] The South Korea government's Audit and Inspection Board later revealed that the Register's licensing was based on falsified documents.[44] Prosecutors later estimated that 1,077 tons of cargo were permissible and that 1,695 tons of ballast was necessary to carry 1,077 tons of cargo.[45]

When Sewol began operating on March 15, 2013, she became the fourth ship operated by the company, and the second to be placed on its route.[46][47] She made three round trips per week from Incheon to Jeju, each 400 kilometres (250 mi) voyage taking 13.5 hours to complete.[48][49] On February 2014, Sewol passed a vessel safety inspection by the South Korean coast guard.[50] She had made the round trip a total of 241 times until the day of the incident.[46]

File:MS Sewol Track.jpg
Route of Sewol during the last voyage from Incheon to Jeju, the capsizing location marked by the rectangular speech bubble[51]

On 15 April 2014, Sewol was scheduled to leave the port at Incheon on 6:30 p.m., Korea Standard Time; instead, she was delayed for two and a half hours due to a thick fog, and was the only ship to leave port that evening, around 9 p.m.[52] When she departed, Sewol was carrying 476 passengers,[11][12][13] which was about half of her legal capacity of 921.[53] 325 of the passengers were students on a field trip from Danwon High School[54] and five passengers did not have a Korean nationality.[55] After the incident, the company reported that she was carrying 124 cars, 56 trucks, and 1157 tons of cargo.[56] The improperly secured cargo weighed twice the legal limit and is estimated to have been worth around ₩200 billion (US$200 million).[4][57]

The ship was commanded by 69-year-old Captain Lee Joon-seok, a substitute captain who was brought in as a replacement for the regular captain.[58][59] He had over 40 years of experience at sea, and had traveled over the route before.[60] He was hired on a one-year contract, with a monthly salary of ₩2.7 million.[61] Lee worked with 33 crew members for the journey,[62] out of which 19 were irregular, part-time workers.[63]

Later investigations revealed that Sewol had been issued warnings regarding its seaworthiness.[64] The South Korean Register of Shipping noted in a stability test report dated January 24, 2014 that Sewol had "became top-heavy and less stable."[65] Throughout the previous year, the regular captain had warned the company about the decrease in stability and passenger satisfaction and attributed it to the removal of the side ramp, but the company responded by threatening to fire him; the last warning and threat was on 9 April 2014, seven days before the incident.[66] The captain had also requested a repair for the malfunctioning steering gear on 1 April 2014, which was not done.[67] Before the last voyage, Sewol was loaded with 2,142 tons of cargo, twice the authorized limit of 1,077 tons, and 761 tons of ballast, less than half of the required 1,695 tons.[45] The company budget for the safety training of the crew was $2 American, which was used to buy a paper certificate.[45]

16 April 2014

Voyage and the channel (08:00–08:47)

File:Sewol passengers on morning of April 16.jpg
A photograph of passengers and crew on the ship on the morning of 16 April

On April 16 at 8:00 a.m. (KST), the 25-year-old third mate, Park Han-gyeol, began her scheduled four-hour shift on the bridge.[68][69] Although Park only had one year of experience in steering ships and an additional five months of experience on Sewol, she was to guide the ship while steering at the helm. During this time, Captain Lee was not required by law to stay at the bridge;[33][70] he left the helm at 8:08 a.m. and did not return for the next 30 minutes.[71]

Sometime before 8:48 a.m., Sewol entered the Maenggol Channel, which is notorious for its strong underwater currents, a condition which on April 16 was exacerbated by the full moon from the night before.[42][72] The channel, which was 3.7 miles (6.0 km) long and 2.8 miles (4.5 km) wide, was located 11 miles (18 km) from Jindo Island and served as a shortcut through the islets of the South coast of Korea.[68] While the wider area contained rock hazards and shallow waters, conditions were calm near the time of the incident and there were no rocks or reefs in the immediate vicinity.[48][73] Han Sang-sik, the head of the Jindo office of Dadohaehaesang National Park, later remarked that the width of the channel would have offered plenty of room for maneuvers.[42] The water temperature in the area was measured to be around 12 degrees Celsius, which can cause hypothermia in 90 minutes.[74]

Park had no previous experience of steering through the channel.[75] CCTV data later recovered showed Captain Lee returning to the helm at 8:37 a.m. and leaving at 8:41 a.m., actions which were then repeated by the chief engineer.[76] Shortly before the incident, the ship was traveling at about 18 knots; according to Chris Ware, a professor of the Greenwich Maritime Institute, this speed was "not excessive" and adequate for sharp turns.[77] Sewol followed its usual course until the sharp turn.[78]

Turn and effects (08:48)

As Sewol approached the fatal turn, breakfast was being served in the cafeteria, leading rescue workers to later guess that a large number of people would have gathered there.[79] Passenger Kim Seong-mok later recalled eating breakfast just before the incident.[80] Other passengers were in their cabins.[81] CCTV data taken on 8:40 a.m. showed students present and socializing on the deck.[82] Right before the incident, Third Mate Park was still at the helm, with Captain Lee absent from the steering room.[83] Helmsman Cho Joon-ki, who only had six months of experience on Sewol, was under Park's command at the time.[84][85]

Right before 8:48 a.m., Cho was steering the ship on a course of 135 degrees, or southeast.[86] At 8:48, Third Mate Park, who was monitoring the radar and radio in the ship, came to believe that another ship was approaching in a collision course and gave two orders to Helmsman Cho to turn the ship, first to 140 degrees, then to 145 degrees.[87][88] The fast undercurrents of the area necessitated that turns must be smaller than five degrees[86] and Park had previously received instructions from the regular captain that turns over five degrees should be performed with care, as Sewol's restoring force was low.[89] The expert advisory panel on the police-prosecution joint investigation team later agreed that a turn greater than five degrees made under any conditions would have upset the ferry, concluding that she was in no shape to carry passengers.[90]

Starting at 8:48 a.m., Cho heard Park's orders and made turns to starboard.[91] The second turn, of 10 degrees in one second, from 8:49:12 to 8:49:13, is considered especially sharp in that most large passenger ships would take two minutes to make a five degree turn.[92] The chief engineer later testified that 10 seconds after Third Mate Park's orders were given, he heard Park stating 'it's not working there, it's not working;' when the chief engineer asked about the situation, Cho replied that the "steering gear was not working."[93] As a response to the resulting imbalance, Park ordered Cho to balance the ship to "Port," but this order was misheard as a Korean word meaning to 'turn in the opposite direction,' a mishearing that did not affect the meaning.[92] The chief engineer testified that the ship began tilting right after Park's last order.[93]

The joint investigation team later found that Cho had attempted a starboard turn, and turned the ship 15 degrees to starboard when he was flustered when he perceived the first turn as being inadequate.[88] The finding corresponded with Third Mate Park's testimony that the ship would not have tilted if a turn from 15 to 35 degrees was not made, and Captain Lee's statement that he later saw the helm indicator fixed on 15 degrees to starboard.[88][94] However, Cho later testified that he had only heard the first order to head the ship to 140 degrees, not the second order for 145 degrees. According to Cho, he had turned three degrees to port because the ship continued to slip to starboard, and five degrees to port after the heading reached 145 degrees; he claimed that he turned 15 degrees to port after hearing Park's order for a restoration of balance.[88]

Later analysis of Sewol's track chart by the Ministry of Oceans and Fisheries revealed that the ship's Automatic Identification System had stopped collecting data from 8:48:37 to 8:49:13; consequently, the Ministry and the Jindo Vessel Traffic Service (VTS) lost 36 and 29 seconds of data, respectively.[95][96] While earlier reports and investigations believed that there was a power outage,[97][98] Huh Yong-bum, the head of the expert advisory panel on the police-prosecution joint investigation team, testified that the AIS failure was due to system limitations and that the failure did not affect the steering.[96]

According to the joint investigation team, the sharp turn was a combined result produced by the steering error and the lessened restoring force caused by overloading; investigations did not show any malfunctions with the generator or the battery.[35][99] From 8:49:26, AIS data showed Sewol's angular velocity accelerate from 0.29 radians per second to 0.83, 1.00, and 2.00 until 8:49:39; these readings were consistent with previous testing data gained from earlier tests conducted on an empty Sewol.[94] Consequently, the ship herself listed 20 degrees into the water; on 8:49:40, causing cargo to fall to one side of the ship.[100][101] The impact caused the ship's gyroscope to erroneously record angular velocities of 15 radians per second on 8:49:40, 14 on the next second, and -11 on the consequent second, and tilt the ship 10 degrees further into the water.[94][100] Passengers also reported hearing a loud "bang."[102]

As Helmsman Cho sharply turned the wheel from 135 to 150 degrees, Sewol began to list to port and tilt towards the water.[88] The overall effect was that the ship turned about 45 degrees to the right, then rotated 22 degrees on the spot for a span of 20 seconds.[103] The cargo falling to one side of the ship caused Sewol to lose all her restoring force and allowed water to flow into the ship through the side door of the cargo loading bay and the car entrance located at the stern. This scenario was confirmed by simulations separately run by the expert advisory panel on the joint investigation team, the Korea Research Institute of Ships and Ocean Engineering, and the Advanced Marine Engineering Center of Seoul National University.[35] The chief engineer testified that the tilting lasted for about two to three minutes after the initial tilt.[93] During this time, Oh Yong-seok, an off-duty helmsman who was sleeping in his cabin, was awakened when he was thrown against its port side.[104] As of 8:50 a.m., Sewol was leaning 30 degrees to port.[105]

Captain Lee, who was in his private cabin at the time of the incident,[106] immediately rushed to the bridge.[107] After a short period, all the ship's mates and helmsmen arrived there as well.[104] Around this time, the chief engineer stopped the engines, although it is unknown whether it was on his own volition or following an order from Captain Lee.[108] At 8:50, the chief engineer ordered an evacuation of the engine room through a call to the assistant engineer.[109] During this time, Park was crying, as she was taken aback by the sudden incident; this lasted until at least 9:06 a.m.[93][110]

With the engines off, Sewol became unable to change directions and began drifting sideways.[108][111] A passenger later testified that lights went out after the ferry started listing.[112]

Calls for rescue (8:52–9:30)

<templatestyles src="Template:Quote_box/styles.css" />

Announcement repeated during capsizing

Do not move. Just stay where you are. It's dangerous if you move, so just stay where you are.

As reported by CNN on April 16th.[113]

As Sewol began sinking, the ferry's intercom system started ordering the passengers to stay put, alleging that moving was dangerous.[114] The announcements were made by a communication officer, Kang Hae-seong, who had not consulted the manual before the broadcast.[104] The announcements began broadcasting by at least 8:52 a.m.[115] and continued even when water began flooding passenger compartments.[116] Other crew members corroborated this order, instructing passengers to stay put.[13] Captain Lee also instructed passengers to stay put and did not change the order even as he was leaving the ship.[117]

The first emergency call was made by Choi Duk-ha, a Danwon high school student aboard the ferry.[118] At 8:52 a.m., he called the national emergency service number and reported to the Jeollanam-do fire station that Sewol was capsizing.[119] Choi was connected to the Mokpo Coast Guard at 8:54 a.m. and was asked to give the latitude and longitude of the ship's location.[120] Three minutes later, the Mokpo Coast Guard station situation room ordered patrol vessel No. 123 to be dispatched to the scene; the vessel was launched at 8:58 a.m.[121][122] Following the Coast Guard search and rescue manual, the boat was to be in charge of surveying the area and "swiftly" rescuing passengers.[121] Choi did not survive the capsizing and was later found dead.[29][123]

At 8:55 a.m., Sewol's crew made their first distress call to the Jeju vessel traffic service and asked the Jeju VTS to notify the Coast Guard, as the ferry was rolling and in danger.[124][125] At 8:56 a.m., the Jeju VTS called the Jeju Coast Guard. Three minutes later, the Jeju Coast Guard called the Mokpo Coast Guard and discovered that a patrol boat had already been dispatched.[122] At 9:01 a.m., a crew member on Sewol called the Incheon branch of Chonghaejin Marine to report the situation, and the Chonghaejin Marine headquarters located in Jeju then called Captain Lee at 9:03 a.m. for a report of the situation. The Incheon branch then talked with the first mate in five telephone calls over the next 35 minutes.[126]

At 9:06 a.m., the Jindo VTS were informed of the capsizing incident by the Mokpo Coast Guard.[122] Around this time, the crew began communicating with the Jindo VTS, which was closer to their location.[125] For the next two minutes, Jindo VTS alerted two other ships that Sewol was sinking, with one confirming that it had visual contact with the ship.[127] At 9:07 a.m., Sewol's crew confirmed that the ferry was capsizing and requested the help of the Coast Guard. At 9:14 a.m., the crew stated that the ship's angle of heel made evacuation impossible. Around this time, the captain of Patrol Vessel 123 was appointed the commander of the scene.[121] Four minutes afterwards, the crew of Sewol reported to the VTS that the ferry has heeled more than 50 degrees to port.[128]

At 9:23 a.m., the VTS ordered the crew to inform the passengers to wear personal flotation devices. When the crew replied that the broadcasting equipment was out of order, the VTS told them to personally order the passengers to wear life jackets and more clothing.[128] At 9:25 a.m., the VTS asked the captain to decide quickly whether to evacuate the ship, stating that they did not have enough information to make the decision. When the captain inquired about the rescue, the VTS replied that patrol boats were due to arrive in 10 minutes and a helicopter in one minute. The captain then replied that there were too many passengers for the helicopter.[128]

During this time, the captain told passengers to stay in their rooms.[129] The communications officer, using the ship's intercom, repeatedly ordered passengers not to move.[102][130]

Around 9:30 a.m., the captain gave orders to evacuate the ship, though the order may not have been relayed to all the passengers.[131] At 9:33 a.m., after confirming that nearby ships had volunteered to help in the rescue operations, the VTS told all ships to drop lifeboats for the passengers. At 9:38 a.m., all communications were cut off between the VTS and the ferry. About three minutes after all communications were cut, about 150 to 160 passengers and crew jumped overboard.[128]

Sewol took two and a half hours to sink.[130] By around 11:18 a.m., the bow of the ship was submerged, with a section of the hull about 2 metres (6 ft 7 in) high and 20 to 30 metres (66 to 98 ft) long showing above the water. At 12:00  noon on 18 April, only 50 centimetres (20 in) of the bulbous bow was above water.[132] As of 1:03 p.m., the ship was completely submerged.[133]

Captain and crew

During the capsizing, some members of the crew drank beer.[134] The crew also had seven phone calls with staff from Chonghaejin Marine.[135] As passengers stayed in their cabins as instructed, the captain and crew members abandoned the ship.[136] The captain, the chief engineer, and the chief and second mates were the first people to be rescued.[137] The captain was rescued around 9:46 a.m.[138][139]

Passengers

As the ship capsized, some passengers followed the announcements to stay put, even as the water came in.[140] Most of the student passengers obeyed the announcements.[141] Some passengers who climbed to the top of the ship or jumped into the water were rescued.[142]

Videos recording passengers during the capsizing have been recovered.[143][144] Some recorded the announcements telling passengers to stay in place and put on life jackets,[145] while some showed passengers joking around,[143] putting on life jackets,[145] and sending farewells.[144]

Passengers made calls,[141] sent text messages,[146] and KakaoTalk mobile messages[147] during the capsizing. The last message was sent at 10:17 a.m.[139] Text messages and social media posts allegedly made by survivors after the capsizing have circulated in the media, but an investigation by the Cyber Terror Response Center found that passengers did not use their phones between 12:00 p.m. on April 16 and 10:00 a.m. of April 17th[148] and that all the reported survivors' messages were fake.[149]

Rescue operations

During the capsizing and the subsequent reporting, the government's announcements, as well as the media, have been inconsistent and inaccurate.[150] An editorial in The Huffington Post stated that the governmental reports were like a rubber band, 'increasing at one moment and decreasing at another.'[151] Newspapers such as The JoongAng Ilbo, MBN, and JTBC have made corrections and apologies concerning their earlier reports.[152] Conspiracy theories have also been present.[153]

First day

Sewol sinking, pictured by the Korea Coast Guard

At 8:58 a.m. (KST) on April 16, 2014, the Mokpo Coast Guard dispatched patrol vessel No. 123 in response to the first report of the incident.[122] After receiving the news of the capsizing from the Jeollanam Provincial Government, the Republic of Korea Navy 3rd Fleet sent a Gumdoksuri-class patrol vessel (PKG) to the accident site at 9:03 a.m.; the Navy dispatched another PKG at 9:09 a.m.[154] At 9:04 a.m., the government created the Central Disaster Countermeasure Headquarters (중앙재난안전대책본부), as an organization which would directly report to the government. The South Korean coast guard set up a rescue operations headquarters at 9:10 a.m.[155]

Patrol vessel No.123 arrived at the scene near 9:30 a.m.[122] as the first ship to reach the site after the incident.[156] During the time between the dispatch and the operations, members failed to raise the Sewol, and chose to call for other ships on the radio.[157] Consequently, members on the vessel had not directly communicated with the Sewol, and were not aware of the content of the communication between the Sewol and the Jindo VTS on arrival.[158] At the time of arrival, the Sewol had listed about 50 to 60 degrees to port.[159] When the vessel arrived, members made announcements for five minutes, calling people to abandon ship and jump into the water.[157] The vessel began rescue operations on 9:38 a.m., with the dispatching of a rubber boat.[159] Passengers who had reached the deck or jumped into the water were rescued, including the captain, but rescue members could not get inside the ship due to the list.[157] However, people trapped inside the pilothouse were rescued by breaking through the windows.[157]

At 9:35 a.m., the Korean Ministry of National Defense started operating Counter-disaster Headquarters (재난대책본부). At 9:40 a.m., the Ministry of Oceans and Fisheries declared the accident to be the highest state of emergency in terms of naval accidents; consequently, the Central Accident Response Headquarters (중앙사고수습본부) was established.[160] At the same time, the Ministry of Health and Welfare sent emergency vehicles and the first squad of the Disaster Medical Support Team (재난의료지원팀) to Jindo.[161] At 11:28 a.m., the Korea Navy's Ship Salvage Unit (SSU) was reported to have been deployed for the operations.[162]

At 2:42 p.m., 150 special forces personnel from the ROK Army Special Warfare Command, including 40 scuba divers, were sent for the operation. At this point, 196 personnel, including 82 in the SSU and 114 in the ROK Naval Special Warfare Flotilla were involved in the operations.[163] At 3:07, the regional government of the Gyeonggi Province was reported to have started operating the Prevention and Countermeasures Headquarters (재난안전대책본부).[164] After 5 p.m., units from the SSU began undersea operations.[165] At 5:13, the Gyeonggi-do Office of Education was reported to have started operating the Ansan Danwon High School Accident Countermeasures Report Compiling Headquarters (안산 단원고 사고대책 종합상황본부).[166] At 8:00, operations investigating the ship's hull were ceased.[167]

As of 22:03, the following units were involved in rescue operations: Naval forces include sailors from the 3rd Fleet (제3함대; 第三艦隊), a Dokdo-class amphibious assault ship, a Chungmugong Yi Sun-sin-class destroyer, and an Ulsan-class frigate. The ROK Air Force sent support units such as the Lockheed C-130 Hercules, Sikorsky HH-60 Pave Hawk, and HH-47 variant of the Boeing CH-47 Chinook. The ROK Army sent units including 150 Special Warfare Command soldiers and 11 ambulances.[168]

Second day

File:U.S. Navy helicopter landing on a ship after Sewol rescue operation.jpg
A U.S. Navy MH-60S Seahawk helicopter conducted search and rescue operations at the request of the South Korean navy near where the Sewol sank, on 17 April 2014.

Starting on April 17, Undine Marine Industries Co., a privately held company,[169] began to lead the search for missing passengers.[170] At 0:30 a.m., hull investigations were started by the ROK Coast Guard with the help of flares.[171] As of 6:00 a.m., 171 ships, 29 aircraft and 30 divers were involved in the rescue effort. The Korea Coast Guard had assigned 20 divers in teams of two. The ROK Navy had also assigned 8 divers.[172] However, the coast guard prevented navy divers from participating[170] while waiting for divers from Undine Industries.[173] At 7:24 a.m., civilian groups of expert divers were reported to be helping out in the rescue operations.[174] During the morning, the number of divers involved in the operations reached 555.[175] The Navy also established a military control tower on a Dokdo-class amphibious assault ship.[176] Starting around 2:00 p.m., rescue operations were practically stopped due to bad weather conditions.[177] A marine crane arrived on the scene at night.[178]

Subsequent operations

At 10:50 a.m. on April 18,[179] the ROK Coast Guard began pumping in air to support possible air pockets.[130] At the same time, divers entered the capsized ship's hull[180] but only gained access to the cargo deck.[181] The divers' entrance was later labeled a 'failure' by the Central Disaster Countermeasure Headquarters.[182] On 19 April, a Navy petty officer who was injured during rescue operations died.[183] On 21 April, remotely operated underwater vehicles began to be used for operations.[184] On 24 April, the CR2000 'Crabster' robot was sent to the rescue site.[185] On 6 May,[186] a diver working for Undine Marine Industries died during the search.[187] This was followed by another diver's death on 30 May.[188] On 17 July, a firefighting helicopter returning from rescue operations crashed near an apartment complex, killing all five officers aboard and injuring a high school student.[189][190]

The South Korean government announced on April 22, 2015 that it had approved plans to salvage the wreckage of the Sewol in hopes of finding more information about the sinking and recovering the bodies of the nine victims still missing. The plan was initially put forward by president Park Geun-hye, and was endorsed by the Minister of Public Safety and Security, Park In-yong. The operation is expected to take as long as 18 months and to cost between $91 and $137 million.[191]

Survivors and casualties

At 11:01 a.m., Munhwa Broadcasting Corporation (MBC) began reporting that all students had been rescued; this news was re-reported by other news organizations, and continued until 11:26 a.m.[192] Around 11 a.m. (KST), officers working for the educational departments for the Gyeonggi Province sent text messages to the students' parents stating that all students had been rescued.[193] The officers' belief was apparently confirmed by a police officer in the Danwon Police Department.[192] Initial reports stated that rescuers retrieved 368 people from cold waters as the passengers, mostly students, had jumped overboard when the vessel started sinking; the South Korean government later corrected this statement, saying 295 passengers remained missing.[194] 22 of the 29 crew survived, including 15 responsible for the navigation.[195]

Early in the rescue efforts, a 27-year-old female crew member was found dead inside the sinking vessel and a male high school student died shortly after arriving at a hospital.[196][197]

In its April 17 morning edition, The Chosun Ilbo reported that 174 people had been rescued, 4 had died, and 284 were missing.[198] According to CNN and its affiliate YTN, six people died.[199] News1 Korea reported that, as of 8:00 a.m. on April 17, 179 people had been rescued, 6 had died and 290 were missing.[172] Three more people were found dead at 11:00 a.m. and the confirmed death toll rose to 9.[200] At 10 p.m., Yonhap news confirmed that the death toll had risen to 14.[201] By the morning of 18 April, the death toll had risen to 28.[202] On April 19, the death toll rose to 36.[203] By 20 April, the death toll reached 49.[204][205] By 6 May, a diver searching the sunken ferry had died; not including the diver, the death toll in the ferry disaster rose to 264, with 38 people still missing.[206] By 10 May 2014, the death toll reached 275, with dozens more still missing.[207] By 21 May, the death toll had risen to 288, leaving 16 missing.[208] As of 21 May, the 16 missing were 7 Danwon High School students, 3 Danwon High School teachers, 4 other passengers, and 2 cabin crew members.[209] On 5 and 6 June, one dead passenger and one dead cabin crew member were found, bringing the casualty count to 290, while the number of missing passengers was reduced to 14.[210][211] By 9 June 2014, a 28-year-old female Danwon High School teacher as well as a 17-year-old male Danwon high school student were found bringing the death toll to 292 and leaving 12 missing.[212][213][214] On 24 June, the body of a female student was recovered bringing the death toll to 293 and lowering the missing to 11, including 5 Danwon High School students.[215] The death toll stands at 294 as of 22 July 2014, with 10 missing; the date marked the recovery of the last cabin crew member.[216]

The sinking of the Sewol is the deadliest ferry disaster in South Korea since 14 December 1970, when the sinking of the ferry Namyoung killed 326 out of the 338 people aboard.[217][218]

Foreign response

Investigation

Causes

Direct causes

As of 17 April 2014, the ROK Coast Guard concluded that an "unreasonably sudden turn" to starboard,[225] made between 8:48 and 8:49 a.m. (KST),[226] was the cause of the capsizing.[225] According to the Coast Guard, the sudden turn caused the cargo to shift to port, causing the ship to list and to eventually become unmanageable for the crew.[225] The existence of the sudden turn has been confirmed by the analysis of the ship's Automatic Identification System data.[227] The crew of the ferry has agreed that the main cause was the sudden turn.[228] Experts such as Lee Sang-yun (Korean: 이상윤), a professor and head of the environment/maritime technology institute of the Pukyong National University, have also agreed.[229]

Overloading and not properly securing cargo are also being seen as direct causes.[230] The MV Sewol was carrying 3,608 tons of cargo, more than three times the limit of 987 tons.[231] The overloading was also previously noted by an off-duty captain and the first mate.[232] Lee Sang-yun also proposed overloading as a cause.[233] According to the off-duty captain of the Sewol, the ship owners ignored his warning that the ship should not carry so much cargo because she would not be stable.[234]

The Sewol was carrying only 580 tons of ballast water, much less than the recommended 2,030 tons; this would make the vessel more prone to list and capsize.[235] South Korean newspaper The Chosun Ilbo argued that the discharging of ballast water was a cause of the incident.[236] The crew had reportedly pumped out hundreds of tons of ballast water from the bottom of the ship in order to accommodate the additional cargo.[237]

Secondary causes

Secondary causes have also affected the capsizing of the ferry by decreasing the restoring force.[238] The crew of the ferry stated that the lack of restoring force was a cause of the disaster.[228] The Prosecution/Police Coalition Investigations Headquarters (검경합동수사본부) is currently investigating secondary causes which could have lessened the ship's restoring force.[239]

Renovations which added extra passenger cabins have been proposed as a main secondary cause by Kim Gill-soo (Korean: 김길수), a professor in the maritime transport technological department at the Korea Maritime University.[240][241] This possible cause has also been supported by the captain,[242] as well as Lee Sang-yun.[229]

Obsolete theories

Explosion

Gong Gil-young (Korean: 공길영), a professor of aviation engineering at Korea Maritime University, commented that the sudden turn was simply the 'first cause' and that there were secondary causes to the incident. He advocated an explosion as the most probable secondary cause.[243][244]

Reef collision

At the beginning of the investigation, the ROK Coast Guard thought that the cause was a collision with a reef, believing this likely because the area was foggy.[245] The captain denied this was the cause of the accident,[246] and a reef collision has been dismissed as a cause by consensus among experts.[247] The theory is also not currently advocated by the Coast Guard.[225]

Captain and crew

On 19 April, the captain of the ferry was arrested on suspicion of negligence of duty, violation of maritime law and other infringements.[248] The captain had abandoned the ship with passengers still aboard the ferry, while South Korean law explicitly requires captains to remain on the ship during a disaster.[249][250][251] Two other crew members, a helmsman and the third mate, were also arrested on that day on suspicion of negligence and manslaughter.[252] By 26 April, twelve further arrests had been made with the whole crew responsible for navigation in detention.[253][254]

On 15 May, Captain Lee Jun-seok, First Mate Kang Won-sik (who was responsible for managing the ship's ballast), Second Mate Kim Young-ho, and Chief Engineer Park Gi-ho were indicted on charges of homicide through gross negligence (also described as murder), which carry a potential death penalty.[237][255][256][257] The other eleven crew members face lesser charges of abandoning the ship and ship safety offences.[25]

Three crew members, Park Ji-young, Jeong Hyun-seon, and Kim Ki-woong, are credited by survivors with staying aboard the ferry to help passengers escape. All three went down with the sinking vessel.[258]

Operators

On 8 May, the chief executive of Chonghaejin Marine, Kim Han-sik, was arrested and faced charges including causing death by negligence.[259] Four other company officials were also taken into custody.[260]

The Ministry of Oceans and Fisheries cancelled Chonghaejin Marine's license to operate ferries on the Incheon-Jeju Island route in May 2014.[261]

Owners

Yoo Byung-eun, former chairman of Chonghaejin Marine, ignored Incheon District Prosecutors' Office summonses,[262][263][264] and went into hiding.[265][266][267] On 22 May, the Incheon District Court issued an arrest warrant and Korean authorities offered a 50 million (US$48,800) reward for information leading to the arrest of Yoo.[268][269] On 25 May, the reward was raised tenfold to ₩500 million (US$488,000).[270][271] On 21 July 2014, it was reported that a body found in a field in June was believed to be Yoo's.[272]

Regulation

The disaster raised questions regarding governmental regulation of shipping in South Korea. Shipping is regulated by the Korean Shipping Association, which is also an industry trade group, which experts consider a likely conflict of interest. In addition, government regulators outside the Association frequently move to jobs as part of the association after their government service. Yun Jong-hwui, a professor at Korea Maritime and Ocean University notes that while South Korean regulations are strong, they are often poorly enforced.[273]

Legal cases

On 3 June, the Gwangju District Court issued arrest warrants for a senior vessel safety operator of the Korea Shipping Association's Incheon unit and a vessel inspector of the Korean Register of Shipping's Mokpo unit.[274] Amongst 15 crew accused of the sinking, prosecutors sought the death penalty for the captain under the charge of homicide and the prosecution told the court that he failed to carry out his duty. Lead prosecutor Park Jae-eok said: "Lee supplied the cause of the sinking of the Sewol...he has the heaviest responsibility for the accident. We ask that the court sentence him to death." While no formal pleas were made, Lee denied intent to kill. The others had lesser charges, including negligence. A three-judge panel would announce its verdicts in November.[275] The Incheon District Court on Wednesday 5 November sentenced the late ferry owner Yoo Byung-eun’s eldest son Yoo Dae-kyoon to three years in prison for embezzlement and breach of trust.[276]

On 11 November 2014, the Gwangju District Court found Captain Lee Jun-seok guilty of negligence and he was sentenced to 36 years' imprisonment. The judges said that he was clearly not the only person responsible for the tragedy and they accepted that his negligence did not amount to an intent to kill. The chief engineer of the ferry, identified by his surname Park, was found guilty of murder and jailed for 30 years. Thirteen other crew members were given jail sentences of up to 20 years on charges including abandonment and violating maritime law. Relatives of victims were distraught at the verdict, with some weeping. The AFP news agency reported that one woman screamed in the courtroom: "It's not fair. What about the lives of our children? They (the defendants) deserve worse than death."[277]

In the cases against officials over the overloading of cargo, Kim Han-sik, Chonghaejin Marine's chief executive, was found guilty of negligence and received a ten-year prison term. Six other company employees and a Korean Shipping Association official also received prison sentences.[278]

Following an appeals by prosecutors and the accused, on 28 April 2015 Captain Lee was found guilty of murder and his sentence increased to life imprisonment, while those for 14 other crew members were reduced to a maximum of 12 years, including 10 years for chief engineer Park, whose murder conviction was overturned.[279][280] Judge Jeon Il-ho explained "We drew a distinction between the Captain Lee Joon-seok who has a grave responsibility and crew members who took orders from the captain."[279] Kim Han-sik's sentence was also reduced to seven years on appeal.[281]

Reactions

File:Memorial for the victims of the sinking of the MV Sewol 13.JPG
A memorial wall near the Danwon High School, where most of the victims were from
File:Memorial for the victims of the sinking of the MV Sewol 47.JPG
A memorial ceremony in Hwarang Public Garden, a park near the Danwon High School
File:Pope Francis Korea Haemi Castle 19.jpg
Pope Francis wearing a yellow ribbon on his 2014 state visit to South Korea.

Political

In addition to reaction against the actions of the captain and much of the crew of the Sewol,[282] there has been a much wider political reaction to the disaster. Criticism has ranged from anger at the lax regulatory environment which may have contributed to the safety violations that could have sunk the Sewol,[283] to anger about the rescue operations,[284] to anger at Park Geun-hye, the President of South Korea, whose approval ratings have fallen from a high of 71 percent before the disaster to "the 40 percent range" weeks afterwards.[285]

Political reaction to the Sewol sinking has been intensified by a series of events. A prominent South Korean politician from the ruling Saenuri Party, Chung Mong-joon, was forced to apologize when his son wrote a controversial Facebook post criticizing the public for criticizing the government over the disaster.[286] Many parents of the victims of the tragedy have been expressing deep anger at the government, ranging from reportedly berating Prime Minister Jung Hong-won[287] to shouting at President Park Geun-hye,[288] to parents staging protests at the presidential palace itself, partly inflamed by a reported remark by a senior news editor at the government-influenced Korean Broadcasting System that the number of dead in the ferry tragedy was "not many, compared with the number of people killed in traffic accidents each year".[289]

Barack Obama, the President of the United States, sent his condolences, stated that the United States would help in the search for survivors and during a state visit to South Korea presented a magnolia tree from the White House to the high school.[290][291] Japanese prime minister Shinzo Abe offered sympathy to the victims.[292] Truong Tan Sang, the President of Vietnam, as well as the deputy prime minister and the minister of foreign affairs sent their condolences to Yun Byung-se, South Korea's Minister of Foreign Affairs.[293] Singapore's Prime Minister Lee Hsien Loong sent their condolences to the president of South Korea.[294] Xi Jinping, the President of China, sent messages on condolences to Park.[295][296]

On 27 April, Jung Hong-won, the prime minister of South Korea, accepted responsibility and announced his resignation.[297]

On 29 April, South Korean president Park Geun-hye indirectly apologized for the government's response to ferry sinking.[298][299][300]

On 30 April, North Korea sent its condolences.[301]

On 18 May 2014, BBC reported that President Park Geun-hye announced South Korea "plans to break up its coastguard" after failing to respond well during the MV Sewol ferry disaster.[302] According to Park, "investigation and information roles will be transferred to the Korean police while the rescue and salvage operation and ocean security roles will be transferred to the Department for National Safety[303] which will be newly established".[304]

On 19 November 2014, the Korea Coast Guard ceased control as the Ministry of Public Safety and Security was founded at the same day.

Civilian

On 17 April, a representative of the Cheonghaejin Marine Company apologized for the incident.[305] The chairman and CEO of Korean Register of Shipping, Chon Young-Kee, resigned on 28 April, following raids on KR offices by South Korean prosecutors.[306]

On 18 April, the rescued vice principal of Danwon High School Kang Min-kyu, 52, committed suicide by hanging himself. Police stated that a note was found in his wallet.[307] He had organized the field trip that had brought the high school party aboard the ship, and Kang had written in his two-page note that "Surviving alone is too painful when 200 lives are unaccounted for ... I take full responsibility."[308][309] The note ended with a request that his body be cremated and the ashes scattered over the site of the accident, "that I might be a teacher in heaven to those kids whose bodies have not been found."[310]

On 22 April, a netizen made a post encouraging others to take part in the 'KakaoTalk yellow ribbon wearing campaign.' The image accompanying the post had a caption stating, 'One small movement, big miracles'.[311][312] Since then, the yellow ribbon has gained meaning to symbolize mourning.[313] The ribbons are prominent in the social media, sometimes as profile photos.[314] Celebrities such as Jo Kwon and Hye-rim Park had joined this movement.[312]

The disaster is the subject of the 2014 documentary film The Truth Shall Not Sink with Sewol.[315]

On 17 April 2015, a day after the first anniversary of sinking that killed 304 people, 4,475 participants holding electronic candles formed the shape of the Sewol ferry at the commemoration event titled ‘The Saddest Challenge in the World’ in Seoul Plaza in front of City Hall. They managed to attempt a Guinness World Record for largest torchlight vigil image. The recent world record,was called ‘Lights in the dark’ that 3,777 participants gathered at a square in Jakarta Indonesia as a symbol of hope and prayer, got broken by ‘The Saddest Challenge in the World’.[316]

See also

Notes

  1. Alternative meanings that have been reported include time and tide, which is a mistranslation that goes against the Hanja of the name

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 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. 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 Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 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. 13.0 13.1 13.2 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. 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.
  19. 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. 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. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.
  26. Jin-man, Lee (17 April 2015) Photo of the Day Yahoo! India. 17 April 2015. Retrieved 5 May 2015.
  27. 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 Lua error in package.lua at line 80: module 'strict' not found.
  30. 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 Lua error in package.lua at line 80: module 'strict' not found.
  34. 34.0 34.1 Lua error in package.lua at line 80: module 'strict' not found.
  35. 35.0 35.1 35.2 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. 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.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. 42.0 42.1 42.2 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. 48.0 48.1 Lua error in package.lua at line 80: module 'strict' not found.
  49. 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. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  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. 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. 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. 68.0 68.1 Lua error in package.lua at line 80: module 'strict' not found.
  69. 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. 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. 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. 86.0 86.1 Lua error in package.lua at line 80: module 'strict' not found.
  87. Lua error in package.lua at line 80: module 'strict' not found.
  88. 88.0 88.1 88.2 88.3 88.4 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.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Lua error in package.lua at line 80: module 'strict' not found.
  92. 92.0 92.1 Lua error in package.lua at line 80: module 'strict' not found.
  93. 93.0 93.1 93.2 93.3 Lua error in package.lua at line 80: module 'strict' not found.
  94. 94.0 94.1 94.2 Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.
  96. 96.0 96.1 Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found.
  98. Lua error in package.lua at line 80: module 'strict' not found.
  99. Lua error in package.lua at line 80: module 'strict' not found.
  100. 100.0 100.1 Lua error in package.lua at line 80: module 'strict' not found.
  101. Lua error in package.lua at line 80: module 'strict' not found.
  102. 102.0 102.1 Lua error in package.lua at line 80: module 'strict' not found.
  103. Lua error in package.lua at line 80: module 'strict' not found.
  104. 104.0 104.1 104.2 Lua error in package.lua at line 80: module 'strict' not found.
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. Lua error in package.lua at line 80: module 'strict' not found.
  107. Lua error in package.lua at line 80: module 'strict' not found.
  108. 108.0 108.1 Lua error in package.lua at line 80: module 'strict' not found.
  109. Lua error in package.lua at line 80: module 'strict' not found.
  110. Lua error in package.lua at line 80: module 'strict' not found.
  111. Lua error in package.lua at line 80: module 'strict' not found.
  112. Lua error in package.lua at line 80: module 'strict' not found.
  113. Lua error in package.lua at line 80: module 'strict' not found.
  114. Lua error in package.lua at line 80: module 'strict' not found.
  115. Lua error in package.lua at line 80: module 'strict' not found.
  116. Lua error in package.lua at line 80: module 'strict' not found.
  117. Lua error in package.lua at line 80: module 'strict' not found.
  118. Lua error in package.lua at line 80: module 'strict' not found.
  119. Lua error in package.lua at line 80: module 'strict' not found.
  120. Lua error in package.lua at line 80: module 'strict' not found.
  121. 121.0 121.1 121.2 Lua error in package.lua at line 80: module 'strict' not found.
  122. 122.0 122.1 122.2 122.3 122.4 Lua error in package.lua at line 80: module 'strict' not found.
  123. Lua error in package.lua at line 80: module 'strict' not found.
  124. Lua error in package.lua at line 80: module 'strict' not found.
  125. 125.0 125.1 Lua error in package.lua at line 80: module 'strict' not found.
  126. Lua error in package.lua at line 80: module 'strict' not found.
  127. Lua error in package.lua at line 80: module 'strict' not found.
  128. 128.0 128.1 128.2 128.3 Lua error in package.lua at line 80: module 'strict' not found.
    • Translation by Wall Street Journal [1]
    • Translation by CNN [2]
  129. Lua error in package.lua at line 80: module 'strict' not found.
  130. 130.0 130.1 130.2 Lua error in package.lua at line 80: module 'strict' not found.
  131. Lua error in package.lua at line 80: module 'strict' not found.
  132. Lua error in package.lua at line 80: module 'strict' not found.
  133. Lua error in package.lua at line 80: module 'strict' not found.
  134. Lua error in package.lua at line 80: module 'strict' not found.
  135. Lua error in package.lua at line 80: module 'strict' not found.
    • Translation [3]
  136. Lua error in package.lua at line 80: module 'strict' not found.
  137. Lua error in package.lua at line 80: module 'strict' not found.
  138. Lua error in package.lua at line 80: module 'strict' not found.
  139. 139.0 139.1 Lua error in package.lua at line 80: module 'strict' not found.
  140. Lua error in package.lua at line 80: module 'strict' not found.
  141. 141.0 141.1 Lua error in package.lua at line 80: module 'strict' not found.
  142. Lua error in package.lua at line 80: module 'strict' not found.
  143. 143.0 143.1 Lua error in package.lua at line 80: module 'strict' not found.
  144. 144.0 144.1 Lua error in package.lua at line 80: module 'strict' not found.
  145. 145.0 145.1 Lua error in package.lua at line 80: module 'strict' not found.
  146. Lua error in package.lua at line 80: module 'strict' not found.
  147. Lua error in package.lua at line 80: module 'strict' not found.
  148. Lua error in package.lua at line 80: module 'strict' not found.
  149. Lua error in package.lua at line 80: module 'strict' not found.
  150. Lua error in package.lua at line 80: module 'strict' not found.
  151. Lua error in package.lua at line 80: module 'strict' not found.
  152. Lua error in package.lua at line 80: module 'strict' not found.
  153. Lua error in package.lua at line 80: module 'strict' not found.
  154. Lua error in package.lua at line 80: module 'strict' not found.
  155. Lua error in package.lua at line 80: module 'strict' not found.
  156. Lua error in package.lua at line 80: module 'strict' not found.
  157. 157.0 157.1 157.2 157.3 Lua error in package.lua at line 80: module 'strict' not found.
  158. Lua error in package.lua at line 80: module 'strict' not found.
  159. 159.0 159.1 Lua error in package.lua at line 80: module 'strict' not found.
  160. Lua error in package.lua at line 80: module 'strict' not found.
  161. Lua error in package.lua at line 80: module 'strict' not found.
  162. Lua error in package.lua at line 80: module 'strict' not found.
  163. Lua error in package.lua at line 80: module 'strict' not found.
  164. Lua error in package.lua at line 80: module 'strict' not found.
  165. Lua error in package.lua at line 80: module 'strict' not found.
  166. Lua error in package.lua at line 80: module 'strict' not found.
  167. Lua error in package.lua at line 80: module 'strict' not found.
  168. Lua error in package.lua at line 80: module 'strict' not found.
  169. Lua error in package.lua at line 80: module 'strict' not found.
  170. 170.0 170.1 Lua error in package.lua at line 80: module 'strict' not found.
  171. Lua error in package.lua at line 80: module 'strict' not found.
  172. 172.0 172.1 Lua error in package.lua at line 80: module 'strict' not found.
  173. Lua error in package.lua at line 80: module 'strict' not found.
  174. Lua error in package.lua at line 80: module 'strict' not found.
  175. Lua error in package.lua at line 80: module 'strict' not found.
  176. Lua error in package.lua at line 80: module 'strict' not found.
  177. Lua error in package.lua at line 80: module 'strict' not found.
  178. Lua error in package.lua at line 80: module 'strict' not found.
  179. Lua error in package.lua at line 80: module 'strict' not found.
  180. Lua error in package.lua at line 80: module 'strict' not found.
  181. Lua error in package.lua at line 80: module 'strict' not found.
  182. Lua error in package.lua at line 80: module 'strict' not found.
  183. Lua error in package.lua at line 80: module 'strict' not found.
  184. Lua error in package.lua at line 80: module 'strict' not found.
  185. Lua error in package.lua at line 80: module 'strict' not found.
  186. Lua error in package.lua at line 80: module 'strict' not found.
  187. Lua error in package.lua at line 80: module 'strict' not found.
  188. Lua error in package.lua at line 80: module 'strict' not found.
  189. Lua error in package.lua at line 80: module 'strict' not found.
  190. Lua error in package.lua at line 80: module 'strict' not found.
  191. Lua error in package.lua at line 80: module 'strict' not found.
  192. 192.0 192.1 Lua error in package.lua at line 80: module 'strict' not found.
  193. Lua error in package.lua at line 80: module 'strict' not found.
  194. Lua error in package.lua at line 80: module 'strict' not found.
  195. Lua error in package.lua at line 80: module 'strict' not found.
  196. Lua error in package.lua at line 80: module 'strict' not found.
  197. Lua error in package.lua at line 80: module 'strict' not found.
  198. Lua error in package.lua at line 80: module 'strict' not found.
  199. Lua error in package.lua at line 80: module 'strict' not found.
  200. Lua error in package.lua at line 80: module 'strict' not found.
  201. Lua error in package.lua at line 80: module 'strict' not found.
  202. Lua error in package.lua at line 80: module 'strict' not found.
  203. Lua error in package.lua at line 80: module 'strict' not found.
  204. Lua error in package.lua at line 80: module 'strict' not found.
  205. Lua error in package.lua at line 80: module 'strict' not found.
  206. Lua error in package.lua at line 80: module 'strict' not found.
  207. Lua error in package.lua at line 80: module 'strict' not found.
  208. Lua error in package.lua at line 80: module 'strict' not found.
  209. Lua error in package.lua at line 80: module 'strict' not found.
  210. Lua error in package.lua at line 80: module 'strict' not found.
  211. Lua error in package.lua at line 80: module 'strict' not found.
  212. Lua error in package.lua at line 80: module 'strict' not found.
  213. Lua error in package.lua at line 80: module 'strict' not found.
  214. Lua error in package.lua at line 80: module 'strict' not found.
  215. Lua error in package.lua at line 80: module 'strict' not found.
  216. Lua error in package.lua at line 80: module 'strict' not found.
  217. Lua error in package.lua at line 80: module 'strict' not found.
  218. Lua error in package.lua at line 80: module 'strict' not found.
  219. Lua error in package.lua at line 80: module 'strict' not found.
  220. Lua error in package.lua at line 80: module 'strict' not found.
  221. Lua error in package.lua at line 80: module 'strict' not found.
  222. Lua error in package.lua at line 80: module 'strict' not found.
  223. Lua error in package.lua at line 80: module 'strict' not found.
  224. Lua error in package.lua at line 80: module 'strict' not found.
  225. 225.0 225.1 225.2 225.3 Lua error in package.lua at line 80: module 'strict' not found.
  226. Lua error in package.lua at line 80: module 'strict' not found.
  227. Lua error in package.lua at line 80: module 'strict' not found.
  228. 228.0 228.1 Lua error in package.lua at line 80: module 'strict' not found.
  229. 229.0 229.1 Lua error in package.lua at line 80: module 'strict' not found.
  230. Lua error in package.lua at line 80: module 'strict' not found.
  231. Lua error in package.lua at line 80: module 'strict' not found.
  232. Lua error in package.lua at line 80: module 'strict' not found.
  233. Lua error in package.lua at line 80: module 'strict' not found.
  234. Lua error in package.lua at line 80: module 'strict' not found.
  235. Lua error in package.lua at line 80: module 'strict' not found.
  236. Lua error in package.lua at line 80: module 'strict' not found.
  237. 237.0 237.1 Lua error in package.lua at line 80: module 'strict' not found.
  238. Lua error in package.lua at line 80: module 'strict' not found.
  239. Lua error in package.lua at line 80: module 'strict' not found.
  240. Lua error in package.lua at line 80: module 'strict' not found.
  241. Lua error in package.lua at line 80: module 'strict' not found.
  242. Lua error in package.lua at line 80: module 'strict' not found.
  243. Lua error in package.lua at line 80: module 'strict' not found.
  244. Lua error in package.lua at line 80: module 'strict' not found.
  245. Lua error in package.lua at line 80: module 'strict' not found.
  246. Lua error in package.lua at line 80: module 'strict' not found.
  247. Lua error in package.lua at line 80: module 'strict' not found.
  248. Lua error in package.lua at line 80: module 'strict' not found.
  249. Lua error in package.lua at line 80: module 'strict' not found.
  250. Lua error in package.lua at line 80: module 'strict' not found.
  251. (in Korean) Wikisource link to 대한민국 선원법 (ROK Maritime Law concerning Sailors). Wikisource. 2008. 
  252. Lua error in package.lua at line 80: module 'strict' not found.
  253. Lua error in package.lua at line 80: module 'strict' not found.
  254. Lua error in package.lua at line 80: module 'strict' not found.
  255. Lua error in package.lua at line 80: module 'strict' not found.
  256. Lua error in package.lua at line 80: module 'strict' not found.
  257. Lua error in package.lua at line 80: module 'strict' not found.
  258. Lua error in package.lua at line 80: module 'strict' not found.
  259. Lua error in package.lua at line 80: module 'strict' not found.
  260. Lua error in package.lua at line 80: module 'strict' not found.
  261. Lua error in package.lua at line 80: module 'strict' not found.
  262. Lua error in package.lua at line 80: module 'strict' not found.
  263. Lua error in package.lua at line 80: module 'strict' not found.
  264. Lua error in package.lua at line 80: module 'strict' not found.
  265. Lua error in package.lua at line 80: module 'strict' not found.
  266. Lua error in package.lua at line 80: module 'strict' not found.
  267. Lua error in package.lua at line 80: module 'strict' not found.
  268. Lua error in package.lua at line 80: module 'strict' not found.
  269. Lua error in package.lua at line 80: module 'strict' not found.
  270. Lua error in package.lua at line 80: module 'strict' not found.
  271. Lua error in package.lua at line 80: module 'strict' not found.
  272. Lua error in package.lua at line 80: module 'strict' not found.
  273. Lua error in package.lua at line 80: module 'strict' not found.(subscription required)
  274. Lua error in package.lua at line 80: module 'strict' not found.
  275. Lua error in package.lua at line 80: module 'strict' not found.
  276. Lua error in package.lua at line 80: module 'strict' not found.
  277. Lua error in package.lua at line 80: module 'strict' not found.
  278. Lua error in package.lua at line 80: module 'strict' not found.
  279. 279.0 279.1 Lua error in package.lua at line 80: module 'strict' not found.
  280. Lua error in package.lua at line 80: module 'strict' not found.
  281. Lua error in package.lua at line 80: module 'strict' not found.
  282. Lua error in package.lua at line 80: module 'strict' not found.
  283. Lua error in package.lua at line 80: module 'strict' not found.
  284. Lua error in package.lua at line 80: module 'strict' not found.
  285. Lua error in package.lua at line 80: module 'strict' not found.
  286. Lua error in package.lua at line 80: module 'strict' not found.
  287. Lua error in package.lua at line 80: module 'strict' not found.
  288. Lua error in package.lua at line 80: module 'strict' not found.
  289. Lua error in package.lua at line 80: module 'strict' not found.
  290. Lua error in package.lua at line 80: module 'strict' not found.
  291. Lua error in package.lua at line 80: module 'strict' not found.
  292. Lua error in package.lua at line 80: module 'strict' not found.
  293. Lua error in package.lua at line 80: module 'strict' not found.
  294. Lua error in package.lua at line 80: module 'strict' not found.
  295. Lua error in package.lua at line 80: module 'strict' not found.
  296. Lua error in package.lua at line 80: module 'strict' not found.
  297. Lua error in package.lua at line 80: module 'strict' not found.
  298. Lua error in package.lua at line 80: module 'strict' not found.
  299. Lua error in package.lua at line 80: module 'strict' not found.
  300. Lua error in package.lua at line 80: module 'strict' not found.
  301. Lua error in package.lua at line 80: module 'strict' not found.
  302. Lua error in package.lua at line 80: module 'strict' not found.
  303. Not to be confused with the Korean Ministry of Security and Public Administration
  304. Lua error in package.lua at line 80: module 'strict' not found.
  305. Lua error in package.lua at line 80: module 'strict' not found.
  306. Lua error in package.lua at line 80: module 'strict' not found.
  307. Lua error in package.lua at line 80: module 'strict' not found.
  308. Lua error in package.lua at line 80: module 'strict' not found.
  309. Lua error in package.lua at line 80: module 'strict' not found.
  310. Lua error in package.lua at line 80: module 'strict' not found.
  311. Lua error in package.lua at line 80: module 'strict' not found.
  312. 312.0 312.1 Lua error in package.lua at line 80: module 'strict' not found.
  313. Lua error in package.lua at line 80: module 'strict' not found.
  314. Lua error in package.lua at line 80: module 'strict' not found.
  315. Lua error in package.lua at line 80: module 'strict' not found.
  316. Hyung-jin, Kim (20 Apr 2015) http://www.washingtonpost.com/world/asia_pacific/south-korea-ready-to-start-work-to-salvage-sunken-ferry/2015/04/20/2870cbae-e738-11e4-8581-633c536add4b_story.html The Washington Post. 20 April 2014. Retrieved 5 May 2014.

External links