Jump to content

Andrew H - 948774

ATS Staff
  • Posts

    94
  • Joined

Posts posted by Andrew H - 948774

  1. Hi all,

     

    I know there have been changes to RNAV SID/STARs at a few places, but wasn't aware of any changes at SY.

     

    Quite few people have been asking me for DEENA7, MARUB6 etc. advising their AIRAC is updated. I can't find these charts when I look at the current DAPs or SUP on the Airservices website. Could someone help show me where these new procedures for SY are located?

     

    Thanks

  2. Hey, just curious how we are supposed to report cloud if it is above 5000.

     

    vMATS 2.1.2.3

    i) [CLOUD (cloud layers below 5000 FT or highest MSA) FEW or

    SCATTERED or BROKEN or OVERCAST (layer base) FEET] or

    [VERTICAL VISIBILITY (number) FEET]

     

    Would "vis gt than 10 km, sh in area, no significant cloud below 5000" be appropriate?

     

     

  3. Thanks to the pilots and ATC for a great turn out on Australia Online tonight. Pretty much sustained traffic most of the night with people opting for some interesting airwork flights as well. The view from BN-TBP as the sequence started to wind down...

     

    Hopefully the interest in Aus Online continues!

     

    ybcs_aus_online.thumb.jpg.12d3b3831edb797916c43293e07ff9ad.jpg

  4. Very interesting feedback. In regards to issuing FF times to the pilot, in an ideal world this would be a great way of ensuring accurate crossings are met. Maybe some pilot education in briefing documents about how to achieve this/stressing the importance of using real world time for these events would assist this. I tried issuing FF times to aircraft at the start but they usually missed it by a few minutes, so I gave up with that.

     

    By the same token, meeting FF times on my own was also a challenge. I found that using the route probe function in ES told me the crossing time but that was based on the groundspeed in the cruise and didn't account for changes as they descended. I'd try and stretch/shorten people up/speed change but it was hard to be accurate all the way. Is there some rule of thumb that helps with factoring this in?

     

    For these kinds of events, would it help to be more "free" with the sequence and build in bigger gaps just as a standard thing. I wonder if running a tight sequence is just not a good idea given all the accumulated errors that build up online, and if we had bigger gaps there would be more roomfor the TMA to play with?

     

    All that said, panic is the name of the game and it certainly lived up to its reputation! I found managing the holds with 10+ aircraft was a definite challenge and as I watched two people hurtle towards each other at FL370, I quickly learnt the MAKKA and CULIN holds aren't really separated!

     

    Thanks David for your efforts.

  5. VATPAC staff,

     

    I'm writing to seek clarification on the bookings policy.

     

    Is the overriding principle still, as it used to be, one of "first come, first served"?

     

    During tonight's milk run event I was asked on several occasions to change positions as they had been reserved in advance. The first time I did so, not

    wanting to create a problem but eventually realized if it continued I'd have to pack up my bat and ball and go home. As I later discovered, all positions were reserved the bookings page.

     

    I can certainly understand why certain members would be annoyed, but from my perspective things could be perceived as annoying also. I don't use thebooking system. I have some free time, look at VatSpy, see some traffic, and log on. This is how I've always done it. If bookings are an unquestionable reservation then these members might find themselves frozen out of weekly events.

     

    However, if a booking is to be taken as not just an intention to control but a solid reservation, then can I suggest we delete section 1 of the bookings policy. Otherwise, some clarification is needed on just what a booking means.

     

    Thanks in advance,

     

    Andrew

  6. I have just been testing out GVCCS with another controller in preparation for this evening and I have found a little problem. The profile filthat we have been given doesn't always include the full frequency for each position, eg. BN-ARL appears as 124.8 rather than 124.800. Without changing the frequencies to include the "00" at the end I was unable to see the other controller as online.

     

    To change the frequency you need to click "ROLE ALLOC" at the bottom of the screen, then edit the frequency and press OK.

     

    I hope the other controllers will be using this too - it's a great little program! :)

  7. first panic stations for me also (believe it or not..) not used to flying with the additional atc, viz sy app(n), sy app(s), director(s), flow, et al.

     

    Inbound from ymml, could someone provide a rough guide to the sequence of control positions i will encounter? (from bik on..).

     

    ml-bik_ctr 125.00

    sy-s_app 128.30

    sy-d_app 126.10

    sy_twr 120.50

  8. 05L/25R still gets used (or has been recently) during runway works on the "real" runway. I think Airservices NZ keep it up their sleeve for contingencies. If it had been forever deactivated the main runway would be renamed 05/25 and loose the R/L designators.

     

    Jackson

     

    I am pretty sure that 05L/25R has had the runway markings removed and now looks like a taxiway. Maybe they are keeping the current runway designator to accomodate the parallel runway to be built north of the terminal. http://202.175.135.195/AirportInformation/Airport-developments/Northern-runway.aspx

  9. The plan seems to come unravelled in the sequencing between QFA953 and QFA154. Even after QFA154 is given a 'minimum clean' instruction his speed doesn't change much at all...I'd assume because on that STAR he doesn't have much room to slow and descend while remaining on profile. Perhaps an earlier action like vectoring QFA154 on to a wider base leg or even just leaving him on the STAR and widening the QFA953 who is already on vectors. I'd probably prefer the latter as vectoring just makes more work. Consequently QFA154 appears to intercept the ILS pretty high and fast and catches up on the one in front very quickly.

     

    The other issue comes about from using the crossing runway configuration and ensuring 5nm between aircraft at the runway intersection (conflict for VOZ1212). Crossing runways can be hard to sequence for at the best of times (I've had this problem myself) and was probably much harder with the TMA split between two controllers.

     

    As Luke said...not laying blame with anyone! I was on ML-HUM and had my fair share of "issues" on the night. Next time I think I'll learn how to use Maestro and volunteer to do FLOW. We could have used one...

×
×
  • Create New...