Master Arms Wiki - Användarbidrag [sv]

Training Briefing Template

2025-06-07T07:51:23Z

Kingtiger45:

''[[Home]] >> [[Training Server]] >> [[Training Briefing Template]]''

Copy-paste this text to make and use it as a base for your own nice looking written briefing!

<nowiki>
Everyone’s welcome to this training!

Training Mission: (e.g CA, Random WX, Night) 

Planned Training:

1. F/A-18C
- TBU

2. F-16C
- TBU

3. F-14B
- TBU

4. AJS 37
- TBU

5. A-10C II
- TBU

6. AH-64D/OH-58D
- TBU

7. AWACS/ATC
- TBU

Additional Training Suggestions:

* Practice things in the <a href="http://wiki.masterarms.se/index.php/Aircraft_Syllabi">syllabus </a>for your main aircraft
* Tanker intercepts and rejoins <a href="https://www.youtube.com/watch?v=ndLOstsNwvo">Jax Tutorial</a>
* Tac turns <a href="http://wiki.masterarms.se/index.php/Advanced_Formations_and_Movement">Wiki</a>
* CASE 1 recovery <a href="http://wiki.masterarms.se/index.php/CASE_1">Wiki</a>
* Overhead break <a href="http://wiki.masterarms.se/index.php/Airport_Procedures#Landing_Pattern">Wiki</a>
* Time-on-target

Sign up, then organize yourselves into flights to practice relevant stuff!
</nowiki>

OH-58D Procedures

2025-06-02T19:16:41Z

Kingtiger45: /* Startup */

''[[Home]] >> [[Standard Operating Procedures]] >> [[Helicopter Procedures]] >> [[OH-58D Procedures]]''

The following sections describe Tactics, Techniques and Procedures (TTP) that are valid only for OH-58D.
<pre style="color: red">Some Tactics and Techniques have reference to the manual "OH58D_User_Guide", this manual can be found in the DCS installation folder "DCS World OpenBeta\Mods\aircraft\OH-58D\Doc"</pre>

==Considerations==

===Operating Altitudes===

===Threat===

===Day versus Night===

==Capabilities==

==Tactics and Techniques==

===Tasks===

===En Route===

====Navigation Tactics====

====Tactical Formations====

===Ingress===

====Control====

Holding Areas: 

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.

Battle Positions:

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====

===Attack (Within the BP)===

====Control====

====Techniques of Attack====

===Disengagement and Egress===

==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 CPO knows who do what and when even if it’s the first time flying together.

===Standard Conventional Loadout===

===Airfield===

====Startup====
When entering the OH-58D Kiowa the pilot will slot in first without touching any controls. Thereafter the CPG slots in and waits untill all textures etc are loaded in. When that is done he will conduct an intercom test with the pilot. When the pilot has replied on the intercom the pilot are clear to initiate the startup procedure.
This is done to avoid common desync issues.

====Taxi / Takeoff====

====Landing====

===En Route===

===Tactical Formations===

===Ingress===

===Attack (Within the BP)===

===Disengagement and Egress===

==Glossary==

OH-58D Procedures

2025-06-02T19:16:30Z

Kingtiger45: /* Startup */

''[[Home]] >> [[Standard Operating Procedures]] >> [[Helicopter Procedures]] >> [[OH-58D Procedures]]''

The following sections describe Tactics, Techniques and Procedures (TTP) that are valid only for OH-58D.
<pre style="color: red">Some Tactics and Techniques have reference to the manual "OH58D_User_Guide", this manual can be found in the DCS installation folder "DCS World OpenBeta\Mods\aircraft\OH-58D\Doc"</pre>

==Considerations==

===Operating Altitudes===

===Threat===

===Day versus Night===

==Capabilities==

==Tactics and Techniques==

===Tasks===

===En Route===

====Navigation Tactics====

====Tactical Formations====

===Ingress===

====Control====

Holding Areas: 

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.

Battle Positions:

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====

===Attack (Within the BP)===

====Control====

====Techniques of Attack====

===Disengagement and Egress===

==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 CPO knows who do what and when even if it’s the first time flying together.

===Standard Conventional Loadout===

===Airfield===

====Startup====
When entering the OH-58D Kiowa the pilot will slot in first without touching any controls. Thereafter the CPG slots in and waits untill all textures etc are loaded in. When that is done he will conduct an intercom test with the pilot. When the pilot has replied on the intercom the pilot are clear to initiate the startup procedure.
This is to avoid common desync issues.

====Taxi / Takeoff====

====Landing====

===En Route===

===Tactical Formations===

===Ingress===

===Attack (Within the BP)===

===Disengagement and Egress===

==Glossary==

Aircraft Type Considerations

2025-06-01T09:29:19Z

Kingtiger45: /* OH-58D Kiowa */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS above rotor so can be in cover and scan/lase
:+ Good mix of weapon options (APKWS+AGM-114K)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP1 needs to be the start up point, if else there is no route back to take off point. Besides that HA and BP as listed on Apache goes for Kiowa to.

Different settings in ME are changed under tab "Aircraft additional properties"
:*Remove doors: OFF as default. Can be adjusted by the crew in mission.
:*Install Pilot Display Unit: OFF for now, realated to CTDs etc bug gives pilot a "HUD" for weapons, nav etc.
:*Remove Mast Mounted Sight: MMS can be removed to loose weight, was done in Iraq a few years or if you want an pre-OH-58D Kiowa warrior version. But this disables all use of laser like buddy-lasing, firing APKWS and Hellires by own aircraft. OH-58D with MMS entered service in 1985 but with no weapons. OH-58D Kiowa warrior with weapons was constructed from 1991 and forward.
:*Rapid Deoployment gear: OFF as standard. Ugly gear that weights more. Was used to load kiowa in cargo planes.
:*Install AN/ALQ-144 IRCM. Older and less effective counter-IR weapons. Was used pre-2009 when CMWS replaced it. NB! If AN/ALQ-144 is installed the L2/MUM function is removed together with CMWS.
:*IDM Net: Leave at 1.

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

Normal weapon loadouts:

:* 0.50cal + 1 pod rockets, can be HE or smoke only or mixed HE/SMK/ILLUM pod.
:* 0.50cal + 1 pod APKWS. APKWS pod can not be mixed with smoke etc.
:* 0.5cal + 1-2 Hellfire AGM-114K
:* 1 APKWS pod + 1-2 Hellfire AGM-114K
:* 2 x rocket pods. can be a mix off one APKWS pod and one HE/SMK pod.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

Aircraft Type Considerations

2025-06-01T09:25:46Z

Kingtiger45: /* OH-58D Kiowa */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS above rotor so can be in cover and scan/lase
:+ Good mix of weapon options (APKWS+AGM-114K)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP1 needs to be the start up point, if else there is no route back to take off point. Besides that HA and BP as listed on Apache goes for Kiowa to.

Different settings in ME are changed under tab "Aircraft additional properties"
:*Remove doors: OFF as default. Can be adjusted by the crew in mission.
:*Install Pilot Display Unit: OFF for now, realated to CTDs etc bug gives pilot a "HUD" for weapons, nav etc.
:*Remove Mast Mounted Sight: MMS can be removed to loose weight, was done in Iraq a few years or if you want an pre-OH-58D (mid-cold war) version. But this disables all use of laser like buddy-lasing, firing APKWS and Hellires by own aircraft.
:*Rapid Deoployment gear: OFF as standard. Ugly gear that weights more. Was used to load kiowa in cargo planes.
:*Install AN/ALQ-144 IRCM. Older and less effective counter-IR weapons. Was used pre-2009 when CMWS replaced it. NB! If AN/ALQ-144 is installed the L2/MUM function is removed together with CMWS.
:*IDM Net: Leave at 1.

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

Normal weapon loadouts:

:* 0.50cal + 1 pod rockets, can be HE or smoke only or mixed HE/SMK/ILLUM pod.
:* 0.50cal + 1 pod APKWS. APKWS pod can not be mixed with smoke etc.
:* 0.5cal + 1-2 Hellfire AGM-114K
:* 1 APKWS pod + 1-2 Hellfire AGM-114K
:* 2 x rocket pods. can be a mix off one APKWS pod and one HE/SMK pod.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

Aircraft Type Considerations

2025-06-01T09:19:38Z

Kingtiger45: /* OH-58D Kiowa */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS above rotor so can be in cover and scan/lase
:+ Good mix of weapon options (APKWS+AGM-114K)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP1 needs to be the start up point, if else there is no route back to take off point. Besides that HA and BP as listed on Apache goes for Kiowa to.

Different settings in ME are changed under tab "Aircraft additional properties"
:*Remove doors: OFF as default. Can be adjusted by the crew in mission.
:*Install Pilot Display Unit: OFF for now, realated to CTDs etc bug gives pilot a "HUD" for weapons, nav etc.
:*Remove Mast Mounted Sight: MMS can be removed to loose weight, was done in Iraq a few years or if you want an pre-OH-58D version. But this disables all use of laser like buddy-lasing, firing APKWS and Hellires by own aircraft.
:*Rapid Deoployment gear: OFF as standard. Ugly gear that weights more. Was used to load kiowa in cargo planes.
:*Install AN/ALQ-144 IRCM. Older and less effective counter-IR weapons. Was used pre-2009 when CMWS replaced it. NB! If AN/ALQ-144 is installed the L2/MUM function is removed together with CMWS.
:*IDM Net: Leave at 1.

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

Normal weapon loadouts:

:* 0.50cal + 1 pod rockets, can be HE or smoke only or mixed HE/SMK/ILLUM pod.
:* 0.50cal + 1 pod APKWS. APKWS pod can not be mixed with smoke etc.
:* 0.5cal + 1-2 Hellfire AGM-114K
:* 1 APKWS pod + 1-2 Hellfire AGM-114K
:* 2 x rocket pods. can be a mix off one APKWS pod and one HE/SMK pod.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

Aircraft Type Considerations

2025-06-01T09:18:32Z

Kingtiger45: /* OH-58D Kiowa */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS above rotor so can be in cover and scan/lase
:+ Good mix of weapon options (APKWS+AGM-114K)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP1 needs to be the start up point, if else there is no route back to take off point. Besides that HA and BP as listed on Apache goes for Kiowa to.

Different settings in ME are changed under tab "Aircraft additional properties"
:*Remove doors: OFF as default. Can be adjusted by the crew in mission.
:*Install Pilot Display Unit: OFF for now, realated to CTDs etc bug gives pilot a "HUD" for weapons, nav etc.
:*Remove Mast Mounted Sight: MMS can be removed to loose weight, was done in Iraq a few years. But this disables all use of laser like buddy-lasing, firing APKWS and Hellires by own aircraft.
:*Rapid Deoployment gear: OFF as standard. Ugly gear that weights more. Was used to load kiowa in cargo planes.
:*Install AN/ALQ-144 IRCM. Older and less effective counter-IR weapons. Was used pre-2009 when CMWS replaced it. NB! If AN/ALQ-144 is installed the L2/MUM function is removed together with CMWS.
:*IDM Net: Leave at 1.

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

Normal weapon loadouts:

:* 0.50cal + 1 pod rockets, can be HE or smoke only or mixed HE/SMK/ILLUM pod.
:* 0.50cal + 1 pod APKWS. APKWS pod can not be mixed with smoke etc.
:* 0.5cal + 1-2 Hellfire AGM-114K
:* 1 APKWS pod + 1-2 Hellfire AGM-114K
:* 2 x rocket pods. can be a mix off one APKWS pod and one HE/SMK pod.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

Aircraft Type Considerations

2025-06-01T09:17:46Z

Kingtiger45: /* OH-58D Kiowa */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS above rotor so can be in cover and scan/lase
:+ Good mix of weapon options (APKWS+AGM-114K)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP1 needs to be the start up point, if else there is no route back to take off point. Besides that HA and BP as listed on Apache goes for Kiowa to.

Different settings in ME are changed under tab "Aircraft additional properties"
:*Remove doors: OFF as default. Can be adjusted by the crew in mission.
:*Install Pilot Display Unit: OFF for now, realated to CTDs etc bug gives pilot a "HUD" for weapons, nav etc.
:*Remove Mast Mounted Sight: MMS can be removed to loose weight, was done in Iraq a few years. But this disables all use of laser like buddy-lasing, firing APKWS and Hellires by own aircraft.
:*Rapid Deoployment gear: OFF as standard. Ugly gear that weights more. Was used to load kiowa in cargo planes.
:*Install AN/ALQ-144 IRCM. Older and less effective counter-IR weapons. Was used pre-2009 when CMWS replaced it.
NB! If AN/ALQ-144 is installed the L2/MUM function is removed together with CMWS.
:*IDM Net: Leave at 1.

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

Normal weapon loadouts:

:* 0.50cal + 1 pod rockets, can be HE or smoke only or mixed HE/SMK/ILLUM pod.
:* 0.50cal + 1 pod APKWS. APKWS pod can not be mixed with smoke etc.
:* 0.5cal + 1-2 Hellfire AGM-114K
:* 1 APKWS pod + 1-2 Hellfire AGM-114K
:* 2 x rocket pods. can be a mix off one APKWS pod and one HE/SMK pod.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

Aircraft Type Considerations

2025-06-01T08:56:00Z

Kingtiger45: /* OH-58D Kiowa */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS above rotor so can be in cover and scan/lase
:+ Good mix of weapon options (APKWS+AGM-114K)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP1 needs to be the start up point, if else there is no route back to take off point. Besides that HA and BP as listed on Apache goes for Kiowa to.

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

Normal weapon loadouts:

:* 0.50cal + 1 pod rockets, can be HE or smoke only or mixed HE/SMK/ILLUM pod.
:* 0.50cal + 1 pod APKWS. APKWS pod can not be mixed with smoke etc.
:* 0.5cal + 1-2 Hellfire AGM-114K
:* 1 APKWS pod + 1-2 Hellfire AGM-114K
:* 2 x rocket pods. can be a mix off one APKWS pod and one HE/SMK pod.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

Aircraft Type Considerations

2025-06-01T08:55:26Z

Kingtiger45: /* OH-58D Kiowa */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS above rotor so can be in cover and scan/lase
:+ Good mix of weapon options (APKWS+AGM-114K)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP1 needs to be the start up point, if else there is no route back to take off point. Besides that HA and BP as listed on Apache goes for Kiowa to.

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

Normal weapon loadouts:

:* 0.50cal + 1 pod rockets, can be HE or smoke only or mixed HE/SMK pod.
:* 0.50cal + 1 pod APKWS. APKWS pod can not be mixed with smoke etc.
:* 0.5cal + 1-2 Hellfire AGM-114K
:* 1 APKWS pod + 1-2 Hellfire AGM-114K
:* 2 x rocket pods. can be a mix off one APKWS pod and one HE/SMK pod.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

Aircraft Type Considerations

2025-06-01T08:55:08Z

Kingtiger45: /* OH-58D Kiowa */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS above rotor so can be in cover and scan/lase
:+ Good mix of weapon options (APKWS+AGM-114K)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP1 needs to be the start up point, if else there is no route back to take off point. Besides that HA and BP as listed on Apache goes for Kiowa to.

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

Normal weapon loadouts:

:* 0.50cal + 1 pod rockets, can be HE or smoke only or mixed HE/SMK pod.
:* 0.50cal + 1 pod APKWS. APWKS pod can not be mixed with smoke etc.
:* 0.5cal + 1-2 Hellfire AGM-114K
:* 1 APKWS pod + 1-2 Hellfire AGM-114K
:* 2 x rocket pods. can be a mix off one APKWS pod and one HE/SMK pod.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

Aircraft Type Considerations

2025-06-01T08:51:05Z

Kingtiger45: /* OH-58D Kiowa */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS above rotor so can be in cover and scan/lase
:+ Good mix of weapon options (APKWS+AGM-114K)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP1 needs to be the start up point, if else there is no route back to take off point. Besides that HA and BP as listed on Apache goes for Kiowa to.

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

Normal weapon loadouts:

:* 0.50cal + 1 pod rockets, can be HE or smoke only or mixed HE/SMK pod.
:* 0.50cal + 1 pod APKWS. APWKS pod can not be mixed with smoke etc.
:* 0.5cal + 1-2 Hellfire AGM-114K
:* 1 APWKS pod + 1-2 Hellfire AGM-114K
:* 2 x rocket pods. can be a mix off one APWKS pod and one HE/SMK pod.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

Aircraft Type Considerations

2025-06-01T08:50:54Z

Kingtiger45: /* OH-58D Kiowa */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS above rotor so can be in cover and scan/lase
:+ Good mix of weapon options (APWKS+AGM-114K)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP1 needs to be the start up point, if else there is no route back to take off point. Besides that HA and BP as listed on Apache goes for Kiowa to.

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

Normal weapon loadouts:

:* 0.50cal + 1 pod rockets, can be HE or smoke only or mixed HE/SMK pod.
:* 0.50cal + 1 pod APKWS. APWKS pod can not be mixed with smoke etc.
:* 0.5cal + 1-2 Hellfire AGM-114K
:* 1 APWKS pod + 1-2 Hellfire AGM-114K
:* 2 x rocket pods. can be a mix off one APWKS pod and one HE/SMK pod.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

Aircraft Type Considerations

2025-06-01T08:42:58Z

Kingtiger45: /* OH-58D Kiowa */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS above rotor so can be in cover and scan/lase
:+ Good mix of weapon options (APWKS+AGM-114L)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP1 needs to be the start up point, if else there is no route back to take off point. Besides that HA and BP as listed on Apache goes for Kiowa to.

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

Normal weapon loadouts:

:* 0.50cal + 1 pod rockets, can be HE or smoke only or mixed HE/SMK pod.
:* 0.50cal + 1 pod APKWS. APWKS pod can not be mixed with smoke etc.
:* 0.5cal + 1-2 Hellfire AGM-114K
:* 1 APWKS pod + 1-2 Hellfire AGM-114K
:* 2 x rocket pods. can be a mix off one APWKS pod and one HE/SMK pod.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

Aircraft Type Considerations

2025-06-01T08:38:24Z

Kingtiger45: /* OH-58D Kiowa */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS above rotor so can be in cover and scan/lase
:+ Good mix of weapon options (APWKS+AGM-114L)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP

::The Kiowa 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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered into system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# BP 3

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

Aircraft Type Considerations

2025-06-01T08:37:49Z

Kingtiger45: /* Helicopters */

''[[Home]] >> [[Technical Guides]] >> [[Aircraft Type Considerations]]''

==Fixed wing aircraft==

===A-10C Warthog===
Typical missions:
:* Attack (BAI/CAS)
:* Reconnaissance
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.48
:* Combat Range ~250nm
:* Normal Fuel Endurance ~3 Hours (3k gallons/hour)

Sensors:

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

Strengths
:+ Air-to-Ground capability
:+ Air-to-Ground ordnance capacity
:+ Playtime/Time on Station

Weaknesses
:- Slow
:- Vulnerable from air threats

Mission Editor:
:* WP

::- Don't need WP on Bullseye (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:
:::# Departure e.g "Exit North"(If specified/forced by missionmaker)
:::# Hold/CP
:::# Target area
:::# Arrival e.g "Entry East"(If known)
::: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# HOLD
:::# TARGET
:::# WP 5
:::# Entry South

===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

===F-14B Tomcat===
Typical missions:
:* CAP/Intercept
:* STRIKE
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.75
:* Normal Fuel Endurance ~2 Hours (6k gallons/hour)

Sensors:

:* LANTIRN TGP (FLIR, LRFD)

Strengths

:+ Radar (A/A)
:+ AIM-54 Phoenix

Weaknesses

:- SA (No HMD, no SA-page like Hornet/Viper)
:- Air-to-Ground capability

Mission Editor:

* WP [[Fil:F14 WP.png|500px|thumb|right|WP TID/Kneeboard]]

:- Set "Fixed Point" (FP) on Bullseye (See "Type specific WP"-section below)

: 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:
:::# WP 1-3 Prioritized mission WP
:::# WP 4-10 Additional WP
:::# HB "Home Base" *

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

:::<nowiki>* HB Waypoint must be the last WP and set to "Landing"</nowiki>

* Type specific WP [[Fil:F-14B Target.png|500px|thumb|right|Elvis5 with surface target 1]]
: To add type specific WP, see F-15E "JDAM Target Point"-section above. Follow step 1-5 and in "Comment" name the point as listed below, e.g "ST" to add a surface target point.(you can add one of each type-specifik point).
: Remember to use capital letters ‘ST’.
::- 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.

===F-15E Strike Eagle===
Typical missions:
:* STRIKE/BAI/CAS
:* CSAR
:* Aerial C2/AFAC

Specifications:
:* Cruise Airspeed ~M0.8
:* Combat Range ~680 NM
:* Normal Fuel Endurance ~3 Hours (~8k gallons/hour)

Sensors:
:* LANTIRN TGP (FLIR, LRFD)

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:
* WP
:- Don't need WP on Bullseye
:-The order in which the waypoints are listed/layed out should be:
::# Departure e.g "Exit North"(If specified/forced by missionmaker)
::# Hold/CP
::# Target area
::# Arrival e.g "Entry East"(If known)
:: Navigation waypoints can be inserted where needed

::: e.g:
:::# Exit North
:::# WP 2
:::# Hold
:::# Target area
:::# WP 5
:::# Entry South

*JDAM Target Points [[Fil:F-15E Target.png|700px|thumb|right|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 circle 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 circle 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’.

===F-16C Viper===
Typical missions: CAP, Strike, CAS, Air Interdiction, SEAD

===F/A-18C Hornet===
Typical missions: Strike, SEAD, Air Interdiction, CAS, CAP

===M-2000C===
Typical missions:
:* INTERCEPT/CAP
:* STRIKE/BAI/CAS

Specifications:
:* Cruise Airspeed ~M0.85
:* Normal Fuel Endurance ~2 Hours (~1500 kg/hour) with Standard air-to-air loadout (including centerline drop tank)

Sensors:
:* RDI pulse-Doppler radar with an maximum detection range of 80 nm and ~65 nm against a fighter sized target

Strengths
:+ Fast
:+ Secure communication link can be used by the AWACS or GCI to transmit target information and directives to the aircraft though the LotAtc software. (Limit use of voice comms)
:+ BAP-100 anti-runway bombs

Weaknesses
:- SA (No HMD or DL like Hornet/Viper)
:- No active radar-guided missile, but the Super 530D is a good semi-active radar guided missile. (The Super 530D are incompatible with any underwing air-to-ground weapon)
:- No sensor- or targeting pod

Mission Editor:
* No WPs need to be set as a standard. M-2000C uses data cartridge (DTC) created by FL.
* Bullseye needs to be set to a WP. (If set by missionmaker)
* Check/set options under "Aricraft Additional Properties" tab as below:
:- IFF Mode 2 code: Auto
:- Waypoint Bullseye: Desired WP
:- Enforce INS drift: Checked
:- Aircraft is ALCM ready: Checked
:- Load NVG Case: Checked
:- Initial drift for in flight start: 0
:- Enable TAF (GCI link): Checked

==Helicopters==

===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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered inteo system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# 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)
:<nowiki>* varies with environmental conditions and mission factors</nowiki>

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

===OH-58D Kiowa===
Strengths

:+ Night capability
:+ MMS over rotor
:+ Good mix of weapon options (APWKS+AGM-114L)
:+ Good SA for ground (bluefor tracker, graphics in system etc)

Weaknesses

:- Limited weight so not weapons heavy
:- SA for air (Link16, etc.)

Mission Editor:

:* Primarily want to operate from FARP
:* Has battle graphics and routes that needs to be added in the ME until bugs are fixed. How to do this is listed in the manual.
:* WP

::The Kiowa 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:
:::# Home Base
:::# HA's (Should be a relatively safe area for collaboration and giving orders)
:::# BP's within 4nm/8km from target (can be determined and entered into system during startup by the crew)

::: e.g:
:::# Home Base
:::# HA 1
:::# HA 2
:::# BP 1
:::# BP 2
:::# BP 3

Tasks:

:* Reconnaissance
:* Movement to contact
:* Screen/Guard/Security
:* Light attack (BAI/CAS)

Specifications:

:*Cruise Airspeed 80 to 90 knots*
:*Normal Fuel Endurance ~2 hours empty, ~1.5 hours with weapon load (average fuel burn: 310-330 gallons/hour with full tank of 717lbs)
:<nowiki>* varies with environmental conditions, mission factors and biggest impact what weapon loadout is carried.</nowiki>

Sensors:

:* MMS is daycamera and thermal capable, and can lase out to 29km with "normal" conditions being able to identify and lase targets up to 20-25km.
:* L2/MUM capable, so can see what a drone is streaming. NB the drone needs to exist when the mission begins, spawned-in drones are not populated to the kiowa feed.
:* Bluefore tracker (ELPS) so tracks ground units that on bluefor and have ELPS active.

===Ka-50 Black Shark===
Typical missions: Air Interdiction, CAS

===Mi-24P Hind===
Typical missions: Air Interdiction, CAS

===UH-1H Huey===
Typical missions: Transport

OH-58D Kiowa Syllabus

2025-03-30T16:42:20Z

Kingtiger45: /* MMS */

''[[Home]] >> [[Helicopter Syllabi]] >> [[OH-58D Kiowa Syllabus]]''

If not specified in the Syllabus all procedures are to be followed as described in the OH-58D. <pre style="color: red">"OH58D_User_Guide" can be found in the DCS installation folder "DCS World OpenBeta\Mods\aircraft\OH-58D\Doc"</pre>

If you are new to the MA-community, be sure to read about our procedures around the airfield (Linked below) to ensure everyone can have a safe training environment. Good luck and have fun!

* [http://wiki.masterarms.se/index.php/Airport_Procedures Airport procedures]
* [http://wiki.masterarms.se/index.php/Charts Airport charts]
:- Runways
:- Taxiways
:- TACAN/ILS Freq
:- Entry/Exit points

=Pilot=

==Basic Section==

The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

===General===

====Radio/SRS====

* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

===Flying===

====Startup====
*According to Manual 18.1 Startup

====Takeoff====

====In-flight====
* Flying
:- Fly in Combat cruise formation at low-level profile.
:- Fly NOE as a single-ship in flat and open terrain.
:- Hover IGE and OGE
:- VRS Recovery

* Navigation
:- Visually navigate between two points using for example terrain objects as guidence (the compass and an empty F10 map may be used)
:- Follow several waypoints in succession (flightplan) using information provided by the in-cockpit instruments or projected on VSD/HSD.

* Trim/Autopilot
:- Force trim
:- Engage/Disengage:

* Fence In / Fence Out procedures

====Landing====

===Combat===

====Air-To-Air====
*ATAS Stingers
:-Engage enemy air targets without the use of MMS slaving.

====Air-To-Ground====
*Gun
:-Engaging soft armored targets with 0.50cal and lead tracers onto target.

*Rockets
:-Engage soft/light armored targets with HE 10pd or 17pd rockets and adjust fire from earlier impact.

*Missiles
:-Engage targets with APWKS
:-Engage targets with Hellfire

====Defence====
*CMWS
:-Set up CMWS for bypass or auto
*AN/APR-39 & AN/AVR-2
:-Understanding AN/APR-39 & AN/AVR-2 Radar and Laser warning systems symbols and sound alerts.

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

=Co-Pilot/Gunner=

==Basic Section==
The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

-MMS basic skills
-Storing targets
-Laser codes/lasing

===General===

====Radio/SRS====
* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

====MMS====

MMS Control Panel
*Laser
:-Change lasercode
:-Arm/disengage laser
:-Using first/last laser return

*Video settings
:-Adjust MMS MFD detail color by using SYM INTEN MFD-MMS
:-Adjust thermal settings by using GAIN and LEVEL
:-Adjust focus using FOC

MMS Mode Select Switch & Copilot Auxiliary Control Panel
*MMS Knob
:-Switch between OFF/PREPT/FWD

*Settings
:-Switching between WPN/ALE
:-Switching between IDM/INIT

*LMC
:-Using LMC to stabilise camera

MMS Display
:-Toggle active lasercode

===Flying===

====Startup====
*According to Manual 18.1 Startup

====Takeoff====

====In-flight====
* Flying
:- Fly in Combat cruise formation at low-level profile.
:- Fly NOE as a single-ship in flat and open terrain.
:- Hover IGE and OGE
:- VRS Recovery

* Navigation
:- Visually navigate between two points using for example terrain objects as guidence (the compass and an empty F10 map may be used)
:- Follow several waypoints in succession (flightplan) using information provided by the in-cockpit instruments or projected on VSD/HSD.

* Trim/Autopilot
:- Force trim
:- Engage/Disengage:

* Fence In / Fence Out procedures

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

OH-58D Kiowa Syllabus

2025-03-30T16:38:27Z

Kingtiger45: /* MMS */

''[[Home]] >> [[Helicopter Syllabi]] >> [[OH-58D Kiowa Syllabus]]''

If not specified in the Syllabus all procedures are to be followed as described in the OH-58D. <pre style="color: red">"OH58D_User_Guide" can be found in the DCS installation folder "DCS World OpenBeta\Mods\aircraft\OH-58D\Doc"</pre>

If you are new to the MA-community, be sure to read about our procedures around the airfield (Linked below) to ensure everyone can have a safe training environment. Good luck and have fun!

* [http://wiki.masterarms.se/index.php/Airport_Procedures Airport procedures]
* [http://wiki.masterarms.se/index.php/Charts Airport charts]
:- Runways
:- Taxiways
:- TACAN/ILS Freq
:- Entry/Exit points

=Pilot=

==Basic Section==

The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

===General===

====Radio/SRS====

* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

===Flying===

====Startup====
*According to Manual 18.1 Startup

====Takeoff====

====In-flight====
* Flying
:- Fly in Combat cruise formation at low-level profile.
:- Fly NOE as a single-ship in flat and open terrain.
:- Hover IGE and OGE
:- VRS Recovery

* Navigation
:- Visually navigate between two points using for example terrain objects as guidence (the compass and an empty F10 map may be used)
:- Follow several waypoints in succession (flightplan) using information provided by the in-cockpit instruments or projected on VSD/HSD.

* Trim/Autopilot
:- Force trim
:- Engage/Disengage:

* Fence In / Fence Out procedures

====Landing====

===Combat===

====Air-To-Air====
*ATAS Stingers
:-Engage enemy air targets without the use of MMS slaving.

====Air-To-Ground====
*Gun
:-Engaging soft armored targets with 0.50cal and lead tracers onto target.

*Rockets
:-Engage soft/light armored targets with HE 10pd or 17pd rockets and adjust fire from earlier impact.

*Missiles
:-Engage targets with APWKS
:-Engage targets with Hellfire

====Defence====
*CMWS
:-Set up CMWS for bypass or auto
*AN/APR-39 & AN/AVR-2
:-Understanding AN/APR-39 & AN/AVR-2 Radar and Laser warning systems symbols and sound alerts.

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

=Co-Pilot/Gunner=

==Basic Section==
The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

-MMS basic skills
-Storing targets
-Laser codes/lasing

===General===

====Radio/SRS====
* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

====MMS====

MMS Control Panel
*Laser
:-Change lasercode
:-Arm/disengage laser
:-Using first/last laser return

*Video settings
:-Adjust MMS MFD detail color by using SYM INTEN MFD-MMS
:-Adjust thermal settings by using GAIN and LEVEL
:-Adjust focus using FOC

MMS Mode Select Switch & Copilot Auxiliary Control Panel

MMS Display
:-Toggle active lasercode

===Flying===

====Startup====
*According to Manual 18.1 Startup

====Takeoff====

====In-flight====
* Flying
:- Fly in Combat cruise formation at low-level profile.
:- Fly NOE as a single-ship in flat and open terrain.
:- Hover IGE and OGE
:- VRS Recovery

* Navigation
:- Visually navigate between two points using for example terrain objects as guidence (the compass and an empty F10 map may be used)
:- Follow several waypoints in succession (flightplan) using information provided by the in-cockpit instruments or projected on VSD/HSD.

* Trim/Autopilot
:- Force trim
:- Engage/Disengage:

* Fence In / Fence Out procedures

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

OH-58D Kiowa Syllabus

2025-03-30T16:34:03Z

Kingtiger45: /* MMS */

''[[Home]] >> [[Helicopter Syllabi]] >> [[OH-58D Kiowa Syllabus]]''

If not specified in the Syllabus all procedures are to be followed as described in the OH-58D. <pre style="color: red">"OH58D_User_Guide" can be found in the DCS installation folder "DCS World OpenBeta\Mods\aircraft\OH-58D\Doc"</pre>

If you are new to the MA-community, be sure to read about our procedures around the airfield (Linked below) to ensure everyone can have a safe training environment. Good luck and have fun!

* [http://wiki.masterarms.se/index.php/Airport_Procedures Airport procedures]
* [http://wiki.masterarms.se/index.php/Charts Airport charts]
:- Runways
:- Taxiways
:- TACAN/ILS Freq
:- Entry/Exit points

=Pilot=

==Basic Section==

The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

===General===

====Radio/SRS====

* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

===Flying===

====Startup====
*According to Manual 18.1 Startup

====Takeoff====

====In-flight====
* Flying
:- Fly in Combat cruise formation at low-level profile.
:- Fly NOE as a single-ship in flat and open terrain.
:- Hover IGE and OGE
:- VRS Recovery

* Navigation
:- Visually navigate between two points using for example terrain objects as guidence (the compass and an empty F10 map may be used)
:- Follow several waypoints in succession (flightplan) using information provided by the in-cockpit instruments or projected on VSD/HSD.

* Trim/Autopilot
:- Force trim
:- Engage/Disengage:

* Fence In / Fence Out procedures

====Landing====

===Combat===

====Air-To-Air====
*ATAS Stingers
:-Engage enemy air targets without the use of MMS slaving.

====Air-To-Ground====
*Gun
:-Engaging soft armored targets with 0.50cal and lead tracers onto target.

*Rockets
:-Engage soft/light armored targets with HE 10pd or 17pd rockets and adjust fire from earlier impact.

*Missiles
:-Engage targets with APWKS
:-Engage targets with Hellfire

====Defence====
*CMWS
:-Set up CMWS for bypass or auto
*AN/APR-39 & AN/AVR-2
:-Understanding AN/APR-39 & AN/AVR-2 Radar and Laser warning systems symbols and sound alerts.

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

=Co-Pilot/Gunner=

==Basic Section==
The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

-MMS basic skills
-Storing targets
-Laser codes/lasing

===General===

====Radio/SRS====
* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

====MMS====

MMS Control Panel

MMS Mode Select Switch & Copilot Auxiliary Control Panel

INIT-Page

===Flying===

====Startup====
*According to Manual 18.1 Startup

====Takeoff====

====In-flight====
* Flying
:- Fly in Combat cruise formation at low-level profile.
:- Fly NOE as a single-ship in flat and open terrain.
:- Hover IGE and OGE
:- VRS Recovery

* Navigation
:- Visually navigate between two points using for example terrain objects as guidence (the compass and an empty F10 map may be used)
:- Follow several waypoints in succession (flightplan) using information provided by the in-cockpit instruments or projected on VSD/HSD.

* Trim/Autopilot
:- Force trim
:- Engage/Disengage:

* Fence In / Fence Out procedures

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

OH-58D Kiowa Syllabus

2025-03-30T16:32:00Z

Kingtiger45: /* General */

''[[Home]] >> [[Helicopter Syllabi]] >> [[OH-58D Kiowa Syllabus]]''

If not specified in the Syllabus all procedures are to be followed as described in the OH-58D. <pre style="color: red">"OH58D_User_Guide" can be found in the DCS installation folder "DCS World OpenBeta\Mods\aircraft\OH-58D\Doc"</pre>

If you are new to the MA-community, be sure to read about our procedures around the airfield (Linked below) to ensure everyone can have a safe training environment. Good luck and have fun!

* [http://wiki.masterarms.se/index.php/Airport_Procedures Airport procedures]
* [http://wiki.masterarms.se/index.php/Charts Airport charts]
:- Runways
:- Taxiways
:- TACAN/ILS Freq
:- Entry/Exit points

=Pilot=

==Basic Section==

The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

===General===

====Radio/SRS====

* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

===Flying===

====Startup====
*According to Manual 18.1 Startup

====Takeoff====

====In-flight====
* Flying
:- Fly in Combat cruise formation at low-level profile.
:- Fly NOE as a single-ship in flat and open terrain.
:- Hover IGE and OGE
:- VRS Recovery

* Navigation
:- Visually navigate between two points using for example terrain objects as guidence (the compass and an empty F10 map may be used)
:- Follow several waypoints in succession (flightplan) using information provided by the in-cockpit instruments or projected on VSD/HSD.

* Trim/Autopilot
:- Force trim
:- Engage/Disengage:

* Fence In / Fence Out procedures

====Landing====

===Combat===

====Air-To-Air====
*ATAS Stingers
:-Engage enemy air targets without the use of MMS slaving.

====Air-To-Ground====
*Gun
:-Engaging soft armored targets with 0.50cal and lead tracers onto target.

*Rockets
:-Engage soft/light armored targets with HE 10pd or 17pd rockets and adjust fire from earlier impact.

*Missiles
:-Engage targets with APWKS
:-Engage targets with Hellfire

====Defence====
*CMWS
:-Set up CMWS for bypass or auto
*AN/APR-39 & AN/AVR-2
:-Understanding AN/APR-39 & AN/AVR-2 Radar and Laser warning systems symbols and sound alerts.

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

=Co-Pilot/Gunner=

==Basic Section==
The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

-MMS basic skills
-Storing targets
-Laser codes/lasing

===General===

====Radio/SRS====
* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

====MMS====

===Flying===

====Startup====
*According to Manual 18.1 Startup

====Takeoff====

====In-flight====
* Flying
:- Fly in Combat cruise formation at low-level profile.
:- Fly NOE as a single-ship in flat and open terrain.
:- Hover IGE and OGE
:- VRS Recovery

* Navigation
:- Visually navigate between two points using for example terrain objects as guidence (the compass and an empty F10 map may be used)
:- Follow several waypoints in succession (flightplan) using information provided by the in-cockpit instruments or projected on VSD/HSD.

* Trim/Autopilot
:- Force trim
:- Engage/Disengage:

* Fence In / Fence Out procedures

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

OH-58D Kiowa Syllabus

2025-03-30T16:28:59Z

Kingtiger45: /* Flying */

''[[Home]] >> [[Helicopter Syllabi]] >> [[OH-58D Kiowa Syllabus]]''

If not specified in the Syllabus all procedures are to be followed as described in the OH-58D. <pre style="color: red">"OH58D_User_Guide" can be found in the DCS installation folder "DCS World OpenBeta\Mods\aircraft\OH-58D\Doc"</pre>

If you are new to the MA-community, be sure to read about our procedures around the airfield (Linked below) to ensure everyone can have a safe training environment. Good luck and have fun!

* [http://wiki.masterarms.se/index.php/Airport_Procedures Airport procedures]
* [http://wiki.masterarms.se/index.php/Charts Airport charts]
:- Runways
:- Taxiways
:- TACAN/ILS Freq
:- Entry/Exit points

=Pilot=

==Basic Section==

The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

===General===

====Radio/SRS====

* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

===Flying===

====Startup====
*According to Manual 18.1 Startup

====Takeoff====

====In-flight====
* Flying
:- Fly in Combat cruise formation at low-level profile.
:- Fly NOE as a single-ship in flat and open terrain.
:- Hover IGE and OGE
:- VRS Recovery

* Navigation
:- Visually navigate between two points using for example terrain objects as guidence (the compass and an empty F10 map may be used)
:- Follow several waypoints in succession (flightplan) using information provided by the in-cockpit instruments or projected on VSD/HSD.

* Trim/Autopilot
:- Force trim
:- Engage/Disengage:

* Fence In / Fence Out procedures

====Landing====

===Combat===

====Air-To-Air====
*ATAS Stingers
:-Engage enemy air targets without the use of MMS slaving.

====Air-To-Ground====
*Gun
:-Engaging soft armored targets with 0.50cal and lead tracers onto target.

*Rockets
:-Engage soft/light armored targets with HE 10pd or 17pd rockets and adjust fire from earlier impact.

*Missiles
:-Engage targets with APWKS
:-Engage targets with Hellfire

====Defence====
*CMWS
:-Set up CMWS for bypass or auto
*AN/APR-39 & AN/AVR-2
:-Understanding AN/APR-39 & AN/AVR-2 Radar and Laser warning systems symbols and sound alerts.

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

=Co-Pilot/Gunner=

==Basic Section==
The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

-MMS basic skills
-Storing targets
-Laser codes/lasing

===General===

====Radio/SRS====
* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

===Flying===

====Startup====
*According to Manual 18.1 Startup

====Takeoff====

====In-flight====
* Flying
:- Fly in Combat cruise formation at low-level profile.
:- Fly NOE as a single-ship in flat and open terrain.
:- Hover IGE and OGE
:- VRS Recovery

* Navigation
:- Visually navigate between two points using for example terrain objects as guidence (the compass and an empty F10 map may be used)
:- Follow several waypoints in succession (flightplan) using information provided by the in-cockpit instruments or projected on VSD/HSD.

* Trim/Autopilot
:- Force trim
:- Engage/Disengage:

* Fence In / Fence Out procedures

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

OH-58D Kiowa Syllabus

2025-03-30T16:27:23Z

Kingtiger45: /* Basic Section */

''[[Home]] >> [[Helicopter Syllabi]] >> [[OH-58D Kiowa Syllabus]]''

If not specified in the Syllabus all procedures are to be followed as described in the OH-58D. <pre style="color: red">"OH58D_User_Guide" can be found in the DCS installation folder "DCS World OpenBeta\Mods\aircraft\OH-58D\Doc"</pre>

If you are new to the MA-community, be sure to read about our procedures around the airfield (Linked below) to ensure everyone can have a safe training environment. Good luck and have fun!

* [http://wiki.masterarms.se/index.php/Airport_Procedures Airport procedures]
* [http://wiki.masterarms.se/index.php/Charts Airport charts]
:- Runways
:- Taxiways
:- TACAN/ILS Freq
:- Entry/Exit points

=Pilot=

==Basic Section==

The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

===General===

====Radio/SRS====

* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

===Flying===

====Startup====
*According to Manual 18.1 Startup

====Takeoff====

====In-flight====
* Flying
:- Fly in Combat cruise formation at low-level profile.
:- Fly NOE as a single-ship in flat and open terrain.
:- Hover IGE and OGE
:- VRS Recovery

* Navigation
:- Visually navigate between two points using for example terrain objects as guidence (the compass and an empty F10 map may be used)
:- Follow several waypoints in succession (flightplan) using information provided by the in-cockpit instruments or projected on VSD/HSD.

* Trim/Autopilot
:- Force trim
:- Engage/Disengage:

* Fence In / Fence Out procedures

====Landing====

===Combat===

====Air-To-Air====
*ATAS Stingers
:-Engage enemy air targets without the use of MMS slaving.

====Air-To-Ground====
*Gun
:-Engaging soft armored targets with 0.50cal and lead tracers onto target.

*Rockets
:-Engage soft/light armored targets with HE 10pd or 17pd rockets and adjust fire from earlier impact.

*Missiles
:-Engage targets with APWKS
:-Engage targets with Hellfire

====Defence====
*CMWS
:-Set up CMWS for bypass or auto
*AN/APR-39 & AN/AVR-2
:-Understanding AN/APR-39 & AN/AVR-2 Radar and Laser warning systems symbols and sound alerts.

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

=Co-Pilot/Gunner=

==Basic Section==
The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

-MMS basic skills
-Storing targets
-Laser codes/lasing

===General===

====Radio/SRS====
* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

OH-58D Kiowa Syllabus

2025-03-30T16:25:42Z

Kingtiger45: /* Co-Pilot */

''[[Home]] >> [[Helicopter Syllabi]] >> [[OH-58D Kiowa Syllabus]]''

If not specified in the Syllabus all procedures are to be followed as described in the OH-58D. <pre style="color: red">"OH58D_User_Guide" can be found in the DCS installation folder "DCS World OpenBeta\Mods\aircraft\OH-58D\Doc"</pre>

If you are new to the MA-community, be sure to read about our procedures around the airfield (Linked below) to ensure everyone can have a safe training environment. Good luck and have fun!

* [http://wiki.masterarms.se/index.php/Airport_Procedures Airport procedures]
* [http://wiki.masterarms.se/index.php/Charts Airport charts]
:- Runways
:- Taxiways
:- TACAN/ILS Freq
:- Entry/Exit points

=Pilot=

==Basic Section==

The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

===General===

====Radio/SRS====

* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

====MFD====

INIT-Page

*PERFORMANCE DATA
:-Check/Set performance values used to perform "hover check"

*DATA LOADER
:- Load DTC (Data Cartridge)

VSD

*Differate between waypoint and MMS indicators

*Switch between next and previus point in flight plan
*Switch between flight plans

*Differate between barometric and radar altimeter indicators

HSD

*FLIGHT PLAN
:-Switch between next and previus point in flight plan

* Map navigation (HSD/RMS)
:- Setting heading/North
:- Toggle map types
:- Slew to WP
* Show/Hide information
* Symbology (Waypoints, NFZ, Hazards etc.)
* Points
:- Create new/Edit waypoint/Targetpoint/Checkpoint
:- Set “Direct To” to a waypoint

WPN-Page
*Settings for Rockets/APWKS
:-Program rocket pod for APWKS
:-Change A or B zone on rocket pod
*Settings for 0.50cal
:-Change ammount of 0.50cal ammunition
*Settings for hellfire
:-Toggle missile code
:-Change primary/secondary codes
:-Change missile per code

COMM-Page
:NIL

===Flying===

====Startup====
*According to Manual 18.1 Startup

====Takeoff====

====In-flight====
* Flying
:- Fly in Combat cruise formation at low-level profile.
:- Fly NOE as a single-ship in flat and open terrain.
:- Hover IGE and OGE
:- VRS Recovery

* Navigation
:- Visually navigate between two points using for example terrain objects as guidence (the compass and an empty F10 map may be used)
:- Follow several waypoints in succession (flightplan) using information provided by the in-cockpit instruments or projected on VSD/HSD.

* Trim/Autopilot
:- Force trim
:- Engage/Disengage:

* Fence In / Fence Out procedures

====Landing====

===Combat===

====Air-To-Air====
*ATAS Stingers
:-Engage enemy air targets without the use of MMS slaving.

====Air-To-Ground====
*Gun
:-Engaging soft armored targets with 0.50cal and lead tracers onto target.

*Rockets
:-Engage soft/light armored targets with HE 10pd or 17pd rockets and adjust fire from earlier impact.

*Missiles
:-Engage targets with APWKS
:-Engage targets with Hellfire

====Defence====
*CMWS
:-Set up CMWS for bypass or auto
*AN/APR-39 & AN/AVR-2
:-Understanding AN/APR-39 & AN/AVR-2 Radar and Laser warning systems symbols and sound alerts.

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

=Co-Pilot/Gunner=

==Basic Section==
The Basic Syllabus gives an overall picture of what is expected to be accomplished by our OH-58D pilots and CPG’s and should be seen as a minimum level of knowledge. The syllabus should be used to identify educational needs and help you set up training goals for the next sortie. When you can complete all parts of the syllabus without the need for external assistance, you should be well prepared to complete the Basic Qualification.

-MMS basic skills
-Storing targets
-Laser codes/lasing

===General===

====Radio/SRS====
* Set Transponder code in SRS as IFF is not modeled in OH-58D.
* Set frequency manually or presets and transmit/receive (SRS) on:
:- Radio 1 FM1
:- Radio 2 UHF
:- Radio 3 VHF
:- Radio 4 NOT IN USE
:- Radio 5 FM2
* Use intercom PTT (SRS)
* Basic [http://wiki.masterarms.se/index.php/Comms Comms] as part of a flight (not as lead)
* Listen to and understand ATIS Information.
:''*'' Recommended settings for SRS can be found [http://wiki.masterarms.se/index.php?title=Technical_Checklist#AH-64D_Apache here.]

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

==Advanced Section==

===General===

===Flying===

====Startup====

====Takeoff====

====In-flight====

====Landing====

===Combat===

====Air-To-Air====

====Air-To-Ground====

====Defence====

OH-58D Kiowa Syllabus

2025-03-30T16:23:36Z

Kingtiger45: /* Radio/SRS */

OH-58D Kiowa Syllabus

2025-03-30T16:20:48Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-30T16:19:11Z

Kingtiger45: /* Startup */

OH-58D Kiowa Syllabus

2025-03-30T16:16:09Z

Kingtiger45: /* In-flight */

OH-58D Kiowa Syllabus

2025-03-30T16:15:54Z

Kingtiger45: /* Air-To-Air */

OH-58D Kiowa Syllabus

2025-03-30T16:15:16Z

Kingtiger45: /* Defence */

OH-58D Kiowa Syllabus

2025-03-30T16:14:45Z

Kingtiger45: /* Defence */

OH-58D Kiowa Syllabus

2025-03-30T16:10:30Z

Kingtiger45: /* Air-To-Ground */

OH-58D Kiowa Syllabus

2025-03-30T16:07:56Z

Kingtiger45: /* In-flight */

OH-58D Kiowa Syllabus

2025-03-30T15:55:41Z

Kingtiger45: /* Air-To-Air */

OH-58D Kiowa Syllabus

2025-03-30T15:55:03Z

Kingtiger45: /* In-flight */

OH-58D Kiowa Syllabus

2025-03-30T15:52:12Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-30T15:52:02Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-29T10:28:38Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-23T14:04:44Z

Kingtiger45: /* Basic Section */

OH-58D Kiowa Syllabus

2025-03-22T16:29:36Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-22T16:28:43Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-22T16:28:18Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-22T16:20:40Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-22T16:16:10Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-22T16:14:27Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-22T16:06:11Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-22T16:04:40Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-22T16:03:09Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-22T16:02:20Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-22T16:01:16Z

Kingtiger45: /* MFD */

OH-58D Kiowa Syllabus

2025-03-22T15:56:59Z

Kingtiger45: /* MFD */