Strict Standards: Declaration of PropertyCollection::create() should be compatible with ItemCollection::create() in /homepages/u42892/contenido/classes/class.properties.php on line 403

Strict Standards: Declaration of PropertyItem::setField() should be compatible with Item::setField($field, $value, $safe = true) in /homepages/u42892/contenido/classes/class.properties.php on line 451

Strict Standards: Declaration of cApiClient::deleteProperty() should be compatible with Item::deleteProperty($type, $name) in /homepages/u42892/contenido/classes/contenido/class.client.php on line 303

Warning: Cannot modify header information - headers already sent by (output started at /homepages/u42892/contenido/classes/class.properties.php:403) in /homepages/u42892/conlib/session.inc on line 502

Warning: Cannot modify header information - headers already sent by (output started at /homepages/u42892/contenido/classes/class.properties.php:403) in /homepages/u42892/conlib/session.inc on line 507

Warning: Cannot modify header information - headers already sent by (output started at /homepages/u42892/contenido/classes/class.properties.php:403) in /homepages/u42892/conlib/session.inc on line 508

Warning: Cannot modify header information - headers already sent by (output started at /homepages/u42892/contenido/classes/class.properties.php:403) in /homepages/u42892/conlib/session.inc on line 509

Warning: Cannot modify header information - headers already sent by (output started at /homepages/u42892/contenido/classes/class.properties.php:403) in /homepages/u42892/conlib/session.inc on line 510

Warning: Cannot modify header information - headers already sent by (output started at /homepages/u42892/contenido/classes/class.properties.php:403) in /homepages/u42892/conlib/session.inc on line 511

Warning: Cannot modify header information - headers already sent by (output started at /homepages/u42892/contenido/classes/class.properties.php:403) in /homepages/u42892/conlib/session.inc on line 512

Warning: Cannot modify header information - headers already sent by (output started at /homepages/u42892/contenido/classes/class.properties.php:403) in /homepages/u42892/conlib/session.inc on line 151

Strict Standards: Declaration of FrontendPermissionCollection::create() should be compatible with ItemCollection::create() in /homepages/u42892/contenido/classes/class.frontend.permissions.php on line 165

Strict Standards: Declaration of FrontendUserCollection::create() should be compatible with ItemCollection::create() in /homepages/u42892/contenido/classes/class.frontend.users.php on line 150

Strict Standards: Declaration of FrontendGroupCollection::create() should be compatible with ItemCollection::create() in /homepages/u42892/contenido/classes/class.frontend.groups.php on line 111

Strict Standards: Declaration of FrontendGroupMemberCollection::create() should be compatible with ItemCollection::create() in /homepages/u42892/contenido/classes/class.frontend.groups.php on line 228

Strict Standards: Declaration of WorkflowAllocations::create() should be compatible with ItemCollection::create() in /homepages/u42892/contenido/plugins/workflow/classes/class.workflowallocation.php on line 148

Strict Standards: Declaration of WorkflowAllocation::setField() should be compatible with Item::setField($field, $value, $safe = true) in /homepages/u42892/contenido/plugins/workflow/classes/class.workflowallocation.php on line 237

Strict Standards: Declaration of WorkflowArtAllocations::create() should be compatible with ItemCollection::create() in /homepages/u42892/contenido/plugins/workflow/classes/class.workflowartallocation.php on line 93

Strict Standards: Declaration of WorkflowItems::create() should be compatible with ItemCollection::create() in /homepages/u42892/contenido/plugins/workflow/classes/class.workflowitems.php on line 198

Strict Standards: Declaration of WorkflowItem::setField() should be compatible with Item::setField($field, $value, $safe = true) in /homepages/u42892/contenido/plugins/workflow/classes/class.workflowitems.php on line 321

Strict Standards: Declaration of WorkflowUserSequences::create() should be compatible with ItemCollection::create() in /homepages/u42892/contenido/plugins/workflow/classes/class.workflowusersequence.php on line 169

Strict Standards: Declaration of WorkflowUserSequence::setField() should be compatible with Item::setField($field, $value, $safe = true) in /homepages/u42892/contenido/plugins/workflow/classes/class.workflowusersequence.php on line 274

Strict Standards: Declaration of cApiUserCollection::create() should be compatible with ItemCollection::create() in /homepages/u42892/contenido/classes/contenido/class.user.php on line 72

Strict Standards: Static function Contenido_UrlBuilder::getInstance() should not be abstract in /homepages/u42892/contenido/classes/UrlBuilder/Contenido_UrlBuilder.class.php on line 55

Warning: Cannot modify header information - headers already sent by (output started at /homepages/u42892/contenido/classes/class.properties.php:403) in /homepages/u42892/cms/front_content.php on line 247

Strict Standards: Declaration of cApiClientLanguage::deleteProperty() should be compatible with Item::deleteProperty($type, $name) in /homepages/u42892/contenido/classes/contenido/class.clientslang.php on line 185
Bürger gegen Atomreaktor Garching e.V. - Störungen und Vorkommnisse am neuen Atomforschungsreaktor FRM 2 seit der Inbetriebnahme
Die erste Kernspaltung im Atomforschungsreaktor FRM 2 erfolgte im März 2004. Seitdem der FRM 2 in Betrieb ist, gibt es immer wieder Probleme. Er läuft seither nicht störungsfrei.

Stand: Februar 2007 3. Mai 2004 Reaktor außer Betrieb Fehlerhafte elektronische Messkarte misst Stickstoff-16-Aktivität im Kühlwasser 11. Mai bis 7. Juli 2004 Reaktor außer Betrieb Genau in dieser Zeit, am 9. Juni 2004, findet pompös die offizielle Inbetriebnahme mit Ministerpräsident Edmund Stoiber statt. Der Reaktor war aber in dieser Zeit 57 Tage (knapp 2 Monate) wegen massiver Probleme außer Betrieb.

 

Im Reinigungskreislauf für das Primärkühlwasser hat sich Radiolysegas angesammelt.

 

In so einem Fall besteht je nach Konzentration die Gefahr einer heftigen Reaktion, z. B. einer Explosion. 23.-25. Mai 2005 Reaktor außer Betrieb Defekte Messstelle zur permanenten Gasanalyse des Moderatorgaspuffers 24. Juni 2005 Reaktor außer Betrieb Störung an Durchflussmessern des Kühlkreislaufes 25. August 2006 Reaktor außer Betrieb Reaktorschnellabschaltung nach erhöhter Ortsdosisleistung 18. Dezember 2006 Reaktor außer Betrieb Reaktorschnellabschaltung 8. Februar 2007 Reaktor außer Betrieb Reaktorschnellabschaltung ... was kommt noch alles?....
Das alte Atomei (FRM) hat bereits Garchinger Boden radioaktiv verseucht.

April 2011


Impressum  Information in English