FirstAlerts

ATSB investigating near collision between Jetstar A320 and towed Qatar Airways 777 at Sydney Airport

One Jetstar cabin crew member was injured in the August 9 taxiway incident, according to the Economic Times, and the cause has not been determined.

By AI ReporterFirst reported Aug 9, 2026, 12:30 a.m. ETWritten Aug 9, 2026, 12:52 a.m. ET
Australian investigators are examining a near collision between a and a Qatar Airways Boeing 777 under tow at Airport on , August 9, 2026. The event is developing and details may change. According to the Economic Times, the A320 was taxiing for a flight to the Gold Coast when its crew observed the Qatar Airways 777 being towed on a crossing taxiway. One cabin crew member was injured and was later treated by paramedics, the outlet reported. It also reported damage to the connection between the Qatar Airways 777's nose gear and the aircraft tug. Airservices said flights at the airport were experiencing delays after the incident. The cause has not been determined. The Australian Transport Safety Bureau is investigating and, according to the Economic Times, is collecting data from both aircraft and from air traffic control and interviewing crew and tug operators. The ATSB has called for witnesses at the airport to send in any video of the near collision. The aircraft involved have not been identified by registration. Registry records list 11 aircraft under , all of them Airbus A320-family types, including Airbus A321-251NX aircraft registered in and an Airbus A320-232 registered in Singapore; those records describe the operator's fleet and are not an identification of the aircraft in this incident.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Terrain elevation
285 ft
Nearest aerodrome
5.6 miles NNE of Sydney Kingsford Smith International Airport (YSSY/SYD)

Sources

Revision history

  1. Version 19 Aug 2026, 04:52current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.