SARAS crash probe report

The report of the investigation into the crash of Saras, the light transport aircraft, near Bangalore on March 6, 2009 that killed all three crew members on board, enumerates dozens of lapses, including an insufficient pre-flight debriefing, a poor telemetry system and “lack of crew coordination.”

The report, prepared by a board constituted by the Directorate-General of Civil Aviation (DGCA) and made public on the DGCA website on
Thursday, said: “Incorrect relight [restart] procedure devised by the designer and adopted by the crew… [led to] abnormal behaviour of
aircraft [and] resulted in the accident.”

The second prototype of the aircraft, built by the National Aerospace Laboratories (NAL), crashed and burst into flames near Bidadi, 30 km from here, less than an hour after it took off, killing Wing Commander K. Praveen, Wing Commander Dipesh Shah and test engineer Squadron Leader
Ilayaraja, all in their mid-thirties.

The 75-page report says the pilots switched off one of the engines midair (as part of the programme requirement), but failed in their attempt to relight it. “Saras-specific intentional engine shutdown and relight procedure was not well planned and prepared,” it says. “Either wrong selection of mode switch or the [failure to press] engine start switch… during the first relight attempt is the most probable cause for the engine not to relight in the first attempt.”

Contributing to the tragedy was the lack of crew coordination; the failure to abort the flight by the crew in coordination with the flight test director after the failure of the first relight attempt; and the NAL’s devising of the engine relight procedure without consulting the propeller manufacturer.

The cockpit voice recorder reveals that telemetry (communication between the aircraft and the ground station) was intermittent. Also, there
appeared to be “no effective pre-flight briefing to the crew,” the report said, adding “there is no contingency plan for emergencies like accident, missing aircraft, loss of communication etc.”

The chilling transcript retrieved from the cockpit voice recorder in the past 38 minutes of the flight reflects concern over the loss of control on several occasions — on one occasion of laughter of relief when the aircraft appears to stabilise, and finally a distraught pilot calling “Going to ground.”
===========
DGCA suggests design changes in crash report

The Directorate General of Civil Aviation (DGCA) has recommended that the National Aerospace Laboratories (NAL) effect design changes in its first civil aircraft, the 14-seater Saras. In its prototype PT2 version, this aircraft crashed in March 2009 during a test flight.

Releasing the report on Wednesday, the DGCA did not indicate any problems in the engine or turbine but zeroed in on design, indicating that some changes will have to come from the drawing board.

DGCA said it would be appropriate for NAL to consult aircraft manufacturers in conducting flight trials rather than rely on private contractors. It recommended that private contractors be engaged only for supplying parts and certain accessories and the contracting system be reviewed.

Implementing these recommendations and getting them certified could mean the Saras project would be further delayed by a couple of years. A third prototype has been planned and after that, it goes into production.

NAL said it would examine the report and issue a comprehensive clarification on the recommendations.

SARAS FACT FILE

* Saras programme conceived in the 1990s as an Indo-Russian joint collaboration

* Wing Commander K Praveen (pilot), Wing Commander Dipesh K Shah (co-pilot) and Squadron Leader S Ilyaraja (flight engineer) died in the 2009 crash

* Same team and same aircraft performed at Aero India 2009

* The aircraft was completely destroyed

* Villagers in Seshagiri village near the crash site praised the pilots for their presence of mind in averting a major disaster and saving several lives.

To download DGCA report  CLICK HERE.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s