12.07.2015 Views

16.2 - Severe Accident Analysis (RRC-B) - EDF Hinkley Point

16.2 - Severe Accident Analysis (RRC-B) - EDF Hinkley Point

16.2 - Severe Accident Analysis (RRC-B) - EDF Hinkley Point

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

SUB-CHAPTER : <strong>16.2</strong>PRE-CONSTRUCTION SAFETY REPORTCHAPTER 16: RISK REDUCTION AND SEVEREACCIDENT ANALYSESPAGE : 143 / 295Document ID.No.UKEPR-0002-162 Issue 04In the stratified mode, the downward MCCI is governed initially by the heavier oxidic melt. Dueto the admixture of lightweight concrete decomposition products, the density of the oxidesteadily approaches that of the metal melt until finally, the metallic melt relocates underneath theoxide. During this layer inversion, the slag layer which formed on top of the metal melt mixeswith the oxide. As the slag layer consists of lightweight material, namely of concretedecomposition products and oxidation-products formed in the metal layer, this admixture resultsin a strong decrease of the oxide density and a new stable stratification.In addition to the described changes of the configurations of the layers, an assumed permanentmixing of the oxidic and metallic phases during the entire MCCI was also analysed. These twocases (fully stratified and fully mixed) bound all intermediate configurations, including a partialmixing of the metal into the oxide at the common interface. Sub-section <strong>16.2</strong>.2.4 - Table 3 givesan overview of all analysed cases.The analysis performed [Ref] had demonstrated that the calculated retention times arepractically independent of the initial Zr-oxidation level, because the Zr-fraction is fully oxidisedwithin a short period. Therefore, in most of the following calculations a best-estimate value of40% by weight was chosen for the degree of Zr-oxidation in the oxidic melt at the time of itsrelease from the RPV.The decay power distribution between oxidic and metallic melt fraction was assumed to be90:10, in accordance with the experimental results obtained of the MASCA projects [Ref].First large pour consisting of metallic melt onlyIn order to supplement the described best-estimate release sequences, a postulated initialrelease of a large amount of metal melt (without oxide) was also analysed. The scenario relatesto an initial breach of the RPV near the lower level of the metallic pool after practically all themetal has already accumulated in the lower head. The resulting fast axial erosion is consideredthe most onerous case for the retention function.The assumptions made for the mass and temperature of the metal melt release are compatiblewith those for the generalised sequences. The chosen amount of 70 te corresponds to the fullmass of the metallic melt release as considered in the other scenarios.While the composition of the ternary Fe/Cr/Ni subsystem is kept constant and taken equal tothat given in Sub-section <strong>16.2</strong>.2.4 - Table 2, the degree of Zr-oxidation was varied between 30%and 70% to parametrically investigate the effect of the Zr-chemistry. In addition, to assess theinfluence of the initial temperature of the metal melt, its value was varied between 1550°C and1700°C. Sub-section <strong>16.2</strong>.2.4 - Table 4 summarises the investigated cases for the metal meltrelease.2.4.1.2.3. ResultsThis sub-section presents the results of the analysis performed to examine the ability of thereactor pit to accumulate the core inventory. Melt accumulation is considered successful if, foreach analysed case, the following two targets are fulfilled, significantly before the MCCI poolcomes into contact with the melt gate:• The lower head plus lower support plate ("RPV-bottom") have failed thermally anddropped into the MCCI pool together with the residual in-vessel melt• All incorporated material is molten and diluted in the MCCI-pool and conditions thatfavour melt spreading are achieved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!