Preliminary report released.
Investigation: AO-2022-016 - Collision with terrain involving Airbus Helicopters EC130 T2, VH-XWD near Mount Disappointment, Victoria, on 31 March 2022 (atsb.gov.au) OMG. the first heli flew into the cloud first and did a U-turn and the second one followed. . The passenger in the front right seat had flown in helicopters for about 30 years. The passenger recalled that, as they crossed Mount Disappointment, heavy cloud rolled in resulting in ‘a white-out with ground visibility no longer evident’. The pilot radioed XWD and said words to the effect of ‘U‑turn, U-turn, U-turn’. Then the pilot of WVV immediately completed a U‑turn. The pilot of XWD radioed back with words to the effect ‘aren’t we going to cut through?’ The passenger then saw XWD pass just below them |
A major issue was to be crossing Mt Disappointment instead of going around it.
|
Why do people quote reports we can all read?
|
Originally Posted by Capt Fathom
(Post 11229073)
Why do people quote reports we can all read?
|
The Preliminary Report was 9 pages. Those interested will read it.
|
It wouldn’t be much of a thread if there wasn’t any discussion!
“Aren’t we going to cut through” I find to be a very interesting comment if factual. |
One minute....
From the report - Helos leave 30 seconds apart. 0756.30 WWV "U turn" 0757.00 WXD still heading North. 0757.25 Last WXD data point heading North West. crash site 250m. I never thought about VFR cloud clearances expressed as time not distance. There but for the grace of God................. |
Sadly when entering cloud, a VFR machine is often measured in time until impact.
|
I appreciate those who post extracts from reports of these kinds of investigations. Usually the extracts are of the most significant factual findings or flaws in the reasoning.
|
On the very first day there was a quote in the media from possibly the same passenger about being in and out of cloud and the following helicopter not emerging from cloud, so it's no revelation, just confirmation it was not just rumor. As for the future I can only see some significant legal action towards the operator given the passengers involved.
|
As for the future I can only see some significant legal action towards the operator given the passengers involved. Although 500 ft AGL is the minimum for low flying over non-populous areas, 'stress of weather or other unavoidable reason' allows you to go lower if you have to. It is arguable as to when it becomes unavoidable, i.e. could you have turned around and avoided it rather than pressing on, but once down in a valley with scud around, that becomes somewhat academic. The reason I say this it that a legal case against a VFR helicopter operation scud running at low level may be hard to win, given the above. Obviously the 'avoid obstacles' part didn't happen, but things can sneak up on you very quickly. This is not a commentary one way or the other on what should or shouldn't have been done, just saying that you can get into some very compromising situations and still be legal, particulary around hills and particularly when there are wires around too. The onus is very much on pilots as to how far they will push. A decision to turn back will often be delayed due to commercial pressure or simple desire to get through, both understandable, and I think we can all appreciate that what may sound cut and dried when reading accident reports may well have been much more ambiguous to the people involved at the time. How far do I press? How bad is the visibility really? Will it improve over the back of this ridge line or past these hills? Always have an out, as the saying goes, but sometimes your 'out' can disappear before you know it. |
Applicable only if the helicopter is operated: › by day › at a speed that allows the pilot to see obstructions or other traffic in sufficient time to avoid collision |
I think not, what radar and GPS track has the ability to reproduce a picture of exactly what the visibility and cloud was like in any given point to that accuracy? This is micro stuff, not macro.
|
This sad occurrence may also highlight the shameful state of flux our aviation rules are currently in. I don't mean to hijack the thread in any way, but if you consider that even though Part 135 rotorcraft passenger transport regs came into force on 02 December last year but are not 'actually' in force in terms of auditing, ops manual acceptance etc there will be a massive can of worms to work through.
|
Originally Posted by Arm out the window
(Post 11229560)
I think not, what radar and GPS track has the ability to reproduce a picture of exactly what the visibility and cloud was like in any given point to that accuracy? This is micro stuff, not macro.
|
Part 135 rotorcraft passenger transport regs |
Yes, sorry, I should've said Part 133. They blend into one another after a while!
|
AOTW.......all good. The MOS for Part 133 is also worth a look. :ok:
|
Has anyone heard much about this and where the report is at?
I heard a rumour that there is video of the event. |
|
All times are GMT. The time now is 23:45. |
Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.