ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Accident at Three Mile Island

Updated on March 21, 2011


The accident occurred at Three Mile Island nuclear power station at Three Mile Island in 1979 and was the worst nuclear accident occurred in the United States, although not proven to have caused deaths.


The incident took place exactly two unit at 4:00 Wednesday, March 28, 1979, when the reactor was under a power of 97%. The incident began in the secondary cooling circuit with the block flow of food to the steam generators. This block flow in the primary cooling core to a substantial increase in pressure of the refrigerant, causing the first opening of a valve located on the pressurizer PORV release and then the "SCRAM" (emergency stop of the reactor by inserting the control rods). At this point, the release valve is not closed without that operators were aware of the problem, because there was no indication in the instrument the actual position of the valve. Thus the primary cooling circuit is partially emptied and the waste heat from the reactor core could not be discarded. Because of this, the radioactive core was severely damaged. Traders could not properly diagnose what was happening and react appropriately. The lack of control room equipment and inadequate training were found to be the main causes of the accident.


During the incident there was a dangerous partial melting of the core and result in serious damage reported that Unit 2 was closed and is still under monitoring, in anticipation of future actions for decommissioning.

The Chain Of Events

 

Within 10 seconds after SCRAM, the release valve should have been close. This did not happen and there was a loss of coolant accident classified as a small break loss of coolant (Small Break LOCA). The operators believed, mistakenly, that the PORV had closed, as had been sent the command closing the valve. However, there was a real response to the closure of the valve.

 

To respond to the loss of coolant pumps high pressure emergency cooling system automatically injects water in the primary circuit, which simultaneously kept losing coolant from PORV open. In this way, however, the primary circuit pressure remained high, with the level in the pressurizer, while the level in the reactor core continued to decline. In a PWR reactor, the water pressure is very important, since it is maintained at high levels to prevent boiling, on the other hand, the water level in the pressurizer is also essential to control the reactor level is too not allow the high pressurizer pressure control system which would tend to increase, causing the rupture of the cooling system.

 

The operators responded by reducing the water flow of the emergency system at high pressure. Their training provided that the water level in the pressurizer was the only reliable indication of the amount of cooling water in the system. Since the level of the pressurizer was increasing, they thought the primary was too full of water. Their training provided that the primary was not 100% full, or risk losing control of pressure in the system.

 

The water vapor before and after, were collected in a tank drainage. When it reached a pressure of 13 bar, the rupture disk broke. At this point, the integrity of the primary circuit was lost. Part of the water began to flow into the containment system and was automatically removed from the pumps, sending the liquid to the auxiliary buildings are not designed to accept contaminated fluids.

 

Following the decrease in pressure of the steam formed in the reactor's primary cooling system. The presence of steam caused strong vibrations in the pumps (cavitation). Since the vibration could damage the pumps and make them unusable, operators decided to stop them. This resulted in overheating of the reactor core (the operators believed the cooling system full of water because of the indication of high pressure in the circuit). However, as the reactor coolant water evaporated due to the reduced pressure, and also was lost from PORV open the reactor core was found, with the result that they heated up further. The fuel rods are damaged and the radioactive material they contain contaminated water from the primary circuit.

 

At 6:22 operators closed the block valve between the relief valve and the booster. This action stopped the coolant leak. However, the presence of steam and hot gas prevented the regular eflusso of water through the reactor's cooling system.

 

 During the morning, traders tried to increase the flow of water into the reactor cooling system to condense the vapor bubbles that impede the smooth flow of cooling water. In the afternoon, traders tried to lower the pressure in the cooling system for groped to stabilize the situation.

 

In the evening, operators began to inject water under high pressure in the reactor cooling system to increase pressure and reduce the bubbles of steam and hydrogen. At 19:50 on March 28, the forced cooling of the reactor was re-established. They condensed the steam so that the pumps could operate without excessive vibration.

 

The radioactive gas from the reactor cooling system had accumulated at the top of the Vessel (the first container of the reactor core).

 

 The hydrogen accumulated, being extremely light, it was collected at the top of reactor. From March 30 to April 1 operators periodically removed by opening the hydrogen vent valve on the pressurized reactor cooling system. For a time, officials of the inspection (NRC) thought that the bubble of hydrogen could be a danger of explosion, with obvious disastrous effects on the integrity of the containment system of the system.

Stopping Cold

 

After months of anxiety and expectation, 27 April traders settled the refrigerant circulation by natural convection: the reactor core was thus cooled by the movement of water by natural convection rather than by mechanical pumping. The plant came into being "cold shutdown."

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)