pic

pic
Showing posts with label Safety Related. Show all posts
Showing posts with label Safety Related. Show all posts

Wednesday, April 5, 2017

Flights On The Bubble

Update: Since I first wrote this, the NTSB has released their findings on one of the events discussed here. Not everyone agrees with the NTSB's conclusions - that is a common occurrence in events like this. I now believe it is an over-simplification and unproductive to find "pilot error" as the main source of a crash - in all but the most egregious and willful incidents of wrong-doing.

Did the pilot err? Maybe. But what role did the other parties play? What role did the culture of the organization play? What subtle pressures were being exerted - or not exerted - and how did that contribute to the pilot's error?

If we were to reexamine these crashes in the light of high-reliability-theory and system analysis and design, the causes would be revealed as more complex and nuanced. Repeatedly blaming the pilot doesn't change anything. If we don't change our way of thinking--these types of events will continue.

Whatever mistakes were or were not made, the victims paid the greatest price. As the companies and the lawyers and the insurance companies swerve, lunge and parry; let's remember this. In a fatal crash, no one wins. (Except maybe the legal teams.)

The crashes discussed here caused a tremendous amount of pain and suffering for the families and friends of these victims. Their lives are forever altered. Their suffering will not end and the sad memories will never be completely gone. Please keep these souls in your heart and your thoughts.

Please know that the purpose of writing this is not to cause fresh pain or re-open a wound. I write this in the hope that we can prevent a repeat occurrence. We have broken enough hearts and scarred enough souls.

Since family members contact me personally, I want them--and you--to know that I and others like me; Jonathan Godfrey, Krista Haugen, Randy Mains, Miles Dunagan, et al--are doing everything we can to make sure that no one else has to endure what these families must. We know that we can never push change on this industry, but together we might just give it a nudge.

Sadly, there have been more HEMS deaths since I wrote this. I wish it were not so. (dcf)

From before...

I have been thinking about Chad Hammond the last few days, Chad was a well-liked and well-respected helicopter air ambulance pilot who, along with his crew and patient, were the last souls to be killed in a HEMS/HAA crash, as of this writing. The anniversary of their deaths was March 26th. As that date drew near, I wondered if we - collectively - could go a full year without killing anyone. And I hoped. I have come to know Chad's widow Natalin over the year since his death, and pondered his loss, and hers, at length. The NTSB report on this crash is not yet complete, so any discussion of cause is pure speculation. But I see similarities in this event and others, and I think it's worth a discussion between you and your HEMS team mates. It may well turn out that all assumptions about what happened to Chad and his team and patient are wrong. About the other events, there is no question.

As an Air Medical Resource Management instructor, I look for patterns and attempt to point these out when I find them - so that you might recognize a pattern as well. So that you might realize an accident chain is being welded together. So that you will not be the subject of a story like this.

And this morning I thought about HEMS flights on the bubble.

Are you familiar with this phrase, "on the bubble?" It normally refers to a team or team member who is right on the edge of not making the cut. It is often used in the context of a sport.  But it has another meaning. According to the Urban Dictionary "on the bubble" can be defined as...

At risk. In peril. Most often used to describe someone or something that may be cut from scope or removed from the group.

So the context I am considering is a flight that a HEMS pilot and crew are considering that is "just good enough to go"  The weather minimums that we VFR HEMS pilots use are pretty loose. Here they are.



So you can see that if we have night vision imaging systems or an approved helicopter terrain avoidance and warning system, our route is non-mountainous, and our destination is within our "local flying area," (as much as fifty nautical miles away from the base) the weather can be as low as 3 statute miles of visibility and 800 feet of clearance between earth and clouds for a night flight. Now, most flight teams understand that those numbers aren't used to start a flight, they are used to terminate one, but invariably some volume-conscious manager will push, or an over-zealous flight team will blast off hoping for the best.  Perhaps the pilot is seeing a trend of improvement and assumes the trend will continue. Never mind the fact that when we consider weather categorically, 800 and 3 is considered IFR, or instrument flight rules weather.

IFR = 500-1000′ and/or 1-3 miles

I imagine helicopter operators pushed for such low numbers and were given them by the regulators because some of the things we can do with a helicopter involve flights very close to the takeoff point, or flights at a very low speed, such as hovering over a grove of fruit trees to keep them from freezing on a cold winter's night, moving timber down a hill to a river, or hovering along next to a high tension power line. And of course, a helicopter can stop just about anywhere, even though many of us pilots have died because of a shocking reluctance to use this capability.

So let's consider the pilot who checks the weather, and finds it "legal" and convinces the crew that all is well. As they proceed to the patient pickup point, things aren't great, but they are good enough to get by.

We are now flying "on the bubble."

We land on a scene or at a hospital pad, and the waiting game starts. Here is where we can get ourselves into trouble. We arrive on the bubble and while we wait it pops.



JALAPA -- Three times before dawn Tuesday, calls went out to emergency medical helicopters: A woman with a broken leg needed help along I-26 in Newberry County. 

Air rescue units from two Columbia hospitals and another in Greenville said it was too foggy to fly.

(added: One helicopter, "CareForce" from Richland Hospital in Columbia, launched and then aborted for weather.) 

A fourth call went to Spartanburg, where Regional One pilot Bob Giard checked the radar, decided the weather looked clear and took off with two crew members. 

The crew never reported problems with the weather en route to the site. But minutes after picking up the patient, their helicopter crashed in woods near the Palmetto Trail, about 1,000 yards from an I-26 rest area, authorities said. 

Giard, 41, flight paramedic David Bacon, 31, nurse Glenda Frazier Tessnear, 42, and an unidentified female patient died.  (text courtesy Associated Press)

Here is a bit from the NTSB on this crash.

"A single-engine emergency medical services (EMS) helicopter was destroyed after impacting trees in a national forest about 0532 eastern daylight time. Night visual meteorological conditions with mist and light fog prevailed in the area of the accident site. The flight crew was contacted about 0452 to determine if they could accept the mission. The pilot performed a weather check and accepted the mission about 0455. He departed about 0502. The helicopter arrived at the accident scene and landed on the interstate highway near a rest stop about 0523. The helicopter departed the scene about 10 minutes later, flying toward the national forest located north of the interstate. A witness reported that the helicopter made no abrupt maneuvers and that the engine "didn't sound like it was missing, sputtering, or any other kind of power loss." He reported that the helicopter was straight and level then it "pitched forward to go forward." He reported the helicopter was "flying level" as it descended into the trees. He reported that the helicopter's searchlight was on and that fog and mist were visible at treetop level. Postaccident inspection of the helicopter revealed no preexisting anomalies that could be associated with a pre-impact condition. Download of the engine's electronic control unit nonvolatile memory indicated that the engine was operating at 98 percent Ng when it impacted the trees. Three other EMS helicopter operators had turned down the mission, including one who had attempted it but had to return because of fog conditions. However, the accident pilot was not informed that other pilots had declined the mission because of fog."

Now maybe you are thinking that "about 10 minutes" isn't long enough for the weather to go from just above minimums to well below them, but I assure you, saturated air can go from muggy to foggy very quickly. Giving this crew the benefit of the doubt, and assuming they weren't breaking the law on the way to the patient, one must surmise that conditions deteriorated while they sat on the ground at the scene. And sadly, they decided they had to go anyway.

When I was doing AMRM for Omniflight, I was privy to event reports in which pilots described adverse flight scenarios they had lived through. I used these redacted reports for classroom discussions so that we might learn from someone else's "thrilling" moments. In one such event report, a pilot recounted a night flight to a patient in which he noticed the weather deteriorating and decided to abort and return to base. The requestor, a ground-based ambulance crew, asked if the aircraft and crew might stop somewhere mid-trip for a linkup and patient transfer. So after doing a 180, this pilot landed and waited for the ambulance to show up. And as he and his crew waited they observed the weather getting worse and worse. Finally, he had had enough and he set about departing for his base. But just as they came up to a high hover, the ambulance pulled into the parking lot!

This is a very uncomfortable position to be in as a pilot. I have been there and done it wrong. I didn't want to disappoint the "customers," (the ambulance crew) and I didn't want to leave the patient in the lurch.

So as this pilot and his crew see the bus pull up, somebody decides to land and load in a hurry and hope for the best. The next few minutes were undoubtedly an experience that none of them will ever forget. The text in the event report went something like, "I took off and got into the clouds and could no longer see the ground. I lost control. The aircraft spun to the left and spun to the right, then I got on the instruments and regained control. I flew on to the receiving hospital." In actuality, there was a little bit more to it. I presented this case study at this pilot's base, not knowing who he was or where he worked, and after the class, he confessed to me that it had been him. I now have the utmost admiration for this man's courage and candor, because he rightly assumed that his experience might be repeated. So he volunteered to tell his story in a video sponsored by Airbus Helicopters.

You can watch this video, titled "That Others May Live" here.  It is chock full of lessons, and it has undoubtedly saved some lives.






So now let's consider the most recent fatal crash. Here is a bit from the initial NTSB report,

"On March 26, 2016 about 0018 central daylight time, a Eurocopter AS 350 B2, N911GF, impacted trees and terrain near Enterprise, Alabama. The airline transport pilot, flight nurse, flight paramedic, and patient being transported, were fatally injured. The helicopter, registered to Haynes Life Flight LLC. and operated by Metro Aviation Inc. was substantially damaged. The flight was operated under the provisions of Title 14 Code of Federal Regulations Part 135, as a helicopter emergency medical services flight. Night instrument meteorological conditions (IMC) prevailed for the flight, which operated on a company visual flight rules (VFR) flight plan. The flight departed from a farm field near Goodman, Alabama about 0017, destined for Baptist Medical Center Heliport (AL11), Montgomery, Alabama.

According to the Coffee County Sherriff's Office, on March 25, 2016 at approximately 2309, a 911 called was received when a witness observed a motor vehicle accident on County Road 606 near Goodman, Alabama. Sheriff's deputies were dispatched along with Enterprise Rescue Squad. Deputies also contacted Haynes Life Flight dispatch, when it was discovered that the vehicle was overturned and that an unconscious victim was inside.

According to communications records, the call from the deputies was received by Haynes Life Flight Dispatch at 23:19:10. The pilot of "Life Flight 2," which was based at the Troy Regional Medical Center, Troy Alabama was notified at 23:20:38. The helicopter departed Troy at 23:26:57 and arrived at the landing zone (LZ) in a farm field adjacent to County Road 606 at 23:53:15.

According to witnesses, after touchdown, the pilot remained in the helicopter with the engine running. The flight paramedic and flight nurse exited the helicopter and entered the Enterprise Rescue Squad ambulance to help prepare the patient for transport. Once the patient was ready for transport, the flight nurse and flight paramedic along with several other emergency responders rolled the gurney approximately 70 yards through a grassy area to the helicopter and loaded the patient on-board. Once the patient had been loaded, the flight nurse and flight paramedic boarded, and at 00:16:45 the helicopter lifted off and turned north towards AL11.

Fog, mist, and reduced visibility existed at the LZ at the time of the helicopter's arrival. Witnesses also observed that these same conditions were still present when the helicopter lifted off approximately 23 minutes later. The helicopter climbed vertically into cloud layer that was approximately 150 feet above ground level and disappeared when it turned left in a northbound direction toward AL11. Review of the recorded weather at Enterprise Municipal Airport (EDN), Enterprise, Alabama, located 4 nautical miles east of the accident site, at 0015, included winds from 120 degrees at 4 knots, 3 statute miles visibility in drizzle, overcast clouds at 3oo feet, temperature 17 degrees C, dew point 17 degrees C, and an altimeter setting of 29.97 inches of mercury."

So, do you see a pattern? We get to the patient, and the weather gets worse, and for whatever reason, we give it a shot. None of these pilots were bad people. They weren't dumb. They were respected and liked and loved. And they certainly didn't walk out to their aircraft thinking "tonight's the night." And yet they all took off into weather that contributed to their deaths.

 (added - bystanders observed low cloud and fog at the scene. If you are a clinician at a scene walking back to your VFR helicopter with your patient, look up! If you see clouds or fog at or near treetop level - or the rain is so thick you can't see anything - don't fly!)

No matter your role on board, be aware of the weather where you are. And be aware of how a pilot's mind works. He or she wants to get the job done. We want to help the patient and avoid disappointing anyone. But in our efforts to do this, in some cases, we cause disappointment beyond belief. YOU may be the person who says, "hey friend, while we have been here things have gotten worse. So I am making the call. We are going by ground." (If your program permits that option, if not maybe you should not go at all.)

Flights on the bubble put us at risk, in peril. I don't want you to be cut from the scope of our business, or removed from the group.



Safe Flights friends...








Wednesday, March 18, 2015

On Machoism...

I have always thought of (and discussed) machoism from a certain perspective. But it has different personas. Here is a comment from a post I wrote on a facebook string.

One of our problems is that we are assumed to have the experience for all the different environments we operate in, or perhaps it's left to "tribal knowledge" (a check-airman's actual words during a message exchange on this topic a couple years back) to prepare us. Landing on, in, and among high-rise buildings is akin to mountain flying. No one in HEMS addresses wind or turbulence limits - it's up to the pilot. And if "all the other guys do it" then I should be able to do it too, right? I now realize that this attitude (I can do it if they can do it) is another form of the hazardous attitude "Machoism."




While attempting a landing at the Medical University of South Carolina's helipad on top of a parking garage, downwind of an airfoil shaped tower (The Ashley River Tower), I realized that the vortices off the building were putting me at the limits of aircraft control.

Image courtesy Vertical Magazine


The thought went through my mind...all the other guys would be able to do this...

I decided that what I was doing and thinking was stupid. It was self-induced pressure to live up to an image. I aborted the approach and went to an airport. The patient went by ground.

Sometimes old pilots try to be bold pilots...




Friday, March 13, 2015

Eagle Med helicopter crashes in Oklahoma

One person has died. The news report indicates four crashes within this company since 2010....

This is the second fatal HEMS crash in a week. Stand by for increased regulatory pressure and government oversight. Hopefully the survivors from last evenings mishap can offer insight into what happened.

Click here for more...

For a historical perspective on the problem, click here...

Tuesday, March 10, 2015

Reflecting on Loss of Power...

 Losing an engine at that point would result in a very rapid decrease in rotor rpm, and a rapid descent to who-knows-what kind of forced landing area. It would be a lot different than pushing the collective down from level slow-cruise at one thousand feet above the threshold of a big beautiful runway. An excerpt from a post on ready-thinking

Over the last few days, I have been doing some hard thinking about what it will mean to lose power from the single engine in the helicopter I fly. Notwithstanding the high reliability and statistically insignificant risk of failure, engines DO fail and when we only have one, it puts us in a bad situation. I have taken to slightly longer hover checks (to let it quit if it wants to while I am near the ground), and climb-outs at max-continuous power and best-climb speed. Altitude and speed are good when the whining stops.

I spoke with Alex Myers, a young pilot-friend about the failure he experienced in a 333 trainer in Saudi Arabia. He noticed a change in engine sound, took the controls, and said, "now what did you do?" to his student. The student didn't do it - a nut on a pressure line came loose. Alex says "everything slows down and time stretches" as he is doing his first-ever real-live no-crap auto to the surface. He had just cleared a built up area and was over flat open terrain. They were lucky. 

Not everyone is so lucky.

Fellow pilot Juan Terraza told me about his two engine failures. In both cases the problem was the same thing, a nut securing a pressure line vibrates loose, a pressure signal is lost, and the engine spools down. Juan said both problems occurred after making a power adjustment, and advised against moving the collective during climb-out until at a safe altitude for autorotation. So after my hover checks are complete, I make one smooth increase in power to the line and leave the collective still until level off. 

Bad fuel will ruin our day as well...

I continue to consider and announce forced-landing areas, for both arrivals and departures. But I know there will be some situations where a forced landing will be difficult if not deadly. It might be good to start looking at rooftop helipads on hospitals as higher-risk propositions, with some additional forethought on escape paths and forced landing areas. It might even be worth considering to begin an approach to a point in space adjacent to a rooftop pad, sliding over the pad as the approach terminates. If the engine burps, farts, or coughs - down-collective to maintain rotor rpm and fly clear...

I find myself reflecting on the amount of time I spend in the avoid-area of the height-velocity chart - that is the combination of altitude (low) and airspeed (slow) from which an autorotation will not end well. A wire strike is more likely than an engine failure, but there are some areas where a wire strike is unlikely - like on approach to a rooftop helipad. If we know that we are into the wind, and won't hit wires, perhaps a super-slow approach (200 feet per minute rate-of-descent) isn't the best way...

(One cannot land a single engine-helicopter on a rooftop hospital-helipad in the city of Boston. Recent events perhaps bear out the logic of this restriction).

When you read about someone perishing - someone of a similar age and with lots of experience - by all accounts a good and safe pilot - it brings on the hard thinking...

May it not happen to you.

Or me.

Please add your thoughts on this in a comment...

Saturday, March 7, 2015

ARCH helicopter crashes near SLU, pilot dead

Image credit: KTRS
ST. LOUIS – (KTRS) The pilot of a medical helicopter is dead following a fiery crash Friday night near the helipad of St. Louis University Hospital, a fire department spokesman said. Shortly after 11 p.m., authorities said the pilot of a helicopter from ARCH Air Medical Services was heading back to the hospital 

Click here for more...

Friday, March 6, 2015

Pressure Relief Valves...

A flight request came across the radio. The young new pilot checked the weather computer, found numbers that looked good, and accepted the flight. As the crew walked outside they looked up at a low ominous ceiling. The nurse looked at him, and back at the sky. She could read his mind. He had accepted a flight, and he was having second thoughts. But he had just said that the weather was good and that they could go.

In an even, friendly voice she said, "it's okay to change your mind, if you don't think the weather is good enough we don't have to go. There won't be any trouble."  

He spoke into his radio, "Communications, this is Lifeflight. We are unable to respond for weather." 

If you are a HEMS crew member, be advised. Your pilot is under pressure.

It's a normal fact of life, and he or she is not unique in this regard. You are under pressure too - but his or her pressure can hurt you, whereas few crew members have ever hurt or killed a pilot.

German HEMS in the news...Hospital employee killed by tail rotor...



Man walks into helicopter tail rotor...click here for more.

Tuesday, February 17, 2015

Trust Your Gut...

Thanks Bruce White, MCFR, for pointing this in my direction...

Prior to lifting from the rooftop helipad, we evaluated the weather and identified low clouds and obscured local mountain tops. ( at least that's how i remember it. Its been a while and i just remember the weather being bad bad.)
The pilot stating something to the effect of “I think i can get down and around some of that stuff and get home…” to which the new flight nurse proclaimed “uh….yeah, OK. im good with that.”

The only thing that was ringing in my head after watching this go down was “Josh…..this is how crews get killed. They're tired, they want to sleep and they're willing to push a bad call to get there. This is what we've always been warned about and now your staring down the barrel of saying something or just going with it.”

What i was seeing was a pilot that is used to flying in worse than crap weather. But in a suitable aircraft. And i was seeing a new flight nurse that didn't know how to say no, or didn't want to.
So i said something. “Hey guys, im calling 3 to go here. I'm not comfortable launching in this weather. I know we all want to get home; i do too, believe me. But lets not push bad weather and make a bad decision. Lets hang out, watch the weather and see if it starts to break up or not.”
They agreed and we waited. I received no flack and no push back. I felt like i almost watched their faces go, “wow, we almost made a dodgy decision. That would have been really dumb. Yeah, lets wait for stuff to clear.” We waited till we could see stars, and the weather continued to break. We lifted with clear skies and stars in our windscreen and made an uneventful flight home.


Flight Nurse and blog contributor Josh Henke, ...

You can contribute too. Really. If you fly HEMS this is your blog. I know you can save a patient; I want you to save a crew.

Friday, February 13, 2015

Flashback Friday : Being in the Right Place at the Right Time With the Right People

edited 2/13/15

I was laying in bed the other morning, thinking about speaking to an international audience who were going to be listening to me not because they had to but because they chose to;  a first-time event.  I teach subject matter that is required by CAMTS, and the Code of Federal Regulations:  the body that certifies air medical transport companies and the FAA.  Thus far the folks in my classes have been there because the boss said so. I was trying to sort out how to approach the problem of being meaningful, and how to relate to the audience. Sitting in front of me would be all sorts of people filling all sorts of roles in health-care, from senior leaders to the newest entry-level healthcare provider, from pilots to paramedics to professional safety managers.

Finally I decided to just talk to the people who work where the metal meets the mud; the flight crews. When I lecture - I am talking to them, because I want them to stay alive. Tragically, as I was thinking these thoughts three persons were losing their lives in a helicopter.

In our industry, safety folks are all about implementing "safety-management-systems." One organization after another touts the fact that they have "exited level one, or two, or three" and so on,  and to be sure I hope that eventually these things will help prevent accidents. But what about not dying right now? I attended a class in which a very smart, educated, and thoughtful pilot and safety executive put up slide after slide explaining that there really are lots of players in our game, and any one of multiple contributing factors can be why we crash aircraft and kill people. Good Stuff. How do I stay alive.

What about you, dear pilot, or nurse, or medic, or RT? What will you do to stay alive throughout your flying career? Do you have any personal strategies, or tricks, or philosophies on how to not get dead? If not, perhaps you should give this some thought. Because what we do is dangerous.



According to the American Journal of Clinical Medicine (Winter 2009 issue) after assessing past statistics then projecting them forward, they predicted that if you fly in a HEMS helicopter and do that job for twenty years, you face a 40 percent chance of losing your life.

Before I started writing this, sitting in my sun-room on a Sunday morning, I was reading the weekend-edition of the Wall Street Journal. This is a great paper, with tons of information that is a bit over my head, and - my favorite part - book reviews and excerpts. One article covers Dr. Thomas Lee, a professor of medicine at Harvard, and his new book "Eugene Braunwald and the Rise of Modern Medicine." In this article there is a line about Dr. Braunwald; "over six decades, he (Braunwald) was repeatedly in the right place, at the right time, with the right people."

This is my advice to you, dear HEMS person who climbs into an aircraft and takes to the sky. Seek always to put yourself in the right place at the right time with the right people. It's as simple as that. If you are not sure where the right place is, educate yourself. Your heart and your head will tell you about the people. The time is now.

In the right place... I now fly a single engine aircraft. I have dedicated myself over the last year to continuously evaluate if I am in a position to survive the loss of that one engine. When I take off, I fly as close as possible to the way the operators manual says I should, at max-continuous power, at best-climb speed, to an altitude allowing a safe landing should my engine fail. I deliberately fly as if the motor is going to quit, even though the odds are that my engine won't. If I am not in the right place, I try and get there as quickly as possible. My new flying style elicits comments from the back like, "wow, I never saw this view from such a high altitude," and "gee, things sure look different from way up here." This at two thousand feet above the ground! Why do we persist in flying so low?

(added 2/13/15: There is an increased industry/FAA interest in over water flight. If you fly a single engine helicopter over water without floats and vests, I recommend you fly at an altitude or on a path such that no person could ever misunderstand or question your ability to reach the nearest shore. Such a misunderstanding got an excellent pilot - who formerly flew the president of the United States - fired.)

By way of explanation...The odds of a sprag-clutch failing to engage on engine-start are probably a billion to one. That happened to me in a BK, and resulted in around a million dollars worth of damage to the aircraft I was in command of. I am not immune to bad fortune. If an engine is going to quit, I take it for granted that it's going to quit on me. I don't want to be in the wrong place when it happens.

With the right people... I heard a story not long ago about a crew heading out to do a PR flight. There was a seasoned pilot at the controls, and a seasoned crew in back. Sometime in flight, or perhaps after landing and on shutdown, the paramedic smelled fuel. He keyed up the mic and announced "I smell fuel." The pilot acknowledged the message and continued on with what he was doing. They shut down and got out, and the pilot wasn't taking any actions related to the fuel smell. The medic began to look into all the openings in the side cowls and observed fuel dripping from a filter assembly. He said, "hey, we have a fuel leak!" The pilot looked and said, "don't worry about it, it's just a drip, these things do that," and walked off to check out the PR.

Time passed and they prepared to leave. The medic asked the pilot again about the fuel leak, the pilot became irritated and told him to get in.

The medic sat still for the engine start and run-up, then announced, "Hey I forgot something, I have to get out for a second." The pilot went back to idle and the medic climbed back out and with his flashlight peered through the opening in the cowl. Jet fuel was spraying in a gusher from the filter assembly...


The flight team in question subsequently decided that this pilot wasn't "the right people," and they cut him loose. Pilots reading this are perhaps excoriating me right now, and to be sure any of the people involved with our work can have the "wrong stuff." Whatever - your job is to actively monitor who YOU are flying with and make sure they are right for you, and for your safety. And you friend have to be the right person too.

At the right time... Our business is one of extreme consequence. A failure or mistake by a surgeon might lead to the death of a patient. A failure by any of us might lead to the death of all of us. So there is no "right time" to do things right. We have to do the right thing every time. All the time. We might let things slip or cut a corner, and get away with it. That will lead us to slip more and more often and eventually we will get caught. Conversely we might let things slip once - and that will be the day... We just don't know - so our job has to be done deliberately, and thoughtfully, and cooperatively - right now

If you are going to fly for two decades, and you don't want to be one of the  forty-percent, make sure you keep yourself in the right place, at the right time, with the right people.

safe flights
f

Sunday, February 8, 2015

Out of Sight But never Out of Mind... Tail Rotor Tales Redux...

I have to admit, Colin tried to warn me.

It was early 2004, and I was undergoing Bell 222 aircraft-transition and single-pilot instrument-flight-rules (SPIFR) training with Omniflight's chief pilot near Dallas, Texas. We were shooting approaches and mixing that with some traffic-pattern work and emergency-procedures training.



While taking a break from the training, Colin had me get out and walk clear of the aircraft, then head back until I was abeam the tail rotor. The point he wanted to make was that the tail on a 222 is much longer and lower than the tail on the BK-117 that I was familiar with. Perhaps because I was tired, and concentrating on all the mistakes I was making during training, I didn't get his message - but he tried.

A few weeks later, shortly after dark, I was flying the Deuce into Richland Hospital's helipad for our contract-opening meet-and-greet. I had two or three other pilots on board, and there was a crowd of hospital-folks on hand; up against the building.  I completed my high recon, and set up for a landing to the west on the patient drop-off pad nearest the hospital, as another aircraft occupied the primary pad.

I was very conscious of being watched as I made my approach, and tried to be as smooth and deliberate as possible in an aircraft that was still  new to me. 

Without even thinking about why, I concentrated on landing dead-center on the helipad, with my aircraft right on top of the "H."  I was completing the shutdown checks, and told the other guys they were clear to exit the aircraft. I sat there filling in the blanks on my forms when my door opened and one of the other pilots told me, "your tail is really close to a fence behind you, you need to shut it down!"  I said, "hold on, I am almost done." He said, "no Dan, it's really close!"

After shutting down, I got out and walked back to the rear of my aircraft, and my knees almost buckled. My stinger, the metal rod sticking out below the tail fin to protect the tail-rotor from a ground strike, was about 4 inches from a 3 foot high chain-link fence. I don't remember seeing the fence on the way in, and if I had drifted backwards on landing......

A pilot affiliated with the customer played it off by saying, "it's no big deal, he landed on the H." But it was a big deal. I almost damaged an aircraft, and and could have hurt some people; and I was actually trying to be careful. 

So, what happened...

Well, as it turns out, what almost happened to me, has  happened to other HEMS crews,  

For example;

Here's a bit from an event in January 2020. "“The pilot had been dispatched to pick up a crew at the hospital but when he landed he noticed a vibration,” said Mary Muhlbradt, Trinity Hospital. “He turned the helicopter off and noticed the tail section got caught in the fencing around the helipad.”

This kind of thing happens regularly.

On July 2, 2009, about 2100 eastern daylight time, a Eurocopter AS 350 B2 helicopter, N53963, operated by Omniflight Helicopters Inc., was substantially damaged while landing at Loris Community Hospital Heliport (5SC5), Loris, South Carolina. The certificated commercial pilot and two clinicians were not injured. Night visual meteorological conditions prevailed and a company flight plan was filed for the medical positioning flight conducted under the provisions of 14 Code of Federal Regulations Part 91. The flight originated from Conway-Horry County Airport (HYW), Conway, South Carolina, at 2040.

According to the pilot, the purpose of the flight was to pick up a patient at 5SC5 for transport. The pilot initiated an approach to 5SC5, to the west, into the wind. As the helicopter approached the helipad, the clinicians were "call(ing)" clear of obstructions, such as trees and light poles. About 5 feet above the helipad, the helicopter shuttered and vibrated. The pilot continued the landing and performed an emergency engine shutdown.

A Federal Aviation Administration (FAA) inspector subsequently interviewed the pilot and clinicians. The FAA inspector stated that although all three persons had been to the heliport before, they simply forgot about several steel poles aligned adjacent to the helipad. Just prior to landing, the tailrotor struck one of the steel poles, and the helicopter came to rest on the helipad.

Two of the four steel poles were about 2 feet high and 4 inches in diameter, and the other two were about 3 feet high and 6 inches in diameter. The poles were placed along one side of the helipad along the perimeter line that separated the helipad from a road.

According to the operator's Vice President of Clinical Services, all clinicians are trained with the pilots in Air Medical Resource Management (AMRAM). Through that training, the clinicians are taught to point out obstacles and hazards to flight.

Examination of the helicopter by the FAA inspector revealed damage to the tailboom, tailrotor, tailrotor gearbox, tailrotor drive shaft, main rotor, and horizontal stabilizer.

The recorded weather at an airport approximately 15 miles northeast of the accident site, at 2058, included calm wind, clear skies, and visibility 10 miles.

The pilot had accumulated 2,587 total flight hours in rotorcraft, including 501 hours as pilot-in-command in the Eurocopter AS 350 B2 helicopters. The pilot logged 46, 19, and 2 flight hours in the previous 90, 30, and 1 days respectively.

Subsequent to the accident, the hospital removed the short steel poles adjacent to the helipad.

“The conclusion of the Pilot involved and the Company Chief Pilot was that the incident could have been averted if the landing to the landing zone had been made further into the landing zone (added: nose into a corner) as to prevent the tail rotor from impacting any obstruction in the vicinity of the edge of the landing zone. Initial and immediate action has been to indoctrinate all pilots flying into medium to small sized landing zones / heliports to position aircraft in such a manner to ensure that all components of the aircraft are clear of all hazards on the periphery and or confines/boundaries of marked landing zones/heliports rather than attempting to place the center of the aircraft at the center of the landing zone / heliport. Corporate wide reassessment of hazards at landing zones/heliports within each regions normal operating area is underway and will be added/updated as needed and posted as part of normal preflight briefings / risk assessments.”


I think the two main factors are a pilot's innate desire to be "squared away," (human factor) and land perfectly on-center on a helipad, coupled with the fact that helicopter landing areas, or "helipads" come in so many shapes and sizes. There are published guidelines for how to construct a helipad, and you have to look no further than the advisory circular at...


to learn all about what a helipad could look like, but in typical FAA fashion they have confused helicopter flight operations with commercial jet travel, and the airports they use and created a document and a set of standards that are, to put it tactfully, unwieldy. 

About a decade ago, the FAA set about making the last advisory circular on this topic regulatoryThe industry pushed back, claiming that complying with the standards would make the use of helicopters too expensive, and would deprive the public of the benefits that helicopters provide. Then the industry went further, and tried to block the publication of the advisory circular (the last iteration) entirely, claiming that the AC would be a de facto regulation by way of lawsuits etc. That dog didn't hunt.

The last time I checked, the only time the advisory circular must be complied with is when a helipad is completed using federal funds. Otherwise, anything goes.



Now when a helipad is obviously an afterthought, it's much like landing at an accident scene, or "off-airport" in FAA-speak. I think these are actually less dangerous than those landing pads that have the look of legitimacy, and are almost correct. When landing on a road, one's senses are on high-alert, and trouble is expected. A hospital pad might be approached with a more relaxed attitude, or even complacency, because it's designed for the use of helicopters, right? 

That was the case with Richland's. It looked legit, but the fence was so close to the pad that unless one landed a 222 diagonally, with the nose tucked well into a corner it was possible to make contact between helicopter and obstruction. That lesson was not lost on me...

Do you see the hazard in this picture?


Every helipad that I have landed on that has been constructed by  http://fecheliports.com/ has been well built, and safe, but even some of these don't comply with the advisory circulars grand designs and details Some FEC structures are more like works of art than utilitarian places to land a helicopter, but if I was in charge of getting a new pad built, and we had money, I would go with them.


As I was briefing this topic this morning, my nurse, an experienced fellow new to us from New York, commented that he would have never thought that landing to the H would present a problem. Okay, he's not a pilot, but a pilot might think the same way.  

A while back some fellow quoted a line from an interesting bit of conventional wisdom, and because of my near-miss with my tail rotor it resonated with me.  The source was posted today on JustHelicopters.com. It is line number 2, for good reason. After rotor RPM, nothing is so important as a working tail rotor for continued success.



So having addressed the fact that people who have no idea about helipad design do so, and understanding that we should approach all hospital helipads as if the designer was trying to kill us; we might also say that in the case of an enclosed, or encumbered rectangle, we should land diagonally to provide the most room, nose-to-tail. 

During my time teaching Air Medical Resource Management for Omniflight, we had more than one tail rotor strike on or near the ground at an accident scene. We tried to figure out how to stop suffering events like this; 

The pilot said that upon landing at the scene he kept the helicopter operating with him at the controls, while the medical crew attended to the patient. After loading the patient into the helicopter, the paramedic did a walk around inspection, entered the helicopter, and called out the before-takeoff-checklist, while voicing an alert to the pilot concerning overhanging trees on the port side of the helicopter. 

The pilot acknowledged, and told the crew that he intended to pick the helicopter up into a hover, slide to the right, and then perform a left pedal turn to exit the scene to the west. The pilot said that while performing a left pedal turn at a hover, a vibration occurred throughout the airframe, and he immediately set the helicopter back on the ground, facing west. 

An EMS technician on the ground who had been observing the helicopter, stated that after the patient had been loaded into the helicopter, the helicopter was lifted into about a 3-foot hover, and then began to rotate and face into the direction of the light wind, coming from the west. After the helicopter completed the rotation into the wind, the EMS technician stated that it then began to increase altitude, and as the altitude increased the tail rotor struck a small pine tree limb that stuck out about 1 to 2 feet into, and over the westbound traffic lane closest to the median. 

He said he heard the change in pitch to the sound of the helicopter's engine, and also saw the tail rotor begin a slight "wobbling." At this point the EMS technician said the helicopter was about 6 to 8 feet off the ground, and he believes that the pilot sensed that something was wrong with the helicopter, and set the helicopter down firmly on the curbside lane, facing west. An examination reveal no evidence of a preaccident mechanical failure or malfunction to the helicopter or any of its systems.

The simplest fix seemed to be asking pilots and crews to minimize manouvering while near the ground, ie. if you fly in and land safely, why not consider staying put, and when you leave, climb vertically until clear of obstacles. Every situation is different of course, but in any case moving around close to the ground is dangerous, and should be thoroughly briefed and understood by all involved - before moving... In the case above, it appears that the crew member attempted to advise the pilot of a nearby hazard, and the pilot acknowledged the advice - and then commenced to hit it. I am familiar with the event and can tell you that they only had to slightly touch a small branch to remove a fist-sized chunk of the skin and core of one of  the tail rotor blades. This put the system out of balance, and the "wobbling" assembly was in the process of ripping itself off the tail fin as you might rip a beer can in half after drinking a few. 

What are we to do? Like the man said, guard your tail rotor... It's back there out of sight, but it can never be out of mind. 

All close-ground movements must be considered hazardous, and should be briefed in detail first

A positive "three-way" communication between pilot and observer might go something like, "guys, I need to bring my nose right and my tail left. Can you clear my tail left?"  

The response might be, "Yes sir, I can see to the left rear and your tail is clear" at which point the pilot would say, "nose right - tail left," and move the aircraft.

Conversely, we might hear,"No Dan, I cannot see to your left rear, or "you are not clear" and then we won't do that move. 

When landing, and there is any question about the size and security of the area, stopping the aircraft at a safe hover altitude, and the pilot announcing, "I want to land here, does this look okay? Can you clear my sides and rear?" will help prevent striking an obstacle. 

This may require clinicians to let the patient go for a few seconds, when one is on board, but in the scheme of things I think it's a fair trade-off...This is simple crew-coordination, and it's how we stay alive.

Safe flights...

Tuesday, January 20, 2015

The Safest Flight Program in the Land?

Ask the question, "What will be the cause of our next crash, and what are we doing to prevent it?"


Mirror mirror on the wall...

Who has the safest program of all?


There is an old legend that says the program that just suffered a fatal crash is the safest program flying. Like a huge control-alternate-delete, a fatal crash resets all of our notions, our beliefs in right and wrong, our ideas about what's most important. Much has been written of late about culture in flying organizations - the current buzz-phrase is "just culture." Companies are quick to boast about how they adhere to these principles, but there is more to just culture than a press-release.

Why should anyone care? Because culture is part of why helicopters crash. And culture starts with the top man or woman in an organization, seeping all the way through to the person who got hired yesterday.

"You sweep the stairs from the top down..." NTSB board member Dr. Earl Wiener

Bill Winn and I just finished speaking on the phone for about an hour. Bill is NEMSPA's only paid employee, managing the day to day business of keeping NEMSPA's lights on and our wheels turning. He called because he had some questions about the progress of the action-team I am on advising the FAA on new rules for HEMS training.

Bill wondered if we are addressing the actual causes of crashes as we discuss how training should be changed. In the conversation, he described multiple factors that lead to crashes - there will be no silver bullet answers.

The military is said to always be training for the last war. That way of thinking may affect (or infect) some of us. We train for the last crash, we focus on the pilot who flew too far for his fuel load, or flew into a storm or the clouds, or lost engine power after ice-ingestion, While learning from other's mistakes is certainly time well spent, the reality is that there are too many factors involved in a crash, too many root causes. Chopping off one root or another won't kill the chances of another crash.

So what's the answer? I believe it is concerned, interested, involved leadership. Have you ever heard of management-by-walking-around. How about "the one minute manager?"  In a business with such high-consequence for any mistake, one minute isn't enough. Leadership cannot push the auto-pilot button, and tend to other tasks. While thousands of problems will keep the phone ringing and the inbox full, the one-two-punch  questions when helicopters are flying through night skies must be...

ARE WE AS SAFE AS WE CAN BE WHILE MAKING AS MUCH MONEY AS WE CAN MAKE?

A  commitment to safety and making money are not mutually exclusive goals. Being safe allows your company to make more money in the long run. And being safe keeps the guy or gal in charge from having to explain to the press why your helicopter crashed, like the leader in the picture below... You don't want to be "that guy."




Tom Madigan of County Rescue pauses as he reads a statement concerning the crash of an EAGLE III helicopter during a news conference April 13, 2006. Photo by H. Marc Larson/Press-Gazette

To learn more about the crash in Green Bay, click here...


Ask the question, "What will be the cause of our next crash, and what are we doing to prevent it?" Really, this is important. It's right up there with profit margin, same-store-sales, or transports at a base opened more than a year. Defending against your next crash should be the first thing, and the last thing you think about every day. And every soul in your employ should know that's how you think.

Especially if you have an excellent safety record. A history of being safe leads to complacency and the loss of the "safety imperative."

According to Wiener, "Complacency is caused by the very things that should prevent accidents, factors like experience, training and knowledge contribute to complacency. Complacency makes crews skip hurriedly through checklists, fail to monitor instruments closely or utilize all navigational aids. It can cause a crew to use shortcuts and poor judgement and to resort to other malpractices that mean the difference between hazardous performance and professional performance." (E. L. Wiener)


#onefullyearnofatalcrashes

Be careful out there...


Friday, January 16, 2015

FLASHBACK FRIDAY...What if both engines quit?

In my post titled "What If?" I considered losing both engines in a twin engine helicopter. (Click here for that post)

It turns out that it has happened more than once, and just as my fictional pilot "Dennis" successfully landed his machine, so did this real life professional.

Bayflite crash-lands on I-275



(Palmetto-AP) -- The pilot of a medical helicopter says he heard
a loud bang just before one of his engines caught fire, forcing him
to make an emergency landing on a state highway.
Amund Moe, pilot of the B-K-1-17 helicopter from Bayfront
Medical Center, told hospital officials he also had trouble with
his second engine. He killed both engines and glided to a rough
landing on Interstate 2-75 in northern Manatee County last night.
Nobody was injured. The infant patient aboard, who was being
transported from Naples Community Hospital to All Children's
Medical Center, is in good condition today.
The Federal Aviation Administration is investigating.


An infant patient and three crew members escape unharmed after the "hard landing''near the Skyway.


The NTSB report...

 The pilot said that while in cruise flight at an altitude of 1,000 feet, a speed of about 130 knots, and about 60 percent torque, without warning he heard a loud explosion from the right side of the helicopter, with simultaneous No. 2 engine fire and failure warning lights and indications, along with severe vibrations. He said that the helicopter yawed several times from left to right and he heard a "whopping" sound. He also said that at the same time the No. 1 engine torque meter needle moving rapidly from about the 9 to 3 or 4 o'clock positions on the gauge. The investigation revealed two of the power turbine blades and four rear bearing support housing (RBSH) failed in overload. The hub had been displaced from the engine centerline, and a deflection had occurred at the engine case axial midpoint, along with a misalignment of the inlet housing and the rear bearing support housing (RBSH). The resultant damage to the gas producer (GP) system, was consistent with an assembly error and mechanical failure having occurred by the loss of critical internal operating clearances and radial support for the rotors. Continued engine operation as the failure progressed led to compressor surge and the emergence of combustion gases from the No. 2 engine inlet, which ignited inlet cowling material. The No. 1 engine ingested smoke and combustion by-products from the engine cowling fire which caused a temporary stall condition.
The National Transportation Safety Board determines the probable cause(s) of this incident to be:
Improper maintenance/installation of the No. 2 engine power turbine (PT) wheel assembly by company maintenance personnel, which resulted in deflection at the engine case axial midpoint and misalignment between the inlet housing and the rear bearing support housing (RBSH) which resulted in damage to the engine and an in-flight fire.


By TAMARA LUSH and LEANORA MINAI
© St. Petersburg Times
published August 27, 2002
Related video
56k | High-Speed

A Bayflite helicopter carrying an infant patient caught fire over Tampa Bay late Monday and was forced to make an emergency landing near the Sunshine Skyway bridge in northwest Manatee County.
Neither the infant nor four crew members were injured when the helicopter made a "hard landing" about 8:35 p.m. on Interstate 275, between the south Skyway toll booth and U.S. 41.
Crew members jumped out of the helicopter and carried the infant to safety. A second Bayflite helicopter arrived about 20 minutes later and transported the child and two crew members to Bayfront Medical Center in St. Petersburg.
"When the helicopter landed it was engulfed in flames," said Gerald Pochodaj, who was driving toward the Skyway when he saw what he thought was a low-flying airplane.
Pochodaj said crew members carried the baby and incubator to safety as flames shot from the right engine.
"These Bayflite folks are the best at what they do," said Bill Hervey, manager of public relations for Bayfront. "They save lives every day. The patient wasn't hurt, the crew wasn't hurt, it was perfect."
The names of baby and the crew members were not released late Monday.
Hervey said Bayflite 3 was 50 minutes into its trip, transporting the infant from Naples Community Hospital to Bayfront, when the warning lights went on, signaling an engine problem.
Another witness saw a small ball of fire near the helicopter as it crossed the bay. One of his children said, "the helicopter . . . it's on fire!"
"You could see a good-sized ball of fire," said Danny Ward, 40, of Bradenton, who was in Rubonia at his sister's house.
He said it was headed toward St. Petersburg and then banked sharply and landed. He said he assumed it did not crash because they didn't hear or see anything.
"That was a good pilot," Ward said.
Pochodaj, an engineer at Transworld Diversified Engineering in Tampa, said the pilot told him that dash lights lit up, the helicopter filled with smoke and they knew they had to land. He called the rescue of the baby heroic.
"Their instinct was to do their job," said Pochodaj, 36.
After the baby and some crew members were picked up, a third helicopter retrieved the remaining crew members.
"Everybody's safe," said Cassandra Morell, Bayfront Medical Center spokeswoman.
The Federal Aviation Administration will investigate why the twin-engine BK-117 developed engine trouble and was forced to make an emergency landing, said Kathleen Bergen, FAA spokeswoman.
"I understand there may have been an engine fire," she said. "Were there mechanical problems? Operational problems?"
A Bayflite maintenance crew dismantled the craft's rotor blades to make it easier to transport. The green and silver helicopter, its right engine charred, was being moved late Monday to a Sarasota airport, home of their Bayflite 2 base, on a flatbed truck.
Hervey, of Bayfront, said the pilot and copter are from Rocky Mountain Helicopter out of Provo, Utah. They contract out staff and equipment, he said.
Such pilots have to have a minimum of 2,000 flight hours to do this kind of work, said Hervey, adding that representatives from Rocky Mountain are coming here to assess the damage.
The hospital routinely has four aircraft in service but keeps a backup, which will immediately go into service.
The last Bayflite helicopter crash was on April 25, 2000, when the medical helicopter hit a radio tower near the Gandy Bridge, killing all three crew members.

Click here for the Sarasota Herald-Tribune story...

Sunday, January 4, 2015

Tower 2000 feet - Dead Ahead...

Mike Mock, pilot with Memorial Hermann Lifeflight writes:

I had a discussion last night with FSS about a 2000' tower near Houston that had the lights out. Apparently they can't post a NOTAM based on a pilot's report, it has to come from the owner of the tower. He asked if I could drive by and find out who owns it, "it's usually on the fence". Uh, no, I flew past it at 0230 and it had no lights. He said he may try calling the local sheriff or something.

This is enough to make the short hairs on your neck stand up. An unlit tower standing 2000 feet up into the sky is a death trap looking for a victim. So how do we avoid being said victim?

In Mike's case, technology gave him a big assist. The aircraft he is flying has equipment that displays tower locations graphically. I have no such equipment in the aircraft I fly. While NVGs increase our ability to see at night, we could easily be upon a tower before seeing it under goggles.

The FAA requirement to check a route prior to flying it has been in effect for several years now, and we haven't had a tower strike in a while. I wonder if pilots are becoming a complacent about completing this step prior to lift off - just a glance at a chart. " I am here... going there.... there's the highest tower..."  Even the most dedicated pilot can get a route change, or deviate for weather or ATC or traffic. In that case, the preflight check no longer works. We really have to be familiar enough with the area to simply know where the big ones are.

It's a big sky, The odds of striking a tower are small. But it happens.


The aftermath of a tower strike


The National Transportation Safety Board attributed the fatal 2008 crash of an Air Angels medical helicopter in Aurora to the pilot's "inadequate preflight planning" and flying too low, which caused the copter to strike a radio tower.
"During preflight planning, the pilot should have identified the obstacles along the route of flight, including the radio station tower," the report said.
I am on duty at a "new" base, on night shifts. On my arrival I was advised about a large unlit tower near here, then another pilot mentioned another one. Checking NOTAMS will reveal a long list of unlit towers in the area, too many to keep up with. I note the ones above a thousand feet, and try to memorize those locations. Being unfamiliar with the area, my night altitude minimums are higher than normal. If the weather won't let me fly at these higher altitudes, I won't go.

I asked a friend about a number to report unlit towers, Stu
writes...
  • The number I have is to the FAA to report unlit towers. 877-487-6867. I haven't used it yet. I don't know if it works.