Search This Blog

Showing posts with label monsoon. Show all posts
Showing posts with label monsoon. Show all posts

Saturday, 6 August 2011

the mystery of the RAK Carrier - where was she for 40 days?




The mystery of the RAK Carrier: Where was she for the past 40 days?
August 04, 2011 03:49 PM
Veeresh Malik

At 8-9 knots, sailing time from Singapore to Mumbai would not exceed 10 days. The RAK Carrier, now sinking off Mumbai, took 40. Where was she in between?

Time was not too long ago, a ship would go adrift or get stranded in and around Mumbai Port about once every two years, and would then become the focus of all discussion at the Seaman's Club. Now it appears to be a weekly affair, like the "specials" on sale in the Irani Hotel next door, and everybody knows that the special is simply what was not moving so had to be flogged.

The RAK Carrier, an Indonesian flag bulk carrier, is one more example.

About 26 years old, with a history as long as that of any history-sheeter, she sailed out of Singapore on or around the 2nd of May 2011, ostensibly towards Indonesia to load coal for Dahej in Gujarat. She then reappeared off Singapore on the 20th of June 2011, ostensibly loaded, and then sat patiently outside Singapore till the 24th of June. She then sailed out towards India through the Malacca Straits, making good about 8-9 knots, giving an ETA (expected time of arrival) Dahej of 7th of July 2011.

So far so good, but then suddenly on the midnight of 24/25 June 2011, all position reporting seems to have stopped from her AIS (Automatic Identification Signal), including most surprisingly no reports when passing Colombo or making landfall off India, until she arrived off the Port of Mumbai almost a month behind schedule. Down by head, and certainly looking like she was about to go under, conveniently near the only port in India where rescue would not be too much of a problem.

For all we know, the Master decided to go on a short tour of the Indian Ocean through most of the month of July 2011, while the cargo receivers in Dahej waited patiently for their coal. Or something happened to the cargo en route, and after that, it became a very brilliant insurance claim. But why does a ship take almost 40 days to come from Singapore to Mumbai, is the question which people should be asking, and also doing a quick check on what's really in those cargo-holds.

Incidentally, the value of the cargo would have been many times the value of the ship, especially in these depressed days. And the coal would find ready buyers anywhere in the world. But that's unfair to the seafarers who probably fought bad monsoon seas before making it to off Mumbai, too.

However, it is not unknown for ships to go elsewhere, offload cargo, fill holds with ballast water, and then go under. Shipping records are full of such cases.

For example, in the days when trade with a particular African country was "banned", ships would often load oil for, say, West Europe. Along the way, the cargo would be quietly unloaded at a port in that African country, and then the ship and ship-owners would go through all sorts of manipulations to close the voyage. In one glorious case, when a particular ship—on her last legs anyway—was going to be scuttled, the ship sent out a sinking signal and asked for help, and the rescuers found everybody dressed in formals with their suitcases neatly packed.

We are not saying that the RAK Carrier is an elaborate insurance scam. Far from it.

We have said it before, and we say it again—it requires a very simple notice to mariners issued by the DG Shipping in Mumbai addressed to all ships globally when they come anywhere near Indian waters—especially those calling Indian ports. All ships coming into Indian territorial waters must establish identity and purposes. All overage ships (those over 15 years old as per marine conventions) must in addition also provide full details of any and every possible issue including cargo, insurance cover, class and adherence to every possible aspect that makes her seaworthy.

Why would the DG Shipping not do it? This is unknown, but in their 'PAVITra WISDOM', maybe they will do it now?

Information Sources:

1) Information on RAK CARRIER movements sourced from:
 http://www.marinetraffic.com/ais/datasheet.aspx?datasource=ITINERARIES&MMSI=351810000

2) Information on possible insurance issues—sourced from the grapevine.

(PS: In addition, I just saw some TV clips of the sailors from this ship. They seem to be interestingly very calm and collected. In addition, it appears as though they had the time to save and get along stuff like their laptops and stereos as well as all their documents. This is something strange, the Indian authorities need to hold these seafarers and question them to find out what happened).

___

Originally published at MoneyLife

Saturday, 13 November 2010

Bulk Iron Ore Fines Loading in India, by Capt. T. Rajkumar, Master Mariner.

(Kind courtesy Capt. T. Rajkumar)


TOPIC: Bulk Iron Ore Fines Loading in India.
Course objectives – Safety & prevention of accidents being the main criteria. 
Ref  IMO Bulk Code.
·        Review situation in India.
·        Application of the BC Code (IMO)
Introducing the topic---
·         In the year, 2002 Iron  Ore “Fines” was sought for by Buyers abroad --to replace “Lumps” and the GOI had approved. This was a major change in iron ore cargo specs from the earlier Lumps to Ore Fines in Exports. Ore Lumps of larger size does not usually become a slurry if wet as the water drains out.
·         With Ore Prices just soaring and China Buying  the all and sundry in the private sector came into the fray.... to Mine & Sell & Ship Out.
·         Exports hit an an all time high but, Loading norms of the IMO- BC Code was not understood or heeded and the trade took many aspects for granted.
·         Also many ports that used to close in Monsoon season just continued all time.
·         With increasing demand for steel, the export of Bulk Ore Fines steadily increased since 2002.  With boom time, many older ships were chartered at lowest freights and soon shoddy operations took its toll. This eventually gave rise to  numerous Bulk Carrier casualties and especially the case of  m.v. Asian Forest, sunk outside at Mangalore and m.v. Black Rose sunk off Paradip drew attention. Refer List of Casualties on last page. This finally got  the attention of the Media- !! -then the trade and industry took notice..
We need to now ask a few queries.
·         After the 12 nos. casualties  reported  and follow instructions  by the  DG, MS Notice,  IMO 2009 Revised, P&I  Club Advice to members & Reports from the Shipp Enquiry Committee--                  What is the position today ?
·         The  awareness and application of the IMO code on loading norms , much less it’s usage is still very poor. The scene all over India is just one of total disregard with compartmentalised working.
·         Shippers need to address the instructions listed in IMO BC Code.
Q: Who will control this ?
·         Refer current practices in the Iron Ore trade and -it is a shocker. Ore Fines is exported all the year round and no stoppage in Monsoon season.
·         Ore is mined and crushed at Mines from Bihar to Jharkhand/AP-Karnataka  and transported in open trucks /rakes to shipment ports. During the monsoon rains the ore piles remain  in the open yards and the moisture content exceeds limits . With heavy rains, pools of stagnant water are seen water but many Shippers wish to continue  loaded Wet Ore.
·         Refer current practices in the Iron Ore trade and Media Reports-it is a shocker. Fines is exported all the time and no stoppage in Monsoon season. Ore is mined and Crushed at Mines from Bihar /Jharkhand/AP-Karnataka  and then  transported in open trucks /rakes to shipment ports. During the monsoon rains they remain  in the open yards and the moisture content exceeds limits . With heavy rains, pools of stagnant water are seen water. This has been photographed and even reported with a caption "Ore in a lake of water!!
·         However despite all circulars and guidelines many Shippers wish to continue  loaded Wet Ore. How does the Ships Officer - Owners and relate with Shippers and Port Authority here on such matters .
·          If a Prudent Master stops loading-- will his vessel be shifted to Outer Roads. (It appears that Ports can be quite unreasonable to achieve a fast turnround).
·         In monsoon rains and cargo soaked on open stacks results in - “Ore Fines getting soaking wet. Thus M- TMT does increase beyond permissible limits  ...will turn into a Slurry and this is unsafe for loading for sea passage.       The Mangalore casualty was seen as a direct result of this as Reports will indicate.
·         The excuse given by Shippers and Assayers to the Shipping Enquiry Committee -Quote “Unable to assess M, FMP of large Bulk Quantity” unquote. This is quite an absurd statement.
·         Loading even in heavy Rains continues today despite various guidelines.
·         The problem really begins here.
·         Who will Monitor this?
·         What Loading supervision and control do we have ?
·         What is the role of Port Authority .
OPEN HOUSE –
Addressing key factors:
What can ships personnel do ?
·         How is the   Ship’s Officer managing the loading ?
·     Does the ship’s officer  inspect cargo  stack on jetty and do the ‘Can Test’.
·         Does the Ship get a  correct   quality Certificate from the Shipper’s Assayer ?
·         P&I Intervention – What is the experience on this assistance on application of the BC Guidelines ?
LOOKING AT SOLUTIONS.-Start at Fixture time with Shippers and Load Port—seems like a good place to begin but this is entirely a Ship owners decision
·         Supervise Loading -don't leave to chance.
·         Be totally informed and communicate.
·         Have Sampling & Testing organized  standard, calibrated equipment please-
·         Trained and competent samplers & analysis.
·         Inform Pre-shipment  specs. to Owner & Master in advance by email.
LET US NOW ADDRESS COPING SKILLS --
1) The 2009 edition of the IMO Bulk Code is really  an excellent doc; Possibly the best edition seen till date and is most comprehensive.

The first 44 pages of instructions itself tells it all- .So also, DG circular on ore loading.
Q:  Have Shippers ever read this or much less used it. 

2) In all fairness, the problem is more in Monsoon conditions with soaking wet ores. Then we also see the lack of regard for Trimming & levelling in stow.. the Shipper is quite oblivious to all this and rests in his "Angle of Repose!! (Sorry about that dig, but it is a fact).

3) The situation in 2007 & the casualties was mainly with old ships and poor management in all aspects of PSI- Load -stow-trim  sail-  fast turnround go.. go--.
This problem mainly arose due a total disregard for the IMO- Bulk Code norms and too much of commercial pressures and this  is quite evident. No doubt 2007 was a bad year-see casualty statistics.

4) The Port Authority's role in this seems to be a limited one, despite what ever legal instruments may exist. The Major Ports Act itself is nearly a 'century old' and  Ports  only respond as Custodian or bailee of cargo etc-so no real proactive role is seen on Cargo Loading matters. The Ports main priority being the turnround and Qty-Output/ shipped mainly.

5) With so many new ports and "inexperienced” personnel, mostly untrained in BC Code the "awareness’ to BC code  is  a key to correcting the situation. Regrettably, we also have today much confusion caused by some dubious Operators  who have not read the directives on loading of Iron ore fines. Then some Operators inc Shippers just do not cooperate and disregard all risk control guidelines.. 

The paradox is whilst all loading directives and control is about due diligence being exercised in the interest of safety, the fact is that few shippers cooperate.




ADDRESSING THE MATTER
Finally, a Preshipment inspection procedure was laid out by end of 2009- and has slowly gained acceptance.i.e. even before loading commenced as the Port Rules do not permit  "Wet Ore" once loaded in holds to be discharged, resulting in an impasse. P&I support and loss prevention measures came to assist the ship master from the arrival of Cargo, with sampling and testing ( PSI ) to loading and final topping when sought by Owners.

REFERENCES:  
IMO, BC Code 2009.
DG Shipping Circulars & MS Notice
P&I Club Circulars
Apart from the above, the National Shipping Committee also met. The GOI Circular from Delhi of May 28, 2010 "guideline" was issued.

Finally in 2010 we seem to have arrived at a reasonable consensus to Monitor the work with P&I support as follows:

Ship & cargo survey attendance to include:

1)  To inspect the cargo at shippers stock yard before arrival of the vessel and to carry out joint sampling with shippers representative / surveyor.

2)  To carryout analysis of one composite sample for Total Moisture, Flow Moisture Point & Transportable Moisture Limit.

3)  The test results of TML to be made available to the Master of the Vessel prior to loading for reference.

4)  To attend the vessel on arrival and carryout monitoring survey of the cargo to be loaded.

5) To Carryout Regular CAN Test and Instant Moisture Test of the sample at hook point during loading.

6)  If a parcel of cargo is suspected to be wet during loading and bringing it to the notice of the concerned. 
7) Surveyor will allow such cargo to be loaded where moisture content is found to be less than TML.  If moisture content is more than TML then please recommend Master to reject such cargo. 
8) OPTIONAL- To carry out initial & final Draft survey and assist Master in stowing and trimming of cargo after loading.

SUMMARISING: 
Ships condition apart--bulk loading can be well organised and managed if basic norms are followed  I do believe this can be well managed with Cooperation from all, plus a better knowledge of the BC Code in loading and esp. due respect by shippers for the specifics.

As a former Surveyor to the mechanical ore Terminal at Chennai (commissioned in 1978 ) operated by the Port & MMTC- we had good results and work progressed with due cooperation from all with successful outcomes.

Time changes many things with expansion and costings and degeneration often sets in when unchecked. This matter was earlier taken up for Masters Revalidation Course. It was  also presented at the Nautical Inst. Chennai Chapter seminar by me this year.

All P&I Clubs have published papers on this matter and it is just a matter of taking this procedure across to Trade –i.e. Shippers and all connected inc. the Port Authority,

There is a serious need to build better Awareness to the BC Code within the shore support sector attending bulk cargoes. 


NOTE: In the 1987 -1992 period Bulker Casualties  were reported all across the world and esp at high loading terminals. In the1990s when the Master's Revalidation course was set on stream "Bulk Carrier disasters" was a key subject- Senior mariners will recall the case study  of the m.v. Derbyshire. The Nautical Institute and later the Classification societies had done much research on Bulkers and provided valuable data. Sadly, all is now archived in vaults. History repeats is a truism. A few problems had also surfaced in India--but did not lead to a sinking. Generally it was Improper loading/overloading, heeled and with torsional deflection - inability to  close hatch covers with disregard for trimming


RECENT CASUALTY STATISTICS

No
Vessel
Load Port
Sailing
Incident
Date
+
1.
m.v. WEN  QIAO
India
..08.07
Capsized and sank at North Korea.
17.9.07
1
2.
m.v.CHANG LE MEN
Mangalore
05.09.07
Beached with 35 deg list near Mangalore
6.9.07
-
3.
m.v. DISCOVERY II
Haldia
18.9.07
Developed severe list and entered Port of Vizag for disch.
21.9.07
-
4.
m.v.VIEN DONG 2
Haldia
26.9.07
Beached with 20 deg. List off Car –Nicabar Islands
30.9.07
-
5.
m.v. HENG TAI
Haldia
27.9.07
Capsized and sank at Andaman Sea – West of Bangkok
2.10.07
2
6.
m.v. ASIAN FOREST
Mangalore
17.7.09
Sank off Mangalore
18.7.09
-
7.
m.v. HODASCO 15
Calcutta
…8.09
Capsized and sank off Malaysia
30.8.09
-
8.
m.v. BLACK ROSE
Paradip
..09.09
Sank shortly after departing
9.9.09
1
9.
m.v. VINALINES MIGHTY
Paradip
..09.09
Serious list short after sailing and returned to load port.
10.9.09
-