Jump to Content

Summary

Summary

Updated: 25 August 2017

Completion of this investigation has been delayed by the involvement of the investigator in charge and reviewers on other investigations and tasks. The draft is now anticipated for release to directly involved parties (DIP) for comment in September 2017. Feedback from those parties over the 28‑day DIP period on the factual accuracy of the draft report will be considered for inclusion in the final report, which is anticipated to be released to the public in November 2017.

 

Updated: 19 December 2016

The additional investigative work has been finalised and relevant content incorporated into the draft investigation report. That draft is now anticipated for release to directly involved parties (DIP) for comment in January 2017. Feedback from those parties over the 28-day DIP period on the factual accuracy of the draft report will be considered for inclusion in the final report, which is anticipated to be released to the public in April 2017.

 

Updated: 18 August 2016

Completion of the draft investigation report has been delayed due to competing team member priorities and workload, and to allow additional investigative work to be finalised. The draft report is now anticipated for release to directly involved parties (DIP) for comment in October 2016. Feedback from those parties over the 28-day DIP period on the factual accuracy of the draft report will be considered for inclusion in the final report, which is anticipated to be released to the public in December 2016.

 

12 February 2015

The ATSB has commenced an investigation into an operational event involving an Airbus A320-232, VH-VND, at Melbourne Airport, Victoria, on 11 February 2015. After reporting ‘visual’ the flight crew was cleared by the Melbourne Approach controller for a visual approach and directed to contact the Tower controller. The approach controller, on observing the aircraft on radar descend towards the lower limit of controlled airspace in that area of 1,500 ft, requested the Tower controller to issue a safety alert to the aircraft. In response, the flight crew initiated a climb to 2,000 ft before completing their approach.

The investigation is continuing and will involve interviewing the flight crew, analysing recorded flight and other data and gathering and examining additional information.

 
Share this page Comment