Master Arms Wiki - Användarbidrag [sv]

Airport Procedures

2023-04-01T14:43:46Z

Urist: /* LotAtc Overlay */

''[[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.

[[Media:MA_OHB_4ship_F-16_2023.zip.acmi|TacView example of overhead break]]

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

Minimum safe altitude (MSA) for Kutaisi:

[[Media:MSA_Kutaisi_v2.zip]]

Fil:MSA Kutaisi v2.zip

2023-04-01T14:42:09Z

Urist: MSA Kutaisi for LotATC v2.3 Urist 2023

== Sammanfattning ==
MSA Kutaisi
for LotATC v2.3
Urist 2023

2023-01-06T17:10:33Z

Urist:

''[[Home]] >> [[Aircraft Syllabi]] >> [[Intro Flight]]''

This text is for F18C/A10C/F16C, for Viggen and UH-1 use:
[[Intro Flight for Viggen]]
[[Intro Flight for Huey]]

The intro flight is a newcomer's first familiarization flight. Its purpose is mainly to make sure all technical things work, make the newcomer feel welcome, go through some radio stuff and have some fun. It's not that important to learn any particular skills during the flight. That can come later.
This article describes the content of the sortie. A newcomer is welcome to practice any moments before, but there is no requirement nor expectation to do so.

However, all newcomers are expected to have gone through the [[Technical Checklist]] carefully, before the flight. This step is important. You're more than welcome to ask for help if you have any issues following the guide, but please don't ignore any of the mandatory steps.

''The intro flight is designed with the F/A-18C Hornet in mind. But it entirely possible, and encouraged, that the newcomer flies the sortie in his/her main aircraft of choice, choosing from the Hornet, Viggen, Tomcat, Viper or Warthog. The content might vary slightly depending on the aircraft type.''

==Brief description of the sortie==
[[Fil:IntroFlight.png|400px|thumb|Overview]]
===Pre-flight===
* Meet up on Teamspeak
* Make sure TS and SRS works, including all three PTT buttons
* The 1 minute version of what MA is and what we do
* Briefing. Quickly go over what we will do in the flight and look at the map.

===Flight===

# Disable Labels
# Startup
## Loadout: XT x 2, AIM-120C x 2, MK83 x 2, AIM-9X x 2
## Tower channel check-in (Report “2!”)
## Jet select
## Joker/Bingo setting
## Setup bombs (Nose, Inst, QTY: 2)
## Configure transponder
## Set QNH
# Formation takeoff
# Tac channel check-in (Report “2!”)
# Fence in at WP2 (Report “2, fenced in, [fuelstate]!”)
# Learn raygun and buddyspike calls (“Raygun, angels 12!”, “Buddyspike, angels 12!”)
# Engage enemy aircraft at WP3 (Report “Fox 3! Splash 1!”)
# Drop bombs on target at WP4 (Report “2, Winchester air-to-ground!”)
# Fence out (Report “2, fenced out, [fuelstate]!”)
# Go through on-speed flying
# Tower channel check-in (Report “2!”)
# Straight-in (or overhead break at 1500’) and land

===Post-flight===

* Short debriefing, going through what we just did and how it went. Some pointers on how to continue.
* Invitation to Discord Rookie-group

Urist: /* Intercept */

''[[Home]] >> [[Aviation guides]] >> [[Intercept]]''

==Intercept==

A short guide for the basics of intercepting flights, mostly for offensive operations such as visual identification, but also applicable for joins with friendly aircraft.

Basic principles:
; Vertical separation : You need a vertical separation for an intercept which depends on altitude, airspeed and bank angle. A rule of thumb is 40 000 feet (12 km / 6.5 NM) for a head on situation. The turn radius is half this distance.
; Lag - pure - lead pursuit : You start the intercept by lag pursuit and the target should pass your centerline for a lead pursuit just before half the turn for a head on intercept.
; Starting turn : For a head on intercept you need to start the turn when the range to the target is approximately 3.7 times the turn radius. The targets angle off the nose should always be 32.5 degrees at the start of the turn.

===Head-on intercept geometry===
[[File: intercept_geom_R2.png]]

===Animated intercepts===
====Top view====
[[File: join_topviev.gif]]
====Radar PPI view====
[[File: join_PPI.gif]]

2021-06-24T13:15:07Z

Urist: /* Intercept */

Intercept

2021-06-24T13:14:36Z

Urist:

Fil:Join topviev.gif

2021-06-24T13:11:09Z

Urist: Animated top view of intercept from three different offset angles

== Sammanfattning ==
Animated top view of intercept from three different offset angles

Intercept

2021-06-24T13:09:59Z

Urist: Utkast till sida om intercept/join

Home

2021-06-24T13:04:29Z

Urist: Lade till intercept (både offensiv och för rejoin)

===Welcome to the Master Arms Wiki v2.0!===

We are a Swedish combat flight sim community mainly focusing on DCS. We are constantly looking for new pilots, ATCs and Fighter Controllers. On this wiki, we aim to collect all important information, easily accessible for all new and old members, as well as any guest participants on our events.

====Language====
For practical reasons, we are a Swedish speaking community. If you don't know Swedish, but you are already proficient in your aircraft and you know somebody in the community who can vouch for you, you can still join our events as a guest and fly on his/her wing. Furthermore, we are always interrested in getting in contact with other communities for mutual scenarios and missions. Please do not hesitate to contact us if you are interested to set something up.
Generally, during events, all comms between flights and other agencies are in English, while comms within the flight are in Swedish.

==Important Links==

*[http://www.masterarms.se Master Arms Website]
*[https://discord.gg/hw3Aat4 Master Arms Discord]

==Wiki Content==

*[[New Member Guide]]
*[[Standard Operating Procedures]]
**[[Comms]]
**[[Lights]]
**[[Carrier Ops]]
**[[Airport Procedures]]
**[[Air-To-Air Operations]]
**[[Advanced Formations and Movement]]
**[[Mission Procedures]] ''(With comms example for airfield and mission procedures)''
**[[Training Server]]
*[[Technical Guides]]
**[[Technical Checklist]]
**[[Deck Spawning]]
**[[Mission Design Guide]]
*[[Aviation Guides]]
**[[Radials]]
**[[VFR Navigation]]
**[[Intercept]]
*[[Mission Files]]
**[[Mission Repository]]
**[[Basic Missions]]
**[[Training Missions]]
*[[Aircraft Syllabi]]
**[[Intro Flight]]
**[[F/A-18C Hornet Syllabus]]
**[[AJS 37 Viggen Syllabus]]
**[[F-16C Viper Syllabus]]
**[[A-10C Warthog Syllabus]]
*[[Mods]]
*[[Qualifications]]
**[[Basic Qualification]]
**[[Carrier Qualification]]
*[[Organization]]

AJS 37 Viggen Syllabus

2021-06-23T16:04:32Z

Urist: Mindre fix

''[[Home]] >> [[Aircraft Syllabi]] >> [[AJS 37 Viggen Syllabus]]''

==Intro Flight==

The intro flight is a newcomer's first familiarization flight. Its purpose is mainly to make sure all technical things work, make the newcomer feel welcome, go through some radio stuff and have some fun. It's not that important to learn any particular skills during the flight. That can come later. However, during this flight, the following topics are briefly covered.

* Cold start
* Changing radio presets
* Checking in
* Basic formation flying
* ARAK, Weapons Selector to ATTACK
* Formation Takeoff (2-ship)
* Fence In / Fence Out procedures
* BRAA calls and Fox 2 Launch
* "Fox" and "Splash" Calls
* Attacking with ARAK
* Straight-in Landing or Break

==Basic Flying==

===Starting Up===

* Cold Start using Quickstart Checklist

===Basic Navigation===

* Waypoint Navigation
* Autopilot Att, Höjd

===Landing===

* On-speed flying with correct Alpha
* Overhead break (Approach in runway direction, 700 km/h IAS, 500m. Break over runway, enter downwind and turn short final at runway threshold)
* Thrust reverse or aerodynamic braking

==Basic Combat==

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

* Radar to B-Scope or PPI
* Fire Rb 24 or Rb 74 Sidewinder (~2-4 NM)

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

* ARAK

===Basic Defence===

* Drop Flares and Chaff
* Evade enemy missile by putting it on your 3 o'clock or 9 o'clock (Evaluate in TacView)

==Intermediate Navigation==

* Radar navfix
* Visual navfix
* Change waypoint to target waypoint

==Intermediate Combat==

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

* Low drag pop-up dive bombing CCIP
* High drag level bombing CCIP
* Rb 04E
* BK 90