Trust ATC, But Verify

We spend most of our IFR lives wrapped in the warm cocoon of radar coverage, vectored from point to point by the all-seeing presence of ATC. And while controllers are human and occasionally make mistakes, the checks and safety nets in place rarely result in close calls, let alone bent metal. Its also true that when clearances get tight in the final descent to the airport, responsibility is handed over to the pilot.

jwanwest

Wednesday, November 16, 2016 at 12:00 AM ET

Verified

Key Takeaways:

"RADAR REQUIRED" on IFR approaches signifies the need for ATC radar vectors to commence the approach, often due to the absence of an Initial Approach Fix (IAF).
For aircraft without DME or GPS, pilots must explicitly request ATC to call certain fixes (e.g., FAF), while relying on timing for others like the Missed Approach Point (MAP).
An Airport Surveillance Radar (ASR) approach offers an alternative, providing full ATC guidance with controllers making heading, trend, and MAP calls for basic aircraft.
Future updates will transition "RADAR REQUIRED" notes to "GPS or RADAR Required" and standardize the location of equipment requirements within the briefing strip.

See a mistake? Contact us.

We spend most of our IFR lives wrapped in the warm cocoon of radar coverage, vectored from point to point by the all-seeing presence of ATC. And while controllers are human and occasionally make mistakes, the checks and safety nets in place rarely result in close calls, let alone bent metal. It’s also true that when clearances get tight in the final descent to the airport, responsibility is handed over to the pilot.

Except when it isn’t. Consider the LOC Rwy 6 to Shreveport, LA (KSHV) and the note “RADAR REQUIRED.” Requirements stated in the plan view and not the approach title mean the requirement is for something other than the final approach segment. Here radar can play at three different levels.