ML15218A227
| ML15218A227 | |
| Person / Time | |
|---|---|
| Site: | Pilgrim |
| Issue date: | 08/05/2015 |
| From: | Maurer W - No Known Affiliation |
| To: | Bill Dean Office of Nuclear Reactor Regulation |
| References | |
| Download: ML15218A227 (4) | |
Text
From:
William Maurer To:
Dean, Bill Cc:
McKinley, Raymond
Subject:
[External_Sender] White Finding SRVs Date:
Wednesday, August 05, 2015 11:07:09 AM Attachments:
Chronology of LOOP events.pdf Hello Mr. Dean, On July 8, 2015 Pilgrim contested an NRC white finding. When will the NRC issue it's determination?
It's troubling that Entergy left SRVs that malfunctioned during the NEMO Nor'easter February 8, 2013 in service for two years only to malfunction again on January 27, 2015 during the JUNO Nor'easter.Similarly troubling was the NRC's discovery (reported in the Jan 26, 2015 Special Inspection Report) of failed switch yard insulators, also from NEMO, that were discovered by NRC investigators in storage that Entergy forgot (?) to send out for lab testing.
I guess Entergy has to legitimize these with the NRC. How does the NRC legitimize it's resident inspectors also letting these kind of issues fall through the cracks? What happened to determination of Root Cause and Corrective Action Plans?
Had the situation deteriorated at Pilgrim during the JUNO blizzard, evacuation would have been impossible for days.This is a significant deficiency in the generic Nuclear Preparedness Planning as applied to Pilgrim.Is the NRC and Entergy just realizing that Blizzards are common place in the Northeast and that Pilgrim's switch yard has recurrently failed during severe winter conditions(see attachment)? How does the NRC and Entergy justify their recurrent decisions to keep rolling the dice at Pilgrim during Nor'easters and severe winter weather conditions?
You are literally gambling with my skin in the game. How bad is it going to have to hurt before the NRC recognizes the seriousness of Pilgrim'scumulativeproblems?
Sincerely concerned, William Maurer 140 Gifford St.
Falmouth, MA 02540 508-548-6221
ChronologyofLOOPEvents PilgrimNuclearPowerStation
1.Sep10,1975Thereactorautomaticallyscrammedduetoapowerinterruptionduringapower supplytransferevolution.
2.Sep13,1975Thereactorautomaticallyscrammedwhenthe345kilovolttransmissionlinewaslost.
Sep13,1975Theoperatorswereshuttingdownthereactorwhentheturbinetripped.Duringtheensuing inplantelectricalpowertransfers,blownfusesdeenergizedthestartupand auxiliary345kilovoltlines,causingaLOOPandanautomaticreactor scram.Theemergencydieselgenerators(EDGs)automaticallystartedandwere connectedtothesafetyrelatedelectricalbuses.Areliefvalve(2032B)openedand stuckopenduetosteamcuttingthepilotvalveassembly.Thereactorpressure droppedtoapproximately300poundspersquareinchgauge.
3.May1,1977ThereactorautomaticallyscrammedonLOOPcausedbyaforestfire
4.Feb6,1978(Noreaster/BlizzardBlizzardof78)Thereactorautomaticallyscrammedwhenheavy snowfallcausedelectricalbreakersinthe345kilovoltswitchyardtoflashoverandtrip.
Feb6,1978Thereactorautomaticallyscrammedfrom24percentpowerwhenhighwindsandicebuildup causedalltransmissionlinestofail(causingaLOOP)..
5.Aug6,1978ThereactorautomaticallyscrammedwithLOOPduetoastorm.
Aug6,1978Thereactorautomaticallyscrammedfrom100percentpowerwhenlightningstrucktransmission linescausingaLOOP.Theemergencydieselgeneratorsautomaticallystartedandconnectedtotheirelectrical buses.Theoperatorsmanuallystartedthereactorcoreisolationcooling(RCIC)andhighpressurecoolant injection(HPCI)systemstomaintainreactorwaterlevel.Theoperatorsopenedasafetyreliefvalvetocontrol reactorpressure.Offsitepowerwasrestoredabout30minuteslater.
6.Jul27,1979ThereactorautomaticallyscrammedonLOOPpowerduetoalightningstrike.
Jul27,1979AlightningstrikecausedaLOOP.
Jul31,1979Theunitwasconnectedtotheelectricalgrid.
7.Aug28,1979ThereactorautomaticallyscrammedwhenalightningstrikecausedaLOOP.
8.Oct12,1982[LicenseeEventReportLER1982051]Highwindscausedsaltaccumulationonelectrical equipmentthatledtoanelectricalfaultandaLOOPlastingabout1minute.(recordsnotonNRCwebpage:
saltaccumulationfaultimpliesflashover)
9.Feb13,1983(Noreaster/Blizzard)[LER1983007LOOP]Withthereactorshutdown,therewasa LOOP.Feb13,1983Highwindscausedsaltaccumulationonelectricalequipmentthatledtoanelectricalfault andaLOOPlastingabout1minute.(recordsnotonNRCwebpage:saltaccumulationandelectricalfault impliesflashover)
Attachment
Feb15,1983Theunitwasconnectedtotheelectricalgridtoenda48.2hourforcedoutage.
10.Nov19,1986IcebuilduponelectricalequipmentcausedafaultandaLOOPlastingabout1minute.
11.Mar31,1987[LER1987005]HeavywindscausedanelectricalfaultandaLOOPlastingabout1minute.
12.Nov8,1987LOOPtriggerssitestopworkorder Nov9,1987Thecompanyhaltedmaintenanceactivitiesandsentabout400contractorshome.
Nineseparateincidentsoverthepriorthreedayperiod,tworesultinginradioactive contaminationofworkers,promptedthedecision.
Nov12,1987NRCdispatchesAugmentedInspectionTeamtositetoinvestigateLOOPevent.
13.Nov12,1987[LER1987014]Highwindscausedsaltaccumulationonelectricalequipmentthatledtoan electricalfaultandaLOOPlasting21hoursand3minutes.(recordsnotonNRCwebpage:saltaccumulation suggestsflashover)
14.Mar13,1989Thereactorwasshutdownduetoatransformerblackoutcausedbyasolarmagnetic storm.
Mar16,1989Theunitwasconnectedtotheelectricalgrid.Anadministrativeorderlimitedthereactorpower levelto25percent.
15.Oct30,1991(Noreaster/Hurricane:PerfectStorm)[LER1991024]LossofPreferredand SecondaryOffsitePowerDuetoSevereCoastalStormWhileShutdown]Theoperatorsshutdown thereactorwhenaseverestormblewseaweedintotheintakestructure,cloggingthecirculatingwaterpumps, andcausingalossofcondenservacuum.
Oct30,1991WeatherrelatedLOOPlasting120minutes(switchyardflashoverreportedinLER)
16.Dec13,1992(Noreaster/Blizzard)[LER1992016]AutomaticScramResultingFromLoad Rejectionat48PercentReactorPower]Thereactorautomaticallyscrammedonageneratorload rejectioncausedbyflashoversintheswitchyardduetosaltdepositsduringaseverestorm.
Dec18,1992Theunitwasconnectedtotheelectricalgridtoenda116.4hourforcedoutage.
17.Mar131993(Noreaster/Superstorm/BlizzardStormoftheCentury)[LER1993004]Thereactor automaticallyscrammedonageneratorloadrejectioncausedbyflashoversintheswitchyarddueto windpackedsnowduringblizzardconditions.
Mar13,1993WeatherrelatedLOOPlasting1minute.
Mar17,1993Theunitwasconnectedtotheelectricalgridtoenda84.5hourforcedoutage
18.Sep10,1993[LER1993022]Thereactorautomaticallyscrammedafterlightningstrikescaused switchyardbreakerstoopen.
Sep10,1993LOOPlasting10minutes.
Sep12,1993Theunitwasconnectedtotheelectricalgridtoenda43.7hourforcedoutage.
19.Dec19,2008(Noreaster/Blizzard)[LER2008006LER2008007]Thereactorautomaticallyscrammed whenawinterstormcausedicinginthemainswitchyard.(switchyardflashoverreportedin1/26/15 SupplementalInspectionReport)
20.Feb8,2013(Noreaster/BlizzardNemo)[LER2013003]Thereactorautomaticallyscrammedat9:17pm whenablizzardcausedLOOP.(switchyardflashoverreportedin1/26/15SupplementalInspectionReport)
Feb9,2013Workersrestoredoffsitepowertothesiteat6:09pm.
Feb10,2013Offsitepowertothesitewaslostat2:02pm.
Feb12,2013Workersrestoredoffsitepowertothesiteat4:05am.
Feb15,2013Thereactorwasconnectedtotheelectricalgridat10:39pmtoenda169.37hourforced outage.
21.Oct14,2013ThereactorautomaticallyscrammedduetoLOOPcausedbyfailureofanoffsitetower supportduringmodificationofoneofthe345kVoffsitelines.
Oct21,2015Reconnectedtothegrid
22.Jan27,2015(Noreaster/BlizzardJuno)ForcedOutageduetoLOOP.Switchyardflashoversreported.
Feb8,2015Restartedto79%Reached100%onFeb10,2015.
PrecautionaryShutdown,noLOOP Feb15,2015(NoreasterNeptune)PrecautionaryshutdowninadvanceofNoreasterNeptuneandan anticipatedLOOP.
Feb18,2015Restartedto18%ComplicationsdelayedrampupReached100%onFeb22,2015.
Summarybycause:
PowerSupplyTransfers2times
OffsiteTowerSupportFailure1time
LightningStrikes4times
ForestFire1time
SolarStorm1time
HighWinds3times
Noreasters/Blizzards,Ice,Snowwithswitchyardflashovers8times
Total=21times
PrecautionaryshutdownpriorNoreaster/Blizzard1time
TheinformationgatheredfromtheNRCwebsiteandAListofEventsbyDaveLochbaumfrom1965toMay 30,2013foundonthePilgrimCoalitionwebsiteunderShutdownTrackerLochbaumNote:Thisreport containsinformationabouteventsthathappenednoteventsthatdidnothappen.Inotherwords,justbecause aneventisNOTlistedinthisreportdoesnotmeanitdidnothappen.Itmightbethattheongoingresearch effortthatyieldedthisreporthasnotyetrecordedtheevent.