Brilliance in the Basics

By Bryan Howell | Prevail Rescue Solutions

A steep-angle rescue on the Timber Fire reinforced something I keep coming back to at PRS: advanced capability does not always require a complicated solution. It requires prepared people who understand the fundamentals, recognize what matters, and can adapt without losing the patient in the process.

We spend a lot of time in the rescue world talking about advanced techniques. Advanced rigging, advanced equipment, advanced courses. Somewhere along the way, it becomes tempting to measure capability by how complicated we can make the solution.

I like technical equipment as much as the next person. Probably more than my wife would prefer. But I do not believe every rescue needs to become a demonstration of everything we learned at the last conference.

Sometimes the most valuable thing an experienced rescuer brings to the incident is the judgment to recognize what is needed—and what is not.

That is what I mean by brilliance in the basics. Not doing less because we know less. Not removing capability because carrying equipment is inconvenient. It is understanding the problem well enough to apply a straightforward solution, execute it competently, and recognize when that solution needs to change.

The August 15 extraction on the Timber Fire provided a very practical example.

Timber Fire: A Straightforward Problem, a Straightforward Response

On August 15, 2026, Rapid Extraction Module Support—REMS 21 was staged on Division Bravo when radio traffic indicated a medical emergency on the adjacent Division Delta. A Fuels Crew member had fallen approximately 150 feet down a steep canyon face, coming to rest above a river. Witnesses reported a loss of consciousness, and the patient subsequently complained of severe lower-back pain. The REMS resource assigned to that Division was in a communications dead spot, not fault of their own; just the hand they were dealt at the time (Big Sur is notorious for communications problems).

REMS 21’s drive to the incident took approximately ten minutes. A Line Medic had already accessed the patient and initiated care. The response was therefore not starting from zero; the arriving team was building on work already underway. We were a reinforcement, or a cog, in the chain of rescue.

The rescue used a human—or “meat”—anchor single-rope technique for initial rescuer access. The UTV was incorporated into the topside anchor arrangement, and a simple 3:1 mechanical-advantage system supported the raise. The REMS medic supplemented the initial medical care with analgesia, and the packaging plan changed from a SKED to a rigid Stokes basket based on the patient’s symptoms and the need for greater structural support. Fuels Crew personnel helped haul while rescuers managed the litter and technical work.

From REMS 21’s arrival through access, treatment, packaging, and rope extraction, approximately 28 minutes elapsed. Including the vehicle response, the report documents 38 minutes from departure at Drop Point 15 to transfer into the waiting ambulance. Those are specific intervals—not the time from the fall to hospital arrival, and not a universal benchmark for the next rescue.

The ambulance moved the patient to a helicopter landing zone for transport to a trauma center. The RLS reports that the patient was treated and released that night and was able to return to work.

For me, the useful lesson is not that everyone should copy that exact rigging configuration. It is that the response connected the necessary pieces without adding work that did not serve the patient. It proved that pre incident planning is KEY during your work cycle, and it proved that we met the problem set with a matching solutions set. We didn’t force anything we didn’t have to.

The problem was serious. The solution did not need to be unnecessarily complicated.

Simple Systems Require Serious Understanding

This conversation did not begin on the Timber Fire.

In Refining Operational Vertical Mobility, Part 1, the 2021 article I coauthored with the Dark Wizard himself Sean McKay, we described operational vertical capabilities as needing to be “adaptive, principle-based, and relatively simple.” The argument was not that technical knowledge could be skipped. It was that responders needed to understand the environment, organizational expectations, and available resources rather than force every incident into a memorized rigging template.

The same paper makes an equally important point: a technique that works for one team in one context may fail when another team applies it somewhere else. Operational vertical mobility is a framework for making informed decisions, not a collection of universally correct answers.

That distinction matters here. A human anchor, single-rope access, a vehicle-based anchor arrangement, or a 3:1 haul is not automatically appropriate because it appeared in a successful incident report. The report describes what this team used in these circumstances. It does not provide enough information to turn those choices into a stand-alone rigging prescription.

Element Rescue’s 2022 On Operational Verticality manifesto adds another important layer. Alongside its emphasis on efficiency and adaptability, it calls for a reluctance to oversimplify the incident: keep looking for failure, question assumptions, understand the team’s limitations, and listen to the person with the relevant expertise.

Simplify the execution. Do not simplify away the hazards.

Brilliance in the basics requires both. A straightforward system operated by someone who understands its limitations is a very different proposition from a straightforward system operated by someone who does not know what they are missing.

The Fast Part Started Before Arrival

It would be easy to look at Timber and make the entire discussion about the 3:1, or the stokes rigging, or the UTV anchor, but that would miss a large part of the lesson.

The RLS identifies radio monitoring and anticipatory movement as contributing factors. REMS 21 recognized the developing problem and began transitioning from training to response before receiving the formal assignment, with confirmation subsequently received from Operations. The report specifically distinguishes that preparation and movement from bypassing command.

There is a difference between initiative and freelancing. Operational awareness should help a team prepare to act within the incident structure, not become an excuse to abandon it.

Geography mattered, too. The adjacent team’s proximity created useful coverage when the assigned resource could not be reached. The report’s planning lesson is that a named REMS resource on each Division is not the whole coverage picture. Cross-Division access, travel time, communications, and the ability to cover temporary gaps also matter.

Then there was equipment readiness. The team left nonessential training equipment behind while retaining its operational rescue and medical capability. Using the UTV in the anchor arrangement was not an idea invented over an injured patient; we had practiced that application repeatedly across several deployments and it was part of the setup process within our PACE plan.

That is the kind of preparation I want us paying attention to. Not just whether the equipment exists, but whether it is ready, accessible, familiar, and connected to a plan the team can execute.

Efficiency begets Speed is useful here because it directs attention toward the entire response, including transitions and overlooked delays—not simply making one isolated task faster. Before adding another pulley, it is worth asking where the time is actually going, and will you make up for it by implementing additional steps. Sometimes yes, sometimes no.

The Patient Is Not an Accessory to the Rope System

One of the strongest lessons from Timber had nothing to do with mechanical advantage.

The initial packaging plan changed.

The team intended to use a SKED, then selected a rigid Stokes basket based on the patient’s symptoms and support needs. The RLS describes that as a patient-centered adjustment rather than rigid adherence to the original equipment plan. That is worth sitting with, particularly for those of us who spend a lot of time promoting lightweight systems.

Light and fast does not mean the lightest piece of equipment must win every decision. Our previous discussion of good REMS teams made the same distinction: equipment selection should support the patient, terrain, staffing, and movement plan. The objective is appropriate capability, not minimal weight at any cost. Specialized Training Solutions

We should be willing to change our equipment plan when the patient gives us a reason to change it. Otherwise, we have simply traded one rigid doctrine for another—this one with smaller carabiners.

The medical response reflected the same integration. The Line Medic provided early access and initial care, and the REMS medic supplemented that care with analgesia before the patient reached the road. Rescue and medicine were contributing to the same operation, rather than waiting for one discipline to finish before the other could begin.

Casualty management through the interconnected work of access, assessment and stabilization, extraction, and evacuation are all nodes of the rescue nucleus. It places the patient’s condition and the environmental problem together, where they belong.

That is the standard I want us training toward. Not a rope evolution with a medical bag nearby, and not a treatment plan with an unresolved transportation problem. The patient needs the whole thing to work, and deserves it.

Available People Are Part of the Rescue Capability

We talk about organic assets frequently at PRS, but the term should not stop at whatever fits inside a ruck.

On Timber, Fuels Crew personnel were incorporated as haulers while trained rescue personnel handled patient access, packaging, litter management, and technical-system control. An additional REMS team arrived and supplemented technical rescue positions. As the team lead, I actually spent a majority of time instructing these members on how to haul, what the commands were, what to expect, and what to do in case of emergency. I had full confidence in my team to execute their specific tasks, and they did with flying colors.

The useful distinction is not simply that more people showed up. It is that available people were placed into roles that supported the operation while specialized personnel remained focused on work requiring their competence.

That is a basic leadership task, and it deserves as much attention as the hardware.

A capable small team should not confuse being self-sufficient with refusing useful help. Nor should it assume that everyone who volunteers to assist can be handed a technical position. The question is what someone can contribute, what direction they need, and how that contribution fits into the plan. Be a good leader and speak in simple easy to understand terms.

The response also had somewhere to go when the rope work ended. The waiting ambulance and subsequent air-transport plan connected extraction to onward medical transportation. Getting the litter to the road is an important milestone. It should not be the first moment anyone asks what happens next.

Train the Basics Until They Survive a Change of Plan

None of this is an argument against advanced training.

It is an argument for making advanced training earn its name.

A team should understand more than one way to solve a problem. The challenge is knowing which option fits, recognizing when it stops fitting, and changing plans without losing control of the operation.

PACE—Primary, Alternate, Contingency, Emergency—calls for training across a range of available resources rather than practicing only with the preferred equipment present. It also challenges attachment to tools or approaches that no longer serve the problem.

That does not require making the operational plan more elaborate. It requires building enough depth beforehand that a change does not become a crisis inside the crisis.

One of our previous training AARs identified lowering-to-raising transitions as a significant source of hesitation and delay. Participants could often complete the raise efficiently, but the conversion between tasks exposed inconsistencies in sequencing, communication, and decision-making. That was an observation from that training program, not a universal finding about every team—but it gives us something useful to work on.

It also connects directly to the progression we have described through SOAR: build the core skills, add specialized capability, and then test whether those pieces function together during an integrated mission.

My recommendation is to make those transitions deliberate training objectives. Practice the basic system, then change the conditions within a controlled exercise. Change the packaging requirement. Make the preferred piece of equipment unavailable. Require another team to integrate. Carry the scenario through the patient handoff instead of calling it complete when the litter clears the edge.

Then review more than the stopwatch. Where did the team hesitate? What information was missing? Which equipment choice helped? Which step created work without improving control, patient care, or movement?

Being brilliant at the basics is not repeating the same comfortable drill forever. It is developing fundamentals that remain useful when the situation stops cooperating.

Final Thought

I do consider the Timber Fire report as proof that a particular anchor or haul system is the answer to every steep-angle rescue.

It is a reminder of what we should be trying to build: teams that recognize the problem, arrive prepared, integrate with the people already working, treat the patient, select an appropriate system, and adapt when the original plan needs to change.

The value is in how those actions fit together.

At PRS, the goal should never be complexity for its own sake. It should be enough knowledge to recognize the simplest appropriate solution, enough practice to execute it well, and enough humility to notice when it is no longer appropriate.

Advanced capability does not always look advanced. Sometimes it looks like a familiar system, a sensible packaging decision, clear roles, and a patient moving toward the next level of care.

That is brilliance in the basics.

Need help building that capability within your team? Prevail Rescue Solutions provides mission-focused REMS and austere rescue training tailored to your personnel, equipment, and operational environment. Contact us through the website or email Bryan@prevailrescue.com. Specialized Training Solutions