What happened in flight 6E-2142 between Pakistan’s nefarious plans and storms, all in DGCA report

[ad_1]


DGCA Report on IndiGo Flight 6E-2142: 21 May. Day Wednesday. In flight 6E-2142 going from Delhi to Srinagar, 220 passengers were on their journey. The aircraft was diving in the air, the passengers inside were enjoying their pleasant journey, suddenly strong thunderstorms, storms and hailstorms faced the aircraft and shouts inside the flight. Many warnings are issued from the aircraft. Given the difficult situations, pilots request Pakistani airspace for an emergency route, but Pakistan rejects it. Then the aircraft had to get down at the rate of 8,500 feet per minute. This is just the beginning. The new reports of this accident have come, they are even more shocking.

DGCA told full details

New details of the accident suggest that the aircraft faced serious in-flight emergency after flying in a strong thunderstorm. The details mentioned by the Directorate General of Civil Aviation Monitoring Institute Civil Aviation (DGCA) show that the pilots were struggling with many cockpit warnings and equipment failures after entering hailstorm. At one time, the IndiGo A321NEO aircraft operated as flight 6E-2142 fell 8,500 feet per minute. While the normal rate of landing is 1,500 to 3,000 feet per minute. According to the initial report of the DGCA, the aircraft flying over 220 passengers including Members of Parliament was at an altitude of 36,000 feet, when the India-Pakistan border got stuck in adverse weather conditions near Pathankot near the border.

Pakistan refuses request

According to the statement of the crew given to the DGCA, the flight team further identified a lot of bad weather and made an immediate request for deviation to the left from the northern control of the Indian Air Force, making the aircraft move to Pakistani airspace for some time. That request was rejected. Subsequently, the flight crew approached Lahore Air Traffic Control directly and sought permission to enter Pakistani airspace for some time to avoid the storm. This request was also rejected.

Due to limited options and rapid storm, pilots initially consider returning to Delhi. However, by then the aircraft had already reached very close to the clouds. Given the proximity and possible threats, the crew decided to penetrate the weather directly to move towards Srinagar.

Video of time of dreadful accident

At the time of storm

At the time of storm, the aircraft faced a large number of hail. Many important systems of the aircraft began to mark the malfunction. The initial assessment of the DGCA confirms that the aircraft had a malfunction for the angle of attack (AOA) while the alternative law protection was lost. These failures were triggered by the aircraft flight control system of the aircraft as the aircraft was bouncing vertically (vertically) by rapid updraft and dowdraft. Amidst this chaos, the autopylot stopped working. The crew was forced to handle full manual control under rapid ups and downs aerpeed signals and excessive stress.

There came a time when the aircraft started landing at a rapid pace at a rate of 8,500 feet per minute. This crisis became even more complicated when the aircraft was warned several times and alerted that the aircraft was getting closer to its maximum operating speed and MAC number. The pilots kept the jet stable until it exited the weather system, relying on manual flight skills. The aircraft continued to move towards Srinagar in the same direction to get out of the storm in the shortest time.

Understand warnings like this

Angle of Attack (AOA) sensor malfunction, possibly can disrupt the stall warning system due to hailstorm, which alerts pilots with light, voice or vibration when the wing’s angle is at risk of stalls for airflow, where the aircraft loses lift and control. In this situation, the fly-wise system of Airbus A321 switched to alternative law, disabled security such as stalls and overspeed security measures. Alternative Law is a poor flight control mode in the Airbus fly-by-wire system, where some automatic security such as stalls and overseas security measures disable, which requires more direct pilot control. Possibly stalls and maximum speeds were given due to incredible readings of air level from the blocked pitot tubes (which measure air level).

Between severe disturbance, A321 descended rapidly at a speed of 8,500 feet per minute in a phase, which was more than the normal 1,500–3,000 feet per minute for a standard outlook. After the trip to the autopylot system, the pilots declared Jetliner manually to Srinagar and made a safe landing.

Emergency had to be declared

When stable, the crew completed all electronic centralized aircraft monitoring (ECAM) Checklist Action and declared “PAN PAN” – this is an international standard urgency signal, which someone in the vehicle uses to declare an emergency. Srinagar ATC directed the flight during the final decent. Despite the first system malfunction, the aircraft landed safely in Srinagar without any other incident.

Assessment of damage

After landing, the standard inspection performed after the flight has caused considerable damage to the aircraft’s nose con, especially the Radom, which has the weather radar and which is sensitive to the effect of hailstorm. There is no information about the injuries of passengers or any member of the crew. DGCA has confirmed that the incident is being formally investigated. Indigo and regulatory technical teams are currently assessing both flight data and cockpit voice recording.

Video of time of dreadful accident

Passenger riding aircraft

Passengers aboard the aircraft also included a five -member delegation of the Trinamool Congress (TMC), including MP Derek O Bryan, Nadimul Haq, Manas Bhaunia, Mamta Thakur and party spokesperson Sagarika Ghosh.

After landing, Sagarika Ghosh said, “It was a close experience of death. People were shouting, praying, nervous. Salute to the saving pilot.”

Ghosh’s talk matches the video footage inside the cabin, which later surfaced on social media. Passengers were seen holding the seats, many people appeared upset, some were praying. IndiGo confirmed in a statement that a compulsory inspection and maintenance of the aircraft was being done before approving further operations.


(Tagstotranslate) Lahore Atc (T) IndiGo Flight 6E-2142 (T) DGCA REPORT on IndiGo Flight (T) Pakistan Indigo Controversy (T) IndiGo Flight 6E -2142 Delhi to Srinagar (T) ATC (T) Indigo Flight 6E-2142 (T) DGCA report (T) Pakistan Indigo Controversy (T) Indigo Flight 6E-2142 Delhi to Srinagar (T) DGCA told the entire details & nbsp; (T) Pakistan refused requests Understand (T) Emergency had to be declared (T) Assessment of damage (T) A video of the passenger (T) a video of the creepy accident

[ad_2]

Leave a Reply

Your email address will not be published. Required fields are marked *