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.

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

19.36. NVG Airdrop Procedures. Qualified NVG airdrop pilots are authorized to perform<br />

normal night operations (including low level flying and formation) at night VMC altitudes IAW<br />

the tactical chapters of this regulation and AFTTP 3-3.C-130E/H. Airdrops may be accomplished<br />

on drop zones marked IAW <strong>AFI</strong> 13-217 lighting patterns (covert and overt) while wearing<br />

NVGs. NVG airdrops on unmarked DZ are prohibited unless permitted by contingency SPINs or<br />

coordinated through contingency ATO.<br />

19.36.1. Loadmasters will use NVGs during airdrops if the mission dictates. Loadmasters<br />

are authorized to perform airdrops with minimum lighting. Use NVGs as necessary to assist<br />

with operations and keep cargo area lighting to a minimum.<br />

19.36.2. Cargo Compartment Lighting. After the Combat Entry Checklist, all cargo<br />

compartment lighting will be minimized. Blacked out (no-light) operations in the cargo<br />

compartment are not authorized. Loadmasters will carefully consider cargo compartment<br />

lighting intensity prior to opening ramp and door to minimize interference with formation<br />

wingmen‘s NVG vision.<br />

19.37. Emergency Procedures. Loadmasters will complete a detailed emergency procedure<br />

coordinated task briefing. All crewmembers should review the applicable emergency procedures<br />

for the airdrop to be performed before takeoff. If a malfunction occurs during an airdrop, the<br />

loadmaster immediately notifies the PIC and takes appropriate action. After all appropriate<br />

emergency actions are complete, run the completion of drop checklist. NOTE: In the event of<br />

a malfunction, incident, or off-DZ drop, do not de-rig, handle or move items unless required for<br />

safety of flight. Any follow-on investigation will benefit from seeing the items in the position or<br />

state they were in at the time of the event.<br />

19.38. Emergency Parachutist Bail Out Procedures.<br />

19.38.1. Under satisfactory conditions (static-line exit), the minimum acceptable emergency<br />

bailout altitude is 400 feet above the terrain. When an aircraft emergency occurs during<br />

static-line airdrops, the PIC maintains an acceptable attitude and altitude for the parachutists<br />

to evacuate the aircraft. If the jump must be made at an airspeed in excess of 150 KIAS,<br />

advise the parachutists of the airspeed and altitude. Order evacuation by turning on the green<br />

light and giving the briefed alarm bell signals.<br />

19.38.2. Minimum emergency bail-out altitude for free-fall parachutists is 2,000 feet AGL.<br />

19.38.3. If conditions are unsuitable for aircraft evacuation, turn the red light on until exit<br />

doors are closed. The PIC advises the jumpmaster through the loadmaster to have the<br />

parachutists unhook, take their seats, and fasten seatbelts.<br />

19.39. Towed Parachutist.<br />

19.39.1. The jumpmaster will stop the remaining parachutists; the loadmaster will notify the<br />

PIC; and the PM will turn on the red light. The PF will maintain drop airspeed, at least the<br />

minimum drop altitude (AGL) for the type parachute being used, and avoid flying over or up<br />

wind of water or built up areas.<br />

19.39.1.1. Crews should suspect they have a towed parachutist if static lines are not fully<br />

tucked into the upper corner of the paratroop door or if a D-bag appears to be stuck<br />

outside the door. It is unlikely for a D-bag to become caught on the outside of the aircraft<br />

and is a probable indicator a parachutist is being towed. In any case, crews should follow

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

Saved successfully!

Ooh no, something went wrong!