Boat capsizes during Kannada film ‘Kantara: Chapter 1’ shoot, Rishab Shetty and crew members escape unhurt

Kaumi GazetteEntertainment15 June, 20258.2K Views

A nonetheless from ‘Kantara’
| Photo Credit: Hombale Films

A ship capsized in a reservoir during the capturing of Kannada film Kantara: Chapter 1, the prequel to 2022’s Kantara, however actor-director Rishab Shetty and 30 crew members escaped unhurt, averting a significant mishap, police sources stated. The incident allegedly occurred during the filming within the Mani reservoir within the Masti Katte area of Shivamogga district, they added.

The accident occurred in a shallow zone of the reservoir, close to an space domestically often known as Melina Koppa, which helped avert a attainable tragedy. However, cameras and different filming tools are believed to have been misplaced to the water. The losses are but to be assessed. According to the Thirthahalli police, who visited the spot, folks onboard escaped unhurt. Police are investigating.

Theatre artist Ramadas Poojary advised PTI that making a film on the spirits of Dakshina Kannada is all the time dangerous, because the spirits (Bhootas-Daivas) don’t just like the commercialisation of any exercise linked to them.

However, Rishab Shetty, who reveres the spirits, has carried out elaborate poojas to them and was given permission to make the film, says Poojary.

A senior crew member who spoke to PTI on the situation of anonymity stated a number of the crew members panicked when the boat overturned, however because it was within the shallow waters, all of them waded by way of to security. “It shows that the spirits have blessed us in some way,” the crew member stated.

This incident marks one more setback for Kantara: Chapter 1, which is grappling with a sequence of unlucky occasions. In the previous month alone, the manufacturing staff has misplaced three artists to unrelated incidents, including to the challenges confronted by the film’s crew.

Loading Next Post...
Loading

Signing-in 3 seconds...

Signing-up 3 seconds...