Kendall Raine
Contributor
This whole discussion brings up the concept of different diving models. On the one hand there is the team concept. At the other extreme is the pick-up model. In the middle is how most LoBs operate.
In team diving the boat is part of the team and everyone is on the same song sheet. The dive plan is developed with this in mind and everyone plays their part-captain, crew, bottom divers/teams and support divers (if any). The plan considers surface conditions and possible sea state changes over the course of the dive, boat traffic, current, team dive plans as well as contingencies (e.g. getting blown off). The higher the complexity of the dive, the closer the tolerances need to be. The plan considers proximity/pre-notification of USCG/SAR assets, proximity to chamber resources, etc. Contingencies aren't left entirely to the boat captain to think through and manage (or not), they are developed with the dive team and known/embraced by everyone involved. Obviously this system works best in smaller groups of competent/dedicated divers committed to and knowledgeable of team concept discipline/procedures and willing to put in the time and money to achieve it. This is how a lot of expedition diving is done-necessitated by the added complexities of those types of dives. I think this is what Nick was getting at, but it is much more involved than simply whether the boat is operating live or static. Besides, there are times when planned live boating/drifting deco is problematic (e.g. shipping lanes). Adjusting the protocol for site conditions (up to and including not doing the dive at all) is inherent in the team concept.
This unified team concept is foreign/contradictory to pick-up dives off open (aka "cattle") boats-the way a lot of diving is done in Florida/California/New York/New Jersey. In that scenario captains typically regard themselves as transportation. They often don't know the divers, their dive plans, capabilities or contingency plans and, frankly, don't ask. Achieving true team execution among a group of pick up divers for a day/open boat is structurally not workable. I don't see it as prima facie evidence of a captain's laziness/incompetence per se (like not having a night watch), but a symptom of a business model driven by volume, speed and price. Site selection is probably influenced by the composition of the divers (classes/hunters/novices/experienced (whatever that means)), but that's about it. Low incident rates are more a function of the low impact/simplicity of the diving rather than any planning worthy of the name. Divers are expected to conform to the boat's procedures, however loosely thought through and articulated those might be. Maybe there is a chase boat (RIB)/underwater recall systems, tag lines, etc.-often times not. But the notion of a unified team operation is unknown/anathema. Divers typically dive in buddy teams (maybe?) with little to no regard/consciousness of what other dive teams are doing. Divers have been taught this is the way diving is done and think that's the end of the story. It doesn't need to be that way. Unfortunately, it also means divers need to take responsibility themselves (including skill development) to organize their diving and work through contingencies (blow off, lost buddy, aborted dives, etc)-something for which they are generally un/under prepared (inherent in high velocity low price/content instruction). The idea that a diver blown off a wreck by current needs "rescue" (the OP's scenario) versus "retrieval" is admission of utter failure of even the most basic form of self-sufficiency/dive planning top to bottom. In a static (non-live boat) boat scenario, a blow off/drifting ascent should be assumed and planned for (e.g. chase boat, DSMBs, etc), not dismissed by a captain's admonition to "come up the anchor line or else." If it can't be factored into the plan (at least as a contingency to the plan) then the dive shouldn't happen. Just common sense.
LoBs deal with this reality by using guides/small dive groups/live boat(s) operating from motherships. This is not team diving, but rather a band aid stuck on a pick up dive model.
In team diving the boat is part of the team and everyone is on the same song sheet. The dive plan is developed with this in mind and everyone plays their part-captain, crew, bottom divers/teams and support divers (if any). The plan considers surface conditions and possible sea state changes over the course of the dive, boat traffic, current, team dive plans as well as contingencies (e.g. getting blown off). The higher the complexity of the dive, the closer the tolerances need to be. The plan considers proximity/pre-notification of USCG/SAR assets, proximity to chamber resources, etc. Contingencies aren't left entirely to the boat captain to think through and manage (or not), they are developed with the dive team and known/embraced by everyone involved. Obviously this system works best in smaller groups of competent/dedicated divers committed to and knowledgeable of team concept discipline/procedures and willing to put in the time and money to achieve it. This is how a lot of expedition diving is done-necessitated by the added complexities of those types of dives. I think this is what Nick was getting at, but it is much more involved than simply whether the boat is operating live or static. Besides, there are times when planned live boating/drifting deco is problematic (e.g. shipping lanes). Adjusting the protocol for site conditions (up to and including not doing the dive at all) is inherent in the team concept.
This unified team concept is foreign/contradictory to pick-up dives off open (aka "cattle") boats-the way a lot of diving is done in Florida/California/New York/New Jersey. In that scenario captains typically regard themselves as transportation. They often don't know the divers, their dive plans, capabilities or contingency plans and, frankly, don't ask. Achieving true team execution among a group of pick up divers for a day/open boat is structurally not workable. I don't see it as prima facie evidence of a captain's laziness/incompetence per se (like not having a night watch), but a symptom of a business model driven by volume, speed and price. Site selection is probably influenced by the composition of the divers (classes/hunters/novices/experienced (whatever that means)), but that's about it. Low incident rates are more a function of the low impact/simplicity of the diving rather than any planning worthy of the name. Divers are expected to conform to the boat's procedures, however loosely thought through and articulated those might be. Maybe there is a chase boat (RIB)/underwater recall systems, tag lines, etc.-often times not. But the notion of a unified team operation is unknown/anathema. Divers typically dive in buddy teams (maybe?) with little to no regard/consciousness of what other dive teams are doing. Divers have been taught this is the way diving is done and think that's the end of the story. It doesn't need to be that way. Unfortunately, it also means divers need to take responsibility themselves (including skill development) to organize their diving and work through contingencies (blow off, lost buddy, aborted dives, etc)-something for which they are generally un/under prepared (inherent in high velocity low price/content instruction). The idea that a diver blown off a wreck by current needs "rescue" (the OP's scenario) versus "retrieval" is admission of utter failure of even the most basic form of self-sufficiency/dive planning top to bottom. In a static (non-live boat) boat scenario, a blow off/drifting ascent should be assumed and planned for (e.g. chase boat, DSMBs, etc), not dismissed by a captain's admonition to "come up the anchor line or else." If it can't be factored into the plan (at least as a contingency to the plan) then the dive shouldn't happen. Just common sense.
LoBs deal with this reality by using guides/small dive groups/live boat(s) operating from motherships. This is not team diving, but rather a band aid stuck on a pick up dive model.