Abstract

Ship-source greenhouse gas (GHG) emissions could increase by up to 250% by 2050 from their 2012 levels, owing to increasing global freight volumes. Binding international legal agreements to regulate GHGs, however, are lacking as technical solutions remain expensive, and crucial industrial support is absent. In 2003, the International Maritime Organization adopted Resolution A.963 (23) to regulate shipping CO2 emissions via technical, operational, and market-based routes. However, progress has been slow and uncertain; there is no concrete emission reduction target or definitive action plan. Yet, a full-fledged roadmap may not even emerge until 2023. In this policy analysis, we revisit the progress of technical, operational, and market-based routes and the associated controversies. We argue that 1) a performance-based index, though good-intentioned, has loopholes affecting meaningful CO2 emission reductions driven by technical advancements; 2) using slow steaming to cut energy consumption stands out among all operational solutions thanks to its immediate and obvious results, but with the already slow speed in practice, this single source has limited emission reduction potential; 3) without a technology-savvy shipping industry, a market-based approach is essentially needed to address the environmental impact. To give shipping a 50:50 chance for contributing fairly and proportionately to keep global warming below 2°C, deep emission reductions should occur soon.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.