SEOUL — Two crew members were killed after a fire erupted aboard a large oil products tanker in waters off Incheon, South Korea, late Thursday night, triggering a major Coast Guard rescue and firefighting operation.
The blaze broke out at around 10:38 p.m. on Aug. 27 aboard a 7,333-ton oil products carrier operating approximately 7.4 kilometers north of Jawoldo Island in Ongjin County, Incheon, according to South Korean authorities and Yonhap News Agency.
There were 18 crew members aboard the vessel, including 11 South Koreans and seven foreign nationals. Sixteen people were rescued, while two male crew members—one in his 60s and another in his 20s—were found in cardiac arrest inside the engine room. They were taken toward a nearby port but later died.
Fire brought under control after hours of firefighting
The Korea Coast Guard launched an extensive response after receiving the emergency report.
SBS News reported that Coast Guard and firefighting authorities deployed multiple vessels to the scene as crews battled the flames aboard the petroleum-product carrier. The remaining 16 crew members were rescued and were reported to be in stable condition.
The fire was eventually extinguished at approximately 4 a.m. Friday, meaning the emergency response continued for several hours after the initial outbreak. Yonhap reported that the fire had been extinguished by that time, while Korean media reported that authorities used a large number of vessels and other emergency resources during the operation.
Authorities focus on the engine room
One of the most important details emerging from the investigation is where the fire appears to have started.
Reuters, citing Yonhap, reported that authorities suspect the blaze originated in the engine room. Importantly, the fire was not reported to have spread to the vessel’s oil cargo tanks, reducing the immediate risk of a much larger cargo-related fire.
The two victims were also found in the engine room, according to Yonhap and Reuters.
The exact cause of the fire, however, remains under investigation.
Authorities are expected to examine the vessel’s engine systems, determine what triggered the blaze and assess the extent of damage before reaching a definitive conclusion.
No report of the oil cargo catching fire
Despite the vessel carrying oil products, available reports indicate that the blaze did not spread to the ship’s oil cargo tanks. This distinction is significant because a fire involving the cargo tanks could have created a substantially greater maritime emergency.
At this stage, reports have not indicated a major oil spill connected to the incident.
Investigation now underway
The deadly incident has prompted authorities to begin a formal investigation into the circumstances surrounding the fire.
The Coast Guard is expected to examine the condition of the vessel, the engine room and other relevant systems to establish how the fire began and why the two crew members were unable to escape.
For now, authorities have confirmed the human toll: two crew members dead and 16 rescued.
The incident also highlights the risks faced by crews working aboard petroleum-product carriers, where a fire in an engine compartment can quickly become a serious maritime emergency even when the cargo itself is not directly affected.
Authorities have yet to release a final determination on the cause of the fire or the full extent of the vessel’s damage.
What is confirmed so far
| Detail | Confirmed information |
|---|---|
| Location | Waters off Jawoldo Island, Incheon |
| Date | Aug. 27, 2026 |
| Time of fire | About 10:38–10:40 p.m. |
| Vessel | 7,333-ton oil products carrier |
| Crew | 18 |
| Rescued | 16 |
| Fatalities | 2 |
| Victims | Men in their 60s and 20s |
| Suspected origin | Engine room |
| Oil cargo tanks | Fire reportedly did not spread to them |
| Fire extinguished | Around 4 a.m., Aug. 28 |
| Investigation | Ongoing |
The above details are cross-checked against CNA/Reuters, Yonhap and SBS News, with Korean reporting providing additional information on the location, crew composition and emergency response.
Leave a Reply