It was the M.V. Indus Fortune , a cargo vessel three days overdue.
He flipped open a fresh page. If he filed this report correctly, the terminal manager would authorize two tugs instead of one, and clear the adjacent berth for safety. But if he made a single error in the coordinates or wind allowance, the vessel could scrape the fender system—or worse, collide with the fuel pier.
Here’s a short narrative-style story built around the title Title: The Citpl Vessel Berthing Report Citpl Vessel Berthing Report
The rain came down in sheets, drumming against the corrugated roof of the harbor master’s shack. Inside, old Manish Rathore adjusted his spectacles and stared at the radar screen. A single blip—large, slow, deliberate—inched toward the approach channel.
CITPL (Coastal Integrated Terminal & Port Logistics) ran a tight operation. Delays meant demurrage fees, unhappy clients, and a cascade of paperwork that could bury a man alive. But Manish had been a harbor pilot for twenty-three years before a bad knee grounded him behind a desk. He knew the sea’s rhythms better than the algorithms in the new berthing software. It was the M
Vessel: M.V. Indus Fortune IMO: 9472031 LOA: 189m Draft: 10.2m Berthing time (scheduled): 21:00 Berthing time (actual): 23:10 (estimated) Tug deployment: Two ASD tugs requested – approved. Weather: NE wind 22 knots, visibility 3 km, moderate chop Incident log: Bow thruster malfunction. Awaiting tug escort.
Date: October 12 Time: 22:47 hours Location: CITPL Marine Terminal, Berth Delta-7 If he filed this report correctly, the terminal
“Control to Indus Fortune , report your ETA to Berth Delta-7,” Manish spoke into the radio.