Nabaz-e-punjab.com

CM rejects kunwar vijay prataps resignation, says punjab needs honest officers

Nabaz-e-Punjab, Chandigarh, April 13:
Punjab Chief Minister Captain Amarinder has refused to accept the resignation letter of IPS Kunwar Vijay Pratap Singh, seeking premature retirement from service. Declining the voluntary retirement plea of Kunwar Vijay Pratap, who is currently heading the Special Investigation Teams (SITs) probing the Kotakpura and Behbal Kalan firing cases, the Chief Minister said he was a highly competent and efficient officer whose services were needed in the border state, especially at a time when Punjab was faced with various internal and external security threats.
The state needs the expertise and experience of the officer, who has contributed exceptional service to the Punjab Police in various important positions, said the Chief Minister, describing Kunwar Vijay Pratap as a skilled, capable and courageous officer, with an exemplary track record.
Referring to media reports on the Punjab & Haryana High Court’s orders in the Kotakpura case probe, the Chief Minister pointed out that he had already made it clear that any decision of the court that seeks to remove Kunwar Vijay Pratap as the SIT chief or to quash the investigations in the case would be challenged by his government in the Supreme Court.
The officer and his team have done an excellent job of expeditiously investigating the Kotakpura case, which the Akalis have tried hard to stall for the past four years, Captain Amarinder said, adding that the probe will be taken to its logical conclusion under the guidance and supervision of the able officer himself.

WordPress database error: [User 'nabazdbd_wp1' has exceeded the 'max_questions' resource (current value: 1)]
SELECT DISTINCT t.term_id FROM wpum_terms AS t INNER JOIN wpum_term_taxonomy AS tt ON t.term_id = tt.term_id INNER JOIN wpum_term_relationships AS tr ON tr.term_taxonomy_id = tt.term_taxonomy_id WHERE tt.taxonomy IN ('post_tag') AND tr.object_id IN (72405) ORDER BY t.name ASC

    WordPress database error: [User 'nabazdbd_wp1' has exceeded the 'max_questions' resource (current value: 1)]
    SELECT SQL_CALC_FOUND_ROWS wpum_posts.ID FROM wpum_posts WHERE 1=1 AND wpum_posts.ID NOT IN (72405) AND ((wpum_posts.post_type = 'post' AND (wpum_posts.post_status = 'publish'))) ORDER BY wpum_posts.post_date DESC LIMIT 0, 3

Load More Related Articles

    WordPress database error: [User 'nabazdbd_wp1' has exceeded the 'max_questions' resource (current value: 1)]
    SELECT SQL_CALC_FOUND_ROWS wpum_posts.ID FROM wpum_posts WHERE 1=1 AND wpum_posts.ID NOT IN (72405) AND wpum_posts.post_author IN (1) AND wpum_posts.post_type = 'post' AND ((wpum_posts.post_status = 'publish')) ORDER BY wpum_posts.post_date DESC LIMIT 0, 3

Load More By Nabaz-e-Punjab

    WordPress database error: [User 'nabazdbd_wp1' has exceeded the 'max_questions' resource (current value: 1)]
    SELECT t.term_id FROM wpum_terms AS t INNER JOIN wpum_term_taxonomy AS tt ON t.term_id = tt.term_id WHERE tt.taxonomy IN ('category') AND t.term_id IN ( 146 )

    WordPress database error: [User 'nabazdbd_wp1' has exceeded the 'max_questions' resource (current value: 1)]
    SELECT SQL_CALC_FOUND_ROWS wpum_posts.ID FROM wpum_posts WHERE 1=1 AND wpum_posts.ID NOT IN (72405) AND ( 0 = 1 ) AND wpum_posts.post_type = 'post' AND ((wpum_posts.post_status = 'publish')) GROUP BY wpum_posts.ID ORDER BY wpum_posts.post_date DESC LIMIT 0, 3

Load More In Awareness/Campaigns

WordPress database error: [User 'nabazdbd_wp1' has exceeded the 'max_questions' resource (current value: 1)]
SELECT t.term_id FROM wpum_terms AS t INNER JOIN wpum_term_taxonomy AS tt ON t.term_id = tt.term_id WHERE tt.taxonomy IN ('category') AND t.term_id IN ( 20,23,33,35,39,146 )

WordPress database error: [User 'nabazdbd_wp1' has exceeded the 'max_questions' resource (current value: 1)]
SELECT wpum_posts.ID FROM wpum_posts WHERE 1=1 AND wpum_posts.ID NOT IN (72405) AND ( 0 = 1 ) AND wpum_posts.post_type = 'post' AND ((wpum_posts.post_status = 'publish')) GROUP BY wpum_posts.ID ORDER BY wpum_posts.post_date DESC LIMIT 0, 1