ASN Wikibase Occurrence # 199503
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Monday 21 August 2017 |
| Time: | c. 10:10 UTC |
| Type: |  Airbus A321-211 |
| Owner/operator: | Air India |
| Registration: | VT-PPL |
| MSN: | 3752 |
| Year of manufacture: | 2008 |
| Engine model: | CFMI CFM56-5B3/P |
| Fatalities: | Fatalities: 0 / Occupants: 171 |
| Aircraft damage: | None |
| Category: | Serious incident |
| Location: | 40 nm east of Mumbai -
 India
|
| Phase: | En route |
| Nature: | Passenger - Scheduled |
| Departure airport: | Varanasi Airport (VNS/VIBN) |
| Mumbai-Chhatrapati Shivaji International Airport (BOM/VABB) | |
| Investigating agency: | AAIB India |
| Confidence Rating: |  Accident investigation report completed and information captured |
Air India flight AIC696 (Varanasi-Mumbai), an Airbus A320 registered VT-PPL was vectored towards southeast of Mumbai.
At the same time Jet Airways flight JAI426 (Calicut-Mumbai), a Boeing 737-800 registered VT-JBE, was in ORBIT east of airway MB394 and heading towards MB394 while AIC696 was approaching MB394 on an easterly heading.
An airprox occurred in the vicinity of MB394 between FL100 to FL120. JAI426 reported getting a TCAS RA (Resolution Advisory) whereas AIC696 reported getting a TCAS-TA (Traffic Advisory).
JAI426 (at FL120) which was 12 NM ahead of AIC696 (maintaining FL110.), was given a right orbit along with descent instructions to FL100 by the Radar Controller. JAI426 thus came in front of AIC696 and descending through the level of AIC696. The separation was reduced to 2.3 NM (horizontal) and 400 feet vertical.
CONCLUSION
The incident happened in the proximity of way point MB394 which is within 40 NM of the MUMBAI and was in Class-C airspace. The density of traffic was high.
Incident happened due to momentarily loss of situational awareness while issuing a descent instruction to JAI426 which was orbiting. There was a delay in detecting the conflict.
The controller lacked situational awareness and basic radar vectoring techniques. It was seen during radar reply that the controller was lacking in Radar Label Management. The controller was more involved in arrival sequencing though AIC696 and JAI426 were almost in opposite direction when the incident occurred./
Accident investigation:
 |
|
Sources:
https://www.bea.aero/en/investigation-reports/notified-events/detail/event/perte-de-separation-entre-deux-avions-en-croisiere-avis-de-resolution-tcas/
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 08-Sep-2017 19:34 | harro | Added |
| 10-May-2023 14:09 | harro | Updated |
Corrections or additions? ... Edit this accident description
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:
©2024 Flight Safety Foundation