Dive planning & Wetnotes

[xslim]

Hi guys!

Some time ago I did my TecRec Tec 40 course and would like to practice some dive planning and deco dives.
I see a lot of options on what people write in their wet notes.
Usually, it is reversed profile, let's say from 40 m to 0m, with depth when to switch gas, do deco stops, time on a stop and run time.

In Wetnotes I have, there are tables for dive planning, but I have not seen any one using them.
Does any one use those?
Any info / article on how those should be filled?

Picture attached.

 

[kensuf]

I have several sets of custom cut laminated tables which I use. As for that printed template you have there, I only follow the column labeled "RUM TIME" (in between "STOP" and "GAS") when I'm on vacation.

 

[xslim]

I have several sets of custom cut laminated tables which I use. As for that printed template you have there, I only follow the column labeled "RUM TIME" (in between "STOP" and "GAS") when I'm on vacation.

So do you write the plan in reverse comparing to what the dive planning software gives you?

 

[kensuf]

I'm deliberately leaving the depth and gas mixes vague. The inversed lines indicate gas switches.

 

[DevonDiver]

What I put in wetnotes depends on the dive. For Tec40 level dives, it's pretty simple.

D....R....T....T+5...D+5
40..15..15...20....15
12..__...__.... 2.....1
9... ..1...20....2....2
6......3...23....4....4
3......6...29....9.... 7

Where:

D = Depth
T = Stop Time
R = Run Time (cumulative)
D+5 = 5m deeper contingency
T+5 = 5 min longer contingecy

No need for a lost gas (LG) plan with Tec40, as the ascent gas is for conservatism only.

For bigger dives, I'd have contingencies for each lost deco gas and the gas switches would be marked by a horizontal line at the relevant depth/stop.

I'd also have varied bailout/abort ascent plans for longer dives, allowing premature ascent without the full bottom time deco obligation.

I use a fine-tip Sharpie to transcribe into wetnotes... the plan isn't much use if it gets smudged or accidentally erased.

 

[Lorenzoid]

I only follow the column labeled "RUM TIME" (in between "STOP" and "GAS") when I'm on vacation.

Hilarious typo. Then again, Mares is Italian, so who knows.

 

[KenGordon]

What I put in wetnotes depends on the dive. For Tec40 level dives, it's pretty simple.

D....R....T....T+5...D+5
40..15..15...20....15
12..__...__.... 2.....1
9... ..1...20....2....2
6......3...23....4....4
3......6...29....9.... 7

Where:

D = Depth
T = Stop Time
R = Run Time (cumulative)
D+5 = 5m deeper contingency
T+5 = 5 min longer contingecy

No need for a lost gas (LG) plan with Tec40, as the ascent gas is for conservatism only.

For bigger dives, I'd have contingencies for each lost deco gas and the gas switches would be marked by a horizontal line at the relevant depth/stop.

I'd also have varied bailout/abort ascent plans for longer dives, allowing premature ascent without the full bottom time deco obligation.

I use a fine-tip Sharpie to transcribe into wetnotes... the plan isn't much use if it gets smudged or accidentally erased.

Your R and T columns are swapped.

 

[xslim]

What I put in wetnotes depends on the dive. For Tec40 level dives, it's pretty simple.

D....R....T....T+5...D+5
40..15..15...20....15
12..__...__.... 2.....1
9... ..1...20....2....2
6......3...23....4....4
3......6...29....9.... 7

I used pretty similar, with switching to 50% on 21 in my Tec40 course.
40...21...12...9...6...3...


What I'm interested is - a lot of manufacturers are putting those tables in the wet notes, and I have not seen any one using them. And why are they putting the depth in increasing order? 3...6...9...12...21...40 ?

 

[DevonDiver]

Your R and T columns are swapped.

If using tables as the primary means, makes sense to have RT first. Stops are just for when you're off the RT.

If the tables are only a backup for primary computer failure, then stops are likely to be more pertinent... and in the initial column.

I dove tables for over a decade, so I stick with what's familiar to me.

There isn't a standardized protocol on it - so there's no "right or wrong".

 

[KenGordon]

If using tables as the primary means, makes sense to have RT first. Stops are just for when you're off the RT.

If the tables are only a backup for primary computer failure, then stops are likely to be more pertinent... and in the initial column.

I dove tables for over a decade, so I stick with what's familiar to me.

There isn't a standardized protocol on it - so there's no "right or wrong".

No, I mean they are swappped in your example. You say R is the cumulative run time column and T the stop time, but you have the stops under R and the cumulative under T.