K Kavitha
KCR duaghter K Kavitha

BRS leader K Kavitha sent to CBI custody till April 15 in Delhi Excise Policy Probe

BRS leader K Kavitha has been remanded to Central Bureau of Investigation (CBI) custody until April 15 by Delhi’s Rouse Avenue Court in connection with the Delhi excise policy case. The arrest of Kavitha, who is a prominent figure in the political landscape, came following allegations related to the excise policy in the capital.

The CBI arrested Kavitha on April 11, and today, during the hearing at the Rouse Avenue Court, the investigative agency sought her custody for further questioning. The court, considering the gravity of the case, granted the CBI’s request and remanded Kavitha to their custody until April 15.

The case revolves around the Delhi excise policy, which has come under scrutiny for various alleged irregularities. Kavitha’s arrest has sent shockwaves through the political circles, with many questioning the implications of her involvement in the case.

The BRS leader’s arrest has also sparked discussions about transparency and accountability in the implementation of policies, especially those concerning excise and taxation. The CBI is expected to delve deeper into the matter during the remand period, aiming to uncover any potential wrongdoing.

Kavitha, known for her vocal stance on various issues, has yet to make an official statement regarding her arrest. The development has drawn attention not only from political quarters but also from the public, who are keen to see how the case unfolds in the coming days.

The Rouse Avenue Court’s decision to grant CBI remand signifies the seriousness of the allegations against Kavitha and the importance of thorough investigation. As the case progresses, more details are expected to emerge, shedding light on the complexities surrounding the Delhi excise policy and its implementation.

x

Check Also

Air india

Bomb Hoax Forces Air India Flight to Divert, Causing Over Rs 3 Crore in Losses

Air India Boeing 777, carrying 130 tonnes of jet fuel, was forced to make an ...

error: