FUA is short for the Flexible Use of Airspace; it is an airspace management concept, according to which airspace should not be determined as completely civil nor completely military, but it should be considered as a continuum and used flexibly on a day-to-day basis.
ASM is short for Airspace Management; it is a function of planning with the main aim of enabling the maximum utilization of available airspace as a continuous whole, taking into consideration the real short-term needs of different civil and military airspace users (e.g. airline companies, the military, private business aircraft, aero clubs, companies performing aerial work…).
In order to facilitate planning and the utilization of airspace, ASM is based on three levels:
ASM1 – Strategic level
ASM2 – Pre-tactical level
ASM3 – Tactical level.
AMC POLAND executes tasks on Airspace Management level 2 and level 3.
UTC is the abrreviation of Coordinated Universal Time, used in RQA/AUP/UUP.
Polish time zone:
Airspace request shall be sent to ASM2 according to the following rules:
(RQA message typ
EPXX ICAO code /sending unit
20/11/2018 06:00 – 21/11/2018 06:00 validity period
19/11/2018 09:00 time of transmission
001 TRA59 A055 F105 11:00 12:00 EPBK PJE requested area parameters.
Always add name and contact details on the person responsible for the activity of areas. )
AUP – Airspace Use Plan is an ASM notifying the daily decision of the Airspace Management Cell on the temporary allocation of airspace within its jurisdiction for a specific time, by means of the standard message format.
UUP – Updated Airspace Use Plan is an ASM message of the NOTAM status issued by the AMC to update and supersede an AUP messages or previous UUP information.
UUP can not introduce additional restrictions in uncontrolled airspace of class “G”.
MESSAGE TYPE | AUP |
SENDING UNIT | AMC POLAND |
VALIDITY PERIOD | D/0600 D+1/0600 |
TIME OF TRANSMISSION | D-1/1400 |
ALPHA – LIST OF AVAILABLE CATEGORY 2 CDRS
NUMBER | DESIGNATOR | FLIGHT LEVEL BLOCK | PERIOD OF USE | REMARKS |
BRAVO – LIST OF UNAVAILABLE ATS ROUTES, DCT, AND CATEGORY 1 CDRs
NUMBER | DESIGNATOR | FLIGHT LEVEL BLOCK | PERIOD OF UNAVAILABILITY | REMARKS |
CHARLIE – MANAGEABLE AREAS (AMA)
NUMBER | DESIGNATOR | FLIGHT LEVEL BLOCK | PERIOD OF USE | RESPONSIBLE UNIT | FUA/EU RESTRICIONS* | REMARKS |
01 | TRA59 | A055 | F105 | EPBK | Y | PJE |
DELTA – NON AMC-MANAGEABLE AREAS (nAM)
NUMBER | DESIGNATOR | FLIGHT LEVEL BLOCK | PERIOD OF USE | RESPONSIBLE UNIT | FUA/EU RESTRICIONS* | REMARKS |
01 | R40A | GND | F155 | ZZZZ | y | see aip |
ECHO – LIST OF UNAVAILABLE SIDS AND STARS
NUMBER | DESIGNATOR | FLIGHT LEVEL BLOCK | PERIOD OF UNAVAILABILITY | REMARKS |
FOXTROT – INFORMACJE DODATKOWE
A.) FREE TEXT INFORMATION
* RESTRICTIONS – 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.
All POLFRA constrains, exceptions and restrictions, are published via the RAD and promulgated in accordance with ENR 1.10.
The users of the airspace elements, which are not in collision with controlled airspace only confirm their usage 30 minutes before its real time activation.
Areas colliding with controlled airspace (look column remarks: “CLN”) must be coordinated with ASM3 on the day of operation 1 hour before planned activation of an element and receive clearance.
more information AIP ENR 2.2.2
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