Basic Search  |  Summaries  |  Advanced Search

Violation Tracker Individual Record

Company: FirstEnergy Nuclear Operating Company
Current Parent Company: FirstEnergy
Parent at the Time of the Penalty Announcement:  subscribe to see this data field
Penalty: $5,450,000
Year: 2005
Date: April 21, 2005
Offense Group: safety-related offenses
Primary Offense: nuclear safety violation
Violation Description: On April 21, 2005, a Notice of Violation and Proposed Imposition of Civil Penalties in the amount of $5,450,000 was issued for multiple violations (some willful) related to the significant degradation of the reactor pressure vessel head identified in February and March 2002. The significant violations included, (1) operation with reactor coolant system pressure boundary leakage (associated with a Red SDP finding, $5,000,000), (2) failure to provide complete and accurate information (Severity Level I, $110,000), (3) failure to promptly identify and correct a significant condition adverse to quality (Severity Level II, $110,000), (4) failure to implement procedures (Severity Level II, $110,000), (5) failure to provide complete and accurate information (Severity Level I, $120,000), (6) failure to promptly identify and correct a significant condition adverse to quality (associated with a Red SDP finding), (7) failure to implement procedures (associated with a Red SDP finding), and (8) failure to provide complete and accurate information (Severity Level III).
Level of Government: federal
Action Type: agency action
Agency: Nuclear Regulatory Commission
Civil or Criminal Case: civil
Facility State: Ohio
HQ Country of Current Parent: USA
HQ State of Current Parent: Ohio
Ownership Structure of Current Parent: publicly traded
Major Industry of Current Parent: utilities and power generation
Specific Industry of Current Parent: utilities
Source of Data: (click here)
Source Notes: If an online information source is not working, check the Violation Tracker Data Sources page for an updated link.
Current parent company note: Parent-subsidiary relationship is current as of the most recent revision listed in the Update Log.