GAA18CA396 · Cessna 182 Q
Above All Aviation Cessna 182 Q · Accident: abnormal runway contact during landing
From Santa Barbara Municipal Airport (SBA) to San Luis County Regional Airport (SBP)
Event
- NTSB case
- GAA18CA396
- 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
- N411BP
- Operator
- Above All Aviation
- Onboard fatalities
- Unknown
- Route
- From Santa Barbara Municipal Airport (SBA), Santa Barbara, CATo San Luis County Regional Airport (SBP), San Luis Obispo, CA
- Aircraft age
- About 41 years (built 1977)
- 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
According to the pilot, he made a straight-in approach about 80 knots and full flaps on final. He initiated the landing flare and "felt a slight sink in lift," which resulted in a hard landing. He reported that the airplane bounced four times with each bounce increasing in height and magnitude. Subsequently, he taxied the airplane to the nearest intersection but was unable to continue because the airplane was "taxiing rough", and he believed that the nose landing gear tire was damaged.
The airplane sustained substantial damage to the left and right fuselage stringers.
Additionally, the pilot asserted that proper trim application could have helped to prevent this accident and that he should have aborted the landing after the first hard bounce.
The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
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 GAA18CA396
- Event ID
- 20180709X25845
- Case number
- GAA18CA396
- 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: 8f4e7cae99085929c88c263030316c26e89246948ae52fbfcb76750067960641; retrieved 2026-09-16T07:47:35.084Z.