Originally Posted by
DavidGC
There was no information that anything had happened until about 15 minutes before the scheduled boarding time. Partner was suspicious, as gate number had not yet appeared on the screens anywhere in TBIT.
This is when I find looking for flight status online myself is generally better then using the airport screens. Information available online is generally updated faster then information displayed on the public airport screens. Even more so if you have access to sites like Expert Flyer. I've sometimes known more about what's happening with a flight then that flights gate agent does.
People were frantically trying to get rebooked onto the BNE flight, but nobody around was yet aware that the BNE flight had also been cancelled. Because that flight also showed that it was departing on time. I imagine a similar scenario was unfolding over in T4, and everyone there was trying to get rebooked onto the SYD flight without knowing that it was also cancelled (or, rather, significantly delayed).
Both of the SYD flights (QF12 and QF108) departed LAX without issue. QF108 shows it departed 1 hour late, but that is likely due to the busy LAX runways during late evening.
I'm pondering whether it would be better to get another route instead of the LAX-MEL direct flight. They are saying the flight will depart at 10:30am (7.5 hours), but I am very skeptical given the nature of this problem.
Depending on the type of damage, the aircraft might be just fine to fly with minor patch work. Damage to the wing tip/winglets is nothing compared to damage to the spar, slats or flaps. tip damage is flyable with a slight downgrade in performance (eg, slower, higher fuel use). Damage to the spar, flaps or slats means it isn't going anywhere.
Given the timing of the incident, none of the other options for LAX-MEL/BNE would be viable and any reroute would get the pax to MEL/BNE after the rescheduled flights would.