Détails:
Tara Air flight 197, a DHC-6 Twin Otter 300, impacted a mountainside at 14500 feet while on a domestic flight from Pokhara to Jomsom, Nepal. All 22 occupants suffered fatal injuries.
The flight was the first of five Tara Air flights from Pokhara to Jomsom that day and scheduled to depart at 06:15 hours.
The flight was delayed because the Lete Pass on the route was covered up with clouds. The Twin Otter finally departed at 09:55, after two aircraft of Summit Air had departed for Jomsom.
9N-AET was supposed to take-off as the second flight but the captain seemed hesitant to commence the flight due to a weather report from the first Summit Air flight that, the en-route weather was not favorable for VFR flights and critical around LETE and TATOPANI.
The cockpit voice recording revealed that someone, either ground staff or some intimate passenger to the crew, advised the PIC strongly to conduct the flight.
The aircraft took off from Pokhara from runway 04. The Tower controller instructed to "report 5 DME northwest runway 04". Then after departure the aircraft turned left to maintain a heading of 345 and planned to join heading 305 degree towards Ghodepani. After four minutes, flight 197 reported, "Now on course... 6000 climbing and ETA Jomsom 32" (0432 UTC). At 04:21 UTC flight 197 reported to Pokhara Tower as position approaching Ghodepani 12000 climbing for 12500.
After 6 Seconds ATC Pokhara asked flight 197, "confirm would like to change level and TRA 197 replied, No Ma'am we have crossed Ghodepani and like to be on. Pokhara Tower
instructed, Tara 197 contact Jomsom Tower 122.5
CVR recordings show that after flight 197 crossed Ghodepani, the PIC was not comfortable with the en-route weather. However, the flight was continued following the advice of the preceding Summit Air flight. At 04:26 UTC, flight 197 made the first contact with Jomsom AFS and reported its position to which Jomsom Tower conveyed the prevailing weather as "Wind South Westerly up to 30 kts, QNH 1019, Temp 18º". The PIC of flight 197 reconfirmed twice if the wind was maximum, up to 30 kts and currently South Westerly 25 kts. The crew was discussing about the bad weather being encountered and the PIC himself voiced his dissatisfaction about the behavior of other pilots who conduct VFR flights in such unfavorable weather. The CVR recordings reveal that the aircraft was encountering clouds and the PIC was trying his best to remain clear of the clouds.
The PIC was searching for light and brighter areas and adamantly heading towards it. The aircraft was maintaining 12000 ft and was in a climbing attitude.
During the continuous attempts of crew to avoid the clouds with Terrain Avoidance and Warning System (TAWS) inhibited, the aircraft struck rocky terrain at an altitude of 4050 meters AMSL at Sanusare Mountain.
The cockpit voice recoerder readout showed that the aural GPWS warning, a function of TAWS, was triggered approximately 3 seconds prior to the impact. However, there was no aural warning of enhanced Forward Looking Terrain Alert (FLTA), Premature Descent Alert (PDA), and Imminent Terrain
Impact (ITI) Alert/Warning function of TAWS.
Further investigation of tht TAWS showed that it was configured to use GPS altitude, however no data was received by the system. This was likely caused by the misconfiguration of the RS-232 output format from the Garmin GPS receiver. As a result Corrected Barometric Altitude (CBA), computed by the Air Data Computer (ADC), was the only altitude input. In order to compute a reliable CBA, a regional barometric pressure setting must be entered into the ADC. This had not been done, so during the previous flights the CBA was off by 73 to 866 feet.
Due to an overabundance of nuisance alerts, the TAWS was inhibited.
Probable Cause:
The probable cause of this accident was the flight crew's failure to monitor and maintain the proper course while inadvertently flying in IMC conditions with the aircraft Terrain Avoidance and Warning System [TAWS] inhibited which resulted into a CFIT accident.
Contributing factors:
1. The flight crew's failure to follow the SOP of company
2. The aircraft flight operation with TAWS inhibited during deteriorating en-route weather condition.
3. Loss of situational awareness of crew
4. Deteriorating en-route weather
5. Less experienced copilot for that sector and high crew gradient
6. Poor CRM during the flight
7. The whole cockpit duties [both PF and PM] were undertaken by the PlC, which likely impaired his performance.
8. Underutilization of the available Navigation instruments
» AAIC Press release
FlightAware track
| Statuts: | Accident investigation report completed and information captured |
| Date: | dimanche 29 mai 2022 |
| Heure: | 10:10 |
| Type/Sous-type: |  de Havilland Canada DHC-6 Twin Otter 300 |
| Compagnie: | Tara Air |
| Immatriculation: | 9N-AET |
| Numéro de série: | 619 |
| Année de Fabrication: | 1979-04-21 (43 years 2 months) |
| Heures de vol: | 41336 |
| Cycles: | 71338 |
| Moteurs: | 2 Pratt & Whitney Canada PT6A-27 |
| Equipage: | victimes: 3 / à bord: 3 |
| Passagers: | victimes: 19 / à bord: 19 |
| Total: | victimes: 22 / à bord: 22 |
| Dégats de l'appareil: | Détruit |
| Conséquences: | Written off (damaged beyond repair) |
| Lieu de l'accident: | Sanosware ( Népal)
|
| Élévation des lieux de l'accident: | 4420 m (14501 feet) amsl |
| Phase de vol: | En vol (ENR) |
| Nature: | Transport de Passagers Nat. |
| Aéroport de départ: | Pokhara Airport (PKR/VNPK), Népal |
| Jomsom Airport (JMO/VNJS), Népal | |
| Numéro de vol: | 197 |
Tara Air flight 197, a DHC-6 Twin Otter 300, impacted a mountainside at 14500 feet while on a domestic flight from Pokhara to Jomsom, Nepal. All 22 occupants suffered fatal injuries.
The flight was the first of five Tara Air flights from Pokhara to Jomsom that day and scheduled to depart at 06:15 hours.
The flight was delayed because the Lete Pass on the route was covered up with clouds. The Twin Otter finally departed at 09:55, after two aircraft of Summit Air had departed for Jomsom.
9N-AET was supposed to take-off as the second flight but the captain seemed hesitant to commence the flight due to a weather report from the first Summit Air flight that, the en-route weather was not favorable for VFR flights and critical around LETE and TATOPANI.
The cockpit voice recording revealed that someone, either ground staff or some intimate passenger to the crew, advised the PIC strongly to conduct the flight.
The aircraft took off from Pokhara from runway 04. The Tower controller instructed to "report 5 DME northwest runway 04". Then after departure the aircraft turned left to maintain a heading of 345 and planned to join heading 305 degree towards Ghodepani. After four minutes, flight 197 reported, "Now on course... 6000 climbing and ETA Jomsom 32" (0432 UTC). At 04:21 UTC flight 197 reported to Pokhara Tower as position approaching Ghodepani 12000 climbing for 12500.
After 6 Seconds ATC Pokhara asked flight 197, "confirm would like to change level and TRA 197 replied, No Ma'am we have crossed Ghodepani and like to be on. Pokhara Tower
instructed, Tara 197 contact Jomsom Tower 122.5
CVR recordings show that after flight 197 crossed Ghodepani, the PIC was not comfortable with the en-route weather. However, the flight was continued following the advice of the preceding Summit Air flight. At 04:26 UTC, flight 197 made the first contact with Jomsom AFS and reported its position to which Jomsom Tower conveyed the prevailing weather as "Wind South Westerly up to 30 kts, QNH 1019, Temp 18º". The PIC of flight 197 reconfirmed twice if the wind was maximum, up to 30 kts and currently South Westerly 25 kts. The crew was discussing about the bad weather being encountered and the PIC himself voiced his dissatisfaction about the behavior of other pilots who conduct VFR flights in such unfavorable weather. The CVR recordings reveal that the aircraft was encountering clouds and the PIC was trying his best to remain clear of the clouds.
The PIC was searching for light and brighter areas and adamantly heading towards it. The aircraft was maintaining 12000 ft and was in a climbing attitude.
During the continuous attempts of crew to avoid the clouds with Terrain Avoidance and Warning System (TAWS) inhibited, the aircraft struck rocky terrain at an altitude of 4050 meters AMSL at Sanusare Mountain.
The cockpit voice recoerder readout showed that the aural GPWS warning, a function of TAWS, was triggered approximately 3 seconds prior to the impact. However, there was no aural warning of enhanced Forward Looking Terrain Alert (FLTA), Premature Descent Alert (PDA), and Imminent Terrain
Impact (ITI) Alert/Warning function of TAWS.
Further investigation of tht TAWS showed that it was configured to use GPS altitude, however no data was received by the system. This was likely caused by the misconfiguration of the RS-232 output format from the Garmin GPS receiver. As a result Corrected Barometric Altitude (CBA), computed by the Air Data Computer (ADC), was the only altitude input. In order to compute a reliable CBA, a regional barometric pressure setting must be entered into the ADC. This had not been done, so during the previous flights the CBA was off by 73 to 866 feet.
Due to an overabundance of nuisance alerts, the TAWS was inhibited.
Probable Cause:
Probable Cause:
The probable cause of this accident was the flight crew's failure to monitor and maintain the proper course while inadvertently flying in IMC conditions with the aircraft Terrain Avoidance and Warning System [TAWS] inhibited which resulted into a CFIT accident.
Contributing factors:
1. The flight crew's failure to follow the SOP of company
2. The aircraft flight operation with TAWS inhibited during deteriorating en-route weather condition.
3. Loss of situational awareness of crew
4. Deteriorating en-route weather
5. Less experienced copilot for that sector and high crew gradient
6. Poor CRM during the flight
7. The whole cockpit duties [both PF and PM] were undertaken by the PlC, which likely impaired his performance.
8. Underutilization of the available Navigation instruments
Accident investigation:
|
Sources:
» kathmandupost.com» AAIC Press release
Opérations de secours
Nepal AAIC issued 10 Safety Recommendations
Show all...
Show all...
Photos
FlightAware track
Video, social media
Crash site: Sanosware, Thasang-2, Mustang pic.twitter.com/OcN93N1Qyb
— NASpokesperson (@NaSpokesperson) May 30, 2022
Plan
Ce plan montre l'aéroport de départ ainsi que la supposée destination du vol. La ligne fixe reliant les deux aéroports n'est pas le plan de vol exact.
La distance entre Pokhara Airport et Jomsom Airport est de 69 km (43 miles).
Accident location: Exact; as reported in the official accident report.
La distance entre Pokhara Airport et Jomsom Airport est de 69 km (43 miles).
Accident location: Exact; as reported in the official accident report.
Les informations ci-dessus ne représentent pas l'opinion de la 'Flight Safety Foundation' ou de 'Aviation Safety Network' sur les causes de l'accident. Ces informations prélimimaires sont basées sur les faits tel qu'ils sont connus à ce jour.
languages: 
Népal
Share
DHC-6 Twin Otter
- 930+ built
- 285ème loss
- 183ème accident fatal
- le accident 6ème le plus grave (à ce moment là)
- le accident 6ème le plus grave (en ce moment)
Népal- le accident 9ème le plus grave (à ce moment là)
- le accident 10ème le plus grave (en ce moment)
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2023 Flight Safety Foundation