Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

R116 Accident AAIU report discussions

Options
1235»

Comments

  • Registered Users Posts: 3,468 ✭✭✭Dohvolle




  • Registered Users Posts: 4,478 ✭✭✭FishOnABike


    A rather simplistic view. Was that the case with both Boeing 747 MCAS accidents?



  • Registered Users Posts: 13,186 ✭✭✭✭jmayo


    Is it not correct that according to flight plan they were to fly into Blacksod using 'Approach Blacksod South' (APBSS) ?

    The Route Guide entry in the report lists the legs and Blackrock at 310'

    The Hazards/Obstacles lists Blackrock Lighthouse at 310'

    So were the route guides consulted or did they just scan the map and not see detail at turning point ?

    Were they online ?

    Why didn't they state min altitude if you had to overfly the lighthouse/rock to reach one of the turning points ?

    Were they trusted because they appeared to be all over the shop?

    I am not allowed discuss …



  • Registered Users Posts: 10,188 ✭✭✭✭smurfjed


    “Boeing 747 MCAS accidents?” What B747 MCAS accidents ?



  • Registered Users Posts: 4,478 ✭✭✭FishOnABike




  • Advertisement
  • Registered Users Posts: 13,186 ✭✭✭✭jmayo


    Actually as far as I know the first Boeing 737 Max accident may have been prevented if the flight crew of the preceding flight had informed the next crew (the doomed flight) about what happened to them and how they resolved it.

    There was a failure of crew documenting events.

    And yes it was pure luck they were able to resolve it.

    I find it illuminating that when one posts certain hard questions as to the events of the night of 14th March 2017 in Blacksod there are very few respondents.

    I am not allowed discuss …



  • Moderators, Motoring & Transport Moderators Posts: 6,522 Mod ✭✭✭✭Irish Steve


    The absence of response to "hard questions" is very easily explained, and should not come as any surprise. The 4 people who knew exactly what happened that night are not here to respond to your questions, and there are very few people within CHC who are going to be willing to stick their necks on a possible block, given how the final report by AAIU has been phrased.

    The AAIU have worked long and hard to determine as much as they could about what went on, by using multiple data sources from a wide range of sources, including recovered data from flight data recorders, and their report leaves very little to the imagination.

    The remit of AAIU does not allow them to allocate blame, so they are not going to come out with black and white statements that will say things like Person A performed action B that resulted in scenario C, but if the report is read with care, and looked at in terms of the changes they now recommend, it's fairly clear to see what went wrong in terms of individual issues, operational issues, and management and governance issues, and how the failures that resulted in the accident came together in such a way as to allow it to happen.

    It's clear that the issues that resulted in the crash are way beyond what happened in the helicopter, and there are significant issues still to be addressed by CHC (the operator), the Irish Coast Guard, the Irish Government and the Irish Aviation Authority. Some of the early AAIU recommendations for action by CHC have been flagged as still open, despite work having been carried out in the period between their initial release and the final report, clearly AAIU are not going to let CHC fudge some of the core issues that are at the core of the organisational changes that are essential to restore acceptable operation of the SAR function.

    There was an initial knee jerk reaction, and time needs to be allowed now for the pendulum to swing back to a more appropriate level of response, and for the outstanding issues to be resolved by all concerned, which will need careful consideration by all of the involved parties, and there will need to be a wider discussion at EASA level of some of the issues surrounding the SAR operation by civilian contractors, and that won't be quick or easy.

    Shore, if it was easy, everybody would be doin it.😁



  • Registered Users Posts: 3,772 ✭✭✭roadmaster


    So where does this go now? Are we looking at civil or criminal cases in the near future. Does someome carry out future inspections/ Audits to see if the reports recomendations are made or does the report sit on a shelf somewhere gathering dust



  • Registered Users Posts: 1,348 ✭✭✭basill


    I would expect lawsuits to be filed by the families against CHC and the IAA in the first instance. The minister will probably have to set up an inquiry which will call for regulatory oversight by the IAA of SAR functions and have to deal with all the other issues such as the inability of Ireland to publish a comprehensive set of charts showing all obstacles in accordance with its international obligations. Behind the scenes EASA might well (hopefully) be asking tough questions of what the IAA was up to. There might (perhaps) be some early retirements.



  • Registered Users Posts: 521 ✭✭✭DontHitTheDitch


    There was a copy on board of a chart with the obstacles shown on the map. Black Rock had a height in feet and a large red dot with the number for it in the corresponding obstacle table on the opposite page, if the ring binder another crew photographed on the night is an exact copy. There is no reason to think they had a different chart.



  • Advertisement
  • Registered Users Posts: 561 ✭✭✭thenightman


    The absolute zero need for 116 and 118 to be out there at all for a crew member who was stable, not bleeding anymore and in no mortal danger annoys me the most. No reason at all that the vessel couldn't start heading for port and a daylight air rescue be performed if needs be, where top cover could've been provided by the AC, who said they would be available from 8am. But the way the call was handled by ICG at Malin and the shoddy communication that followed set the tone for the 'ah sure be grand' approach to things. Such a needless waste of life.



  • Registered Users Posts: 7,252 ✭✭✭plodder


    Was it not the case that the cockpit lighting made it hard to read printed documentation at night, which was why they relied more on the information on the flight displays instead? Or maybe they would rely on the flight displays more if they were understood to be displaying the same information as are on the printed charts?



  • Registered Users Posts: 5,930 ✭✭✭Storm 10


    In my opinion for what it's worth Rescue 116 should have been sent to Shannon and Rescue 115 carry out the top cover they are well used to Blacksod like Rescue 118 it's their patch, such al loss to the their families and to the search and rescue service, Rescue 116 never forgotten



  • Registered Users Posts: 1,707 ✭✭✭BeardySi


    This all feeds back to the potential for fatigue and taking mental shortcuts when taking in data. Easier to read a line of text than to assimilate and process a chart or table of data, especially when poor lighting conditions makes charts hard to read.

    Crew read the notes and probably see it listed as an obstacle on the page (as they made reference to another obstacle listed with it), but not specifically noted in the info on the approach.

    Crew is used to a slightly different way of laying out those approach notes where relevant obstacles are noted in the text and the route is planned to avoid obstacles and be fly able at minimums. Crew fail to note the rock as a dangerous obstacle and seem to have made the assumption that, like the east coast plans they were familiar with, the entire route was safe to fly at 200'.

    Very much the swiss-cheese model in operation.


    Procedures weren't followed properly when deciding to launch a SAR mission in the first place. Malin had decided to launch the OP before even getting the full detail. Even the FV crew weren't looking for it.

    There was a complete lack of cohesion or oversight on the approaches that weren't approaches. With differences from base to base and inaccurate information that had been left unverified or unchanged for years. A company decision was obviously take to treat them as "guides" and not approaches to avoid having the responsibility of keeping them current and correct. The complete lack of Vnav info on a route "guide" to be used in poor visibility conditions is both laughable and now tragic.

    If the weather in Blacksod had been better when the crew briefed at the base it could well have been a different outcome. It's far easier to take that in in the bright light (and fresher mindset) of the briefing room, rather than in the dark on a late night flight.

    The missing data from the EGPWS database was obviously a crucial factor. The fact that it was not dealt with as a matter of urgency because they never had it on the S61 is damning. It takes no consideration for the different ways modern crews use the information at their disposal.


    Changing any one of those factors could have changed the outcome, but ultimately the management of the whole CHC operation was exposed as very slapdash and poor, as was the government and coastguard oversight of their contractor.



  • Registered Users Posts: 7,252 ✭✭✭plodder


    Interesting summary.

    Regarding "The missing data from the EGPWS database was obviously a crucial factor."

    With the low altitude switch on, would that have made a difference? The report seems to suggest that the look ahead envelope was almost completely inhibited at the air-speed at impact. Low altitude switch was in the DVE approach checklist which is the reason it was on.



  • Registered Users Posts: 1,707 ✭✭✭BeardySi


    I'd have to reread to refresh myself, but didn't they find from the review flight that it was not showing up at speeds of 70kts and below due to the reduced envelope, but as R116 was travelling at 77kts it would have shown had it been in the database?



  • Registered Users Posts: 7,252 ✭✭✭plodder



    "The EGPWS manufacturer’s manual states that the LOW ALTITUDE reduces the look ahead from 1.1 NM to 0.75 NM at 120 kts and that ‘Forward airspeed will also modify the look-ahead envelope. Below 100 knots, the envelope is reduced until it is completely inhibited at 70 knots or less.’"

    It doesn't say what the exact look ahead at 77kts would be, but it sounds like it gradually reduces between 100 and 70, where it's completely inhibited.



  • Registered Users Posts: 2,979 ✭✭✭Stovepipe


    It's also not the first crash on this island (Ireland) from using an unofficial,unapproved procedure. It wouldn't have been impossible to put that let-down approach procedure into a flight simulator and test it there, before using it for real.



  • Registered Users Posts: 35,057 ✭✭✭✭Hotblack Desiato


    Presumably the simlulator would also have been missing the rock so what's the point of that?

    © 1982 Sinclair Research Ltd



  • Registered Users Posts: 2,979 ✭✭✭Stovepipe


    The "rock" was already in the OS database/IAA VFR charts and had been for a very long time,plus the procedure was designed to overfly the rock as part of a descending left hand turn,so it had to have been known about. The location of the rock was not a "point in space" like an RNAV entry,but a crucial pivot point about which the second last turn was made, before the straight section/run-in to Blacksod. Whoever designed the procedure was clearly familiar with non-precision approaches.



  • Advertisement
  • Registered Users Posts: 44 spark23


    Would this indicate as was stated in a report many years ago that three SAR bases was ideal for Ireland with modern helicopters? ie Dublin,Cork,Knock, there seemed to be political issues around Waterford and that a 12hr service(possibly linked to ferry service's) was more suitable there rather than 24 hrs. There seems to have been a corporate crossover of SAR with some elements of HEMS and Patient transfer and obviously Topcover. If more operation missions being flown by fewer bases would allow crews to remain current with less training obviously in line with crew duty periods etc. All that being said there was no real medical need to launch the mission that night in darkness and daylight would have shined a different look on the situation. Hopefully positive outcomes result out of this tragic incident.



  • Registered Users Posts: 2,979 ✭✭✭Stovepipe


    they are also often tasked with casevac from mountains, Carrauntoohil being a frequent "port of call". It's a lot of helicopter just to lift one person off.



  • Registered Users Posts: 4,478 ✭✭✭FishOnABike


    Looking at the R116 approach overlaid on Blackrock, the approach appears to be slightly North of West. The route guide seems to position Blackrock slightly South of West of waypoint BLKMYO. Could this also have been a factor? It may have given the impression that the approach taken would have passed to the North of Blackrock.



  • Registered Users Posts: 11,238 ✭✭✭✭Furze99


    Snickersman on other closed thread "An Inquest jury has ruled that the deaths were "accidental". Not sure about all the legal implications here because the foreman of the jury also said that 'deficiencies in mapping “contributed considerably to this accident”.'

    Too bloody right they did.

    I am not a pilot, but I knew a man (long dead now) who flew Fairey Swordfish biplanes off aircraft carriers in the second world war. He once remarked, after a famous case when a private plane crashed at night while flying over water, that it was very common for inexperienced pilots in such circumstances to become disoriented. The golden rule, he said, was "you have to trust your instruments"

    If that was true flying open-cockpit biplanes in the 1940s, you would imagine it would be even more valid in the 21st century. One would hope that navigation aids might have actually improved with the advances in digital and GPS technology. By that token, if Captain Fitzpatrick, a highly experienced pilot, was concentrating on her instrument panel instead of looking out the window into the gloom, she was only following best practice. If the information being presented to her was faulty, ie if it neglected to mention that she was heading straight for a rocky promontory, then could the crash really be called an accident? Albeit not her fault?

    i think this has some room to run. But as I said, I'm not an aviation professional. Or amateur."


    I wondered about this too, there was possibly a bit of the 'state washing it's hands' in this verdict. Will we now see a civil case now against the manufacturers of the on board navigation systems and suppliers of data to same?

    May they all RIP regardless.



  • Registered Users Posts: 3,000 ✭✭✭skallywag


    FURZE99 wrote> ...Will we now see a civil case now against the manufacturers of the on board navigation systems and suppliers of data to same?

    I have heard this argument doing the rounds quite a bit, but I do not follow it.

    EGPWS is a navigation aid and as such should never be used as a primary navigation system. I believe that Honeywell themselves call this clearly out in their documentation.



  • Registered Users Posts: 5,301 ✭✭✭Snickers Man


    Is that really the case?

    "We provide this system at (presumably) huge cost to ultimately the Irish tax payer but we take no responsibility for the omission of natural obstacles from the data on which it is based?"

    Seriously???

    I could maybe have some sympathy if it was a high-rise hotel that had been thrown up in the year or so since the system was provided to the helicopter operator but a piece of geographical real estate that has been there for centuries? "Well, shucks. Our cartographer must have missed it"

    If that is the case then as a taxpayer I'm outraged.



  • Moderators, Motoring & Transport Moderators Posts: 6,522 Mod ✭✭✭✭Irish Steve


    There has been all manner of obfuscation around some of the issues that were found when the AAIU went into real detail of the reasons for the loss of R116.

    For me, one of the most damning was a statement made at one point along the lines of "VFR charts are prepared on the basis that an aircraft should only operate below 500 Ft when approaching to land, or departing from a licensed airfield, so the charts don't need to have accurate detail outside of those (very limited) areas, and not at all off the coast for any objects that are below 500 Ft".

    Effectively, that meant that VFR charts as supplied for the SAR operation were effectively unreliable for the vast majority of their operation, as the whole concept of SAR operation is that they operate at a level that enables them to perform their function of rescue, and they're not about to start winching people in and out of operational sites from 500 Ft above them.

    If VFR charts are not suitable for use below 500 Ft, and things like terrain clearance information is based on those charts, then one has to ask about the validity of even having a GPWS system in a (primarily marine) rescue helicopter, yet Sikorsky put it in the airframe, and the supplier provided a database for it, and as far as I am aware, there was no placarding or other warnings that stated "this system is not suuitable for use below 500 Fr amsl", so it was anticipated that it would be used, but it's become very clear from the in depth investigation that there were some glaring errors and omissions in the database, and that was effectively admitted when a number of updates to VFR charts were rushed out shortly after the accident, where locations or spot heights were updated to reflect the reality that was actually on the ground, and over time, those changes (and others) would have rippled into the database information used to generate things like GPWS systems.

    Part of the problems is that historically, SAR operations were carried out by the military organisations, and they were not necessarily dependent on navigational information that was prepared by civilian services, it was only when the SAR function was moved out of the military domain that some of the issues that became clear after the accident were exposed to the harsh light of reality.

    The problem with SAR is that there is no other operation like it in civilian aviation. The closest to it is helicopter operations that services things like oil rigs, and the like, but they are restricted to operating within civilian flight limits, and IFR operations at very low level do not form a part of that remit, whereas because of the very specific issues of saving life in hazardous situations, SAR operations are not subject to the same absolute limits that apply to every other branch of civilian aviation, and it is only when an accident of this nature happens that the spotlight is brought to bear on some of the underlying issues that come out of the woodwork.

    In theory, SAR operators should be using a database that doesn't exist, as it's outside of the remit of the civilian authorities provision requirements, but to a degree that goes much further than for any other branch of aviation, SAR desperately needs a level of accuracy that hasn't existed until the advent of high resolution satellite mapping, and even now, some of the highest levels of accuracy are still in the fiefdom of the military, because it's usually them that have provided the (significant) funding to produce that level of accuracy. There are now civilian services that are in a position to provide data to meet the requirement, but funding the provision of that data for a small country like Ireland, that's another story, in that the only user of a high level accuracy database of this nature will be SAR, no one else needs it, as they can't legally fly to the limits that would demand such accuracy and remain legal.

    There was a media comment as a result of the inquest report that the AAIU will be releasing an update on the work that is ongoing as a result of the R116 accident, while their report won't change, what will be updated will be the manner in which all the recipients of their many safety findings have dealt with their responsibilities and shortcomings that have been highlighted, as AAIU will have been monitoring their progress in dealing with the specific findings.

    I am not convinced that some of those organisations are going to come out of that review smelling of roses, there has been a history of inertia, especially around state services, and changing that culture will not be quick or easy.

    Shore, if it was easy, everybody would be doin it.😁



  • Registered Users Posts: 3,000 ✭✭✭skallywag


    Snickers Man wrote> ...is that really the case?

    I believe so.

    I remember at the time being sent a link to the actual Honeywell manuals for EGPWS where it very clearly called out that this system must not be used as a primary navigation system. It is intended to be an aid, but not your single source of truth to the 'where am I and what obstacles must I avoid' question. I cannot find the same link on a quick search, but if you do a google for EGPWS documentation I think you will find the wording which I refer to within the Honeywell user manuals.

    Some good points from Steve in the post above, particularly on the 500ft topic.



  • Registered Users Posts: 2,979 ✭✭✭Stovepipe


    It also begs the question of why they were so low in the first place when the MSA for that block is greater than 1000 feet.



  • Advertisement
  • Registered Users Posts: 2,279 ✭✭✭MayoForSam


    'Meitheal' on RTE1 currently, documentary about the search after the accident and impact on the local community.



Advertisement