Aircraft Type Considerations

Home >> Technical Guides >> Aircraft Type Considerations

Fixed wing aircraft

F/A-18C Hornet

Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

F-16C Viper

Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

F-15E Strike Eagle

Strengths

+ Radar (A/A and A/G)

+ Air-to-Ground capability

+ Air-to-Ground ordnance capacity

+ Playtime/Time on Station

Weaknesses

- SA (No HMD or DL like Hornet/Viper)

Mission Editor:

• Target Points
  

  Hitman3 with targets 1-3

To simulate the capability of creating missions when still on the ground and then uploading them into the jet using the Data Cartridge, a special Mission Editor option has been added to the F-15E.

Step 1: Click on the flight for which you want to create a new target.

Step 2: Click on the fifth icon from the left and open the "NAVIGATION TARGET POINTS" menu (Red cicle 1).

Step 3: Click on the "ADD" button (Red circle 2).

Step 4: With "ADD" highlighted, click on the point on the map which you would like to become the target. (e.g S-300 TR)

Step 5: Click in the text box "Comment" on the right.

Step 6: Type target info (Red cicle 3).

Target info (Copy to ME and update target number*):

  M1.Y
  H-1
  A0
  V0

* M1.Y, where Y is the target number (1-8). E.g M1.1=target 1, M1.2=target 2 etc. Remember to use capital ‘M’.

Tasks:

• Attack (STRIKE/BAI/CAS)
• CSAR
• Aerial C2/AFAC

Specifications:

• Cruise Airspeed ~M0.8
• Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:

• LANTIRN TGP (FLIR, LRFD)

F-14B Tomcat

Strengths

+ Radar (A/A)

+ AIM-54 Phoenix

Weaknesses

- SA (No HMD, no SA-page like Hornet/Viper)

- Air-to-Ground capability

Mission Editor:

• WP
  

  WP TID/Kneeboard

The F-14 can store up to 10 WP's in the kneeboard but only has 3 active WP in the system, WP 1-3, and these will be put in to the system by "Jester" during startup. Therefore it is recommended to set the most important WP for the mission as WP 1-3. WP4-10 will be added to the kneeboard (See picture)

If using a RIO, the RIO will have to put in WP's in to the system manually.

If using more then 10 WP's they need to be added to the brief to let the crew take notes.

- The order in which the waypoints are listed/layed out should be:

1. WP 1-3 Prioritized mission WP
2. WP 4-10 Additional WP
3. HB "Home Base" *

e.g:

1. WP 1 Nav point
2. WP 2 CAP East
3. WP 3 CAP East
4. WP 4 CAP North (alternative task)
5. WP 5 CAP North (alternative task)
6. WP 6 HB

* HB Waypoint must be the last WP and set to "Landing"

- Type specific WP

In ME the F-14 have a tab (same as Waypoints, Payload etc.) called "Navigation Target Fix Points". In "comment" naming the point as listed below (FP to set a Fixed point etc.) you can add one of each type-specifik point.

• FP = Fix Point, Generic fix-point waypoint.
• IP = Initial Point, Waypoint used for air-to-ground engagement
• ST = Surface Target, Waypoint indicating a surface target.
• DP = Defended Point, Waypoint used to show area to protect.
• HA = Hostile Area, Waypoint indicating a hostile area.

These points can be put in to the system manually by the RIO.

If so, use WP 4-10 in ME and be sure to tell the crew what is what in the brief. E.g: WP 4 = FP, WP 5 = ST etc.

Tasks:

• CAP/Intercept
• Attack (BAI/CAS)
• Reconnaissance
• Aerial C2

Specifications:

• Cruise Airspeed ~470kts
• Normal Fuel Endurance ~2 Hours (7k gallons/hour)

Sensors:

• LANTIRN TGP (FLIR, LRFD)

A-10C Warthog

Strengths

+ Air-to-Ground capability

+ Air-to-Ground ordnance capacity

+ Playtime/Time on Station

Weaknesses

- Slow

- Vulnerable from air threats

Mission Editor:

• WP

- WP2049 = Bullseye and is set automatically on misison start

- If possible, name important waypoints in ME. e.g Target WP = "TGT" or "Target"etc.

-The order in which the waypoints are listed/layed out should be:

1. Departure e.g "Exit North"(If specified/forced by missionmaker)
2. Hold/CP
3. Target
4. Arrival e.g "Entry East"(If known)

Navigation waypoints can be inserted where needed

e.g:

1. Exit North
2. WP 2
3. HOLD
4. TARGET
5. WP 5
6. Entry South

Tasks:

• Attack (BAI/CAS)
• Reconnaissance
• CSAR
• Aerial C2/AFAC

Specifications:

• Cruise Airspeed 300 knots*
• Combat Range ~250nm
• Normal Fuel Endurance ~3 Hours (3k gallons/hour)

* varies with environmental conditions and mission factors

Sensors:

• AN/AAQ-28 LITENING TGP (FLIR, CCD, LST, LRFD and IR-Pointer)

AJS 37 Viggen

The AJS37 is an air-to-ground mission with air-to-air self-defense weapons. When creating missions it is better if possible to divert to road base or secondary airport, instead establishing a holding pattern due to navigation drift. If a holding pattern is needed, it is normally better that it is above ground than above water. However, it is possible to have it above water, but then there should be a WP on a landmark that can be used as a fix point after the hold.

AJS37 should always be placed on a fixed stand due to a bug to get the start point LS correct without editing this manually. It is good to have the first WP near the departure, especially when ToT is in use. AJS37 can use 9 normal WPs plus the landing WP which should always be added as the last WP.

BE could be set as a special WP Bx1, it should not be a normal WP since this will affect fuel calculations and ToT calculations.

To get more out for Viggens it is good to create trigger zone because the AI in DCS is very smart and can see the flight even if they come in low and fast. So something like below 150m doesn't trigger until directly over the target.

It may also be good to give Viggen several tasks, especially if there are short flight distances.

AV-8B Harrier

Typical missions: Air Interdiction, CAS, Strike

Helicopters

UH-1H Huey

Typical missions: Transport

Ka-50 Black Shark

Typical missions: Air Interdiction, CAS

Mi-24P Hind

Typical missions: Air Interdiction, CAS

AH-64D Apache

Strengths

+ Night capability

+ Longbow/AGM-114L (WIP)

Weaknesses

- Limited choice of ordnance / AGM-114 limitations

- SA (Link16, etc.)

Mission Editor:

• Primarily want to operate from FARP
• WP

The apache doesn't quite use the same method regarding flightplan (following wp1->2->3->4 etc.) but instead uses HA's and BP's and moves between them irregularly.

-The order in which the waypoints are listed/layed out should be:

1. Home Base
2. HA's (Should be a relatively safe area for collaboration and giving orders)
3. BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

e.g:

1. Home Base
2. HA 1
3. HA 2
4. BP 1
5. BP 2
6. BP 3

Tasks:

• Movement to contact
• Attack (BAI/CAS)
• Reconnaissance
• Screen/Guard/Security
• Aerial C2

Specifications:

• Cruise Airspeed 110 to 120 knots*
• Normal Fuel Endurance ~2 Hours (average fuel burn: 150 gallons/hour)

* varies with environmental conditions and mission factors

Sensors:

• FCR is capable of detecting, classifying, and prioritizing targets without visual line of sight or in limited visibility, and engaging with RF Hellfire missiles. (WIP)
• RFI identifies and prioritizes radar emitters based on pre-designated signatures.(WIP)
• FLIR, DTV, LST and LRFD