FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23FA257 · Cessna 550

8 Jul 2023 · Murrieta, CA, United States

Cessna 550 · Accident: altitude deviation on approach

From Harry Reid International Airport (LAS) to an unrecorded destination

Report a problem

Event

NTSB case
WPR23FA257
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
6 · 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
Instrument Meteorological Cond

Cessna 550

Aircraft type
Cessna 550
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
N819KR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Harry Reid International Airport (LAS), Las Vegas, NVTo not recorded
Aircraft age
About 44 years (built 1979)
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
Approach · IFR final approach
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
Altitude deviation
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During an early morning night flight, the flight encountered deteriorating weather conditions with a low overcast ceiling and rapidly decreasing visibility at the destination due to fog. A few minutes before the flight’s arrival time at the destination airport, the weather had changed from being clear with 10 statute miles (sm) visibility to 300 ft overcast with 3/4 sm visibility. Additionally, in the next 20 minutes, the visibility further decreased to about 1/2 sm with fog. The airplane was cleared for the RNAV (GPS) Runway 18 instrument approach to the airport. The lowest visibility requirement on the approach was 7/8 of a mile. During the final approach, the pilot executed a missed approach and asked to try another instrument approach. During the second instrument approach, while on final approach, the pilot failed to fly a stabilized approach as the airplane’s descent rate and airspeed were excessive. Subsequently, the airplane descended below the decision altitude of the approach without appropriate visual references and impacted terrain about 810 ft short of the runway threshold. The circumstances of the accident flight were consistent with controlled flight into terrain (CFIT). The postaccident examination of the airplane and engines revealed no evidence of mechanical failures or malfunctions that would have precluded normal operation of the airplane. The pilot had very low levels of ethanol detected in postmortem vitreous fluid and cavity blood. Some or all of this small amount of ethanol may have been from sources other than alcohol consumption. Although it is uncertain whether the pilot had consumed alcohol overnight, the toxicology results indicate that it is unlikely that the pilot’s performance would be significantly affected by ethanol. The copilot’s ethanol levels were high in all tested postmortem specimens. Based on the toxicology results and the circumstances of the event, it is likely that the copilot had consumed alcohol. However, based on the extent of his injuries, the presence of indicators of microbial decomposition, and the relative differences in ethanol levels across specimens, it also is likely that some of the detected ethanol was from sources other than alcohol consumption. The copilot’s blood alcohol level at the time of the crash cannot be reliably determined from available evidence. Overall, alcohol-related impairment may have limited the copilot’s ability to make a positive contribution to flight safety (such as by helping to monitor the approach); however, whether the effects of alcohol use by the copilot contributed to the accident outcome could not be determined.

Probable cause

The flight crew’s decision to descend below the decision altitude of an instrument approach without having the appropriate runway visual reference(s) distinctively identified and with the visibility below the minimum that was prescribed for the approach, which resulted in controlled flight into terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23FA257
Event ID
20230708192559
Case number
WPR23FA257
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, cause areas. 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: 570dfdc054705b68a82aedc9a0c0ca1f1ba7daa185693ff479d0fc8e69d04b69; retrieved 2026-09-15T08:02:37.294Z.