PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Rotorheads (https://www.pprune.org/rotorheads-23/)
-   -   Pasadena Police - two OH-58s make contact (https://www.pprune.org/rotorheads/500795-pasadena-police-two-oh-58s-make-contact.html)

GrayHorizonsHeli 9th Mar 2018 16:03

Ive heard of police departments going great lengths to convince managers that a fleet upgrade to B3e's was necessary....this takes it to a whole new level. Congrats on the unique fleet renewal program that not many will undertake.

r22butters 9th Mar 2018 17:10

Landing on the same spot, in the same way day after day for years, then one day things are slightly off and visibility is poor,...?

Sometimes **** just happens, and the scary truth is this could easily happen to any of us! Complacency's a bitch, and the only real way to avoid it, is to change jobs/aircraft/location every couple years or so.

,...or watch a video like this and remember in time.

malabo 9th Mar 2018 18:07

The first complacency and lack of professionalism was from the doughheads that pushed the helicopter out and didn’t put it on the spot. Spots that are there to assure a safe distance. I’ve operated from a tight Apron with 8 pads, and if you were even a few inches off your ears got boxed. Chief needs his boxed for failing to promote a professional operation - as seen from the miscreant’s comments on positioning.

[email protected] 9th Mar 2018 22:21

I think the report states that initially the second aircraft was intended to be tasked as well as the first one, so presumably the expectation was that ship #2 would be airborne long before ship#1 returned - that makes the positioning less vital if you are under pressure to get the aircraft airborne.

Carbon Bootprint 9th Mar 2018 23:16

Among the other failings mentioned, the report notes there was no established UNICOM or uniform procedure for a helicopter on approach. Incoming aircraft were apparently detected only by hearing them, which nobody on the tarmac apparently did prior to this incident due to the bird running on the ground.

To their credit, the report states that after the fact, PFD did add monitored UNICOM and approach procedures to their toolbox. I Googled PFD air support section to see how/if they replaced these two ships, but the only reference I could find was one dated 2010 which still mentioned the OH-58s lost in the 2012 prang. Does anyone know the current state of affairs there?

roscoe1 9th Mar 2018 23:35

There is the root cause, which is that the pilot of the moving helicopter hit a stationary machine. No getting around that fact (blades turning or not, that part is kind of like saying "I didn't know if it was loaded and it just went off"). Guns are always loaded and things are always in your way until you know they are not. Then there is the list of mitigating factors, the incorrect parking, the rain, hard to see turning rotors (the strobe should have been a giveaway, cant miss that), the intended departure prior to return of second aircraft all made it so that by being complacent and assuming clearance the pilot guided the aircraft into the other. What if it had been real gusty....still the pilot's fault. Pitch black and power failure of helipad lights....still pilot's fault. There are always safer but perhaps less convenient options that we simply ignore because we are basically sort of lazy. This happened because someone was complacent. That needs to be accepted. It is a real shame they parked the stationary ship where they did and I could see splitting the root cause and blame but one ship was moving and one was not.

LRP 10th Mar 2018 03:06


Originally Posted by roscoe1 (Post 10078773)
There is the root cause, which is that the pilot of the moving helicopter hit a stationary machine. No getting around that fact (blades turning or not, that part is kind of like saying "I didn't know if it was loaded and it just went off"). Guns are always loaded and things are always in your way until you know they are not. Then there is the list of mitigating factors, the incorrect parking, the rain, hard to see turning rotors (the strobe should have been a giveaway, cant miss that), the intended departure prior to return of second aircraft all made it so that by being complacent and assuming clearance the pilot guided the aircraft into the other. What if it had been real gusty....still the pilot's fault. Pitch black and power failure of helipad lights....still pilot's fault. There are always safer but perhaps less convenient options that we simply ignore because we are basically sort of lazy. This happened because someone was complacent. That needs to be accepted. It is a real shame they parked the stationary ship where they did and I could see splitting the root cause and blame but one ship was moving and one was not.

As we used to say, "there it is".

2016parks 10th Mar 2018 03:45

"she also stated she was unsure if the other helicopters rotor was rotating" Isn't it a fact that sometimes a rotating blade simply cannot be seen on reasonably quick examination--because it is moving! If so, are pilots trained to know that fact? How then could she safely rely on "the absence of a visible blade"?

BigMike 10th Mar 2018 03:52

Or she could have just landed outside the other aircrafts estimated rotor disc like she should of, regardless of where it was parked...
There is only one person to blame for this accident.

The crew in the parked machine were bloody lucky...

ZFT 10th Mar 2018 04:01


Originally Posted by roscoe1 (Post 10078773)
There is the root cause, which is that the pilot of the moving helicopter hit a stationary machine. No getting around that fact (blades turning or not, that part is kind of like saying "I didn't know if it was loaded and it just went off"). Guns are always loaded and things are always in your way until you know they are not. Then there is the list of mitigating factors, the incorrect parking, the rain, hard to see turning rotors (the strobe should have been a giveaway, cant miss that), the intended departure prior to return of second aircraft all made it so that by being complacent and assuming clearance the pilot guided the aircraft into the other. What if it had been real gusty....still the pilot's fault. Pitch black and power failure of helipad lights....still pilot's fault. There are always safer but perhaps less convenient options that we simply ignore because we are basically sort of lazy. This happened because someone was complacent. That needs to be accepted. It is a real shame they parked the stationary ship where they did and I could see splitting the root cause and blame but one ship was moving and one was not.

That's not a root cause

r22butters 10th Mar 2018 04:25


Originally Posted by 2016parks (Post 10078886)
"she also stated she was unsure if the other helicopters rotor was rotating" Isn't it a fact that sometimes a rotating blade simply cannot be seen on reasonably quick examination--because it is moving! If so, are pilots trained to know that fact? How then could she safely rely on "the absence of a visible blade"?

Say the other chopper's blades weren't spinning and she parks in her spot without incident,...they're still too close.

Now the other chopper starts to spin up and WHACK they hit!

Who's to blame now?

John Eacott 10th Mar 2018 08:47

This incident reminds me of a similar helipad collision on an offshore pad on the Great Barrier Reef, IIRC out of Cairns, back in the early 90s. The pilot of the shut down helicopter (Bell 222?) had shut down with the blades fore and aft but unable to be tied down as the tail was out over the water. The landing helicopter (LongRanger?) collided with a blade and there was a fatality as a result. The 222 pilot was nowhere near the machine, yet ultimately was blamed for the accident which turned nasty with charges laid against him. IIRC his defence against accusations that he should have secured the blades with the rotor brake was that such an application was specifically prohibited in the Flight Manual.

I've searched for a reference without luck, someone else out there may remember the accident and have more accurate details but it never ceases to amaze me the unexpected outcomes of an accident. The pilot was well known and lost a significant amount of money on legal expenses which were unrecoverable as charges were ultimately withdrawn.

ShyTorque 10th Mar 2018 10:13

Seems there is lots of real estate behind those helicopter landing points. The sensible thing to do, in case of any doubt of tip clearance, would be to have landed on the grass and sorted out the parking issue later, using a marshaller if necessary.

Flyting 10th Mar 2018 10:43

According to Google Maps, looks like the two parking spots have now been replaced by one.

skadi 10th Mar 2018 11:20


Originally Posted by Flyting (Post 10079158)
According to Google Maps, looks like the two parking spots have now been replaced by one.

Yucca Ln
Altadena, Kalifornien 91001, USA

https://goo.gl/maps/EkE1fdja3NA2

601 10th Mar 2018 12:00


that makes the positioning less vital if you are under pressure to get the aircraft airborne.
No

That is why the bl00dy things are painted on the tarmac, to prevent this kind of accident.

Same as guidance lines and parking bays for fixed wing aircraft. They are there for a reason.

2016parks 10th Mar 2018 12:14

"Say the other chopper's blades weren't spinning and she parks in her spot without incident,...they're still too close. Now the other chopper starts to spin up and WHACK they hit! Who's to blame now"

I would think that regardless of what markings are painted on the ground, the arriving machine has a duty to stay far enough away from the parked machine so that both can be safely operated. But: in addition, the parked machine should not , thereafter, spool up unless it knows that it can do so safely. It's like driving your car--"who has the right of way" becomes secondary when one has the opportunity to avoid an accident. The doctrine is called "last clear chance".

r22butters 10th Mar 2018 14:55


Originally Posted by 2016parks (Post 10079218)
"Say the other chopper's blades weren't spinning and she parks in her spot without incident,...they're still too close. Now the other chopper starts to spin up and WHACK they hit! Who's to blame now"

I would think that regardless of what markings are painted on the ground, the arriving machine has a duty to stay far enough away from the parked machine so that both can be safely operated. But: in addition, the parked machine should not , thereafter, spool up unless it knows that it can do so safely. It's like driving your car--"who has the right of way" becomes secondary when one has the opportunity to avoid an accident. The doctrine is called "last clear chance".

Seems to me that the reason those markings are there on the ground are to ensure the aircraft are parked a safe distance from each other in the event someone may be landing with less than ideal visibility and therefore cannot judge accurately their distance from the other parked aircraft?

Is that why those markings are there? Anyone know for sure, 'cause I'm just guessing?

Fareastdriver 10th Mar 2018 15:11

If the first one had been pulled out of the shed and positioned on to the waiting square this accident wouldn't have happened.

[email protected] 10th Mar 2018 15:31


No

That is why the bl00dy things are painted on the tarmac, to prevent this kind of accident.

Same as guidance lines and parking bays for fixed wing aircraft. They are there for a reason.
Regardless of what is painted on the tarmac (the area could be contaminated with oil/fuel etc) the accident was still very preventable if you don't land too close to the other aircraft.

This is a little 2-pad heliport not an international airport.

If you are expecting to launch immediately and the other aircraft isn't expected back until later then why be pedantic and take more time over exact positioning of the aircraft?

The failure to leave enough clearance by the pilot of the landing aircraft is the overriding cause of this accident - the other bits are additional holes in the swiss cheese.


All times are GMT. The time now is 12: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.