25.12.2012 Views

BY ORDER OF THE COMMANDER 305TH AIR MOBILITY WING ...

BY ORDER OF THE COMMANDER 305TH AIR MOBILITY WING ...

BY ORDER OF THE COMMANDER 305TH AIR MOBILITY WING ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

4 AFI11-2C-17V3_305AMWSUP 28 JANUARY 2011<br />

leadership, crews should report via deployed channels. When in doubt, always keep home<br />

station leadership informed.<br />

3.10.6.1. (Added) Include Flying Crew Chiefs (FCCs) in the work-rest plan and allow them to<br />

use in-flight crew rest facilities when necessary. During aircraft debrief, the PIC will coordinate<br />

with the FCC and maintenance supervision on how long the FCC can safely work. This is<br />

especially important for augmented duty days or crew-staged operations. Rest periods may only<br />

be interrupted for necessary questions concerning the airplane maintenance history.<br />

4.4. (Added) During non-duty hours, contact standby OGV personnel through 87 ABW/CP.<br />

When beyond command and control capability, the Aircraft Commander (AC) retains ultimate<br />

authority and responsibility. In these cases, contact OGV as soon as practical after the flight.<br />

McGuire crews should request technical support and additional assistance from home unit or the<br />

appropriate A3 or A4 agency. Work Higher Headquarters (HHQ) assistance requests through the<br />

Tanker/Airlift Control Center (TACC) to the maximum extent possible.<br />

5.4.5. (Added) Landings in the Area of Responsibility (AOR) (305 AMW only). In a combat<br />

zone, First Pilots (FPs) will not land on runways less than 120’ wide. EXCEPTION: FPs may<br />

land on runways less than 120’ wide provided that they are accomplishing Aircraft Commander<br />

upgrade/certification and under the direct supervision of an Instructor Pilot (IP)/Examiner Pilot<br />

(EP).<br />

5.15.3.1.2. (Added) Assault Landing Zone (ALZ) landings may be accomplished with one or<br />

more thrust reversers pinned or brakes capped provided the Mission Computer (MC) Takeoff<br />

and Landing Data (TOLD) provide adequate ground roll distance. Pilots will ensure the MC<br />

non-standard TOLD pages reflect the proper aircraft configuration.<br />

5.15.3.3.1. (Added) Mission Planning. Before departure, ensure the aircraft is prepared for<br />

Semi-Prepared Runway Operations (SPRO) by maintenance personnel. Ensure turn-around<br />

areas at the assigned airfield are adequately marked to allow the aircrew to easily identify<br />

useable surfaces.<br />

5.15.3.3.2. (Added) Takeoff. For cement-capped runways, use a Runway Friction Factor (RFF)<br />

of two (2) for takeoff data calculations. For other than cement-capped, use the reported RFF<br />

from the special tactics team. Selecting “EOCS-YES” on the non-standard TOLD page may be<br />

required to correct VMCG problems.<br />

5.15.3.3.3. (Added) Taxi. Use differential braking with caution. Loadmaster will monitor the<br />

landing gear on the inside of the turn through an open paratroop door and notify the pilot if the<br />

wheels become locked or begin plowing the soil.<br />

5.15.3.3.4. (Added) Aircraft Backing. Only use backing when necessary for mission<br />

accomplishment. The loadmaster may be positioned in the paratroop door when backing the<br />

aircraft on dirt surfaces (use of the cargo door and ramp may allow dust into the cargo area<br />

setting off the smoke alarms). During dusty conditions, the loadmaster should wear eye<br />

protection to protect from blowing debris. Avoid backing up on sloping terrain if possible. Plan<br />

ground operations to avoid star turns. Expect significant surface damage if star turns are<br />

performed.<br />

5.15.3.3.5. (Added) Engine Running On/Offload (ERO). If reverse idle causes vortex<br />

ingestion, terminate ERO procedures and position the throttles to forward idle after all ground

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

Saved successfully!

Ooh no, something went wrong!