Learn what a straight-in approach is, how to plan the 3° descent, join final, stabilise, manage traffic and decide when to go around.
To fly a straight-in approach, join the extended runway centreline early, intercept the intended glidepath from below, slow and configure in stages, then stabilise on target speed with only small corrections. Confirm the runway, wind, traffic and clearance, and go around if alignment, descent, speed or landing clearance is not assured.
In Aviation & Real-World Flying, straight-in describes the route onto final approach. It does not remove any requirement to follow ATC instructions, published procedures, circuit rules, terrain limits, weather minima or right-of-way rules.
What is a straight-in approach?
A straight-in approach places the aircraft on the runway's extended centreline without first flying the usual downwind and base legs immediately before landing.
| Term | What it means | What it does not mean |
|---|---|---|
| Visual straight-in approach | The pilot visually joins final and follows a suitable path to the runway. | It does not confer priority over established circuit traffic. |
| Instrument straight-in approach | The aircraft follows published or assigned routing to an instrument final that supports a direct landing. | The earlier parts of the procedure may still contain turns, vectors or altitude restrictions. |
| Straight-in landing | The aircraft lands from the final approach instead of circling to another runway. | An approach clearance is not necessarily a landing clearance. |
| Straight descent | A descent without a level segment, often called a continuous descent. | It is not a synonym for straight-in; the aircraft can level, turn or decelerate before final. |
Casual phrases such as “straight approach” and “straight-in landing” usually refer to the same basic geometry, but instrument terminology has more specific procedural meanings. When flying IFR, the chart and clearance determine what is authorised; our instrument-approach procedure guide explains how to brief and fly that sequence.
How do you set up and fly a straight-in final?
A good straight-in final starts far enough from the runway to settle alignment, speed, configuration and descent before the stabilisation gate.
- Confirm the runway and arrival. Check wind, runway length and surface, threshold elevation, obstacles, traffic and local joining restrictions. At a controlled aerodrome, distinguish between an approach clearance and a landing clearance.
- Identify the correct runway. Cross-check its designation, position, approach lights, markings and navigation indications. Runway numbers are rounded magnetic designators, so multiplying the painted number by ten does not always produce the exact final course; parallel runways demand an additional left, centre or right check.
- Join the extended centreline. Use a shallow intercept rather than turning aggressively close to the runway. Allow for wind so that the aircraft's ground track, not merely its heading, remains aligned with final.
- Intercept the glidepath from below. Use the published vertical path, PAPI, VASI or a planned visual profile. On a standard four-light PAPI, two white and two red lights indicate the nominal path; more white means high and more red means low.
- Manage energy before adding drag. Reduce speed early and extend gear and flaps in the approved sequence and within their limits. Full flap and a steep dive are not a sound cure for arriving high and fast.
- Set an initial descent rate. On a 3° path, groundspeed multiplied by five gives a useful rough vertical speed in feet per minute. At 90 knots start near 450 feet per minute; at 120 knots, near 600. The more exact multiplier is about 5.3, and wind changes groundspeed even when indicated airspeed remains constant.
- Hold the path and aiming point. Make small, coordinated pitch and power changes using the technique specified for the aircraft. After each change has settled, the intended aiming point should remain almost stationary in the windscreen; movement upwards suggests an undershoot trend, while movement downwards suggests an overshoot.
- Make a positive landing decision. Continue only if the runway is correct and available, required visual references are present, and the aircraft can land in the intended touchdown area without excessive correction. Otherwise, go around.
For more detail on sight picture, PAPI interpretation and centreline control, use our practical visual-final technique.
Why does a 3° glidepath descend about 318 feet per nautical mile?
A geometric 3° slope changes height by approximately 318 feet per nautical mile: one nautical mile is about 6,076 feet, and tan(3°) × 6,076 is roughly 318. The familiar 300-feet-per-mile or three-miles-per-1,000-feet rule is deliberately approximate.
At five nautical miles from the threshold, an exact 3° line is about 1,590 feet above threshold level, before adding any applicable threshold-crossing height. To convert that into an indicated altitude, add the runway threshold elevation. Do not assume a displayed GPS or DME distance is measured from the threshold; it may reference a navaid, waypoint or airport reference point.
A published approach can use a slope other than 3°, so its charted altitudes take precedence over mental arithmetic. If the problem begins before final, our guide to choosing the descent point for landing shows how to avoid reaching the runway high and fast.
How far out should you join a straight-in approach?
Join far enough out to be stable by the required gate, but not so far away that an unnecessarily long final obstructs or confuses established traffic.
Work backwards from the runway. Allow roughly three nautical miles for each 1,000 feet that must be lost on a normal path, then add distance for deceleration, configuration, checklists and centreline interception. A tailwind increases groundspeed and therefore the descent rate and ground distance needed for the same time-based configuration sequence.
A light training aircraft may be comfortable with several miles of final; a fast or heavy aircraft normally needs more room. There is no universal joining distance. Aircraft performance, starting altitude, wind, flap and gear limits, terrain, ATC sequencing and local circuit procedures all matter.
Does straight-in mean flying straight for the whole descent?
No. “Straight-in” describes the arrival onto final, not an obligation to hold one heading or make one uninterrupted straight descent.
Wind requires heading corrections, and ATC vectors or a published procedure may include turns before final. The aircraft may also fly level while slowing or waiting to intercept the glidepath. Once established, the aim is a steady final ground track and normal descent rather than constant control movement.
In a crosswind, the nose may point away from the runway centreline while the aircraft tracks directly towards it. Use the aircraft's recommended crab or wing-low technique and complete the transition for touchdown at the appropriate point.
When is a straight-in approach stable?
A straight-in approach is stable when the aircraft is on the intended lateral and vertical path, near target speed, in landing configuration and requiring only small corrections.
- The runway and final course are positively identified.
- Landing gear, flaps and required checklists are complete at the planned point.
- Airspeed is within the aircraft or operator's permitted range, including any approved wind additive.
- Power, attitude and descent rate are appropriate and not changing rapidly.
- Centreline and glidepath deviations are small and being corrected smoothly.
- The intended touchdown area is reachable without steep manoeuvring, excessive sink or prolonged floating.
- Traffic separation, runway availability and required visual references are assured.
Many operators use gates near 1,000 feet above aerodrome level in instrument conditions and 500 feet in visual conditions, but these are not universal legal limits. Follow the aircraft manual, operator policy, instructor's standard and local regulations applicable to the flight.
If the approach is not stable by the applicable gate—or becomes unstable below it—execute the correct go-around or published missed-approach procedure. Do not use the remaining runway to repair a poor final.
Should you fly straight in at a non-towered aerodrome?
A straight-in arrival at a non-towered aerodrome is suitable only when local rules permit it and the aircraft can integrate safely with existing circuit traffic.
Listen early, make any required position reports and scan for aircraft that may not be transmitting. Radio calls do not create separation, and a pilot on downwind or base may have difficulty seeing an aircraft approaching head-on against the background. A long final does not automatically confer priority.
If the traffic picture or spacing is uncertain, discontinue the straight-in join early and use the published circuit entry. Procedures differ by country and aerodrome, and some locations restrict or discourage straight-in arrivals.
How do you practise a straight-in landing in a flight simulator?
For a first flight-simulator or FS exercise, use a familiar light aircraft, daylight, good visibility and little wind so that path control is the only problem being trained.
- Position about five nautical miles from the threshold on the extended centreline, around 1,600 feet above threshold elevation for a 3° path.
- Remember that the altimeter normally displays altitude above mean sea level, not height above the runway. Add airport elevation to the planned height.
- Begin the first repetition at a sensible approach speed and configuration. On the next attempt, start farther out and practise slowing, selecting flaps and completing the landing checks.
- Use the PAPI or VASI as the primary visual path reference and vertical speed only as an initial estimate.
- Add crosswind, traffic, lower visibility and instrument guidance one variable at a time.
Built-in simulator ATC and AI traffic can behave differently between platforms and add-ons. Treat charted procedures and sound airmanship as the standard rather than assuming every generated vector or clearance is operationally sensible.
Common straight-in approach mistakes and fixes
- Arriving high and fast: slow earlier, extend the final if permitted, reposition or go around. Do not force the aircraft down with an excessive descent rate.
- Using airport elevation incorrectly: calculate the target indicated altitude by adding height above threshold to threshold elevation.
- Measuring distance from the wrong point: verify whether GPS or DME distance refers to the threshold, a waypoint, a navaid or the airport reference point.
- Chasing vertical speed: use glidepath position as the primary reference. Recalculate the expected rate when groundspeed changes.
- Chasing the PAPI: make one measured correction and allow time to see its effect rather than alternating between steep and shallow flight.
- Selecting the wrong runway: cross-check heading, markings, lighting and navigation indications, particularly at airports with parallel runways.
- Joining without a traffic picture: monitor the appropriate frequency and visually scan the entire circuit before committing to final.
- Configuring too late: choose gear, flap and checklist points before the approach rather than improvising below the stabilisation gate.
- Continuing an unstable final: go around for excessive speed, sink, misalignment, an occupied runway, lost visual reference or any unresolved doubt about a safe landing.