ASN Wikibase Occurrence # 310866
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: | Tuesday 4 June 2013 |
Time: | 18:58 |
Type: | Airbus A320 |
Owner/operator: | |
Registration: | |
MSN: | |
Fatalities: | Fatalities: 0 / Occupants: |
Aircraft damage: | None |
Category: | Serious incident |
Location: | Sydney-Kingsford Smith International Airport, NSW (SYD/YSSY) -
Australia
|
Phase: | Approach |
Nature: | Passenger - Scheduled |
Departure airport: | Melbourne International Airport, VIC (MEL/YMML) |
Destination airport: | Sydney-Kingsford Smith International Airport, NSW (SYD/YSSY) |
Investigating agency: | ATSB |
Confidence Rating: | Information verified through data from accident investigation authorities |
Narrative:On 4 June 2013, a Boeing 737-800 (737) aircraft, registered VH-YIR and operated by Virgin Australia (Virgin), was on a scheduled passenger service from Melbourne, Victoria to Sydney, New South Wales. During descent into Sydney, the crew was advised by air traffic control (ATC) to expect an independent visual approach (IVA) to runway 16 Right (16R). As the aircraft approached the extended centre-line of runway 16R, the aircraft’s traffic collision avoidance system (TCAS) provided a traffic alert followed by a resolution advisory (RA) in relation to an Airbus A320 aircraft on approach to parallel runway 16 Left (16L). As the crew commenced descent in response to the RA, the aircraft continued through the extended centre-line of runway 16R by about 300 m. When the TCAS alert ceased, the pilot flying captured the extended runway centre-line from the other side. The flight crew continued the approach and landed, whilst the A320 executed a go-around procedure.
Sources:
ATSB AO-2013-095
Revision history:
Date/time | Contributor | Updates |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation