Flying in Poland

[Wade Williams 877539]

Hi all,

 

Late the other night I was going to attempt my first flight in Poland. I got all the charts (I think) and started diligently planning my flight. Unfortunately, time got away from me and when I looked up and saw what time it was, it was too late to start.

 

But I did have some questions for next time.

 

My flight was going to be from EPGD to EPWA.

 

The route I decided up on was:

 

DCT GRU ADLAR and then along the STAR for runway 29/33 (based on the expected wind)

 

Questions:

 

1) Is that an appropriate route?

 

2) How would I specify "Runway 29/33 STAR" in my flight plan

 

3) I noticed the ATC gave altitudes to some planes in meters and some in feet. I'm sure he was giving altitude in meters to the pilots speaking Polish, but if I'm flying a US-registered aircraft and have a very obvious American accent, will the controller automatically give me altitudes in feet?

 

4) I got my charts from:

 

http://www.ead.eurocontrol.int

 

I [Mod - Happy Thoughts]ume this is the best place?

 

5) Looking at the STAR for runway 29/33, I'm not sure what the procedure would be. I would [Mod - Happy Thoughts]ume sometime around the Medur Fix, I'd receive vectors. Is that correct? [Mod - Happy Thoughts]uming I was told to fly the STAR and not received any further instructions, what would be the proper procedure? Follow the STAR to Linin and hold?

 

6) I noticed some fixes like ADLAR, noted with a black triangle on the chart are in the NAV database. However, I noted that many other fixes, such as BADUX, LEBRO, etc (noted with a white triangle) were not in my NAV database. I could enter them by LAT/LONG obviously, but wondered if other pilots have the same issue or perhaps it's just my NAV database.

 

Thanks for any help.

 

Wade

[Krzysztof Szerszen 861225]

ATC in Poland never issues altitudes in metres to IFR a/c.

[Christopher Spencer 102404]

6) I noticed some fixes like ADLAR, noted with a black triangle on the chart are in the NAV database. However, I noted that many other fixes, such as BADUX, LEBRO, etc (noted with a white triangle) were not in my NAV database. I could enter them by LAT/LONG obviously, but wondered if other pilots have the same issue or perhaps it's just my NAV database.

ADLAR is an intersection, BADUX and LEBRO are GPS fixes. I'm not entirely sure what the difference between these are, but it may have something to do with it. Is your nav database up to date? All these are in mine (AIRAC 0713).

[Krzysztof Szerszen 861225]

ADLAR is an intersection, BADUX and LEBRO are GPS fixes.

 

They are all intersections. The difference is some are compulsory reporting points and some are not, but its irrelevant in radar environment.

 

1. Most appropriate route would be KRT UN133 GRU UL621 ADLAR. Although there are no waypoints between GRU and ADLAR along UL621.

 

2. You don't specify STAR in your fp.

 

3. Answered above.

 

4. "Best" is subjective, but its an appropriate source.

 

5. Yes, clearance limit is LIN. STAR may be terminated by radar vectors at any time.

 

6. See above.

[Sebastian Valdes 951169]

1. Most appropriate route would be KRT UN133 GRU UL621 ADLAR. Although there are no waypoints between GRU and ADLAR along UL621.

 

Worth to mention that KRT N133 GRU L621 ADLAR would be a more suitable route for props or any other aircraft non capable of reaching FL290 on this distance.

[Wade Williams 877539]

So, just to be clear, if all I file in my flight plan is:

 

KRT N133 GRU L621 ADLAR (I was in a turboprop)

 

then I would be expecting the controller to [Mod - Happy Thoughts]ign me a STAR at clearance time or enroute. If he does not, then I would fly to and hold at ADLAR until further instructions.