• Skip to primary navigation
  • Skip to main content
General Aviation News

General Aviation News

Because flying is cool

  • Pictures of the Day
    • Submit Picture of the Day
  • Stories
    • News
    • Features
    • Opinion
    • Products
    • NTSB Accidents
    • ASRS Reports
  • Comments
  • Classifieds
    • Place Classified Ad
  • Events
  • Digital Archives
  • Subscribe
  • Show Search
Hide Search

Pilot not transmitting on CTAF causes near miss in pattern

By General Aviation News Staff · May 15, 2025 · 4 Comments

This is an excerpt from a report made to the Aviation Safety Reporting System. The narrative is written by the pilot, rather than FAA or NTSB officials. To maintain anonymity, many details, such as aircraft model or airport, are often scrubbed from the reports.

At Bowling Green-Warren County Regional Airport (KBWG) in Kentucky, winds were 310@07G20. My student and I were back taxiing on 30 for departure.

We heard Aircraft Y on the CTAF saying he was “taxiing to Runway 21 for a downwind departure to the north.” This would be the last transmission we heard from that pilot.

I immediately transmitted over CTAF that we were “back taxiing on Runway 30 and would be a crosswind departure to the south.”

I thought the other pilot’s runway selection was a strange course, choosing the longer runway, but with a crosswind gusting to 20 knots.

Less than a minute later, my student and I had completed our back taxiing and were lined up in position for departure on 30. We were simulating a short field departure, so we held in place for a moment as RPM stabilized at full power.

We couldn’t see Aircraft Y anywhere. Not by sight and not by ADS-B.

We let off the brakes and carried out a textbook short-field takeoff. Not long after we left ground effect, Aircraft Y came into view just to our right and on their climb-out from Runway 21. He was much faster than our aircraft.

I took the flight controls and turned right to avoid a mid-air collision. The closest we got to each other was probably within 400 feet horizontally and 150 feet vertically.

Once clear of conflict I transferred controls back to my student, who continued our takeoff and departed the pattern to the south off the crosswind leg.

We never heard from the pilot again. He did depart off the downwind.

I tried to find his tail number on ADS-B just moments after we were above 1,500 feet AGL. No luck. I suspect he turned off his ADS-B because he knew he’d screwed up.

I asked my student “Did I miss anything? Did you hear him say he was taking off, departing, on the roll, or on the go for Runway 21?” My student didn’t hear anything of the sort either.

To the best of our knowledge, this guy made a single radio call to say that he was leaving the ramp area and taxiing to Runway 21 via Taxiway A. Never made an announcement that he was turning onto the runway or beginning his takeoff. We were very clear in stating our every position, action, and intentions.

Primary Problem: Human Factors

ACN: 2189275

When you click on the link it will take you to the ASRS Online Database. Click on Report Number and put the ACN in the search box, then click Search. On that page, click on “view only the 1 most recent report.”

Reader Interactions

Share this story

  • Share on Twitter Share on Twitter
  • Share on Facebook Share on Facebook
  • Share on LinkedIn Share on LinkedIn
  • Share on Reddit Share on Reddit
  • Share via Email Share via Email

Become better informed pilot.

Join 110,000 readers each month and get the latest news and entertainment from the world of general aviation direct to your inbox, daily.

This field is for validation purposes and should be left unchanged.

Curious to know what fellow pilots think on random stories on the General Aviation News website? Click on our Recent Comments page to find out. Read our Comment Policy here.

Comments

  1. Ronny says

    May 16, 2025 at 6:30 am

    If there was a sudden electrical failure then all avionics could shut down. I doubt that he would turn off ADSB on purpose. Good for you for keeping your head on an swivel.

    Reply
  2. Mark says

    May 16, 2025 at 6:22 am

    “ I suspect he turned off his ADS-B because he knew he’d screwed up.”

    How did he screw up?

    Reply
  3. Scott Patterson says

    May 16, 2025 at 4:59 am

    Maybe next time be more vigilant of runway 21 since you knew he was there somewhere, instead of preoccupied with the textbook soft field. Since he wasn’t in sight or on ADS-B did you try to contact him on CTAF before brake release? Non towered airports with intersecting runways require extra caution, especially when focusing on training.

    Reply
    • Bibocas says

      May 16, 2025 at 9:58 am

      You’re correct Mr. Scott Patterson.

      Reply

Leave a Reply to Mark Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

© 2025 Flyer Media, Inc. All rights reserved. Privacy Policy.

  • About
  • Advertise
  • Comment Policy
  • Contact Us
  • Privacy Policy
  • Writer’s Guidelines
  • Photographer’s Guidelines