LAX04FA031 · Cessna 421B
Cessna 421B · Accident: in flight encounter with weather en route
From Laughlin Bullhead International Airport (IFP) to Van Nuys Airport (VNY)
Event
- NTSB case
- LAX04FA031
- 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
- 5 · 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 421B
- Aircraft type
- Cessna 421
- 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
- N444AM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Laughlin Bullhead International Airport (IFP), Bullhead City, AZTo Van Nuys Airport (VNY), Van Nuys, CA
- 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
- First occurrenceThe 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
- In flight encounter with weather
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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
- Flight control, elevator › Overload
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Design stress limits of aircraft, exceeded
- Pilot in command › Spatial disorientation
- Pilot in command › VFR flight into imc, continued
- Wing › Overload
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The aircraft broke up in-flight during a high speed descent after encountering clouds and reduced visibilities aloft. The weather conditions included multiple cloud layers at 9,000, 12,000 and 16,000 feet, and reduced visibility aloft from smoke and haze from wilderness wild fires that were occurring over large portions of Southern California. The aircraft departed the airport toward a VORTAC to the west, approximately 30 nautical miles (nm) away. The first radar contact was at 1159, and the aircraft's Mode C transponder reported an altitude of 3,500 feet mean sea level (msl). By the time the aircraft reached the VORTAC, the altitude had increased to 4,900 feet msl. The aircraft continued to climb, passing through the VFR flight plan filed altitude of 8,500 feet msl, until it reached an altitude of 12,900 feet msl. The last 6 minutes of radar data reported the aircraft at various altitudes, starting at 11,000 feet msl and climbing to a maximum altitude of 12,700 feet msl. During the last 3 minutes of flight, radar data showed the aircraft made numerous left and right climbing and descending turns, eventually reversing course. The next to last radar return at 1221:24 indicated an altitude of 11,900 feet msl. Nineteen seconds later, the last radar return reported an altitude of 7,700 feet msl. The computed vertical speed between the last two radar returns was 13,263 feet per minute. The wreckage was distributed over a 0.2-nm distance, with the main wreckage approximately 0.5 miles northwest of the last radar return. The northern end of the debris path began with pieces of the left elevator, followed by sections of the right stabilizer and elevator, and more sections from both horizontal empennage surfaces. Pieces of the vertical stabilizer, rudder, and both ailerons were also found along the debris path. The southern 100 feet of the debris path contained the fuselage and both sets of wings, engines, and propellers. The aircraft impacted the ground inverted. The wings separated just outboard of the nacelles at the initial point of impact. Examination of the wreckage showed that all structural failures were the result of overload.
Probable cause
The pilot's continued VFR flight into instrument conditions between cloud layers and with reduced visibility due to smoke that resulted in an in-flight loss of control from spatial disorientation, and the structural overload of the airframe during the subsequent high speed descent.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04FA031
- Event ID
- 20031110X01878
- Case number
- LAX04FA031
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 319f39c5d85c837adff3e522c152d8738b5dac5d86b35e9a92b271dace1b3a55; retrieved 2026-09-20T18:50:00.666Z.