PLBs and Plenty of Zs

I'm still here! Didn't want you to think I'd gotten tired of SAR blogging. No, there just hasn't been a lot of action lately. At least, nothing that's panned out.

We did have a call last Monday morning, I think it was, around 9 a.m. I was in Walmart at the time (yippee!), looking for stuff for our new house, when my back pocket started beeping a tune. A 200 (search) page for a couple of overdue woodcutters on or near the Hualapai Reservation, which is about a three-hour drive from Flagstaff.

It turned out to be a good drill, basically. Several of us proceeded to load tech gear, ATVs, the Ranger UTV, cubes of water, MREs and snacks, and full gas cans, then drove for about 15 minutes before the mission was 10-22'd. The woodcutters had been located near Peach Springs. So we did an about-face, returned to the SAR building, and unloaded and put away all the gear. And that's been about it over the past couple of weeks. I've had way too many full nights of sleep. I'm thinkin' something will happen soon.

Oh, and we did have another cancelled call-out on the afternoon of Saturday, October 25, just as we were finishing up a rather frustrating personal locator beacon, or PLB, training. (I'll get back to that in a sec.) It sounded like a pretty dire call at that. A girl—not sure if it was an adult or child—had been attacked by bees about four miles up the West Fork of Oak Creek, and she was having an anaphylactic reaction. It was going to be a tough litter-carry, possibly involving some wading in places where the creek fills the canyon. And word through the grapevine was that first responders (not sure if that meant medics, deputies, or civilians) were already "working a code." So we were thinking this might end up being one very rugged body recovery by the sound of things.

On my way across town to the SAR building, though, the mission was cancelled. At the time, I thought perhaps the girl had been short-hauled since her condition was apparently very serious. But I later found out she'd been given epinephrine and walked out on her own. Glad to hear that.

So, back to the PLB training. To read specifics about this and other types of devices used to transmit distress signals, you can visit the Search and Rescue Satellite-Aided Tracking, or SARSAT, website. As for me, I refer to the thing that emits the distress signal as a "gadget," and the device responders use to track down the gadget (and hopefully the person/s needing help) as a "gizmo." Gadget and gizmo... got it?

So, first we had a classroom session. We learned about the different types of beacons—PLBs used for land-based applications, ELTs for aviation use, and EPIRBS for maritime use—and the basics of how they work. Seemed pretty straightforward at that point.

Then, we went out behind the Sheriff's office, where Sergeant D turned on the training PLB gadget, and we walked a couple hundred yards across the parking lot where we used the gizmo to locate the gadget. Of course, we could see the gadget from where we were standing with the gizmo. Straight line, no obstacles, flat terrain. I understood how it worked and figured, hey, this is easy!

And then it was time to take the gadget and gizmo into the field. We relocated to Fort Tuthill, where the plan was to take turns going off into the woods with the gadget with about a 10-minute head start, and then the rest of the group would use the gizmo to locate the source of the distress signal.

Well, the first time out, things went fine. Trees, yeah, but pretty flat. Now, the gizmo, by the way, makes a continuous, rather annoying sound—a constant, high-pitched, whiny beep—which the responders have to listen to the whole time they're searching. This first trial didn't take us that long so none of us mentioned anything about stomping on the whiny thing. Second time around, though: different story.

We were all over the place, with me using the gizmo for the first hour. At least, it seemed that long. But the thing couldn't seem to make up its gizmo mind. I was getting conflicting signals, first this way and now that. We were now in hilly terrain with lots of rocks and other obstacles, and I guess the signal was bouncing all over the place.

Eventually, I held the gizmo out to Sergeant D and asked (trying not to sound desperate), "Do you wanna try?" thinking at that point, I must be doing something wrong. I'm not sure what our leader was thinking, but he wasn't saying much as the rest of us followed him follow the gizmo.

A few members of our team, who'd been using the low-tech method of detecting a PLB signal with a radio set to a certain frequency and a body shield (if you really want an explanation, feel free to let me know in the blog comments, and I'll give it my best try), had disappeared. I hadn't noticed they'd walked off, leaving just me and another lady following Sergeant D. I looked around and didn't see them anywhere.

Eventually, Sergeant D radioed the others, and we learned they'd found the guy with the gadget a long time ago. What? The gizmo had failed us while the low-tech method had worked? When I saw where the guy with the gadget had been the whole time, I realized we'd passed pretty close to his location early on in the search. Ugh.

So, then Sergeant D took the low-tech method out of the equation, grabbed the gadget, wished the rest of us luck, and took off to hide. Basically, the gizmo took us in a huge circle, leading us to think Sergeant D was on the move with the thing the whole time. So, a moving distress signal, right? We even thought, based on the signals we were getting, that he'd gone back to the vehicles. But, when we got there, not only was there no sign of Sergeant D, but the gizmo was registering no signal at all. Nada. Dead.

Frustrated, we called Sergeant D on the radio, and he gave us coordinates. We used our GPSes to go to those coordinates, thinking we were looking for him and/or the gadget, but we soon realized he'd gotten us fairly close but not right to the spot. He continued to give us hints; we continued to try to follow the directions the gizmo seemed to be leading us in, but we wandered all over the place with no luck. Finally, thankfully, Sergeant D called the whole thing off. We'd apparently walked right by him more than once.

Was it the hills and obstacles interfering, making the signal bounce all over the place? Or was it us, the searchers using the gizmo, who were the problem? What I do know is that I was hearing that whiny beep in my dreams for several nights thereafter.

A Search for Moving Targets

We were sitting in a coffee shop again, my husband and I, when my pager went off. That's a common pastime for us on Sunday afternoons, when we like to relax and chat. At about 7:00 p.m., after several hours of that relaxing and chatting, we were just getting ready to peel our butts off the vinyl seats when I got the call-out for a rescue on Mt. Elden.

I thought I'd be the last one to the SAR building since I had to drop Steve off at home before driving across town. But only two of the eight volunteers responding were there when I arrived, and as it turned out, we all had to stand by for another hour anyway. Two tech team members were already on the mountain doing a hasty search, and, via radio communications, it sounded as though the rest of us might not be needed at all—just a couple of hikers without lights who'd lost the trail. However, a second potential SAR mission was unfolding at the same time.

And it was that second situation the eight of us responded to, ending up an hour south in Sedona instead of ten minutes away on Mt. Elden. Two stranded mountain bikers had used a cellphone to call for help.

When we rendezvoused with the deputy waiting at Midgley Bridge, he called the subjects and asked them to turn on their headlamps, which we immediately spotted in the distance—little pinpoints of light against the dark backdrop of a mountain. Well, this didn't look like a big deal, really.

Uh-huh.

Victor, our team leader that night who knows the area well, suggested the best course of action would be to hike from the other side of the ridge, from Schenbly Hill Rd. up and over the saddle, and descend to the subjects, then bring them back the way we'd come.

Steve and I had hiked that non-system, or what some call "social," trail, most of which is not on the map, a couple of years ago, and I recalled it being tough to locate in places on the other side of the mountain while fairly easy to follow on the side where tonight's subjects were. Obviously, though, the bikers had strayed quite a distance from the trail. But since I couldn't remember where to access the beginning of the trail on their side of the mountain, I didn't suggest an alternative to Victor's plan. By contrast, the access on Schnebly Hill Rd. is easy to locate because the route begins with a short out-and-back trail that is on the map, and that trailhead has its own parking area. (Hope that makes sense.)

So, the eight of us drove around to Schnebly Hill Road, which apparently hasn't seen any maintenance in years, and arrived at the trailhead about 40 minutes later. It was a rough ride, and I'm surprised none of the three SAR vehicles ended up with at least one flat tire.

Before beginning the hike, Victor divided us into two teams, designating me the leader of Team 1—my first time officially being named a leader. (I had to smile at that. How cool.) I'd communicate with Incident Command back at Midgely Bridge on 1-Baker, while another team member would keep her radio on the SAR frequency for communication between us and Team 2 when necessary. The other two members of Team 1 would keep their radios off for the time being, to preserve the batteries. Then the eight of us started up the trail together.

As we went along, we set out glow sticks in spots that were a bit confusing or might prove to be on the way back. At one point, we had to bushwhack around a stretch where the route would have taken us too close to a fall hazard. Erring on the side of caution as we're always supposed to, we picked our way through some cactus, coming back to the trail in a safer spot to continue the traverse.

Soon, we ascended an open slickrock face to a flat area not far from the saddle. At that point, our two teams split up. Mine would stay put while Team 2 went up and over. Team 1 would stand by in case backup was needed and eventually take over when the subjects were retrieved. They'd be handed off to us for the descent to the vehicles.
 

Maybe that second part—the hand-off—was merely to make my team feel more useful, but there really was no need for all eight of us to continue to the subjects, especially because the going would get rough off-trail. So, my group of four made ourselves comfortable and enjoyed a beautiful, still night filled with moonlight and shooting stars.

While one of my teammates, new to the unit and rearing to go, was very fidgety and not happy about staying behind, I was quite content. I've learned over time that we all perform a function during a mission, even if we have to sit tight for a while. Sometimes, waiting as backup becomes vitally important. Even searching an area with a low probability of finding a subject, or driving perimeter roads while other team members are searching high-probability areas, is crucial to a mission, even if it means just ruling out, or "clearing," those places. Besides, after not hiking this route for quite some time and my memory of the details being fuzzy, I felt the four team members who continued on were best skilled to deal with a potentially technical situation, especially with it being darker on the other side of the saddle despite the bright moon, in the mountain's shadow.

As it turned out, I'm glad I was on the team who stayed put. Monitoring radio communications between Team 2 and IC, I could hear they were encountering some difficulty. When they left the trail to try to access the subjects, Team 2 soon found themselves in a tricky spot with significant fall hazards. And, in the meantime, the subjects had become moving targets, apparently now trying to self-rescue. Despite phone calls from the deputy and verbal communication between Team 2 and the subjects, shouting back and forth, the two men who'd called for help were not listening to those who were trying to help them.

At that point, Team 2 had gone far enough down the other side in rough terrain that backtracking would have been more difficult than continuing a descent toward Midgley Bridge... with or without the subjects. The fidgeting member of my team kept asking me to call and see if he could go join Team 2 since he's from Sedona and felt he knew the area better than they did. When I refused to make that call, he asked why we shouldn't just go back to the vehicles then. But I felt we should stay where we were until Team 2 or Incident Command instructed us otherwise. We had radio communication, so they'd let us know.

At the same time, I didn't feel it necessary to interrupt Team 2, as they were obviously busy negotiating hazardous terrain. So, I had a wee bit of a tug-of-war, shall we say, with the one teammate who, like every SAR member, will have to get used to taking direction from those with more experience. I got instructions from Victor, and my new teammate would have to live with a few decisions from me. So there.

After listening to Team 2's increasingly frustrated transmissions for quite some time, Victor told IC they'd decided to hunker down and stay put till daylight, when it would be easier to see. They were still in voice contact with the subjects who had by then split up. Meanwhile, my team was instructed to return to the vehicles on Schnebly Hill Rd. and drive back around to IC at Midgely Bridge, where we'd see what our next assignment would be, if any, for this mission. On the hike back to the vehicles, we collected the glow sticks we'd set out on the way up, after first confirming with Victor that his team wouldn't need them.

When we arrived at the bridge more than an hour later, nothing had changed. There was some talk about our Team 1 hiking another trail to try to get close to the subjects from that way, but we and the deputy decided that wasn't such a hot idea. Comparing the location of the subjects and the nearest point on that trail, the distance between the two was significant given the terrain. Instead, we decided to make a run into town for coffee and snacks, then return to IC and wait.

To make a long story a bit shorter, I'll wrap this up by saying that one of the two subjects made his way to the SAR members still in the field. At that point, he just wanted water for himself and his buddy, and SAR gave him what he asked for. Victor then decided to assist the mountain bikers down to the trail my team had briefly considered hiking up, though the two men would have to carry their bikes.

Once on the well-maintained trail, Victor and his two teammates left the subjects to ride or walk their bikes out on their own. Team 2 arrived at the road maybe 10 minutes before the subjects, wet past their knees from the creek crossing. SAR waited until they arrived and were being interviewed by the deputy before we departed for Flagstaff.

After a 10-hour mission that we thought would take less than half that time, we signed out and headed for home just as the sun was coming up.