Jump to Content
Download Final Report
[ Download PDF: 15KB]
 
 
 
The crew had been issued a runway 34R MARUB2 SID with a requirement to maintain 5,000 ft and had confirmed this altitude on contact with Departures North. The aircraft was then observed on radar to climb above the assigned altitude. The controller confirmed the altitude requirement and passed traffic information on a crossing A320 at 6,000 ft. The B737 crew immediately descended from 5,400 ft to 5,000 ft. Concurrently the crew of the A320 responded to a TCAS Resolution Advisory and climbed from 6,000 ft to 6,700 ft. A plot of the recorded radar data showed that the B737 had levelled at 5,400 ft and that the two aircraft had come within 600 ft of one another. The required standard was 1,000 ft and, therefore, an infringement of separation standards had occurred. The company operating the B737 conducted an investigation into the circumstances surrounding this incident and a copy of their report was duly lodged with the Bureau. Their investigation found that a captain under training was flying the aircraft. A training captain occupied the right crew seat and performed the crew functions of the pilot not flying. The captain under training was hand-flying the aircraft at the time of the incident. Although he had correctly set the assigned altitude of 5,000 ft in the window of the Mode Control Panel, the Flight Director (FD) did not capture the 5,000 ft level-off altitude and, despite the training captain having alerted him to the approaching assigned altitude, he had allowed the aircraft to climb above the assigned 5,000 ft altitude. An intermittent fault in the altitude selection function of the FD had been detected a few days earlier but because the problem was not thought to be an aberrant operation, it was not reported. After this occurrence the problem was reported and a few days later manifested itself in a 'hard' failure. The Mode Control Panel of the Flight Management System was subsequently replaced. The investigation concluded that the slow response of the captain under training had allowed the aircraft to exceed the assigned altitude. The company's Standard Operating Procedures were found to be adequate and, despite this event, did not require amendment. However, a recommendation was made that training captains require pilots under training to use greater levels of automation in busy flight phases in order to enhance their monitoring role.
Download Final Report
[ Download PDF: 15KB]
 
 
 
 
General details
Date: 05 July 1999 Investigation status: Completed 
Time: 10:13 EST Investigation type: Occurrence Investigation 
 Occurrence type:Loss of separation 
 Occurrence class: Airspace 
Release date: 28 September 1999 Occurrence category: Incident 
Report status: Final  
 
Aircraft 1 details
Aircraft manufacturer: Airbus 
Aircraft model: A320-211 
Aircraft registration: VH-HYF 
Sector: Jet 
Damage to aircraft: Nil 
Departure point:Brisbane Qld
Destination:Sydney NSW
Aircraft 2 details
Aircraft manufacturer: The Boeing Company 
Aircraft model: 737-300 
Aircraft registration: ZK-FDM 
Sector: Other 
Damage to aircraft: Nil 
Departure point:Sydney NSW
Destination:Dunedin New Zealand
 
 
 
Share this page Provide feedback on this investigation
Last update 28 October 2014