The map above is ENR 6-2 from local AIP Romania, link to AIP.
The TMA NAPOC consists of two sectors: TMA NAPOC North and TMA NAPOC South, always one controller even IRL.
More than this, in the North of TMA there is a delegated airspace from ACC to APP (FL55-FL175) the same upper limit of TMA (FL175) due airways used by LRSM/LRBM ARR/DEP traffic. This information is not published on AIP, but the APP (LRCL_APP) does control the entire area.
Additional info
If needed, you can contact @georgeenciu, George being our vACC Director to confirm all the information here.
An explication to how sectors are defined below:
Data here in json file:
Data from GNG:
Is this a breaking change?
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist
[x] My change or addition follow the formatting standard of the project.
Description
Add TMA NAPOC
Motivation and Context
325
How to prove the effect of this PR?
Data is taken from GNG sectors data.
The map above is ENR 6-2 from local AIP Romania, link to AIP. The TMA NAPOC consists of two sectors: TMA NAPOC North and TMA NAPOC South, always one controller even IRL. More than this, in the North of TMA there is a delegated airspace from ACC to APP (FL55-FL175) the same upper limit of TMA (FL175) due airways used by LRSM/LRBM ARR/DEP traffic. This information is not published on AIP, but the APP (LRCL_APP) does control the entire area.
Additional info
If needed, you can contact @georgeenciu, George being our vACC Director to confirm all the information here.
An explication to how sectors are defined below:
Data here in json file:
Data from GNG:
Is this a breaking change?
Checklist