کاروبار · Aviation safetySydney airport taxiway close call: Qantas stopped after Virgin's incomplete readbackتحریری 27 اکتوبر، 2026 کو 5:06 AM UTCدیکھیںنقلِ متن0:07A Qantas crew stopped its jet as a Virgin aircraft crossed in front.0:10A missed radio safeguard preceded the taxiway conflict.0:13The controller was alone in the tower, with a roster that predicted a high fatigue0:17risk.0:17Investigators still have to determine why the flight crew had to prevent a more0:21serious outcome.0:22The conflict happened on August17,2026 .0:25Investigators released their preliminary report on October26.0:28The new development is the investigation's release.0:31More than two months after the aircraft crossed paths on the ground.0:33Virgin flight VA1589 , had diverted from Newcastle because of bad weather and was0:39taxiing towards the domestic terminal.0:40Both aircraft were Boeing seven hundred and thirty-seven seconds.0:43Virgin's registration was VHIXJ, and Qantas's was VHVZV.0:48The conflict developed at about nine forty in the morning.0:51After both jets had landed, Virgin had landed on runway sixteen L and was traveling0:56north on Taxiway B.0:57Quantas had landed on runway sixteen R and was leaving through taxiway B8.1:01Their routes brought them towards the taxiway intersection where Qantas expected1:05Virgin to give way.1:06The controller gave Virgin two requirements in one transmission.1:09Follow Quantas as it left the runway, then stop before runway twenty five.1:13Pilots repeat clearances so the controller can check that they've understood them.1:17In this exchange, the captain's reply included only one of those requirements.1:21The controller said, Follow the Quantas to vacate ahead.1:24Hold short runway20 ,5 quantitative.1:26The captain repeated the hold short instruction.1:29The missing part was the instruction to follow Qantas.1:31The controller didn't catch the incomplete reply and moved on to other tasks.1:35The Qantas flight QF four hundred and twenty crew saw Virgin approaching at a speed1:39that suggested it wouldn't give way.1:40They stopped using normal braking, and Virgin passed in front.1:43The Virgin crew didn't realize there had been a conflict until the Qantas crew1:46queried it with the controller.1:48The controller later told investigators that equipment inside the tower cab limited1:52their view of the intersection.1:53After the occurrence, the controller was removed from duty for the rest of the day.1:57That was the immediate operational response.1:59The radio exchange and the restricted view involved different safety barriers.2:03The readback check didn't expose the missing instruction.2:06Visual monitoring didn't prevent the conflicting movements.2:09The investigation must assess how each circumstance affected what happened.2:13The controller's roster brings a separate question about fatigue risk into that2:16assessment.2:17The scheduled interval between shifts was eight hours and forty minutes.2:21The roster base prediction put fatigue risk at high.2:24The controller described their state as fine and alert and said they were fit for2:27duty.2:28Their actual fatigue remains unresolved.2:30The roster had the controller finishing at eight fifty the previous evening and2:33starting again at five thirty the next morning.2:35That leaves eight hours and forty minutes between scheduled shifts, with travel and2:39other activities taking time too.2:41It doesn't tell us how much the controller slept.2:44Air Services Australia, which provides air traffic control at Sydney, lacked a2:47fatigue management system approved by the Civil Aviation Safety Authority.2:51Air Services acknowledged the interim reports and said it would review the findings2:55once the investigations were complete.2:56Investigators released a second preliminary report concerning an August twenty-five3:00pushback conflict between Jetstar and Quantus Link aircraft.3:03Flight crews and ground staff stopped those movements.3:05Together, the two releases form part of six ongoing close call investigations at the3:10airport.3:10Chief Commissioner Angus Mitchell credited crews and ground staff with identifying3:14the conflicts and acting.3:16Investigators are examining whether staffing contributed to any of the six incidents3:20or whether Air Services was effectively managing it.3:22That question hasn't been settled.3:24The August17 preliminary report contains no analysis, findings, or recommendations.3:29Qantas's recognition and stop protected the aircraft while the Virgin crew remained3:33unaware of the conflict.3:34Investigators still have to weigh the missed raid back.3:36Restricted sight line and roster risk before deciding what changes are needed.3:40A publication date for the final report hasn't been announced.مضمون پڑھیںخبر کی زمانی ترتیبHeyDexمختصر ویڈیو ↗
