Cleared to Land, Cleared for the Option, Land and Hold Short: Every Landing Clearance ATC Can Issue and What Each One Actually Authorizes

Every ATC landing clearance authorizes something specific, and the differences matter most when your workload is highest - on short final. Knowing exactly what each phrase permits, and what it doesn’t, is the difference between operating with precision and accepting a clearance you’re not fully prepared to comply with.

Cleared to Land: What It Authorizes (and What It Doesn’t)

Cleared to land is the most common landing clearance and the most specific: it authorizes a full-stop landing on the designated runway. When the controller issues it, the runway belongs to you. No other traffic will be authorized to use it until you’ve exited.

What it does not authorize: a touch-and-go, a low approach, a stop-and-go, or a go-around that returns you with different intentions. If your plans involve anything other than landing and stopping, communicate that before you’re established on final - not at the threshold.

The clearance remains active while you’re on the runway. You don’t need to switch to ground control the moment the wheels touch. But once you cross the hold short line on exit, you’re in ground’s domain. Switch frequencies and don’t sit on an active runway without anyone knowing your position.

What to Do If You Reach the Threshold Without a Clearance

At busy controlled fields, a saturated frequency can leave pilots on final without a landing clearance. The answer is unambiguous: you do not land without one. If you’re approaching the threshold and still haven’t been cleared, initiate a go-around, advise the controller, and wait for the sequence to sort out.

Landing at a towered airport without a clearance is a FAR violation - and a leading mechanism for runway incursions.

Cleared for the Option: Five Doors, One Choice

Cleared for the option authorizes any one of five operations: a full-stop landing, a touch-and-go, a stop-and-go, a low approach, or a missed approach. The controller is granting flexibility while protecting the runway for your use.

But the “option” doesn’t mean all five choices stay open until the flare. You pick one and communicate it before crossing the threshold. Another aircraft may be turning base. A departure may be holding for you. Your silence creates gaps in the controller’s traffic picture that can compress spacing behind you.

Standard practice: call your intent on short final. “Touch-and-go” or “full stop” transmitted early closes the loop.

Touch-and-Go: High Workload, Firm Standards

A touch-and-go authorizes landing and immediately applying takeoff power without a full stop - wheels down, configure for takeoff, power in, rolling.

The workload is real. You’re adjusting flaps, confirming controls, and managing power while rolling at speed with runway disappearing behind you. In a Cessna 172, this is manageable. In aircraft with constant-speed propellers or retractable gear, the reconfiguration checklist gets heavier - which is why many instructors transition to stop-and-goes when students move into complex aircraft. The brief stop allows proper reconfiguration. The touch-and-go does not.

One rule supersedes all technique discussion: if anything about the landing felt wrong - a bounce, excessive speed, an unstable touchdown - go around. The runway behind you is gone. A go-around from a bad landing is always the correct call over attempting to salvage a touch-and-go from an unstable touchdown.

Stop-and-Go: Calculate Available Runway Before You Land

A stop-and-go authorizes landing, bringing the aircraft to a complete stop on the runway, and then taking off from that point without exiting to a taxiway.

The critical variable is available runway. If you stop at the midpoint of a 5,000-foot runway, you’re taking off with roughly 2,500 feet - minus your stopping distance. Know your aircraft’s performance numbers, weight, and density altitude before accepting the clearance. Once you’ve stopped, it’s too late to rethink it.

Stop-and-go operations are not universally available. Busy towered airports often restrict them during peak traffic periods, and some prohibit them entirely based on traffic volume or runway length. Check the Chart Supplement (formerly the Airport/Facility Directory) before flying into an unfamiliar field expecting pattern work, and have a touch-and-go or full stop ready as a backup.

Land and Hold Short (LAHSO): The Clearance With the Sharpest Consequences

Land and hold short operations (LAHSO) require you to land and stop before a specific intersection - typically a crossing runway or taxiway. A full clearance sounds like: “N457NA, runway 28, cleared to land, hold short of runway 19.”

Your readback must include the hold short point. Not “cleared to land.” Not “wilco.” You repeat the runway and the intersection. On the other side of that line, there may be an aircraft rolling for takeoff on the crossing runway. The controller is sequencing two aircraft on intersecting paths, using a painted line as the separation standard. Your correct readback is the confirmation that you understand where that boundary is.

You are not required to accept a LAHSO clearance. The regulations are explicit on this. If you have any doubt about your ability to comply - a heavier landing weight, a wet runway, an unfamiliar aircraft, any factor that shifts your stopping distance - say “unable LAHSO.” The controller will build a different sequence. No clearance is worth accepting if you cannot confidently meet its conditions.

Before flying into airports where LAHSO is common, look up the available landing distance for the relevant intersection in the Chart Supplement. Compare it to your aircraft’s actual landing distance at your current weight and conditions. Do this on the ground, not on final.

LAHSO is also a VFR-only operation. Controllers do not issue LAHSO clearances in instrument meteorological conditions.

Low Approach: The Full Profile Without the Landing

A low approach authorizes flying the complete approach profile down to low altitude over the runway and then executing a go-around without landing. You fly over the pavement and climb away.

Low approaches appear in training when an instructor wants to evaluate the stabilized approach all the way through the flare sequence without committing to a touchdown. They also come up in instrument approach practice. From the controller’s perspective, a low approach functions like a landing that doesn’t happen - the runway is protected, traffic is held. When you start climbing away, expect a heading assignment or direct traffic pattern entry.

Short Approach: Not a Landing Clearance, But It Changes Your Path

A short approach instruction is not itself a landing clearance. When a controller says “make short approach,” they’re asking you to compress the pattern - shorten the downwind, turn base early, tighten final - to fit you into a gap in the sequence.

You’ll typically hear it paired with the clearance: “Make short approach, cleared to land, runway 24.” Both parts matter. The instruction changes your flight path. The clearance authorizes the landing.

If you cannot fly a short approach safely, say so before you start flying it. “Unable short approach, requesting full pattern” is a complete sentence that solves the problem. A controller who hears nothing and then watches an unstabilized approach develop is now problem-solving in real time - and so are you.

Why Your Readback Is the Last Line of Defense

Every landing clearance should be read back in full, every time. “Cleared to land, runway 36.” “Cleared to land, hold short of runway 19.” Not “roger.” Not “wilco.” The full clearance, repeated back, because the controller listening to that readback is the last check in the chain before you’re committed to the pavement.

The FAA Aeronautical Information Manual is explicit: readbacks are not optional for clearances. And they matter most precisely when workload is highest - which is exactly when pilots are most tempted to shorten them.

NASA’s Aviation Safety Reporting System has documented runway incursions that began with incomplete readbacks. A controller heard what they expected. A pilot read back something close but not exact. The mismatch didn’t surface until both aircraft were already in motion. The readback is the system working as designed.

If you don’t understand what you were cleared for, ask. “Say again” gets a repeat. “Unable” gets an alternative. Thirty seconds of clarification is cheaper than any outcome that follows an assumed clearance.

Key Takeaways

Cleared to land authorizes a full-stop landing only - nothing else. If you need a different operation, request it before you’re on final.
Cleared for the option provides five choices, but you must communicate your intent before crossing the threshold, not at it.
LAHSO clearances require a readback that includes the hold short point; you are never obligated to accept one if there is any doubt about your ability to comply.
Stop-and-go operations require you to calculate available runway distance before landing - once you’ve stopped, the decision is already made.
Read back every landing clearance in full, every time - especially when workload is high and the temptation to abbreviate is strongest.