Too close for comfort

3653
Piper Archer

By Des Webster

I was flying a Piper Archer from Richmond to Young in December 2018. Around midday I was approaching Young airport from the north-east, expecting to join the circuit midfield crosswind for a landing on runway 01.

I was on descent to circuit height of 2300 feet and was at about 2500 feet when I turned to head perpendicular to the runway about two nm east of the runway on the inactive side, aiming to cross over the threshold at the far end of the runway. I had radioed inbound intentions at 10 nm and again at around three nm to confirm that I was manoeuvring on the inactive side to join midfield crosswind for runway 01.

There had been no other calls received on the frequency. About one nm from the runway, I noticed another aircraft heading straight for me and about 50–100 feet above me at my 10 o’clock. It was travelling parallel to the runway. I picked it up quite late as I was not expecting any other aircraft to be in the area as there had been no other radio calls.

I immediately dived to put some extra space between us and was very concerned the other aircraft might be on descent to circuit height. Fortunately, it safely passed over and behind me. However, it was too close for comfort and, given there was no indication on the radio or change in their flight path, I do not believe the other aircraft had ever seen me.

Somewhat shaken, I continued my approach, giving radio calls on downwind and final and landed as quickly as I could, as I thought the other aircraft may also be planning to join midfield crosswind. It did give a belated radio call a few minutes later that it was in the circuit, but as it was not in my immediate vicinity, I didn’t really take it in and focused on my landing. It never actually appeared on final.

I was left wondering what could have happened if I had just been a fraction higher and fraction later. Anyway, I learnt two things from the near miss:

  • Just because there is nothing on the radio, doesn’t mean there is nothing there. The other aircraft may have called on the wrong frequency or had a malfunctioning radio or may simply not called at all. One must always maintain high vigilance in the vicinity of any airstrip and diligently scan the skies.
  • Just because you are on the right doesn’t mean you will be given way to. The other aircraft may not see you—their view may be obstructed or they may be distracted. It’s no use having the right of way in a collision!

In addition, there was a further safety issue in this incident. After the near miss, I was left uncertain as to what the other aircraft’s intentions were and whether it knew I was even in the circuit. Given its initial position, it could have been manoeuvring to join midfield crosswind for 01 as I was or it could have been downwind for 19, as the wind was light and largely crosswind.

This confusion led me to hurry my approach and landing, as I felt I needed to get on the ground as fast as possible. As it turned out, the landing, though not my best, was fine but the risk had been increased by the confusion and distraction that confusion had caused. If the other aircraft had radioed to say they had in fact seen me and provided intentions, I would have felt more comfortable and not hurried my landing.

So other things learnt from this incident were:

  • If you do have a close call, radio the other aircraft to confirm you have sighted them and confirm your intentions even if you have already broadcast them. The other aircraft may have been on the wrong frequency and not received your call at the time. Knowing each other’s position and intentions around the airstrip is vital to safe manoeuvring.
  • Assuming what another aircraft will do can be dangerous. In this instance, I assumed they were joining for runway 01 but if it was in fact 19, then there was potential for another incident. Sometimes, as in this case, you have to assume, but be aware that assumption may not be right and try to do whatever you can to validate the assumption.

 

 

 

 

 

8 COMMENTS

  1. I think I would have put distance between me and the airfield and then do some orbits and wait while I got settled and try to accertain the other aircraft was on the ground, or not in the vicinity.
    Then make a plan to join the circuit and land in my own time.

  2. This sort of event happens far more than most realise especially with today’s well equiped light A/C where the driver has their head in the cockpit more than ever fiddling!
    When I was operating high perf turbines/jets in CTAF’s my head was on a swivel all the time! So many out there that are in a confused world of their own when flying!
    Flying is risky, mostly calculated risks but someone or something is always trying to kill you!

    • I’d have thought distraction would be as much, if not more, of an issue in ‘high performance turbines / jets’ given how well equipped they tend to be.

      Whether you are a (self professed) experienced jet jockey or a near novice piston wrangler, the need for a thorough lookout and maintained situational awareness remains identical.

      My flight instructor was vastly experienced but still believed he was in possession of a license to learn.

  3. Not that it would correct a faulty radio or incorrect frequency BUT! I have always been concerned with the “relaxation” in the mandatory reporting/communication rules. What was so wrong with requiring radio communication at certain phases of flight ? We now have pilots assuming that there is no one around, because they haven’t heard any transmissions, so they don’t make any either, compounding the problem. I get very “twitchy” when I have not heard anything for a while – check my frequency selection – wait a little longer – then do an “All Stations” position report – still nothing – contact ATC for area QNH. I always get something from ATC, so “all good”. My point is, if its too quiet, start checking – it might be your radio or theirs or it might just be that you are all alone up there.

  4. It’s a sad fact that most near misses go unreported. Alerted see and avoid is the best we’ve got… low risk doesn’t mean no risk unfortunately.

  5. I’ve had the ‘pleasure’ of being mid takeoff roll only to see a landing light flick on in the sky above and ahead of me. A crop duster on short final, downwind with more than 20 knots on the tail, and no radio calls. Aborted my takeoff, pulled off side of runway. Crop duster landed, made a radio call to say ‘sorry about that, long day, tired, probably shouldn’t be flying’.

    Lesson I took from this: we always check for inbound aircraft when entering the active, but how often do we check for inbounds on our climb out path.

LEAVE A REPLY

Please enter your comment!
Please enter your name here