FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13LA281 · Cessna 172K

12 Jun 2013 · Newton, MS, United States

Newton Flying Club Cessna 172K · Accident: controlled flight into terrain/object (CFIT) on approach

From James H Easom Field (M23) to James H Easom Field (M23)

Report a problem

Event

NTSB case
ERA13LA281
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 172K

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
N7045G
Onboard fatalities
Unknown
Route
From James H Easom Field (M23), Newton, MSTo James H Easom Field (M23), Newton, MS
Aircraft age
About 44 years (built 1969)
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
Approach · VFR pattern final
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)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Psychological

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

NTSB narrative

After an uneventful instructional flight, the student pilot entered the left downwind leg of the traffic pattern while the airplane was at 1,200 ft mean sea level. The flight instructor then asked the student to turn onto the base leg of the traffic pattern, but "he was slow to respond," and the airplane was too fast, which extended the downwind leg farther out than normal. The flight instructor then noticed that the student had not extended the wing flaps to the 10-degree position. The student pilot then extended the wing flaps to 10 degrees and started to slow the airplane. The flight instructor then asked the student to turn onto final, and, because of the extended downwind leg, to stop descending and add power. The student then arrested the descent, but he failed to add power as instructed. The flight instructor again asked the student to add power; however, the student did not respond by either adding power or by asking the flight instructor for clarification. The flight instructor stated that he was distracted by the airplane's airspeed and altitude and the student's lack of response and that he did not see the power lines during the final approach even though he had flown over them many times. When he finally did see the power lines, he took control of the airplane and then added full power and maximum up elevator. However, the airplane struck a static wire that ran along the top of the power poles, nosed over, and impacted terrain.

Review of Federal Aviation Administration records revealed that the student pilot held a third-class medical certificate with the limitation that he "must use hearing amplification." However, the student pilot was not wearing a hearing aid during the accident flight; therefore, he might not have heard the flight instructor's command to increase engine power, which would explain his failure to do so as instructed. Further, neither the student pilot nor the flight instructor were wearing headsets in the loud cockpit of the single-engine airplane, which also could have made it difficult for the student pilot to hear the flight instructor's command.

Although the power lines were not included in the airport information in the Airport/Facility Directory, they were depicted in the sectional aeronautical chart for the area. Examination of the power lines revealed that not only were they below the runway's 7.00-degree glidepath that was provided by a pulsating visual approach slope indicator to ensure obstacle clearance but that they were also below the obstruction identification surfaces listed in federal regulations, and, in many areas, they were at or below the trees located on the approach end of the runway. Given this information and the fact that the flight instructor had flown over them many times, the power lines should not have been a hazard. The flight instructor's slow response to the student pilot's failure to increase power during the descent led to the airplane's collision with the wire.

Probable cause

The student pilot's failure to increase engine power during the descent for landing when instructed to do so by the flight instructor and the flight instructor's delayed remedial action, which resulted in collision with a static wire. Contributing to the accident was the student pilot's failure to use hearing amplification as required by his Federal Aviation Administration medical certificate.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13LA281
Event ID
20130612X33520
Case number
ERA13LA281
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: f524fc7bae2f750ae33f926c14ce60d61d103fe05eb30764a2ad43e904a516c3; retrieved 2026-09-14T15:58:41.539Z.