Master Arms Wiki - Användarbidrag [sv]

Airport Procedures

2022-11-10T23:30:49Z

Lillfilly: Ändrade på regeln för hastighetsbegränsning under 10000ft

''[[Home]] >> [[Standard Operating Procedures]] >> [[Airport Procedures]]''

Though inspired by real life operations, our goal is to strike a balance between realism and manageability. The airspace types listed below are most useful during training events with live ATC in order to increase immersion.

==Overview==
[[Fil:MA_airspace_wiki_01.png|400px|thumb|Overview]]
The airspace structure is usually viewed as an inverted cake, extending from the airport and up.

===Control Area (CTA)===
[[Fil:MA_airspace_wiki_04_CTA.png|400px|thumb|CTA]]
The CTA represents the top of the cake and covers a large area, it’s purpose is to route and separate traffic to, from and through the region. With live ATC the airspace is controlled. It’s bottom starts at 10 000 feet above mean sea level (MSL) and continues to infinity (marked as UNL). Note that you can fly below the CTA.

===Terminal Area (TMA)===
[[Fil:MA_airspace_wiki_03_TMA.png|400px|thumb|TMA]]
The TMA is the middle portion of the cake and serves more as a facility to route traffic to and from airports. With live ATC the airspace is controlled. It’s bottom starts at 1500 feet MSL and the ceiling stops at 10 000 feet where the CTA starts. Parts of the the TMA can have a floor defined as 1500 feet above ground level (AGL) due to high terrain elevation. Several airports are located under a single TMA. Note that you can fly below the TMA.

===Control Zone (CTR)===
[[Fil:MA_airspace_wiki_02_CTR.png|400px|thumb|CTR]]
The CTR is the top of the inverted cake and covers an airfield. It’s purpose is to protect aircraft departing and arriving at individual airports. With live ATC the airspace is controlled. It reaches from ground level to 1500 feet AGL. Note that you shouldn’t fly below the CTR.

===Restricted Area (R)===

A restricted area is basically a controlled airspace which is not necessarily close to any airports. They are positioned to protect traffic from live fire. Avoid these unless cleared by ATC or if you are aware of traffic within the airspace.

===Departure and arrival===

The most common type of departure used is a visual one. Normally ATC will clear you towards an exit point marked on a Visual Operations Chart, you are then expected to navigate visually following the route on the chart. Same goes for arrival.

ATC can also issue specific headings or TACAN radials to follow after take off, in this case the exit points are no longer valid.

===Controlled and Uncontrolled Flight===

With live ATC all flights are controlled within CTR, TMA and CTA. Players can still fly uncontrolled below TMA and CTA without any clearance, just be aware of your position relative to any airports or restricted areas.
===VFR or IFR===

Visual Flight Rules (VFR) means that the pilot has navigation responsibility using visual references. Navigation aids such as INS, TACAN or ATC may be used to enhance situational awareness.

Instrument Flight Rules (IFR) can be applied in visual conditions but puts more navigation responsibility on ATC. INS or TACAN etc. may also be used for navigation. IFR flights may be conducted in poor weather.

===Speed restrictions===

Maintain a maximum speed of 300 KIAS when inside CTR or TMA unless cleared high speed by ATC. This can always be requested but might be denied due to ATC workload.

If there is no ATC available you may deviate from this rule, but you should communicate this with other pilots in the area (on the appropriate channel for the area you are flying in, typically Tower for CTR, Tactical for TMA). Warn other pilots of where you are, where you are going, and that you will be flying at high speed.

Wingmen may exceed 300 KIAS if their flight lead is nearby to rejoin/fix the formation.

This speed restriction is intended to reduce the risk of collision by giving pilots time to find eachother visually, and to give ATC time to manage the traffic.

===Landing Pattern===
[[Fil:OverheadBreak.png|400px|thumb|Overhead Break]]
The standard landing pattern for arriving traffic is the overhead break. Straight in landings or formation landings must be requested well ahead of arrival to accommodate for increased spacing on final approach. All aircraft from all branches are expected to break at 1500 feet AGL and to maintain that altitude until turning base. The pattern direction is indicated on the Visual Operations Chart.

===Go Around / Missed Approach===

If the approach is aborted after the break, complete the pattern and position yourself overhead the runway and continue on the runway track. Climb gently to 1000 feet AGL to stay below arriving traffic and increase speed to 300 KIAS. You will then be cleared by tower to break again when the sequence is correct, this includes a climb to 1500 feet AGL.

 
 
 
 
 
 
 
 
 
 
 
 
 
==Kutaisi CTA==

[[Fil:Kutaisi CTA v0.5.png|400px|thumb|Overview]]

The descriptions above apply to the airspace surrounding the western region of Georgia.

====Lanchhuti Transition====
[[Fil:Kutaisi Lanchhuti Transition 01.jpg|400px|thumb|Overview]]

Lanchhuti Transition is a local procedure to deconflict departing and arriving traffic from R99 and Kobuleti CTR while flying to and from Kutaisi airfield. It is a VFR transition.

====Departing traffic:====

* After passing assigned exit point, fly towards and then along the ridge southwest of Kutaisi. Pass between Kobuleti CTR and R99.

* Expect 5000 feet initially and further climb once established along the ridge.

====Arriving traffic:====

* Expect 3000 feet initially and 1600 feet once clear of terrain.

* Report approaching Entry West if you still have not recieved "Cleared approach" or tower channel by that time.
 
 
 
 
 
 
 
 
 
 
 
 

==Resources==

====In Game Kneeboard====

Drop the images contained in the file below in your C:\Users\YOURNAME\Saved Games\DCS.openbeta\Kneeboard folder to access section charts of Kutaisi CTA during flight.

[[Media:MA Kutaisi CTA kneeboard.zip]]

====Tacview Objects====

Drop the XML file into C:\Users\YOURNAME\AppData\Roaming\Tacview\Data\Static Objects to display Kutaisi CTA in Tacview.

[[Media:Kutaisi CTA Tacview.zip]]

====LotAtc Overlay====

Use the draw tool and open the json file to display Kutaisi CTA in LotAtc.

[[Media:MA_Master_Kutaisi_CTA_220210.zip]]

Comms

2022-11-04T20:21:33Z

Lillfilly: Ändrade kanalnamnet "Package" till "Tactical"

''[[Home]] >> [[Standard Operating Procedures]] >> [[Comms]]''

==Channels and Frequencies==

===PRI===

This is the default comms plan for missions.

''Mission specific channels'' (11 through 13) are used to fit the scenario of a mission. These may include additional tankers, airport towers & ground, specific tasking channels, JTAC etc. If used for a mission, the table will be updated with said channels' functions in the mission event page.

These common channels are called the PRI (primary) channels. They are used on Com1 (i.e the left radio in the Hornet).

{| class="wikitable"
! Channel
! Function
! Frequency
|-
| 1
| Carrier Tower
| 305.00
|-
| 2
| Carrier Tower (AI)
| 264.00
|-
| 3
| Tactical
| 265.00
|-
| 4
| Carrier Red Crown
| 256.00
|-
| 5
| CAP A
| 254.00
|-
| 6
| Ground
| 250.00
|-
| 7
| Tower
| 270.00
|-
| 8
| Control
| 257.00
|-
| 9
| AWACS Check In
| 255.00
|-
| 10
| CAP B
| 262.00
|-
| 11
| Air Force Secondary Tanker (AI)
| 259.00
|-
| 12
| Navy Secondary Tanker (AI)
| 268.00
|-
| 13
| Mission Specific
| 269.00
|-
| 14
| Navy Primary Tanker (AI)
| 260.00
|-
| 15
| Carrier Approach A
| 263.00
|-
| 16
| Carrier Marshal
| 261.00
|-
| 17
| Carrier Approach B
| 267.00
|-
| 18
| AWACS (AI)
| 251.00
|-
| 19
| Carrier Overhead Tankers (AI)
| 253.00
|-
| 20
| Air Force Primary Tanker (AI)
| 266.00
|}

This is the standard comms table for AJS 37. Note that there's no AJS 37 preset for Ground. It has to be manually set to 250.00.

{| class="wikitable"
! Channel
! Function
! Frequency
|-
|
| Ground
| 250.00
|-
| S1
| Tower
| 270.00
|-
| S2
| Control
| 257.00
|-
| S3
| Tactical
| 265.00
|-
| E
| AWACS Check In
| 255.00
|-
| F
| Mission Specific
| 259.00
|-
| G
| Mission Specific
| 268.00
|-
| H
| Guard
| 243.00
|}

===AUX===

The AUX frequencies are used by flights for intraflight comms. These are ''not'' presets. You have to manually tune your AUX radio to the correct frequency. The frequencies start at 130.10 and increases by .10 for each flight, corresponding to that flight's number.

Com2 (i.e the right radio in the Hornet) is used for this. As a flight lead, you may instead opt to use Teamspeak for intraflight comms. (If you do, the recommendation is to use TS ''instead'' of the AUX radio, not using TS as third radio)

{| class="wikitable"
! Flight
! VHF
! UHF
|-
| Flight 1
| 130.10
| 330.10
|-
| Flight 2
| 130.20
| 330.20
|-
| Flight 3
| 130.30
| 330.30
|-
| Flight 4
| 130.40
| 330.40
|-
| Flight 5
| 130.50
| 330.50
|-
| ...
| ...
| ...
|-
| Flight 10
| 131.00
| 331.00
|-
| Flight 11
| 131.10
| 331.10
|-
| ...
| ...
| ...
|}

==Common Radio Procedures==

===Changing frequency===
When the flight lead wants its flight to switch to a new channel (or specific frequency), he declares it on the frequency they are currently on. That way, the flight know where to go, and the controller of the frequency knows that you're now leaving. The brevity is "[Flight callsign], [Channel (or freq) to go to], push!].

Example:
''(Camel3, flight of four Hornets, is on channel 14 after finishing their aerial refueling, and should now go to channel 3 (tactical channel).''
Camel31: "Camel Three, button 3, push!"

''Note: The terms "Button" and "Channel" are used interchangeably. "Button" sounds a little more US Navy than "Channel" and we tend to use that, but it doesn't matter.''

===Check-ins===
After a flight enters a new PRI channel, they should "check in". This is done by having the leader say "[Flight name and number]". The wingmen then simply reply (on the channel they are entering) with their numbers in the flight. Note that you should not say the words ''"check in"'' or ''"checking in"'' at any point.

Example:
''(Camel3, flight of four Hornets, checks in on Tactical channel)''
Camel31: "Camel Three"
Camel32: "Two!"
Camel33: "Three!"
Camel34: "Four!"

''Exception: During CASE 1 carrier procedures, flights do not check in on the tower channel (1) before the recovery. The check in is implicit, and nothing is said on the radio.''

===Contacting controlling agency===
After a flight has checked in for the first time, it is common (and in the case of the Tactical channel, mandatory) to contact the controlling agency on that channel. The most common situation is that a flight has checked in on the tactical channel and contacts AWACS. Let the controlling agency know your airframe count, your position and any other relevant information (for instance fuel state on lowest flight member, tasking, any technical issues and so on). If some of these things should already be known by the controlling agency (because they are pre-briefed) and they haven't changed, you don't need to mention them, but instead state "as fragged".

Example:
''(Camel3, flight of four Hornets on CAP tasking, has just checked in and now contacts AWACS "Stingray" on Tactical channel)''
Camel31: "Stingray, Camel31, marking bullseye 270 for 35 at angels 28, lowest state 10.8, as fragged!"
Stingray: "Camel31, Stingray, radar contact, continue as fragged."

===Authentication===
This is not always used, but sometimes a controlling agency may ask a flight (or vice-versa) to authenticate themselves to prove that they are friendly. When this happens, we're using a system called "RAMROD". It works by having a certain phrase communicated to all parties in the briefing. The phrase is then used as a key to be able to correctly reply to the querying instance's authentication request. The query consists of two letters from the phrase, with exactly one letter between them. The letter in between is the correct answer. Note that the phrase is assumed to "wrap around", meaning the first letter in the phrase is located between the last and the second letter.

Example 1:
''(Stingray asks Camel3 for authentication. The prebriefed RAMROD key is "MONKEYSPIT")''
Stingray: "Camel3, authenticate October Kilo!"
Camel31: "Stingray, Camel31 authenticates November."
Stingray: "Camel3, approved."

MONKEYSPIT

Example 2:
''(Same situation)''
Stingray: "Camel3, authenticate India Mike!"
Camel31: "Stingray, Camel31 authenticates Tango."
Stingray: "Camel31, approved."

MONKEYSPIT

==Transponder Codes==

When flying in events (and preferably during casual flying), you are expected to turn on your transponder and enable Mode 3 using a certain code. The way it's done is different in every aircraft. We use a simple system for knowing what code to use.

* During training events, you should use 0 + your sidenumber. If your sidenumber is 403, you should input 0403.
* During mission events, you should use 1 + your sidenumber. If your sidenumber is 403, you should input 1403.

Following these instructions, your callsign will automatically display for our ATC and AWACS people using the standalone program LotATC, saving them lots of trouble.

==Brevity List==

Here is a list of brevity that is good to learn! [[Brevity]]