ARTICLES
The stabilised approach: the criteria, and how to check them flight after flight
A good approach is decided before the flare. At a height set in advance, the aircraft is on its path, on speed, configured, with a reasonable rate of descent; if not, you go around. The recognised criteria, why they matter, and how to read them back after every flight from the aircraft's log.
Where the criteria come from
The most quoted criteria come from the Flight Safety Foundation (FSF) task force on approach-and-landing accident reduction, known as ALAR. Its Briefing Note 7.1, “Stabilized Approach”, published in 2000, gives a simple definition: an approach is stabilised only if all the criteria of the operator's procedures are met before or when reaching the minimum stabilisation height.
The task force found that unstabilised approaches, flown low and slow or high and fast, were a causal factor in 66% of the 76 approach-and-landing accidents and serious incidents it studied, which occurred worldwide from 1984 to 1997. The note is written first for airline crews: it speaks of the pilot flying and the pilot not flying, of flight management systems. Its principles hold for a club aircraft all the same.
EASA carries the principle over to general aviation, on its page about loss of control in approach and landing: a stabilised approach follows a constant-angle path towards a reference landing point; the aircraft is configured early, so that only small corrections of pitch, heading and power are needed; and if the approach is not stabilised, you go around.
The Flight Safety Foundation criteria
The FSF sets two minimum stabilisation heights: 1,000 ft above the airport in instrument meteorological conditions (IMC), 500 ft in visual meteorological conditions (VMC). At that height, all of the following must be true:
- the aircraft is on the correct flight path;
- only small changes of heading and pitch are needed to stay on it;
- the indicated airspeed is no more than VREF + 20 kt and no less than VREF;
- the aircraft is in the landing configuration;
- the sink rate is no greater than 1,000 ft/min; an approach that needs more calls for a special briefing;
- the power setting suits the configuration and is not below the minimum set by the aircraft operating manual;
- all briefings and checklists have been completed;
- on an ILS approach, the aircraft stays within one dot of the localizer and the glideslope; on a circling approach, the wings are level on final by 300 ft above the airport;
- an unusual procedure or an abnormal situation that requires a departure from these criteria calls for a special briefing.
And the rule that gives the list its meaning: an approach that is not stabilised at the minimum stabilisation height, or that becomes unstabilised below it, requires an immediate go-around.
Why it matters, even in the circuit
The FSF note describes the two ways an approach goes wrong. In the accidents studied, the low and slow approaches led to losses of control and, most often, to collisions with terrain; the high and fast ones, to losses of control, overruns and runway excursions. Among the deviations it lists: a whole approach flown at idle because the aircraft arrived too high or too fast, a threshold crossed more than 50 ft high, an extended flare and a long touchdown.
Setting the stabilisation height before the approach mostly changes the decision. At 500 ft the question is no longer “will it work out?” but “are the criteria met?”. The go-around becomes a planned manoeuvre, not an admission of failure. EASA puts it plainly: there is no shame in going around. It also advises carrying enough fuel for a go-around and practising it, as it is a critical phase of the flight.
What the flight log can show
Many club aircraft already record every flight. A Garmin G1000, for instance, writes a file at each power-up in the data_log folder of the SD card in its multifunction display. Engine monitors, other avionics and navigation apps also leave logs or GPS tracks. After the flight, the approach can be read back from them.
Heights are the difficulty: a light aircraft has no radio altimeter. The height above the airfield is worked out from the altitude recorded, minus the altitude of the airfield read in the same log while the aircraft rolls on it. Both come from the same source, so a wrong altimeter setting cancels out.
| Criterion | What the log shows |
|---|---|
| Flight path | The track on the map; on a guided approach, the course and glidepath deviations if the avionics records them. |
| Airspeed | The indicated airspeed between the stabilisation height and the threshold. A plain GPS track gives only the ground speed, which the wind distorts. |
| Sink rate | The vertical speed recorded, or the one worked out from the altitude. |
| Bank | The roll angle, when the log holds the attitude. |
| Configuration, power, checklists | Rarely: the flap position and the checklists are not in most logs; the engine speed sometimes is. |
| Touchdown | The sink rate and the load factor at the touchdown; the touchdown point from the threshold, if the runway's position is known. |
The method takes three steps. Choose your stabilisation height: 500 ft above the airfield in VFR, or your school's. Between that height and the threshold, note the highest sink rate, the spread between the highest and the lowest airspeed, and the steepest bank on short final. Compare them with your limits, then look at the touchdown: where you aimed, with no marked load factor?
Flight after flight: look for the trend
One approach says little. Ten approaches on the same runway tell a habit: an airspeed always a little high on final, a sink rate that climbs below 300 ft, touchdowns further and further down the runway. Follow the share of stabilised approaches month after month, and the criterion that fails most often: that is the one to work on with your instructor.
A go-around after an unstabilised approach never counts as a failure: it is exactly what the criteria ask for. To learn from it, replay the flight with your instructor; how to run that debrief is the subject of our article Debriefing a flight with your instructor.
Sources
- FSF ALAR Briefing Note 7.1 — Stabilized Approach Flight Safety Foundation, Approach-and-landing Accident Reduction Tool Kit (Flight Safety Digest, August–November 2000)
- Loss of Control (LOC-I) in Approach and Landing EASA, general aviation safety pages
Texts read on the date of the article. For regulations, only the official version is authentic.