Slow is Smooth, and Smooth is Fast
Flight Debrief, Cessna C172RG VH-JVG 1.2h, Moorabbin - Essendon - Moorabbin (2 x full stops)
Learning Points:
The Flight
Essendon
An Essendon VFR approach has been something I've been wanting to practice and execute for a few months. I have been a passenger in two Essendon approaches, once in a TBM Socata several years ago and more recently on a Mustang flight from Moorabbin to Essendon (six minutes of flight time!), and tried to take in as much as possible from an osmosis-learning perspective. I remember being amazed at the high rate of workload and constant procedural tempo, but also at how sequential and controlled the two pilots on those flights made it seem.
I used a controlled airspace entry the week prior as a building block in my preparation for Essendon - with a Melbourne City orbit requiring Essendon Tower's clearance and control.
Chair Flying
I haven't chair flown for awhile, as I've written before on how I found it not a helpful method for my own style of learning. But, I do find writing out procedures in bullet point format, and running these procedures over a map to be an effective visualisation method. The approach I've found to work is:
This approach worked well for my biennial flight review earlier in the year, and I've since repeated it particularly for high workload flight phases.
"No, no. Do it... doucement. Do it, very slowly."
I planned to be at Essendon just before 11:00 in order to make a meeting. I was running late, and was acutely mindful of not rushing. The morning of the flight I had a list of final preparation I needed to achieve: flight notification, call Essendon Operations Officer, lodge SARTIME, review weather & NOTAMs, kneepad finalisation, and a final check of everything.
I worked really deliberately to make sure, during my morning preparation, and subsequent pre-flight checks and procedures, that I was not rushing. Despite being behind time - I needed to deliberately control myself to be slow, thorough, and sequential with every step and checklist. This conscious effort to accept delays, and to prioritise slowness and smoothness of my pre-flight checks worked very well as by assigning such importance to it, treating it like a sterile cockpit environment, it became a non-negotiable factor in my flight preparation.
Thus, while my checks and preparation did feel rushed - I did not feel like I had compromised my safety or preparation through being so deliberate. The flight proceeded well and followed the below flow:
Recommended by LinkedIn
Essendon Departure, Moorabbin Entry
After my meetings finished I went and found a quiet spot in the terminal to prepare my flightplan for the trip home. It was nice not having time pressure, so I enjoyed slowly planning my trip and going through an abbreviated visualisation flow as per the above points.
One aspect I wasn't clear on was once I was airborne, would Tower vector my deparature directions or was I selecting headings. I called Todd, who helpfully explained that Essendon should clear me per my flight plan (via Westgate Bridge).
I had also asked my friend and pilot, Steve, earlier in the week what to readback when ATC announced that I was "leaving controlled airspace," as I wasn't sure if a readback or acknowledgment was necessary. Steve's guidance was that trying to understand what ATC's intent with a communication was helpful. For instance, where they are pointing out traffic information, or departing controlled airspace, they're largely wanting to ensure my safety and situational awareness so they do not have responsibility any longer. A simple callsign response, "JVG," can achieve this. This was the case leaving Essendon's airspace on departure, as well as on various traffic advisory calls when inbound to Moorabbin.
Per ERSA's instructions I also called the airport operations officer before departing Moorabbin, and again to gain tarmac access at Essendon. Keery and Greg (different shifts) were super helpful in ground instructions, parking directions, and also when I was preflighting before YMEN departure, rather than ask over radio where the runup bay, I called the OPSO. Thank you!
Departure flow was as follows:
Approaching Moorabbin was busy, with lots of inbound calls at the approach points. I was tracking south over water preparing for my inbound Carrum call. As I was over Shoal turning inland I heard another aircraft reporting inbound at Carrum. I spotted him, delayed my inbound, and then used him as a tracking aid as I followed him while reporting inbound. I was cleared downwind runway 17R.
As I tracked for downwind, another aircraft reported inbound from Brighton and I thought Tower would either slot him ahead of my preceding aircraft, or behind me. As it happened, Tower advised me of the traffic over Moorabbin Oval and asked me to widen my approach to slot in behind him. I was not visual, and advised. Lots of radio traffic, and I jumped in once visual and followed him in.
I was cleared to the apron by Tower instead of needing to make a ground call.
Landed and refuelled just in time for my work weekend wind-down call! The only thing I neglected to do was cancel SARTIME, and I received a call at 17:00 local... Whoops.
Next Flight
Co-Founder and VP Strategy at Seeing Machines
1ySomehow this post reminds me of how to write good code. Slow is smooth and smooth is fast. Mental preparation in the morning. Efficient execution through the day, not losing focus from uncheduled interupts. Maybe good software engineers could make good pilots? 😁
Engagement Manager - Defence Science Institute
1yPeter Nicholls