Safety & OperationsClearance sheet
737 freighter rejected take-off at 139kt after safety vehicle entered runway
ATSB final report: a 737-800BCF rejected its take-off at 139kt at Melbourne after a safety vehicle crossed runway 34 during night works, exposing briefing and marking failures.
Read-back
- Team Global Express 737-800BCF ZK-TXB rejected take-off at 139 knots on runway 34 at Melbourne, 17 February 2026, about 04:45.
- Safety vehicle crossed when the aircraft was roughly 400 metres from the intersection; the 737 passed through at an estimated 70–80 knots.
- ATSB cites an incomplete pre-shift works briefing and changed unserviceability light positions as contributing factors.
- CASA plans to amend two advisory circulars on aerodrome works after findings on inadequate marking distinction.
- Melbourne Airport did not risk assess all stages of the runway overlay project; it has since strengthened airside works management.
A Team Global Express Boeing 737-800BCF performed a high-speed rejected take-off at 139 knots after an airport safety vehicle crossed the active runway ahead of it at Melbourne Airport, the Australian Transport Safety Bureau has found.
The freighter, registered ZK-TXB, was departing runway 34 at about 04:45 on 17 February 2026 on a scheduled freight service to Adelaide when the vehicle "inadvertently entered the active runway", investigators stated in their final report.
How did the incursion unfold?
"As the 737 was lining up on runway 34 for a scheduled freight service to Adelaide, the driver of the airport safety vehicle was retrieving unserviceability markers and lights along runway 09/27, so it could be re-opened [following maintenance]," said ATSB chief commissioner Angus Mitchell.
After the aircraft began its take-off roll, the airside safety officer drove the vehicle, with a trailer in tow, onto runway 34. The incursion triggered an electronic alert in the tower, prompting the controller to order the vehicle off the runway and the aircraft to stop.
The pilot in command, who was the pilot flying, recalled spotting the vehicle at the same moment the ATC instruction arrived, and initiated the rejected take-off at 139 knots. The vehicle accelerated and cleared the runway when the 737 was roughly 400 metres from the intersection. The aircraft then passed through that intersection at an estimated 70–80 knots.
The margin, in other words, was seconds rather than minutes.
Why did the driver cross?
Mitchell said the airside safety officer had misidentified their position on runway 09/27, believing they were crossing an adjacent taxiway.
"The airside safety officer was experienced in night-time maintenance works but was operating in a complex airside environment in the dark," he said.
Two failures compounded the darkness. The positioning of unserviceability lights had changed when the works plan progressed the night before the occurrence, and the pre-shift briefing did not include the required review of the local works plan. The officer therefore held an incomplete understanding of the revised works.
The ATSB also found that the available visual cues did not sufficiently distinguish the active runway intersection from other crossings within the works area.
"Civil Aviation Safety Authority guidance did not require sufficient distinction between these markings to mitigate the greater potential consequences associated with inadvertently entering an active runway," said Mitchell. CASA plans to amend relevant sections of two advisory circulars on aerodrome works in response.
What changes at Melbourne Airport?
The investigation further found, though it did not contribute to the incident, that Melbourne Airport did not risk assess all stages of the runway overlay project during its development. The airport has since taken several steps to strengthen airside works management, aimed at reducing the likelihood of future runway incursions.
Mitchell framed the event within a wider problem. "Runway incursions are a global safety concern," he said. He noted one mitigation worked as designed: the airport vehicle carried a transponder, and its entry onto the runway triggered the alert that allowed timely controller action.
The episode nonetheless shows how airport works can substantially alter the visual cues that flight crews and airside vehicle operators rely upon. "Effective worksite controls must provide clear and distinct indications of the boundary between active and inactive runways when temporary works alter or remove normal runway and taxiway cues," Mitchell said.
The ATSB last month opened a separate investigation into an October near-miss at Townsville between a Jetstar aircraft and a van, suggesting the Melbourne findings will be read well beyond one airport.
via australianaviation.com.au (Source)
More from Grace Kim
Show full bio
News editor covering companies, deals and strategy in Commercial aviation industry coverage at Flightdeck Report.
692 articles
Same bay
- Amazon suspends 21 Air after freighter overruns Miami runway · October 9, 2026
- BA 787-10 Leaves Taxiway at Heathrow, Cancels Lagos Flight · November 18, 2026
- Delta CRJ-900 returns to JFK after 20-minute smoke response · November 16, 2026
- Aer Lingus A330 Returns to Dublin After Double Weather Radar Failure · November 10, 2026
- United 737 MAX 9 Squawks 7500 After Cockpit Breach Attempt · November 10, 2026