Skillnader mellan sidorna "AH-64D Procedures" och "Quickstart Checklists"

Från Master Arms Wiki
(Skillnad mellan sidor)
Hoppa till navigering Hoppa till sök
 
 
Rad 1: Rad 1:
The following sections describe Tactics, Techniques and Procedures (TTP) that are valid only for AH-64D.
+
The purpose of "Quickstart Checklists" is to make it easier for new members to carry out a startup in a new model.  Be sure to check out [https://wiki.masterarms.se/index.php/Aircraft_Procedures TTP] for repective module and MA [https://wiki.masterarms.se/index.php/Home#Standard_Operating_Procedures SOP] for mandatory steps during startup. In addition, these checklists show only one of many different ways to carry out a startup and there is room to change the order of certain points to suit the pilot's own preferences.
<pre style="color: red">Some Tactics and Techniques have reference to the manual "AH-64D Quick Start Manual EN", this manual can be found in the DCS installation folder "DCS World OpenBeta\Mods\aircraft\AH-64D\Doc"</pre>
 
  
==Considerations==
+
==A-10C==
 +
The "System Startup Checklist" aims to be easily memorized by walking around the cockpit from left to right.</br>
 +
When performing a "Full startup" (Ordered by FL or when you fly single-ship) the steps in "Engine startup" are preferably carried out simultaneously as the "System Startup". Eg start left engine then go throug the steps in system startup. When left engine is running, start right engine and continue with system startup.
  
RW attack assets provide the ability to maneuver and reposition firepower in response to changing situations. They carry a wide variety of forward firing munitions, are equipped with advanced sensors, have excellent response and loiter times, can conduct low altitude or nap of the earth ingress, attacks, and egress, and have an excellent capability to conduct CAS in diverse terrain and when accompanying other transport or rescue assets.
+
<gallery>
 +
File:A-10C STARTUP 1.png|''Startup Procedure''
 +
File:A-10C STARTUP 2.png|''System Startup''
 +
File:A-10C STARTUP 3.png|''Engine Startup''
 +
</gallery>
  
Consider combining FW and RW platform capabilities in an urban environment. FW can often target/designate within urban areas more easily due to the ability to loiter high above many threat envelopes. Once the FW aircraft has identified and confirmed the target it can designate the target with a LASER to guide precise, low-yield PGMs fired from a RW attack asset holding in a relatively safe BP.
+
==AH-64D==
 +
Steps 1-7 in "Startup Procedure" are carried out jointly between the Pilot and CPG (and within the whole flight if not flying single-ship).
 +
"System Startup" can mostly be performed in any order as mentioned above.
  
===Operating Altitudes===  
+
===Pilot===
  
The following are altitude ranges for RW aircraft:
+
<gallery>
*High - Above 3,000 ft. AGL.
+
File:AH-64D STARTUP 1.png|''Startup Procedure''
*Medium - 500 to 3,000 ft. AGL.
+
File:AH-64D STARTUP 2.png|''System Startup''
*Low - Below 500 ft. AGL.
+
</gallery>
  
===Threat===  
+
===CPG===
  
In an environment where small arms and RPGs are the predominant threat, attack helicopter aircrews will normally elevate in order to stay out of the effective range of the weapons systems, usually operating at medium altitude. Specific altitudes selected will depend on the mission en route.  
+
<gallery>
For example, if the mission en route is to conduct visual reconnaissance, the helicopters will select the lowest altitude that will allow them to effectively use their sensors while avoiding the heart of the small-arms threat envelope.  
+
File:AH-64D STARTUP 1.png|''Startup Procedure''
 +
File:AH-64D STARTUP 3.png|''System Startup''
 +
</gallery>
  
When transiting urban areas attack helicopters may elect to transit at roof top level to minimize exposure time. In general, attack helicopters will avoid urban areas unless they are conducting an attack.
+
==F-14B==
  
===Day versus Night===
+
===Pilot===
  
Altitudes will normally vary for the same area of operations from day to nighttime, and will depend heavily on threat, weather, and terrain. In open desert, helicopters will normally decrease their altitude as lighting conditions decay in order to maintain visual reference with the ground.
+
<gallery>
Over urban areas, attack helicopters can often operate more safely than during the daytime but will elevate high enough to avoid being belly-lit by cultural lighting, usually operating in the 1,500-3,000 ft. AGL block .
+
</gallery>
  
 +
===RIO===
  
==Capabilities==
+
<gallery>
 +
</gallery>
  
RW-assets conducts AGO (Air-Ground Operations) as the aerial maneuver force of the combined arms team, or as an independent maneuver force in support of ground forces conducting offensive, defensive or stability operations. Regardless of the type of mission performed by the ground force, most aviation operations are offensive in nature and designed to provide an asymmetric advantage. Aviation operations are most effective when assets are task organized to correctly support the higher headquarters mission.
+
==F-16C==
  
These operations are executed through the following tactical, enabling, and sustaining tasks:
+
==F/A-18C==
  
*Reconnaissance
+
==AJS 37==
*Security
 
*Movement to contact
 
*Attack
 
 
 
 
 
==Tactics and Techniques==
 
 
 
===Tasks===
 
'''WIP'''
 
 
 
*Reconnaissance
 
**Zone
 
**Area
 
**Route
 
**Reconnaissance in force
 
*Security
 
**Screen
 
**Guard
 
*Movement to contact
 
*Attack
 
**Continous
 
**Phased
 
**Max Destruction
 
 
 
 
 
===En Route===
 
 
 
Ideally, en route tactics (route, altitude, airspeed selection, terrain flight profile, and formations) allow attack helicopter aircrews to avoid concentrations of enemy air defenses, prevent early acquisition, avoid detection or allow the attack helicopters to remain outside of the effective range of certain threat systems.
 
 
 
====Navigation Tactics====
 
 
 
DCS AH-64D Quick Start Manual EN page 313-314 (Terrain Flight Modes)
 
 
 
====Tactical Formations====
 
 
 
Cruise principles utilizing radius of turn and altitude to maintain or regain position apply to these formations. Separation between aircraft is dependent on the threat.
 
 
 
<u>Combat Spread:</u>
 
 
 
DCS AH-64D Quick Start Manual EN page 311-313 (Combat Spread)
 
 
 
 
 
<u>Combat Cruise:</u> '''(Default if not specified)'''
 
 
 
DCS AH-64D Quick Start Manual EN page 311-313 (Combat Cruise)
 
 
 
 
 
If there is a need for increased control, Lead can choose to use one of the following formations:
 
*Trail
 
*Column
 
*Echelon
 
 
 
<u>Trail: </u>
 
 
 
Everyone moving in the same track usually with lead in front. Used in narrow terrain and during NOE.
 
 
 
:+ Allows high speed, easy management and good observation to the sides.
 
 
 
:- Limited observation and fire power to the front.
 
 
 
<u>Column:</u>
 
 
 
Like Trail but every other pilot flies offset to the right by 45° from the pilot infront of them.
 
(2nd pilot 45° to the right behind lead, 4th pilot 45° to the right behind 3rd and trailing the 2nd)
 
Used during Traveling
 
 
 
:+ Allows high speed, easy management and good observation to the sides.
 
:+ Allows greater opportunity for observation going forward and twice the fire power compared to Trail.
 
 
 
:- Still limited observation and fire power to the front.
 
:- Somewhat more demanding for the pilot to keep formation
 
 
 
<u>Echelon:</u>
 
 
 
Like Trail but every pilot is offset to the right/left (all to the same side) by 45°.
 
 
 
:+ Allows equal observation/fire power to the front and sides.
 
:+ Allows opportunity for easy transition into Combat Spread.
 
 
 
:- Somewhat more demanding for the pilot to keep formation, especially through turns.
 
 
 
===Ingress===
 
 
 
Ingress tactics apply from arrival at the release point or HA until the target attack
 
phase begins at the BP.
 
 
 
Aircrews select HAs and BPs that are tactically sound, support the scheme of maneuver, and are coordinated with other supporting arms.
 
 
 
====Control====
 
 
 
<u>Holding Areas: </u>
 
 
 
HAs may be established throughout the battlefield to be used by helicopters awaiting targets or missions. These HAs serves as informal ACAs while they are in use. HAs provide the attack helicopter aircrews an area in which to loiter. HAs may be established during
 
planning, referred to by name or number, and activated/established during operations.
 
 
 
<u>Battle Positions:</u>
 
 
 
BPs are maneuver maneuvering areas containing firing points (FPs) for attack helicopters. Like HAs, BPs serve as informal ACAs while in use. Planning considerations and methods of
 
establishment for BPs are the same as those involved in the use of HAs.
 
 
 
====Techniques of Movement====
 
 
 
Due to proximity to the threat, aircrews use TERF to move during ingress to the BP. If aircrews are close to friendly artillery and mortars, they use TERF in conjunction with ACMs to deconflict with artillery and mortar trajectories. Particularly when conducting terrain flight, helicopter movement must be coordinated with the applicable FC/JFSEC.
 
 
 
Aircrews use three techniques of movement:
 
 
 
* Traveling
 
* Traveling overwatch
 
* Bounding overwatch
 
 
 
<u>Traveling:</u>
 
 
 
Traveling is a technique that aircrews use when enemy contact is remote. The flight moves at a constant speed using low-level or contour terrain flight. Movement should be as constant as the terrain allows. Traveling allows rapid movement in relatively secure areas.
 
 
 
<u>Traveling Overwatch:</u>
 
 
 
Traveling overwatch is a technique that aircrews use when enemy contact is possible. The flight moves using contour or NOE terrain flight. While caution is justified, speed is desirable. The flight consists of two major elements: the main element and the overwatch element. The overwatch element may contain multiple sub elements. The main element maintains continuous forward movement. The overwatch elements move to provide visual and weapons coverage of the main element. The overwatch elements provide weapons coverage
 
of terrain from which the enemy might fire on the main element.
 
 
 
<u>Bounding Overwatch:</u>
 
 
 
Bounding overwatch is a technique that aircrews use when enemy contact is imminent. The flight moves using NOE terrain flight. Movement is deliberate and speed is not essential. The
 
flight consists of two elements. One element moves or “bounds” while the other element takes up an overwatch position. The overwatch element covers the bounding elements from covered, concealed positions that offer observation and fields of fire.
 
 
 
 
 
===Attack (Within the BP)===
 
 
 
====Control====
 
 
 
Once the aircrew reaches the BP, the JTAC/FAC(A) or mission
 
commander issues final instructions to the flight. Aircrews select individual FPs
 
and remain masked while awaiting the TOT/TTT or the order to attack.
 
 
 
====Techniques of Attack====
 
 
 
Specific techniques used to attack a target are the choice
 
of the air mission commander. Choose attack tactics considering the threat,
 
target size and vulnerability, weather, terrain, accuracy requirements, weapons
 
effectiveness, and fragmentation patterns.
 
 
 
DCS AH-64D Quick Start Manual EN page 315 (Weapon Delivery Techniques)
 
 
 
===Disengagement and Egress===
 
 
 
Following actions on the objective area or when the attack helicopters’ time on station is complete, the flight will conduct a check out and egress via planned or assigned routing. Tactical considerations for the egress and return to force in terms of airspeed, altitude, formation, and TTP are the same as for the inbound en route phase. RW attack assets may use a forward arming and refueling point (FARP) to refuel and rearm, extending their ability to provide support to the troops on the ground. When complete with the mission, the attack helicopter aircrew will make every attempt to provide BDA and a mission report (MISREP) via the ALO’s C2 system. The connectivity plan for the low altitude block will enhance the flow of information from attack helicopters to decision makers allowing for timely decisions regarding follow on sorties and support required, as well as vital information flow on the enemy and friendly force situations.
 
 
 
==Procedures==
 
The procedures described here aim to ensure a common view of the workflow during assignments in order to facilitate the change of staff. Pilot and CPG knows who do what and when even if it’s the first time flying together.
 
 
 
The order in which the steps not numbered are performed can be changed as needed.
 
 
 
===Standard Conventional Loadout===
 
 
 
* SCL 1
 
:- 300xM789 HEDP, 8xAGM-114K, 2xM261 (M229)
 
* SCL 2
 
:- 1200xM789 HEDP, 4xAGM-114K, 2xM261 (M229)
 
* SCL 3
 
:- 1200xM789 HEDP, 12xAGM-114K
 
 
 
 
 
===Airfield===
 
 
 
====Startup====
 
 
 
<u>Pilot:</u>
 
# Connect ground power (MSTR IGN – EXT PWR) or start up the APU
 
# Rearm as briefed
 
# Listen to ATIS and take notes. (Wait for CPG to enter Freq.)
 
# FL perform radiocheck on Intra-Flight (Wait for CPG to enter Freq)
 
# Engine Startup (After CPG has received clearance from Ground)
 
:* CMWS Setup
 
:* Set transponder (SRS Overlay)
 
:* Exterior Lights
 
:**Nav -> BRT and ANTI-COL -> WHT (Day) / RED (Night)
 
:* MENU-Page
 
:**ASE
 
:::- RLWR - ON
 
::* FLT
 
:::- QNH
 
::* FUEL
 
:::- Auxiliary tanks transfer setup
 
::* PERF (WIP)
 
:::- Enter current value for PA, FAT and GWT 
 
:* WPN-Page
 
:::- Boresight IHADSS
 
:::- Set Manual Range (GUN) as desired
 
:* Personal preferred settings
 
::- Phase/Threat Show
 
::- MAP
 
::- BAM
 
::- HI/LO Altitude Warnings 
 
 
 
<u>CPG:</u>
 
<ol start="2">
 
<li>Enter frequency for ATIS</li>
 
<li>Enter Intra-Flight </li>
 
<li>Enter frequency for Ground/Tower
 
<li>Request startup clearance if needed '''(Only FL CPG)'''</li></ol>
 
:* COM-Page
 
::- Enter freq. or select presets as briefed incl. “swap” if two freq’s are to be used on same radio.
 
:* WPN-Page
 
::- Boresight IHADSS
 
::- LRFD/LST Channel (LRFD = own, LST = A if not briefed)
 
::- Set frequencies on channel A-D as briefed (A=FL, B-D= wingman 2-4)
 
::- Set Manual Range (GUN) as desired
 
::- Laser - ARM
 
:* TSD-Page
 
::- Create/Edit Points and Route as briefed
 
::- Set up Battle Areas as briefed
 
:::- PFZ
 
:::- NFZ
 
:* Personal preferred settings
 
::- Phase/Threat Show
 
::- MAP
 
::- BAM
 
::- Etc.
 
 
 
====Taxi / Takeoff====
 
 
 
<u>Pilot:</u>
 
<ol start="2"><li> Taxi (If taxiing is needed this is done on the ground)</li></ol>
 
<ol start="4"><li> Hover power check</li>
 
<ol style="list-style-type:lower-alpha">
 
<li>HOVER Q INDICATED = REQUIRED IGE</li>
 
<li>HOVER Q INDICATED < GO-NO/GO OGE</li>
 
</ol>
 
<li>Takeoff</li>
 
<ol style="list-style-type:lower-alpha">
 
<li>VMC Takeoff</li>
 
<li>VMC Level Acceleration '''(Default if not specified)'''</li>
 
<li>VMC Minimum Power Takeoff</li>
 
<li>Rolling Takeoff</li>
 
</ol></ol>
 
 
 
<u>CPG:</u>
 
# Request clearance and taxi if necessary '''(Only FL CPG)'''
 
<ol start="3"><li>Request takeoff '''(Only FL CPG)'''</li></ol>
 
<ol start="6"><li>Check in with control/AWACS as briefed '''(Only FL CPG)'''</li></ol>
 
 
 
====Landing====
 
 
 
<u>Pilot:</u>
 
<ol start="3"><li>Land as briefed or instructed by Tower</li>
 
<ol style="list-style-type:lower-alpha">
 
<li>VMC Approach to a Hover (Default if not specified)</li>
 
<li>Rolling Landing</li>
 
</ol></ol>
 
<ol start="5"><li>Taxi to parking (If taxiing is needed this is done on the ground)</ol>
 
 
 
<u>CPG:</u>
 
# Check-In with Control/Tower '''(Only FL CPG)'''
 
# Perform Approach/Landing Check
 
::- Wind
 
::- Hazards
 
::- Power required/available
 
::- Etc.
 
<ol start="4"><li>Request taxi to parking if necessary '''(Only FL CPG)'''</ol>
 
 
 
 
 
===En Route===
 
 
 
* Fence In/Fence Out procedures
 
:- Countermeasures – ARM
 
:- Exterior lights – OFF
 
:- MASTER ARM – ARM
 
:- ADF – OFF
 
:- Check fuel state
 
 
 
===Tactical Formations===
 
 
 
<u>Combat Spread:</u>
 
 
 
When entering combat spread, Lead should call out the attack heading (or point of breakthrough) and speed in order to make it easier for wing to keep the formation.
 
 
 
<u>Combat Cruise:</u> '''(Default if not specified)'''
 
 
 
<u>Trail:</u>
 
 
 
<u>Column:</u>
 
 
 
<u>Echelon:</u>
 
 
 
 
 
===Ingress===
 
 
 
 
 
===Attack (Within the BP)===
 
 
 
 
 
===Disengagement and Egress===
 
 
 
==Glossary==
 
 
 
STANDARD MARKING BREVITY TERMS
 
 
 
*<b>BLIND</b> No visual contact with FRIENDLY aircraft/ground position.
 
*<b>VISUAL</b> Sighting of a FRIENDLY aircraft or ground position.
 
*<b>CONTACT</b> Acknowledges sighting of a specified reference point (either visually or via sensor).
 
*<b>CAPTURED</b> Specified surface target or object has been acquired and is being tracked with an onboard sensor.
 
*<b>LOOKING</b> Aircrew does not have the ground object, reference point, or target in sight.
 
*<b>TALLY</b> Sighting of a target, non-friendly aircraft, or enemy position.
 
*<b>NO JOY</b> Aircrew does not have visual contact with the TARGET/BANDIT.
 
 
 
LASER BREVITY TERMS
 
 
 
*<b>TEN SECONDS</b> Standby for LASER ON call in approximately 10 seconds
 
*<b>LASER ON</b> Start/ acknowledge LASER designation
 
*<b>SHIFT</b> Shift LASER aimpoint.
 
*<b>SPOT</b> Acquisition of LASER designation
 
*<b>CEASE LASER</b> Discontinue lasing
 
*<b>DEAD EYE</b> LASER designator system inoperative
 
*<b>NEGATIVE LASER</b> LASER energy has not been acquired
 
*<b>LASING</b> The speaker is firing the LASER
 
*<b>STARE</b> Cue the LASER spot search/ tracker function on the specified location
 
 
 
==Abbreviations==
 
 
 
*<b>ACA</b> Airspace Coordination Areas
 
*<b>ACM</b> Airspace Coordinating Measure/Airspace Control Means
 
*<b>AGL</b> Above Ground Level
 
*<b>AGO</b> Air-Ground Operations*
 
*<b>ALO</b> Air Liaison Officer
 
*<b>BDA</b> Battle Damage Assessment
 
*<b>C2</b> Command and Control
 
*<b>JFC</b> Joint Force Commander
 
 
 
<nowiki>*The simultaneous or synchronized employment of ground forces with aviation
 
maneuver and fires to seize, retain, and exploit the initiative. Also called AGO.</nowiki>
 

Versionen från 1 februari 2023 kl. 16.50

The purpose of "Quickstart Checklists" is to make it easier for new members to carry out a startup in a new model. Be sure to check out TTP for repective module and MA SOP for mandatory steps during startup. In addition, these checklists show only one of many different ways to carry out a startup and there is room to change the order of certain points to suit the pilot's own preferences.

A-10C

The "System Startup Checklist" aims to be easily memorized by walking around the cockpit from left to right.
When performing a "Full startup" (Ordered by FL or when you fly single-ship) the steps in "Engine startup" are preferably carried out simultaneously as the "System Startup". Eg start left engine then go throug the steps in system startup. When left engine is running, start right engine and continue with system startup.

AH-64D

Steps 1-7 in "Startup Procedure" are carried out jointly between the Pilot and CPG (and within the whole flight if not flying single-ship). "System Startup" can mostly be performed in any order as mentioned above.

Pilot

CPG

F-14B

Pilot

RIO

F-16C

F/A-18C

AJS 37