procedure turn or straight in

The question of when a procedure turn is required versus when a straight-in approach is expected sits at the intersection of regulatory language, charting conventions, and real-world ATC practice — and the disconnect between those three elements creates genuine confusion for instrument-rated pilots operating in the IFR system. Per AIM 5-4-9 and 14 CFR Part 97, a procedure turn is required when it is depicted on the approach chart and the aircraft is being positioned from a fix that necessitates course reversal, unless the published chart segment is marked "NoPT," the pilot receives an explicit straight-in clearance, or ATC is providing radar vectors to the final approach course. When radar vectors are provided, a procedure turn is never appropriate — executing one would create a serious collision hazard and constitute a deviation from ATC instructions. The reference to a "red course" in the original question most likely refers to the procedure turn outbound leg or barb as depicted in a specific charting format, such as Jeppesen, where color coding differentiates segments of the procedure.

The ambiguity arises most acutely when ATC issues a clearance such as "Cleared for the ILS Runway 28 approach" without specifying vectoring to final or explicitly waiving the procedure turn. In that scenario, regulatory and AIM guidance is clear: if the pilot is being positioned from the IAF in a manner that requires course reversal and no "NoPT" notation applies, the procedure turn is mandatory. However, many TRACON and approach control facilities routinely position aircraft via radar vectors without using the phrase "vectors to final" explicitly, or they expect pilots to proceed direct to the FAF based on routing that makes the procedure turn geometrically unnecessary. This creates a gap between what the regulation requires and what controllers actually expect, and it places the burden of clarification squarely on the pilot. A simple pilot request — "Do you want the procedure turn or straight-in?" — resolves the ambiguity immediately and is consistent with both good airmanship and CRM principles.

The practical operational guidance for professional and corporate pilots is unambiguous: when in doubt, ask. IFR clearances are not complete until the pilot understands the expected routing, and no controller will penalize a pilot for requesting clarification on a procedure turn requirement. For Part 91, 91K, and 135 operators, this matters beyond individual flights — failure to fly a published procedure turn when required, or conversely flying one when not expected, can lead to traffic conflicts, altitude busts near the FAF, and loss of situational awareness in IMC. Standard operating procedures at professional flight departments should explicitly address this scenario in their approach briefing flows, ensuring the crew confirms with ATC whether a procedure turn is expected before commencing the approach segment.

The broader context here reflects a persistent structural issue in U.S. instrument operations: the gap between charted procedures and operational norms in radar environments. Most of the U.S. IFR system operates with radar coverage, and ATC routinely vectors aircraft to final in a manner that renders procedure turns operationally obsolete at many facilities — yet the regulatory and charting infrastructure still presumes pilots will fly the full published procedure absent instruction otherwise. The FAA's ongoing work on procedure design and the expansion of RNAV and RNP approaches has reduced reliance on traditional procedure turns at many airports, but thousands of legacy VOR, ILS, and NDB approaches with published procedure turns remain active. Pilots flying into lower-traffic or non-radar environments — particularly during ferry flights, training, or operations into rural airports — must be especially careful not to assume the radar-vector habits of busy terminal environments apply universally. The discipline of reading the applicable charting notes, confirming ATC intent, and flying the published procedure when required is a foundational instrument skill that does not become optional simply because local ATC practice has evolved informally around it.