Controlled Flight Into Terrain (CFIT)

The defining feature of Controlled Flight Into Terrain is that nothing is wrong with the aircraft. It is airworthy, its systems are functioning, and the crew is flying it — but their mental picture of where the aircraft is relative to the ground has diverged from reality, and they fly a serviceable aeroplane into the surface. The CAST/ICAO Common Taxonomy Team (CICTT) defines CFIT as in-flight collision or near-collision with terrain, water, or an obstacle without indication of loss of control. CFIT is one of the five Global High-Risk Categories of Occurrence named in the ICAO Global Aviation Safety Plan, alongside Loss of Control In-Flight (LOC-I), Mid-Air Collision, Runway Excursion, and Runway Incursion.

The distinction from LOC-I is fundamental and is the reason the two categories are counted separately. In LOC-I the aircraft has departed controlled flight — it is outside the envelope and the crew can no longer command its trajectory. In CFIT the aircraft is under complete control the entire time; the failure is one of situational awareness and terrain awareness, not of aircraft control. It is equally important to distinguish CFIT from an uncontrolled collision with terrain, in which the aircraft strikes the ground because control had already been lost — that would be classified under LOC-I. The word 'controlled' in CFIT is doing precise work: it means the crew was flying the aircraft, deliberately, right up to the moment of impact.

CFIT concentrates in predictable scenarios. Non-precision approaches, where the vertical path is not protected by an electronic glideslope, are a classic setting — particularly when flown as a series of step-downs (the 'dive and drive' technique) rather than a continuous descent, allowing the aircraft to level off at an intermediate altitude close to terrain. Night operations and instrument meteorological conditions remove the external visual cues a pilot would otherwise use to notice rising ground. Descent below the minimum descent altitude or decision altitude without the required visual reference, loss of positional awareness during a circling approach or in mountainous terrain, and pressure to complete the approach all recur in the accident record. Spatial disorientation and the absence of a clear horizon frequently accompany these events.

Two interventions have driven the large historical reduction in CFIT. The first is terrain-awareness equipment: the Ground Proximity Warning System (GPWS) and its successor the Terrain Awareness and Warning System (TAWS), which uses a terrain database and GPS position to give predictive alerts and a 'pull up' warning ahead of terrain the aircraft is closing on. Mandates for TAWS on turbine aircraft transformed the CFIT statistics for equipped fleets. The second is procedural: flying approaches as a stabilized, Continuous Descent Final Approach (CDFA) with defined stabilized-approach criteria and a firm commitment to go around if those criteria are not met by a specified gate. The Flight Safety Foundation's Approach and Landing Accident Reduction (ALAR) work, and its associated toolkit, was built substantially around defeating CFIT and unstable-approach accidents. Together, terrain-awareness technology and disciplined approach procedures address CFIT from both the equipment and the human-factors sides.

Flight schools sit at both ends of the CFIT problem. Their aircraft — piston singles and light twins used for training — are often the least likely to carry certified TAWS, and their students are, by definition, building the terrain-awareness and approach discipline that prevents CFIT. Cross-country training at night, early instrument-approach practice, and any operation in or near high terrain are precisely the conditions in which CFIT precursors appear. A school that teaches continuous-descent, stabilized approaches from the beginning, and that makes going around a normal, expected outcome rather than a mark of failure, is directly building the habits that keep its graduates out of the CFIT statistics.

There is a fleet and dispatch dimension as well. Whether a given training aircraft carries functioning terrain awareness, whether its databases are current, and whether the aircraft is dispatched into night or marginal-weather cross-countries appropriate to the student's experience are all operational decisions a school makes daily. Capturing terrain-awareness alerts, descents below minima, and unstable approaches as reported occurrences — rather than treating them as unremarkable training events — is what lets a Head of Training see CFIT risk accumulating and address it before it becomes an accident.

Aviatize's Safety Management module lets a school log CFIT precursors — a TAWS or terrain alert, a descent below minimums, an unstable approach continued past the gate — as structured occurrence reports that feed a hazard log and risk register instead of disappearing into a debrief that leaves no trace. Patterns across those reports appear in KPI Reporting & Dashboards, so recurring problems on a particular approach, airfield, or time of day become visible rather than anecdotal.

On the training side, the Training Management module tracks instrument-approach, night cross-country, and stabilized-approach exercises as syllabus items with instructor sign-off, so the approach discipline that prevents CFIT is demonstrably taught and recorded. Where terrain-awareness equipment and database currency matter, Maintenance Control keeps the aircraft's status and any avionics database updates visible against the fleet, so dispatch decisions rest on the aircraft's real configuration.