A recent discussion on r/flying raises a deceptively simple but operationally important question: when requesting VFR flight following for a trip that includes an intermediate fuel stop, should a pilot state the ultimate destination or just the airport for the first leg? The consensus among experienced pilots answering this thread is straightforward — flight following is a leg-by-leg, discretionary ATC service, not a filed flight plan that carries through a stop. Pilots should tell the initial controller their destination for that specific leg (the fuel stop airport). Once on the ground and ready to depart again, a new flight following request should be made for the second leg to the actual final destination. Attempting to tell ATC the "final" destination while skipping over the interim stop can create confusion, since the controller will be planning handoffs and routing based on the stated destination, not anticipating a landing and restart partway through.
This matters to working pilots because flight following, unlike an IFR clearance or a filed VFR flight plan, is not a persistent, transferable service tied to a single flight plan number that survives a full-stop landing. It is a radar advisory and traffic-separation service provided on a workload-permitting basis, coordinated controller-to-controller as the aircraft transits airspace. When an aircraft lands, that specific flight-following instance terminates — the squawk code is typically dropped, and the "flight" from ATC's perspective is complete. Treating a multi-leg VFR trip as a single continuous flight-following request, especially across a full-stop fuel stop, misunderstands how the system works and can lead to controllers being unprepared for a landing they didn't expect, or unable to properly hand off the aircraft's intentions to the next sector.
For professional and corporate pilots who may not fly VFR cross-country often — jet operators are typically in a fully IFR environment where flight plans and stops are handled very differently — this thread is a useful reminder of the practical, informal nature of VFR services in the National Airspace System. It underscores a broader theme in general aviation: VFR flight following is a courtesy service, subject to controller workload, sector boundaries, and radar coverage, and pilots are responsible for re-establishing services at each leg of a multi-stop trip. This contrasts sharply with IFR operations, where a flight plan can include stops and reroutes are handled formally through amended clearances, and where lost-comm and handoff procedures are far more rigidly defined.
More broadly, this kind of question reflects the ongoing knowledge gap many pilots — both new and experienced — have about the boundary between VFR advisory services and IFR flight plan management, a gap that training programs and even instrument students sometimes gloss over since flight following is not a formally tested procedure in the same way IFR procedures are. For flight schools, mentors, and content creators in the aviation education space, threads like this highlight the value of explicitly covering "real world" VFR cross-country logistics — fuel stops, restarting flight following, and communicating intentions clearly to each new controller — since these operational nuances often aren't covered in depth during initial training but come up constantly in actual cross-country flying, including for corporate and charter pilots who may occasionally reposition aircraft VFR for maintenance ferries, positioning flights, or personal flying outside of their primary IFR operations.