CEN16LA231 · Cessna 182Q Q
Cessna 182Q Q · Accident: hard landing
From Anoka County-Blaine (Janes Field) Airport (ANE) to Anoka County-Blaine (Janes Field) Airport (ANE)
Event
- NTSB case
- CEN16LA231
- 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 182Q 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
- N377H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Anoka County-Blaine (Janes Field) Airport (ANE), Anoka, MNTo Anoka County-Blaine (Janes Field) Airport (ANE), Anoka, MN
- 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 · 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
- 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 was conducting a local personal flight. The pilot reported that, while in the traffic pattern, she applied carburetor heat and extended the flaps to 10 degrees. At this point, the passenger informed her that the engine manifold air pressure had reduced to 4 inches. She added throttle, and the manifold air pressure recovered to between 14 and 15 inches. The pilot stated that she was concerned about having an engine failure and kept the airspeed at 80 knots until she was sure the airplane could reach the runway. She added that she then throttled back and that the airspeed reduced to 60 knots and, as the airplane crossed the end of the runway, she "lost all airspeed." She stated that, shortly after, the airplane descended to 8 to 10 ft above the ground and then landed hard. Based on the available information, the airplane's engine responded to the pilot's control inputs. It is likely that the pilot's concern about the engine led to her failure to maintain a proper approach airspeed during the landing, which resulted in a hard landing.
Probable cause
The pilot's failure to maintain a proper airspeed during the landing approach, which resulted in an improper flare and hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA231
- Event ID
- 20160623X01153
- Case number
- CEN16LA231
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-06-22.
- API snapshot SHA-256: 7cb9580efa9abd6975495ac2eac5943539c282ab7c01ce4b74408d31ec17b7c9; retrieved 2026-09-16T03:32:38.778Z.