SOURCE DCS WIKI - Recent changes [en]

How To Read Charts

Iceman1 1 — Thu, 30 Apr 2026 00:00:22 GMT

← Older revision		Revision as of 00:00, 30 April 2026
Line 22:		Line 22:
	- Reference (REF) Charts		- Reference (REF) Charts

	== ~~Standart~~ terminal Arrival (STAR) Charts ==		== Standard terminal Arrival (STAR) Charts ==
	STAR Charts feature informations about multiple Arrival routes to an specific Aerodrome. Along with that, they contain informations about how the routes are to be flown and how the reader can perform the required actions. Arrivals in general lead the Pilots into the following approach. They also give hints about the enviroment and continious NOTAMS		STAR Charts feature informations about multiple Arrival routes to an specific Aerodrome. Along with that, they contain informations about how the routes are to be flown and how the reader can perform the required actions. Arrivals in general lead the Pilots into the following approach. They also give hints about the enviroment and continious NOTAMS
	[[File:RAF Akrotiri.png\|thumb\|1071x1071px\|Example Chart RAF Akrotiri\|border]]The given example is an arrival chart for RAF Akrotiri. It contains informations for the ANANE ALPHA, IREA ALPHA, and the MEZUS ALPHA Arrival. The name of an arrival route is about its first leg or in other words its entry leg.		[[File:RAF Akrotiri.png\|thumb\|1071x1071px\|Example Chart RAF Akrotiri\|border]]The given example is an arrival chart for RAF Akrotiri. It contains informations for the ANANE ALPHA, IREA ALPHA, and the MEZUS ALPHA Arrival. The name of an arrival route is about its first leg or in other words its entry leg.

Main Page

Iceman1 1 — Wed, 29 Apr 2026 23:59:25 GMT

← Older revision		Revision as of 23:59, 29 April 2026
Line 32:		Line 32:
	'''IN CASE OF DOUBT USE PLAIN LANGUAGE'''		'''IN CASE OF DOUBT USE PLAIN LANGUAGE'''

	[[General/Tactical Communication\|Tactical Communication]] · [[General/CATC Communications Guide\|CATC Communications Guide]] · [[General/Air Traffic Communication\|Airfield Communications]] · [[DDFORM1801\|Filing Flight Plans]]		[[General/Tactical Communication\|Tactical Communication]] · [[General/CATC Communications Guide\|CATC Communications Guide]] · [[General/Air Traffic Communication\|Airfield Communications]] · [[DDFORM1801\|Filing Flight Plans]] · [[How To Read Charts]]

	----		----

How To Read Charts

Iceman1 1 — Wed, 29 Apr 2026 23:57:47 GMT

@@ Line 23: / Line 23: @@
 == Standart terminal Arrival (STAR) Charts ==
-STAR Charts feature informations about multiple Arrival routes to an specific Aerodrome. Along with that, they contain informations about how the routes are to be flown and how the reader can perform the required actions. Arrivals in general lead the Pilots into the floowing approach. They also give hints about the enviroment and continious NOTAMS
+STAR Charts feature informations about multiple Arrival routes to an specific Aerodrome. Along with that, they contain informations about how the routes are to be flown and how the reader can perform the required actions. Arrivals in general lead the Pilots into the following approach. They also give hints about the enviroment and continious NOTAMS
 [[File:RAF Akrotiri.png|thumb|1071x1071px|Example Chart RAF Akrotiri|border]]The given example is an arrival chart for RAF Akrotiri. It contains informations for the ANANE ALPHA, IREA ALPHA, and the MEZUS ALPHA Arrival. The name of an arrival route is about its first leg or in other words its entry leg.
@@ Line 33: / Line 33: @@
 At last there is the Airport elevations MSL in ft. (ex. 75 ft. MSL)

File:Navigraph Charts 26.04.2026 20 19 13.png

Iceman1 1 — Wed, 29 Apr 2026 23:07:20 GMT

Iceman1 1 uploaded File:Navigraph Charts 26.04.2026 20 19 13.png

New page

adafwas

How To Read Charts

Iceman1 1 — Wed, 29 Apr 2026 22:41:07 GMT

← Older revision		Revision as of 22:41, 29 April 2026
(One intermediate revision by the same user not shown)
Line 21:		Line 21:

	- Reference (REF) Charts		- Reference (REF) Charts

			== Standart terminal Arrival (STAR) Charts ==
			STAR Charts feature informations about multiple Arrival routes to an specific Aerodrome. Along with that, they contain informations about how the routes are to be flown and how the reader can perform the required actions. Arrivals in general lead the Pilots into the floowing approach. They also give hints about the enviroment and continious NOTAMS
			[[File:RAF Akrotiri.png\|thumb\|1071x1071px\|Example Chart RAF Akrotiri\|border]]The given example is an arrival chart for RAF Akrotiri. It contains informations for the ANANE ALPHA, IREA ALPHA, and the MEZUS ALPHA Arrival. The name of an arrival route is about its first leg or in other words its entry leg.

			Startet from the actual top, which in the example is the right side each chart has the Airports ICAO code its related to in its upper left corner, The day of publishment in the center and the full name and country in the upper right corner.

			Below the firs line of information from left to right the chart contains informations about the ATIS Frequency (ex. 125.0)

			Followed by the Approach Frequency (ex. 123.6) and the frequencys of the sorrounding centers (ex. NICOSIA CONTROL WEST and EAST)

			At last there is the Airport elevations MSL in ft. (ex. 75 ft. MSL)

File:RAF Akrotiri.png

Iceman1 1 — Wed, 29 Apr 2026 22:20:20 GMT

Iceman1 1 uploaded File:RAF Akrotiri.png

New page

fafa

How To Read Charts

Iceman1 1 — Wed, 29 Apr 2026 22:10:04 GMT

Created page with "== Charts == An '''aeronautical chart''' is a map designed to assist in the navigation of aircraft, much as nautical charts do for watercraft, or a roadmap does for drivers. Using these charts and other tools, pilots are able to determine their position, safe altitude, best route to a destination, navigation aids along the way, alternative landing areas in case of an in-flight emergency, and other useful information such as radio frequencies and airspace boundaries. Ther..."

New page

== Charts ==
An '''aeronautical chart''' is a map designed to assist in the navigation of aircraft, much as nautical charts do for watercraft, or a roadmap does for drivers. Using these charts and other tools, pilots are able to determine their position, safe altitude, best route to a destination, navigation aids along the way, alternative landing areas in case of an in-flight emergency, and other useful information such as radio frequencies and airspace boundaries. There are charts for all land masses on Earth, and long-distance charts for trans-oceanic travel.

Specific charts are used for each phase of a flight and may vary from a map of a particular airport facility to an overview of the instrument routes covering an entire continent (e.g., global navigation charts), and many types in between.

Visual flight charts are categorized according to their scale, which is proportional to the size of the area covered by one map. The amount of detail is necessarily reduced when larger areas are represented on a map.

* World aeronautical charts (WACs) have a scale of 1:1,000,000 and cover relatively large areas. Outside of WAC coverage, operational navigation charts (ONC) may be used. They use the same scale as WACs, but omit some useful information such as airspace restrictions.
* Sectional charts typically cover a total area of about 340x340 miles, printed on both sides of the map. The scale is 1:500,000.
* VFR terminal area charts are created with a scale and coverage appropriate for the general vicinity of a large airport (1:250,000). They may depict preferred VFR flight routes within areas of congested airspace.

Each Aerodrome has it´s own charts refering to specialized local procedures such as Taxing, Departing, Arriving and Approaching. According to the mentioned topics, Airport Charts can be devided into four to five catagories:

- Standard Terminal Arrival (STAR) Charts

- Approach (APP) Charts

- TAXI Charts

- Standard Instrument Departure (SID) Charts

- Reference (REF) Charts

DDFORM1801

Niknam3 — Wed, 29 Apr 2026 15:54:53 GMT

Example 1 — 4-Ship IFR ACM Sortie

← Older revision		Revision as of 15:54, 29 April 2026
Line 256:		Line 256:
	\| Equipment \|\| <code>ITUV/C</code> \|\| Standard fit		\| Equipment \|\| <code>ITUV/C</code> \|\| Standard fit
	\|-		\|-
	\| Departure \|\| <code>LTAG1530</code> \|\| Incirlik, ~~departure~~-~~time~~ 15:30Z		\| Departure \|\| <code>LTAG1530</code> \|\| Incirlik, block-out 15:30Z
	\|-		\|-
	\| Speed/Level \|\| <code>N0420F120</code> \|\| 420 kt TAS, FL120		\| Speed/Level \|\| <code>N0420F120</code> \|\| 420 kt TAS, FL120
Line 270:		Line 270:
	\| Formation \|\| <code>FFLT SHADW11–14 FFLTEND</code> \|\| 4 aircraft listed		\| Formation \|\| <code>FFLT SHADW11–14 FFLTEND</code> \|\| 4 aircraft listed
	\|-		\|-
	\| Stay area \|\| <code>STAYINFO1/AREA LTR1 GND FL660 FOR ACM RUBIK0010 RUBIK0110</code> \|\| LTR1 area, surface to FL660, ACM, ~~00:10–01:10Z~~ relative to ~~block~~-~~out~~		\| Stay area \|\| <code>STAYINFO1/AREA LTR1 GND FL660 FOR ACM RUBIK0010 RUBIK0110</code> \|\| LTR1 area, surface to FL660, ACM, 0010–0110 relative to departure-time
	\|}		\|}

DDFORM1801

Pi lot se — Wed, 29 Apr 2026 15:52:55 GMT

Example 1 — 4-Ship IFR ACM Sortie

← Older revision		Revision as of 15:52, 29 April 2026
Line 256:		Line 256:
	\| Equipment \|\| <code>ITUV/C</code> \|\| Standard fit		\| Equipment \|\| <code>ITUV/C</code> \|\| Standard fit
	\|-		\|-
	\| Departure \|\| <code>LTAG1530</code> \|\| Incirlik, ~~block~~-~~out~~ 15:30Z		\| Departure \|\| <code>LTAG1530</code> \|\| Incirlik, departure-time 15:30Z
	\|-		\|-
	\| Speed/Level \|\| <code>N0420F120</code> \|\| 420 kt TAS, FL120		\| Speed/Level \|\| <code>N0420F120</code> \|\| 420 kt TAS, FL120

Main Page

Niknam3 — Tue, 28 Apr 2026 17:37:20 GMT

← Older revision		Revision as of 17:37, 28 April 2026
Line 32:		Line 32:
	'''IN CASE OF DOUBT USE PLAIN LANGUAGE'''		'''IN CASE OF DOUBT USE PLAIN LANGUAGE'''

	[[General/Tactical Communication\|Tactical Communication]] · [[General/CATC Communications Guide\|CATC Communications Guide]] · [[General/Air Traffic Communication\|Airfield Communications]] · [[~~DDFORM175~~\|Filing Flight Plans]]		[[General/Tactical Communication\|Tactical Communication]] · [[General/CATC Communications Guide\|CATC Communications Guide]] · [[General/Air Traffic Communication\|Airfield Communications]] · [[DDFORM1801\|Filing Flight Plans]]

	----		----

DDFORM1801

Niknam3 — Tue, 28 Apr 2026 17:36:57 GMT

← Older revision		Revision as of 17:36, 28 April 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:Filing a DoD International Flight Plan (DD Form 1801)}}		{{DISPLAYTITLE:Filing a DoD International Flight Plan (DD Form 1801)}}
	~~[[Category:Procedures]]~~
	~~[[Category:Navigation]]~~
	~~[[Category:Pilot Resources]]~~

	= Filing a DoD International Flight Plan (DD Form 1801) =		= Filing a DoD International Flight Plan (DD Form 1801) =
Line 361:		Line 358:
	-DOF/[YYMMDD] OPR/DOD REG/TBN STS/STATE RMK/OAT [FFLT ... FFLTEND] MDCN PERM [NUMBER] FUEL[HHMM] POB[N] STAYINFO1/[DESCRIPTION])		-DOF/[YYMMDD] OPR/DOD REG/TBN STS/STATE RMK/OAT [FFLT ... FFLTEND] MDCN PERM [NUMBER] FUEL[HHMM] POB[N] STAYINFO1/[DESCRIPTION])
	</pre>		</pre>

	~~== See Also ==~~

	* [[ATC Procedures — Turkish FIR]]
	* [[STAY and STAYINFO Procedures]]
	* [[Formation Flight Filing]]
	* [[OAT Flight Rules]]

	== References ==		== References ==
Line 374:		Line 364:
	* ICAO Doc 8643 — Aircraft Type Designators		* ICAO Doc 8643 — Aircraft Type Designators
	* DoD FLIP General Planning		* DoD FLIP General Planning
	* DD Form 1801 Field Specification ([[DD Form 1801 Field Spec]])		* DD Form 1801 Field Specification ([https://skybrary.aero/articles/flight-plan-completion DD Form 1801 Field Spec])

DDFORM1801

Niknam3 — Tue, 28 Apr 2026 17:35:49 GMT

Created page with "{{DISPLAYTITLE:Filing a DoD International Flight Plan (DD Form 1801)}} Category:Procedures Category:Navigation Category:Pilot Resources = Filing a DoD International Flight Plan (DD Form 1801) = This article explains how to correctly fill out the DD Form 1801 / ICAO FPL message used for all cross-border and controlled airspace operations. Read this before filing your first plan — a malformed FPL will be rejected by ATC and may delay or ground your flight...."

New page

{{DISPLAYTITLE:Filing a DoD International Flight Plan (DD Form 1801)}}
[[Category:Procedures]]
[[Category:Navigation]]
[[Category:Pilot Resources]]

= Filing a DoD International Flight Plan (DD Form 1801) =

This article explains how to correctly fill out the DD Form 1801 / ICAO FPL message used for all cross-border and controlled airspace operations. Read this before filing your first plan — a malformed FPL will be rejected by ATC and may delay or ground your flight.

== Overview ==

The DD Form 1801 generates an ICAO-format '''FPL message''' — a structured string of fields separated by dashes that gets transmitted to ATC. Every field has strict formatting rules. The form handles the formatting for you, but you still need to know what goes where and why.

A complete FPL message looks like this:

<pre>
(FPL-[callsign]-[rules][type]
-[number]/[actype]/[WTC]
-[equipment]/[transponder]
-[departure][time]
-[speed][level] [route]
-[destination][EET] [alternate]
-[field 18])
</pre>

== Field-by-Field Guide ==

=== Field 7 — Aircraft Identification (Callsign) ===

Your '''mission callsign''', up to 7 alphanumeric characters, no spaces.

{| class="wikitable"
! Format !! Example !! Notes
|-
| Up to 7 alphanumeric chars || <code>SHADW11</code> || Formation lead uses flight callsign
|}

For a 4-ship, all aircraft file under the '''lead's callsign''' (<code>SHADW11</code>). Wingmen are not filed separately unless splitting.

=== Field 8 — Flight Rules / Type of Flight ===

Two characters, written together (e.g. <code>IM</code>, <code>VM</code>).

'''Flight Rules (first character):'''

{| class="wikitable"
! Code !! Meaning !! When to use
|-
| <code>I</code> || IFR || En-route in controlled airspace, IMC, or above transition altitude
|-
| <code>V</code> || VFR || Visual, low-level, uncontrolled airspace
|-
| <code>Y</code> || IFR → VFR || Departs IFR, transitions to VFR en route
|-
| <code>Z</code> || VFR → IFR || Departs VFR, picks up IFR clearance en route
|}

'''Type of Flight (second character):'''

{| class="wikitable"
! Code !! Meaning
|-
| <code>M</code> || Military
|-
| <code>S</code> || Scheduled Air Transport
|-
| <code>G</code> || General Aviation
|-
| <code>X</code> || Other
|}

All SHADW flights use <code>M</code>. Flight rules depend on the mission profile — see the examples below.

=== Field 9 — Number / Aircraft Type / Wake Turbulence Category ===

Format: <code>[number]/[type]/[WTC]</code>

{| class="wikitable"
! Sub-field !! Format !! Example !! Notes
|-
| Number of aircraft || Integer 1–99 || <code>4</code> || Formation size. Solo = <code>1</code>
|-
| Aircraft type || ICAO designator (2–4 chars) || <code>F16</code> || Per ICAO Doc 8643
|-
| Wake turbulence category || Single letter || <code>M</code> || L / M / H / J
|}

F-16 is always <code>F16/M</code> (Medium).

=== Field 10 — Equipment / Transponder ===

Format: <code>[equipment]/[transponder]</code>

Standard SHADW configuration is <code>ITUV/C</code>:

{| class="wikitable"
! Code !! Meaning
|-
| <code>I</code> || Inertial navigation
|-
| <code>T</code> || TACAN
|-
| <code>U</code> || UHF radio
|-
| <code>V</code> || VHF radio
|-
| <code>C</code> || Transponder Mode C (altitude reporting)
|}

Do not change this unless maintenance has confirmed a system is inoperative, in which case remove the relevant letter and add <code>STS/HOSP</code> or a RMK as appropriate.

=== Field 13 — Departure Aerodrome / Time ===

Format: <code>[ICAO][HHMM]</code> — no space, no separator.

{| class="wikitable"
! Sub-field !! Format !! Example !! Notes
|-
| Departure aerodrome || 4-letter ICAO code || <code>LTAG</code> || Incirlik AB
|-
| Departure time || HHMM UTC || <code>1530</code> || Block-out time, not wheels-up
|}

Always use '''UTC'''. Never local time.

=== Field 15 — Cruising Speed / Level / Route ===

This field has three parts written together: <code>[speed][level] [route]</code>

==== Speed ====

{| class="wikitable"
! Prefix !! Unit !! Example !! Meaning
|-
| <code>N</code> || Knots TAS || <code>N0420</code> || 420 kt TAS
|-
| <code>K</code> || km/h || <code>K0780</code> || 780 km/h TAS
|-
| <code>M</code> || Mach || <code>M082</code> || Mach 0.82
|}

==== Level ====

{| class="wikitable"
! Prefix !! Unit !! Example !! Meaning
|-
| <code>F</code> || Flight Level || <code>F120</code> || FL120 (12,000 ft, altimeter set to std)
|-
| <code>A</code> || Altitude (hundreds of ft) || <code>A025</code> || 2,500 ft MSL (QNH)
|-
| <code>S</code> || Standard metric level || <code>S1130</code> || (rare, used in some regions)
|}

'''F vs A:''' Use <code>F</code> when flying above the transition altitude (on standard pressure). Use <code>A</code> when flying below it on QNH. In Turkish airspace the transition altitude is typically 3,000 ft AMSL / FL050 — check current AIP.

==== Route ====

Space-separated routing elements after the speed/level. Common elements:

{| class="wikitable"
! Element !! Meaning !! Example
|-
| <code>DCT</code> || Direct to next fix || <code>DCT DAN</code>
|-
| Airway designator || Follow named airway || <code>AG105</code>
|-
| Waypoint name || 5-letter ICAO fix || <code>RUBIK</code>
|-
| <code>fix/speed level</code> || Speed/level change at fix || <code>RUBIK/N0420F120</code>
|-
| <code>STAYn/HHMM</code> || Holding/loiter at previous fix for duration || <code>STAY1/0100</code>
|}

'''<code>STAY</code> items''' are critical for training events. <code>STAY1/0100</code> means "hold/remain in the area of the preceding fix for 1 hour." The number after STAY is an index (1, 2, 3…) used to cross-reference <code>STAYINFO</code> in Field 18.

=== Field 16 — Destination / EET / Alternates ===

Format: <code>[destination][EET] [alternate] [2nd alternate]</code>

{| class="wikitable"
! Sub-field !! Format !! Example !! Notes
|-
| Destination || 4-letter ICAO || <code>LTAG</code> || Can be same as departure for closed patterns
|-
| Total EET || HHMM || <code>0120</code> || Estimated elapsed time departure→destination
|-
| Alternate || 4-letter ICAO || <code>LTAJ</code> || Diyarbakır. Required if weather/fuel rules apply
|-
| 2nd Alternate || 4-letter ICAO || (optional) ||
|}

=== Field 18 — Other Information ===

Free-text field with <code>INDICATOR/value</code> pairs, space-separated. Use <code>0</code> (zero) if nothing to declare.

'''Standard SHADW indicators:'''

{| class="wikitable"
! Indicator !! Format !! Example !! Meaning
|-
| <code>DOF/</code> || YYMMDD || <code>DOF/260428</code> || Date of flight — 28 April 2026
|-
| <code>OPR/</code> || Free text || <code>OPR/DOD</code> || Operating agency
|-
| <code>REG/</code> || Alphanumeric || <code>REG/TBN</code> || Aircraft registration. Use <code>TBN</code> (To Be Notified) for military
|-
| <code>STS/</code> || Code || <code>STS/STATE</code> || State aircraft — grants diplomatic overflight status
|-
| <code>RMK/</code> || Free text || see below || Remarks — used extensively for DoD-specific data
|}

'''<code>RMK/</code> sub-fields used in SHADW plans:'''

{| class="wikitable"
! Tag !! Example !! Meaning
|-
| <code>OAT</code> || <code>OAT</code> || Operational Air Traffic — identifies this as a military OAT flight
|-
| <code>FFLT ... FFLTEND</code> || <code>FFLT SHADW11 SHADW12 SHADW13 SHADW14 FFLTEND</code> || Formation flight membership list. List all callsigns between tags.
|-
| <code>MDCN</code> || <code>MDCN</code> || Medical clearance confirmed
|-
| <code>PERM</code> || <code>PERM 265501</code> || Diplomatic overflight permission number
|-
| <code>FUEL</code> || <code>FUEL0130</code> || Fuel endurance in HHMM
|-
| <code>POB</code> || <code>POB4</code> || Persons on board (integer, no space)
|-
| <code>STAYINFO</code> || <code>STAYINFO1/AREA LTR1 GND FL660 FOR ACM RUBIK0010 RUBIK0110</code> || Describes the STAY1 area/activity. Index matches STAYn in Field 15.
|}

<code>STAYINFO</code> format: <code>STAYINFOn/[free text description]</code>. The description should include the area name/block, vertical limits, activity type, and time window where applicable.

== Worked Examples ==

=== Example 1 — 4-Ship IFR ACM Sortie ===

<pre>
(FPL-SHADW11-IM
-4/F16/M
-ITUV/C
-LTAG1530
-N0420F120 AG105 DAN DCT RUBIK/N0420F120 STAY1/0100 RUBIK/N0420F110 DCT DAN DCT
-LTAG0120 LTAJ
-DOF/260428 OPR/DOD REG/TBN STS/STATE RMK/OAT FFLT SHADW11 SHADW12 SHADW13 SHADW14 FFLTEND MDCN PERM 265501 FUEL0130 POB4 STAYINFO1/AREA LTR1 GND FL660 FOR ACM RUBIK0010 RUBIK0110)
</pre>

'''Breakdown:'''

{| class="wikitable"
! Field !! Value !! Explanation
|-
| Callsign || <code>SHADW11</code> || Formation lead
|-
| Rules/Type || <code>IM</code> || IFR, Military
|-
| Aircraft || <code>4/F16/M</code> || 4-ship, F-16, Medium WTC
|-
| Equipment || <code>ITUV/C</code> || Standard fit
|-
| Departure || <code>LTAG1530</code> || Incirlik, block-out 15:30Z
|-
| Speed/Level || <code>N0420F120</code> || 420 kt TAS, FL120
|-
| Route || <code>AG105 DAN DCT RUBIK/N0420F120 STAY1/0100 RUBIK/N0420F110 DCT DAN DCT</code> || Depart via airway AG105 to DAN, direct RUBIK; hold at RUBIK for 1 hr at FL120; exit RUBIK at FL110, direct DAN, then direct back
|-
| Destination || <code>LTAG0120</code> || Return Incirlik, EET 1h20
|-
| Alternate || <code>LTAJ</code> || Diyarbakır
|-
| DOF || <code>260428</code> || 28 Apr 2026
|-
| Formation || <code>FFLT SHADW11–14 FFLTEND</code> || 4 aircraft listed
|-
| Stay area || <code>STAYINFO1/AREA LTR1 GND FL660 FOR ACM RUBIK0010 RUBIK0110</code> || LTR1 area, surface to FL660, ACM, 00:10–01:10Z relative to block-out
|}

=== Example 2 — Solo VFR Approach Practice ===

<pre>
(FPL-SHADW11-VM
-1/F16/M
-ITUV/C
-LTAG1530
-N0420A025 DCT DAN/N0420A025 STAY1/0100 DAN/N0420A025 DCT
-LTAG0105 LTAJ
-DOF/260428 OPR/DOD REG/TBN STS/STATE RMK/OAT MDCN PERM 265501 FUEL0130 POB1 STAYINFO1/MULT APCH AT LTAG)
</pre>

'''Key differences from Example 1:'''

{| class="wikitable"
! Field !! Value !! Why it differs
|-
| Rules/Type || <code>VM</code> || '''VFR''' — this sortie is flown VMC below transition altitude
|-
| Aircraft count || <code>1</code> || Solo — no FFLT block needed in RMK
|-
| Level || <code>A025</code> || '''Altitude 2,500 ft''' on QNH, not a flight level — appropriate below transition
|-
| Route || <code>DCT DAN STAY1/0100 DAN DCT</code> || Direct to DAN, hold 1 hr, return direct
|-
| STAYINFO || <code>MULT APCH AT LTAG</code> || Multiple approaches at Incirlik during hold period
|}

=== Example 3 — Solo IFR Approach Practice ===

<pre>
(FPL-SHADW11-IM
-1/F16/M
-ITUV/C
-LTAG1530
-N0420A050 DCT DAN/N0420A050 STAY1/0100 DAN/N0420A050 DCT
-LTAG0105 LTAJ
-DOF/260428 OPR/DOD REG/TBN STS/STATE RMK/OAT MDCN PERM 265501 FUEL0130 POB1 STAYINFO1/MULT APCH AT LTAG)
</pre>

'''Key differences from Example 2:'''

{| class="wikitable"
! Field !! Value !! Why it differs
|-
| Rules/Type || <code>IM</code> || '''IFR''' — same profile but flown under instrument rules
|-
| Level || <code>A050</code> || '''Altitude 5,000 ft''' on QNH — higher block required for IFR separation
|}

'''IFR vs VFR approach practice:''' Both Examples 2 and 3 are the same mission (multiple approaches at LTAG), but the flight rules code and requested altitude differ. IFR requires a higher block for approach sequencing. Choose based on actual met conditions and whether you need an instrument clearance.

== Common Mistakes ==

{| class="wikitable"
! Mistake !! Correct practice
|-
| Using local time in Fields 13 / EET || Always UTC. <code>1530</code> means 15:30Z.
|-
| Filing <code>F</code> level below transition altitude || Use <code>A</code> (altitude on QNH) below transition. Use <code>F</code> (flight level) above.
|-
| Omitting <code>FFLT...FFLTEND</code> for a formation || Required for any multi-ship. ATC needs the full call list.
|-
| Leaving <code>STAYINFO</code> vague || Include area name, vertical limits, activity, and local time window.
|-
| Forgetting <code>DOF/</code> in Field 18 || Always include. Some ATSU systems reject plans without it.
|-
| <code>POB</code> not matching formation count || <code>POB4</code> for a 4-ship (one pilot per aircraft). Adjust for two-seat variants.
|-
| Using local registration for military jets || Use <code>REG/TBN</code> unless a specific tail number is required.
|}

== Quick Reference — SHADW Standard Template ==

Copy and adapt for each sortie. Replace values in <code>[brackets]</code>.

<pre>
(FPL-[CALLSIGN]-[RULES]M
-[N]/F16/M
-ITUV/C
-LTAG[HHMM]
-N0420[LEVEL] [ROUTE] STAY1/[HHMM] [FIX]/N0420[LEVEL] DCT
-LTAG[EET] LTAJ
-DOF/[YYMMDD] OPR/DOD REG/TBN STS/STATE RMK/OAT [FFLT ... FFLTEND] MDCN PERM [NUMBER] FUEL[HHMM] POB[N] STAYINFO1/[DESCRIPTION])
</pre>

== See Also ==

* [[ATC Procedures — Turkish FIR]]
* [[STAY and STAYINFO Procedures]]
* [[Formation Flight Filing]]
* [[OAT Flight Rules]]

== References ==

* ICAO Doc 4444 — PANS-ATM, Appendix 2 (FPL format)
* ICAO Doc 8643 — Aircraft Type Designators
* DoD FLIP General Planning
* DD Form 1801 Field Specification ([[DD Form 1801 Field Spec]])

Incirlic Air Base

Niknam3 — Tue, 28 Apr 2026 10:49:54 GMT

Local Training Area

← Older revision		Revision as of 10:49, 28 April 2026
Line 221:		Line 221:
	\|LTD-19		\|LTD-19
	\|NO FLY AREA		\|NO FLY AREA
	~~suface~~ to unlimited		surface to unlimited
	\|-		\|-
	\|Square		\|Square

Server Info/Airfields

Iceman1 1 — Sun, 26 Apr 2026 18:16:08 GMT

← Older revision		Revision as of 18:16, 26 April 2026
Line 5:		Line 5:

	On the server, İncirlik functions as a major coalition base offering full ground services, a controlled airfield environment, and both VFR and IFR approach options. For detailed procedures including startup, taxi, departure, arrival, and pattern operations, see [[Incirlic Air Base]]		On the server, İncirlik functions as a major coalition base offering full ground services, a controlled airfield environment, and both VFR and IFR approach options. For detailed procedures including startup, taxi, departure, arrival, and pattern operations, see [[Incirlic Air Base]]

			For Charts see https://polybox.ethz.ch/index.php/s/GC3LqQtentcgYFs?path=%2FCharts%2FINCIRLIC%20LTAG

Incirlic Air Base

Niknam3 — Sun, 26 Apr 2026 11:43:40 GMT

FREQUENCYS

← Older revision		Revision as of 11:43, 26 April 2026
Line 507:		Line 507:
	\|		\|
	\|8-10		\|8-10
			\|-
			\|Tankers
			\|
			\|11-14
	\|-		\|-
	\|Unit Option		\|Unit Option
	\|		\|
	\|11-20		\|15-20
	\|}		\|}

Main Page

Niknam3 — Sat, 25 Apr 2026 15:28:42 GMT

← Older revision		Revision as of 15:28, 25 April 2026
Line 22:		Line 22:
	New to SOURCE? Complete all onboarding steps before your first operation. Install required software, read the rules of engagement, and familiarise yourself with communications procedures.		New to SOURCE? Complete all onboarding steps before your first operation. Install required software, read the rules of engagement, and familiarise yourself with communications procedures.

	[[Guides/New Member Guide\|New Member Guide]] · [[Guides/SRS Setup\|SRS Setup]] · [[Guides/Mod Installation\|Mod Installation]]		[[Guides/New Member Guide\|New Member Guide]] · [[Guides/SRS Setup\|SRS Setup]] · [[Guides/Mod Installation\|Mod Installation]]

	----		----

Guides/Mod Installation

Niknam3 — Sat, 25 Apr 2026 11:08:10 GMT

← Older revision		Revision as of 11:08, 25 April 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	== ~~How~~ to ~~install~~ Mods ==		= Mod Installation Guide =

			This guide walks you through installing the required mods for our operations.

			== Installation ==

			# Go to the [https://polybox.ethz.ch/index.php/s/S8Es6KCzBao5WYm?path=%2FMods%2FOperation%20Inherent%20Resolve%20Mods Polybox]
			# Download the <code>tech</code> folder.
			# Unzip the downloaded archive.
			# Open your '''DCS Saved Games''' folder.
			# Open the <code>Mods</code> subfolder inside it.
			# Add the contents of the newly downloaded tech folder to your existing <code>tech</code> folder.

			=== Folder Structure ===

			Make sure the folder structure looks exactly like this - no nested folders:

			<pre>
			Mods/
			└── Tech/
			├── Mod1/
			└── Mod2/
			</pre>

			If there is an extra layer of folders inside <code>Tech</code>, something went wrong during extraction - move the contents up one level.

			== Need Help? ==

			If you run into any issues, contact any staff member in Discord and they'll get you sorted.

Guides/New Member Guide

Niknam3 — Sat, 25 Apr 2026 11:04:13 GMT

← Older revision		Revision as of 11:04, 25 April 2026
Line 29:		Line 29:

	Make sure you have read the briefing before joining the server for an event.		Make sure you have read the briefing before joining the server for an event.

			== TRAINING ==
			You can track your training on our training Page

			* [https://sourcedcs.page/skills.html Training Overview]

	== Weekly Events ==		== Weekly Events ==

Guides/New Member Guide

Niknam3 — Sat, 25 Apr 2026 11:02:04 GMT

Created page with "= New Members Guide = Welcome to the group! This page gives you a quick overview of how things work, where to find information, and what you need to get started. Feel free to jump to whichever section is most relevant to you. __TOC__ == Getting Set Up == Before joining the server or attending any events, make sure you have the required mods and SRS installed and configured. * '''Required Mods:''' → Mod Installation Guide * '''SRS:''' ..."

New page

= New Members Guide =

Welcome to the group! This page gives you a quick overview of how things work, where to find information, and what you need to get started. Feel free to jump to whichever section is most relevant to you.

__TOC__

== Getting Set Up ==

Before joining the server or attending any events, make sure you have the required mods and SRS installed and configured.

* '''Required Mods:''' [[Guides/Mod Installation|→ Mod Installation Guide]]
* '''SRS:''' [[Guides/SRS Setup|→ SRS Installation & Setup Guide]]

== The Training Server ==

Our training server is the place to practice, familiarise yourself with procedures, and find official documentation. SOPs — including the LTAG SOPs — are available directly on the server.

=== Flight Plans ===

Whenever the server is controlled, file a flight plan.

* [[DDFORM175|→ How to File a Flight Plan]]

== Missions & Briefings ==

Mission briefings are hosted on the ATO Brief website. Before any event, check there for the current ATO, tasking, and relevant mission information.

* [https://ato.sourcedcs.page → ATO Brief]

Make sure you have read the briefing before joining the server for an event.

== Weekly Events ==

We run events on a weekly basis. All events are announced in Discord.

* To sign up, click '''Interested''' on the Discord event post.
* If you can no longer make it, '''text someone''' to let the team know in advance — don't just not show up.

== Where to Find Help ==

If you have questions not covered here, the best place to ask is in the relevant Discord channel. If you're unsure who to contact, reach out to any of the staff members — someone will point you in the right direction.

[[Category:Guides]]
[[Category:Onboarding]]

DDFORM175

Niknam3 — Sat, 25 Apr 2026 11:01:21 GMT

DD Form 175 — Military Flight Plan

← Older revision		Revision as of 11:01, 25 April 2026
Line 2:		Line 2:

	''How to file a military flight plan''		''How to file a military flight plan''

			[https://sourcedcs.page/flightplan.html File a Flight Plan]

	== 1. Overview ==		== 1. Overview ==

Guides/Mod Installation

Niknam3 — Sat, 25 Apr 2026 10:59:23 GMT

Created page with "== How to install Mods =="

New page

== How to install Mods ==

Guides/SRS Setup

Niknam3 — Sat, 25 Apr 2026 10:40:13 GMT

Show changes

DDFORM175

Niknam3 — Sat, 25 Apr 2026 10:30:31 GMT

← Older revision		Revision as of 10:30, 25 April 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	= DD Form 175 — Military Flight Plan =		= DD Form 175 — Military Flight Plan =

	''How to file a military flight plan ~~for your virtual squadron~~''		''How to file a military flight plan''

	~~{{toc}}~~

	== 1. Overview ==		== 1. Overview ==

	The DD Form 175 is the standard US military domestic flight plan. Every mission—regardless of aircraft type or complexity—is filed on this form before departure. Base Operations reviews and approves it; ~~one copy stays with base ops, one flies with the crew.~~		The DD Form 175 is the standard US military domestic flight plan. Every mission—regardless of aircraft type or complexity—is filed on this form before departure. Base Operations reviews and approves it;

	The form has four logical parts: a '''document header''' that identifies the aircraft and date, one or more '''route leg rows''' covering the actual routing, an '''administrative section''' for fuel, weather, and remarks, and a '''crew manifest'''.		The form has four logical parts: a '''document header''' that identifies the aircraft and date, one or more '''route leg rows''' covering the actual routing, an '''administrative section''' for fuel, weather, and remarks, and a '''crew manifest'''.

	{~~{Callout~~\|In the virtual squadron digital form, required fields are marked with a red asterisk (*). ~~Fields labeled "Base ops" are filled after submission — do not fill these yourself.}~~}		{\| style="border-left: 4px solid #36c; background: #eef; padding: 8px; width: 100%;"
			\| '''Note:''' In the virtual squadron digital form, required fields are marked with a red asterisk (*).
			\|}

	== 2. Before you start ==		== 2. Before you start ==
Line 41:		Line 41:
	\|}		\|}

	{{Note\|The Authority field is pre-filled (<code>10 USC 8012 AND EO 9397</code>) and does not need to be changed for standard missions.}}		{\| style="border-left: 4px solid #36c; background: #eef; padding: 8px; width: 100%;"
			\| '''Note:''' The Authority field is pre-filled (<code>10 USC 8012 AND EO 9397</code>) and does not need to be changed for standard missions.
			\|}

	== 4. Route of flight (fields 4–11) ==		== 4. Route of flight (fields 4–11) ==
Line 98:		Line 100:
	\|}		\|}

	{{Warning\|For stopover legs: add <code>(R)[ICAO]</code> as a second line in the route field — do not create a separate leg row for the ground stop. The ETE for the leg should cover the total time including the ground delay.}}		{\| style="border-left: 4px solid #e8a000; background: #fef6e0; padding: 8px; width: 100%;"
			\| '''Warning:''' For stopover legs: add <code>(R)[ICAO]</code> as a second line in the route field — do not create a separate leg row for the ground stop. The ETE for the leg should cover the total time including the ground delay.
			\|}

	== 5. Administrative data (fields 12–20) ==		== 5. Administrative data (fields 12–20) ==
Line 124:		Line 128:
	\|}		\|}

	{{Note\|Fields 21 (approval signature) and 23 (actual departure time) are filled by base operations after submission. Leave these blank.}}		{\| style="border-left: 4px solid #36c; background: #eef; padding: 8px; width: 100%;"
			\| '''Note:''' Fields 21 (approval signature) and 23 (actual departure time) are filled by base operations after submission. Leave these blank.
			\|}

	== 6. Crew manifest (fields 24–28) ==		== 6. Crew manifest (fields 24–28) ==
Line 182:		Line 188:
	; Filling base ops fields		; Filling base ops fields
	: Fields 21 (signature) and 23 (actual departure time) are base ops only. Do not fill these during initial plan submission.		: Fields 21 (signature) and 23 (actual departure time) are base ops only. Do not fill these during initial plan submission.

	~~[[Category:Flight Operations]]~~
	~~[[Category:Squadron Procedures]]~~

Main Page

Niknam3 — Sat, 25 Apr 2026 10:26:14 GMT

← Older revision		Revision as of 10:26, 25 April 2026
Line 32:		Line 32:
	'''IN CASE OF DOUBT USE PLAIN LANGUAGE'''		'''IN CASE OF DOUBT USE PLAIN LANGUAGE'''

	[[General/Tactical Communication\|Tactical Communication]] · [[General/CATC Communications Guide\|CATC Communications Guide]] · [[General/Air Traffic Communication\|Airfield Communications]]		[[General/Tactical Communication\|Tactical Communication]] · [[General/CATC Communications Guide\|CATC Communications Guide]] · [[General/Air Traffic Communication\|Airfield Communications]] · [[DDFORM175\|Filing Flight Plans]]

	----		----

DDFORM175

Niknam3 — Sat, 25 Apr 2026 10:23:54 GMT

Created page with "= DD Form 175 — Military Flight Plan = ''How to file a military flight plan for your virtual squadron'' {{toc}} == 1. Overview == The DD Form 175 is the standard US military domestic flight plan. Every mission—regardless of aircraft type or complexity—is filed on this form before departure. Base Operations reviews and approves it; one copy stays with base ops, one flies with the crew. The form has four logical parts: a '''document header''' that identifies the..."

New page

= DD Form 175 — Military Flight Plan =

''How to file a military flight plan for your virtual squadron''

{{toc}}

== 1. Overview ==

The DD Form 175 is the standard US military domestic flight plan. Every mission—regardless of aircraft type or complexity—is filed on this form before departure. Base Operations reviews and approves it; one copy stays with base ops, one flies with the crew.

The form has four logical parts: a '''document header''' that identifies the aircraft and date, one or more '''route leg rows''' covering the actual routing, an '''administrative section''' for fuel, weather, and remarks, and a '''crew manifest'''.

{{Callout|In the virtual squadron digital form, required fields are marked with a red asterisk (*). Fields labeled "Base ops" are filled after submission — do not fill these yourself.}}

== 2. Before you start ==

; Step 1 — Get your weather brief
: Obtain a weather briefing and note the source and time (Zulu). You will enter this in field 18. Example: <code>LS 18</code> (local brief at 1800Z).

; Step 2 — Plan your route
: Determine departure fix, airways, intermediate fixes, and destination. Note any refueling anchors, SUA transits, or holding requirements. All ICAO identifiers are 4-letter codes (e.g. <code>KLSF</code>).

; Step 3 — Compute fuel and ETE
: Calculate estimated time en-route and total fuel endurance in <code>H+MM</code> format (e.g. <code>2+30</code> = 2 hours 30 minutes). This is DoD standard — do not use <code>HH:MM</code>.

; Step 4 — Check NOTAMs and alternate
: Review NOTAMs for your route and select an alternate airfield (required for IFR). You will check a box confirming NOTAM review.

== 3. Document header (fields 1–3) ==

These three fields identify the mission and appear once at the top of the form. They apply to every leg.

{| class="wikitable"
! Field !! What to enter !! Status
|-
| '''Field 1 — Date''' || Date of flight in <code>DD MON YY</code> format. Example: <code>24 APR 26</code>. || Required
|-
| '''Field 2 — Call sign''' || Radio call sign for this mission. Example: <code>HAWK 11</code>, <code>VIPER 07</code>. Uppercase, 4–12 characters. || Required
|-
| '''Field 3 — A/C designation''' || Aircraft MDS and performance code in <code>[Type]/[Code]</code> format. Example: <code>F-16C/B</code>, <code>H/C-17/R</code>. The <code>H/</code> prefix denotes a heavy aircraft. || Required
|}

{{Note|The Authority field is pre-filled (<code>10 USC 8012 AND EO 9397</code>) and does not need to be changed for standard missions.}}

== 4. Route of flight (fields 4–11) ==

Each leg of the flight occupies one row. A direct flight has one leg; a mission with a stopover or multiple segments has multiple rows. Click '''+ Add leg''' in the form to add more rows.

{| class="wikitable"
! Field !! What to enter !! Status
|-
| '''Field 4 — Type''' || Flight rules for this leg: <code>I</code> (IFR), <code>V</code> (VFR), <code>Y</code> (IFR then VFR), <code>Z</code> (VFR then IFR). || Required
|-
| '''Field 5 — TAS''' || True airspeed in knots, integer, no unit suffix. Examples: <code>330</code>, <code>450</code>, <code>98</code>. || Required
|-
| '''Field 6 — Departure''' || ICAO 4-letter identifier of the departure airfield. Example: <code>KLSF</code>, <code>KVAD</code>. For legs originating from a fix, enter the fix and radial/distance: <code>PSX 242038</code>. || Required
|-
| '''Field 7 — Dep time (Z)''' || Planned departure in Zulu time, 4-digit <code>HHMM</code> format. Example: <code>1430</code>. All times on DD 175 are Zulu. || Required
|-
| '''Field 8 — Altitude''' || Cruising altitude in hundreds of feet MSL. Example: <code>200</code> = 20,000 ft, <code>260</code> = FL260. For low-level legs: <code>50</code> = 5,000 ft. || Required
|-
| '''Field 9 — Route''' || Free-text route string. See [[#4a. Writing the route string (field 9)|section 4a]] below. || Required
|-
| '''Field 10 — Destination''' || ICAO 4-letter identifier of the destination for this leg. Example: <code>KSKF</code>. || Required
|-
| '''Field 11 — ETE''' || Estimated time en-route in <code>H+MM</code> format. Example: <code>1+30</code>, <code>0+45</code>. || Required
|}

=== 4a. Writing the route string (field 9) ===

Field 9 is a free-text field. Enter your routing exactly as you would on the paper form — space-separated airways and fixes on a single line. Do not add punctuation between tokens unless it is a defined annotation (see [[#4b. Special annotations in field 9|section 4b]]).

'''Simple point-to-point:'''
EUF V159 PZD V578 IFM

'''High-altitude jet route:'''
MQP J23 BATIK J58 SPS 282078

'''Fix defined by radial and distance:'''
AUS 291061 BSM344017

Radial/distance fixes are written as <code>[NAVAID][3-digit radial][6-digit distance]</code>, all run together with no spaces within the token.

=== 4b. Special annotations in field 9 ===

{| class="wikitable"
! Situation !! Notation !! Example
|-
| Airborne holding delay at a fix || <code>[FIX]/D0+MM</code> || <code>DUMPS/D0+10 J17</code>
|-
| Ground stop at intermediate airport || <code>(R)[ICAO] D0+MM</code> on a second route line || <code>(R)KVAD D0+30 KLSF</code>
|-
| Aerial refueling track || <code>AR[###]</code> followed by anchor points || <code>AR611 AUS 302044 AUS J21 SAT</code>
|-
| SUA transit with delay || <code>[SUA name] D0+MM [exit fix]</code> || <code>REESE 1 D0+15 KREE</code>
|-
| ALTRV block entry || <code>[ALTRV name]/D[H+MM] [exit fix]</code> || <code>ALB/D4+39 PGS</code>
|}

{{Warning|For stopover legs: add <code>(R)[ICAO]</code> as a second line in the route field — do not create a separate leg row for the ground stop. The ETE for the leg should cover the total time including the ground delay.}}

== 5. Administrative data (fields 12–20) ==

{| class="wikitable"
! Field !! What to enter !! Status
|-
| '''Field 12 — Remarks''' || Free text. Common entries: stopover notation <code>KMGM-S</code>; PPR reference <code>KFWH-PPR 0723</code>; ATC requests <code>REQUEST RADAR DEPARTURE</code>; ALTRV joining statement. || Recommended
|-
| '''Field 13 — Rank / honor code''' || Priority code and mission description. Example: <code>R50 REAL KOZR TO KMGM</code>. Required only for VIP or priority missions. || Conditional
|-
| '''Field 14 — Fuel on board''' || Total fuel endurance at departure in <code>H+MM</code>. Example: <code>7+30</code>. || Required
|-
| '''Field 15 — Alternate''' || ICAO identifier of the alternate airfield. Required for all IFR flights. Example: <code>KLSF</code>. || IFR only
|-
| '''Field 16 — ETE to alternate''' || Time from destination to alternate in <code>H+MM</code>. Example: <code>0+50</code>. || IFR only
|-
| '''Field 17 — NOTAMs''' || Check the box after reviewing NOTAMs for your route. || Required
|-
| '''Field 18 — Weather''' || Brief source and time code. Example: <code>LS 18</code> (local, 1800Z). || Required
|-
| '''Field 19 — Weight and balance''' || Reference to your W&B document: home station and date. Example: <code>KOZR, 24 APR 26</code>. || Required
|-
| '''Field 20 — Serial / unit / station''' || Aircraft serial, unit name, and home station ICAO separated by <code>/</code>. Example: <code>96-0001 / VIPER SQDN / UGKO</code>. || Required
|}

{{Note|Fields 21 (approval signature) and 23 (actual departure time) are filled by base operations after submission. Leave these blank.}}

== 6. Crew manifest (fields 24–28) ==

Add one row per crew member or passenger. Click '''+ Add row''' to add more. The pilot-in-command row is pre-populated.

{| class="wikitable"
! Field !! What to enter
|-
| '''Field 24 — Duty''' || Position: <code>PILOT IN COMMAND</code>, <code>CP</code> (copilot), <code>CE</code> (crew chief), <code>N</code> (navigator), <code>TO</code>, or free text for non-standard roles.
|-
| '''Field 25 — Name''' || Last name, first initial, middle initial. Format: <code>SMITH, J.R.</code> Uppercase.
|-
| '''Field 26 — Rank''' || Pay grade abbreviation. Examples: <code>CPT</code>, <code>CW4</code>, <code>MAJ</code>, <code>1LT</code>, <code>CDR</code>.
|-
| '''Field 27 — Member ID''' || Virtual squadron member ID (replaces SSN in sim context). Format: <code>###-##-####</code>.
|-
| '''Field 28 — Unit / station''' || Unit name and home station ICAO. Example: <code>VIPER SQDN / UGKO</code>.
|}

== 7. Plan types ==

=== Simple point-to-point ===

One leg row. Fill fields 4–11 for the single segment. Remarks are brief or absent.

=== Multi-leg / stopover ===

Use multiple leg rows. Each row is a complete segment with its own departure, routing, destination, and ETE. Note each stopover in Remarks as <code>[ICAO]-S</code>. If the aircraft makes a ground stop but the planner treats it as one continuous leg (composite plan), use a single leg row with the <code>(R)[ICAO] D0+MM</code> notation on the second line of field 9.

=== Aerial refueling ===

Include the <code>AR[###]</code> track identifier in field 9, followed by the anchor fix sequence. Add any PPR reference to Remarks (e.g. <code>KFWH-PPR 0723</code>). If the refueling point is also the alternate, note that in field 15.

=== ALTRV (altitude reservation) ===

The ALTRV block name and timing go in field 9 using the <code>[NAME]/D[H+MM] [exit fix]</code> format. Add the joining statement to Remarks: <code>ALTRV: (ALB) JOINED AT ALB/MARSA</code>. ALTRV coordination itself happens outside the form.

=== Heavy aircraft ===

Prefix the aircraft designation in field 3 with <code>H/</code> (e.g. <code>H/C-17/R</code>). No other fields change; the prefix affects ATC wake turbulence separation only.

== 8. Common mistakes ==

; Wrong time format
: All times are Zulu and in <code>HHMM</code> format. All durations are in <code>H+MM</code>. Never use <code>HH:MM</code> or local time.

; Altitude in feet instead of hundreds
: Field 8 takes altitude in hundreds of feet. Enter <code>200</code> for 20,000 ft — not <code>20000</code>.

; Blank NOTAMs checkbox
: Field 17 must be checked before submission. Base ops will reject plans with an unchecked NOTAM box.

; No alternate for IFR flight
: Any IFR leg requires field 15 (alternate airfield) and field 16 (ETE to alternate) to be filled.

; Filling base ops fields
: Fields 21 (signature) and 23 (actual departure time) are base ops only. Do not fill these during initial plan submission.

[[Category:Flight Operations]]
[[Category:Squadron Procedures]]

Main Page

Niknam3 — Wed, 22 Apr 2026 12:05:32 GMT

← Older revision		Revision as of 12:05, 22 April 2026
(3 intermediate revisions by the same user not shown)
Line 11:		Line 11:
	<div style="border-top:1px solid #c8c5bf; max-width:200px; margin:0 auto 16px auto;"></div>		<div style="border-top:1px solid #c8c5bf; max-width:200px; margin:0 auto 16px auto;"></div>
	<div style="font-size:0.62rem; letter-spacing:2px; color:#9a9690;">		<div style="font-size:0.62rem; letter-spacing:2px; color:#9a9690;">
	~~▮ ~~ CURRENT THEATER: SYRIA ~~ ▮  SERVER: ONLINE  ▮ ~~		CURRENT THEATER: SYRIA -
	~~[[Server Info/Server Rules\|ROE]]  · ~~
	~~[[Server Info/Frequency Plan\|FREQ PLAN]]  · ~~
	[[Server Info/Airfields\|AIRFIELDS]]		[[Server Info/Airfields\|AIRFIELDS]]
	</div>		</div>
Line 24:		Line 22:
	New to SOURCE? Complete all onboarding steps before your first operation. Install required software, read the rules of engagement, and familiarise yourself with communications procedures.		New to SOURCE? Complete all onboarding steps before your first operation. Install required software, read the rules of engagement, and familiarise yourself with communications procedures.

	[[Guides/New Member Guide\|New Member Guide]] · [[Guides/SRS Setup\|SRS Setup]] · [[Guides/Mod Installation\|Mod Installation~~]] · [[Guides/DCS Settings\|DCS Settings~~]]		[[Guides/New Member Guide\|New Member Guide]] · [[Guides/SRS Setup\|SRS Setup]] · [[Guides/Mod Installation\|Mod Installation]]

	----		----

Guides/SRS Setup

Niknam3 — Wed, 22 Apr 2026 12:03:08 GMT

02. Install SRS

← Older revision		Revision as of 12:03, 22 April 2026
Line 2:		Line 2:

	=== 01. Download SRS Installer ===		=== 01. Download SRS Installer ===
	You can download SRS from [https://github.com/ciribob/DCS-SimpleRadioStandalone/releases here] \| Make sure the version has Latest in Green to the right of it.		You can download SRS from [https://github.com/ciribob/DCS-SimpleRadioStandalone/releases here] \| Make sure the version has Latest in Green to the right of it.

	=== 02. Install SRS ===		=== 02. Install SRS ===
	Installation is pretty straightforward. Unzip SRS and run Installer.exe. SRS should automatically point to the Saved Games folder if not point to your DCS Saved Games folder		Installation is pretty straightforward. Unzip SRS and run Installer.exe. SRS should automatically point to the Saved Games folder if not point to your DCS Saved Games folder
	(C:\Users\{your-username-here]\Saved Games) <- Should look something like this. If you look for it manually the folders are visually named by your local windows language so make sure to translate accordingly! After that you can click "Install/Update DCS-SRS" button!		(C:\Users\{your-username-here]\Saved Games) <- Should look something like this. If you look for it manually the folders are visually named by your local windows language so make sure to translate accordingly! After that you can click "Install/Update DCS-SRS" button!

	== 02 / SRS Settings ==		== 02 / SRS Settings ==

	=== 01. Radio Keybinds ===		=== 01. Radio Keybinds ===
	Click on Controls		Click on Controls[[File:SRS General Edited.png\|left\|frameless\|465x465px]]
	[[File:SRS General Edited.png\|left\|frameless\|465x465px]]
	[[File:SRS Controls.png\|left\|frameless\|465x465px]]		[[File:SRS Controls.png\|left\|frameless\|465x465px]]

Guides/SRS Setup

Knifej — Tue, 21 Apr 2026 20:11:23 GMT

Title capital letter adjustments

← Older revision		Revision as of 20:11, 21 April 2026
(3 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	== 01 / Installing SRS ==		== 01 / Installing SRS ==

	=== 01. ~~DOWNLOAD srs iNSTALLER~~ ===		=== 01. Download SRS Installer ===
	You can download SRS from [https://github.com/ciribob/DCS-SimpleRadioStandalone/releases here] \| Make sure the version has Latest in Green to the right of it.		You can download SRS from [https://github.com/ciribob/DCS-SimpleRadioStandalone/releases here] \| Make sure the version has Latest in Green to the right of it.

	=== 02. ~~INSTALL~~ SRS ===		=== 02. Install SRS ===
	Installation is pretty straightforward. Unzip SRS and run Installer.exe. SRS should automatically point to the Saved Games folder if not point to your DCS Saved Games folder		Installation is pretty straightforward. Unzip SRS and run Installer.exe. SRS should automatically point to the Saved Games folder if not point to your DCS Saved Games folder
	(C:\Users\{your-username-here]\Saved Games) <- Should look something like this. If you look for it manually the folders are visually named by your local windows language so make sure to translate accordingly! After that you can click "Install/Update DCS-SRS" button!		(C:\Users\{your-username-here]\Saved Games) <- Should look something like this. If you look for it manually the folders are visually named by your local windows language so make sure to translate accordingly! After that you can click "Install/Update DCS-SRS" button!

	== 02 / ~~srs settings~~ ==		== 02 / SRS Settings ==

	=== 01. ~~radio keybinds~~ ===		=== 01. Radio Keybinds ===
	Click on Controls		Click on Controls
	[[File:SRS General Edited.png\|left\|frameless\|465x465px]]		[[File:SRS General Edited.png\|left\|frameless\|465x465px]]
			[[File:SRS Controls.png\|left\|frameless\|465x465px]]











	~~Then bind Radio 1 & 2 and 3 & 4 if your an F/A-18C Pilot (You can bind the radio keybind to your HOTAS like you see on the screen but as far as i know only to one device)~~
	[[File:SRS Controls.png\|left\|~~thumb~~\|~~466x466px~~]]

Guides/SRS Setup

Knifej — Tue, 21 Apr 2026 20:00:00 GMT

SRS Page / INSTALLING SRS / SRS SETTINGS - RADIO KEYBINDS /

New page

== 01 / Installing SRS ==

=== 01. DOWNLOAD srs iNSTALLER ===
You can download SRS from [https://github.com/ciribob/DCS-SimpleRadioStandalone/releases here] | Make sure the version has Latest in Green to the right of it.

=== 02. INSTALL SRS ===
Installation is pretty straightforward. Unzip SRS and run Installer.exe. SRS should automatically point to the Saved Games folder if not point to your DCS Saved Games folder
(C:\Users\{your-username-here]\Saved Games) <- Should look something like this. If you look for it manually the folders are visually named by your local windows language so make sure to translate accordingly! After that you can click "Install/Update DCS-SRS" button!

== 02 / srs settings ==

=== 01. radio keybinds ===
Click on Controls
[[File:SRS General Edited.png|left|frameless|465x465px]]

Then bind Radio 1 & 2 and 3 & 4 if your an F/A-18C Pilot (You can bind the radio keybind to your HOTAS like you see on the screen but as far as i know only to one device)
[[File:SRS Controls.png|left|thumb|466x466px]]

File:SRS Controls.png

Knifej — Tue, 21 Apr 2026 19:57:57 GMT

Knifej uploaded File:SRS Controls.png

New page

File:SRS General Edited.png

Knifej — Tue, 21 Apr 2026 19:53:10 GMT

Knifej uploaded File:SRS General Edited.png

New page

yes

File:SRS General.png

Knifej — Tue, 21 Apr 2026 19:50:40 GMT

Knifej uploaded File:SRS General.png

New page

Approach Types

Niknam3 — Tue, 21 Apr 2026 19:32:27 GMT

← Older revision		Revision as of 19:32, 21 April 2026
Line 71:		Line 71:
	!Phrase		!Phrase
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''Radar vectors the aircraft towards the airport / Instructs to Resume Own Navigation''		\| colspan="2" style="text-align:center;" \|''Radar vectors the aircraft towards the airport / Instructs to Resume Own Navigation''
	\|-		\|-
	\|LTAA-Radar		\|LTAA-Radar
Line 91:		Line 91:
	\|{CS}, push {BTN / FREQ}		\|{CS}, push {BTN / FREQ}
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''From here, normal tower procedures apply (straight-in, overhead break, etc.)''		\| colspan="2" style="text-align:center;" \|''From here, normal tower procedures apply (straight-in, overhead break, etc.)''
	\|}		\|}
	----		----
Line 141:		Line 141:
	!Phrase		!Phrase
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''Radar vectors the aircraft to intercept the localizer''		\| colspan="2" style="text-align:center;" \|''Radar vectors the aircraft to intercept the localizer''
	\|-		\|-
	\|LTAA-Radar		\|LTAA-Radar
Line 149:		Line 149:
	\|{CS}, heading {Heading}, descend and maintain {Altitude}		\|{CS}, heading {Heading}, descend and maintain {Altitude}
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''Approaching localizer intercept''		\| colspan="2" style="text-align:center;" \|''Approaching localizer intercept''
	\|-		\|-
	\|LTAA-Radar		\|LTAA-Radar
Line 157:		Line 157:
	\|{CS}, cleared ILS runway {RWY} approach, report established		\|{CS}, cleared ILS runway {RWY} approach, report established
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''Once established on the localizer and glideslope, the pilot follows the needles down. ATC may hand off to Tower.''		\| colspan="2" style="text-align:center;" \|''Once established on the localizer and glideslope, the pilot follows the needles down. ATC may hand off to Tower.''
	\|-		\|-
	\|LTAA-Radar		\|LTAA-Radar
Line 165:		Line 165:
	\|{CS}, push {FREQ}		\|{CS}, push {FREQ}
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''Tower''		\| colspan="2" style="text-align:center;" \|''Tower''
	\|-		\|-
	\|Flight Lead		\|Flight Lead
Line 223:		Line 223:
	!Phrase		!Phrase
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''Radar vectors the aircraft towards the final approach course, or the pilot navigates via a published procedure''		\| colspan="2" style="text-align:center;" \|''Radar vectors the aircraft towards the final approach course, or the pilot navigates via a published procedure''
	\|-		\|-
	\|LTAA-Radar		\|LTAA-Radar
Line 231:		Line 231:
	\|{CS}, heading {Heading}, descend and maintain {Altitude}		\|{CS}, heading {Heading}, descend and maintain {Altitude}
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''Approaching the final approach course''		\| colspan="2" style="text-align:center;" \|''Approaching the final approach course''
	\|-		\|-
	\|LTAA-Radar		\|LTAA-Radar
Line 239:		Line 239:
	\|{CS}, heading {Heading}, maintain {Altitude} until established, cleared TACAN runway {RWY} approach		\|{CS}, heading {Heading}, maintain {Altitude} until established, cleared TACAN runway {RWY} approach
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''Once established, pilot tracks the course and descends per the published procedure. ATC hands off to Tower.''		\| colspan="2" style="text-align:center;" \|''Once established, pilot tracks the course and descends per the published procedure. ATC hands off to Tower.''
	\|-		\|-
	\|LTAA-Radar		\|LTAA-Radar
Line 247:		Line 247:
	\|{CS}, push {FREQ}		\|{CS}, push {FREQ}
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''Tower''		\| colspan="2" style="text-align:center;" \|''Tower''
	\|-		\|-
	\|Flight Lead		\|Flight Lead
Line 323:		Line 323:
	!Phrase		!Phrase
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|'''Pattern Controller'''		\| colspan="2" style="text-align:center;" \|'''Pattern Controller'''
	\|-		\|-
	\|Pattern Controller		\|Pattern Controller
Line 331:		Line 331:
	\|{CS}, roger		\|{CS}, roger
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''Pattern controller vectors the aircraft to the final approach course using heading and altitude instructions''		\| colspan="2" style="text-align:center;" \|''Pattern controller vectors the aircraft to the final approach course using heading and altitude instructions''
	\|-		\|-
	\|Pattern Controller		\|Pattern Controller
Line 345:		Line 345:
	\|{CS}, push {FREQ}		\|{CS}, push {FREQ}
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|'''Final Controller'''		\| colspan="2" style="text-align:center;" \|'''Final Controller'''
	\|-		\|-
	\|Final Controller		\|Final Controller
Line 356:		Line 356:
	\|{CS}, do not acknowledge further transmissions. {Distance} miles from touchdown. Heading {Heading}, on course, on glidepath.		\|{CS}, do not acknowledge further transmissions. {Distance} miles from touchdown. Heading {Heading}, on course, on glidepath.
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''Approaching glidepath intercept''		\| colspan="2" style="text-align:center;" \|''Approaching glidepath intercept''
	\|-		\|-
	\|Final Controller		\|Final Controller
	\|Approaching glidepath. Begin descent.		\|Approaching glidepath. Begin descent.
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''Continuous guidance — approximately every 5 seconds — heading, course, glidepath, and distance information until landing threshold''		\| colspan="2" style="text-align:center;" \|''Continuous guidance — approximately every 5 seconds — heading, course, glidepath, and distance information until landing threshold''
	\|-		\|-
	\|Final Controller		\|Final Controller
	\|At decision height.		\|At decision height.
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \|''If runway in sight, pilot lands. If not:''		\| colspan="2" style="text-align:center;" \|''If runway in sight, pilot lands. If not:''
	\|-		\|-
	\|Flight Lead		\|Flight Lead
Line 391:		Line 391:
	\| Flight Lead \|\| {CS}, wilco		\| Flight Lead \|\| {CS}, wilco
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \| ''Once over the initial''		\| colspan="2" style="text-align:center;" \| ''Once over the initial''
	\|-		\|-
	\| Flight Lead \|\| {CS} initial		\| Flight Lead \|\| {CS} initial
Line 397:		Line 397:
	\| LTAG-TWR \|\| {CS} {Left / Right} hand break, wind {Winds}, altimeter {Altimeter}, report on the break		\| LTAG-TWR \|\| {CS} {Left / Right} hand break, wind {Winds}, altimeter {Altimeter}, report on the break
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \| ''Assuming number 4 breaks first''		\| colspan="2" style="text-align:center;" \| ''Assuming number 4 breaks first''
	\|-		\|-
	\| Flight Number 4 \|\| {CS} 4, on the break		\| Flight Number 4 \|\| {CS} 4, on the break
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \| ''Repeated for each flight member at their interval''		\| colspan="2" style="text-align:center;" \| ''Repeated for each flight member at their interval''
	\|-		\|-
	\| colspan="2" style="text-align:center~~; background:#ddd~~;" \| ''After the break turn, once configured for landing''		\| colspan="2" style="text-align:center;" \| ''After the break turn, once configured for landing''
	\|-		\|-
	\| LTAG-TWR \|\| {CS}, check gear down, wind {Winds}, runway {RWY}, cleared to land		\| LTAG-TWR \|\| {CS}, check gear down, wind {Winds}, runway {RWY}, cleared to land

General/Air Traffic Communication

Knifej — Tue, 21 Apr 2026 19:09:58 GMT

no ai used hopefully fixed this god forsaken page

Show changes

General/CATC Communications Guide

Niknam3 — Tue, 21 Apr 2026 19:07:37 GMT

CASE I Recovery

← Older revision		Revision as of 19:07, 21 April 2026
Line 207:		Line 207:
	! colspan="2" \| CASE I BOLTER / WAVEOFF		! colspan="2" \| CASE I BOLTER / WAVEOFF
	\|-		\|-
	\| ~~style="background:#efefef; color:#000000;"~~ \| LSO \|\| \| WAVE-OFF! / BOLTER BOLTER BOLTER!		\| \| LSO \|\| \| WAVE-OFF! / BOLTER BOLTER BOLTER!
	\|-		\|-
	\| colspan="2" \| Technically bolter/waveoff procedures are completely zip-lip. Aircraft are to visually fly the bolter procedure and are responsible for maintaining visual separation with all aircraft.		\| colspan="2" \| Technically bolter/waveoff procedures are completely zip-lip. Aircraft are to visually fly the bolter procedure and are responsible for maintaining visual separation with all aircraft.