Within the scope of the pan-European network FRA initiatives, Polish Air Navigation Services Agency (PANSA) will implement permanent Free Route Operations from 28 FEB 2019. The FRA within the airspace of Warszawa FIR, Poland is named POLFRA.
On the following website the documents related to the implementation of POLFRA will be published by PANSA.
All the materials on the page are not the official aeronautical publications and should not be used for operational purposes. Please consult AIP Poland for final data.
A specified airspace within which users may freely plan a route between a defined entry point and a defined exit point, with the possibility to route via intermediate (published) waypoints, without reference to the ATS route network, subject to airspace availability. Within this airspace, flights remain subject to air traffic control.
FRA Horizontal Entry Point (E)
A published significant point on the horizontal boundary of the Free Route Airspace from which FRA operations are allowed. The FRA relevance of such points is included in ENR 4.4 columns as (E).
FRA Horizontal Exit Point (X)
A published Significant Point on the horizontal boundary of the Free Route Airspace to which FRA operations are allowed. The FRA relevance of such points is included in ENR 4.4 columns as (X).
FRA Intermediate Point (I)
A published Significant Point via which FRA operations are allowed. Intermediate points may be used to connect FRA operations to ATS Route Network. The FRA relevance of such points is included in ENR 4.1/4.4 columns as (I).
FRA Arrival Connecting Point (A)
A published Significant Point to which FRA operations are allowed for arriving traffic to specific aerodromes. The FRA relevance of such points is included in ENR 4.4 columns as (A).
TIME:
POLFRA in Warszawa FIR is applicable H24.
LATERAL AND VERTICAL LIMITS OF POLFRA:
POLFRA comprises the controlled area of the Warszawa FIR, from FL095 to FL 660, and additionally delegation of ATS: S OF DESEN, except the airspaces listed below:
AIRSPACE CLASSIFICATION:
POLFRA in Warszawa FIR is implemented only in Class C airspace.
Eligible flights are all flights that are intending to operate within the vertical and horizontal limits of POLFRA, regardless of the phase of flight (overflights, arriving or departing to/from local airports or to/from airports situated in close proximity of POLFRA).
Within POLFRA airspace users are allowed to plan user preferred trajectories using significant points (see ENR 4.1 and ENR 4.4) under special conditions and rules laid down in AIP and RAD.
Within POLFRA relevant significant points are considered as FRA Horizontal Entry (E), FRA Horizontal Exit (X), FRA Intermediate (I), FRA Arrival Connecting (A) and FRA Departure Connecting (D) Points, as described in ENR 4.1 / ENR 4.4.
Eligible flights shall flight plan via FRA relevant points according to the table below.
From | To | Remark |
---|---|---|
FRA Horizontal Entry Point (E) | FRA Horizontal Exit Point (X) | Flight plan direct or via one or several intermediate points. |
FRA Arrival Connecting Point (A) | ||
FRA Intermediate Point (I) | ||
FRA Horizontal Departure Connecting Point (D) | FRA Horizontal Exit Point (X) | |
FRA Arrival Connecting Point (A) | ||
FRA Intermediate Point (I) | ||
FRA Intermediate Point (I) | FRA Horizontal Exit Point (X) | |
FRA Arrival Connecting Point (A) | ||
FRA Intermediate Point (I) |
In POLFRA there is no limitation on the number of FRA Intermediate Points (I) and DCTs used in field 15.
Within POLFRA there is no limitation on the maximum DCT distance.
Flights shall not be planned closer than 5NM to the published POLFRA border.
It is mandatory to insert a FRA Horizontal Entry/Exit Point in the flight plan when entering/exiting POLFRA Area except for traffic entering/exiting to/from FIR EPWW via TMAs.
The ATS route network within FIR Warszawa remains available for flight planning and is mandatory to cross TMAs above FL095 and the following areas published in ENR 2.1.2: CTA 01/CTA 02/CTA 03/CTA 04/CTA 05.
Entering the POLFRA by departing traffic shall be planned via:
Exiting the POLFRA by arriving traffic shall be planned via:
Mandatory connecting routes should be used for flight planning of departing/arriving traffic from/to airports published in ENR 3.5.
Recommended connecting routes are optional for flight planning of departing/arriving traffic from/to airports published in ENR 3.5. If in line with POLFRA rules other flight plans will be accepted.
The Flight Level Orientation Scheme (FLOS) applicable within POLFRA corresponds to the current Table of Cruising levels published in ENR 1.7.
Flight planning is not permitted through active restricted airspace, unless otherwise stated in FUA restrictions.
In order to correctly manage flight planning validation process in POLFRA all restricted areas above FL095 are associated with corresponding FBZ (Flight Buffer Zone) and/or relevant FUA restriction. All active restricted areas and FBZs will be published in EAUP/EUUP on NOP portal and should be used for proper flight planning validation.
EAUP/EUUP should be considered the main source for FPL purposes to notify airspace users about the status of airspace structures. The EAUPs/EUUPs update automatically the Network Manager CACD, therefore its information is used by IFPS for flight planning validation purposes.
Airspace Users shall plan their trajectory around airspaces that are not available for civil operations as published by EAUP/EUUP or NOTAM by using FRA Intermediate points published in ENR 4.1 / ENR 4.4.
All POLFRA constrains, exceptions and restrictions, are published via the RAD and promulgated in accordance with ENR 1.10.
Polska Agencja Żeglugi Powietrznej
ul. Wieżowa 8, 02-147 Warsaw
Informacje kontaktowe:
e-mail: info@pansa.pl
tel.: + 48 (22) 574 57 06
We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.
To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the website is accessible to all people: blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.
This website utilizes various technologies that are meant to make it as accessible as possible at all times. We utilize an accessibility interface that allows persons with specific disabilities to adjust the website’s UI (user interface) and design it to their personal needs.
Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the website’s HTML, adapts Its functionality and behavior for screen-readers used by the blind users, and for keyboard functions used by individuals with motor impairments.
If you’ve found a malfunction or have ideas for improvement, we’ll be happy to hear from you. You can reach out to the website’s operators by using the following email
Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting with screen-readers are able to read, comprehend, and enjoy the website’s functions. As soon as a user with a screen-reader enters your site, they immediately receive a prompt to enter the Screen-Reader Profile so they can browse and operate your site effectively. Here’s how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:
Screen-reader optimization: we run a background process that learns the website’s components from top to bottom, to ensure ongoing compliance even when updating the website. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.); validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process scans all of the website’s images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen-reader mode on as soon as they enter the website.
These adjustments are compatible with all popular screen readers, including JAWS and NVDA.
Keyboard navigation optimization: The background process also adjusts the website’s HTML, and adds various behaviors using JavaScript code to make the website operable by the keyboard. This includes the ability to navigate the website using the Tab and Shift+Tab keys, operate dropdowns with the arrow keys, close them with Esc, trigger buttons and links using the Enter key, navigate between radio and checkbox elements using the arrow keys, and fill them in with the Spacebar or Enter key.Additionally, keyboard users will find quick-navigation and content-skip menus, available at any time by clicking Alt+1, or as the first elements of the site while navigating with the keyboard. The background process also handles triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus drift outside of it.
Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers), both for Windows and for MAC users.
Despite our very best efforts to allow anybody to adjust the website to their needs, there may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating and improving its options and features, and developing and adopting new technologies. All this is meant to reach the optimal level of accessibility, following technological advancements. For any assistance, please reach out to