Intentional Cutaway, what's your Protrack gonna do?

[whatever 0]

Ok, heres the jump:

exit at 4800 ft, short delay, fly canopy to good spot to get cutaway canopy to land on DZ

cutaway at around 3000ft, take a short delay before deploying second canopy

you wear a Protrack on this jump, what's it gonna do?


I did this jump, I had my 2 Protracks in the left and right pockets inside my Z1 helmet. I will post what they did after I've gotten an idea of what people think their Protracks will do, just so I do not affect anyone's opinion by posting my experience up front.

cya
sam

soon to be gone

[phoenixlpr 0]

I had a cut-away from an almost working canopy. I can check my logs for that.

[mr2mk1g 10]

Quote

cutaway at around 3000ft, take a short delay before deploying second canopy

How longs a "short delay"? It all depends on that. Sometimes my protrack will log a hop and pop and sometimes it wont. It all depends on how long I delay out the door.

It'll work exactly the same on a cutaway - if you've left it long enough to trigger the protrack to think your back in freefall it'll log it as another jump. All it does is sense pressure; it doesn't know or care what's causing the change.

[phoenixlpr 0]

Quote

if you've left it long enough to trigger the protrack to think your back in freefall it'll log it as another jump. All it does is sense pressure; it doesn't know or care what's causing the change.

I don't think so. I had some hop'n'pop and plane was going below warning alitute, I got the warning beep, but only one jump was logged.

[whatever 0]

OK, so here's the answers: - log the second jump only (my one Protrack did this) 21% off the poll chose this so far
- log both deployments as separate jumps (my other Protrack did this) 26 % off the poll chose this so far

the WRONG answer would be: - log the first deployment only (neither Protrack did this) 54 % off the poll chose this so far

(I know they sum up to 101% - which must just be a rounding up error in the polling program)

mr2mk1g - Protrack 1 showed only the 2nd deployment, logging a 10 second delay, Protrack 2 showed both, logging 8 seconds on the first deployment and 10 seconds on the 2nd, with pretty much the same altitudes as Protrack 1 for the 2nd 'exit' and deployment.

I guess one likely explanation is that 8 seconds is close enough to the minimum required 6 seconds for logging the jump, so likely Protrack 1 did not register the exit as quickly, or the deployment as late, as Protrack 2 and did not see the required 'delay' to log the jump.

phoenixlpr - I agree with mr2k1g on this one, also, I have a number of jumps with exits below the first warning on my Protrack and it still logged them as long as I did the required minimum 6 second 'delay'.


interesting instruments, these Protracks, these days I am in the habit of chasing my home DZ's Twin Otter around the turn after I exit in my S3 and the resulting dive has seen me attain descent rates of up to 152mph TAS, before the plane gets too far away and I pull out of the dive, translating forward speed into 'lift' and usually achieving enough deceleration to fool the Protrack into thinking I have deployed a canopy.

Exits normally around 14000ft, Protrack normally logs 'deployment' at 11-17 seconds and around 12500ft.

For all the Neptune fans - I jumped a Neptune for a weekend and fooled that into fake deployments far more frequently than my Protracks....
(it's owner thought it might be in need of a software update)

soon to be gone