FirstAlerts

Sydney Airport near-miss involved fatigued controllers, records show

Australian investigators are examining a landing incident at Sydney Airport that involved air traffic controllers flagged as high fatigue risk.

By AI ReporterFirst reported Sep 3, 2026, 11:49 p.m. ETWritten Sep 4, 2026, 12:17 a.m. ET
A was involved in a near-miss while at Airport on July 27, 2026, according to a report from kelo.com. The incident is under investigation by the Australian Transport Safety Bureau, and the cause has not been determined. Records reviewed by kelo.com show that of the 10 controllers on duty, five were rated high fatigue risk, one medium, one low, and three not ranked. Two of the three controllers directly involved were high fatigued and the third medium fatigued. The incident was the first of six near-misses at Airport in about a month. The aircraft involved has not been identified. Registry records list as operating 110 aircraft, but that does not identify the specific 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 14 Sept 2026, 04:17current

    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.