PAR vs. ASR vs. No-Gyro Approaches: Radar Talkdowns Explained — What the Controller Gives You, What You Fly, the Phraseology, Half-Standard-Rate on Final, and Where to Find the Minimums
Most instrument approaches you fly are procedure-based: you track a published course with your own equipment and descend on published altitudes. Radar approaches are different. A controller watching your target on a radar display gives you headings — and on a precision approach radar, your position relative to a glidepath — by voice, continuously, all the way to minimums. The only airborne equipment required is a working transmitter and receiver. That makes the radar approach the ultimate backup: when the nav equipment fails, the GPS loses integrity, or the heading indicator quits, a controller can still talk you to the runway.
Three variations matter. The PAR (precision approach radar) gives azimuth and elevation guidance to a decision height — the closest thing to an ILS you’ll fly without your own localizer and glideslope. The ASR (airport surveillance radar) gives azimuth only, to an MDA, with you managing the descent. The no-gyro approach is a technique layered on either: when your heading reference is unreliable, the controller stops assigning headings and instead commands “turn left … stop turn,” with you turning at standard rate until final and half standard rate on final. This post covers all three as AIM 5-4-11 defines them, the phraseology, your responsibilities, when guidance ends, the regulatory frame, where to find the minimums, a worked scenario, and the checkride questions.
Study this full length lesson (video, podcast, flashcards, and quiz) here: Full Length Lesson >
The Regulatory Frame (AIM 5-4-11)
What a radar approach is:
An approach in which the radar controller vectors the aircraft to align it with the runway centerline and continues vectors to keep it on course until the pilot can complete the approach and landing by visual reference to the surface
Two types: precision (PAR) and surveillance (ASR)
The only airborne radio equipment required is a functioning transmitter and receiver
Your nav receivers, GPS, and even your heading indicator can be dead and a radar approach still works
Who can get one:
A radar approach may be given to any aircraft on request, and may be offered to aircraft in distress or to expedite traffic
An ASR may not be approved unless there’s an ATC operational requirement or an unusual or emergency situation — it’s not a convenience approach at busy civil facilities
Availability depends on the facility: PARs are mostly at military fields; ASR capability exists at some civil approach controls
The TPP’s “Radar Instrument Approach Minimums” pages list the airports, runways, and minima
Weather minimums still apply:
Acceptance of a PAR or ASR does not waive the prescribed weather minimums for the airport or for the operator
The decision to make a radar approach when reported weather is below minimums rests with the pilot (Part 91 can begin an approach regardless of reported weather; Part 121/135 cannot continue past the FAF below minimums)
PAR and ASR minimums are published on separate pages of the TPP, not on a plate
Brief them like any other minimums
Radar service:
Automatically terminated at the completion of a radar approach
Guidance can be terminated earlier by the controller (unsafe to continue), at your request, or — for civil aircraft — when you report the runway, airport, or required visual reference in sight
Before the final, the controller issues specific lost-communications instructions for the radar approach (if no transmissions are received for a stated interval, attempt contact on another frequency, then execute the missed approach or proceed as instructed) — copy them
The whole approach is a conversation

PAR — Precision Approach Radar
The controller provides the localizer and the glideslope by voice.
What you get:
Highly accurate navigational guidance in azimuth and elevation
Headings to fly that direct you to, and keep you on, the extended runway centerline
A warning to anticipate glidepath interception about 10 to 30 seconds before it occurs, and the instruction to start descent
Range from touchdown at least once each mile
The decision height:
A PAR is a precision approach flown to a published decision height
The published DH is given only if the pilot requests it — ask for it in the brief (“say decision height”) or look it up on the TPP radar minimums page
Navigational guidance in azimuth and elevation is provided until the aircraft reaches the DH
After DH, advisory course and glidepath information continues until you pass over the landing threshold, where you’re advised of any deviation from centerline
The phraseology (what the calls mean):
Elevation deviations are given with the relative amount — “slightly above glidepath” / “well below glidepath” — and you adjust your rate of descent to return to the path
Trend information is added and may be modified by “rapidly” or “slowly” — “well above glidepath, coming down rapidly”
Azimuth: “slightly left of course, turn right heading 265” / “on course”
“On course, on glidepath” is the goal; the controller’s job is to say something every few seconds
The safety zone:
If you deviate outside specified safety-zone limits in azimuth and/or elevation and continue outside them, the controller directs a missed approach or a specified course — unless you have the runway environment in sight
A PAR controller will not let you fly a badly off-path approach into the weather
Respond to the corrections; the limits are tighter than you think
“Execute missed approach” on a PAR is an instruction, not a suggestion
What you fly:
The assigned headings, promptly and precisely — small heading changes, no overshooting
Your own pitch and power to hold the glidepath per the controller’s calls: “slightly above” means reduce the descent rate a little, not dive
Airspeed, configuration, trim, checklists — set before the talkdown begins
At DH: the 91.175(c) visual references → land; otherwise the missed, immediately
The gotchas:
The tempo: calls come continuously; there’s no time to reconfigure or troubleshoot
Over-controlling: “slightly” means a small correction; chasing every word with large inputs produces oscillations the controller then has to talk you out of
Readbacks: as you begin final the controller will say “do not acknowledge further transmissions” — the controller watches the result on the scope; acknowledge the clearance, the DH if given, the missed approach instructions, and the lost-comm instructions before that point
Stabilize before final or you’ll drown in corrections
ASR — Airport Surveillance Radar
The controller provides the localizer; you provide the descent.
What you get:
Navigational guidance in azimuth only — headings to align you with the extended centerline
Less precise radar than a PAR, so less accuracy and higher minimums
No elevation guidance — but the controller tells you when to begin descent to the MDA, or to an intermediate step-down fix minimum crossing altitude and then to the MDA
Your position each mile on final from the runway, airport, or MAP
The MDA:
An ASR is a nonprecision approach flown to an MDA
The published MDA for a straight-in ASR is issued to you before you begin descent
Recommended altitudes at each mile — based on the procedure’s descent gradient, down to the last mile at or above the MDA — are issued if you request them: ask for them, they make the descent a planned profile instead of a dive
When an ASR terminates in a circling approach, the circling MDA for your aircraft category applies
The MAP:
The controller advises you of the location of the MAP prescribed for the procedure (a distance from the runway, typically)
Guidance is normally provided until you reach the MAP
At the MAP, the controller terminates guidance and instructs you to execute the missed approach unless you have the runway, airport, or heliport in sight
There’s no “continuing to look” past the MAP on an ASR — the controller ends it
When guidance is terminated early:
If at any time the controller considers that safe guidance for the rest of the approach can’t be provided, guidance is terminated and you’re instructed to go missed
On your request
For civil aircraft, when you report the runway/airport in sight or indicate guidance isn’t needed
Radar service ends at the completion of the approach
The phraseology:
“Turn left heading 170, this will be a surveillance approach to runway 17; missed approach point is one mile from the runway; published minimum descent altitude 1,460”
“Six miles from runway, descend to your minimum descent altitude” / “recommended altitude 2,200” (if requested)
“Slightly right of course, turn left heading 168” / “on course”
“At missed approach point, execute missed approach unless runway in sight”
The gotchas:
Vertical discipline is entirely yours: this is where ASR altitude busts happen — step-down MCAs and the MDA are hard altitudes
Don’t treat it as a PAR lite; there is no glidepath, and “descend to MDA” is a clearance to a floor, not a path
Request the recommended altitudes each mile so you have a profile
Brief the missed early; the MAP is close in and the controller will call it
No-Gyro Approach
A technique for when your heading reference is gone.
When it’s used:
Available to a pilot under radar control whose directional gyro or other stabilized compass is inoperative or inaccurate — vacuum failure, a toppled or precessing DG, a failed AHRS, a frozen HSI
Also available to aircraft not equipped with a DG or stabilized compass that want radar handling
You advise ATC and request a “no-gyro vector” or “no-gyro approach”
The controller gives turn commands instead of headings, because you can’t fly a heading
How it works:
Instead of “turn left heading 180,” you’ll hear “turn left” … “stop turn”
The controller watches your track and stops the turn when you’re aligned
You make all turns at standard rate and execute each turn immediately on receipt of the instruction — the controller’s timing assumes no delay
Once turned onto final on a surveillance or precision approach, you’ll be advised to make turns at half standard rate — the finer rate for the finer corrections
Combined with PAR or ASR:
No-gyro is a turn-control method, not a separate approach; it’s layered on an ASR (azimuth by start/stop turns, vertical yours) or a PAR (azimuth by start/stop turns, elevation by the talkdown)
Everything else about the underlying approach is unchanged: ASR to an MDA, PAR to a DH
The defining feature is “turn left … stop turn,” not heading assignments
Partial-panel flying with a controller as your heading indicator
What you fly:
Standard-rate turns (the turn coordinator or turn-and-bank is your reference — it doesn’t depend on the gyro that failed, if it’s electric and the failure is vacuum) initiated instantly on “turn left/right,” and rolled out instantly on “stop turn”
Half standard rate once on final, when instructed
Stable airspeed: the bank angle for standard rate depends on airspeed, so a speed change changes the turn rate the controller is counting on
The vertical profile as assigned (ASR) or per the talkdown (PAR)
The gotchas:
Lag: a second or two late on “stop turn” at standard rate is several degrees of heading; late on half rate is less, which is why final is flown at half rate
Rate consistency: hold airspeed so the controller’s mental model of your turn matches reality
Partial panel plus configuration changes plus a talkdown is a lot — configure early, trim, and keep the scan on the turn coordinator and airspeed
Tell the controller immediately if you can’t hold a rate or you’ve lost another instrument
PAR vs. ASR vs. No-Gyro: Side by Side
PAR | ASR | No-Gyro | |
Guidance from the controller | Azimuth AND elevation (headings + glidepath calls) | Azimuth only (headings) | Turn commands (“turn left … stop turn”) instead of headings, layered on PAR or ASR |
Vertical | Controller’s glidepath calls; you adjust descent rate | Yours: descend when told, to step-down MCAs and the MDA; recommended altitudes each mile on request | Per the underlying approach |
Decision point | DH (precision) — given on request | MDA (nonprecision) — issued before descent | Per the underlying approach |
Position info | Range from touchdown at least each mile | Position each mile on final | Per the underlying approach |
Guidance ends | At DH; advisory to the threshold | At the MAP — controller terminates and instructs missed unless the field is in sight | Per the underlying approach |
Turn rate | Normal | Normal | Standard rate; half standard rate on final |
Equipment | A radio | A radio | A radio (and a turn coordinator helps) |
Minimums | TPP radar minimums page | TPP radar minimums page (higher than PAR) | Per the underlying approach |
Where | Mostly military fields | Some civil approach controls | Any radar facility, on request |
Practical Technique for All Three
Brief it like a checkride:
Which approach (PAR/ASR), to which runway, the DH or MDA (ask for the DH on a PAR; the MDA is issued on an ASR), the MAP (ASR), the missed approach instructions, the lost-comm instructions, and the no-gyro plan if your heading is gone
Who does what: the controller gives headings (or turn commands) and, on a PAR, glidepath calls; you fly airspeed, configuration, pitch/power, and the vertical profile on an ASR
Your hard gates: configuration complete before final; stabilized by 1,000 feet AGL in IMC; the decision at DH/MDA
Ten seconds, before the talkdown starts
Stabilize early:
Gear, flaps, approach speed, trim, and the descent power setting before the controller begins rapid corrections
A PAR or ASR final is no place to run a checklist
On a no-gyro, configuration changes alter the airspeed and therefore the turn rate — do them before the turns matter
Fly the airplane first; the controller handles the navigation
Readbacks and acknowledgments:
Acknowledge the approach clearance, altitudes, the MDA/DH, the missed approach instructions, and the lost-comm instructions
Once the controller says “do not acknowledge further transmissions,” stop — the continuous corrections don’t need readbacks, and acknowledging each one would jam the frequency; the controller sees the result on the scope
On an ASR, read back assigned altitudes and the MAP before final
If in doubt before that point, acknowledge with your call sign
The missed, mentally armed:
At DH on a PAR or the MAP on an ASR, the decision is instant — the controller will call it
The controller gives the missed approach instructions before the final; know them
Lost comms during the talkdown: fly the lost-comm instructions the controller issued before final (attempt contact on the stated frequency, then the missed approach or the instructed course), then 91.185 if still no contact
“Unable” or “say again” beats guessing
Say when you’re behind:
Radar approaches are offered to aircraft in distress; the controller expects a loaded pilot
“Unable to hold standard rate,” “need a moment,” “say again the MDA” are all appropriate
A no-gyro ASR with a vacuum failure in IMC is an emergency — say so
The controller can slow the tempo, extend the final, or re-sequence
Worked Scenario
The setup:
Vacuum failure in IMC: attitude indicator and heading indicator dead; turn coordinator (electric), airspeed, altimeter, VSI, and magnetic compass working. GPS still working but the pilot’s heading reference is gone. Nearest facility with ASR capability 20 NM away; weather 800 overcast, 2 miles
The call:
“Approach, N123AB, vacuum failure, partial panel, request no-gyro surveillance approach, runway 17”
Approach: “N123AB, roger, this will be a no-gyro surveillance approach runway 17; make all turns at standard rate; missed approach point is one mile from the runway; published MDA 1,460; missed approach: climb to 3,000 on runway heading, expect vectors; if no transmissions received for one minute in the pattern or fifteen seconds on final, attempt contact on 121.5 and proceed with the missed approach; turn right … stop turn”
Pilot: acknowledges; configures early, sets approach speed, trims; standard-rate turns on the turn coordinator, started and stopped immediately
“Request recommended altitudes each mile”
On final:
“On final, make turns at half standard rate; do not acknowledge further transmissions … turn left … stop turn … on course … six miles from runway, descend to your minimum descent altitude; recommended altitude 2,500 … five miles, recommended altitude 2,200 … slightly left of course, turn right … stop turn … two miles, recommended altitude 1,600 … one mile from runway, at missed approach point”
Runway lights in sight at 1.3 NM: “runway in sight” — controller: “guidance terminated, contact tower”; land
Not in sight at the MAP: “execute missed approach, climb to 3,000 runway heading” — comply; the controller continues no-gyro vectors to the alternate plan
What made it work:
A radio, a turn coordinator, and immediate, consistent standard-rate (then half-rate) turns
Recommended altitudes gave a profile; the MDA was a hard floor
Configuration and speed set before the turns mattered
Declaring the partial panel got the tempo and help that a no-gyro approach is designed for
Common Pilot Mistakes
Treating an ASR like a PAR and expecting glidepath calls — the descent is yours
Not requesting the recommended altitudes on an ASR, then diving to the MDA
Busting a step-down MCA or the MDA on an ASR — the only altitudes you get are hard ones
Not asking for the DH on a PAR (it’s given only on request)
Over-controlling PAR corrections — “slightly” is small
Acknowledging every PAR correction after “do not acknowledge further transmissions” and jamming the frequency
Starting or stopping no-gyro turns late, or changing airspeed mid-turn and changing the rate
Forgetting to switch to half standard rate on final when instructed
Continuing past the ASR MAP after the controller terminates guidance
Assuming a radar approach waives the weather minimums
Not copying the lost-comm instructions, or not declaring the partial panel or the emergency that made the radar approach necessary
Checkride Questions — With Answers
“What equipment do you need for a radar approach?”
Only a functioning radio transmitter and receiver (AIM 5-4-11).
“What’s the difference between a PAR and an ASR?”
A PAR provides azimuth and elevation guidance — headings plus glidepath calls — to a decision height; it’s a precision approach. An ASR provides azimuth only — headings — with the controller telling you when to descend to step-down altitudes and the MDA; it’s a nonprecision approach with higher minimums because the radar is less precise.
“On a PAR, how do you get the decision height?”
The published DH is given only if the pilot requests it; otherwise look it up on the TPP radar minimums page. Guidance continues to DH; advisory information continues to the threshold.
“On an ASR, what information does the controller give you?”
The MDA (before descent), when to begin descent (to a step-down MCA and/or the MDA), your position each mile on final, the location of the MAP, and — on request — recommended altitudes at each mile. At the MAP the controller terminates guidance and instructs a missed unless you have the runway or airport in sight.
“What is a no-gyro approach, and what turn rate do you use?”
A radar approach (ASR or PAR) in which the controller commands turns — “turn left … stop turn” — instead of assigning headings, used when the DG or stabilized compass is inoperative or inaccurate (or the aircraft has none). Make all turns at standard rate, executed immediately; once turned onto final, make turns at half standard rate when so advised.
“Does accepting a radar approach waive weather minimums?”
No. The published minimums for the airport and operator still apply; the decision to begin a radar approach with weather below minimums rests with the pilot (within the operator’s rules).
“Where are PAR and ASR minimums published?”
On separate radar instrument approach minimums pages in the TPP, not on an approach plate.
“When does radar service end on a radar approach?”
Automatically at the completion of the approach; guidance may be terminated earlier by the controller (unsafe to continue), on pilot request, or (civil aircraft) when the pilot reports the runway/airport in sight.
Final Thoughts
Radar approaches are the system’s answer to “everything in the panel has failed”: a controller who can see you, a radio, and a vocabulary of headings, glidepath calls, and turn commands that will get you to minimums. The PAR is a precision approach by voice; the ASR is a nonprecision approach with a controller flying the lateral half; the no-gyro technique replaces the heading indicator you lost with “turn left … stop turn” at standard rate, then half rate on final. None of them require anything but a working radio — and all of them require a pilot who has configured early, holds airspeed, responds to each call promptly and in proportion, and knows exactly where the decision point is.
Ask for the DH on a PAR and the recommended altitudes on an ASR; copy the lost-comm instructions; treat ASR altitudes as hard floors; turn immediately and consistently on a no-gyro; acknowledge what matters and go quiet when told; and say “unable” when you’re behind. The controller will do the rest.
On the Written Test and Checkride
Radar approaches appear on the instrument knowledge test and in instrument orals. The most commonly tested topics:
Radio-only equipment requirement
PAR: azimuth and elevation, DH on request, “slightly/well,” “rapidly/slowly,” range each mile, safety-zone missed, “do not acknowledge further transmissions”
ASR: azimuth only, MDA issued before descent, recommended altitudes each mile on request, MAP advised, guidance terminated at the MAP
No-gyro: start/stop turns, standard rate, half standard rate on final, immediate execution
Weather minimums not waived; ASR requires an operational need or emergency
Lost-comm instructions issued before final; TPP radar minimums pages; radar service terminated at completion
Quick Reference
Radar Approaches (AIM 5-4-11):
Controller vectors you to and along the extended centerline until you can land visually; only a functioning radio required
Given on request, offered to aircraft in distress or to expedite traffic; ASR may require an operational need or emergency
Weather minimums not waived; PAR/ASR minimums on the TPP radar minimums pages
Lost-comm instructions issued before final — copy them
Radar service ends automatically at completion; guidance can be terminated earlier (controller/safety, pilot request, civil “field in sight”)
PAR — Precision:
Azimuth + elevation by voice; headings to the centerline; glidepath intercept anticipated 10–30 sec ahead; range each mile
Deviation terms “slightly / well above/below glidepath”; trend “coming down rapidly / slowly”
Flown to a DH — given only on request; guidance to DH, advisory to the threshold
Outside the safety zone and not correcting → directed to go missed (unless runway environment in sight)
“Do not acknowledge further transmissions” on final
Mostly military fields
ASR — Surveillance:
Azimuth only; less precise radar → higher minimums
MDA issued before descent; told when to descend (to step-down MCA and/or MDA); position each mile; recommended altitudes each mile on request
MAP location advised; at the MAP, guidance terminated and missed instructed unless the runway/airport is in sight
Flown to an MDA (circling MDA by category if circling)
Some civil approach controls
No-Gyro:
DG/stabilized compass inoperative or inaccurate (or none installed) → request “no-gyro vector/approach”
Controller commands “turn left/right … stop turn” instead of headings
Standard rate, executed immediately; half standard rate on final when advised
Layered on ASR (your vertical) or PAR (talkdown vertical); hold airspeed — bank for standard rate depends on it
Technique:
Brief: approach type, DH/MDA (ask for the DH), MAP, missed instructions, lost-comm instructions, no-gyro plan
Configure and trim before the talkdown; stabilized by 1,000 ft AGL IMC
Acknowledge clearance/minimums/missed/lost-comm before final; then no readbacks of corrections
ASR: altitudes are hard floors; request recommended altitudes; the controller calls the MAP
No-gyro: turn coordinator is the reference; start/stop instantly; keep speed constant
Say “unable” / declare the emergency when behind
Key Principle:
PAR = the controller talks you down in azimuth and elevation to a DH; ASR = the controller gives headings only and you fly the descent to an MDA with recommended altitudes on request; no-gyro = “turn … stop turn” at standard rate, half rate on final, when your heading reference is gone. All need only a radio; none waive the weather minimums; all reward a pilot who configures early, holds airspeed, and responds promptly.
Study Full Aviation Courses:
wifiCFI's full suite of aviation courses has everything you need to go from brand new to flight instructor and airline pilot! Check out any of the courses below for free:
Study Courses:
Checkride Lesson Plans:
Teaching Courses:

Author: Nathan Hodell
CFI, CFII, MEI, ATP, Creator and CEO
Nathan is an aviation enthusiast with thousands of hours of flying and dual instruction over the past 15+ years. Through his aviation career he has been able to earn his ATP, fly as an airline pilot, own/operate flight schools, and create and host wifiCFI.


