Solvent Extraction of Copper from Sulfate Leach Liquor of Chalcopyrite Concentrate: Mitigation Strategies for Iron Coextraction

No Thumbnail Available

Date

2025

Journal Title

Journal ISSN

Volume Title

Publisher

Wiley

Open Access Color

GOLD

Green Open Access

No

OpenAIRE Downloads

OpenAIRE Views

Publicly Funded

No
Impulse
Average
Influence
Average
Popularity
Average

Research Projects

Journal Issue

Abstract

In this study, solvent extraction of copper (Cu) from sulfate leach liquor of chalcopyrite concentrate was investigated using LIX 984N as the extractant and kerosene as the diluent. The effects of pH (1-4.5), organic-to-aqueous phase ratio (O/A, 1/3-3/1), extractant concentration (3%-9% v/v), diluent type (kerosene, benzene, and hexane), and temperature (25 degrees C-55 degrees C) on the extraction efficiency were systematically evaluated. Stripping experiments were also carried out using sulfuric acid at different concentrations (0.75-3 M) and agitation rates (200-600 rpm). The results revealed that up to 98.1% of copper could be extracted at pH 4.5, O/A = 1, 6% (v/v) LIX 984N, and 25 degrees C when hexane was used as the diluent. However, a significant amount of iron (20%-28%) was also coextracted into the organic phase under similar conditions, which poses challenges for downstream electrowinning. Complete stripping of copper and iron was achieved at 1.5 M H2SO4 with the agitation of 500 rpm. These findings highlight the need for a preliminary iron removal step prior to solvent extraction to ensure selective copper recovery.

Description

Keywords

Copper, Extraction Efficiency, LIX 984N, Solvent Extraction

Turkish CoHE Thesis Center URL

Fields of Science

Citation

WoS Q

Q3

Scopus Q

Q2
OpenCitations Logo
OpenCitations Citation Count
N/A

Source

International Journal of Chemical Engineering

Volume

2025

Issue

1

Start Page

End Page

PlumX Metrics
Citations

Scopus : 0

Google Scholar Logo
Google Scholar™

Sustainable Development Goals

SDG data could not be loaded because of an error. Please refresh the page or try again later.