# Arrival

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

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

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

Sector Friesland is part of EDWW sectorgroup [Nord-B (EBG Nord-B)](https://knowledgebase.vatsim-germany.org/books/edww-bremen-radar/page/ubersichtskarte-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">POBZU Area</span>

<span class="mw-headline">During non-usage of ED-R 202 E, sector FRI delegates ATS within the POBZU area from FL195 to FL245 to sector ALR. This is to enable sector ALR better descents for EDDH inbound traffic. </span><span class="mw-headline">Sector FRI shall inform sector ALR when the delegation needs to be terminated due to the usage of ED-R 202E.[![EDDW POBZU Area.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-10/scaled-1680-/chrome-dhiho6l0ue.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-10/chrome-dhiho6l0ue.png)</span>

### <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">Sector Friesland will not provide top-down service. This is the task of the EDWW sector EIDW. </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 (GND-FL245), the TRA Weser may be active from FL80-FL245. Traffic is generally not approved to cross ED-R 202A and ED-R 202B. ED-R 202E may be crossed if the traffic is proceeding on one of the following airways: N125, Y200, M105 and T968. All TRA priority airways can be displayed in the EDWW Euroscope Package (MIL MAPS).</span>

<span class="mw-headline">Additionally, ED-R 302 (whole TRA) or ED-R 302B (sub-sector) may be active above FL245.</span>

<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, 202E, 302B or 302 all SOFED departures shall not be used. Traffic shall be routed via OTEXE N125 SOFED instead. </span></p>

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

## Arriving Traffic to EDDW

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

Traffic inbound to EDDW will be transferred descending to FL110 from EDWW and descending to FL250 from EDYY. 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 [HAME/HAMW](https://knowledgebase.vatsim-germany.org/books/edww-bremen-radar/page/ubersichtskarte-ebg-nord-a) and [HAN](https://knowledgebase.vatsim-germany.org/books/edww-bremen-radar/page/ubersichtskarte-ebg-sud) to avoid uncoordinated sector entries.

EDYY sector JEV is responsible for separation to outbound traffic on airway N125. For separation purposes, EDYY sector JEV may request a lower level from EDWW sector FRI.

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 switch automatically frequency from Tower to EDWW. Traffic via BASUM, ERLAD, NIE, GESTO and WSN shall be transferred to EDWW ACC sectors according to [LOP EDWW para 3.9.3](https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/lop-bremen-acc). Traffic via SOFED or OTEXE with an RFL above FL245 shall be transferred to EDYY UAC sector JEV according to [LoA EDWW-EDYY para 3.5.1](https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/maastricht-uac-bremen-acc). Traffic via SOFED or OTEXE with an RFL below FL245 shall be transferred to EHAA ACC.

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

<p class="callout info">When workload permits, sector ALR shall offer sector FRI to issue a higher level than FL100. In this case,  
sector FRI is responsible for keeping aircraft clear of HAME/HAMW.  
</p>

<p class="callout warning">When coordinating a higher flight level with sector EMS for flights with ADEP EDDW via ERLAD, NIE and BASUM, sector FRI is responsible for separation to sector ALR. Sector EMS is responsible for separation to sector HAN.</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.

## Enroute Traffic

Due to the sector partially reaching up to FL245, en-route traffic may be expected. Primarily, traffic will fly from west to east (airway M105) or from east to west (airway N125).

<p class="callout info">For traffic via EEL to the EHAA FIR, sector Friesland shall generally use the following flight levels: FL240, FL200, FL160, FL120 and FL80. Any deviation from this shall be coordinated with the station responsible for EDWW sector EIDW. </p>

### Emden (EDWE) and Wilhelmshaven (EDWI)

When online, Wittmund Radar will provide ATC service for traffic from/to Emden and Wilhelmshaven. If Wittmund Radar is offline, the station responsible for EIDW will take over all duties.

In general, inbound traffic shall be transferred to Wittmund Radar at an altitude of 5000 ft. An early handoff is required, so Wittmund Radar has enough time to clear the approach.

Departing traffic from EDWE, EDWI will be transferred to sector FRI at either 4000 ft or 5000 ft. For traffic out of EDWE, EDWI and EDWF via EDWW sector ALR, Friesland shall coordinate the transfer level individually.

### Groningen (EHGG)

It is possible, that IFR traffic will approach EHGG via sector Friesland. Inbound traffic shall be transferred inbound DOBAK at FL70 to EHGG APP. Outbound traffic from EHGG via DOBAK will be cleared to FL60 from EHGG APP.