GAA18CA202 · Cessna 182 Q
Cessna 182 Q · Accident: abnormal runway contact during landing
From Skypark Airport (BTF) to J. Randy McKnight Nephi Municipal Airport (U14)
Event
- NTSB case
- GAA18CA202
- 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 182 Q
- Aircraft type
- Cessna 182
- 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
- N5292N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Skypark Airport (BTF), Bountiful, UTTo J. Randy McKnight Nephi Municipal Airport (U14), Nephi, UT
- Aircraft age
- About 38 years (built 1980)
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during the landing flare, the airplane "lurched to the left of the runway, yawed to the right, and nosed down." He added that, as he corrected the airplane parallel with the runway centerline, the airplane "immediately dropped" to the ground and it felt like a "hard landing." He continued the landing roll, taxied clear of the runway, and did a brief check from inside of the airplane for damage. Subsequently, he did not note anything abnormal and proceeded to taxi to the departure airport without further incident.
A postflight examination revealed that the airplane sustained substantial damage to the fuselage.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
The pilot further reported that he believed that a tailwind gust may have been responsible for the sideways lurch, and that the airplane may have stalled resulting in the nose pitching down and the hard landing.
A commercial weather reporting station for the town, about 3 miles from the accident airport, reported about the time of the accident that the sky was clear, and the wind was southwest at 5 knots. The pilot landed runway 17.
Probable cause
The pilot’s failure to maintain a proper landing flare, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA202
- Event ID
- 20180405X31138
- Case number
- GAA18CA202
- 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: aab6587b3a2475b704df9e1f48c8ba454a83d540949e92fa46de830d8825f276; retrieved 2026-09-16T06:47:01.712Z.