Thank you for your feedback Kemal.
Of course, ivac labels
shall be used at all times and unconditionally
MUST be used when there are nearby ATC(s). My phrasing was misleading.
On a side note, labels can be written for example
PIMA1Z,
PIM1Z or even just
1Z (obviously referring to the first waypoint of fpl), we all understand what it means. Should anyone be interested, CH DIV
listed a set of good(?) practices to "standardize" different controlling habits. Not necessarily relevant here.
Other side note about runway selection. According to LTBA AIP (
DEPARTURES item 6)). Pilots shall even be prepared for
very last minute runway changes (for example 35R to 35L) to increase departure rate. But sure, it sounds preferable in IVAO to stick to the runway assigned in the first place.
About squawk codes. A list like
this with "checkboxes" could really help. Again, it's CH and outdated I guess. I guess I saw a list of somewhere here (in Turkish :/ ) some times ago...
About initial altitudes for
all runways, my controlling habits and figures in the handysheet were base on the AIPs. Even when cleared to 5'000ft, many pilots (not relying on their fmc's database if they have any), will bust for example the (below)4'000ft limit over BA040 and BA041 during 1X 1E departures. If they're cleared higher, it looks even harder to coordinate with arrivals on a crossing path...
But sure, in the end, about all these (label, init FL, sqwk), I will stick to whatever you (TR-xxx's.) recommend on IVAO.
