Flying the Mil Mi-24, crash safety progress, attacking the Thomas Fire, Germany’s ADAC, and more!
Editor’s note: This article originally appeared in the AMTC 2017 issue of Vertical 911.
I wish I could say that it was my idea.
I wish I could say that having a medical team member call out checklist items prior to takeoff was something I cooked up.
I thought perhaps it was my old paramedic friend Les Langdale’s idea — he was the safety representative at the base in Charleston, South Carolina, where I first encountered the practice while filling in for a pilot who was out sick.
I called Les and he told me it wasn’t his idea. They were doing it at Meducare Air, the program owned by the Medical University of South Carolina, when he started there in January 1988 — so it must have been someone who started the program in July 1987.
I had to reach back further, to a pilot who started that base and this industry.
I looked on my phone’s contact list and there he was: 75-year-old retired helicopter pilot Dave Andrews. I gave Dave a call. “Dave, do you remember who it was that had the idea of posting some checklist items in the aircraft on a placard?”
“Oh! Let me think… You know, it was probably me!” He then told me some stories about the early days of helicopter emergency medical services (HEMS). Two or three pilots flew on a contract. Pilot shifts covered a full 24-hour day — or more.
They called it helicopter emergency medical evacuation services (HEMES) then, and the rules for HEMES are still in the Code of Federal Regulations; a vestigial reminder of how things have changed. There were no operational control centers and no need for a flight release. There was less scrutiny. After killing so many people and destroying so many aircraft, we have evolved how we operate. We continue to evolve to prevent our extinction.
Dave mentioned that all across Omniflight, pilots were starting helicopters from memory. There often wasn’t a checklist in the aircraft. Just a flight manual — a thick book situated under or behind a seat. He said, “We printed a checklist on paper, but it kept getting lost. So finally we had a placard made and posted it on the instrument panel. That worked fine right up until we had to send the helicopter back to Omniflight for some modifications. An FAA [Federal Aviation Administration] inspector had to come look at the mods, and when he saw that placard he had a fit.”
The FAA guy said, “DOES THAT MATCH THE INFORMATION IN THE ROTORCRAFT FLIGHT MANUAL? HOW ARE YOU GOING TO UPDATE CHANGES ON THAT?”
Dave chuckled on the phone and said, “That was a real big deal. I was hiding under my desk for a while.” But they got through it, and they kept their placard. And it was there on the instrument panel with an identical copy in the aft cabin when I showed up in 2001, 14 years after they started.
Somewhere along the way, Meducare Air had adopted the practice of having the paramedic sitting in the front seat call off the items, one at a time. First, the pilot would start and prepare the aircraft from memory, and then he would pick up his checklist and scan it for any missed items. That is “do-verify.” It is an “acceptable” method of checklist accomplishment and common in single-pilot operations. Then the pilot would stow the checklist and ask for the placarded items to be called off.
The pilot would put his fingers on the control or switch for the item being challenged and verbally confirm that it was set correctly. This “challenge-do-verify” method (or challenge and response) is a more deliberate method of ensuring that the aircraft is configured for departure — that the critical switches and controls are set correctly.
They didn’t have every checklist item on this placard, only the ones that would kill you or destroy the aircraft. They added “drugs and mission equipment” because on more than one occasion they had departed without something needed to care for a patient. The medical team is human, too.
So it wasn’t the Charleston ship that took off with the fuel transfer pumps in the off position and the instrument lights on early one morning shortly after sun-up. It was an Omniflight ship in Texas.
The day pilot had arrived just as a flight request was coming in, and he decided he would take it. The night pilot had left the instrument lights on, making the master caution and warning and caution panel segment lights virtually invisible. In his haste, the day pilot forgot to turn on the transfer pumps. The aircraft’s engine supply tanks ran dry in flight with the mains almost full. The engines quit and the landing was “hard.” That pilot was paralyzed.
A pilot forgetting to switch on transfer pumps that fill supply tanks has happened more than once. It happened in a medical BK117 in New Zealand in 2014. It apparently happened in a Police Scotland EC135 in 2013. If we don’t change how we operate, it’s going to happen again.
In November 2002, an Agusta pilot in Texas attempted to take off with one motor at ground idle. From the National Transportation Safety Board (NTSB) report, “In an interview, the pilot reported that ‘he attempted a rolling takeoff . . . with an incorrect power setting (selection switch) which resulted in an emergency (hard) landing on the roof of an adjacent automobile parking garage due to insufficient engine power to maintain flight.'”
While flying a Dauphin at State College Pennsylvania in 1999, I did the same thing — minus the hard landing. I got in a hurry, I was trying to beat some taxiing traffic, and I did a rolling takeoff with one motor at ground idle. Shortly thereafter, my friend at another base did the same thing. A good and smart pilot, he got a Dauphin up in the air and over wires before realizing that one of the motors was set to ground idle.
Krista Haugen, a co-founder of the Survivor’s Network for Air Medical Transport, has first-hand experience with this issue. She lived through a crash near Seattle that occurred because her pilot took off with one motor at ground idle.
I know of three crashes with pilots attempting to take off in AStar helicopters with hydraulic switches set incorrectly. In two of the three, people were killed. In each of these cases, the pilot failed to properly configure the aircraft for takeoff. This problem cuts across all lines of attitude, age, and experience.
We can look at all these accidents and say, “Well, that pilot was inferior. He made a mistake I would never make.” That’s invulnerability talking. On the other hand, we can recognize that humans, by our very nature, make mistakes. Our personalities are composed of the cognitive, the emotional, and the behavioral. Three chances to get things right. Three chances to get things wrong. We get in a hurry, we get distracted, we get complacent or we get tired, and we miss something. They did it. I did it. And you or your pilot might do it too.
After filling in at Charleston in those early years, I brought up the practice of challenge and response at a monthly safety meeting at my home base in Savannah, Georgia. I explained what they did in Charleston, and why they did it. My aviation base manager, Dutch Martin, looked around the room and said, “This sounds like a reasonable idea. It’s not instead of, it’s in addition to. Do you all want to do this here?”
Lifestar Savannah adopted the practice. When Omniflight expanded our service and opened a base in Vidalia, Georgia, the practice went there, too. It’s all they ever knew. No one thought twice about it. None of those bases ever had a problem related to missing a switch or control. Everyone on board knew when the aircraft was going to take off; everyone was “in the loop.” More than once a mistake was caught — before takeoff.
I discussed using a medical team member for challenge and response with the director of flight operations of a large air medical company three years ago. He said he endorsed the idea and would take it up with the chief pilot. But nothing was done and the crashes in that company continue.
Another DO told me that the medical side of the business has intruded into the aviation side enough — that the answer is training and standardization for the pilot. I don’t think you can train the human out of a standard pilot. But you can add a layer of safety to account for the human factors at play.
Is any safety layer perfect? Does any practice or procedure absolutely prevent disappointment or disaster? No. I know about the Swiss-cheese model and slipping through the cracks. But if making a change eliminates a majority of mishaps, if we can save a life or two or a helicopter, shouldn’t we keep our minds open to the idea of change?
A National EMS Pilots Association friend noted that many programs have never had the issue of taking off with a switch or control in the wrong position, and it’s not fair to ask them to change how they operate. It is impossible to tell people how to feel about something. But I would like people in our industry to consider my proposal. After all, many programs have a perfect history, right up until the minute they have a crash. Were they good? Or were they lucky?
Some have suggested I delay and perfect this proposal before putting it out. That I conduct surveys. That I do research. I have all the information I need now. It’s in the NTSB reports.
I published a position paper about this on my blog at HelicopterEMS.com, and linked it to the Facebook page with the same name. At last check, 15,536 people have read my proposal. It’s been shared 52 times. People are interested in this idea.
It’s probably the medical folks at your base who hope and pray that you never make a mistake. If you are their pilot; they like you, and they trust you. But like you, they are human and subject to error. They know this. They double check medications, dosages, and intervention plans with each other. They help each other avoid a mistake. They would be happy to help ensure you don’t make a mistake as well.
Many programs already incorporate some form of challenge and response. If yours doesn’t, I hope you will consider it.