OpenAirDocs.org

20141108020249A

Accident · Destroyed
Open the Markdown

FAA accident report · Cessna 172S · Hinton, VA · November 8, 2014

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
November 8, 2014 · 19:30 local
Place
Hinton, VA
Phase of flight
Cruise/Level Flight
Operating rules
General operating rules (Part 91)
Damage
Destroyed
Aircraft
N2152T
NTSB investigation
NTSBERA15FA046
Reported as
Cessna 172S
Reported engine
Lycoming IO-360-L2A
People aboard
2
Fatal injuries
1
Other injuries
1
Pilot’s certificates
Airline transport, flight instructor, unknown or foreign certificate
Pilot’s flight hours
5,938 total56 in the last 90 days
N2152TRegistration cancelled Mar 21, 2018 · Cessna 172SS/N 172S9446 · Built 2003Airframe modelCessna 172SEngine modelLycoming IO-360-L2AReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

Conducted face-to-face interview with surviving student pilot who stated the cause as controlled flight into terrain during a night VFR training flight.

Outcome: CFI fatally injured, student pilot air-evacuated with non-life threatening injuries.

CFI assigned a night cross-country route, okv - hsp, to the student without conducting any prior flight planning for route, altitude, etc.

CFI assigned heading based on GPS direct-to information and assigned the student an altitude of 3,000 ft MSL.

CFI was demonstrating operation of the aircraft autopilot in the moments just prior to impact. CFI had programmed a 500 ft/min climb without adding power. Student expressed concern about lack of airspeed so CFI applied maximum power just as the aircraft impacted terrain associated with a 3,700 ft MSL peak.

Student pilot stated that the aircraft performed normally and was not a factor.

No flight plan filed

No use of radar services / VFR flight following

CFI did not have an aeronautical chart out during the flight. Chart was in his flight bag.

No violation filed, PIC deceased.

As the FAA filed it

CONDUCTED FACE-TO-FACE INTERVIEW WITH SURVIVING STUDENT PILOT WHO STATED THE CAUSE AS CONTROLLED FLIGHT INTO TERRAIN DURING A NIGHT VFR TRAINING FLIGHT.

OUTCOME: CFI FATALLY INJURED, STUDENT PILOT AIR-EVACUATED WITH NON-LIFE THREATENING INJURIES.

CFI ASSIGNED A NIGHT CROSS-COUNTRY ROUTE, OKV - HSP, TO THE STUDENT WITHOUT CONDUCTING ANY PRIOR FLIGHT PLANNING FOR ROUTE, ALTITUDE, ETC.

CFI ASSIGNED HEADING BASED ON GPS DIRECT-TO INFORMATION AND ASSIGNED THE STUDENT AN ALTITUDE OF 3,000 FT MSL.

CFI WAS DEMONSTRATING OPERATION OF THE AIRCRAFT AUTOPILOT IN THE MOMENTS JUST PRIOR TO IMPACT. CFI HAD PROGRAMMED A 500 FT/MIN CLIMB WITHOUT ADDING POWER. STUDENT EXPRESSED CONCERN ABOUT LACK OF AIRSPEED SO CFI APPLIED MAXIMUM POWER JUST AS THE AIRCRAFT IMPACTED TERRAIN ASSOCIATED WITH A 3,700 FT MSL PEAK.

STUDENT PILOT STATED THAT THE AIRCRAFT PERFORMED NORMALLY AND WAS NOT A FACTOR.

NO FLIGHT PLAN FILED

NO USE OF RADAR SERVICES / VFR FLIGHT FOLLOWING

CFI DID NOT HAVE AN AERONAUTICAL CHART OUT DURING THE FLIGHT. CHART WAS IN HIS FLIGHT BAG.

NO VIOLATION FILED, PIC DECEASED.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

NTSB ERA15FA046Accident · 1 fatalField investigationFinal reportHinton, VAThe 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…Nov 8, 2014 · Substantial damage

Other reports on N2152T · 1

Matched to the same aircraft by N-number and date.

Incident 20111024024309ITaxi · Frederick, MDPilot landed at fdk on rwy 05 without incident. He proceeded on taxiway bravo making a left turn off the taxiway and onto the grass. When he realized he had taxiied onto the grass he attempted to return to the hard surface and in the process went through a…Oct 24, 2011 · Minor damage