GAA18CA552 · Cessna 182 Q
Hill Flying Club Cessna 182 Q · Accident: abnormal runway contact during landing
From Ogden Hinckley Airport (OGD) to Page Municipal Airport (PGA)
Event
- NTSB case
- GAA18CA552
- 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
- N5198N
- Operator
- Hill Flying Club
- Onboard fatalities
- Unknown
- Route
- From Ogden Hinckley Airport (OGD), Ogden, UTTo Page Municipal Airport (PGA), Page, AZ
- 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
- 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, shortly after transition to cruise flight, he noticed that the engine was "running rough," the cylinder head temperature was almost in the red, and the engine rpm and manifold pressure were decreasing. He decided to return to the departure airport for a precautionary landing. On approach, he decreased the engine power setting and increased the mixture and propeller settings, and the airplane then crossed the runway threshold about 80 knots with full flaps. The pilot added that, during the landing flare, the airplane "dropped" and then bounced two to three times on the runway. He taxied the airplane off the runway, and it was then was towed back to the ramp.
The airplane sustained substantial damage to the fuselage.
The Federal Aviation Administration inspector reported that there no mechanical failures or malfunctions with the airplane that would have precluded normal operation.
The airport's automated weather observation station reported that, about the time of the accident, the wind was variable at 4 knots. The pilot landed the airplane on runway 33.
Probable cause
The pilot's improper landing flare, which resulted in a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA552
- Event ID
- 20180911X12858
- Case number
- GAA18CA552
- 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: 5aad654cbd9c338eb3036be538702ce097d413e73032ac99bc6759d547eb58a5; retrieved 2026-09-16T08:14:07.366Z.