Classification
- Incident Type: Other
- Severity: Medium
- Region: North Sea
Vessel Details
| Field | Value |
|---|---|
| Vessel Name | Wilco-B |
| Vessel Type | Tug |
| Flag State | |
| IMO Number | |
| Gross Tonnage | |
| LOA (m) | |
| Breadth (m) | |
| Power (kW) |
Incident Details
| Field | Value |
|---|---|
| Date | |
| Location | Eems near Eemshaven, Netherlands |
| Region | North Sea |
| Fatalities | |
| Injuries | 0 |
| Missing | |
| Direct Damage | Material damage reported; extent and final condition of the tug are not established. |
| Economic Damage |
Key facts
- The article, displayed as published on 27 July 2015, places the incident on the Eems near Eemshaven but gives no separate incident date.
- Wilco-B was attempting to pull a pontoon that had grounded on a shallow area toward deeper water.
- The article says the opposing current had not been considered and reports material damage, but gives no damage assessment or confirmed failure mechanism.
- The article states that there were no injuries; it does not give casualty counts for fatalities or missing persons.
Narrative
The available account is a short VK Magazine item accompanied by a video link. It says Wilco-B was working to pull a pontoon from a shallow area into deeper water on the Eems near Eemshaven. The article attributes the trouble to the opposing current not having been considered and says the tug sustained material damage, with no injuries reported. It does not describe the tow arrangement, the tug’s motions, the damage, any response or recovery, or the vessel’s final condition. The account therefore does not establish whether the tug grounded, capsized, girded, or suffered another towage-control problem. Its displayed date, 27 July 2015, is a publication date and cannot independently confirm the occurrence date.
Investigation
No official investigation or incident-specific findings were located in the bounded search. The cause and extent of damage remain unverified beyond the brief secondary account.
References
- VK Magazine, “Sleepboot in de problemen op de Eems” (displayed publication date: 27 July 2015; incident date not stated).