|Description||It appears, that 124thATC is detecting a SID, however does not find and communicate the related runway (IFR clearance and later also taxi instructions), causing further problems, when approaching the correct runway (according to charts), but getting no possibility to contact tower, as it seems, that 124thATC actually does not know the runway (or maybe uses some wrong runway not matching the SID).|
|Steps To Reproduce||Following flight LSZH to LIPZ can be used to reproduce the problem:|
GERSA URNAS KELIP SOPER PELAD RESIA GIGGI TAGIP ADOSA ALBET
When getting the IFR clearance, we will get a GERSA1C departure assigned. 124thATC is also saying the word "runway", but followed by no number. Anyway, be checking the airport charts we will find out, that this departure route is related to runway 10. So everything is prepared and set for that runway and departure. Later, when getting the taxi clearance, 124thATC will only give you the clearance "taxi to runway via taxiway" (also giving no runway number). Finally, when approaching runway 10 (which has to be the correct one according to the charts), there will be no possibility to contact tower (probably as 124thATC does not know, which runway and holding point to go to). For testing I also taxied around the whole airport (all 3 runways, each two starting points), but could not find any point which would activate the communication dialogue with tower.