Skillnader mellan sidorna "Close Air Support" och "Mission Procedures"

Från Master Arms Wiki
(Skillnad mellan sidor)
Hoppa till navigering Hoppa till sök
 
 
Rad 1: Rad 1:
''[[Home]] >> [[Tactical Guides]] >> [[Close Air Support]]''
+
''[[Home]] >> [[Standard Operating Procedures]] >> [[Mission Procedures]]''
  
What is close air support?
+
In this example, you are a two-ship F/A-18C Hornet flight called Chevy1 ("Chevy One") on a strike mission. Since you are #1 in the flight and your buddy is #2, you are called Chevy11 ("Chevy One One") and your wingman is called Chevy12 ("Chevy One Two"). Even when contacting someone representing your whole flight, you call yourself Chevy11.
  
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.
+
===Startup===
  
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.
+
Complete the aircraft startup.
  
''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.''
+
Switch to Ground (Ch 6).
  
==Flow overview==
+
Perform a quick check-in, to make sure your wingman/wingmen are on the same channel.
* CAS Request - The JTAC contacts the commander requesting Close Air Support.
 
* CAS Check-in - The CAS flight provides the JTAC with its capabilities.
 
* Situation Update - The JTAC provides some information to give the aircrew some SA.
 
* 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==
+
Pilot: "Chevy1"
 +
Wingman: "2"
  
===CAS Request===
+
Use the kneeboard airport page, along with F2/F10 camera to find out where you are located. For instance "Stand 3" (in the north part of Ramat David).  
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.
 
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).
 
  
===CAS Check-in===
+
Contact Ground (GND) on Ch 6, stating who and where you are. Be ready to readback active runway and QNH.
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: "Ground, Chevy11"
# Position and altitude
+
GND: "Chevy11, Ground"
# Ordnance (including laser codes)
+
Pilot: "Two-ship Hornets on Stand 3."
# Playtime
+
GND: "Chevy1 – Weather is CAVOK. Wind 090, 2 knots, Runway 27 in use, QNH 2992."
# Relevant sensors (typically if the aircraft is carrying targeting pod)
+
Pilot: "Copy weather, 27 in use, QNH 2992."
# 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.
+
With QNH set, contact GND again for clearance. Be ready to take notes, as you are required to readback the clearance.
  
===Situation Update===
+
Pilot: "Ground, Chevy11, Ready to copy clearance"
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.
+
GND: "Chevy11, after departure turn right Exit Kishon. 1500 ft or below"
 +
Pilot: "After departure turn right, Exit Kishon, 1500 ft or below, Chevy11"
  
===CAS-brief===
+
Reflect a few seconds about what this means and take a look in the charts to identify where this "Exit Kishon" is, and if there are any useful landmarks that will help you find it. Visualize the path you’ll be flying after takeoff.  
The pilot writes this down. Typically in a printed CAS sheet. The CAS brief contains three parts:
 
  
====A) Gameplan====
+
===Taxi===
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.
+
When ready to taxi, contact Ground again. Be ready to take quick notes as ground will now give you taxi instructions.
  
====B) 9-line====
+
Pilot: "Chevy11, requesting taxi."
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.
+
GND: "Chevy11 cleared taxi Alpha Hotel Bravo Foxtrot and hold short Runway 27."
 +
Pilot: "Cleared taxi Hotel Bravo Foxtrot and hold short Runway 27, Chevy11."
  
# 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.
+
Take a look in the kneeboard, find the mentioned taxiways, and make up a plan for how to get to Runway 27 by taxiing on those taxiways.  
# 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.
+
Start taxiing. Don’t go too fast. It’s easy to miss a turn. When you have reached the runway (but not entered it, since they asked you to "hold short"), contact ground again (unless they have already contacted you with instructions).
  
====C) Remarks/Restrictions====
+
Pilot: "Chevy1 holding short, Runway 27"
 +
GND: "Chevy11, Contact Tower on channel 7"
 +
Pilot: "Tower on 7. Chevy11." (single aircraft) OR "Chevy1, channel 7, push" (flight of 2+)
  
'''Remarks''' are additional info items to help the pilot. Typical remarks are:
+
Switch to Tower Ch 7, and perform a flight check in.
* 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:
+
Pilot: "Chevy1"
* Final attack heading - If the attack needs to be performed at a certain heading (for instance "090 plus/minus 20").
+
Wingman: "2"
* 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===
+
Let the tower know that you are ready to go.
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===
+
Pilot: "Tower, Chevy11, at runway 27, ready for departure"
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.
+
TWR: "Chevy11, line up and wait runway 27"
 +
Pilot: "Line up and wait 27, Chevy11"
  
===Attack===
+
Now taxi onto the runway coming to a stop with #1 to the left and #2 to the right slightly behind.
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 there is a #3 and/or a #4 they should get behind #1 and #2 in a similar manner.
 +
If there is significant wind coming from the left, mirror the formation so that #1 stands to the right etc instead.
  
* If the JTAC wants the pilot to continue, but he's not ready to let him open fire just yet, he calls "Continue".
+
TWR: "Chevy11, right turnout, cleared for take-off runway 27"
* When the pilot is 'ready to fire' he calls "In hot".
+
Pilot: "Right turn out, cleared for take-off, 27, Chevy11"
* 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.''
+
===Take off and exit===
  
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.  
+
Take off in pairs or as single aircraft with 15 second separation. When airborne, turn towards the exit point, staying below 300 kts and 1500 feet. Expect instructions to switch to control.
  
When the pilot has fired, he calls "Off" if he has fired, or "Off dry" if he didn't fire.
+
TWR: "Chevy11, contact control on channel 8"
 +
Pilot: "Control on 8, Chevy11" (single aircraft) OR "Chevy1, channel 8, push" (flight of 2+)
  
====Laser considerations====
+
Switch to Control Ch 8 and, and perform a flight check in.
  
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.
+
Pilot: "Chevy1"
 +
Wingman: "2"
  
* For a Laser Maverick delivery, laser should be on before launch.
+
Let them know that you are on your way,
* 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".
+
Pilot: "Control, Chevy11, at 1500 ft"
 +
CTL: "Chevy11, radar contact, maintain heading and altitude"
 +
Pilot: "Maintain heading and altitude, Chevy11"
  
===Assessment===
+
When reaching the exit point, expect instructions to switch to AWACS.  
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===
+
CTL: "Chevy11, contact Stingray on channel 3"
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).
+
Pilot: "Stingray on 3, Chevy11" (single aircraft) OR "Chevy1, channel 3, push" (flight of 2+)
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==
+
===Contacting AWACS===
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)===
+
Switch to Package Ch 3, and perform a flight check in.
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===
+
Pilot: "Chevy1"
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''.
+
Wingman: "2"
  
===Type 3 (currently not used)===
+
Perform an AIC (Aeronautical Information Circular) check in with the commanding agency on the channel (usually an AWACS). This often involves an [https://wiki.masterarms.se/index.php?title=Comms#Authentication authentication]. In this example the RAMROD is "GRANDSLICE", so G and A generates the answer R.
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==
+
Pilot: "Stingray, Chevy11"
WIP
+
Stingray: "Chevy11, Stingray"
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.
+
Pilot: "Stingray, Chevy11, Bullseye 180 for 50, Angels 15, as fragged"
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.
+
Stingray: "Stingray copy, Chevy11 authenticate Golf Alpha"
 +
Pilot: "Chevy11 authenticates Romeo"
 +
Stingray: "Stingray Radar Contact"
  
===CAS Request===
+
===Holding and Push===
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===
+
Continue on your mission. In this example you are on a strike mission. It’s common to have a pre-briefed "push time" and a "time on target". The push time tells when you are supposed to leave holding around a certain point (often marked by a waypoint) and continue towards your target (often marked by another waypoint). The reason for this is to make sure you’re in sync with other flights in your package, as planned.
The flight Arctic1 are now enroute to CP Eddie, and has switched to Bowser5's frequency.
 
  
Arctic11: "Bowser5, Arctic11."
+
Continue towards your holding point and orbit around it. 250-300 kts IAS is generally a good speed when holding. When it’s getting close to your push time, adjust your turn so that you get your nose towards the target as close to the push time as possible. Report on the package channel that your flight is pushing.  
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===
+
Pilot: "Chevy1 pushing"
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."
+
===The Attack===
Arctic11: "Ready to copy."
+
In most cases, the leg taking you from hold to target, is planned in a way to put you on the target on the briefed "Time-on-target" (TOT) if you fly at around M 0.8-M 0.9. Sometimes lower depending on aircraft type among other factors. Regardless, you have to monitor your systems and adjust speed to make sure you hit your TOT. In the Hornet, in the top corner of your HSI you can see the estimated time it will take to fly to the selected waypoint.
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).
+
For high altitude JDAM drops (which is very common for strike missions), as a rule of thumb, fly fast enough that the HSI tells you that you will arrive (overfly) the target waypoint 15-30 seconds before your TOT. The reason for this is that it will take some time for your bombs to reach the ground. Being 15-30 seconds early will put you in the ballpark. You will get into max range roughly 90 seconds before your TOT, and this is roughly how long it takes for the bomb to reach the target. Call out on package when you release your bombs:
  
===CAS-brief===
+
Pilot: "Chevy11, pickle"
 +
Wingman: "Chevy12, pickle"
  
====A) Gameplan====
+
As soon as you have dropped your bombs, turn around towards friendly territory. Don’t overfly the target area. As you were on a strike mission in this example, there is normally little reason to stick around, so point your nose towards the home base, and let AWACS know that your flight has dropped the bombs ("Miller Time") and is returning to base ("RTB").
Arctic11: "Ready for gameplan"
 
Bowser5: "Type 2. Bomb on target. Advice when ready for 9-line."
 
Arctic11: "Ready for 9-line."
 
  
====B) 9-line====
+
  Pilot: "Stingray, Chevy11"
  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"
+
Stingray: "Chevy11, Stingray"
  Bowser5: "Advice when ready for remarks."
+
  Pilot: "Chevy1 Miller Time, requesting RTB"
  Arctic11: "Ready for remarks."
+
  Stingray: "Copy, RTB"
  
====C) Remarks/Restrictions====
+
===Returning to Base===
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===
+
When you get close to the base (often somewhere between 25 and 80 nm), AWACS will push you over to Ground. If you haven’t heard anything, before 25 nm, feel free to request a switch to Ground.
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===
+
  Stingray: "Chevy11, Stingray"
  Arctic11: "IP inbound."
+
  Pilot: "Stingray, Chevy11"
  Bowser5: "Continue."
+
  Stingray: "Contact Ramat David Control on Channel 8"
  Arctic11: "In hot."
+
  Pilot: "Control on 8, Chevy11" (single aircraft) OR "Chevy1, channel 8, push" (flight of 2+)
  Bowser5: "Cleared hot!"
 
Arctic11: "Pickle!"
 
  
The bomb hits the first tank and Arctic11 turns back to the IP.
+
Switch to Control Ch 8, and perform a flight check in.
  
  Arctic11: "Off."
+
  Pilot: "Chevy1"
 +
Wingman: "2"
  
===Assessment===
+
Contact control, telling them who you are, distance, altitude and fuel state.
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.
+
Pilot: "Ramat David Control, Chevy11"
 +
CTL: "Chevy11, Control"
 +
Pilot: "Control, Chevy11, two-ship Hornets, inbound, 35 miles south/west of Ramat David at Angels 6, lowest state 4.5."
 +
CTL: "Chevy11, radar contact, turn left/right heading 310"
 +
Pilot: "310 for Chevy11"
  
Arctic11: "Ready for re-attack."
+
Control will continue guiding you to a position which takes you to the airfield from the correct direction (i.e along the radial of the active runway). You might have to hold a while at this position (in a left hand orbit), but can sometimes be cleared for approach without holding.
Bowser: "9 line as before. Do you see another tank 70 meters west of the one you just hit?"
+
Control will guide you towards the airfield, and when you get near, they will hand you over to tower.
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.
+
  CTL: "Chevy11, contact Tower on Channel 7"
   
+
  Pilot "Tower on 7, Chevy11" (single aircraft) OR "Chevy1, channel 7, push" (flight of 2+)
  Bowser5: "Impact. Target destroyed."
 
  
Arctic11 flies back to the IP once again.
+
Switch to Tower Ch 7, and perform a flight check in.
  
===BDA===
+
  Pilot: "Chevy1"
  Bowser5: "BDA as follows. Mission success. Two tanks destroyed. No other enemies. No further help needed. Thanks!"
+
  Wingman: "2"
  Arctic11: "Copy, thanks, checking out!"
 
  
Arctic11 leaves the ROZ and goes back to the package channel.
+
Contact Tower:
  
==Glossary==
+
Pilot "Tower, Chevy11, inbound"
WIP
+
Tower: "Chevy11 report runway in sight"
 +
Pilot: "Report runway in sight, Chevy11"
 +
 
 +
===Landing===
 +
 
 +
When you see the runway, contact tower again:
 +
 
 +
Pilot: "Tower, Chevy11, runway in sight"
 +
Tower: "Chevy11, wind 270, 2 knots, cleared for left overhead break runway 27"
 +
Pilot: "Cleared for left overhead break runway 27, Chevy11"
 +
 
 +
Line up with the runway, flying 300 kts IAS at 1500 feet. Perform the overhead break. The flight lead should contact the tower to receive landing clearance by stating his position either in the base turn or on final. The landing clearance is valid for the wingmen as well. They don't need individual clearances.
 +
 
 +
Pilot: "Chevy11 on final"
 +
Tower: "Chevy11, Tower, cleared to land!"
 +
Pilot: "Cleared to land, Chevy11"
 +
 
 +
===Taxi to Parking===
 +
 
 +
If this wasn’t a touch-n-go, after landing, tower will push you to the Ground channel.
 +
 
 +
Tower: "Chevy11, contact Ground on channel 6"
 +
Pilot: "Ground on 6, Chevy11" (single aircraft) OR "Chevy1, channel 6, push" (flight of 2+)
 +
 
 +
Switch to Ground Ch 6, and perform a flight check in.
 +
 
 +
Pilot: "Chevy1"
 +
Wingman: "2"
 +
 
 +
Contact ground for parking instructions
 +
 
 +
Pilot: "Ground, Chevy11"
 +
GND: "Chevy11, Ground"
 +
Pilot: "Ground, Chevy11, rolling off runway 27, requesting taxi to parking"
 +
GND: "Chevy11, cleared taxi Stand 3 via Lima Mike Alpha"
 +
Pilot: "Cleared to Stand 3 via Lima Mike Alpha, Chevy11"
 +
 
 +
Taxi as instructed, park and shut down.

Versionen från 8 november 2021 kl. 21.58

Home >> Standard Operating Procedures >> Mission Procedures

In this example, you are a two-ship F/A-18C Hornet flight called Chevy1 ("Chevy One") on a strike mission. Since you are #1 in the flight and your buddy is #2, you are called Chevy11 ("Chevy One One") and your wingman is called Chevy12 ("Chevy One Two"). Even when contacting someone representing your whole flight, you call yourself Chevy11.

Startup

Complete the aircraft startup.

Switch to Ground (Ch 6).

Perform a quick check-in, to make sure your wingman/wingmen are on the same channel.

Pilot: "Chevy1"
Wingman: "2"

Use the kneeboard airport page, along with F2/F10 camera to find out where you are located. For instance "Stand 3" (in the north part of Ramat David).

Contact Ground (GND) on Ch 6, stating who and where you are. Be ready to readback active runway and QNH.

Pilot: "Ground, Chevy11"
GND: "Chevy11, Ground"
Pilot: "Two-ship Hornets on Stand 3."
GND: "Chevy1 – Weather is CAVOK. Wind 090, 2 knots, Runway 27 in use, QNH 2992."
Pilot: "Copy weather, 27 in use, QNH 2992."

With QNH set, contact GND again for clearance. Be ready to take notes, as you are required to readback the clearance.

Pilot: "Ground, Chevy11, Ready to copy clearance"
GND: "Chevy11, after departure turn right Exit Kishon. 1500 ft or below"
Pilot: "After departure turn right, Exit Kishon, 1500 ft or below, Chevy11"

Reflect a few seconds about what this means and take a look in the charts to identify where this "Exit Kishon" is, and if there are any useful landmarks that will help you find it. Visualize the path you’ll be flying after takeoff.

Taxi

When ready to taxi, contact Ground again. Be ready to take quick notes as ground will now give you taxi instructions.

Pilot: "Chevy11, requesting taxi."
GND: "Chevy11 cleared taxi Alpha Hotel Bravo Foxtrot and hold short Runway 27."
Pilot: "Cleared taxi Hotel Bravo Foxtrot and hold short Runway 27, Chevy11."

Take a look in the kneeboard, find the mentioned taxiways, and make up a plan for how to get to Runway 27 by taxiing on those taxiways.

Start taxiing. Don’t go too fast. It’s easy to miss a turn. When you have reached the runway (but not entered it, since they asked you to "hold short"), contact ground again (unless they have already contacted you with instructions).

Pilot: "Chevy1 holding short, Runway 27"
GND: "Chevy11, Contact Tower on channel 7"
Pilot: "Tower on 7. Chevy11." (single aircraft) OR "Chevy1, channel 7, push" (flight of 2+)

Switch to Tower Ch 7, and perform a flight check in.

Pilot: "Chevy1"
Wingman: "2"

Let the tower know that you are ready to go.

Pilot: "Tower, Chevy11, at runway 27, ready for departure"
TWR: "Chevy11, line up and wait runway 27"
Pilot: "Line up and wait 27, Chevy11"

Now taxi onto the runway coming to a stop with #1 to the left and #2 to the right slightly behind. If there is a #3 and/or a #4 they should get behind #1 and #2 in a similar manner. If there is significant wind coming from the left, mirror the formation so that #1 stands to the right etc instead.

TWR: "Chevy11, right turnout, cleared for take-off runway 27"
Pilot: "Right turn out, cleared for take-off, 27, Chevy11"

Take off and exit

Take off in pairs or as single aircraft with 15 second separation. When airborne, turn towards the exit point, staying below 300 kts and 1500 feet. Expect instructions to switch to control.

TWR: "Chevy11, contact control on channel 8"
Pilot: "Control on 8, Chevy11" (single aircraft) OR "Chevy1, channel 8, push" (flight of 2+)

Switch to Control Ch 8 and, and perform a flight check in.

Pilot: "Chevy1"
Wingman: "2"

Let them know that you are on your way,

Pilot: "Control, Chevy11, at 1500 ft"
CTL: "Chevy11, radar contact, maintain heading and altitude"
Pilot: "Maintain heading and altitude, Chevy11"

When reaching the exit point, expect instructions to switch to AWACS.

CTL: "Chevy11, contact Stingray on channel 3"
Pilot: "Stingray on 3, Chevy11" (single aircraft) OR "Chevy1, channel 3, push" (flight of 2+)

Contacting AWACS

Switch to Package Ch 3, and perform a flight check in.

Pilot: "Chevy1"
Wingman: "2"

Perform an AIC (Aeronautical Information Circular) check in with the commanding agency on the channel (usually an AWACS). This often involves an authentication. In this example the RAMROD is "GRANDSLICE", so G and A generates the answer R.

Pilot: "Stingray, Chevy11"	
Stingray: "Chevy11, Stingray"		
Pilot: "Stingray, Chevy11, Bullseye 180 for 50, Angels 15, as fragged"
Stingray: "Stingray copy, Chevy11 authenticate Golf Alpha"
Pilot: "Chevy11 authenticates Romeo"
Stingray: "Stingray Radar Contact"

Holding and Push

Continue on your mission. In this example you are on a strike mission. It’s common to have a pre-briefed "push time" and a "time on target". The push time tells when you are supposed to leave holding around a certain point (often marked by a waypoint) and continue towards your target (often marked by another waypoint). The reason for this is to make sure you’re in sync with other flights in your package, as planned.

Continue towards your holding point and orbit around it. 250-300 kts IAS is generally a good speed when holding. When it’s getting close to your push time, adjust your turn so that you get your nose towards the target as close to the push time as possible. Report on the package channel that your flight is pushing.

Pilot: "Chevy1 pushing"

The Attack

In most cases, the leg taking you from hold to target, is planned in a way to put you on the target on the briefed "Time-on-target" (TOT) if you fly at around M 0.8-M 0.9. Sometimes lower depending on aircraft type among other factors. Regardless, you have to monitor your systems and adjust speed to make sure you hit your TOT. In the Hornet, in the top corner of your HSI you can see the estimated time it will take to fly to the selected waypoint.

For high altitude JDAM drops (which is very common for strike missions), as a rule of thumb, fly fast enough that the HSI tells you that you will arrive (overfly) the target waypoint 15-30 seconds before your TOT. The reason for this is that it will take some time for your bombs to reach the ground. Being 15-30 seconds early will put you in the ballpark. You will get into max range roughly 90 seconds before your TOT, and this is roughly how long it takes for the bomb to reach the target. Call out on package when you release your bombs:

Pilot: "Chevy11, pickle"
Wingman: "Chevy12, pickle"

As soon as you have dropped your bombs, turn around towards friendly territory. Don’t overfly the target area. As you were on a strike mission in this example, there is normally little reason to stick around, so point your nose towards the home base, and let AWACS know that your flight has dropped the bombs ("Miller Time") and is returning to base ("RTB").

Pilot: "Stingray, Chevy11"
Stingray: "Chevy11, Stingray"
Pilot: "Chevy1 Miller Time, requesting RTB"
Stingray: "Copy, RTB"

Returning to Base

When you get close to the base (often somewhere between 25 and 80 nm), AWACS will push you over to Ground. If you haven’t heard anything, before 25 nm, feel free to request a switch to Ground.

Stingray: "Chevy11, Stingray"
Pilot: "Stingray, Chevy11"
Stingray: "Contact Ramat David Control on Channel 8"
Pilot: "Control on 8, Chevy11" (single aircraft) OR "Chevy1, channel 8, push" (flight of 2+)

Switch to Control Ch 8, and perform a flight check in.

Pilot: "Chevy1"
Wingman: "2"

Contact control, telling them who you are, distance, altitude and fuel state.

Pilot: "Ramat David Control, Chevy11"
CTL: "Chevy11, Control"
Pilot: "Control, Chevy11, two-ship Hornets, inbound, 35 miles south/west of Ramat David at Angels 6, lowest state 4.5."
CTL: "Chevy11, radar contact, turn left/right heading 310"
Pilot: "310 for Chevy11"

Control will continue guiding you to a position which takes you to the airfield from the correct direction (i.e along the radial of the active runway). You might have to hold a while at this position (in a left hand orbit), but can sometimes be cleared for approach without holding. Control will guide you towards the airfield, and when you get near, they will hand you over to tower.

CTL: "Chevy11, contact Tower on Channel 7"
Pilot "Tower on 7, Chevy11" (single aircraft) OR "Chevy1, channel 7, push" (flight of 2+)

Switch to Tower Ch 7, and perform a flight check in.

Pilot: "Chevy1"
Wingman: "2"

Contact Tower:

Pilot "Tower, Chevy11, inbound"
Tower: "Chevy11 report runway in sight"
Pilot: "Report runway in sight, Chevy11"

Landing

When you see the runway, contact tower again:

Pilot: "Tower, Chevy11, runway in sight"
Tower: "Chevy11, wind 270, 2 knots, cleared for left overhead break runway 27"
Pilot: "Cleared for left overhead break runway 27, Chevy11"

Line up with the runway, flying 300 kts IAS at 1500 feet. Perform the overhead break. The flight lead should contact the tower to receive landing clearance by stating his position either in the base turn or on final. The landing clearance is valid for the wingmen as well. They don't need individual clearances.

Pilot: "Chevy11 on final"
Tower: "Chevy11, Tower, cleared to land!"
Pilot: "Cleared to land, Chevy11"

Taxi to Parking

If this wasn’t a touch-n-go, after landing, tower will push you to the Ground channel.

Tower: "Chevy11, contact Ground on channel 6"
Pilot: "Ground on 6, Chevy11" (single aircraft) OR "Chevy1, channel 6, push" (flight of 2+)

Switch to Ground Ch 6, and perform a flight check in.

Pilot: "Chevy1"
Wingman: "2"

Contact ground for parking instructions

Pilot: "Ground, Chevy11"
GND: "Chevy11, Ground"
Pilot: "Ground, Chevy11, rolling off runway 27, requesting taxi to parking"
GND: "Chevy11, cleared taxi Stand 3 via Lima Mike Alpha"
Pilot: "Cleared to Stand 3 via Lima Mike Alpha, Chevy11"

Taxi as instructed, park and shut down.