# Departing Traffic

<p class="callout success"><span lang="EN-US" style="mso-ansi-language: EN-US; mso-bidi-font-weight: bold;">We ask all pilots to also read the [General section](https://knowledgebase.vatsim-germany.org/books/airports-langen-fir-edgg/page/general-VGN "EDLV Pilotbriefing General") with **information relevant to all pilots**.</span></p>

### <span lang="EN-US" style="mso-ansi-language: EN-US; mso-bidi-font-weight: bold;">Preparation</span>

<span lang="EN-US" style="mso-ansi-language: EN-US; mso-bidi-font-weight: bold;">A thorough preparation is important for any flight. We ask you to **conduct a thorough briefing to avoid delays and keep it fun for everyone**.</span>

##### <span lang="EN-US" style="mso-ansi-language: EN-US; mso-bidi-font-weight: bold;">Route planning</span>

When planning a route via SimBrief, please use routes with the Eurocontrol icon when available, as those will generally be valid.

[![Eurocontrol SimBrief.jpg](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-04/scaled-1680-/eurocontrol-simbrief.jpg)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-04/eurocontrol-simbrief.jpg)

<p class="callout info">When filing an invalid flight plan, you will usually have to **file a completely new flight plan** before ATC can issue your enroute clearance.</p>

##### SID assignment

If there is no SID leading to the first waypoint of your flight plan, **please check which AIRAC you are using** - if your AIRAC cycle is too outdated, it might take some time until the controllers can coordinate a solution for you. Please also make sure you are **complying with the following restrictions** that exist for some of these waypoints.

<table border="1" id="bkmrk-waypoint-restriction" style="border-collapse: collapse; width: 100%;"><colgroup><col style="width: 17.0581%;"></col><col style="width: 82.9419%;"></col></colgroup><tbody><tr><td class="align-center" style="background-color: rgb(194, 224, 244); border-color: rgb(149, 165, 166); vertical-align: middle;">**Waypoint**  
</td><td class="align-center" style="background-color: rgb(194, 224, 244); border-color: rgb(149, 165, 166); vertical-align: middle;">**Restrictions**  
</td></tr><tr><td class="align-center" style="background-color: rgb(236, 240, 241); border-color: rgb(149, 165, 166); vertical-align: middle;">**SONEB**  
</td><td class="align-left" style="background-color: rgb(255, 255, 255); border-color: rgb(149, 165, 166); vertical-align: middle;">only for flights with requested **min. FL140**  
</td></tr></tbody></table>

### Enroute Clearance

Clearance requests in Germany are very short. Please **avoid unnecessarily long clearance requests** to reduce frequency congestion.

> **Pilot:** Niederrhein Tower, Ryanair 7XQ, stand 4, request enroute clearance, information N.

#### Datalink Clearance (DCL)

In contrast to the real world, on Vatsim we offer datalink clearance (DCL/PDC) at Niederrhein using the [Hoppie ACARS system](https://www.hoppie.nl/acars/ "Hoppie ACARS"). The station code is **EDLV**. If your aircraft does not have a direct integration of the Hoppie system, you can also use [easyCPDLC](https://github.com/quassbutreally/EasyCPDLC "easyCPDLC GitHub page").

### Startup

Startup approval is the "go" from the controller's side to start your engines. It is also an **assurance that you will be cleared to start moving within the next 20 minutes**. It can be requested and approved together with pushback.

### Pushback

Only request pushback if you are actually ready to start pushing back. If you take longer than **1 - 2 minutes to start moving**, ATC might have to cancel your pushback clearance to avoid delays for other pilots.

Keep in mind that some all positions on Niederrhein's apron except for stands 1 thru 9 are **taxi-out stands**. If you are parked on one of these taxi-out stands, you won't need a pushback.

<p class="callout warning">If you are unsure about your pushback instruction or unable to comply for any reason, **hold position and inform ATC immediately**.</p>

### Taxi

While Niederrhein's layout is relatively simple, it is still important to conduct a **thorough briefing of expected taxi routes** as well as **correct taxiing**. To avoid delays for yourself and other users, **start taxiing as soon as possible after receiving your taxi clearance** and **request taxi in a timely manner after your pushback**.

<p class="callout warning">If you are unsure about your taxi instructions, **hold position and inform ATC immediately**.</p>

### Takeoff

Niederrhein has only one runway which needs to be used for both departures and arrivals. While there is usually not too much other traffic, it is still important to **begin your takeoff roll as soon as you receive your clearance** and be prepared for immediate takeoff clearances. If you take too long, **ATC might have to cancel your takeoff clearance** and issue a go around for an arriving aircraft.

<p class="callout info">Intersection departures are not possible at Niederrhein. **All aircraft have to depart from full length**.</p>

##### <span lang="EN-US" style="mso-ansi-language: EN-US; mso-bidi-font-weight: bold;">Auto-handoff</span>

<span lang="EN-US" style="mso-ansi-language: EN-US; mso-bidi-font-weight: bold;">Niederrhein utilizes an auto-handoff procedure for IFR departures where **Tower will not hand off outbounds to the approach controller**. The current airborne frequency will always be noted in the ATIS.</span>

<p class="callout danger"><span lang="EN-US" style="mso-ansi-language: EN-US; mso-bidi-font-weight: bold;">Contact the airborne frequency **immediately when airborne** unless explicitly told to remain on Tower frequency.</span></p>