25.02.2013 Views

AFI 11-2C-130v3 - BITS

AFI 11-2C-130v3 - BITS

AFI 11-2C-130v3 - BITS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

higher altitude is required by DOD FLIP AP/1B, Area Planning North and South<br />

America.<br />

16.4.1.7. Emergency Safe Altitude (ESA). ESA is designed to provide positive IMC<br />

terrain clearance during emergency situations that require leaving the low level structure.<br />

Several ESAs may be computed for route segments transiting significant terrain<br />

differentials or a single ESA may be computed for the entire low level route. To compute<br />

ESA, add 1,000 feet (2,000 feet in mountainous terrain) to the elevation of the highest<br />

obstruction to flight within 22 NMs of planned route centerline. An ESA will be<br />

computed for the route and conspicuously annotated on the chart. NOTE: Climbing to<br />

ESA may put the aircraft or formation in a controlled (i.e., IFR) altitude structure<br />

requiring coordination with Air Traffic Control agencies. NOTE: Pressure altimeters<br />

are calibrated to indicate true altitudes under International Standard Atmospheric (ISA)<br />

conditions. Any deviation from these standard conditions will result in erroneous<br />

readings on the altimeter. This error becomes important when considering obstacle<br />

clearances in temperatures lower than standard since the aircraft‘s altitude is below the<br />

figure indicated by the altimeter. Refer to the flight information handbook to determine<br />

correction.<br />

16.4.1.8. When routes are flown at temperatures of 0 degrees Celsius or less, apply cold<br />

weather temperature corrections to Night VMC Enroute, NVG Enroute, Minimum Safe,<br />

and Emergency Safe Altitudes IAW FIH Section D procedures.<br />

16.4.2. Airdrops will not be conducted below the following altitudes: WARNING: DZ<br />

surveys do not assure terrain and obstruction clearance. Planners and aircrews are responsible<br />

for ensuring clearance through mission planning/chart preparation. NOTE: In combat or<br />

contingency operations the supported unit commander may direct drops below the <strong>AFI</strong> <strong>11</strong>-<br />

231, Computed Air Release Point Procedures, altitudes.<br />

16.4.2.1. Day VMC Drop Altitude. Fly minimum day VMC airdrop altitudes as specified<br />

in <strong>AFI</strong> <strong>11</strong>-231, visually avoiding high terrain and obstacles in the vicinity of the drop<br />

zone.<br />

16.4.2.2. Night VMC Drop Altitude. If not on NVGs, fly minimum night VMC run-in<br />

altitudes through slowdown, at an indicated altitude of 500-feet above the highest<br />

obstruction to flight (man-made obstacle, terrain feature, or spot elevation), or 400-feet<br />

plus one contour interval above the highest depicted terrain contour, whichever is higher,<br />

within 3 NM of run-in centerline. If on NVGs, fly NVG enroute altitudes through<br />

slowdown. In both instances (with/without NVGs), after slowdown, when the drop zone<br />

is in sight and will remain in sight, or when a positive position is identified and adequate<br />

terrain clearance is assured, the aircraft may descend from run-in altitude to drop altitude<br />

specified in <strong>AFI</strong> <strong>11</strong>-231, AMT, SPINS, or mission planning sheet.<br />

16.4.2.3. IMC Drop Altitude. Fly minimum IMC drop altitudes at 500 feet above the<br />

highest obstruction to flight (man-made obstruction, terrain feature, or spot elevation), or<br />

400 feet plus one contour interval above the highest depicted terrain contour, whichever<br />

is highest, within 3 nautical miles either side of the run-in centerline from DZ entry point<br />

to DZ exit point or as specified in <strong>AFI</strong> <strong>11</strong>-231, whichever is higher.

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

Saved successfully!

Ooh no, something went wrong!