Classification
- Incident Type: Security Incident / Fire
- Severity: High
- Vessel Type: Container
Vessel Details
| Field | Value |
|---|---|
| Vessel Name | Safeen Prestige |
| Vessel Type | Container |
| Flag State | Malta [MT] |
| IMO Number | 9593517 |
| Gross Tonnage | 18252 |
| LOA (m) | 175.43 |
| Breadth (m) | 27.41 |
| Year Built | 2013 |
| Crew Size | 24 |
Identity and crew complement follow IFC-IOR. Dimensions, tonnage and build year are supporting database particulars. (IFC-IOR, p. 22; VesselFinder)
Incident Details
| Field | Value |
|---|---|
| Date | 2026-03-04 |
| Location | Strait of Hormuz, approximately 2 NM north of Salib, Oman |
| Region | Persian Gulf |
| Fatalities | |
| Injuries | 0 |
| Missing | |
| Vessels Lost | 1 |
| Direct Damage | |
| Economic Damage |
IMO explicitly records no injuries. The later sinking position differs from the initial attack location. (IMO; Lloyd's List; JMIC, p. 6)
Key facts
- IFC-IOR identified the ship by IMO 9593517 and reported two projectile impacts causing an engine-room fire. (IFC-IOR, p. 22)
- All 24 crew were rescued and recorded as safe. (IFC-IOR, p. 22)
- Named contemporary reporting identifies the rescuing service as Oman's Royal Navy. (The Maritime Executive)
- JMIC reported attacks on 4 and 18 March, followed by sinking by 2 April. (JMIC, p. 6)
- IMO records the vessel as sunk, with an oil slick detected and no injuries. (IMO)
Narrative
Safeen Prestige was transiting eastbound about two nautical miles north of Salib when it was hit above the waterline. IFC-IOR reported two projectiles, an engine-room fire and rescue of all 24 crew. Contemporary reporting identified Oman's Royal Navy as the rescuing service and matched the ship's name, Malta flag, date and location. (Lloyd's List; IFC-IOR, p. 22; The Maritime Executive)
JMIC's 2 April update reported a second attack on 18 March and a wreck 6.5 nautical miles northeast of Ra's Makhbūq, Oman, in approximately 120 metres of water. IMO subsequently listed the ship as sunk and noted an oil slick. These records do not determine whether the sinking resulted from the second attack, accumulated damage or another mechanism. They do not establish the attacker's identity or a confirmed weapon type. (JMIC, p. 6; IMO)
Sequence of events
| Date/time | Event |
|---|---|
| 2026-03-04 | Projectile impacts caused an engine-room fire; the crew abandoned and all 24 were rescued. |
| 2026-03-18 | A second attack was later reported by JMIC. |
| 2026-04-02 | JMIC's update reported the ship sunk northeast of Ra's Makhbūq. |
Sources: IFC-IOR, p. 22 and JMIC, p. 6. The update establishes sinking by 2 April, rather than an exact sinking time.
Contributing factors
| Factor | Evidence status | Description |
|---|---|---|
| Projectile impacts | Reported | IFC-IOR recorded two projectile impacts followed by an engine-room fire. This is security reporting, not a final technical investigation finding. |
Source: IFC-IOR weekly update, p. 22.
Investigation
The available official records document rescue, security incidents and the later wreck. They do not provide a final accident-investigation finding. The attacker, exact weapon, detailed damage progression and quantified loss remain unresolved. Rescue-tug casualties from the separate Mussafah 2 incident are not included in this ship's casualty totals. (IFC-IOR; JMIC; IMO)
References
- IFC-IOR weekly maritime security update, 26 February–4 March 2026, p. 22
- JMIC Update 027: 2 April sinking update, p. 6
- IMO: Middle East highlighted confirmed incidents
- Lloyd's List: AD Ports Group-controlled feeder boxship hit by projectile
- The Maritime Executive: Oman rescues crew of UAE containership