ERA16CA222 · Cessna 172M
Lenoir Aviation Club Cessna 172M · Accident: abnormal runway contact during landing
From Davidson County Executive Airport (EXX) to Lower Creek Airport (NC27)
Event
- NTSB case
- ERA16CA222
- 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 172M
- 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
- N12184
- Operator
- Lenoir Aviation Club
- Onboard fatalities
- Unknown
- Route
- From Davidson County Executive Airport (EXX), Lexington, NCTo Lower Creek Airport (NC27), Lenoir, NC
- Aircraft age
- About 43 years (built 1973)
- 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
- Abnormal runway contact
- 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 › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot was returning to his home airport while on his first solo cross-country flight. The wind sock at the airport was favoring a landing on runway 23 with a slight crosswind. He entered the traffic pattern, and when he lined up on the final leg of the traffic pattern to the turf runway, the airplane encountered a large wind gust. He then aborted the landing and rejoined the traffic pattern. The wind sock was still favoring a landing on runway 23, so he set up for the landing again, and this time encountered a larger wind gust, so he aborted the landing a second time. He then entered the traffic pattern again and noticed that the wind sock was still indicating a slight crosswind but now favored a landing on runway 5. He then flew around the traffic pattern and set up for a landing on runway 5. The student reported that, while on final approach for runway 5, the airspeed was "good." The airplane touched down and then "bounced," and the pilot attempted to recover the landing, but the nose landing gear then dug into the ground. The airplane nosed over and came to rest inverted, which resulted in substantial damage to the empennage and vertical stabilizer.
Review of archived weather information revealed that, about the time of the accident, the wind was 330° at 11 knots, gusting to 16 knots. Additionally, wind gusts were present for nearly 4 hours before the accident and continued for about 4 hours after the accident. Before the flight, the student pilot met with his flight instructor and showed him his flight plan. The instructor spoke with the student but did not look at the weather reports, and they "did not call in to check the weather." Review of the student's logbook revealed that it contained an endorsement from the instructor stating that he had reviewed the student's cross-country planning and preparation and found it to be correct and adequate for the flight. The endorsement also contained the caveat that the weather should be "clear," and crosswinds should not exceed 7 knots.
Probable cause
The student pilot’s failure to compensate for gusting wind conditions during landing, which resulted in a bounced landing. Contributing to the accident was the flight instructor’s inadequate review of the weather conditions with the student and his inadequate supervision of the student’s solo cross-country flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16CA222
- Event ID
- 20160621X22330
- Case number
- ERA16CA222
- 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: 95e47e13744713f968cff0defb61075612752ea3de3a01ea80a9249d352709c2; retrieved 2026-09-16T03:31:55.157Z.