Airservices Adds 'Follow' to Mandatory Readbacks from 26 November
From 26 November, Airservices' change notice adds follow-instruction readbacks in MATS section 9.2.2 and AIP GEN 3.4. The ATSB's 17 August Sydney taxiing-conflict report is still preliminary.
Organizational byline
Updated November 19, 2026
4 min read
News. From 26 November 2026, Airservices Australia's manual and the Aeronautical Information Publication pick up a readback change that includes "follow" instructions. The notice that says so is National Information Circular 09/2026. The Sydney taxiing conflict that put the same change into a public investigation file is still a preliminary report. It is not a finding.
An earlier note on Sydney runway incursions is here: ATSB reviews Sydney runway incursions. The 17 August occurrence below is a taxiing conflict between two Boeing 737s. The bureau's preliminary report does not call it a runway incursion.
What the preliminary report says happened
The report is investigation AO-2026-093. The ATSB released it on 26 October 2026 and labels it preliminary. The cover note says it sets out evidence gathered so far and areas of further work. It says it does not contain analysis or findings. Those will be in a final report. The summary says the investigation is active, in examination and analysis, with anticipated completion in the first quarter of 2027. No one was hurt. Damage is listed as nil.
On the morning of 17 August 2026, Virgin Australia Boeing 737-800 VH-IXJ, flight VA1589, was going from Melbourne to Newcastle and diverted to Sydney. The report says it landed on runway 16L at 0933. Qantas Boeing 737-800 VH-VZV, flight QF420 from Melbourne, was on approach to runway 16R.
At 0940 the surface movement controller east told the VA1589 crew to "follow the Qantas to vacate ahead, hold short runway 25." The captain read back "hold short of runway 25" and did not read back "follow the Qantas." The report says the controller did not recognise the incomplete readback. The QF420 crew were on Sydney Tower's frequency and did not hear that exchange.
Vacating via taxiway B8, the QF420 crew saw VA1589 approaching the B/B8 intersection at a speed that indicated it would not give way. They stopped with normal braking and asked if they were to give way. The controller said VA1589 should have given way, and that QF420 should now follow VA1589. The report says the VA1589 crew learned of the conflict from that question, by which time VA1589 was already passing in front. Both taxied in. The transcript times the instruction at 0940:21 and the readback at 0940:28. The summary lists 0941 Australian Eastern Standard Time.
That is the preliminary report's account of the evidence. The ATSB has not published findings on why the readback was incomplete or why it was not corrected.
The ATSB's 26 October news release, covering this report and a separate 25 August pushback conflict, says the preliminary reports do not contain findings and analysis. Chief Commissioner Angus Mitchell is quoted saying crews and ground staff caught the conflicts, and that the bureau's job is to establish why those actions were needed. He also said the bureau has not yet determined whether staff resourcing contributed to any of six Sydney occurrences, or whether those conditions were being managed. This article does not treat roster or fatigue notes in the VA1589 file as a cause.
Where the readback change is written down
In the safety-action section of the same preliminary report, the ATSB says Airservices reviewed MATS and AIP guidance on "follow" clearances in response to safety issue AO-2025-033-SI-01. On 17 September 2026, the report says, Airservices told the ATSB that the review had led to a decision to change MATS 9.2.2.13.2, and the related AIP reference GEN 3.4, so that the instruction "follow" is in the list of items requiring readback. The report says those changes will be implemented on 26 November 2026.
The report records that advice. It does not quote the amended sentence.
Airservices' own notice is NIC 09/2026, issued 2 November 2026. It says MATS version 78 and AIP Book amendment 129 take effect on 26 November 2026. The MATS table row "Follow instruction readback" says "Inclusion of safety-related requirements within readbacks," section 9.2.2, change request 53875. The AIP summary says phraseology updates for the added follow readback requirements include GEN 3.4 paragraphs 5.4, 6.3, 6.4, 6.9, 6.14, 6.15, 6.16 and 7.5.
The circular does not print the new readback list. The paragraph number 9.2.2.13.2 is the one Airservices gave the ATSB. The circular's table stops at section 9.2.2.
The earlier safety issue named in the report is AO-2025-033-SI-01. The 17 August Sydney conflict is AO-2026-093. The preliminary report places the readback change under the safety action for the Sydney investigation, and it says the review was in response to the earlier safety issue. Both of those sentences are in the preliminary report. The final report on 17 August is not out.