NCB witness in Aryan Khan’s arrest case who alleged Rs 25-cr extortion against Sameer Wankhede dies

News Network
April 2, 2022

starkid.jpg

In a shocking development, Prabhakar Sail, a panch witness in the drugs-on-cruise case involving the Narcotics Control Bureau raid on Cordelia cruise liner, died of a suspected heart attack on Friday evening.

The case pertains to a drug bust in which a total of 20 persons were arrested in the intervening hours of October 2 and 3, 2021. Bollywood superstar Shah Rukh Khan’s son Aryan Khan was also arrested in connection with the case from the cruise liner. 

Sail, in his early forties, died at his residence in Mahul of Chembur. 

Sail was the personal bodyguard of independent witness KP Gosavi, who claims to be a private detective and is currently behind bars. Gosavi's selfie with Aryan Khan led to a furore. Initially, it appeared that Gosavi was an officer, however, later NCB denied it and revealed that he was a witness. 

Prabhakar Sail’s allegation

In October last year, Sail stunned everyone by alleging the exchange of a huge volume of money involving officers from the Narcotics Control Bureau including its Zonal Director Sameer Wankhede. 

Sail, in his affidavit, had alleged that he heard Gosavi speak with one Sam D’Souza about one Rs. 18 crore deal of which Rs. 8 crore was meant to be paid to NCB Zonal Director Sameer Wankhede. According to Sail’s affidavit, he was present in the car when Gosavi spoke to D’Souza.

Sail had alleged that Gosavi held a meeting with D’Souza and Shah Rukh Khan’s manager, Pooja Dadlani in a car the same evening. Sail had gone on to add that he received the cash from Gosavi and personally delivered it to D’Souza.

Sail, one of the nine witnesses whose names were later released by the NCB, had said that he feared for his life after Gosavi went missing. This, according to him, was the reason why he decided to file an affidavit.

The affidavit had read, “On 1st October 2021, at about 9.45 PM, he (Gosavi) called me and said that I should be ready by 7.30 AM and that he has left. On 2nd October 2021, at about 7.35 Kiran Gosavi called me and said that he had transferred Rs. 500 to my gpay account and told me that he is sending me a location on WhatsApp and told me to come to that location.”

“I reached CST station at 8.45 PM and when I saw the location at WhatsApp, it was shown as NCB office. I reached there by taxi and saw white Innova car MH-12 GJ-3000 parked opposite NCB office, I asked the driver Vijay Suryavanshi as to where is KP Gosavi. He told me that KP Gosavi is in NCB office and he is in a meeting with NCB officials.”

He had continued, “I was with the driver at about 10 AM. Kiran Gosavi called the driver and came down with NCB officer for NCB office. Kiran Gosavi and the said officer left in the said Innova and instructed me to wait there itself. (sic)

“At about 10.30 pm I was called (by) KP Gosavi in the boarding area and I saw Aryan Khan in one of the cabins at the cruise boarding area. I saw one girl, Munmun Dhamecha and few others with NCB officials.”

“Till such time we reached Lower Parel KP Gosavi was talking to Sam on the phone and stated that you put a bomb of 25 crores and let’s settle at 18 final because we have to give 8 crores to Sameer Wankhede,” Sail had concluded.

Wankhede had denied allegations made by Sail.

The Mumbai Police later formed a four-member team to investigate sensational claims made by NCB witness Prabhaakr Sail. It was only after Sail’s claims that the NCB was forced to remove Sameer Wankhede from the case’s investigation.

Interestingly, Maharashtra Minister Nawab Malik had also accused Wankhede of indulging in extortion as he raised questions on the latter’s mysterious trips to the Maldives and Dubai in the past.

Malik was later arrested by another central government agency, the Enforcement Directorate.

Aryan Khan was arrested with seven others from a Goa-bound cruise ship by the NCB. He had to spend nearly a month in Mumbai’s Arthur Road jail until the Bombay High Court granted him bail.

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
December 7,2025

envoy.jpg

Since 1946, the United States has attempted 93 coups or “regime change” operations across the world — including two in Iran, US Special Envoy for Syria Tom Barrack has admitted.

Speaking to the UAE-based IMI Media Group, in remarks published by The National, Barrack said Washington tried twice to overthrow the Iranian government but failed both times. 

“For (Trump) then to be imputed with regime change — we had two regime changes in Iran already. Neither one worked. So I think wisely leave it to the region to solve,” said Barrack, who also serves as the US ambassador to Turkey.

His comments come six months after the US joined Israel in airstrikes against Iran during ongoing indirect nuclear negotiations between Tehran and Washington.

On June 13, Israel launched an attack on Iran that killed at least 1,064 people and hit civilian infrastructure. Days later, the United States targeted three nuclear facilities — Fordow, Natanz and Isfahan — in what Iran called a clear violation of international law. Iranian retaliation eventually forced a halt to the assault on June 24.

Barrack further claimed that US President Donald Trump and Foreign Secretary Marco Rubio are “not into regime change” and prefer a regional approach driven by Middle Eastern countries themselves. According to him, regional dialogue and non-interference by outside powers offer a more durable path forward.

He added that Washington is still open to an agreement with Tehran if Iranian authorities show “seriousness” and willingness to engage constructively.

However, Iran maintains the US has not shown readiness for meaningful talks. In an interview with Japan’s Kyodo News, Iranian Foreign Minister Abbas Araghchi said negotiations could advance only if Washington acknowledges Iran’s right to peaceful nuclear energy and lifts unilateral sanctions.

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
December 4,2025

Mangaluru: Chaos erupted at Mangaluru International Airport (MIA) after IndiGo flight 6E 5150, bound for Mumbai, was repeatedly delayed and ultimately cancelled, leaving around 100 passengers stranded overnight. The incident highlights the ongoing country-wide operational disruptions affecting the airline, largely due to the implementation of new Flight Duty Time Limitations (FDTL) norms for crew.

The flight was initially scheduled for 9:25 PM on Tuesday but was first postponed to 11:40 PM, then midnight, before being cancelled around 3:00 AM. Passengers expressed frustration over last-minute communication and the lack of clarity, with elderly and ailing travellers particularly affected. “Though the airline arranged food, there was no proper communication, leaving us confused,” said one family member.

An IndiGo executive at MIA cited the FDTL rules, designed to prevent pilot fatigue by limiting crew working hours, as the cause of the cancellation. While alternative arrangements, including hotel stays, were offered, about 100 passengers chose to remain at the airport, creating tension. A replacement flight was arranged but also faced delays due to the same constraints, finally departing for Mumbai around 1:45 PM on Wednesday. Passengers either flew, requested refunds, or postponed their travel.

The Mangaluru delay is part of a broader crisis for IndiGo. The airline has been forced to make “calibrated schedule adjustments”—a euphemism for widespread cancellations and delays—after stricter FDTL norms came into effect on November 1.

While an IndiGo spokesperson acknowledged unavoidable flight disruptions due to technology issues, operational requirements, and the updated crew rostering rules, the DGCA has intervened, summoning senior airline officials to explain the chaos and outline corrective measures.

The ripple effect has been felt across the country, with major hubs like Bengaluru and Mumbai reporting numerous cancellations. The Mangaluru incident underscores the systemic operational strain currently confronting India’s largest carrier, leaving passengers nationwide grappling with uncertainty and delays.

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
December 3,2025

indigo.jpg

IndiGo, India’s largest airline, is battling one of its worst operational disruptions in recent years, with hundreds of delays and cancellations throwing domestic travel into chaos.

Government data on Tuesday showed its on-time performance plunging to 35%, an unusual dip for a carrier long associated with punctuality.

By Wednesday afternoon, airports in Delhi, Mumbai, Bengaluru and Hyderabad had collectively reported close to 200 cancellations, stranding travellers across the country.

Crew Shortage After New Duty Norms

A major trigger behind the meltdown is a severe crew shortage, especially among pilots, following the rollout of revised Flight Duty Time Limitation (FDTL) norms last month.

The rules mandate longer rest hours and more humane rosters — a shift IndiGo has struggled to incorporate across its vast network.

Sources said several flights were grounded due to lack of cabin crew, while some delays stretched upwards of eight hours.

With IndiGo controlling over 60% of India’s domestic aviation market, the ripple effect has impacted airports nationwide.

IndiGo Issues Apology, Lists “Compounding Factors”

In a statement, IndiGo acknowledged the large-scale disruption:

“We sincerely apologise to customers. A series of unforeseen operational challenges — technology glitches, winter schedule changes, adverse weather, system congestion and updated FDTL norms — created a compounding impact that could not have been anticipated.”

To stabilise operations, the airline has begun calibrated schedule adjustments for the next 48 hours, aiming to restore punctuality. Affected passengers are being offered refunds or alternate travel arrangements, IndiGo said.

What the FDTL Rules Require

The FDTL norms, designed to reduce pilot fatigue, cap duty and flying hours as follows:
•    Maximum 8 hours of flying per day
•    35 hours per week
•    125 hours per month
•    1,000 hours per year

Crew must also receive rest equalling twice the flight duration, with a minimum 10-hour rest period in any 24-hour window.

The DGCA introduced these limits to enhance flight safety.

Hyderabad: 33 Flights Cancelled, Long Queues Reported

Hyderabad’s Rajiv Gandhi International Airport saw heavy early-morning crowds as 33 IndiGo flights (arrivals and departures) were cancelled.

The airport clarified on X that operations were normal, advising passengers to contact IndiGo directly for latest flight status.

Cancellations included flights to and from Visakhapatnam, Goa, Ahmedabad, Delhi, Bengaluru, Chennai, Madurai, Hubli, Bhopal and Bhubaneswar.

Bengaluru: 42 Flights Disrupted

Bengaluru’s Kempegowda International Airport recorded 42 cancellations — 22 arrivals and 20 departures — affecting routes to Delhi, Mumbai, Chennai, Hyderabad, Goa, Kolkata and Lucknow.

Passengers Vent on Social Media

Irate travellers took to X to share their experiences. One passenger stranded in Hyderabad wrote: “I have been here since 3 a.m. and missed an important meeting.”

Another said: “My flight was pushed from 1:55 PM to 2:55 PM and now 4:35 PM. I was informed only three minutes before entering the airport.”

Delhi Airport Hit by Tech Glitch

At Delhi Airport, the disruption deepened due to a slowdown in the Amadeus system — used for reservations, check-ins and departure control.

The technical issue led to longer queues and sluggish processing, adding to delays already worsened by staff shortages.

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.