Home / Library / Operational Procedures

Controlled Flight Into Terrain (CFIT)

Operational ProceduresCPL · IR · ATPL10 min readUpdated Sep 2026
Definition

Controlled flight into terrain (CFIT) is an in-flight collision, or near collision, with terrain, water or an obstacle by an airworthy aircraft that is under the control of its crew, with no indication of loss of control. The crew is usually unaware of the danger until it is too late.

Controlled flight into terrain (CFIT) is an accident in which an airworthy aircraft, fully under its crew's control, is flown into the ground, water or an obstacle. The crew usually realises the danger only seconds before impact, or not at all. Nothing is wrong with the aircraft or its handling; what fails is the crew's mental picture of where the aircraft is relative to the terrain.

For many years CFIT was one of the main killers in commercial aviation, and it drove the fitting of ground proximity warning systems. It remains among the deadliest accident types because few people survive it. IATA's analysis of 2008 to 2017 found CFIT in about 6% of accidents, yet it was the second-largest fatal accident category after loss of control in flight. About two-thirds of the CFIT accidents happened during approach and landing, and turboprops accounted for 70% of them, with an accident rate of 0.47 per million sectors against 0.05 for jets.

On this page
  1. What is CFIT
  2. Contributing factors and threats
  3. Minimum safe altitudes
  4. Approach-and-landing accidents (ALA)
  5. ALAR prevention strategies
  6. Terrain awareness and warnings
  7. Terrain escape manoeuvre
  8. Lessons from accidents
  9. Frequently asked questions

What is CFIT

The CAST/ICAO Common Taxonomy Team, whose categories ICAO, IATA and most investigators use, defines CFIT as an "in-flight collision or near collision with terrain, water, or obstacle without indication of loss of control". Three consequences follow:

The typical CFIT flight is descending or approaching in cloud or darkness near high ground. The crew is busy and confident of its position, and the aircraft is doing exactly what it has been told to do.

Contributing factors and threats

At the heart of almost every CFIT accident is lost situational awareness: the crew no longer knows, continuously, the aircraft's position, its height above the terrain around it, the minimum safe altitude for that position and where the flight path will take it next. The loss can be vertical, horizontal or both, and it usually builds from several small threats.

Threat How it leads to CFIT Main defences
Wrong altimeter setting or very low temperature The aircraft is lower than indicated Setting cross-checks, temperature corrections, radio altimeter callouts
Navigation or FMS entry error The aircraft is not where the crew believes Raw data cross-check, verify every FMS entry, terrain display
Premature descent Minimum altitude left before the fix Know each segment minimum, check altitude against distance
Misunderstood clearance or vectors Crew assumes ATC guarantees terrain clearance Readback, query any clearance below a known safe altitude
Automation mode error Wrong vertical mode or target selected Read the flight mode annunciator, cross-check and call out
Visual illusions, whiteout Visual descent below a safe path Use vertical guidance, keep to the procedure
Fatigue, time pressure, expectation Monitoring and challenge break down CRM, briefing, no-fault go-around policy
Missing or inhibited warnings No safety net when the rest has failed TAWS carriage, current databases, no unbriefed inhibits

Vertical errors usually come from altimetry: a QNH set wrongly, a QFE/QNH or hPa/inHg confusion, or cold-temperature error (see altimeter settings and the guide to cold-weather altimetry). Horizontal errors come from navigation: a wrong waypoint, a map shift, or a misread clearance. Night approaches over dark ground add the black-hole illusion, which makes the pilot feel higher than the aircraft is (see spatial disorientation and visual illusions).

Minimum safe altitudes

Charts publish several minimum altitudes, and each guarantees something different. Knowing which one applies at any moment is the basic CFIT defence. The minimum safe altitudes are:

Where no minimum altitude is published, the IFR minimum levels differ. EASA's SERA.5015 requires at least 1,000 ft above the highest obstacle within 8 km of the aircraft's estimated position, or 2,000 ft over high terrain or in mountainous areas. The FAA's 14 CFR 91.177 uses 1,000 ft, or 2,000 ft in designated mountainous areas, above the highest obstacle within 4 NM of the course. Under radar vectors ATC provides terrain clearance, but a clearance never relieves the pilot of responsibility for terrain avoidance.

Controlled Flight Into Terrain (CFIT): v1prep schematic.
Controlled Flight Into Terrain (CFIT): v1prep schematic.Illustration © v1prep

Approach-and-landing accidents (ALA)

An approach and landing accident (ALA) is one that occurs during the approach or landing. The category includes runway excursions, hard landings and loss of control on final as well as CFIT short of the runway, which is the deadliest variant. IATA's data put 51% of CFIT accidents in the approach phase alone.

Non-precision approaches carry much of this risk. The traditional "dive and drive" technique descends promptly to each step-down altitude and then flies level at the minimum descent altitude (MDA), looking for the runway. That keeps the aircraft low for longer, adds thrust and attitude changes, and tempts the crew below the MDA to find the lights.

The alternative is the continuous descent final approach (CDFA): the final segment of a non-precision approach flown as a continuous descent, without level-off, from at or above the final approach fix altitude to about 50 ft above the threshold or the flare point. The go-around starts at a decision altitude chosen so that the aircraft does not descend below the MDA. EASA's Air Ops rules require commercial operators to fly non-precision approaches with CDFA unless the competent authority approves another technique for a particular runway. The FAA promotes the same technique through AC 120-108. Approaches with vertical guidance, such as LNAV/VNAV and LPV (RNP approaches), remove the problem at source; in 2010 ICAO Assembly Resolution A37-11 urged States to provide them for all instrument runway ends.

The companion defence is the stabilised approach. The Flight Safety Foundation's criteria require the aircraft to be stabilised by 1,000 ft above aerodrome elevation in IMC and 500 ft in VMC. That means on the correct lateral and vertical path, in landing configuration, at a speed between VREF and VREF + 20 kt, with a sink rate of no more than 1,000 ft/min and suitable thrust. On an ILS the aircraft must be within one dot of the localiser and glide slope. An approach that is not stabilised at the gate, or becomes unstabilised below it, requires an immediate go-around.

ALAR prevention strategies

In the late 1990s the Flight Safety Foundation led an international task force on approach-and-landing accident reduction (ALAR), which studied ALAs and CFIT accidents and published conclusions and recommendations. Its ALAR Tool Kit turned them into briefing notes, videos and presentations for airlines, training organisations, air traffic services and regulators. The main themes are:

The Foundation also published a CFIT checklist, a scoring sheet with which an operator or crew can assess the terrain risk of a flight before it happens. Much of the Tool Kit comes down to crew resource management: the pilot monitoring must be willing and expected to challenge a descent that does not match the chart.

Terrain awareness and warnings

When every other defence has failed, warning systems give the last chance. A ground proximity warning system reacts to radio altitude, descent rate and configuration. A terrain awareness and warning system (TAWS) such as EGPWS adds a terrain and obstacle database that looks ahead of the aircraft, typically giving a caution 40 to 60 seconds before a potential impact and a warning 20 to 30 seconds before. Their modes, displays and carriage rules are described in GPWS and TAWS.

Three rules matter for CFIT. The terrain display is for awareness, not navigation. A database is only as good as its coverage and the aircraft's position accuracy. And a warning is never inhibited on the assumption that it is false.

The forested volcano Mount Salak in West Java, Indonesia.
Mount Salak, south of Jakarta. In 2012 a Sukhoi Superjet 100 demonstration flight struck it after the crew had inhibited valid terrain warnings.Vitaium · CC BY-SA 4.0 · Wikimedia Commons

On the ground, radar systems with a minimum safe altitude warning (MSAW) alert the controller when an aircraft is, or is predicted to be, below a safe altitude. FAA controllers then transmit "low altitude alert, check your altitude immediately". Crews should treat such a call as they would a terrain warning.

Terrain escape manoeuvre

The terrain avoidance manoeuvre, also called the terrain escape manoeuvre or pull-up manoeuvre, is the maximum-performance climb flown after a PULL UP warning, or after a caution at night or in IMC where the operator requires it. It is flown immediately, from memory, without first diagnosing the alert:

  1. Disconnect the autopilot and autothrottle as the type procedure requires.
  2. Apply maximum or take-off/go-around thrust.
  3. Roll wings level, since bank reduces the climb gradient, and pitch up firmly to the attitude the type specifies (on Boeing types typically 20° initially, then towards the pitch limit indicator or stick shaker; on Airbus fly-by-wire types full back stick).
  4. Retract the speedbrakes and do not change the gear or flap configuration until terrain clearance is assured.
  5. Climb until the warning stops and the aircraft is above the minimum safe altitude, then tell ATC.

The detail is type-specific and practised in the simulator. American Airlines Flight 965 near Cali showed why it matters: the crew began the escape, but the speedbrakes remained extended and cost climb performance.

Exam tip: the immediate response to a GPWS or TAWS warning is to level the wings and climb at maximum gradient. The warning is not a prompt to analyse, and a caution becomes a warning if the flight path does not change.

Lessons from accidents

Accident What happened Lesson
Air New Zealand 901, DC-10, Mount Erebus, 1979 On an Antarctic sightseeing flight the crew descended below cloud to fly visually. The programmed track had been changed without their knowledge and led over Mount Erebus, which merged into the overcast. Verify navigation data; poor visual contrast can hide terrain in apparently clear air.
Air Inter 148, A320, Mont Sainte-Odile, 1992 On a night approach to Strasbourg the aircraft descended at about 3,300 ft/min. The investigators' leading explanation was that this vertical speed had been selected when a 3.3° flight path angle was intended. No GPWS was fitted. Read the flight mode annunciator; fit terrain warning systems.
American 965, B757, near Cali, 1995 Rushed after accepting a straight-in approach, the crew entered a waypoint that the FMS resolved to a beacon near Bogotá. The aircraft turned towards high ground while still descending. Cross-check FMS entries with charts and raw data; refuse a rushed approach.
Korean Air 801, B747, Guam, 1997 At night, with the glide slope out of service, the captain descended below the step-down altitudes of the localiser approach. Fatigue and poor monitoring contributed, and the approach radar's MSAW had been inhibited. Fly step-down or CDFA profiles precisely; challenge deviations; keep ground safety nets working.
Sukhoi Superjet 100, Mount Salak, 2012 On a demonstration flight the crew descended in cloud near a volcano while distracted. They took the TAWS warnings for a database fault and inhibited them. Never inhibit a warning without positive proof that it is false.
The snow-covered volcano Mount Erebus on Ross Island, Antarctica.
Mount Erebus, Antarctica. In 1979 an Air New Zealand DC-10 on a sightseeing flight struck its lower slopes after its programmed track had been changed without the crew's knowledge.owamux · CC BY 2.0 · Wikimedia Commons

Each accident combined several of the threats above, and in each a single barrier, a cross-check, a challenge, a stabilised profile or a respected warning, would have broken the chain.

Frequently asked questions

What is controlled flight into terrain (CFIT)?

CFIT is an accident or serious incident in which a serviceable aircraft, under the full control of its crew, is flown into terrain, water or an obstacle, or only just avoids it. Nothing is wrong with the aircraft; the crew has lost awareness of where it is relative to the ground, usually at night, in cloud or on approach. It remains one of the deadliest accident categories because few occupants survive.

How is CFIT different from loss of control in flight?

In CFIT the aircraft is flying normally and doing what the crew or autopilot commands, but the flight path meets the ground. In loss of control in flight (LOC-I) the crew can no longer control the aircraft, for example after a stall or an upset, and the impact follows from that. An accident is classed as CFIT only when there is no indication of loss of control.

What should a pilot do after a terrain PULL UP warning?

Fly the terrain escape manoeuvre at once, without first trying to confirm the warning. Disconnect the autopilot, apply maximum or take-off/go-around thrust, roll wings level, pitch up to the attitude the aircraft type specifies, retract the speedbrakes and leave the gear and flaps alone. Keep climbing until the warning stops and the aircraft is above the minimum safe altitude, then tell ATC.

What is the Flight Safety Foundation ALAR Tool Kit?

It is a set of briefing notes, videos and presentations produced by the Flight Safety Foundation from the work of its international Approach-and-Landing Accident Reduction task force, which studied approach-and-landing and CFIT accidents in the late 1990s. It covers standard operating procedures, stabilised approaches, go-around decisions, constant-angle non-precision approaches, altimetry, pilot-controller communication and the terrain avoidance manoeuvre.

What is the difference between MSA, MORA and MEA?

The minimum sector altitude on an approach chart gives 1,000 ft of obstacle clearance within 25 NM of a navaid or fix but no guarantee of navigation signal. A minimum en-route altitude guarantees both obstacle clearance and navigation signal along an airway segment. A MORA, a Jeppesen figure, clears terrain by 1,000 ft, or 2,000 ft where it exceeds 5,000 ft, around a route or within a grid square, with no signal guarantee.

Why are non-precision approaches flown with the CDFA technique?

Stepping down to each minimum altitude and then flying level at the minimum descent altitude keeps the aircraft low for longer, adds thrust and attitude changes and makes the visual transition harder, a pattern repeatedly found in CFIT accidents. Flying a continuous descent on a constant angle, like an ILS, gives a stable approach with a clear decision point. EASA requires it for commercial non-precision approaches unless the authority approves otherwise.

Test yourself on Controlled Flight Into Terrain (CFIT)

The v1prep banks cover this topic in Operational Procedures (070), with a worked explanation for every answer. EASA ATPL, PPL, IR and CPL, the FAA written tests and A320/B737 type ratings.

Start practising →
16,000+ questions · EASA & FAA · Free to start

Sources and further reading

  1. CAST/ICAO Common Taxonomy Team, Aviation Occurrence Categories, Definitions and Usage Notes
  2. IATA, Controlled Flight Into Terrain Accident Analysis Report, 2008-2017 Data
  3. IATA, Controlled Flight Into Terrain (CFIT) safety programme
  4. Flight Safety Foundation, Controlled Flight Into Terrain (CFIT)
  5. FAA Lessons Learned, American Airlines Flight 965, Boeing 757-223 N651AA
  6. NTSB AAR-00/01, Korean Air Flight 801, Boeing 747-300, Nimitz Hill, Guam
  7. 14 CFR 91.177, Minimum altitudes for IFR operations

Library articles are written for study and exam preparation. They do not replace your aircraft's approved documentation, your operator's procedures or the regulations themselves.