Key Points

The AAIB's preliminary report confirms the Uttarkashi helicopter crash occurred when the main rotor blade struck an overhead cable during an emergency landing. The Bell 407, carrying pilgrims for the Char Dham Yatra, descended unexpectedly before crashing into a gorge. Despite a prior tail rotor issue, the aircraft was deemed airworthy before the fatal flight. International experts are assisting in the ongoing investigation to determine the root cause.

Key Points: Uttarkashi Helicopter Crash Caused by Rotor Blade Hitting Cable During Emergency Landing

  • Emergency landing led to rotor blade hitting overhead cable
  • Bell 407 helicopter destroyed but no fire post-crash
  • Single-pilot operation during Char Dham Yatra flight
  • Tail rotor defect fixed days before was not a factor
3 min read

Main rotor blade struck overhead cable while emergency landing, says AAIB's preliminary report on Uttarkashi helicopter crash

AAIB report reveals main rotor blade struck overhead cable during emergency landing, killing 6 in Uttarkashi helicopter crash.

"The helicopter flew for 20 minutes before descending from its assigned altitude... eventually coming to rest 250 feet deep into a gorge. — AAIB Preliminary Report"

New Delhi, July 19

The Aircraft Accident Investigation Bureau (AAIB) on Saturday released the preliminary report into the May 8 Uttarkashi helicopter crash which claimed the lives of six people including the pilot.

The report said that the helicopter crash near Gangnani in Uttarkashi was caused during emergency landing by the main rotor blade striking an overhead fibre optic cable.

The report said that 20 minutes after takeoff, the helicopter began to descend from its assigned altitude.

One passenger survived but sustained serious injuries. The crash occurred around 08:35 am during a chartered Char Dham Yatra flight.

The Bell 407 helicopter, registered as VT-OXF and operated by Aerotrans Services Pvt. Ltd., had departed from Kharsali Helipad to Jhala Helipad with six passengers. This was a single-pilot operation and followed an earlier routine hill familiarisation flight completed earlier that day.

"The purpose of the flight was Charter flying for Char Dham Yatra. This was a single pilot operation flight, and this sector was planned to be operated by another pilot. The assigned flight level for this entire sector was 10,500ft AMSL... The helicopter airborne again at 08:11 IST from Kharsali helipad," the report said.

Investigators noted that the helicopter began descending from its assigned cruising altitude and attempted an emergency landing on the Uttarkashi-Gangotri Road (NH 34), near Gangnani.

During the descent, the main rotor blade struck an overhead cable that ran parallel to the road. The impact also damaged nearby metal barricades before the helicopter tumbled down a steep slope. It eventually came to rest against a tree roughly 250 feet into a gorge.

"The helicopter flew for 20 minutes before descending from its assigned altitude... Eventually, it came to rest against a tree, approximately 250 feet deep into a gorge," the report said.

The accident claimed the lives of the pilot and five passengers, leaving one passenger with serious injuries.

"The pilot and five passengers were fatally injured in the accident, while one passenger sustained serious injuries. The helicopter was destroyed in the crash. However, there was no fire," the preliminary report said.

The report said the aircraft was airworthy at the time of the flight. Records show a tail rotor defect had been fixed two days prior to the crash and is not believed to have contributed to the incident. All required inspections were current as of April 25, 2025.

"The BELL 407 helicopter was manufactured in 2008... The last scheduled inspections were carried out on April 25, 2025," the report noted.

The technical logbook showed the last pilot-reported defect was tail rotor skin peeling on May 3, 2025, which was corrected by May 7.

"The last defect reported by the pilot was 'surface skin peeled at the tail rotor tip'... the Certificate to Release to service was issued on 07th May 2025," the report said.

The wreckage has been transported to a secure facility for further examination. Experts from the US National Transportation Safety Board (NTSB), Transportation Safety Board of Canada (TSB), and Rolls-Royce are aiding in the investigation.

"The investigation team visited the accident site and carried out onsite investigation... The identified helicopter and engine components were brought to the AAIB Headquarters by the investigation team," the report said.

Additional coordination with international authorities and technical advisors is ongoing as investigators continue to gather and analyse evidence to determine the root causes.

- ANI

Share this article:

Reader Comments

P
Priyanka N
As someone from Uttarakhand, I can say these mountain cables are death traps! They should be marked properly with bright colors or removed from flight paths. So many accidents happen because of these invisible wires. Government needs to take action.
A
Aditya G
The report says the helicopter was airworthy but descending from cruising altitude suddenly is concerning. Maybe pilot fatigue? These Char Dham pilots do back-to-back flights during season. DGCA should limit flight hours strictly.
S
Sarah B
Respectfully, while the report is detailed, it raises more questions than answers. Why was this a single-pilot operation on such a dangerous route? And why was the planned pilot changed last minute? Hope the final report addresses these.
K
Karthik V
The survivor must be traumatized for life. We need better emergency medical response in these remote areas. 20 minutes is too long for help to arrive in such cases. Helicopter operators should have standby rescue teams during pilgrimage season.
M
Meera T
My uncle took this same route last month! This is terrifying. The government must audit all helicopter operators immediately. Too many shortcuts being taken in the name of religious tourism. Safety first always 🙏
R
Rohit P
The tail rotor repair just 2 days before crash is suspicious

We welcome thoughtful discussions from our readers. Please keep comments respectful and on-topic.

Leave a Comment

Minimum 50 characters 0/50