WPR12FA031 · Cessna 182Q
Cessna 182Q · Accident: loss of control in flight en route
From Glendale Municipal Airport (GEU) to Lake Havasu City Airport (HII)
Event
- NTSB case
- WPR12FA031
- 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
- 3 · 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
- 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
- N4701N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Glendale Municipal Airport (GEU), Glendale, AZTo Lake Havasu City Airport (HII), Lake Havasu, AZ
- 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
- En route · cruise
- 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
- Loss of control in flight
- 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
- Personnel issues › Action/decision
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The non-instrument rated pilot was flying home after watching a football game. Because the game continued into overtime, the flight home occurred later than the pilot expected and involved flying at night. The pilot had obtained a weather briefing earlier that morning and was aware that a storm was due to arrive in the area about the time the return flight took place. At the time of the accident, visual meteorological weather conditions existed at all area airports; however, it was raining and clouds were present at the pilot’s intended cruise altitude during portions of the return flight.
According to global positioning system data, the flight appeared to progress normally until about halfway along the planned route when the airplane suddenly descended about 1,000 feet, presumably to avoid clouds. A short time later, the airplane began a series of altitude and airspeed oscillations, which ultimately resulted in a rapidly descending turn into terrain. The debris field length and orientation were consistent with a loss of airplane control, with the airplane striking the ground inverted and at high speed. All sections of the airplane were accounted for at the accident site, and postaccident examination did not reveal any mechanical malfunctions or failures that would have precluded normal operation.
The pilot had flown the same route at night on four previous occasions, the most recent of which was 2 weeks before the accident; however, clear skies and unlimited visibilities existed for each of the previous flights. According to weather data, on the night of the accident, the moon was obscured by cloud, and therefore would have provided no visual reference. In addition, most of the accident flight occurred over uninhabited desert terrain, so limited ground references would have been available.
Probable cause
The pilot's continued cruise flight into cloudy conditions at night, which resulted in a loss of airplane control due to spatial disorientation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12FA031
- Event ID
- 20111109X93553
- Case number
- WPR12FA031
- 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 2011-11-07.
- API snapshot SHA-256: dd0e119fb676939689ad708ffece8215ffdc659fc6e6855162e3a7c05ff0f411; retrieved 2026-09-13T21:57:58.817Z.