Kieran17

The unavailability of FL110 for cruise when the Area QNH is less than 1013 is due to the Transition Layer becoming squished in with the low QNH. If the Area QNH is less than 1013hPa, the vertical distance between A100 and FL110 is less than 1000ft (squished). If the Area QNH is 1013hPa (1013.25), the vertical distance between A100 and FL110 is 1000ft. If the Area QNH is Greater than 1013hPa, the vertical distance between A100 and FL110 is greater than 1000ft (fattened). Due to the squishing of the Transition Layer when the QNH is low (Transition Altitude and Transition Level less than 1000ft apart), cruising at FL110 is not available with an Area QNH less than 1013hPa. This squishing continues to happen as the Area QNH lowers, at less than 997hPa, there will be less than 1000ft between A100 and FL115. Example QNH table below: For QNH 1013 the Transition Layer is 1000ft thick. The higher the QNH goes, the thicker the Transition Layer becomes: at QNH 1017, the Transition Layer is 1120ft thick. As the QNH lowers, the Transition Layer becomes compressed, so a 'correction*' is applied. At QNH 1012, there is only 970ft between A100 and FL110, therefore, cruising at FL110 is no longer available and a 500ft 'correction buffer*' is added to the Transition Layer to ensure there is at least 1000ft between A100 and the next available Flight Level (FL115). The compression continues as the QNH lowers, and at QNH 996, there is 990ft between A100 and FL115, so the next 'correction*' value kicks in, FL115 is no longer available and the next available Flight Level is FL120. So, on a low QNH day, if the Area QNH is less than 997, cruising at FL115 is not available because there is less than 1000ft between A100 and FL115. If there were no corrections* applied to the Transition Layer, by the time the QNH reaches 979hPa, altitude A100 would be 20ft above flight level FL110. (*not an actual term, but I couldn't think of a better one) QNH Compression Correction Transition Altitude Layer Thickness Transition Level 1017 1120 0 A100 1120 FL110 1016 1090 0 A100 1090 FL110 1015 1060 0 A100 1060 FL110 1014 1030 0 A100 1030 FL110 1013 1000 0 A100 1000 FL110 1012 970 +500ft A100 1470 FL115 1011 940 +500ft A100 1440 FL115 1010 910 +500ft A100 1410 FL115 1009 880 +500ft A100 1380 FL115 1008 850 +500ft A100 1350 FL115 1007 820 +500ft A100 1320 FL115 1006 790 +500ft A100 1290 FL115 1005 760 +500ft A100 1260 FL115 1004 730 +500ft A100 1230 FL115 1003 700 +500ft A100 1200 FL115 1002 670 +500ft A100 1170 FL115 1001 640 +500ft A100 1140 FL115 1000 610 +500ft A100 1110 FL115 999 580 +500ft A100 1080 FL115 998 550 +500ft A100 1050 FL115 997 520 +500ft A100 1020 FL115 996 490 +1000ft A100 1490 FL120 995 460 +1000ft A100 1460 FL120 994 430 +1000ft A100 1430 FL120 993 400 +1000ft A100 1400 FL120 992 370 +1000ft A100 1370 FL120 991 340 +1000ft A100 1340 FL120 990 310 +1000ft A100 1310 FL120 989 280 +1000ft A100 1280 FL120 988 250 +1000ft A100 1250 FL120 987 220 +1000ft A100 1220 FL120 986 190 +1000ft A100 1190 FL120 985 160 +1000ft A100 1160 FL120 984 130 +1000ft A100 1130 FL120 983 100 +1000ft A100 1100 FL120 982 70 +1000ft A100 1070 FL120 981 40 +1000ft A100 1040 FL120 980 10 +1000ft A100 1010 FL120

Does anyone know if Wedgetail Aircraft still are operating? Their website seems to have been down for quiet a while and the facebook listing is about the same...

My previous beacon from a number of years ago was an ACR ResQLink which was used at an incident in regional Victoria a decade or so ago. Worked as advertised. I was in mobile phone coverage at the time, standing next to an emergency marker, however the site involved was about 1.5km away at the bottom of the hill. I activated the beacon and called 000 at the same time, dealing with 000 for an accident location that did not have an address was difficult. When they were told that the accident site was 1.5km west of the emergency marker, they were not able to put it onto their system, instead asking for a nearby road intersection or other address. I was on the phone to 000 for about 6 minutes to get the message through to them. By the time I was done with 000, I had two missed calls on my phone and answered on the third call that came shortly afterward from AMSA. They advised me that my beacon activation was detected and I confirmed intentional and gave them the details, they said they could see the location of the beacon, to which I advised that the accident site was 1.5km west, "no problem, keep your phone on and we'll call back shortly" they said. Seven minutes later they called back and said the helicopter is airborne at Warrnambool and on its way. HEMS4 arrived 30 minutes later. Following that I ended up doing a deal with the importer of the Ocean Signal rescueME PLB and bought 40 of them, and passed them on at cost price just to get more of them out there. Battery life in the beacons is finite, my first one was rated for 10 years, the second for 7 years. Within the rated life, the PLB will broadcast for a minimum of 24 hours (EPIRBs are 48 hours). They will broadcast on 406MHz which will include the encoded GPS data (get a GPS equipped version) which is detected by several satellites and downlinked to the JRCC as well as a low power 121.5MHz signal which can be used for aerial homing. When you get one, make sure you register it with AMSA. If you have a chance to look and feel before you buy, see how it goes getting the antenna up and turning it on one handed. If you fall while hiking and break your arm, will you still be able to activate it? When you buy one, keep it accessible. There'll be no point having a beacon in a bag in the back of the plane that you can't access (altitude above you, runway behind you etc). When ever I'm travelling away from town, I'll carry the PLB in the car/plane/kayak/backpack, including when I'm overseas (it'll work anywhere globally). You never know when you'll be driving down a county road away from mobile reception and come across a car crash, or worse, be involved on one. The life that your beacon saves may not be your own. Buy one (anywhere around $350 seems to be the mark), keep it accessible, save a life. Kieran

Hi everyone, I've recently acquired trike T2-2490. For about the last six years it has been on static display in a Paramatta school before they wanted to move it on to a new home. That's where I came in to snap it up. Now comes the task of trying to get it airworthy again. The wing is in good condition, but needs a replacement sail after sun exposure degradation... The first step that I am hoping to achieve is to get in contact with previous owner. I've contacted SAFA with an attempt to have them pass on a message, but haven't heard anything back yet, which brings me here. So what I know: -Former registered at T2-2490 -Deregistered in 2016 when it was given to a Parramatta school for use as a static display where it has been for the last five years -I expect it was based in the Sydney basin not entirely sure -Streak wing and Rotax 582 blue head (not the original engine for the base) -Base build in September 2002 Not sure if the previous owner is still around or if the log books still exist but I live in hope! If anyone has any leads it would be hugely appreciated. Kieran

You're welcome. I try to advocate for better change summaries being published at the AIRACs. Broad stroke summaries like this just don't cut it when there are significant changes, particularly when it refers to information removed without detailing what was removed and why, meaning a page by page comparison between versions is needed to keep track. We (country) can do better than this. Kieran

Doubled post removed

That section of website is out of date, not helpful that outdated information is still accessible, and if you google "mercy flight' it still directs to incorrect information on the CASA site. That page listed was last updated in February last year. In the update change summary it notes that this section of the website was supposed to be switched off after the Dec 2nd 2021 AIRAC. The new version of VFRG can be downloaded here https://www.casa.gov.au/search-centre/visual-flight-rules-guide The current and next versions of the AIP suite of docs can be downloaded here https://www.airservicesaustralia.com/aip/aip.asp The short version for the removal was they came to realise that "there is no regulatory basis for mercy flights' so it has been (disappointingly quietly) removed for the AIP docs. The only option left in a case that a mercy flight would have covered is to declare an emergency. RFDS pilot flying beyond flight and duty time limits to get their pax to hospital, declare a mayday. Landing five minutes after last light so your snake bitten pax can get to a hospital, declare a mayday (side note, in a case like this, tell ATC and we'll help out as best we can, need an ambulance to meet you, we'll arrange it). Kieran

CEO mentioned that "there's always the Mercy Flight Provisions", however these have been removed from AIP as 'there's no legislative base for them', so no, there are not Mercy Flight provisions available to be used anymore.

There is a difference between what FlightRadar24 and the Airservices systems will display because they are entirely separate systems. The link to the Airservices ADSB coverage maps show what the ATC system will see. In some areas this may be better than what FR24 is capable of, but in many areas, FR24 is capable of much better coverage due to a higher number of receivers provided by community input. In the way of a couple of examples: Kalgoorlie WA. ATC system nearest receivers are Leonora and Esperance, lowest level coverage at Kalgoorlie is around 10000-12000 feet. FR24 has a local receiver with coverage to the ground. Learmonth WA. ATC system has coverage to the ground, FR24 does not (not sure of actual coverage floor there but it didn't show RPT jets at around 5000ft when I was there the other week). This can provide a lead in to the question 'why can't ATC extend their network by using FR24?'. The answer to this the system integrity and redundancy requirements that need to be met in order to ensure its accuracy. There are very specific standards for this equipment. Each ADSB receiver site is not just one single receiver, but requires additional infrastructure to support it. Each site will have the antenna mast with two separate antennas with separate cabling feeding independent receivers. Each receiver is powered by a main power source with battery UPS backups capable of providing power for several days. There are also redundant signal paths for the data to travel to Melbourne/Brisbane centre via terrestrial and satellite links. As much as I would have loved to have better coverage in the ATC system, sadly the costs involved are not trivial. All this is to say, ADSB is a great tool, but don't expect that just because you can see it on FR24, ATC can see you on their screens.

I forgot to add in the last post, if you were instructed to follow the Cessna and you don't have them in sight, that's when you tell us. "ABC, you are number three, follow the Cessna on downwind" "Looking for traffic, ABC" Have a look for the Cessna, when you still can't see them: "Traffic not yet sighted, ABC" At this point you can expect a new instruction or an update on the position of the Cessna

No, there's no need. That can be one of the other reasons for the original transmission: we know you won't be able to see the Cessna, you're safe to continue what you're doing, expect to hear from us again soon. If you get to the point that you're ready for base and haven't heard anything from us, then give us a nudge. Maybe we forgot about you, maybe we're busy, maybe we don't want you turning yet. "ABC, ready for base" "ABC, continue approach/turn base" (same thing) or "maintain downwind". If we want to know whether you can see the Cessna or not, we'll say so. "ABC, number three to a Cessna on downwind, expect base turn on my call, report traffic in sight" "Looking/traffic in sight, ABC"

Just the callsign will do thanks. "ABC". What you have been given is some information and an expectation, no clearance. It may open up some flexibility if you have the Cessna in sight and let us know "Cessna in sight, ABC", in which case you may get "ABC, follow the Cessna" (an instruction requiring readback). As it's only an expectation that's been given, it may change and doesn't need a readback. If wanted to lock it in, you'd be told to "maintain downwind". As for why we'd say this, it can come down to a few possible reasons but it's primarily done to keep you on the loop of what the plan is (and reduce the chance of you messing it up...). 1. We may be planning on getting a departure away between said Cessna and yourself, and want to buffer the spacing. 2. We may know something you don't, maybe the Cessna will be doing a stop and go (require backtrack?), or touch and go with practice EFATO? ** 3. Maybe you've been cutting it too fine and we no longer trust you to play nicely Being a bit pedantic here with words and I'm sure it's what you meant, but, readbacks relate to what is a clearance, not can be/could be/might be/maybe... **If you're wanting to to some oddball stuff, let us know before hand and we can work it into our plans accordingly.

Learmonth is only active occasionally when there's some left over RAAF budget money to turn into smoke and noise, it's R-Areas are partially active from 20-31 this month but that's usually it for the year... Like a lot of the North West there's no end of awesome coast line and sparse scenary. There's some trikes I've seen a few times so maybe I'll be able to get away later in the week for a scenic...

I've been staying in the area this week and it's been good to see some aviation being committed by a variety types...

Remember, the controllers in the tower are there to help, but we're not mind readers. If you don't tell us what we don't know, we won't know. One of the reasons things can go off plan for us is when what we know and what you know don't match up. So never be timid about speaking up if you're ever not comfortable with something, need some help or something just 'feels off'. I've had plenty of times where something didn't sound quite right on the radio or my spider-senses were telling me there was something amiss, so I ask questions and resolve the uncertainty (most of the time everything was fine and my feeling was wrong, but lots of times right as well...). If you're uncertain about an instruction, a taxi route for example, just say so and we'll slow it down. We'd rather prevent problems than resolve them! This not only goes for towers but also enroute airspace as well with Centre. Anyway, back to the point: If you want full length, just lets us know and we'll be able to work it into our plans.