I can understand Siddu's pain, I too have lost my son: Sadananda Gowda

[email protected] (CD Network)
July 30, 2016

Mangaluru, Jul 30: Even as hundreds of Sangh Parivar activist continued to post sadistic comments on social media celebrating the untimely death of Karnataka chief minister Siddaramaiah's elder son Rakesh, a senior BJP leader, who too had lost his son 13 years ago, has expressed deep condolences over the sad demise of 39-year-old budding leader.

1gowda“The grief of having lost a child can be known only by a father who has lost one and I fully understand CM's grief,” said former chief minister DV Sadananda Gowda, who is currently a union minister.

"I can understand his pain, I too have lost my son," said Mr Gowda, recalling the death of his own elder son — Kaushik Gowda, who died following a road accident in Puttur in 2003. Mr Gowda was a member of parliament representing Dakshina Kannada then.

Mr Gowda also took to twitter to express his shock: “I am shocked at the sad demise of Sri Rakesh Son of @CMofKarnataka Sri Siddaramaiaha ji .. No words to explain my feelings at this time,” he tweeted.

Speaking to media persons in Mangaluru, Mr Gowda said that at this situation Mr Siddaramiah not only manage the turmoil that is going on within the family, but also discharge his duties towards society as the head of the state.

Now the only option is that CM should see his departed son in the youth of the state and work towards their welfare, he added.

Also Read:

Karnataka CM Siddaramaiah's son Rakesh, 39, dies in Belgium hospital

Son dead, but they' show no sympathy for CM Siddaramaiah

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.
News Network
March 6,2020

Bengaluru, Mar 6: At least 13 persons, including women and children, were killed and five critically wounded when an SUV collided with a car that had crashed against a road divider moments ago near Kunigal in Tumakuru district of Karnataka in the early hours of Friday, police said.

Of the victims, while 12 died on the spot, a child breathed his last in a hospital, they added.

The injured were admitted to the hospital, the police said.

Among the dead, 10 were from Tamil Nadu and three from Bengaluru. All of them were pilgrims who were on their way to Dharmasthala in Karnataka.

There were five women and two children among the dead, the police said.

"Thirteen persons have died. The incident occurred post midnight. A car crashed against the road divider and another car collided with it," Tumakuru Superintendent of Police (SP) K Vamsi Krishna said.

The police had to struggle to pull the bodies out from the mangled vehicles.

On learning about the incident, relatives of the victims rushed to the spot.

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.
News Network
February 20,2020

Bengaluru, Feb 20: The poultry industry is facing losses amid rumours of the discovery of a chicken infected with coronavirus in Bengaluru.

DK Kantharaju, president, Karnataka Cooperative Poultry Federation said, "Karnataka is facing losses of Rs 60 to 65 crores. The consumption percentage has also decreased by 30-35 per cent".

Atiq, a meat seller, said, "Because of coronavirus people are scared. But I want to say that chicken is safe to consume here. All this fear is caused due to fake news on social media."

Another person Abdul Hafeez said, "Chicken and coronavirus are not related. People are scared because of what is being spread on social media. The business has definitely gone down due to fear of coronavirus."

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.