|
|
| Rad 1: |
Rad 1: |
| − | ''[[Home]] >> [[Tactical Guides]] >> [[Close Air Support]]''
| + | 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. |
| | | | |
| − | What is close air support?
| + | ==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. |
| | | | |
| − | Close Air Support (CAS) is the direct support of troops on the ground by air assets. It can be done by performed by both fixed wing aircraft and helicopters. Typically, there is an aircraft involved to deliver the weapons, and a controller to direct the fire. In general, the Master Arms CAS procedures are, while based on real life concepts, a bit simplified and streamlined. Most notably, we're currently focusing on ''one'' single way of doing it, namely the '''Keyhole, Type 2''' procedure.
| + | <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> |
| | | | |
| − | A controller is typically on the ground, and called a JTAC (Joint Terminal Attack Controller) or a FAC (Forward Air Controller). He can also be airborne, and is then called a FAC(A) (Forward Air Controller Airborne). For the sake of simplicity we will just refer to the controller as JTAC.
| + | ==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. |
| | | | |
| − | ''In real life, another key player is the ground commander, responsible for ground operations, but in our context it's not a role that is present, so you can disregard from that.''
| + | ===Pilot=== |
| | | | |
| − | ==Flow overview==
| + | <gallery> |
| − | * CAS Request - The JTAC contacts the commander requesting Close Air Support.
| + | File:AH-64D STARTUP 1.png|''Startup Procedure'' |
| − | * CAS Check-in - The CAS flight provides the JTAC with its capabilities.
| + | File:AH-64D STARTUP 2.png|''System Startup'' |
| − | * Situation Update - The JTAC provides some information to give the aircrew some SA.
| + | </gallery> |
| − | * CAS Brief
| |
| − | ** A) Gameplan - The JTAC provides broad term info for the upcoming attack.
| |
| − | ** B) 9-line - The JTAC provides the necessary details for the attack in a standard format.
| |
| − | ** C) Remarks/Restrictions - The JTAC provides additional ''optional'' details.
| |
| − | * Readback - The pilot reads back the ''mandatory'' info from the 9-line and the remarks/restrictions.
| |
| − | * Correlation - The JTAC confirms that the pilot has acquired the correct target.
| |
| − | * Attack - The pilot attacks the target.
| |
| − | * Assessment - The JTAC provides an evaluation of the attack.
| |
| − | * BDA - The JTAC (or the pilot) summarizes the final result of the CAS.
| |
| | | | |
| − | ==Flow details== | + | ===CPG=== |
| | | | |
| − | ===CAS Request===
| + | <gallery> |
| − | The JTAC have identified a situation in which he needs air support. He contacts the commander to request an asset. In our context, this would typically be the AWACS controller. He should specify if he has any certain requirements when it comes to aircraft type, capabilities (sensors, weapons), play time and such. The commander will let the JTAC know if there's a flight available, provide the callsign for that flight and, if possible, and ETA when they will arrive.
| + | File:AH-64D STARTUP 1.png|''Startup Procedure'' |
| − | The commander will provide the CAS flight with the JTAC callsign, a frequency (or channel), and a location to go (can be a waypoint, a coordinate or some other instruction). It can be the target area or the location of a CP (contact point).
| + | File:AH-64D STARTUP 3.png|''System Startup'' |
| | + | </gallery> |
| | | | |
| − | ===CAS Check-in=== | + | ==F-14B== |
| − | When the flight is enroute to the location, they will contact the JTAC letting them know they are on their way. JTACs should be directive about when they want the aircraft to ''check-in'', providing the details on the flight's capabilities. The following info should be included:
| |
| | | | |
| − | # Number and type of aircraft
| + | ===Pilot=== |
| − | # Position and altitude
| |
| − | # Ordnance (including laser codes)
| |
| − | # Playtime
| |
| − | # Relevant sensors (typically if the aircraft is carrying targeting pod)
| |
| − | # Abort code (always "none" or "in the clear" in our case)
| |
| | | | |
| − | If the flight is ''not'' able to work with MGRS coordinates (which is standard), and need some other format (typically DD:MM:DEC coordinates), this should be mentioned.
| + | <gallery> |
| | + | </gallery> |
| | | | |
| − | ===Situation Update=== | + | ===RIO=== |
| − | The JTAC provides a short overview on what's happening, and if there is anything the flight needs to know, like and hazards (air defenses, other CAS flights) or so. In our case, where we always use the Keyhole procedures, an Echo-point is always communicated (and read back) in this step.
| |
| | | | |
| − | ===CAS-brief===
| + | <gallery> |
| − | The pilot writes this down. Typically in a printed CAS sheet. The CAS brief contains three parts:
| + | </gallery> |
| | | | |
| − | ====A) Gameplan==== | + | ==F-16C== |
| − | The JTAC provides a short summary of how the attack is going to be performed. At the least, two items need to be communicated (and typically, this is enough):
| |
| − | * Type of control - There is Type 1, Type 2 and Type 3 attacks.
| |
| − | * Method - "Bomb on target" (BOT) or "Bomb on coordinate" (BOC). With BOT, the pilot will need to acquire the target visually or with a sensor. With BOC, this is not needed, but he will instead attack a certain location on the ground.
| |
| | | | |
| − | The gameplan ''may'' include a requested ordnance type/number.
| + | ==F/A-18C== |
| | | | |
| − | ====B) 9-line==== | + | ==AJS 37== |
| − | The 9-line is a standard format describing the attack details. The JTAC reads every line (some of them might be "not applicable", and are then explicitly communicated that way). The lines are always read in a certain order and should be as short/to-the-point as possible. It's encouraged that the JTAC reads all the line headers ("Elevation", "Target" etc) out loud, to make it easier for less experienced pilots.
| |
| − | | |
| − | # IP (Intitial point) - This starting point from which the attack. In our Type 2 Keyhole procedure, it's a cardinal heading ("Alpha" for North, "Bravo" for East, "Charlie" for South, "Delta" for East) and a distance from the Echo (target) point.
| |
| − | # Heading - The magnetic heading from the IP to the target. Not used if there's no IP. ''(Not relevant during Keyhole procedure)''
| |
| − | # Distance - The distance from the IP to the target. Not used if there's no IP. ''(Not relevant during Keyhole procedure)''
| |
| − | # '''Elevation''' - The target altitude in feet MSL (above mean sea level).
| |
| − | # Target - A concise description, for instance "T-72 tank".
| |
| − | # '''Location''' - Typically just communicated as "by sensor talk-on", but ''can'' be communicated by grid position or lat/long ''if needed''.
| |
| − | # Mark - The JTAC can mark the target with smoke, laser or IR. If laser is used, the laser code should also be provided.
| |
| − | # '''Friendles''' - The distance (in meters) and cardinal/subcardinal ("North-west") direction from the target to the nearest friendles.
| |
| − | # Egress - The cardinal/subcardinal direction for the pilot to egress after weapon employment.
| |
| − | | |
| − | The '''bold''' lines are mandatory for the pilot readback below.
| |
| − | | |
| − | ====C) Remarks/Restrictions====
| |
| − | | |
| − | '''Remarks''' are additional info items to help the pilot. Typical remarks are:
| |
| − | * Type/number or ordnance (if not already specified in gameplan).
| |
| − | * Laser-to-target line - The direction of the laser (for instance "south to north").
| |
| − | * Threats - AAA, manpads etc.
| |
| − | * Weather - Cloud ceiling etc.
| |
| − | * Friendly mark - If the friendlies have marked themselves with smoke or IR.
| |
| − | | |
| − | '''Restrictions''' are things that need to be followed, and always require readback. Typical restrictions are:
| |
| − | * Final attack heading - If the attack needs to be performed at a certain heading (for instance "090 plus/minus 20").
| |
| − | * Danger close - If the attack is expected to hit very close to friendlies (inside of the weapon's "0.1% probability of incapacitation" radius).
| |
| − | * TOT - If there is a certain time-on-target when the weapons is intended to hit the target.
| |
| − | | |
| − | ===Readback===
| |
| − | After the JTAC's CAS brief is finished, the pilot should read back the following things:
| |
| − | * Line 4, 6 and 8 from the 9-line brief.
| |
| − | * Any restrictions.
| |
| − | | |
| − | ===Correlation===
| |
| − | The JTAC needs to make sure the pilot is acquiring the correct target. It can be done in many ways. Typically through a talk-on, guiding the pilot from a reference point, through distinguishable landmarks, to the target. This is a back-and-forth talk between the JTAC and the pilot, and can be very different depending on the situation.
| |
| − | | |
| − | ===Attack===
| |
| − | When the correlation has been completed, the JTAC clears the pilot to approach by asking him to "call when leaving IP". When the pilot has completed his preparations, and has turned towards the target, he calls "IP inbound", meaning he has left the IP and is inbound towards the target.
| |
| − | | |
| − | * If the JTAC wants the pilot to continue, but he's not ready to let him open fire just yet, he calls "Continue".
| |
| − | * When the pilot is 'ready to fire' he calls "In hot".
| |
| − | * If the JTAC wants to cancel the attack, he calls "Abort, abort, abort!".
| |
| − | * When the JTAC is confident everything looks good, he calls "Cleared hot!".
| |
| − | | |
| − | ''Note: For safety, "cleared hot!" are words ONLY to be said by the JTAC, ever. You are not allowed to asked "am I cleared hot". Just say "in", or "in, 4 miles" or such if you need to make the JTAC aware that your delivery window is closing.''
| |
| − | | |
| − | When the pilot fires, he should preferably call out the weapon release. For instance "Pickle" (all bombs) or Rifle (air-to-ground missile, like a Maverick). No callout is needed for a strafe.
| |
| − | | |
| − | When the pilot has fired, he calls "Off" if he has fired, or "Off dry" if he didn't fire.
| |
| − | | |
| − | ====Laser considerations====
| |
| − | | |
| − | If the pilot has released a laser guided weapon, and the JTAC should guide it, the ''pilot'' should call "laser on" when he wants the JTAC to start lasing.
| |
| − | | |
| − | * For a Laser Maverick delivery, laser should be on before launch.
| |
| − | * For a LGB drop, it's generally better to let the bomb fall for a while, building up energy before the laser is turned on, causing the bomb to maneuver.
| |
| − | | |
| − | When the JTAC is firing the laser, he acknowledges this by calling "lasing".
| |
| − | | |
| − | ===Assessment===
| |
| − | After the weapon has impacted, the JTAC should let the pilot know whether it was a hit or miss. Many times, a re-attack is needed. In this case, the JTAC simply asks for a re-attack. The instructions and restrictions from the first attack still apply, so no new CAS brief is needed. The JTAC may give additional instructions when the pilot is maneuvering, typically an target position adjustment. This is typically given with reference to where the previous attack hit ("from your hits, north 100").
| |
| − | | |
| − | ===BDA===
| |
| − | When the JTAC no longer needs the CAS flight, or the CAS flight can no longer support (out of playtime i.e low fuel, out of weapons, other reason), the CAS session ends. The pilot 'or' the JTAC could perform a BDA, but in our case typically the JTAC makes the BDA and communicates it to the pilot).
| |
| − | At minimum, the BDA should say if the engagements were ''successful or not''. Preferably, it should also include the size of the remaining enemy force, their activity (moving or digging in), and observed damage (typically number of destroyed vehicles).
| |
| − | | |
| − | ==Types of control==
| |
| − | There are three different types of control. Currently, we ''only'' use Type 2. The other ones are listed here for future reference.
| |
| − | | |
| − | ===Type 1 (currently not used)===
| |
| − | Type 1 is the most strict type, designed to minimize risk for hitting the wrong target. In this type, the JTAC is required to visually see ''both'' the target ''and'' the attacking aircraft.
| |
| − | | |
| − | ===Type 2===
| |
| − | Type 2 control requires the JTAC to control individual attacks. For safety, the JTAC should attempt to visually acquire both the target and the attacking aircraft, but ''neither is required''.
| |
| − | | |
| − | ===Type 3 (currently not used)===
| |
| − | During Type 3, the JTAC clears the aircraft to engage targets in an area with ''multiple attacks''. Just like in Type 2, he can, but doesn't have to, visually acquire the targets nor the attacking aircraft.
| |
| − | | |
| − | ==Example==
| |
| − | WIP
| |
| − | In our example, a JTAC called Bowser5 has found a group of T-72 tanks that he needs to see destroyed. He has requested air support from his commander (in our case, the mission commander, or the AWACS) called Stingray. A flight of two F/A-18C Hornets called Arctic1 will be dispatched to the area where Bowser5 is operating.
| |
| − | A contact point (CP) called "Eddie" has been setup over a known and clearly visible lake in the AO. This point is known by everybody in the coalition.
| |
| − | | |
| − | ===CAS Request===
| |
| − | Bowser5: "Stingray, Bowser5"
| |
| − | Stingray: "Bowser5, Stingray"
| |
| − | Bowser5: "Requesting air support near CP Eddie"
| |
| − | Stingray5: "Copy. Standby."
| |
| − | Stingray5: "Arctic11, Stingray"
| |
| − | Arctic11: "Stingray, Arctic11."
| |
| − | Stingray: "Are you available for CAS tasking near CP Eddie?"
| |
| − | Arctic11: "Affirmative. Playtime 50 minutes."
| |
| − | Stingray: "Roger. Fly to CP Eddie. Contact Bowser5 on button 10."
| |
| − | Arctic11: "Arctic1, button 10, push."
| |
| − | Stingray: "Bowser5, two-ship F/A-18 Arctic1 is coming to you."
| |
| − | | |
| − | ===CAS Check-in===
| |
| − | The flight Arctic1 are now enroute to CP Eddie, and has switched to Bowser5's frequency.
| |
| − | | |
| − | Arctic11: "Bowser5, Arctic11."
| |
| − | Bowser5: "Arctic11, Bowser5, send your check-in."
| |
| − | Arctic11: "Arctic1, two-ship F/A-18 Charlie, at CP Eddie, angels 15. Carrying 500 20 mike mike, 2 GBU-12, 1 GBU-32 and 1 AMG-65E each aircraft. Laser codes: Arctic11 - 1511, Arctic12 - 1512. Playtime 40 minutes. Carrying ATFLIR."
| |
| − | | |
| − | ===Situation Update===
| |
| − | The JTAC provides a short overview on what's happening, and if there is anything the flight needs to know, like and hazards (air defenses, other CAS flights) or so. In our case, where we always use the Keyhole procedures, an Echo-point is always communicated (and read back) in this step.
| |
| − | | |
| − | Bowser5: "Two enemy T-72 tanks located near a bridge. You are the only flight in the AO. Advice when ready for Echo point."
| |
| − | Arctic11: "Ready to copy."
| |
| − | Bowser5: "38 Tango, Lima November, 480 098."
| |
| − | Arctic11: "38 Tango, Lima November, 480 098."
| |
| − | Bowser5: "Readback correct. Proceed to Bravo 10. Advice when ready for gameplan."
| |
| − | | |
| − | Arctic1 flight now turns to Bravo 10 (meaning 10 nm east of Echo).
| |
| − | | |
| − | ===CAS-brief===
| |
| − | | |
| − | ====A) Gameplan====
| |
| − | Arctic11: "Ready for gameplan"
| |
| − | Bowser5: "Type 2. Bomb on target. Advice when ready for 9-line."
| |
| − | Arctic11: "Ready for 9-line."
| |
| − | | |
| − | ====B) 9-line====
| |
| − | Bowser5: "IP: Bravo 10", "Heading and Distance: N/A", "Elevation: 1725 (One-seven-two-five)", "Target: T-72 tank", "Location: By sensor talk-on", "Mark: None", "Friendlies: 500 meters north", "Egress: Left turn back to IP"
| |
| − | Bowser5: "Advice when ready for remarks."
| |
| − | Arctic11: "Ready for remarks."
| |
| − | | |
| − | ====C) Remarks/Restrictions====
| |
| − | Bowser5: "Requesting GBU-12. Self lase. Restrictions: Final attack heading 270, plus/minus 45."
| |
| − |
| |
| − | ===Readback===
| |
| − | Arctic11: "Elevation: 1725, Location: By sensor talk-on, Friendlies: 500 meters north. Final attack heading 270, plus/minus 45."
| |
| − | Bowser5: "Readback correct. Advice when ready for talk-on."
| |
| − | Arctic11: "Ready for talk-on."
| |
| − | | |
| − | ===Correlation===
| |
| − | Bowser5: "Do you see the bridge on the echo point?"
| |
| − | Arctic11: "Capture."
| |
| − | Bowser5: "Following the road west, 100 meters, do you see the small building?"
| |
| − | Arctic11: "Capture."
| |
| − | Bowser5: "Just to the south of that building, do you see a T-72 tank?"
| |
| − | Arctic11: "Capture."
| |
| − | Bowser5: "That's your target. Advice when IP inbound."
| |
| − | | |
| − | ===Attack===
| |
| − | Arctic11: "IP inbound."
| |
| − | Bowser5: "Continue."
| |
| − | Arctic11: "In hot."
| |
| − | Bowser5: "Cleared hot!"
| |
| − | Arctic11: "Pickle!"
| |
| − | | |
| − | The bomb hits the first tank and Arctic11 turns back to the IP.
| |
| − | | |
| − | Arctic11: "Off."
| |
| − | | |
| − | ===Assessment===
| |
| − | Bowser: "Impact! Target Destroyed. One tank left. Advice when ready for re-attack."
| |
| − | | |
| − | Arctic11 flies back to the IP, and starts looking for the other tank.
| |
| − | | |
| − | Arctic11: "Ready for re-attack."
| |
| − | Bowser: "9 line as before. Do you see another tank 70 meters west of the one you just hit?"
| |
| − | Arctic11: "Capture."
| |
| − | Bowser5: "That's your target. Advice when IP inbound."
| |
| − | Arctic11: "IP inbound."
| |
| − | Bowser5: "Continue."
| |
| − | Arctic11: "In hot."
| |
| − | Bowser5: "Cleared hot!"
| |
| − | Arctic11: "Pickle!"
| |
| − | | |
| − | The bomb hits the other tank and Arctic11 turns back to the IP.
| |
| − |
| |
| − | Bowser5: "Impact. Target destroyed."
| |
| − | | |
| − | Arctic11 flies back to the IP once again.
| |
| − | | |
| − | ===BDA===
| |
| − | Bowser5: "BDA as follows. Mission success. Two tanks destroyed. No other enemies. No further help needed. Thanks!"
| |
| − | Arctic11: "Copy, thanks, checking out!"
| |
| − | | |
| − | Arctic11 leaves the ROZ and goes back to the package channel.
| |
| − | | |
| − | ==Glossary==
| |
| − | WIP
| |
