ERA17LA319 · Cessna 172 P
Cessna 172 P · Accident: hard landing
From Pensacola International Airport (PNS) to Jack Edwards National Airport (JKA)
Event
- NTSB case
- ERA17LA319
- 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
- 0 · 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 P
- 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
- N97116
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Pensacola International Airport (PNS), Pensacola, FLTo Jack Edwards National Airport (JKA), Gulf Shores, AL
- Aircraft age
- About 33 years (built 1984)
- 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial helicopter pilot, who was enrolled in transition training for airplanes, stated that he made a normal approach to land the airplane, but when he pulled back on the control yoke, the nose of the airplane did not come up as expected. The airplane had a flat attitude, landed hard, and bounced four or five times, which resulted in damage to the firewall, the nosewheel, and both propeller blades. Postaccident examination of the airplane revealed that the control yoke had minimal movement due to the upper yoke control tubes at the chain sprocket binding against the aluminum channel brace due to the bent firewall. The examination also found that the elevator trim tab cable had slack and was not rigged correctly, which was not due to the hard landing: when the trim tab wheel was moved, the cable's center travel block would catch on the aft tail cone bulkhead. However, subsequent examination of the airplane did not reveal any evidence of a preimpact elevator control problem, despite the rigging of the elevator trim tab cable. A student pilot who had flown the airplane before the accident flight had not reported any issues with landing the airplane.
At the time of the accident, the pilot had accrued 29 hours of flight experience in single-engine airplanes. About 1 month after the accident, the pilot flew with a Federal Aviation Administration designated pilot examiner (DPE) and, according to the DPE, executed several landings that had a flat attitude versus a nose-high attitude. On one landing, the airplane bounced and then ballooned, which resulted in the DPE taking control of the airplane. The DPE later spoke with the pilot's flight instructor, who confirmed that the pilot tended to not properly flare on landing. Although the elevator trim tab cable was not rigged correctly, it did not impede the use of the elevator or the pilot's ability to properly flare the airplane for a safe landing. Thus, it is likely that the pilot did not flare properly, which resulted in a hard landing.
Probable cause
The pilot's improper landing flare, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17LA319
- Event ID
- 20170912X10501
- Case number
- ERA17LA319
- 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: 85a81b5f35cd78521c62ce9dc70253edccbc47d12d4625e90f31a6003f848507; retrieved 2026-09-16T05:49:46.631Z.