|
Bankstown SID
Just noticed a new AIP SUP has been issued - the new Bankstown 3 SID has been superseded (before it even comes into effect on 3 June) with an even newer Bankstown 4 SID to come into effect on 1 July. :rolleyes: Similarly for other (former) GAAP aerodromes.
There is now a requirement to ensure your own terrain clearance while turning on to a heading of 290 before contacting Departures for vectors. And here was me thinking that a SID was designed (to quote AIP ENR 1.5 section 10.1.1 (AL/63)) "to satisfy ... obstacle clearance requirements"! :ugh: The new SID (and two attempts at getting it right) hardly fills one with confidence ... |
ensure your own terrain clearance On a SID?.....???.....Is this April 1st? |
I don't get it either ...
While not OCTA, I suppose below 1,500FT you're in non-radar Class D (since BK tower only has the situation display) :confused:. And I suppose it is possible that, off runway 29 in particular, an aircraft might be OCTA outside the zone because it has not managed to climb to 2,500FT by the zone boundary. Thing is - we've been getting airborne for years off rwy 11 on the SID, starting a left turn at 500FT on to our assigned heading of 290, and lo' and behold not hitting any terrain or obtacles on the way. Even more straightforward off runway 29. That won't change, even though someone has decided that the old SID is no good :ugh: Presumably, whoever designed the old SID got out their obstacle chart and worked out that, at the required climb gradient, we could safely do that - ie, to quote AIP ENR 1.1 section 10.3.2, we could be assigned a heading by ATC (usually 290) "to be flown after the initial take-off phase, as depicted on the Radar SID chart, to the minimum vectoring altitude" without risk of hitting anything stationary. Are they suggesting now that for all those years a Bankstown SID has been unsafe :confused:. Methinks not! The latest version - Bankstown 4 Departure - doesn't make any sense to me, particularly as a radar SID. If they're going to insist that "no vectors OCTA" (by which they might really mean "no vectors outside radar CTA") means the old SID has to go, then they should redesign it as one or more procedural SIDs (with alternative tracking points of the CN NDB, KAT NDB and RIC NDB). Once in Class C, identified and at or above the MVA, Departures can cancel the SID and give you a vector. That would make sense - but it is more complicated, and I still can't really see there is anything wrong with the old SID! Ted PS It used to be possible, sometimes, to get a right turn off runway 11 on the SID straight into the Sydney control zone. Seems that won't ever be possible anymore ... |
PS Isn't it a requirement, on an initial issue of a CIR, to demonstrate you can fly a SID? |
No requirement to demonstrate a SID (or STAR) in flight exists for initial issue |
Ted D Bear,
As far as I am aware all aircraft departing/arriving BK under "IFR" are part of the Sydney traffic sequence! It will be no longer just about geographical limitations and runway configurations. Do you really think Qantas etc are going to be happy about giving up a dep/arr slot so that a Duchess can depart BK?? I think not. Sure, in VMC, pilots can elect a "VFR departure" but what about when the weather is less than VMC?? If you require IFR to depart the control zone, expect lengthy delays at certain times during the day. :( On approach I'm guessing the same will apply if an instrument approach is required. That's how it's been explained to us in the Class D training package :eek: |
Bankstown 4 departure?
er.. http://www.airservicesaustralia.com....BKDP01-123.pdf Not according to this?! I don't get it. |
Bankstown 4 departure
Bankstown 4 departure? The Bankstown 3 departure is in turn replaced by the Bankstown 4 departure effective 1 July in AIP SUP H31/10: http://www.airservicesaustralia.com/...up/s10-h31.pdf. :\ |
Can't see what all the fuss is about?!:hmm:
|
One size does not fit all...
Why should aircraft in the real Class D CTRs be limited to 200KIAS within 4nm? Fair enough in an ex-GAAP with myriad bugsmashers everywhere, but not at YBAS, for example. An unnecessary restriction that will reduce flexibility and cost money. :=
|
| All times are GMT. The time now is 15:42. |
Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.