Melburnian1
Veteran Member
- Joined
- Jun 7, 2013
- Posts
- 25,256
Hi M1, am on 93 today.
The problem is a bird strike was identified on the walk around. Captain advised not a safety issue, but paperwork needed to send us on way.
At 9.30 told it would be probably be another hour...
Terrific post. The QF website 'flight status' hasn't caught up with that. Your delay may - I stress 'may' - mean a delay to the Saturday 4 May QF11 from LAX to JFK if it is held for connecting passengers ex MEL, and if so, a delay to the Saturday QF12 ex JFK and then QF12 to SYD and QF16 to BNE (which is why sometimes when there's such a delay, those from MEL are instead placed on AA flights across to JFK).
Good that the flight crew informed you, as their focus is on completing the documentation. Can such a report be submitted online by them?
Thank goodness it was not a more severe bird strike. While there are more flights operating than a decade ago, the number of bird strikes has risen in raw terms (though perhaps not when considered against the rise in aircraft movements).
However given there are far fewer aircraft movements at airports such as Darwin, Gold Coast or Townsville than there are at the 'big three' east coast capital city airports, it's more likely that a plane will be affected by bird strikes at these smaller airports:
Australian planes hit more than 16,000 birds in the past 10 years
One can't be definitive because a VA plane was recently hit by a flock of galahs in central Australia (ASP) but it'd be logical to expect more bird strikes at coastal airports in Australia's north where typically tropical or sub-tropical vegetation and higher rainfall means more birds per square kilometre around airports (even though airports are at pains to make their immediate enviironment as unattractive as possible to our feathered friends):
18 galahs hit as commercial airliner lands in Central Australia
Last edited: