12.02.2016 Views

Third IMO Greenhouse Gas Study 2014

GHG3%20Executive%20Summary%20and%20Report

GHG3%20Executive%20Summary%20and%20Report

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

262 <strong>Third</strong> <strong>IMO</strong> GHG <strong>Study</strong> <strong>2014</strong><br />

Container ships 1<br />

Figure 39: Productivity of dry bulk carriers measured in thousand tonne-miles<br />

(five main dry bulks) per dwt (all bulk carriers), 1970–2013<br />

In the period 1999–2013, the productivity of container ships (see Figure 40) reached a maximum in 2005 with<br />

53,000 tonne-miles per dwt – the supply side could probably only satisfy the high demand by sailing at high<br />

speeds and at high cargo load factors. The order placed for container ships in these years and the following<br />

economic downturn can explain the decrease of the productivity until 2009. The 2012 productivity amounts<br />

to 39,000 tonne-miles per dwt and is higher than the 2009 productivity of 37,000 tonne-miles per dwt.<br />

Liquefied gas ships<br />

In the period 1999–2013, the productivity of the liquefied gas tankers (see Figure 40) fluctuated between<br />

22,000 and 30,000 tonne-miles per dwt and was thus less volatile than the productivity of the other ship<br />

types. In 2012, the productivity amounted to 24,000 tonne-miles per dwt.<br />

1 The productivity of container ships is determined on the basis of tonne-miles data as published by UNCTAD in the Review of<br />

Maritime Transport. If the tonne-miles data has been determined by applying a default container weight factor to TEU-miles data,<br />

which is our understanding of the UNCTAD data, then it can be concluded that the development of the container ship tonne-miles as<br />

used in the emissions projection model is the same as the development in terms of TEU-miles.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!