Less Bliss and more Boredom

Three weeks after our inbound flight, it was time to say goodbye to the European summer and brace for the Australian winter. Not that we noticed much difference: we spent our first afternoon back in Australia soaking in the sun at Balmoral Beach, officially for the sole purpose of helping our Circadian Clock readjust itself to Australian time.

The flight back was very long, entirely experienced in economy class and entirely uneventful. The photo below was taken at sunrise over the Queensland coast, about one hour before touchdown at Sydney.

The Great Circle from Frankfurt to Seoul took us over Berlin, Gdansk at sunset, the Russian exclave of Kaliningrad, Riga and Tartu before entering Russian airspace not too far from St Petersburg.

Entering Russian airspace in a Korean Air 747 brings back memories of KAL 007, the airliner shot down by the USSR Air Force in 1983. I was only nine at the time but I remember reading about it in the Midi Libre newspaper while on summer holidays with my grandparents in the South of France. Not that I was reading international news at such an early age, I was most likely attracted to the article by a photo of the airliner.

In Russian airspace we used a metric flight level at 11000 meters. However, when flying from Poland to Lithuania through the small Russian territory around Kaliningrad, we stayed at FL 350, i.e. 35,000 feet above the reference datum of 1013.25 hPa.

The landscapes of the Gobi desert over Mongolia and north-western China reminded me of the Australian Outback, minus the color red. Then I realised that, since the Great Wall of China was built in order to ward off Mongolian invasions our flightpath would eventualy cross it and I could maybe spot it from the airplane. I remembered something about it being visible from space, so if I kept my face glued to the window I would not miss it. How awesome would that be.

Unfortunately this was not meant to be as a thick layer of stratus clouds started building below us as we approached Beijing from the north-west. Soon after the airliner altered its south-easterly course to track due south towards Beijing, before resuming a more direct route to Seoul.

The reason for the dogleg could be seen right out the window: a massive thunderstorm had developped right on our intended flightpath.

On approach to Seoul I could observe the little crystals of ice that build up on the inside side of the window quickly melt as we passed through the freezing level at about 15,000ft. Yes, I was utterly bored at this stage of the flight.

By the way, I learnt by reading a German flying magazine on holidays that the German word for freezing level is Nullgradgrenze, literaly "zero degree limit". Another funny one is Wolkenuntergrenze, which means cloud base.

We approached Sydney at sunrise, Brooklyn bridge is sort of visible on the photo below.

We landed on 34L at Sydney after a left-hand circuit. We cleared Customs and Quarantine relatively quickly and jumped into a cab direction home. Just like most cabs it had a GPS on the dashboard.

It's amazing how in the space of a couple of decades a classified military technology initially developed during the Cold War to guide ICBMs has now found its way into most cars, mobile phones and of course airplanes.

It's in 1983 that the Reagan Administration took the decision to declassify the NAVSTAR GPS satellite navigation system in order to allow civilian applications, such as better navigation systems for airplanes. It became operational in 1990, just in time for the first Gulf War.

A decision that was taken when it became clear that the downing of Korean Airlines flight KAL 007 by a Russian fighter jet had been triggered by a navigation error that took it over a prohibited section of Russian airspace.

Bliss is Being Bumped up and Bibimbap

This is a post written from an airliner seat I can plug my netbook into, which seasoned travellers will immediately recognise as a Good Sign. A very good sign that the Gods of Seat Assignment finally smiled at me and bumped me up to Business Class. Bumped us up to business class actually since I have the pleasure of travelling with my wife.

This post is low on the usual aviation technicalities, although as we might see later the subtelties of flight level assignment in Mongolian and Russian airspace can be sensed from a passenger seat for passengers with an inquisitive or bored mind.

For a change, this transcontinental trip was not a business trip, which is why we didn't fly Qantas or Singapore Airlines as usual. When the time came to book our tickets for our (Northern Hemisphere) summer holidays, we decided to go with Korean Airlines, who offered the cheapest fares among all the acceptable airlines. We flew Sydney to Seoul in the half-empty A330-300 in the photo above. Note the Emirates A380 in the background. Maybe next time.

As Nina sat in her seat she couldn't suppress a cry of surprise. Her finger was pointing at the back of the seat in front of her, and at the obvious absence of any personal in-flight entertainment system. There was a screen at the other end of our section, but it all looked like a scene out of the movie Airplane.

Our in-flight entertainment came under the guise of the making of Bibimbap. The choice for food was beef or Bibimbap, which the flight attendant explained was a traditional Korean dish. Being the curious and culturally sensitive couple that we are, we both went for Bibimbap, to the obvious delight of the flight attendant.

That's the only in-flight meal I have ever been served that comes with a five-step instruction sheet. Thinking about it, that's the only meal I ever had that comes with printed instructions. On completing step 5 I recognized the dish as something I ordered a couple of times in the past in a small Korean eatery in the Elizabeth Street Arcade in Brisbane.

Bibimbap is a very healthy mix of vegetables, beef, mushrooms and steamed rice. Sesame oil and hot pepper sauce come as separate ingredients. I enjoyed the dish and washed everything down with a big bowl of seaweed soup, not too bad either, just like a Miso soup, but without the evil tofu.

The cabin crew insisted on having all passengers pull the window shades down even though we were right in the middle of the day. This is all the less understandable since there is only one hour time difference between Sydney and Seoul, so it's not like fake night will help us shift our circadian rhythm to our destination. When asked, the flight attendant said it was "rest time". I felt like I was in Kindergarten again, when they forced us to stop playing and take a nap. Anyway, sticking to our theme of cultural sensitiveness, we accepted the Korean Siesta.

Maybe because the cabin was in the dark, a flight attendant carrying a tray full of glasses down the aisle stumbled as she walked by us and spilled some water over Nina's blanket. No drama at all, the spillage was quickly removed using a single napkin, and no garment got stained in the process. The ensuing display of apologies by the flight attendant, and later by the cabin chief was just amazing. I joked to Nina that she should have played the offended customer and ask for a business class upgrade on our next flight.

After a night in Seoul we resumed our journey with a long 12-hour flight to Frankfurt in a 747-400. I had seat 19B. I entered the airplane, turned right and started looking for my row number on the overhead baggage compartment. Suddenly the most bizarre thing happened. The numbers jumped from 12 to 39. I was so surprised that I asked the flight attendant who directed me upstairs. I climbed up the stairs, turned left and found my wife who had followed instructions and arrived there before me. We looked at the wide seat and exchange a very big smile. Business class. And not any business class seats. Exit row business class seats. To paraphrase Flight of the Conchords, It's Business Time.

After that stupid smile left my face and I had finished playing with the controls of the eight different ways in which I could adjust my seat, I looked through the window and saw lots of convective activity down below in the steppes. We were north-west of Beijing, approaching the border with Mongolia.

Then of course came time for our Korean siesta, even though flight KE905 left at 1:15 PM and arrived in Frankfurt at 5:35 PM. I started exploring the options of the in-flight entertainment system. The flight information gave our cruising altitude over Mongolia as 31494ft. Not a round number? How comes? Cruising altitudes obey the rule of flight levels, which typically work in increments of 1000ft.

Then I clicked on the "Metric" box and it said 9600m. Ah ah... Maybe just like the Russians, Mongolia uses the metric system in aviation. That wouldn't be terribly surprising given Mongolia's history of close alignment with the Soviet Union in the 20th century.

The mystery got thicker later when over Russia we cruised at 38094ft / 11611m for over an hour. Maybe the aiplane was assigned a block level and chose the most efficient altitude. Or maybe something else.

The rest of the flight was absolutely uneventful, which is good. I had a Tuna and Kimchi Onigiri sandwich which wasn't bad at all, very filling and quite likely very healthy too. The good thing with flying Seoul to Frankfurt is that it makes one realise how freaking huge Russia is. You could fit a couple of Australias in there. Which to my European appreciation of distances is simply mind-boggling.

Alone in the dark

I was driving to the airport from work for my first night solo when rain started to fall. Great. Just what I needed, a wet runway and the likelihood of reduced visibility in the circuit. Or even no night solo at all if Dan estimated it was not safe enough for me to go.

I preflighted the airplane under the rain. It took me a while to understand that the navigation lights on that airplane are activated by the panel lights switch, as opposed to having a dedicated switch like on other airplanes. The landing light had been fixed since the first time I flew the airplane, so I wouldn't have to rely on the wing-mounted light this time. Good. The ground was soaked with water which made it difficult to check the flap hinges or the fuel drains without covering myself in mud.

I went out for three circuits with Dan, the Deputy Chief Flying Instructor, so that he could check that I actually knew what I was doing before signing me out for solo at night. We taxied to 11C, did two normal circuits, one go-around, one normal circuit with no landing light and one full-stop behind a rescue helicopter.

On my first circuit I ended up too high on final so I decided to perform a sideslip to loose altitude without gaining airspeed. "Do you know you're sideslipping?" asked Dan. Yes I answered. I guess I should have verbalised the manoeuvre instead of letting him believe I had developed a habit of unwittingly flying with crossed controls.

Dan explained that sideslips should be avoided at night since judging height is harder than in daytime. Better work on fixing the problem of being high on final rather than on the unsafe solution required to recapture the correct descent profile. 1500 rpm when turning base is the magical number said Dan if I want to be at 500 feet when turning final. Of course this all assumes I fly circuits of correct dimensions, i.e. one minute for each of the last two legs.

Dan said he was happy with me going solo for another hour of circuits. He added that if the airplane started to skid on the wet runway on landing I should apply full power and take-off immediately rather than trying to control the airplane on the ground.

Dan jumped out of the airplane and I taxied back to the run-up bay and then to 11C for ten more circuits. VH-SFA and VH-SFR were the other two aircraft in the circuit, with Dan in one and Ben in the other. So I had two pairs of instructor eyes looking after me. Nice of them to not leave me alone in the dark.

The clouds had cleared a bit by now, and the full moon had risen to the east. On downwind the full moon lit up the entire panel. Having only one person on board allows the 160 hp Warrior to climb and accelerate a lot better. At some point after a touch-and-go I even found myself catching up with a 152 in front so requested and obtained an extended upwind leg for spacing.

The rule when night flying though is to spend the entire upwind leg on instruments and not look outside below 500ft, when ready to turn crosswind. I find that difficult with an aircraft in front of me in the circuit, both because the anti-collision light of the preceding aircraft appear in my peripheral field of vision, right above the dashboard, and also because I want to positively maintain separation, not just rely on ATC spacing aircraft correctly in the circuit. As a matter of fact, in GAAP control zones ATC do not provide separation, the responsibility for avoiding collisions rests entirely with the pilots.

On one circuit I learned a valuable lesson. I had just turned final and the preceding aircraft was on short final. It looked like it was too much to the right so I kept an eye on him to see how he was landing. This distracted me from my scan, and when I next looked at the PAPI lights I saw 4 red lights! I got a bit scared since I didn't how far below the glideslope I was and in addition I remembered there's a line of tall trees in the area. More power, back up to the glideslope.

I landed a few minutes before the tower closed and taxied back to the club house. We spent a bit of time going through all the paperwork required and putting a new stamp in my logbook that says I am competent to fly solo at night in PA28 aircraft at night according to the requirements of CAR 5.01A.

It was starting to get a bit late and I was hungry so I said thank you and good bye to Dan and Ben and walked back to my car. I had not turned round the corner of the airport when rain started to fall again. I made a special mental note that I was lucky with weather this time, so that I won't get too upset next time weather Karma does not go my way.

First go-around in a commercial airplane

Tuesday morning, about 7:30AM. I am half-awake in a window seat on the left-hand side of a Qantas Boeing 737-400 on approach to Brisbane airport. We just flew past the tip of North Stradbroke Island, and in a minute or two the airplane will touch down on runway 19. The landing gear goes down, soon followed by flaps. We make a left turn onto final. More flaps.

This is a beautiful Queensland winter morning, with high clouds and amazing visibility. I can see Brisbane CBD very clearly, and in the distance the towers of Swanbank power station, some 50km away. The sight brings back memories of screwing up majorly in this very area on a PPL navigation exercise about a year ago. But back to our story.

My seat is a perfect vantage point for observing the trailing edge of the left wing. We're now aligned with the runway. The flaps move down a little more and then stop. They're about half-way down, definitely not extended as they should be for landing. A few seconds pass and then we pitch up for a go-around. Some power is applied, but not full take-off power, or at least it doesn't sound like it. The rate of climb is moderate.

We make a series of left turns back to the Mud Island area. The captain makes an announcement saying that we went around because of a problem with the flight controls, that this is a routine procedure, no need to worry, we will be on the ground shortly, and sorry for the inconvenience. The flaps haven't moved at all since final. We come back for a very uneventful landing on 19.

As we taxi to the gate the flaps are still in the same partially extended position. They only come back up a few minutes after we reach the gate. The flaps actually come up very slowly, possibly because the backup electrical flap retraction mechanism was used, rather than the normal hydraulic one. That's my guess based on those notes, and I'll stop here with the armchair incident investigation.

As I was walking out of the narrowbody airplane I noticed the captain standing at the cockpit door saying goodbye to passengers, which is rather unusual for Qantas. I asked him if this was a flaps failure and he confirmed with a wink.

So that was all for the adventure. Nothing spectacular really. Sorry for indulging in Gonzo journalism, but that's la loi du genre. The fact that this was my first go-around ever on a commercial flight after hundreds of flights on airliners I guess should be taken as a testimony to the reliability of airline flying.

Speaking about journalism, I found this article about a similar incident on the same type of airplane in Alaska. They quote an FAA person as saying that they do not regard the failure of flaps to be a safety hazard. Which makes a lot of sense. Some airplanes do not have flaps at all. Student pilots perform flapless landings routinely. Flaps are a very convenient luxury.

I was momentarily impressed by how a local newspaper actually sought qualified technical advice when reporting about an aviation incident that didn't even involve injured passengers or a bent airplane. That was before I read the final two paragraphs, where they quote a local ham radio operator who describes the radio transmissions as "dramatic and alarming to hear" and offers a piece of definitive advice by saying "I would definitely be watching and questioning. I would be kind of apprehensive". I guess the opinion of the FAA person was too sensible to end an aviation story with.

More night circuits and a bit of daylight

My last session of night circuits was much, much better than the previous one. Ben said he is now ready to send me solo at night, which will happen as soon as my schedule and the weather conditions agree. So all the beating myself up and rehearsing circuit procedures in my head and on paper paid off.

This time I was prepared. I had eaten a triple cheeseburger on the way to Bankstown. For some reason whenever I go flying I feel excused for eating junk food. I was hydrated but not too much. I had my own torchlight and the pre-flight visit didn't reveal any nasty surprise. Earlier in the day the wind was blowing at 15 knots gusting to 25, but as night fell so did the wind, down to a more manageable 8 knots. There was a catch though: the forecast called for moderate to severe turbulence below 5000ft, which combined with the crosswind made for a few challenging final legs.

The aircraft that night was VH-SFK, still a Warrior but much better equipped than IJK which I flew the time before. As you can see on the photo above, the row of switches actually lights up on this aircraft. The Garmin 430 automatically dims the display at night. Ben showed me the settings page where the display brightness can be adjusted. If you look back at the photos taken on my very first night flight, you can tell the GPS display was still on full bright. The lights of the annunciator panel can also be dimmed.

I flashed the landing light three times as a warning sign for anyone around to stay clear of the aircraft and started the engine after a bit of priming. We taxied for left-hand circuits on 29C. As we approached the main apron two Aero Commander crossed in front of us, following a larger Metroliner, like ducklings lined up behind their mother.

For some unknown reason, we were the only training aircraft in the circuit that evening, in contrast with the time before when we had to wait twenty minutes in the run-up bay before someone left the circuit and the controller allowed us to join the merry-go-round. Maybe the forecasted turbulence discouraged other pilots. Maybe we were just lucky. Maybe there was something good on TV for a change.

We started with two normal circuits to get me back in the saddle. Preparation paid off, I didn't forget anything and the shape of the circuits was acceptable this time. Not great, but acceptable. There was a crosswind from the right on final which I managed to handle reasonably well, even though we drifted a bit far from the centreline on a couple of occasions. I should have put more ailerons in after removing the crab. Landings were a lot harder than the previous time, but my excuse is that that's what one wants with crosswind landings: a long float means the possibility of drifting downwind of the centreline, and flying with crossed control in the flare means more drag.

The crosswind was blowing our downwind leg a bit too far away from the runway, and the moving map on the GPS showed us a bit too close to the edge of the control zone for comfort. The control zone at Bankstown is more or less a circle with a radius of 3 nautical miles, so the correct analogy for circuits there would be a goldfish in his bowl. Ben suggested I do not fly a straight crosswind leg, but rather fly a climbing turn from upwind to downwind, which definitely helped bring us closer to the runway.

Then came lighting failures. Ben turned all the interior lights off. I took my torchlight which I had kept handy, turned it on and stuck it to the side of my headset, right above the earcup gel. It works fantastically well, and the red glow from the torchlight illuminated the whole panel. The added bonus of sticking the torchlight under the headset of course is that the light follows where the pilot is looking.

We did four or five circuits like that. The torchlight didn't move. Ben asked the tower controller to shine at us the green light that would indicate we are cleared to land in the event of a radio failure. On the next circuit the controller showed us the red light for a so-called "tower-initiated go-around". I didn't forget to clean up the aircraft this time. We did an uneventful flapless landing, another normal circuit and then it was time to call it a night.

Back at the clubhouse we looked at the syllabus for Night VFR and realised that I cannot go solo before I have practiced unusual attitude recovery under the hood in daytime. I guess CASA does not like the idea of people practicing spiral dives and approaching the stall in a climbing turn at night.

So on the next Sunday we went out to the training area for practicing unusual attitude recovery. There's only two techniques to remember, depending on whether the nose is pointing up or down, so that wasn't too hard. Nose up, full power, push nose down, wings level. Nose down, power to idle, wings level, pull nose up. And in both cases finish by re-establishing straight and level flying at cruise power.

The good thing on that short 0.7 hour flight is that I spent 0.4 hour under the hood. I put the hood on as we passed 500 ft after take-off. Ben handled the radios and gave me vectors to the training area to perform unusual attitude recovery exercises and later back to Bankstown via Prospect and all the way to late downwind where I took the hood off before landing on 29R.

So I'm now officially ready to go solo at night. I'm just waiting for the planets to align between my availability, that of my instructor and that crap weather we've been having for the last three months. Even though it is obviously not the same as a first solo, this is still very exciting.

Flying Competition at Warnervale

I recently participated in a flying competition organised by the club at Warnervale aerodrome. Another pilot had already put his hand up for ferrying the Warrior from Bankstown for the day, so I decided to drive instead, Warnervale being about an hour drive north of Sydney. And since the weather forecast was good and we had not explored that corner of New South Wales yet, Nina and I decided to make a day trip out of it.

We drove from Sydney and crossed the Hawkesbury River at Brooklyn Bridge. Not to be confused with the bridge of the same name in New York City. The area seems to have more than a coincidental relationship with the Big Apple since the bridge itself was built by American contractors, and the suburb across the river is called Long Island.

Brooklyn Bridge happens to be the entry point for the Bankstown GA Lane southbound. The lane is a north-south corridor of Class G airspace squeezed in-between the Richmond RAAF base to the west and the Sydney CTR to the east. The lane has an upper limit of 2500 ft.

Warnervale aerodrome is very easy too find, just a couple of kilometers off the motorway. It's one of those typical country aerodromes. What's also unfortunately typical about it is that it's soon going to be closed down under the pressure of property developers. A sign on the wall in the clubhouse seemed to indicate that the flying activities will be relocated to Aeropelican, about 15 nautical miles to the North-East.

Because there was a suspected problem with the starter motor on VH-IJK, we didn't stop the engine in-between competitors. Lindsay, the instructor, would stand on the wing while pilots swapped places. I have to say I love the idea of just sitting down in the airplane, fastening the seat belt and pushing the throttle forward. Feels just like driving a flying car.

We taxied to the run-up bay and then down a dirt track to the holding point where we decided to take-off immediately rather than wait for the aircraft on base to land. As I lined up I was shocked at how narrow the runway was. It really looked like we had taken the wrong turn down a local farmer's driveway. The irreplaceable Google Earth told me later that the runway is about 8 metres wide, compared to 18 at Redcliffe or 30 metres at Bankstown.

At 400 feet Lindsay took over while I put on the hood. Then she got me to do some climbing turns, straight climbs and straight and level flying under the hood. At the stage we were about 3000 feet. Lindsay briefly took over to put the aircraft into an unusual attitude (a spiral dive) from which I had to recover on instruments. Throttle back smoothly, wings level, pull the yoke back without stalling and recover.

Next was a simulated forced landing without power. Throttle to idle, carby heat, mixture, fuel, capture and trim for glide attitude. Finding where to land was not too hard since we were right overhead the aerodrome. I had plenty of altitude to expend before landing so I brought the flaps in early and we touched down not too far from the threshold. Full power and one more circuit, this time for a precision landing.

My precision landing was anything but precise. The only precise thing about it is the height above the runway I maintained while floating for a long long time. My approach was actually good, but soon after I turned final I got a bit spooked by the line of trees that seemed very close to the approach path. I added a bit of power and pulled the nose up to give myself more clearance over the trees, and as a consequence I ended up way too fast on short final, probably 10 or 15 knots too fast. All this energy had to go somewhere hence the long float. We taxied back on a muddy dirt taxiway this time, with one main wheel skidding in the mud.

I checked my score with John who was organising the whole event and realised that this time around I wouldn't make it into the top three. Last time was probably a fluke, cause by people not wanting to get up too early on a Sunday.

We then drove to Toukley and went for a walk on the local beach. We came across the cutest sand castle ever, played fetch with a local dog for a little while and enjoyed the end of the afternoon while a 152 was performing airwork above our heads.

Just round the corner we climbed up the stairs to the Norah Head lighthouse. According to this web site maintained by lighthouse nerds, this lighthouse shares a similar design with its two other NSW siblings at Cape Byron and Point Perpendicular (you have to love the name). Lighthouses tend themselves quite well to aerial photography, and the three of them could be covered in a day's flight... here's an idea for a Sunday flight with a difference.

It's been a hard day's night flying session

Remember how I said in my previous post that I loved the idea of flying at night on weekdays because it freed me from having to take time off work or planning my week-ends around flying lessons? Well, I just came across a huge downside of this nice little theory: after a full day at work, it is very, very hard to empty your mind, restore energy levels and focus on the flying. As a result, my first night flying lesson was very, very messy and I was quite upset with that.

I met my instructor Ben in the clubhouse and we started with a quick whiteboard briefing about taxiway and runway lighting and how night circuits are flown differently from daytime circuits.

Because I had forgotten my torchlight at home, I had to borrow Ben's for preflighting the aircraft. The pre-flight visit is essentially the same as in daylight, with the addition of landing and navigation lights. I noticed that the landing light was not working. That's the light right at the front of the aircraft, below the engine air intake, the one that's used for lighting up the runway on take-off and landing at night. Can't really go without it at night. Ben said we could use the other landing light instead, the one situated near the middle of the leading edge of the right wing. Problem solved.

The aircraft on that night was VH-IJK, the oldest Warrior in the club's fleet. It could definitely do with a new interior trim, but that didn't bother me much in the dark. Before startup, Ben showed me how to use the panel lighting. Unfortunately, the row of switches is not lit up, and I had to be extra careful not to switch the electrical master off when going for the fuel pump switch.

We taxied to 11C and Ben reminded me to perform taxi checks when turning. Keeping the nose wheel on the taxiway centerline was quite hard because the light was coming from the side and not all yellow taxi lines at Bankstown have green lights down the middle. Ben explained that one common mistake is to taxi too fast at night because the pilot has less cues in his field of vision for gauging speed. The trick is to look in the general direction of the wingtip to get a better idea of how fast we are going.

The circuit was already full, with five or six aircraft practicing night circuits. The tower told us to expect a delay and that we would not be cleared before an airplane currently in the circuit makes a full-stop landing. We shut down everything and agreed with the tower controller that he would shine a torchlight at us when he wanted us to start up and talk to him again. The light eventually came and we lined up for a session of about 7 or 8 circuits.

Maintaining the runway centerline on take-off is hard without a front landing light, so I concentrated instead on keeping the picture drawn by the runway side lights and the distant threshold symmetrical while accelerating to take-off speed. The upwind section of the climb is done on instruments up to 500 feet. Wings level, maintain best rate of climb speed with the airspeed indicator and maintain runway heading with the DG. And keep that instrument scan going.

On crosswind when the opposite threshold is about 45 degrees behind us I turn downwind, make my downwind call, BUMFHH checks and try to maintain the runway about one third of the way down from the wingtip. Same story with the other threshold before turning base. Ben explained that the trick for knowing when to turn final is to watch for when the first runway side light on the near side aligns with the third light on the far side. This worked quite well, but I always ended up too high on final. Ben identified the source of the problem as me not flying a square base, but rather having the base leg point toward the threshold, thereby giving myself less time for descending.

A few times when I ended up too high on the glideslope I managed to recapture the correct approach profile (2 red lights and 2 white lights on the PAPI), only to go too high again on late final. Ben insisted that I do not push the nose down below 300 feet to recapture the perfect glideslope otherwise I'll end up touching nose wheel first: if it's too high, just accept it and fly it. 300 feet is also the magical number for the altitude where I more often than not forgot to turn carby heat off. Not good.

On one circuit Ben asked the tower to switch the PAPI lights off, which lead to a good landing actually. Flare and touchdown require a bit of a leap of faith at night though. We tried without the landing light, which worked well too. Having the lights off forces the pilot to concentrate on the picture of the whole runway rather than the beam of light from the landing light.

On one circuit we had a rescue helicopter join the circuit on final from Prospect when we were on downwind. That's because, as per the ERSA, helicopters at Bankstown must use fixed-wing procedures at night. The tower advised us of possible wake turbulence and I extended downwind to allow more time for the turbulence to dissipate. Not that it helped anyway. I was on short final when the aircraft suddenly rolled to the left. Very similar story to what happened to Chris recently. Right rudder, full power and we went around. I forgot to retract the flaps though and it took me an embarrassingly long amount of time to find out why I wasn't climbing as well as in the previous circuits. That and leaving carby heat on are really the kind of beginner's mistakes that make me very upset with myself. Power up, nose up, clean up and speak up. It's not that hard.

Because of our late start we were alone in the circuit when the tower shut down and the control zone reverted to a CTAF. We did one more circuit and taxied back to the club house. We had a debrief where we went through the list of things that could have been done better. Ben gave me a copy of the Night Rating syllabus so that I know what's coming up. We booked two circuits sessions for next week, any one of which can be converted to a simulator session should the weather be less than ideal.