Format

Send to:

Choose Destination
See comment in PubMed Commons below
Appl Environ Microbiol. 2001 Dec;67(12):5497-505.

Identification of a novel metabolite in the degradation of pyrene by Mycobacterium sp. strain AP1: actions of the isolate on two- and three-ring polycyclic aromatic hydrocarbons.

Author information

  • 1Department of Microbiology, University of Barcelona, Barcelona, Spain.

Abstract

Mycobacterium sp. strain AP1 grew with pyrene as a sole source of carbon and energy. The identification of metabolites accumulating during growth suggests that this strain initiates its attack on pyrene by either monooxygenation or dioxygenation at its C-4, C-5 positions to give trans- or cis-4,5-dihydroxy-4,5-dihydropyrene, respectively. Dehydrogenation of the latter, ortho cleavage of the resulting diol to form phenanthrene 4,5-dicarboxylic acid, and subsequent decarboxylation to phenanthrene 4-carboxylic acid lead to degradation of the phenanthrene 4-carboxylic acid via phthalate. A novel metabolite identified as 6,6'-dihydroxy-2,2'-biphenyl dicarboxylic acid demonstrates a new branch in the pathway that involves the cleavage of both central rings of pyrene. In addition to pyrene, strain AP1 utilized hexadecane, phenanthrene, and fluoranthene for growth. Pyrene-grown cells oxidized the methylenic groups of fluorene and acenaphthene and catalyzed the dihydroxylation and ortho cleavage of one of the rings of naphthalene and phenanthrene to give 2-carboxycinnamic and diphenic acids, respectively. The catabolic versatility of strain AP1 and its use of ortho cleavage mechanisms during the degradation of polycyclic aromatic hydrocarbons (PAHs) give new insight into the role that pyrene-degrading bacterial strains may play in the environmental fate of PAH mixtures.

PMID:
11722898
[PubMed - indexed for MEDLINE]
PMCID:
PMC93335
Free PMC Article
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for HighWire Icon for PubMed Central
    Loading ...
    Write to the Help Desk