1C1K

BACTERIOPHAGE T4 GENE 59 HELICASE ASSEMBLY PROTEIN


Experimental Data Snapshot

  • Method: X-RAY DIFFRACTION
  • Resolution: 1.45 Å
  • R-Value Free: 0.253 
  • R-Value Work: 0.200 

wwPDB Validation 3D Report Full Report


This is version 1.2 of the entry. See complete history

Literature

Bacteriophage T4 gene 59 helicase assembly protein binds replication fork DNA. The 1.45 A resolution crystal structure reveals a novel alpha-helical two-domain fold.

Mueser, T.C.Jones, C.E.Nossal, N.G.Hyde, C.C.

(2000) J.Mol.Biol. 296: 597-613

  • DOI: 10.1006/jmbi.1999.3438

  • PubMed Abstract: 
  • The bacteriophage T4 gene 59 helicase assembly protein is required for recombination-dependent DNA replication, which is the predominant mode of DNA replication in the late stage of T4 infection. T4 gene 59 helicase assembly protein accelerates the l ...

    The bacteriophage T4 gene 59 helicase assembly protein is required for recombination-dependent DNA replication, which is the predominant mode of DNA replication in the late stage of T4 infection. T4 gene 59 helicase assembly protein accelerates the loading of the T4 gene 41 helicase during DNA synthesis by the T4 replication system in vitro. T4 gene 59 helicase assembly protein binds to both T4 gene 41 helicase and T4 gene 32 single-stranded DNA binding protein, and to single and double-stranded DNA. We show here that T4 gene 59 helicase assembly protein binds most tightly to fork DNA substrates, with either single or almost entirely double-stranded arms. Our studies suggest that the helicase assembly protein is responsible for loading T4 gene 41 helicase specifically at replication forks, and that its binding sites for each arm must hold more than six, but not more than 12 nucleotides. The 1.45 A resolution crystal structure of the full-length 217-residue monomeric T4 gene 59 helicase assembly protein reveals a novel alpha-helical bundle fold with two domains of similar size. Surface residues are predominantly basic (pI 9.37) with clusters of acidic residues but exposed hydrophobic residues suggest sites for potential contact with DNA and with other protein molecules. The N-terminal domain has structural similarity to the double-stranded DNA binding domain of rat HMG1A. We propose a speculative model of how the T4 gene 59 helicase assembly protein might bind to fork DNA based on the similarity to HMG1, the location of the basic and hydrophobic regions, and the site size of the fork arms needed for tight fork DNA binding. The fork-binding model suggests putative binding sites for the T4 gene 32 single-stranded DNA binding protein and for the hexameric T4 gene 41 helicase assembly.


    Organizational Affiliation

    Laboratory of Structural Biology Research, Bldg. 6 Room B2-34A, National Institute of Arthritis and Musculoskeletal and Skin Diseases National Institutes of Health, Bethesda, MD, 20892-2717, USA. tcm@neon.niams.nih.gov




Macromolecules

Find similar proteins by: Sequence  |  Structure

Entity ID: 1
MoleculeChainsSequence LengthOrganismDetails
BPT4 GENE 59 HELICASE ASSEMBLY PROTEIN
A
217Enterobacteria phage T4Gene Names: 59
Find proteins for P13342 (Enterobacteria phage T4)
Go to UniProtKB:  P13342
Small Molecules
Ligands 2 Unique
IDChainsName / Formula / InChI Key2D Diagram3D Interactions
CL
Query on CL

Download SDF File 
Download CCD File 
A
CHLORIDE ION
Cl
VEXZGXHMUGYJMC-UHFFFAOYSA-M
 Ligand Interaction
IR
Query on IR

Download SDF File 
Download CCD File 
A
IRIDIUM ION
Ir
MOHYGSBMXIJZBJ-UHFFFAOYSA-N
 Ligand Interaction
Experimental Data & Validation

Experimental Data

  • Method: X-RAY DIFFRACTION
  • Resolution: 1.45 Å
  • R-Value Free: 0.253 
  • R-Value Work: 0.200 
  • Space Group: P 21 21 21
Unit Cell:
Length (Å)Angle (°)
a = 31.865α = 90.00
b = 65.882β = 90.00
c = 108.166γ = 90.00
Software Package:
Software NamePurpose
PHASESphasing
DENZOdata reduction
SCALEPACKdata scaling
X-PLORrefinement

Structure Validation

View Full Validation Report or Ramachandran Plots



Entry History 

Deposition Data

Revision History 

  • Version 1.0: 2000-02-16
    Type: Initial release
  • Version 1.1: 2008-04-27
    Type: Version format compliance
  • Version 1.2: 2011-07-13
    Type: Version format compliance