Airprox Serious incident Boeing 747SP-38 VH-EAA, Monday 9 October 1995
ASN logo
 

Date:Monday 9 October 1995
Time:c. 8:10 LT
Type:Silhouette image of generic B74S model; specific model in this crash may look slightly different    
Boeing 747SP-38
Owner/operator:Australia Asia Airlines
Registration: VH-EAA
MSN: 22495/505
Year of manufacture:1981
Fatalities:Fatalities: 0 / Occupants:
Other fatalities:0
Aircraft damage: None
Category:Serious incident
Location:17 KM East of Sydney -   Australia
Phase: Approach
Nature:Passenger - Scheduled
Departure airport:Auckland Airport (AKL/NZAA)
Destination airport:Sydney-Kingsford Smith Airport, NSW (SYD/YSSY)
Investigating agency: BASI
Confidence Rating: Accident investigation report completed and information captured
Narrative:
VH-EAA was processed into the Sydney Terminal Area by the Approach south radar control sector, and was tracking via the 094 VOR radial, on descent to 6,000 ft in visual conditions. At 9 DME, the flight crew, in response to a TCAS RA alert, climbed the aircraft approximately 300 ft. They did not advise ATC of the alert.

VH-NEK had departed runway 16L, on initial climb to 5,000 ft, and was being processed to depart the Sydney Terminal Area by the Departures south radar control sector. The aircraft was vectored onto a north-easterly track from a left turn after take-off.

Recorded radar information indicated that VH-EAA had continued descent to a pressure altitude of 5,700 ft and VH-NEK had climbed to a pressure altitude of 4,900 ft. When their flight paths crossed, VH-EAA was 800 ft above, and 1.86 NM to the right of VH-NEK.

The traffic management plan, techniques and procedures, for processing both aircraft were adequate to maintain prescribed separation standards and tolerances in accordance with the runway 16 airspace agreement. However, neither controller had recognised the incident, probably due to the short duration of the encounter, and the lack of advice from either flight crew.

Findings:
1. The traffic management procedures adopted by the controllers for processing the aircraft were adequate.

2. VH-EAA descended below the assigned altitude.

3. In response to the TCAS RA alert, the flight crew returned the aircraft to the assigned altitude.

Probable Cause:
The required separation standard was infringed when the flight crew permitted VH-EAA to descend below their assigned altitude.

Accident investigation:
cover
  
Investigating agency: BASI
Report number: 
Status: Investigation completed
Duration: 2 months
Download report: Final report

Sources:

https://www.atsb.gov.au/sites/default/files/media/4933293/199503410.pdf

https://www.jetphotos.com/photo/5665069 (Photo)

Location

Revision history:

Date/timeContributorUpdates
13-Oct-2025 11:19 Justanormalperson Added
13-Oct-2025 11:20 Justanormalperson Updated
13-Oct-2025 11:22 Justanormalperson Updated
13-Oct-2025 11:36 Justanormalperson Updated [Operator, ]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2025 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org