FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12FA021 · Cessna 182R

26 Oct 2011 · Lexington, OR, United States

Cessna 182R · Accident: controlled flight into terrain/object (CFIT) en route

From Tri Cities Airport (PSC) to Lexington, OR

Report a problem

Event

NTSB case
WPR12FA021
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
1 · 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 182R

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
N6545E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tri Cities Airport (PSC), Pasco, WATo Lexington, OR
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 · descent
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
Controlled flight into terrain/object (CFIT)
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 › Action/decision
  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot was returning to his home airport during dark night conditions with 0 percent moon illumination. The passenger reported that he had been resting during the flight until the pilot announced that they were approaching the airport. The passenger stated that the airplane was on a 5-mile base leg and that they could see the runway lights when the airplane unexpectedly hit the ground. The passenger reported that he did not hear the pilot make any warning comments. Postaccident examination of the engine and airframe revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.

A review of recorded radar data indicated that the airplane had attained a maximum altitude of 4,400 ft as it tracked toward the destination airport, which has an elevation of 1,634 ft. The airplane then began a gradual descent; the last radar target showed the airplane at 2,300 ft near the accident site, which was at an elevation of 2,262 ft and was located high on a ridge in the middle of a wheat field. The debris path was about 486 ft long. Although the pilot could see the runway lights in the distance, it is likely that, due to the lack of illumination, he failed to maintain situational awareness of the hilly terrain that was higher than the airport.

The passenger sustained serious injuries. The pilot was conscious after the accident, and he told the passenger that he was trapped in the wreckage and could not get free. The passenger subsequently went for help, and, after 4 hours, he located a house and reported the accident. A search had already been initiated about 2 hours earlier because the airplane had been reported overdue. The wreckage was located shortly after the passenger reported the accident. By the time first responders arrived on site, the pilot had succumbed to his injuries.

A review of the pilot's medical history indicated that he was apparently in good health. Toxicology tests detected the sedating antihistamine diphenhydramine in the pilot's urine, which precluded it from having any ongoing systemic effects on the pilot's performance. The pilot's injuries, which included blunt force head and chest trauma, were not immediately fatal, and it is possible he could have survived for hours. The cold weather likely contributed to the development of acidosis due to the severity of the pilot's injuries and may have further impeded his ability to breathe.

The only emergency locator transmitter (ELT) device on board the airplane broadcast an emergency signal on 121.5 and 243.0 MHz. The ELT was functional, but no pilots reported hearing an emergency beacon following the accident. Further, the International Search and Rescue Satellite-Aided Tracking (SARSAT) system has not monitored ELTs operating on 121.5 and 243.0 MHz since February 2009. Therefore, with the ELT that was on board the airplane, the injured pilot could not have been located any faster than the 4-hour response time that occurred after the injured passenger notified local authorities about the accident. The pilot's injuries led to his death within this time period.

The National Oceanic and Atmospheric Administration-SARSAT reported that, if a 406-MHz ELT had survived the crash and activated properly, it could have provided a first alert within minutes to the Air Force Rescue Coordination Center and an accurate location within 90 minutes. Further, if the ELT had GPS capabilities, the location of the accident site could also have been identified within minutes. An earlier notification would have significantly reduced the emergency response time and increased the chances of the pilot's survival.

Probable cause

The pilot’s failure to maintain situational awareness and terrain clearance on a dark night during the approach to landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12FA021
Event ID
20111027X60809
Case number
WPR12FA021
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-10-27.
  • API snapshot SHA-256: 3ec4a135cd3a61d17cd1d56651f9d6e542cdd6f4e909554aec5dd0fab071ab8c; retrieved 2026-09-13T21:56:44.877Z.