25.02.2013 Views

AFI 11-2C-130v3 - BITS

AFI 11-2C-130v3 - BITS

AFI 11-2C-130v3 - BITS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>AFI</strong><strong>11</strong>-<strong>2C</strong>-130V3 23 APRIL 2012 243<br />

19.15.4.1.5. JMD releases will not be mixed with any other type of airdrop method,<br />

i.e., GMRS, VIRS, or standard CARP drops. If JMD drop procedures are called for,<br />

the crew will follow the jumpmaster‘s instructions, while adhering to normal safety<br />

concerns. Should the crew believe the drop will occur outside of safe parameters, they<br />

will call ―no drop‖ and ensure the red light is illuminated.<br />

19.15.5. AWADS Airdrops. AWADS-equipped units are authorized to make airdrops using<br />

AWADS equipment in VMC or IMC.<br />

19.15.6. Radar Beacon Airdrops. Radar beacon drops in IMC during peacetime must be<br />

approved by MAJCOM/A3/DO for active duty units and either HQ AFRC/A3 or ANG/A3<br />

for AFRC/ANG units. The AOC/AMD may approve IMC radar beacon airdrops for<br />

exercises or for contingency and combat operations.<br />

19.15.7. I-CDS / JPADS Procedures<br />

19.15.7.1. I-CDS and JPADS airdrop operations are conducted using the JPADS Mission<br />

Support Equipment (MSE) (UHF Dropsonde Receiver Subsystem (UHF-DRS), GPS<br />

Retransmit System (GPS-RTS), Precision Aerial Delivery System Mission Planner<br />

(PADS-MP) laptop and software. I-CDS operations are conventional ballistic CDS<br />

airdrops with non-steerable chutes using the JPADS MSE, PADS-MP, and Dropsondes to<br />

calculate an improved CARP. JPADS operations are conducted using steerable chutes<br />

with Autonomous Guidance Units (AGUs).<br />

19.15.7.2. Airdrop Damage Estimate (ADE): Units must perform a full airdrop damage<br />

assessment prior to CDS/I-CDS/JPADS airdrops. The ADE must be coordinated and<br />

approved by the area controlling agency. Coordinate with the owning agency of the<br />

restricted airspace or controlled airspace and landowners with property surrounding the<br />

DZ for all CDS/I-CDS/JPADS operations. Examine the area in the vicinity of the DZ for<br />

potential damage or hazards in the course of normal operations or during extraordinary<br />

system failure events. If the ADE demonstrates potential damage or hazards restrict the<br />

airdrop release Launch Acceptability Region (LAR); lower the drop altitude, change the<br />

run-in, change parachute type or cancel airdrop operations. Inform the controlling unit of<br />

the risk to their operations; the controlling unit, and the JFC designated agency are<br />

approving authorities for risk to the area surrounding the DZ. Intelligence personnel are<br />

responsible for providing the JFC-designated agency close-up and overview imagery to<br />

facilitate ADE. For actual JPADS training airdrops, units will contact AMC/A3DT (2-3<br />

weeks prior) in order to ensure all planning, coordination and reviews/assessments have<br />

been accomplished. Operations conducted at Yuma Proving Ground under JPADS<br />

related test plans do not need AMC/A3DT review. See <strong>AFI</strong> 13-217 for further<br />

information. The ADE must include, at a minimum, a review of the airspace and ground<br />

space with respect to: CARP and LAR location, 63% 1-sigma I-CDS success ellipse,<br />

Chute failure footprint and Guidance failure footprint.<br />

19.15.7.3. The PO or mission planner is required to provide JPADS-MP derived<br />

CARP(s) for each airdrop pass and a completed ADE prior to airdrop mission execution.<br />

Both pilots will review preflight CARP(s) and ADE for each respective airdrop. During<br />

the cargo door Dropsonde release, use of zero flaps at speeds between 170 – 180 KIAS is<br />

required to preclude Dropsonde tail strikes. Loadmasters will open the cargo door for the<br />

Dropsonde airdrops. Loadmasters will release the Dropsondes from the corner of the

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!