ERA24LA352 · Cessna 172 N
Wings Flight Enterprises Cessna 172 N · Accident: hard landing
From DKK · Knoxville, TN to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA24LA352
- 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
- Event fatalities
- Unknown
- 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 N
- 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
- N9991E
- Operator
- Wings Flight Enterprises
- Onboard fatalities
- Unknown
- Route Possible conflict
- From DKK · Knoxville, TNTo not recorded
- Aircraft age
- Not recorded
- 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
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot (who was the pilot-in-command for the flight) was flying with two passengers, one of whom was seated in the right front pilot seat, held a commercial pilot certificate, and had more flight experience than the private pilot. The pilot-rated passenger in the right front seat reported that during the approach, she had commented to the pilot twice about the airplane’s airspeed, and that she had nudged the yoke forward with one finger as an indication to the pilot to lower the nose; however, the pilot pulled back on the yoke and added power to cushion the landing, which resulted in several bounces on the runway before the airplane traveled off the left side. She further described that the landing flare occurred while the airplane too high above the runway and at too slow a speed, about 15 ft above the runway and at an airspeed decreasing to less than 50 knots. The pilot reported that during the landing attempt, after the pilot-rated passenger pushed the yoke forward, he pulled back because he did not want the nose of the airplane to strike the runway first, which resulted in a hard landing and subsequent bounce. As the pilot was attempting to regain control of the airplane, the pilot-rated passenger increased the engine power to full in attempt to abort the landing, but the airplane then veered to the left and departed the runway surface. The airplane came to rest upright in a grass area next to the runway. The fuselage was substantially damaged during the accident sequence. The pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation. He also stated that, “…we will need to improve the communication between me as the PIC and [any pilot-rated passengers] such as informing me of their concern rather than touching the control, especially during landing.”
Probable cause
The pilot’s failure to maintain control of the airplane while landing and his inadequate communication to the pilot-rated passenger of her role during the flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA352
- Event ID
- 20240820194966
- Case number
- ERA24LA352
- 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, coordinates, cause areas. 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: cd16f102d37c397fb5958fa52b98b53b3ac1fbf119dddf8ece5963e8d09986a9; retrieved 2026-09-16T19:11:22.922Z.