Showing posts with label canberra. Show all posts
Showing posts with label canberra. Show all posts

Monday, February 15, 2010

Spot the airfield: Canberra

On a flight from Sydney to Melbourne in a Qantas 767 we flew over Canberra airport. Which is not terribly surprising since Canberra is on a straight line between Sydney and Melbourne.

It is actually for this very reason that Canberra was chosen as the Australian federal capital in 1908 since neither Sydney nor Melbourne would accept the rival city as the federal capital.


The longuest of the two runways at YSCB is 17/35 with a length of nearly 3300m while runway 12/30 is about half the length. There's a great video taken from the control tower of a Russian IL-76 using every single inch of runway 17 on take-off. I'll let you decide how much chance and careful planning were involved in this successful take-off.

Right near the left edge of the photo above you can see two concentric ring roads around Capital Hill on top of which sits the Australian Federal Parliament.


It took me a while to realise which airport this was. I had only been to Canberra once before, it was at night and it was a disaster. For previous photos of airfields I took from airliners, you can start here.

It feels good to know I'm not the only one filling up blog posts with photos taken through the windows of airliners: don't miss this awesome photo of Grand Canyon taken by Rob Bremmer, the blogger behind why2fly who nicely captured the two pillars of spotting things from the sky: always carry a camera and look out the window often.

Tuesday, October 27, 2009

Why flight planning matters even more at night

The first two dual navigation exercises towards my Night Rating were very different from each other. Thankfully, it was the first one that was very bad, and the second one that was rather good, so I must have learnt something in the middle. I'll spare you the usual blow-by-blow account of each flight and rather focus on what went wrong and the lessons learnt.

My first night flight beyond the confines of the local circuit took me and my instructor Ben from Bankstown to Canberra via Goulburn and back via Goulburn NDB, Bindook VOR and Camden NDB.


My airmanship was all over the place. Soon after departing Bankstown I realised that making any sense of the ERC chart at night was going to be very, very difficult, especially when trying to distinguish between the blue and the green lines under red light. The track I had carefully drawn and highlighted was also undistinguishable from the million other lines on the chart, and the large yellow streak of highlighter had disappeared.

It would have taken me five seconds to look at the chart at home under red light and anticipate the problem. But I didn't and ended up giving Ben a massive headache on the way back when I descended at more than double the standard rate in order to stay under controlled airspace. Staying ahead of the airplane is hard when you are reading the chart with your finger like a six-year-old.

I had also forgotten to write down the PAL frequency for Goulburn. No problem I thought, let me look it up in the ERSA. Where's the ERSA? In my flight bag. Where's the flight bag? On the back seat. I turn around. While flying on instruments. Where's my black bag? Which bag is which? I can't see anything. I hand over the controls to Ben who kindly accepts, at that stage probably wondering what he got himself into when he took me on as a student.

Ah good, here's my bag. I can feel the spiral-bound book, I pull it out. Bad luck, that's the VFG, which is also spiral-bound. Second try lucky, that's the ERSA. Flip, flip, flip to the page for Goulburn. PAL is 119.6. Scribble it down and tune it in. End of the minor drama, which could have been altogether avoided with five extra seconds of preparation at home, namely writing the PAL frequency down on my flight plan, next to the YGLB waypoint. Lesson learnt.

My two circuits at Canberra were so abysmally bad I still feel the full pain of utter embarrassment writing about it. And that was in controlled airspace, with someone telling me what altitude to keep and when to turn base in order to avoid the big hill not too far from the threshold of runway 30. The hill was named Disaster Hill, after what is known as the Canberra Air Disaster of 1940.

When initially approaching the airport coming from Goulburn I mistook one runway for the other, which threw me off right from the start. I was soon overwhelmed by loss of situational awareness, flying a circuit at an airport I had never been to before, even by day, listening to and talking to the controller at the same time. Which could all have been saved with preparation since I knew exactly which direction I would be coming from.

I was obviously very upset with myself after the flight. It was one of those moments I mentioned earlier when I wonder if flying is really the thing for me and if am I not deluding myself thinking I can reach the standard required for the test, let alone fly an airplane safely.

But going through the (many) notes I took during the debrief and after counselling myself on the topic I decided to make the next flight an absolute success by being thoroughly prepared.

The other flight took us to Cessnock for circuits via the Calga and Mount McQuoid NDB, then east to the Norah Head lighthouse and following the coastline south to Barrenjoey Head, a Harbour Scenic procedure at 2500ft and back to Bankstown down the GA lane.

Apart from a bad approach on the first circuit when I decided to go-around, the rest of the flight was fine and even very enjoyable. I was most of the time sufficiently ahead of the airplane and could anticipate turns, climbs, descents and all frequency changes. The only thing that threw me off was situating the aerodrome relative to the town of Cessnock. That was the only bit I had forgotten to prepare, and it came back to bite me. In the photo below the town is the yellow area on the left, which turns into a thin outline under red light.


How did I prepare for the flight? I had drawn a number of mud maps, one for each section of the flight. I didn't invent the concept, it is recommended in the Civil Aviation Advisory Publication about Night Flying. Here's what a mud map looks like:


It's a schematic representation of the flight that contains all the information I need for flying the flight as planned, and only that information. Obviously if I had to perform a diversion I would have to revert to the regular documentation. Preparing the mud map is also of course a great way to rehearse the flight at home. I drew my mud maps using only a lead pencil on A5 portrait sheets so that they would fit on my kneeboard.


Because we are navigating by instruments, we do not need topographical information, and angles and distances do not have to be accurate. I write down track and altitude for each leg, frequencies for ATC and navaids, boundaries where to change frequency, and anything else that may be useful, such as circuit altitude or forecast QNH for an aerodrome. Writing this I realise that one thing is missing, it is the lowest safe altitude for the area, which I would need for a diversion.


It only costs the time it takes to draw the mud map, and it makes a world of a difference. It is amazing how much difference preparation can make. And not just being prepared as I would for a day flight, but being prepared for navigating at night. Which by now you must have realised is a very different kettle of fish.


I knew I had to be very prepared for flying at night. I read about it. I even blogged about it. But for some reason I had to get burnt once for the lesson to permeate my thick skull.

Or, as I read recently, good judgment comes from experience. Unfortunately, the experience usually comes from bad judgement.

Friday, May 29, 2009

C182 performs wheeler landing at Canberra airport

I was in Canberra recently and came across this article on the front page of the local Canberra Times:


The nose wheel of a Cessna 182 fell off in flight, the pilot didn't notice and obviously was in for a little surprise on landing when he lowered what he thought was the nose wheel onto the runway at Canberra International Airport. The pilot was unharmed, the runway was closed for a little while and the ATSB is not investigating the incident.

This may sound odd at first, but when you look at their prioritization guidelines you understand why: no-one died or even got hurt and this was a private flight (priority level 6 out of 7, only above "High risk personal recreation/sports aviation/experimental aircraft operations"). In addition, and that's only my own uneducated guess, there is probably very little to be learned from this freak incident that would improve safety. Unless 182s around the world start loosing nose wheels in flight, investigating why this happened is not worth it.

The article goes on to say:

''[The pilot] said it was a very crunchy landing, but that he didn't know until he got out of the plane that he had lost the wheel,'' Ms Davy said.

This may sound funny, but is actually perfectly logical. There's no way the pilot can tell that the nose wheel fell in flight. The wheel just fell, and the pilot cannot see the front wheel from the cockpit anyway. Losing the nose wheel may reduce drag a little, but nothing noticeable through either the controls or the airspeed indicator.

On landing the noise of the nose wheel fork ploughing the runway must indeed have been very "crunchy", and the nose-down attitude surely indicated that something had gone wrong.

I just love the fact that the pilot went to the turf farm a week or so later to collect the missing wheel. Goes to show you never know where aviation might take you.