FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15FA046 · Cessna 172 S

8 Nov 2014 · Hinton, VA, United States

Fredrick Flight Center Cessna 172 S · Accident: controlled flight into terrain/object (CFIT) en route

From Winchester Regional Airport (OKV) to Ingalls Field (HSP)

Report a problem

Event

NTSB case
ERA15FA046
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 172 S

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N2152T
Onboard fatalities
Unknown
Route
From Winchester Regional Airport (OKV), Winchester, VATo Ingalls Field (HSP), Hot Springs, VA
Aircraft age
About 11 years (built 2003)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Controlled flight into terrain/object (CFIT)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The student pilot had planned the instructional cross-country flight from his home base airport to another airport about 100 miles away with an intermediate stop to practice landings. However, just before departure, the flight instructor changed the destination to a different airport that was located further away and in mountainous terrain; however, he did not provide the student pilot time to plan the new flight route. No flight plan was filed nor was there any record of flight following for the accident flight. After conducting several landings at the intermediate airport, the flight proceeded toward the destination; the sun had set at this time. The instructor told the student to fly a heading of 240 degrees at 3,000 ft mean sea level (msl). The student asked the instructor about terrain elevation in the area, and the instructor responded that he was not certain of the elevations because the airplane was not equipped with a G-1000 navigation system. The student pilot reported that there were no aeronautical charts readily accessible while in flight to reference terrain elevation, and no aeronautical charts associated with the accident area were found in the accident airplane during postaccident examination. The aeronautical chart for the area showed a maximum elevation of 5,100 ft, and a mountain near the accident location with an elevation of 3,700 ft.

The instructor then began to demonstrate the autopilot to the student, including various climb rates. The student stated that the airspeed began to decline and he asked the instructor if he should add power, which the instructor did. The student reported that the engine was operating normally and responded to power inputs. However, shortly thereafter, the airplane impacted a mountain at an elevation of about 3,100 feet msl, which was about 300 feet below the mountain peak. Ground scar and wreckage information indicated that the airplane impacted the terrain in a wings-level attitude on a near horizontal flight path.

Postaccident examination of the airframe and engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Given the lack of onboard navigation charts for the area, the dark night conditions, and the instructor's decision to change the destination and not conduct preflight planning for that leg of the flight, the pilots were likely not aware of the altitude of the surrounding terrain, which resulted in controlled flight into rising terrain.

Probable cause

The flight instructor’s decision to conduct a night training flight in mountainous terrain without conducting or allowing the student to conduct appropriate preflight planning and his lack of situational awareness of the surrounding terrain altitude, which resulted in controlled flight into terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15FA046
Event ID
20141109X22459
Case number
ERA15FA046
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 4c41a0accf0ebe33d19e8e450a6e2fe9ba0a008b70c9bf8337b42a51e1ac94cf; retrieved 2026-09-14T17:28:34.217Z.