Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the all-in-one-seo-pack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/nepalgun/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the sharethis-share-buttons domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/nepalgun/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpreactions-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/nepalgun/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-statistics domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/nepalgun/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the add-search-to-menu domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/nepalgun/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the olympus-google-fonts domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/nepalgun/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the denra-wp-dt domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/nepalgun/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the denra-wp-dt domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/nepalgun/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the advanced-ads domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/nepalgun/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the viral domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/nepalgun/public_html/wp-includes/functions.php on line 6121
रुख कटान नहुँदा कोहलपुर–सुर्खेत १३२ केभी प्रसारण लाइन निर्माणमा ढिलाइ | नेपालगञ्ज पाटी
३ श्रावण २०८२, शुक्रबार

रुख कटान नहुँदा कोहलपुर–सुर्खेत १३२ केभी प्रसारण लाइन निर्माणमा ढिलाइ

रुख कटान नहुँदा कोहलपुर–सुर्खेत १३२ केभी प्रसारण लाइन निर्माणमा ढिलाइ

प्रकाश अधिकारी, रासस
कर्णाली, मङ्सिर ७ गते । रुख कटानको प्रक्रिया अघि नबढ्दा कोहलपुर–सुर्खेत १३२ केभी प्रसारण लाइनको काम प्रभावित भएको छ । आयोजना निर्माणका लागि बाँके, बर्दिया र सुर्खेतको वन क्षेत्रका रुख कटान नहुँदा टावर निर्माणको कार्य प्रभावित भएको हो ।
आयोजनाले बाँके, बर्दिया र सुर्खेतको वन क्षेत्रअन्तर्गतका १३ हजार ११९ रुख कटान गर्न प्रस्ताव गरेको छ । आयोजना प्रमुख रविकुमार चौधरीले रुख कटानसम्बन्धी प्रस्ताव स्वीकृतिमा भएको ढिलाइले निर्माण प्रभावित हुने बताउनुभयो । “आयोजना र नेपाल विद्युत् प्राधिकरणबाट सबै तयारी पूरा भइसकेको छ, मन्त्रिपरिषद्मा रुख कटानसम्बन्धी प्रस्ताव लैजाने काम वन तथा वातावरण मन्त्रालयको हो”, उहाँले भन्नुभयो । निकुञ्ज क्षेत्रका रुख कटान गर्नुपर्ने भएकाले वन मन्त्रालयलाई समय लागेको हुनसक्ने उहाँको भनाइ थियो ।
आयोजना र भारतीय ठेकेदार कम्पनी आरएस इन्फ्राप्रोजेक्टबीच भएको सम्झौताअनुसार २०७९ भदौसम्म निर्माण पूरा गर्नुपर्नेछ । हालसम्म रुख कटान सुरु भएको छैन । रुख कटान नहुँदा टावर निर्माणको काम प्रभावित भएको छ । विसं २०७७ असारमा ठेक्का सम्झौता भए पनि कम्पनीले यही भदौ तेस्रो सातादेखि निर्माणको काम थालेको हो ।
रुख कटानको अनुमति पाउन ढिलाइ हुँदा आयोजनाले जहाँ जङ्गल क्षेत्र छैन त्यस्ता ठाउँमा मात्र टावर निर्माणको काम गरिरहेको छ । हालसम्म १३ स्थानमा टावरको जग निर्माण गरिसकेको छ । झण्डै ५२ किमी दूरी रहेको सो प्रसारण लाइनमा डबल सर्किटका १६१ टावर निर्माण गर्नुपर्नेछ । मन्त्रिपरिषद् बैठकबाट रुख कटानको स्वीकृति पाएलगत्तै आयोजनाले रुख कटानका लागि बोलपत्र आह्वान, जग्गाको मुआब्जालगायत प्रक्रिया सुरु गर्नेछ ।
“अबको १० महिनाभित्र प्रसारण लाइन निर्माण गरिसक्नुपर्छ”, आयोजना प्रमुख चौधरीले भन्नुभयो, “रुख कटानमा ढिलाइ भए प्रसारण लाइन निर्माणको अवधि लम्बिन सक्छ ।” उहाँका अनुसार विस्तृत अध्ययन, रुख गणना, डिजाइन र टावर रहने स्थानको टुङ्गो लागिसकेको छ । सुर्खेतको छिन्चु र बाँकेको चिसापानी गाभरमा स्थानीयवासीको असहमतिका कारण जग्गाको मुआब्जा वितरण हुन नसकेको आयोजनाले जनाएको छ ।
विसं २०४५ मा निर्माण गरिएको ३३ केभी प्रसारण लाइनका कारण हाल कर्णालीमा ‘अनियमित विद्युत्’ ठूलो समस्याका रूपमा छ । भोल्टेज कम हुने, सामान्य वर्षा र हावाहुरीमै पोल ढल्नेजस्ता समस्याले यहाँका उपभोक्ताले हैरानी खेप्नुपरेको छ । यो आयोजना निर्माण भएमा उक्त समस्या हट्ने कर्णालीवासीको अपेक्षा छ ।
करिब रु ७० करोड लागतमा ठेकेदार कम्पनीले प्रसारण लाइनका लागि डिजाइन, निर्माण, परीक्षण, वितरण र प्लान्ट खरिदका काम सम्पन्न गर्नुपर्नेछ । प्रसारणलाइनको अधिकांश क्षेत्र बाँके राष्ट्रिय निकुञ्ज र बर्दिया राष्ट्रिय निकुञ्ज तथा यसका मध्यवर्ती क्षेत्र पर्दछन् । प्रसारण लाइनको ७०।५४५ भाग वन क्षेत्र, १५।१३५ खेतीयोग्य, २।२६५ बाँझो जमिन र ११।०६५ अन्य भागले ओगटेको छ । प्रसारण लाइनका लागि जग्गाको क्षेत्रफल २२५ वर्गमिटर तोकिएको छ । आयोजनाबाट बाँकेका कोहलपुर नगरपालिका र बैजनाथ गाउँपालिका, बर्दियाको बासगढी नगरपालिका तथा सुर्खेतका भेरीगङ्गा, लेकबेँसी र वीरेन्द्रनगर नगरपालिका प्रभावित हुनेछन् । आयोजना बाँकेको कोहलपुर सबस्टेशनबाट प्रारम्भ भई वीरेन्द्रनगरस्थित सुर्खेत सबस्टेशनमा पुगेर टुङ्गिनेछ । (रासस)

यो खबर पढेर तपाईलाई कस्तो महसुस भयो ?
+1
0
+1
0
+1
0
+1
0
+1
0
+1
0
+1
0

Leave a Reply

Your email address will not be published. Required fields are marked *