Supreme Court grants bail to 17 Gujarat mass massacre CONVICTS, asks admin to find them work

News Network
January 28, 2020

New Delhi, Jan 28: The Supreme Court of India today granted bail to 17 convicts sentenced to life imprisonment in 2002 Gujarat massacre case, pending their appeal before the Supreme Court.

The convicts also have to participate in social and spiritual services, said the court, announcing the riders for bail.

The Bench of Chief Justice of India SA Bobde and Justices BR Gavai and Surya Kant directed for the convicts to be segregated into two groups to be sent to Indore and Jabalpur.

District legal authorities in Indore and Jabalpur in Madhya Pradesh have been asked to ensure that the convicts do the spiritual and social work the court has asked for.

The Supreme Court has also asked the administration to find them work for livelihood. The state legal services authority has been asked to file a compliance report as also report on their conduct.

The case concerns the mass killing of 33 innocent Muslims - mostly women and children - who were burnt alive at Sardarpura village in March 2002.

This was part of the mass massacre that swept through Gujarat in the aftermath of the death of train passengers on Sabarmati Express in Godhra on Feb 27, 2002. Thousands of innocent Muslims were killed and raped in the three-day violence. The victims include hundreds of children including newborns.

In 2016, the Gujarat High Court had upheld the conviction of 17 accused in the Sardarpura massacre case.

Earlier, a Special SIT court had convicted a total of 31 persons in the case, after three years of trial against 73 persons from Sardarpura and nearby villages.

Comments

Abdul Gaffar Bolar
 - 
Wednesday, 29 Jan 2020

Justice denied.RIP Justice.

 

Indian Soul
 - 
Wednesday, 29 Jan 2020

BJP Boot lickers

 

2000 people including small child and not born child has been killed in gujrath riot...forget about people even GOD also not show mercy on them.

the man who protect the criminal is equal to the man who did the crime.

 

Neshu,Mangalore
 - 
Wednesday, 29 Jan 2020

Justice delayed is Justice denied!!!! Supreme court since last 6 months taking decission not as per Just. please Uphold the Supreme court Honour as its noble institution.as culprit must be punished so has to set example for the wrong doers.

Fairman
 - 
Tuesday, 28 Jan 2020

Wah, the real culprit  who orchestered the complete episode has been PM to commit more such.

This man need to be facing the similar justice system. He knows, this is India, anything can be done.

 

Only these few are punished.

 

We will see the justice is really done as per real justice.

Ham bhee dekhenge

Althaf
 - 
Tuesday, 28 Jan 2020

For the sake of God please do not call them JUSTICE. If they str aware of meaning of word justice then they would have given death penalty to all the culprits. So sad that supreme court of india is running as per the instructions of MODI govt. RIP Justice

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
May 26,2020

Newsroom, May 26: A migrant worker died of hunger while a 10-month-old boy suffering from fever and breathing difficulties died negligence in two separate incidents onboard Shramik Special trains in Uttar Pradesh.

The 46-year-old dead migrant worker’s nephew, who was accompanying him, said that the victim had not eaten anything in the last 60 hours.

Raveesh Yadav said that no food or water was provided on the train, which they had boarded from Mumbai to travel to their native place in Jaunpur district in Uttar Pradesh.

Yadav and his uncle were working as construction workers in Mumbai.

Yadav told the paper that the train had left the Lokmanya Terminal in Mumbai, at 7pm on May 20 and arrived at its final stop, Varanasi Cantonment station, at 7.30am on May 23.

“But my uncle, who was complaining of hunger and pain all over his body, fainted half an hour before we reached Varanasi Cantonment and died within a few minutes,” Raveesh was quoted as saying.

He added that he and his uncle were hungry when they boarded the train but could not find food or water to buy.

Railways’ apathy

Meanwhile, the family of 10 month old child, who died in the train, alleged that the railways did not arrange for a doctor despite their repeated pleas.

The railway doctors had been moved to Covid-19 hospitals and by the time a doctor was provided at Tundla railway station, it was too late, the report quoted the child's grandfather, Dev Lal, as saying.

Lal said that the family members had tried to speak to the GRP at many stations, including at Aligarh, where the train had halted. "But they showed no interest and said any help would be available only in Tundla,” Lal said.

Railways officials then took the kin to a quarantine centre in Tundla, as they suspected that the baby had died because of the novel coronavirus.  It was only on Monday that the incident came to light when another individual at the quarantine facility intimated journalists after the condition of the child's mother worsened.

Last November, the mother of the child, Priyanka Devi of Bihar's Notan village in West Champaran, had gone to visit her parents who reside in Noida with the baby, who was then just four months old. Her husband Pramod Kumar is a farmer, the report added.

Comments

andh bakth
 - 
Tuesday, 26 May 2020

Vote for BJP and you need only hindutva dont worry about food, job etc.......jai modiji

very sad for baby:(

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
coastaldigest.com news network
June 6,2020

Bengaluru, Jun 6: Karnataka registered 378 Covid-19 cases in the past 24 hours, breaching the 5,000-mark to settle at 5,213, said an official, here on Saturday. "New cases reported from Friday 5 p.m. to Saturday 6 p.m. is 378," said a health official.

Of the new cases, 333 are local returnees, comprising 88 per cent of the new infections. Returnees from Maharashtra accounted for 99 per cent new cases at 329.

Majority infections in Karnataka nowadays are returnees, mostly from the state''s northern neighbour. Only 27 new infections were contacts of earlier cases.

On Saturday, cases spiked in Udupi, Kalaburagi, Yadgir, Bengaluru Urban, Belagavi, Vijayapura, Davangere and Dakshina Kannada.

Udupi witnessed the highest number of cases (121), followed by Yadgir (103), Kalaburagi (69), Dakshina Kannada (24), Bengaluru Urban (18), Vijayapura and Davangere (6 each), Belagavi (5), Gadag (4), Mandya, Hassan, Dharwad and Haveri (3 each), Raichur, Chikkaballapura and Uttara Kannada (2 each) and Bidar, Tumkur, Kolar and Koppal (1 each).

Among the new cases, three patients from Bengaluru Urban are suffering from Influenza Like Illness (ILI) and another from Severe Acute Respiratory Infection (SARI).

There were seven cases with international travel history to United Arab Emirates (UAE) and one to Turkey.

Meanwhile, 280 people were discharged in the past 24 hours and two persons succumbed to the virus, one from Bidar and another from Vijayapura. Of all the cases, 3,184 are active, 1,968 discharged, 59 dead and 11 in the ICU.

In the past 24 hours, Karnataka tested 11,862 people, of which 11,431 reports returned negative. In total, 3.72 lakh samples have been tested so far, of which 3.61 lakh have returned negative.

Currently, Udupi is leading the state''s Covid-19 burden with 785 active cases, followed by Kalaburagi (448), Yadgir (407), Raichur (320) and Mandya (163) among others.

Bengaluru Urban has accounted for 13 deaths, followed by Kalaburagi (7), Bidar, Vijayapura, Davangere and Dakshina Kannada (6 each) and Chikkaballapura (3 each), among others.

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
coastaldigest.com news network
August 8,2020

Mangaluru, Aug 8: As visuals of the Air India Express flight crash at Kozhikode international airport emerge, one cannot help but be reminded of an eerily similar and unfortunate accident that occurred a decade ago. The August 7, 2020 tragedy brought back memories of the 2010 crash.

It was on May 22, 2010 that an Air India Express Boeing 737-800 flight from Dubai to Mangaluru over shot the runway while landing at Bajpe airport and fell into a cliff. Of the 160 passengers and 6 crew members on board, 158 were killed (all crew members and 152 passengers) and only 8 survived.

Even back then, the plane had split into two. The crash has been termed as one of India's worst aviation disasters.

The final conversations between Air traffic control (ATC) and the pilot prior to the landing showed no indication of any distress.

Like the Mangaluru accident, Karipur crash too happened when the flight was attempting to land.

The captain of the aircraft which crashed at Mangaluru, Z Glucia, was an experienced pilot with 10,000 hours of flying experience and had 19 landings at the Mangalore airport. Co-pilot S S Ahluwalia, with 3,000 hours of flying experience had as many as 66 landings at this airport. Both the pilot and co-pilot were among the victims.

An investigation into the accident later found that the cause of the accident was the captain’s failure to discontinue an ‘unstabilised approach’ and his persistence to continue with the landing, despite three calls from the First Officer to ‘go-around’.

Comments

Add new comment

  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.