Roundsounds

Sorry Nev, I meant other FTF Class D exemptions. The others I've read only permit student cert holders to fly solo. Once their RPC has been issued they're banned from CTR/A unless they satisfy the minimum GA licence requirements (and aircraft certification standards).

Interesting subtle difference to the other exemptions I've read. Maybe that's part of the idea of keeping individual exemptions in place.

The document behind the link is titled: "Exemption — solo flight training at Coffs Harbour Aerodrome using ultralight aeroplanes and weight shift controlled aeroplanes registered with the RAA" The whole exemption thing makes the Class D restriction more ridiculous. Most Class D airports have RAAus FTFs operating from them under an exemption. The last quote I had from CASA was $800 for initial issue, plus a fee for renewals each 2 years. Again, I ask why is it Gliders and Balloons (private Op's) are not subject to the airspace restrictions imposed upon RAAus? No requirement for motorised gliders to be fitted with certified engines, are the gas burners in the hot air balloons certified?

So you're telling me you're acting like a "professional", yet you don't know what's in the regulations and guidance material under which you are acting professionally?

So you are saying you deliberately chose to ignore the guidance provided by CAAP 166? These procedures have been developed by a panel of CASA, Airservices and industry representatives and are considered to be the safest and useable option to be adopted by all non-controlled airport users. I'm glad I'll be driving to the Temora Airshow in November, can you imagine the RT congestion and the impact it will have on the safe and efficient flow of traffic with every aircraft making IFR/commercial departure reports on CTAF? There will be no air time for taxying or runway entry calls. In addition to the line up call there would be "Temora traffic, Jabiru twenty eight thirty six departed time 23, climbing to 6000, tracking 090, Temora" as opposed to "Temora traffic, Jabiru twenty eight thirty six lining up runway 23, departing crosswind Temora" Not sure how IFR/commercial inbound and departure reports differ from any other operation?

I suspect with the loss of country (NCTL) based flying schools most pilot and instructor training is being conducted at Class D aerodromes. These newly trained pilots and instructors then move to country areas and lose their security blanket (ATS) and feel they need to talk a lot routinely, instructors then pass this onto their students. RAA pilots hear the charter / training flights make their routine 6 calls between 10NM and shutdown and think "if that's how the 'professionals' do it, then so should I". Having returned to instructing at Class G aerodromes after a few years break, the difference in RT is very obvious, probably more so than for someone who has lived with the gradual changes. I studied the AIP and CAAP 166 prior to venturing back into class G and found nothing in the rules had changed, however the practices certainly have! Provided there is no immediate likely hood of a collision, routine calls should be limited to - Inbound - joining circuit (or 3Nm final for a straight in app) - a base call (if you really think it's warranted and for all circuit traffic) For anyone in the circuit respond to inbound traffic with your call sign, type, position and intentions - this allows the inbound guy to start forming a mental picture (situational awareness). For the naysayers, maybe have a chat with some of your mates one day when the circuit is quiet and go try circuits with 3 or 4 aircraft making only a lineup then turning base calls and see how it goes?

You must've misread my comment then, I suggested a base call was all that's needed as a standard call and routine downwind and final calls are not necessary.

To begin with I'm merely trying to pass on my experience of many years of safe flying including private, charter and flight training and testing. I think your tone is inappropriate. Situational awareness in terms of circuit traffic does not require any more than base calls. You use this information to form a mental picture of the circuit traffic, which is then confirmed by visual sightings. To a certain extent a busy circuit is easier, as you simply maintain visual contact with the aircraft ahead.

It's not only about keeping traffic in sight, it's about situational awareness which pilots are trying to replace with constant radio chatter.

I was recently doing some training with a gentleman in his newly acquired aeroplane at Cessnock, the local school there obviously teaches the 3 calls per circuit method and don't teach them to wait until no one else is transmitting. There were 4 of us in the circuit, when we were overtaken by a Piper Navajo on downwind. After we landed the Navajo pilot came over and apologised for not calling his circuit entry, as he was unable to due RT congestion. Interestingly the ERSA recommends only base calls at Cessnock for this very reason. I've been flying for 40 years and find the trend in increased RT in the circuit area distracting, unnecessary and dangerous. The constant chatter eventually becomes white noise and if there is an urgent need to use the radio you can't.

I also use a kneepad when on cross country flights, but always remove it for takeoff and landing. If you review the video at 6:42 you'll see what I mean. He can use full right aileron, provided the control column is full forward. I'm not criticising the guy, just pointing out traps. Control checks include "full and free movement, correct response" With regards to do lists, by all means use them but you should go back and run the check list. I've seen numerous events where critical a item in a procedure was missed as the line was jumped, by going back through the same list when you think it's complete, you will reduce the chances of an error. I use a pneumonic for my before takeoff checks, followed by the written checklist.

A few observations made watching the video: - Too many distracting gadgets (iPad, ADSB receiver on glare shield, knee pad) - Knee pad limited control wheel movement, not good if landing with a right crosswind. - Checklist used as do list (do checks from memory, then use the checklist to make sure you didn't miss anything, which why they're called "check" lists) - Too much chatter between pilots, which led to missing aircraft on RWY 27 calls. - Aircraft on final 27 didn't respond to the line-up call of aircraft entering 32 So much for radio calls preventing traffic conflicts, lots and lots of talking but the good old lookout saved the day!

To put this into perspective, 5 aircraft doing circuits (average 6 minutes per circuit) all giving 3 calls per circuit at say 7 seconds per call. 360 seconds of radio time to accomodate 15 calls totalling 105 seconds. This leaves 17 seconds between calls to allow taxying, inbound, joining and overfly calls. A base call is all that is needed when flying circuits, it's up to pilots to maintain situational awareness (mental picture of traffic) and to not become reliant on radio calls to keep tabs on traffic. Downwind calls came into effect when GAAP were developed, as the call suited ATC for sequencing purposes. The old Secondary Airport procedures had traffic making base calls, which worked well. (Secondary Airport procedures were in effect before GAAP / Class D)

The only way the communication issue can be identified is by submitting incident reports for each event. CASA / ATSB cannot act on the matter in any other way, they need the statistics. So, if you have an incident involving communication issues raise an ASIR: http://www.atsb.gov.au/mandatory/asair.aspx

I'm not too sure about the right turn at 500' being acceptable? Try reading CAR166A or AIP ENR 1.1-71 para 43.1. Basically it says you must depart by extending a leg of the circuit, if turning opposite the normal circuit direction you should be 3 miles from the departure end of the runway. CAAP 166-1 is worth reading, it also spells this out and the recommended radio procedures for non-controlled aerodromes.

I get Ada's point, an instructor should know that basic stuff. By all means suggest something more conservative with justification, but at least know the answer.

The answer is actually in AIP- AIP ENR 1.2, Visual Flight Rules: 1.1.2 Unless the pilot in command is authorised under CASR Part 61 to conduct a flight under the IFR or at night under the VFR and the aircraft is appropriately equipped for flight at night or under the IFR, a VFR flight must not: be conducted at night; and depart from an aerodrome unless the ETA for the destination (or alternate) is at least 10 minutes before last light allowing for any required holding. Or in the VFRG, pretty basic and simple rule. http://www.vfrg.com.au/operations/general-information/visual-flight-rules/

The speed differences between most GA singles and RAAus aircraft in the circuit is insignificant. Flying an appropriate sized circuit and approach for the speed of the aircraft will overcome most of the issues caused by differences, any remaining issues are dealt with by ATS. After all that's ATS's purpose in life, to stop aircraft from bumping into each other and facilitating an expeditious flow of air traffic.

Perhaps, rather than insist on PPL theory, introduce some form of on-line training targeting theory issues specific to RAAus type aircraft? The suggestion of an on-line format is to create standardised training, allows remote pre-study for prospective instructors without the need to cram when attending an instructor approved school. Additionally, this allows students and RPC holders the ability to improve / refresh their knowledge. The content could initially be driven by findings from incident data - eg stall/spin or weather related decision making practices. Instructor trainees could be required to pass a written exam prior to commencing their instructor training to establish they have a sound knowledge of RAAus aircraft type BAK and Human Factors principles.

Nev, the pure gliders do as you state for comps, however motor glider pilots operate as though they have a PPL. For example at Camden (Class D), motor glider operations are permitted on a self certified medical, no GA quals and have a controlled airspace endorsement issued by the GFA. The pure glider operators also self certify medicals, but aren't required to hold an airspace endorsement. Private balloon pilots also operate from Camden, again no GA quals or CASA medical. Glaring double standards, I dare say the RAAus airspace limitations are a legacy from the days of ops not above 300', unreliable power plants, single seat aircraft and self taught pilots.

I know I'm sounding like a broken record, but.... how is it GFA and Ballooning Certificate holders are permitted to operate in CTA, but not RAAus? If RAAus were granted the ability to operate in at least Class D, that would open the sport up to our larger / capital city folk and potentially give RAAus a larger membership, voice and viability.

While I'm on my high horse.... You can teach spin awareness without spinning an aeroplane, just like you can teach ditching without actually ditching. A series of discussions during training with appropriate demonstrations / guided and monitored practice of scenarios leading to a stall / spin conducted at a safe height can be done - like I do. This subject could be the target of an on-line training package (video / fact sheets). Under CASR Part 61 all new Grade 3 instructors are required to hold a spinning endorsement. No reason why some sort of GA training for RAAus instructors couldn't be completed in say a C150/2, Citabria, Tiger Moth or GA registered Cub or Champ - similar handling to most 3 axis RAAus training aeroplanes. Then instructors would at least know what a spin entry looks like.

Could agree more, an inadvertent spin from anywhere in the circuit will not be recoverable by a pilot capable of entering such a spin! Early recognition of the tell-tale signs of a spin (stick position / unbalanced flight / holding off bank) is far more important than spin recovery and its achievable in any RAAus registered aeroplane.

Here is a current example of poor training: I recently finished training a young guy to fly. As part of his training we stalled the aeroplane with power on, off, clean, landing configuration, turning and induced wing drops (I'm also a GA instructor and teach aerobatics, so am comfortable to train correct stall recognition and recovery within the limits of RAAus aircraft). Having gained his pilot certificate at an FTF a fair distance from his home town he decided to get checked out in a local FTF aircraft. During the upper air sequence he was to demonstrate a stall recovery, he tells me the instructor almost wet himself at the suggestion of stalling the aeroplane in a turn! The FTF insists on glide approaches, but don't allow slipping but use s-turns to lose height. When asked why glide approaches in a Rotax 912 powered aeroplane was considered necessary he was told the earlier "Ultralight" aircraft had two stroke engines which were prone to stopping, so every approach is a glide approach and have carried on this practice. A couple of points here: 1. The operator insists on doing low level turns on final approach to lose height, yet doesn't teach or practice stall recovery in turns. 2. The operator's reasoning for glide approaches in a modern 4 stroke powered aeroplane is like teaching Cirrus SR22 pilots to do glide approaches because that's what was done in Tiger Moths. I'm quite sure there are poor practices in GA too, but from my observations some instructors can't put training of certain sequences into context. I don't know what the answer is?

1. Establish an incident database so the common causes, aircraft type, pilot profile etc can be determined. 2. Create educational material targeting the common topics determined from the incident data base. The material would be in the form of on-line video and fact sheets. 3. Make the common causes of incidents discussion points during flight reviews.