# Arrival

## <span class="mw-headline">Sectorization and Airspace</span>

### <span class="mw-headline">Sector Friesland</span>

<span class="mw-headline">[![FRI_2503.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2025-02/fri.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/fri.png)</span>

Sector Friesland is part of EDWW sector group [Nord-B (EBG Nord-B)](https://knowledgebase.vatsim-germany.org/books/edww-bremen-radar/page/overview-ebg-nord-b).

<table border="1" class="align-center" id="bkmrk-station-frequency-lo" style="border-collapse: collapse; width: 98.8889%; height: 297.969px;"><tbody><tr style="height: 29.7969px;"><td class="align-center" style="width: 32.125%; background-color: rgb(194, 224, 244); border-color: rgb(149, 165, 166); border-style: solid; height: 29.7969px; vertical-align: middle;">**Station**  
</td><td style="width: 15.375%; background-color: rgb(194, 224, 244); border-color: rgb(149, 165, 166); border-style: solid; vertical-align: middle; height: 29.7969px;">**Station ID** </td><td class="align-center" style="width: 20.75%; background-color: rgb(194, 224, 244); border-color: rgb(149, 165, 166); border-style: solid; height: 29.7969px; vertical-align: middle;">**Frequency**  
</td><td class="align-center" style="width: 31.625%; background-color: rgb(194, 224, 244); border-color: rgb(149, 165, 166); border-style: solid; height: 29.7969px; vertical-align: middle;">**Login**  
</td></tr><tr style="height: 29.7969px;"><td style="width: 32.125%; background-color: rgb(236, 240, 241); border-color: rgb(149, 165, 166); border-style: solid; vertical-align: middle; height: 29.7969px;">Friesland  
</td><td style="width: 15.375%; border-color: rgb(149, 165, 166); border-style: solid; vertical-align: middle; height: 29.7969px;">FRI</td><td style="width: 20.75%; border-color: rgb(149, 165, 166); border-style: solid; vertical-align: middle; height: 29.7969px;">124.800  
</td><td style="width: 31.625%; border-color: rgb(149, 165, 166); border-style: solid; vertical-align: middle; height: 29.7969px;">EDDW\_APP</td></tr></tbody></table>

### <span class="mw-headline">Airspace</span>

<span class="mw-headline">Bremen airport is surrounded by a class D (non-CTR) airspace up to FL65 (see picture). Below a class E airspace has been established reaching down to 1000 ft AGL. Above FL65 a Transponder Mandatory Zone (TMZ) exists up to FL100. VFR traffic is allowed to cross the TMZ without ATC clearance. Pilots must monitor frequency 124.800 (no initial call required) and squawk 4471. The squawk will indicate that the pilot crossing the TMZ is on the frequency. ATC may issue traffic information about arriving and departing IFR traffic when required. </span>

<span class="mw-headline">Arriving IFR traffic to EDDW will usually descend outside protected airspace. ATC shall provide traffic information about VFR traffic whenever possible. </span>

<span class="mw-headline">[![EDDW airspace.jpg](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-10/scaled-1680-/chrome-v4zc4kvu0j.jpg)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-10/chrome-v4zc4kvu0j.jpg)</span>

### <span class="mw-headline">Military AoRs</span>

<span class="mw-headline">Wittmund AoR (ETNT\_APP) and Nordholz AoR (ETMN\_APP) may be active. Parts of those military AoRs are within sector Friesland. When active, airspace within the AoRs will be delegated from sector FRI from GND to 5500 ft. Every movement between a military AoR and sector FRI is subject to individual coordination. Wittmund Radar and Nordholz Radar shall inform sector Friesland about the opening and closure of the military AoRs. </span>

<span class="mw-headline" style="color: rgb(53, 152, 219);">Sector Friesland will provide top-down service for ETNT, EDWE and EDWI where possible. Bremen sector Eider is responsible for the provision of top-down service at ETMN. </span>

<span class="mw-headline">[![EDWW ETNT AoR.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-05/scaled-1680-/msedge-1xmqbevapb.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-05/msedge-1xmqbevapb.png)[![EDWW ETMN AoR.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-05/scaled-1680-/msedge-dgf2p3etc4.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-05/msedge-dgf2p3etc4.png)</span>

### <span class="mw-headline">TRA Weser</span>

<span class="mw-headline">Within the western part of sector FRI, parts of TRA Weser may be active from FL80-FL245. Traffic is generally not approved to cross ED-R 202A and ED-R202B. Traffic may cross ED-R 202E on the following priority routes (see box below):</span>

<details id="bkmrk-tra-priority-airway-"><summary>TRA Priority Airway ED-R 202E</summary>

Traffic on the following routes may be generally approved for crossing ED-R 202E provided traffic information for traffic using the TRA is given:

- ANDIK M105 OPWOT
- MIZUH N125 BLUFA
- MALYK Z529 SUQIF
- SUQIF Z529 MALYK
- YEFAW Z595 REVLA
- APNOC Z45 OMEPA
- DOBAK DCT SUQIF
- ITMIZ DCT DOBAK
- ABDIM DCT ITMIZ
- REVLA DCT OKWEL
- SUQIF DCT ABFAD
- ABFAD DCT SUQIF
- ITMIZ DCT ABFAD
- ABFAD DCT ITMIZ

<p class="callout info">Note: Unless otherwise coordinated, traffic has to exactly proceed on the listed routes. Shortcuts through the TRA are not allowed. </p>

</details><p class="callout warning"><span class="mw-headline">Sector FRI shall inform Bremen Ground/Tower about the activity of TRA Weser. During the activity of ED-R 202A, 202B or 202E all SOFED departures shall not be used. Traffic shall be routed via <span style="color: rgb(53, 152, 219);">OKWEL</span> N125 <span style="color: rgb(53, 152, 219);">ITMIZ</span> instead. </span></p>

<span class="mw-headline">[![TRA Weser.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2025-03/image-5.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-10/tra-wesrer.png)</span>

### TRA Friesland

Within the northern part of sector FRI, parts of TRA Friesland may be active from FL80-FL245. Traffic is generally not approved to cross ED-R 201A and ED-R201C. Traffic may cross ED-R 201B on the following priority routes (see box below):

<details id="bkmrk-tra-priority-airway--1"><summary>TRA Priority Airway ED-R 201B</summary>

Traffic on the following routes may be generally approved for crossing ED-R 201B provided traffic information for traffic using the TRA is given:

- BEDUM N873 HUNQI
- MOXCI P174 KUBAT
- AMCUB N872 EEL
- KUBAT T200 BLUFA
- TEMLU DCT JUIST
- JUIST DCT ABFAD
- JUIST DCT GASTU
- OLWOF DCT JUIST
- ABFAD DCT KUBAT
- GASTU DCT KUBAT

<p class="callout info">Note: Unless otherwise coordinated, traffic has to exactly proceed on the listed routes. Shortcuts through the TRA are not allowed. </p>

</details>![TRA Friesland.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2025-03/image-4.png)

## Arriving Traffic to EDDW

### <span class="mw-headline" id="bkmrk-transitions-0">Managing inbound traffic</span>

<span style="color: rgb(53, 152, 219);">Traffic inbound to EDDW will be transferred descending to FL110 from EDWW. </span>The published STARs are not used. The clearance limits are VERED, PIXUR, EKROV and GIBMA. For further descents, sector FRI shall pay close attention to sectors [HAM](https://knowledgebase.vatsim-germany.org/books/edww-bremen-radar/page/overview-ebg-nord-a) and [HAN](https://knowledgebase.vatsim-germany.org/books/edww-bremen-radar/page/overview-ebg-sud) to avoid uncoordinated sector entries.

Usually, sector Friesland will use vectors to sequence traffic into EDDW. Alternatively, early directs onto the transition (e.g. DW555) can be coordinated with the surrounding sectors.

Due to the limited airspace available, sector Friesland may vector aircraft from the south to the northern downwind and vice versa, to generate extra track miles during periods of high traffic. Alternatively, the published transitions may be used to relieve the frequency. During 09-Ops either VERED09B (south downwind) or VERED09A (north downwind) can be used.

### <span class="mw-headline">Approach Types</span>

<span class="mw-headline">There are different published approach types available at EDDW. By default, the ILS Z approach will be used. All other approach types are on the pilot's request only. </span>

<table border="1" class="align-center" id="bkmrk-runway-available-app" style="border-collapse: collapse; width: 74.0741%; height: 148.984px;"><colgroup><col style="width: 33.3216%;"></col><col style="width: 33.3216%;"></col><col style="width: 33.3216%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td class="align-center" style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244); height: 29.7969px;">**Runway**  
</td><td class="align-center" style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244); height: 29.7969px;">**Available Approach Types**</td><td class="align-center" style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244); height: 29.7969px;">**Intercept Altitude**</td></tr><tr style="height: 29.7969px;"><td class="align-center" rowspan="2" style="border-color: rgb(149, 165, 166); height: 29.7969px;">09/27

</td><td class="align-center" style="border-color: rgb(149, 165, 166); height: 29.7969px;">ILS Z, LOC Z, RNP, VOR</td><td class="align-center" style="border-color: rgb(149, 165, 166); height: 29.7969px;">3000 ft</td></tr><tr><td style="border-color: rgb(149, 165, 166);">ILS Y</td><td style="border-color: rgb(149, 165, 166);">1700 ft (as published)</td></tr></tbody></table>

The ILS Z and ILS Y are approved for CAT III operations.

### <span class="mw-headline">Target Spacing</span>

The following target spacings shall be used between aircraft on the same final, except if wake turbulence separation is higher:

<table border="1" class="align-center" id="bkmrk-conditions-target-sp" style="border-collapse: collapse; width: 74.0741%; height: 59.5938px;"><colgroup><col style="width: 50.0835%;"></col><col style="width: 50.0835%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td class="align-center" style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244); height: 29.7969px;">**Conditions**  
</td><td class="align-center" style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244); height: 29.7969px;">**Target Spacing**</td></tr><tr style="height: 29.7969px;"><td class="align-center" style="border-color: rgb(149, 165, 166); height: 29.7969px;">Normal Operations</td><td class="align-center" style="border-color: rgb(149, 165, 166); height: 29.7969px;">6 NM (\*)</td></tr><tr><td style="border-color: rgb(149, 165, 166);">After coordination with Tower</td><td style="border-color: rgb(149, 165, 166);">3 NM</td></tr><tr><td style="border-color: rgb(149, 165, 166);">During Low Visibility Conditions</td><td style="border-color: rgb(149, 165, 166);">10 NM</td></tr></tbody></table>

<p class="callout info">(\*) Behind a Beluga XL (A337) landing on runway 27, Bremen Radar shall increase the target spacing as a backtrack is required to vacate the runway via taxiway C due to wing span limitation. The normal Beluga (A3ST) is not affected from this. </p>

## Departing Traffic from EDDW

Departing traffic from EDDW shall automatically switch frequency from Tower to EDWW. <span style="color: rgb(53, 152, 219);">Traffic transferred to EDWW ACC sectors according to [LOP EDWW](https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/lop-bremen-acc). </span>

Often traffic may be coordinated on a higher flight level with sector ALR, EID or EMS to avoid unnecessary level-offs.

#### <span style="color: rgb(53, 152, 219);">Special Procedure - SOFED SIDs</span>

<span style="color: rgb(53, 152, 219);">Beginning on March 20, 2025, the SOFED SIDs are no longer connected to airway N125 due to changes to the ATS routes. Nevertheless, SOFED SIDs will still be used for departures to the west. Traffic intending to use SOFED SIDs is requested to file "ABDIM DCT ITMIZ N125 ..." as the initial segment of the F-Plan route. Traffic will then be instructed to follow a SOFED SID and to then join ITMIZ when reaching ABDIM located on the SID. </span>

<span style="color: rgb(53, 152, 219);">[![SOFED SID AIRAC 2503.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2025-03/scaled-1680-/inkscape-owgoufmqnj.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2025-03/inkscape-owgoufmqnj.png)</span>

<p class="callout info"><span style="color: rgb(53, 152, 219);">It is to be expected that some pilots will file flight plans with the first waypoint "SOFED" instead of "ABDIM". This will still be considered as valid and Bremen Ground may clear SOFED SIDs nonetheless. Additionally, traffic may not follow the short cut to ITMIZ as instructed by Bremen Ground. It is highly recommended to coordinate shortcuts with sector Ems and Eider, especially when the route looks invalid.</span></p>

## VFR Traffic

### VFR Departures

<p class="callout info">Jet aircraft or any aircraft with an MTOM of more than 5700 kg shall follow a published IFR departure route under VFR conditions.</p>

By default, the Bremen Tower will instruct the aircraft to stay clear of airspace class D (non-CTR). Nevertheless, coordination may be required between Bremen Tower and Bremen Radar in case the pilots request further climb. In this case, Bremen Radar shall issue the approval to enter airspace D (non-CTR) to Bremen Tower directly.

### VFR Arrivals

<p class="callout info">Jet aircraft or any aircraft with an MTOM of more than 5700 kg shall follow published IFR arrival routes under VFR conditions.</p>

In this case, the arriving VFR traffic shall contact Bremen Radar latest 25 NM before approaching EDDW. Bremen Radar shall provide service for a practice approach VFR (e.g. via an ILS approach). An entry via published VFR arrival routes into the CTR is not possible.

## <span style="color: rgb(53, 152, 219);">Emden (EDWE)</span>

<span style="color: rgb(53, 152, 219);">Emden (EDWE) is an uncontrolled aerodrome located about 19 NM southwest of ETNT. Due to published IFR procedures, limited service has to be provided for IFR traffic:</span>

- <span style="color: rgb(53, 152, 219);">Approach clearance</span>
- <span style="color: rgb(53, 152, 219);">IFR clearance</span>

<p class="callout warning"><span style="color: rgb(53, 152, 219);">**When online, Wittmund Radar (ETNT\_APP) will take over all responsibilities for IFR traffic from/to Emden.** In this case, traffic shall be coordinated individually between Bremen Radar and Wittmund Radar. **Bremen Radar shall transfer arriving traffic early enough before reaching IAF for Wittmund Radar to clear the approach.** </span></p>

### <span class="mw-headline" style="color: rgb(53, 152, 219);">Approach Types</span>

<span class="mw-headline" style="color: rgb(53, 152, 219);">There is one published approach type available at EDWE: </span>

<table border="1" class="align-center" id="bkmrk-runway-available-app-1" style="border-collapse: collapse; width: 74.0741%; height: 59.5938px;"><colgroup><col style="width: 20.9266%;"></col><col style="width: 29.1363%;"></col><col style="width: 16.7413%;"></col><col style="width: 33.3216%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td class="align-center" style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244); height: 29.7969px;"><span style="color: rgb(53, 152, 219);">**Runway**</span>  
</td><td class="align-center" style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244); height: 29.7969px;"><span style="color: rgb(53, 152, 219);">**Available Approach Types**</span></td><td style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244);"><span style="color: rgb(53, 152, 219);">**IAF**</span></td><td class="align-center" style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244); height: 29.7969px;"><span style="color: rgb(53, 152, 219);">**Altitude at IAF**</span></td></tr><tr style="height: 29.7969px;"><td class="align-center" rowspan="2" style="border-color: rgb(149, 165, 166); height: 29.7969px;"><span style="color: rgb(53, 152, 219);">07/25</span>

</td><td class="align-center" style="border-color: rgb(149, 165, 166); height: 29.7969px;"><span style="color: rgb(53, 152, 219);">**RNP Z**</span></td><td style="border-color: rgb(149, 165, 166);"><span style="color: rgb(53, 152, 219);">**SUQIF**</span></td><td class="align-center" style="border-color: rgb(149, 165, 166); height: 29.7969px;"><span style="color: rgb(53, 152, 219);">**4000 ft**</span></td></tr><tr><td style="border-color: rgb(149, 165, 166);"><span style="color: rgb(53, 152, 219);">RNP Y (HEL)</span></td><td style="border-color: rgb(149, 165, 166);"><span style="color: rgb(53, 152, 219);">JUIST</span></td><td style="border-color: rgb(149, 165, 166);"><span style="color: rgb(53, 152, 219);">3000 ft</span></td></tr></tbody></table>



<span class="mw-headline" id="bkmrk-holdings-0" style="color: rgb(53, 152, 219);"></span>

<p class="callout info"><span style="color: rgb(53, 152, 219);">**The RNP Y is only available for helicopter traffic.** This approach is primarily used by helicopter traffic approaching from oil rigs located in the North Sea during IMC. This approach shall only be cleared when requested by the helicopter pilot. </span></p>

<p class="callout info"><span style="color: rgb(53, 152, 219);">As traffic will leave controlled airspace during the approach, traffic must proceed via the published approach procedures only! Arriving traffic shall be instructed to switch to Emden Information or 122.800 before reaching FAF. </span></p>

### <span class="mw-headline" style="color: rgb(53, 152, 219);">Departing Traffic</span>

<span class="mw-headline" style="color: rgb(53, 152, 219);">Departing traffic will request the IFR clearance on the ground. Traffic will depart at its discretion and shall be instructed to report when airborne. Departing traffic from EDWE shall be offered to switch frequency for taxi and departure to properly communicate with other (VFR) traffic at Emden. Departing traffic shall be transferred according to [LOP EDWW](https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/lop-bremen-acc). </span>

<p class="callout info"><span class="mw-headline" style="color: rgb(53, 152, 219);">JUIST departures are only available for helicopter traffic. In general, traffic shall only depart via published departure procedures. </span></p>

### <span class="mw-headline" style="color: rgb(53, 152, 219);">Emden Block Clearance Area</span>

<span style="color: #3598db;">To keep sufficient distance from EHGG APP for traffic on the published approach procedure for runway 07 at EDWE, the airspace within the "Emden Block Clearance Area" is permanently delegated from Eelde Approach to Bremen Radar/Wittmund Radar: </span>

<span style="color: #3598db;">[![Emden Block Clearance Area.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2025-02/scaled-1680-/msedge-d9o3j30tuw.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2025-02/msedge-d9o3j30tuw.png)</span>

## <span style="color: rgb(53, 152, 219);">Wilhelmshaven (EDWI)</span>

<span style="color: rgb(53, 152, 219);">Wilhelmshaven Jadeweser Airport (EDWI) is an uncontrolled aerodrome located about 14 NM southeast of ETNT. Due to published IFR procedures, limited service has to be provided for IFR traffic:</span>

- <span style="color: rgb(53, 152, 219);">Approach clearance</span>
- <span style="color: rgb(53, 152, 219);">IFR clearance</span>

<p class="callout warning"><span style="color: rgb(53, 152, 219);">**When online, Wittmund Radar (ETNT\_APP) will take over all responsibilities for IFR traffic from/to Wilhelmshaven.** In this case, traffic shall be coordinated individually between Bremen Radar and Wittmund Radar. **Bremen Radar shall transfer arriving traffic early enough before reaching IAF for Wittmund Radar to clear the approach.** </span></p>

### <span class="mw-headline" style="color: rgb(53, 152, 219);">Approach Types</span>

<span class="mw-headline" style="color: rgb(53, 152, 219);">There is one published approach type available at EDWI: </span>

<table border="1" class="align-center" id="bkmrk-runway-available-app-2" style="border-collapse: collapse; width: 74.0741%; height: 59.5938px;"><colgroup><col style="width: 20.9266%;"></col><col style="width: 29.1363%;"></col><col style="width: 16.7413%;"></col><col style="width: 33.3216%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td class="align-center" style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244); height: 29.7969px;"><span style="color: rgb(53, 152, 219);">**Runway**</span>  
</td><td class="align-center" style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244); height: 29.7969px;"><span style="color: rgb(53, 152, 219);">**Available Approach Types**</span></td><td style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244);"><span style="color: rgb(53, 152, 219);">**IAF**</span></td><td class="align-center" style="border-color: rgb(149, 165, 166); background-color: rgb(194, 224, 244); height: 29.7969px;"><span style="color: rgb(53, 152, 219);">**Altitude at IAF**</span></td></tr><tr style="height: 29.7969px;"><td class="align-center" style="border-color: rgb(149, 165, 166); height: 29.7969px;"><span style="color: rgb(53, 152, 219);">02/20</span>

</td><td class="align-center" style="border-color: rgb(149, 165, 166); height: 29.7969px;"><span style="color: rgb(53, 152, 219);">RNP</span></td><td style="border-color: rgb(149, 165, 166);"><span style="color: rgb(53, 152, 219);">REVLA</span></td><td class="align-center" style="border-color: rgb(149, 165, 166); height: 29.7969px;"><span style="color: rgb(53, 152, 219);">4000 ft</span></td></tr></tbody></table>



<span class="mw-headline" id="bkmrk--13" style="color: rgb(53, 152, 219);"></span>

<p class="callout info"><span style="color: rgb(53, 152, 219);">As traffic will leave controlled airspace during the approach, traffic must proceed via the published approach procedures only! Arriving traffic shall be instructed to switch to Wilhelmshaven Information or 122.800 before reaching FAF. </span></p>

### <span class="mw-headline" style="color: rgb(53, 152, 219);">Departing Traffic</span>

<span class="mw-headline" style="color: rgb(53, 152, 219);">Departing traffic will request the IFR clearance on the ground. Traffic will depart at its discretion and shall be instructed to report when airborne. Departing traffic from EDWI shall be offered to switch frequency for taxi and departures to properly communicate with other (VFR) traffic at Wilhelmshaven. Departing traffic shall be transferred according to [LOP EDWW](https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/lop-bremen-acc). </span>

## Groningen (EHGG)

<span style="color: rgb(53, 152, 219);">IFR traffic may approach EHGG via sector Friesland. Inbound traffic shall be transferred at FL70 to EHGG APP. Outbound traffic from EHGG will be cleared to FL60 from EHGG APP. </span>