Filing an IFR flight plan with an IAF or IF as a route waypoint is a legitimate and widely used practice, particularly at low-traffic airports where a single instrument approach serves the favored runway. The pilot in this scenario correctly identified that with winds favoring one runway and only one RNAV approach available, including the IAF in the filed route was a reasonable way to communicate intended routing to ATC. The controller's objection — that the pilot is not guaranteed to receive that approach — is technically accurate but does not render the filing improper. Pilots routinely file to approach fixes knowing that ATC retains full authority over final routing and approach assignments; the filed route is a request and a planning tool, not a contract.
The AIM and FAA Order JO 7110.65 both acknowledge and support filing to approach fixes, including IAFs and IFs on RNAV procedures. Filing to an IAF signals to ATC and flight data systems how the pilot intends to transition from the en route structure to the terminal environment. At airports with minimal traffic and a single viable approach, this kind of filing actually helps controllers sequence the aircraft efficiently and reduces coordination workload. The confusion in this exchange likely stems from a less experienced or lower-familiarity controller at a quieter facility who may not regularly see approach-fix-inclusive flight plans and defaulted to a reflexive objection about approach assignment uncertainty.
The controller's follow-on suggestion — to file the IF instead of the IAF — is itself puzzling, because on many RNAV approaches designed with a "T" or "Y" configuration, the IF is a single shared fix that also functions as an IAF for arrivals from specific directions. A combined IAF/IF waypoint is common on GPS approaches where the charted intermediate fix lies along the published final approach course and serves as both the entry point from multiple IAF transitions and the beginning of the intermediate segment. If the fix in question was labeled as IAF/IF on the approach chart, the controller's distinction was operationally meaningless.
For professional and IFR-current pilots, the practical takeaway is that filing to an IAF or IF is appropriate and should not generate concern, but pilots should be prepared for controllers unfamiliar with the practice to push back. Knowing the approach plate cold — specifically how a fix is categorized and whether it carries a combined IAF/IF designation — allows pilots to respond authoritatively and maintain the filed routing or negotiate a sensible alternative. Part 135 and corporate Part 91K operators who frequently file to low-density airports benefit from building this knowledge into crew briefing standards, particularly when operating into fields served by only a single approach procedure.
The broader trend here reflects a growing gap between RNAV approach design complexity and line-controller familiarity at terminal and TRACON facilities that see limited traffic. As the FAA continues to publish PBN approaches to previously unserved or underserved runways, pilots will increasingly encounter controllers who are less fluent in the procedural structure of those approaches. Understanding IAF, IF, FAF, and the T/Y design architecture is no longer just an instrument rating knowledge item — it is a practical communication skill for any IFR operator filing into the expanding universe of GPS-only approach environments.