0
petetheladd

Amending the pull priority list

Recommended Posts

We have all heard the "in order of priority" list of

1) pull
2) pull at the correct altitude
3) pull at the correct altitude with stability

However should'nt this have a forth variable i.e. speed added and the list amended to look maybe like -

1) pull
2) pull at the correct altitude
3) pull at the correct altitude after slowing to the correct speed
4) pull at the correct altitude with stability after slowing to the correct speed

or maybe get rid of 3) above and replace it with 4) as we tend to like lists of 3 items apiece

Let the debate begin ......

PTL

No, Not without incident

Share this post


Link to post
Share on other sites
If you're going to do that it would have to be:

1. Slow down to the correct speed
2. Pull
etc.

Slowing down has to come before the rest if damage is to be avoided. But that seems like a bad thing to put second; I would amend it to "do not exceed the rated limits of your gear" and then keep the pull stuff in its original order.

Share this post


Link to post
Share on other sites
They make sense as they are.
My take on them

1) pull --do this no matter what
2) pull at the correct altitude- do this no matter what-i.e enough altitude for the parachute open no matter what
3) pull at the correct altitude with stability-- if we are doing things right then this is what we do every jump. and if you are pulling with stabillity at the right altitude speed shouldn't be an issue.

If speed is an issue see 1 and 2.-- Speed doesn't matter if you skipped 3 and are stuck with 2. if it is to late for 2 you better just start pulling everything and pray;)

MAKE EVERY DAY COUNT
Life is Short and we never know how long we are going to have. We must live life to the fullest EVERY DAY. Everything we do should have a greater purpose.

Share this post


Link to post
Share on other sites
Quote

We have all heard the "in order of priority" list of

1) pull
2) pull at the correct altitude
3) pull at the correct altitude with stability

However should'nt this have a forth variable i.e. speed added and the list amended to look maybe like -

1) pull
2) pull at the correct altitude
3) pull at the correct altitude after slowing to the correct speed
4) pull at the correct altitude with stability after slowing to the correct speed

or maybe get rid of 3) above and replace it with 4) as we tend to like lists of 3 items apiece



I think your proposition implicitly indicates an incorrect interpretation of the priority list.

The list of
1) pull
2) pull at the correct altitude
3) pull at the correct altitude with stability

is not a list of what you do in order on a jump from the start of a jump to its conclusion.

It is a list of the bare minimum actions to do before you land, crash or hit the ground at a high rate of speed. It is not a priority task list of things to do in such-n-such order from exit to landing. It is a priority list of what you must do before landing.

Think of it this way:
Regular RW type jump:
1. exit ac
2. go to 2nd point (or grip switch to first point)
3. go to next point
4. go to next point
5. repeat from top of page
6. break-off
7. track to assigned pull altitude
8. wave-off
9. pull
10. check for good canopy
11. determine landing point
12. set up for landing pattern with traffic clearance
13. fly in for final and flare
14. land safely, PLF if necessary

OTOH the priority list of:
1) pull
2) pull at the correct altitude
3) pull at the correct altitude with stability

kicks in when

1. you find yourself doing 4-way below 2K and immediately pull
2. you are a student tumbling thru the sky at 2900 ft and immediately pull
3. you are any jumper caught up with a distraction with the main deployment, realize it's 1500 ft and pull your reserve, no matter what body position you are in or fall rate you have
4. you are doing a solo FF jump and your dirt alert flat lines, you pull immediately
5. etc

IOW, the priority list of
1) pull
2) pull at the correct altitude
3) pull at the correct altitude with stability
is an emergency procedure, not a dive flow of a normal jump. All of us non-CRW jumpers, jump out and freefall for awhile. We don't immediately pull.

Jumps that go according to plan have jumpers seeking adequate separation distance from others, slowing down, waving off etc. It is only when jumpers screw up that we need this priority list to shoot thru our brains to get us to act and save ourselves.

Jumps are 'You are dead until you save yourself. For the first 45-70 seconds, we have fun turning points. Then we decide to save ourselves.'

The other comment is to get gear that operates properly if you do the higher speed type jumps. aka - do not overload mains, reserves or harnesses.
.
.
Make It Happen
Parachute History
DiveMaker

Share this post


Link to post
Share on other sites
Quote

If you're going to do that it would have to be:

1. Slow down to the correct speed
2. Pull
etc.

Slowing down has to come before the rest if damage is to be avoided. But that seems like a bad thing to put second; I would amend it to "do not exceed the rated limits of your gear" and then keep the pull stuff in its original order.


Pulling has to be done if death is to be avoided. A head down pull has better survival chances than a nopull so pull has to be top priority.

Share this post


Link to post
Share on other sites
>Pulling has to be done if death is to be avoided. A head down pull
>has better survival chances than a nopull so pull has to be top priority.

I agree, but like I said, if you want to stick to that you shouldn't exceed the limits of your gear. It's a decision you have to make _before_ the jump; what you decide on the ground or in the plane has a lot to do with the options you keep when you're at 700 feet in freefall. It's like asking "But what if I have a malfunction on my main, and I'm jumping a reserve I can't land in these winds?" A better place to deal with such a problem is before you get on the plane, by making sure you _do_ have a reserve you can land under all conditions.

Share this post


Link to post
Share on other sites
Quote

I think your proposition implicitly indicates an incorrect interpretation of the priority list.

The list of
1) pull
2) pull at the correct altitude
3) pull at the correct altitude with stability

is not a list of what you do in order on a jump from the start of a jump to its conclusion.

It is a list of the bare minimum actions to do before you land, crash or hit the ground at a high rate of speed. It is not a priority task list of things to do in such-n-such order from exit to landing. It is a priority list of what you must do before landing.



I think this list is something that is pushed to the fore front of the minds of both students and low time jumpers by the more experienced/instructor crowd.

The idea being these jumpers are more likely to need a definitive plan up front[due to lack of experience] if things start going wrong.

Additionally, I believe more experienced skydivers implicitly try to keep this in the back of their minds because when the poop goes down and we are maybe innovating someway to fix a situation[ maybe under high stress ] we have something relativly simple to reference back on [ similar to something like the hard deck concept ].

The list was something that goes way back.
I'm just pondering the value of updating this list as skydiving has evolved so very far from when this list was initially concieved.

PTL

P.S. Pull will always be numero uno, without the pull, your number is almost always, as a certainty, up

No, Not without incident

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

0