Economic and Environmental Perspectives of End-of-Life Ship Management
Document Type
Article
Publication Date
2-2016
Publication Source
Resources, Conservation, and Recycling
Abstract
The economic feasibility and environmental impacts of three examples of end-of-life management options were analyzed with a cost–benefit analysis and an environmental life cycle assessment. The economics of ship recycling methods depend on various parameters such as the market price of reclaimed materials, ship purchase price, environmental and work safety regulation fees, labor costs, and overhead costs. Standard recycling methods are typically used in the U.S., EU, China, and Turkey. The example of recycling the USS Forrestal, showed that standard ship recycling methods can be profitable. Standard ship recycling methods must follow strict regulations, and therefore, can only release negligible amounts of hazardous substances into the environment. In addition, the reclaimed materials from standard ship recycling methods provide various life cycle environmental benefits. Substandard recycling methods, such as beaching, used in southern Asia countries, allow shipyard owners to outbid standard method recycling companies and remain profitable due to a lack of enforced environmental regulations. The non-compliance with environmental regulations, allows these substandard methods to release a large amount of harmful substances into the environment. The reefing option is neither economically viable nor completely safe for the environment, but it could improve the local economy and underwater habitats for local sea life.
Inclusive pages
82-91
ISBN/ISSN
0921-3449
Copyright
Copyright © 2015, Elsevier
Publisher
Elsevier
Volume
107
Peer Reviewed
yes
eCommons Citation
Choi, Jun-Ki; Kelley, Daniel; Murphy, Sean; and Thangamani, Dillip, "Economic and Environmental Perspectives of End-of-Life Ship Management" (2016). Mechanical and Aerospace Engineering Faculty Publications. 209.
https://ecommons.udayton.edu/mee_fac_pub/209
COinS
Comments
Permission documentation is on file.