Advertisement
Help Keep Boards Alive. Support us by going ad free today. See here: https://subscriptions.boards.ie/.
https://www.boards.ie/group/1878-subscribers-forum

Private Group for paid up members of Boards.ie. Join the club.
Hi all, please see this major site announcement: https://www.boards.ie/discussion/2058427594/boards-ie-2026

Rescue 116 Crash at Blackrock, Co Mayo(Mod note in post 1)

1115116118120121136

Comments

  • Registered Users, Registered Users 2 Posts: 1,980 ✭✭✭Growler!!!


    BoatMad wrote: »
    reasons to why the light itself wasnt seen ( or recognised ). The issue with the EGPWS is in effect resolved in that regard

    It would be very difficult to distinguish between the flash from the lighthouse and the flash from the aircraft strobe light also taking into account the whiteout effect of the landing lights while flying in IMC. Also the pilots would have been looking inside at their instruments while flying in these conditions.

    You mentioned stats about the lighthouse. Did it mention the power output in Lux or Candella?


  • Registered Users, Registered Users 2 Posts: 1,897 ✭✭✭Means Of Escape


    I would very much hope that this tragic event might finally force the politicians to properly resource the Air Corps. Time and time again we've kicked this can down the road, huffed and puffed, and generally acted the eejit. SAR services undertaken by a private operator is one thing but our Air Corps should have the capability to assist, provide top cover and general back up as necessary.

    It's time to finally join the dots.

    Remove post to new thread


  • Closed Accounts Posts: 558 ✭✭✭Biggest lickspittle on boardz


    I'd say it's time to close this thread, it has turned into a North Korean parody at this stage. The natural ebb and flow of human conversation and discussion is not even being allowed, what's the point any more? Everything that has been allowed to be said, has been.


  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    Growler!!! wrote: »
    It would be very difficult to distinguish between the flash from the lighthouse and the flash from the aircraft strobe light also taking into account the whiteout effect of the landing lights while flying in IMC. Also the pilots would have been looking inside at their instruments while flying in these conditions.

    You mentioned stats about the lighthouse. Did it mention the power output in Lux or Candella?

    We have debated this issue over some considerable numbers of posts. I dont think there is anything new to say, which again is why hopefully the final report may add some expert perspective on this

    Again , Its not the key issue, on the key issue , ( in essence a navigation issue ) I think that there is sufficient information to form a conclusion.

    I say its not the key issue, because if they had detected the rock, and avoided it , the main issue still remains


  • Registered Users, Registered Users 2, Paid Member Posts: 8,421 ✭✭✭plodder


    BoatMad wrote: »
    The issue with the EGPWS is in effect resolved in that regard
    When you say "resolved in that regard", do you mean that they have issued an interim safety recommendation, and that's the end of it? I would hope that is not the end of it, because it doesn't look likely to be within CHC's competence to review the data sources for Honeywell's terrain database.

    “The beginning of wisdom is to call things by their proper name.” - Confucius



  • Advertisement
  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    plodder wrote: »
    When you say "resolved in that regard", do you mean that they have issued an interim safety recommendation, and that's the end of it? I would hope that is not the end of it, because it doesn't look likely to be within CHC's competence to review the data sources for Honeywell's terrain database.

    The interim safety recommendation was nothing to do with the EGPWS, rather a review of operator routes , based on the fact that this one had a 300 foot rock at the start of the recommended route .

    I suspect that was because , as was mentioned elsewhere , these routes were drawn up long before reliable GPS locations fixing and is quite common too place a waypoint near or at an identifiable location .

    This has the unfortunate issue with the arrival of high performance position fixing , in boat navigation , where historically , a waypoint might use a nav buoy , and now people just program up the waypoint and the accuracy is such that they run into the same buoy. !!!

    The issue is that the EGPWS was not going too save the crew ( cause the data wasn't present ) , and expert discussion elsewhere suggest even if the feature was in the database its unlikely to have reported it in time any way .

    Hence , its " resolved" in that it it place no part in providing the crew with any info

    A bigger issue surrounds the use of the radar , that certainly needs investigation , to determine if there are SOP or training or equipment issues here . But again this is not the kernel of the accident, even if it is a question that hopefully will be answered


  • Registered Users, Registered Users 2, Paid Member Posts: 8,421 ✭✭✭plodder


    BoatMad wrote: »
    Hence , its " resolved" in that it it place no part in providing the crew with any info
    What is the point of it then? The EGPWS should have been the last line of defence (or the second last). The fact that it failed means the question is far from resolved.

    “The beginning of wisdom is to call things by their proper name.” - Confucius



  • Registered Users, Registered Users 2 Posts: 1,980 ✭✭✭Growler!!!


    BoatMad wrote: »
    Growler!!! wrote: »
    It would be very difficult to distinguish between the flash from the lighthouse and the flash from the aircraft strobe light also taking into account the whiteout effect of the landing lights while flying in IMC. Also the pilots would have been looking inside at their instruments while flying in these conditions.

    You mentioned stats about the lighthouse. Did it mention the power output in Lux or Candella?

    We have debated this issue over some considerable numbers of posts. I dont think there is anything new to say, which again is why hopefully the final report may add some expert perspective on this

    Again , Its not the key issue, on the key issue , ( in essence a navigation issue ) I think that there is sufficient information to form a conclusion.

    I say its not the key issue, because if they had detected the rock, and avoided it , the main issue still remains

    So you're not going to answer my question and shutting down any further debate on the subject you brought up?

    I believe the debate as you call it was you saying that in your sea going experience the light should have been seen.
    I believe that it could not be seen based on my aviation experience (Cat2/3 ops). You brought the subject back up in your post above in relation to the final report giving reasons why the light was not seen or recognised.

    You are correct as it is not the main issue. If it was seen then this incident would not have occurred. I am merely trying to counter your assertion that the light should have been seen using my own experience.


  • Registered Users, Registered Users 2 Posts: 6,180 ✭✭✭Storm 10


    Discodog wrote: »
    I watched the AC take off from Galway Hospital & the CG arrive. A northerly wind makes for a tricky take off & landing. They have to come around the side of the hospital & land sideways into wind. So a long low level hover. If the field next to hospital is an emergency landing site it's worrying that it has high goalposts around it.

    As a person who knows a lot of the crews they are not an issue for them they have been in and out of the pad and the pitch so many times they are well used to landing in both places, the pad inside the hospital has to be re-certified before they can go back there again. the long low hover they use is called a flared landing and they also do this for the comfort of the patient on board, got to say I love watching them when I am around there.


  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    So you're not going to answer my question and shutting down any further debate on the subject you brought up?

    merely that everyone has stated their ( our ) positions and understanding and deductions and in the absence of any more information , I personally dont think there is anything more to say , thats all ,

    I brought up that subject , not to debate it further here, but to suggest , its on elf the areas where the main report might/must investigate
    , i.e. why did all the detection methods fail, we conclusively know whey the EGPWS didnt work.

    As I said before, the issue that the detection methods failed is part of the event cascade, but the fundamental error remains


  • Advertisement
  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    plodder wrote: »
    What is the point of it then? The EGPWS should have been the last line of defence (or the second last). The fact that it failed means the question is far from resolved.

    NO one , in their right mind, selects a navigation route that contains a serious obstacle and then relies on an inherently unreliable detection system to save their asses

    Thats not how professional navigators works.

    That why is not a key issue with the accident . The key issue is that as I stated above, why did professional crew, select a approach route at a selected height that contained a obstacle fatal to their progress along that designated route

    The answer is in the preliminary report, in my opinion, but the mods are uncomfortable with deductive speculation , so I do not intend to outline my conclusions in that regard

    PS: there are ships taller then the flight altitude selected !


  • Registered Users, Registered Users 2 Posts: 8,261 ✭✭✭Gaoth Laidir


    BoatMad wrote: »
    merely that everyone has stated their ( our ) positions and understanding and deductions and in the absence of any more information , I personally dont think there is anything more to say , thats all ,


    I'm glad to hear it.


  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    I'm glad to hear it.

    on that specific subject , I might add. we can debate the main issue however , but th issue is how much speculation is allowed and the basis for that speculation ( i.e. informed or other wise )

    at the end of the day , the report itself speculates and will continue to do so


  • Registered Users, Registered Users 2, Paid Member Posts: 8,421 ✭✭✭plodder


    BoatMad wrote: »
    NO one , in their right mind, selects a navigation route that contains a serious obstacle and then relies on an inherently unreliable detection system to save their asses
    You're surely not suggesting they did that knowingly? :confused:

    The purpose of systems like EGPWS is precisely to save your ass when you do make a mistake or other issue arises, such that you become reliant on it.

    I understand there has been talk about the system not being as effective in whatever mode it was being used. If that is true, then that becomes part of the conversation as well as the omission from the database. Or when the landing gear is deployed if that affects it too, but that sounds quite ludicrous to me. For all we know, this accident has implications for manufacturers like Honeywell and Sikorsky themselves, for the mapping providers, including state agencies here presumably, for CHC. This aspect is certainly not resolved.

    “The beginning of wisdom is to call things by their proper name.” - Confucius



  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    You're surely not suggesting that is what they did?

    I can only answer that ini the context of speculation based on the preliminary report, but " not knowingly , the issue is in the presence of information , why did they do in unknowingly )

    but clearly they selected a route and picked an altitude and flew that route completely unaware of the existence of the obstacle . yet information on the existence of the obstacle was present in the systems of the helicopter
    The purpose of systems like EGPWS is precisely to save your ass when you do make a mistake or other issue arises, such that you become reliant on it.

    thats not what the experts on PPrune state. remember Honeywell state that they do not guarantee that the database contains everything of danger to a helicopter ( no manufacture could ) and this is true of any database related information displays ( map databases etc )

    to rely on a last ditch warning system that is not based on " whats actually out there " is to put you life in the hands of a less then 100% perfect IT system . The result is after 99.9% successful flights the 0.1% kills you. If you think thats acceptable , then thats OK to " rely " on those systems

    too bring it back to ordinary actvitiers, DO you blame drivers that have driven in walls and rivers , because a error in a GPS satnav, said " turn right now " !!!. or do you blame the GPS. Who carries the major blame here


  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    gctest50 wrote: »
    No no, if it saves your ass it's a bonus

    bonus, yes, but it does not excuse the underlying error of navigation

    wiping you brow , after a brown trouser moment , and patting the computer is not a reason to say there was not problem in your decision logic

    its called automation complacency

    Its one thing to deduce that the crew selected a route and an altitude without any backup information present in the aircraft that would have prompted a change off decision , but thats not the case


  • Registered Users, Registered Users 2 Posts: 9,534 ✭✭✭gctest50


    plodder wrote: »
    ...........

    The purpose of systems like EGPWS is precisely to save your ass ........

    .

    No no, if it saves your ass it's a bonus

    That's why all that piloting is complicated and pilots have that little bit of extra talents


    I mean it's not like yer out in a boat doing all of 30mph, where you can :

    go left a bit
    go right a bit,
    or stop for tea

    BoatMad wrote: »


    This has the unfortunate issue with the arrival of high performance position fixing , in boat navigation , where historically , a waypoint might use a nav buoy , and now people just program up the waypoint and the accuracy is such that they run into the same buoy. !!!


  • Registered Users, Registered Users 2, Paid Member Posts: 8,421 ✭✭✭plodder


    BoatMad wrote: »
    I can only answer that ini the context of speculation based on the preliminary report

    but clearly they selected a route and picked an altitude and flew that route completely unaware of the existence of the obstacle . yet information on the existence of the obstacle was present in the systems of the helicopter
    Agreed. I meant to say deliberately or knowingly selected such a route, or to be more specific, height at the beginning of the route.

    thats not what the experts on PPrune state. remember Honeywell state that they do not guarantee that the database contains everything of danger to a helicopter ( no manufacture could ) and this is true of any database related information displays ( map databases etc )
    Obviously they can't guarantee every object is in the database, but we need to find out why Blackrock wasn't. And the implication coming from the report is quite disturbing on that front
    to rely on a last ditch warning system that is not based on " whats actually out there " is to put you life in the hands of a less then 100% perfect IT system . The result is after 99.9% successful flights the 0.1% kills you. If you think thats acceptable , then thats OK to " rely " on those systems
    Seriously, who wouldn't put their fate in the hands of a system that offers to be 99% right as opposed to you being 100% dead? I'm not suggesting that pilots should rely on this system exclusively.
    too bring it back to ordinary actvitiers, DO you blame drivers that have driven in walls and rivers , because a euro in a GPS maps, said " turn right now " !!!. or do you blame the GPS. Who carries the major blame here
    I see where you are coming from. You are focusing on the navigation issue. It may well have been (and probably was) the major proximate cause. But, the investigation has to look at everything, including the systems that might have saved them, had they worked. Otherwise, what is the point of having these systems?

    “The beginning of wisdom is to call things by their proper name.” - Confucius



  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    I mean it's not like yer out in a boat doing all of 30mph, where you can go left a bit, go right a bit, or stop for tea

    The issues underlying the accident of 116 are seen regularly in modern yacht systems. Th exact specifics are different, but the underlying problem is identical

    in fact modern high tech boats will have higher automation depending and often more extensive IT oriented that a helicopter and often the issues are seen here , some time before they are seen elsewhere

    The difference is that the speed is less likely to result in fatalities, ( but it has in many cases )

    the parallels are surprising , because this accident was nothing to do with it being an aircraft per se. Its a navigation error


  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    I see where you are coming from. You are focusing on the navigation issue. It may well have been (and probably was) the major proximate cause. But, the investigation has to look at everything, including the systems that might have saved them, had they worked. Otherwise, what is the point of having these systems?

    Yes I beleive the core issue is a navigation error

    Yes the report ( as I said several times ) needs to look at the failure of the " save you ass" system which did not do that . In particular the radar failure is peculiar to say the least

    the point of warning systems , is that they are " aids" to piloting the craft , they are not responsible for that piloting , the human is . Hence any professional navigator uses the inputs of all systems to inform them, but ultimately they must plan on the basis that these systems are NOT 100% reliable and proceed accordingly


  • Advertisement
  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    Seriously, who wouldn't put their fate in the hands of a system that offers to be 99% right as opposed to you being 100% dead? I'm not suggesting that pilots should rely on this system exclusively.

    MY GPS is about 99% right , are you saying the 1% failures that result in me being dead, is acceptable for me to there fore relay on it 100% and stop looking out the windows!!!!!

    its ridiculous to suggest that you should plan an inherently dangerous route and then rely on tech system to " save you ass"

    for example , if you had a reliable system that detected walls in your car and applied the brakes, would that then justify you in driving at a wall ???


  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    Obviously they can't guarantee every object is in the database, but we need to find out why Blackrock wasn't. And the implication coming from the report is quite disturbing on that front

    it wasn't there because Honeywell didnt put it there , and I suspect there are many structures not in the database , Yes this needs to quantified and any reliance of such systems flagged, but again this is not the kernel of the accident

    The general feeling elsewhere is that these systems are far from satisfactory and of limited functionality . The main reason SAR is fitted with them , is that from time to time , in a SAR activity , the aircraft is moving in a unplanned way . Rescue 116 was not engaged in a SAR activity , it was following a conventional flight plan style of operation


  • Registered Users, Registered Users 2, Paid Member Posts: 8,421 ✭✭✭plodder


    BoatMad wrote: »
    MY GPS is about 99% right , are you saying the 1% failures that result in me being dead, is acceptable for me to there fore relay on it 100% and stop looking out the windows!!!!!

    its ridiculous to suggest that you should plan an inherently dangerous route and then rely on tech system to " save you ass"

    for example , if you had a reliable system that detected walls in your car and applied the brakes, would that then justify you in driving at a wall ???
    Come on, who is saying you should "plan an inherently dangerous route?" I'm saying you should do your best to not make mistakes in the first place, and then if you have a system that might save your ass, then use it.

    It's like TCAS: it seems like you're saying it should be switched it off, and ATC and pilots should just not make navigation errors. It's a technological system that isn't perfect, but has saved countless lives.

    “The beginning of wisdom is to call things by their proper name.” - Confucius



  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    plodder wrote: »
    Come on, who is saying you should "plan an inherently dangerous route?" I'm saying you should do your best to not make mistakes in the first place, and then if you have a system that might save your ass, then use it.

    It's like TCAS: it seems like you're saying it should be switched it off, and ATC and pilots should just not make navigation errors. It's a technological system that isn't perfect, but has saved countless lives.

    yes , but the fact remains that controlled airspace , the navigation within it and the existence of defined flight paths does not depend on the existence of TCAS

    Thats the kernel, you fly safely using ALL information available to you and your decisions must take into account the fact that warning systems are NOT 100% reliable


  • Registered Users, Registered Users 2, Paid Member Posts: 8,421 ✭✭✭plodder


    BoatMad wrote: »
    it wasn't there because Honeywell didnt put it there , and I suspect there are many structures not in the database , Yes this needs to quantified and any reliance of such systems flagged, but again this is not the kernel of the accident

    The general feeling elsewhere is that these systems are far from satisfactory and of limited functionality . The main reason SAR is fitted with them , is that from time to time , in a SAR activity , the aircraft is moving in a unplanned way . Rescue 116 was not engaged in a SAR activity , it was following a conventional flight plan style of operation
    The report says that the low altitude switch was on, and it's hard to understand why that was the case. This constrains the capabilities of the system including the "look ahead" mode which relies on the terrain database and GPS. Given, that the system knows what speed an aircraft is flying at, what its position and heading are, and what obstacles lie ahead, it should be able to give ample warning in this situation. But, it can't do that if the terrain isn't in the database.

    So, I hope to be seeing a range of different scenarios explored of what might have happened, and excuses aren't presented like "Oh we don't need to look at X. It wouldn't have helped because the crew did Y". In any case, I think it's clear that the point will be elaborated further in the final report.
    The Investigation is continuing to engage with Honeywell and other parties/agencies to reach a full understanding of this issue

    “The beginning of wisdom is to call things by their proper name.” - Confucius



  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    The report says that the low altitude switch was on, and it's hard to understand why that was the case. This constrains the capabilities of the system including the "look ahead" mode which relies on the terrain database and GPS. Given, that the system knows what speed an aircraft is flying at, what its position and heading are, and what obstacles lie ahead, it should be able to give ample warning in this situation. But, it can't do that if the terrain isn't in the database.

    Again , no professional navigator , would knowingly select a route and altitude that then relies on a "last ditch" warning system to save their asses. Sorry , its simply not an form of SOP to my knowledge

    Nobody using terrain warning , whether in a boat or in the air, can in any way , have 100% reliance on these systems. As an example, modern yacht systems, in an attempt to overcome the issues around map zoom issues, now have software that attempts to identify obstacles on the route chosen ( by examining the underlying map database ) , this is similar to what the EPGWS does.

    However no navigator, would totally rely on that system, to sail that route without manually inspecting the underlying data yourself and using ANY other supporting information that may be present on the boat would be crazy ( but it happens )

    So, I hope to be seeing a range of different scenarios explored of what might have happened,

    we have been told exactly what happened, thats not in dispute
    and excuses aren't presented like "Oh we don't need to look at X. It wouldn't have helped because the crew did Y"
    the operation of warning systems , like FLIR, Radar and EPGWS and their contribution ( or NOT ) to the pilots SA, will of course be interesting and provide useful pointers to future operations

    However the performance of the warning systems ( i.e. the crews use of it and the underlying technology ) is not the key issue

    Again the issue is why did a experienced crew select a route with a known obstacle ( i.e. that information was on board the aircraft ) and then fly that route .

    The answer is clear in my mind, even if its deductive


  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    perhaps if I restated the logic in a different way

    Scenario (A)

    The crew selected a pre-programmed route and manually the altitude that they knew contained a fatal obstacle

    conclusion : Bizarre, clearly discountable

    Scenario (B)

    The crew selected a pre-programmed route and manually the altitude that they knew contained a fatal obstacle, yet relied on the various warning systems to avoid the object

    Conclusion: I suggest that no SOP would countananced that approach


    Scenario (C)

    The crew selected a preprogrammed route and manually the altitude that they did not know contained a fatal obstacle, yet the report states the information was available to them from two sources that identified the obstacle and its elevation

    Conclusion : ???

    if you feel there are other decision trees that apply , Id be interested to hear


  • Registered Users, Registered Users 2, Paid Member Posts: 8,421 ✭✭✭plodder


    (A) and (B) are clearly absurd. (C) is the starting point for discussion in my opinion, not the end point.

    Among the questions that the investigation will want to answer are:

    1) why did the crew overlook the details of the obstacle when planning the route?

    2) why was the low altitude switch selected?

    3) why did the EGPWS system not contain the terrain data, because if 2) had been different then the system might saved them.

    I'm sure there are a plethora of other questions.

    “The beginning of wisdom is to call things by their proper name.” - Confucius



  • Registered Users, Registered Users 2 Posts: 10,506 ✭✭✭✭BoatMad


    plodder wrote: »
    1) why did the crew overlook the details of the obstacle when planning the route?
    clearly the issue, because cleary they did, whether the report can shed any more light remains to be seen , my own view is it will not.


    2) why was the low altitude switch selected?

    because according to others elsewhere this is standard SOP for a low altitude operation
    3) why did the EGPWS system not contain the terrain data, because if 2) had been different then the system might saved them.

    we know that , Honeywell have stated that basically not all features of danger are present , no digital database is 100% perfect anyway and cannot be relied upon per se

    The issue if a last ditch system " saving " them , unfortunately doesnt overlook the original error that put them on a path to the accident , So determining that may have valuable lessons for other operators, its not the specific issue behind the accident
    I'm sure there are a plethora of other questions.
    indeed , many of peripheral , though useful , in themselves to get answers to


  • Advertisement
  • Registered Users, Registered Users 2, Paid Member Posts: 8,421 ✭✭✭plodder


    BoatMad wrote: »

    clearly the issue, because cleary they did, whether the report can shed any more light remains to be seen , my own view is it will not.
    I can think of a number of factors that might help explain it. It would be a major failure for the investigation to not get to the bottom of it.

    because according to others elsewhere this is standard SOP for a low altitude operation
    In simple terms yes, and it probably ties in with the first question, because they obviously believed the route to be safe, but so far out, the non visual conditions, and the route being unfamiliar? If it is SOP, then maybe it needs to be changed. Not a question either of us can answer obviously.
    we know that , Honeywell have stated that basically not all features of danger are present , no digital database is 100% perfect anyway and cannot be relied upon per se

    The issue if a last ditch system " saving " them , unfortunately doesnt overlook the original error that put them on a path to the accident , So determining that may have valuable lessons for other operators, its not the specific issue behind the accident
    Yes, you keep setting up this straw man, to be able to knock it down in every post. I'm not going to address it further. The investigators are looking into it. That's all that matters as far as I'm concerned.

    “The beginning of wisdom is to call things by their proper name.” - Confucius



This discussion has been closed.
Advertisement