Flight Following Fail


I’m part of a pilot’s breakfast group that flies from the airport in Big Bear City, Calif., elevation 6700 feet, to lower-elevation airports in the Los Angeles Basin airspace. On this day, we were headed to the Corona (Calif.) Municipal Airport (KAJO) and its good restaurant.

Upon departing our home airport, we request VFR flight following from ATC so we are in the system. The controllers at SoCal Approach keep a watchful eye on us for any conflicts and clear us through the crowded airspace.

Having done this flight many times before, we all anticipated a controller handoff to 135.4 MHz about 10 nm from Corona and then a final VFR let-loose about five nm out. We all had the frequency dialed in ahead of the first handoff, ready to comply, but this day’s controller didn’t do the handoff. Instead, he just turned us loose on our own with, “Radar services terminated, squawk VFR.” This was a real surprise to us!

On both sides were towered airports like Chino and Riverside, with their own Class D airspace and frequencies, and here we were heading straight for non-towered Corona without the blessing of ATC anymore. One of our guys accidentally clipped Chino’s airspace without talking to their tower and received a comm call from ATC.

I climbed a couple of hundred feet to get over the Riverside airspace and motored onward to Corona. It was always much easier and comfortable when ATC kept us in the system.

On the flight back, all handoffs occurred normally and there were no calls or additional surprises from ATC.

The lesson learned is that you can’t always assume that what happened last time will happen again. You have to be ready for the unexpected, and know the airspace boundaries and frequencies, just in case ATC gets busy or goes out for a break and leaves you on your own.

Learning Experiences

Have you encountered a situation or hazardous condition that yielded lessons on how to better manage the risks involved in flying? Do you have an experience to share with Aviation Safety’s readers about an occasion that taught you something significant about ways to conduct safer flight operations? If so, we want to hear about it.

We encourage you to submit a brief (500 words) write-up of your Learning Experience to Aviation Safety for possible publication. Each month, Aviation Safety publishes a collection of similar experiences sent to us by readers. Sharing with others the benefit of your experience and the lessons you learned can be an invaluable aid to other pilots.

You can send your account directly to the editor by e-mailing it to [email protected]. Put “Learning Experience Submission” in the subject line; add your name and daytime telephone number at the bottom of the e-mail.

Your report will be considered for publication in the Aviation Safety’s readers’ forum, “Learning Experiences,” and may be edited for style and length. Anonymity is guaranteed if you want it. No one but Aviation Safety’s editor is permitted access to the reports. Your name and telephone number are requested only so that the editor can contact you, if necessary.

While we can’t guarantee your submission will get published, we can guarantee that we’ll closely review and consider using it.

All Learning Experience submissions become the property of Aviation Safety and may be republished.


  1. VFR FF is subject to controller workload. It’s nice to have VFR FF, but to really get into the system have someone file IFR.


Please enter your comment!
Please enter your name here