While a rigger was performing a reserve repack, they noticed this damage to the reserve ripcord cable.  This damage required replacement of the ripcord before the next jump, because failure would mean the pin could not be extracted from the closing loop, preventing the user from deploying the reserve. The two most common times that a reserve ripcord becomes compromised are after reserve-static-line deployments or during packing. The reserve had not been used since the last repack, and it is unclear when or how this damage occurred.

RSL deployments can cause significant wear due to the cable passing through the RSL’s guide rings with force.  Some manufacturers suggest replacing a ripcord after no more than two RSL activations. This advice is particularly applicable to systems where the RSL ring pulls the ripcord straight up through a guide ring or those that have additional guide rings on the ripcord handle side. If the cable has a noticeable pigtail—a signature spiraling of the end of a ripcord that resembles a pig’s tail—it must be replaced immediately. Main-assisted-reserve-deployment (MARD) devices—a type of RSL—can usually endure multiple RSL activations without affecting the ripcord’s integrity. This makes them a more durable option in terms of ripcord longevity.

Reserve ripcords can also become damaged during packing.  When the rigger closes the last flap, the ripcord may kink (almost unavoidable on some systems). This kinking can weaken the ripcord over time, potentially leading to failure.

Your rigger should be vigilant about reserve-ripcord issues and thoroughly inspect the entire length of the ripcord during the repack, paying particular attention to the swage fittings at both ends. Anytime you or your rigger find any broken strands, the ripcord must be replaced to ensure the rig is in safe, airworthy condition.