LAX98FA296 · Cessna 310K
Cessna 310K · Accident: in flight encounter with weather while maneuvering
From General William J Fox Airfield (WJF) to Van Nuys Airport (VNY)
Event
- NTSB case
- LAX98FA296
- 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
- 2 · all aircraft and ground
- Ground fatalities
- 0
- 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 310K
- Aircraft type
- Cessna 310
- 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
- N711CG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From General William J Fox Airfield (WJF), Lancaster, CATo 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
- Maneuvering
- 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
- 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
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Design stress limits of aircraft, exceeded
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
The instrument rated private pilot and two passengers were returning from the Reno Air Races where they had participated as pylon spotters. The destination airport was overcast with low stratus clouds. The pilot checked three mountain passes for a visual route into the coastal basin without success and diverted to an airport on the desert side of the coastal mountains for additional fuel and to file an IFR flight plan into the basin. One passenger chose to disembark and the pilot and remaining passenger departed. Recorded radar data and air-to-ground communications tapes between the airplane and the ATC facilities that worked the flight were obtained and disclosed that the pilot responded to heading and altitude instructions. While on vectors to intercept the destination ILS, the controller took the aircraft through the final approach twice for spacing with a preceding airplane. The mode C report displayed a 6,000-foot altitude as the controller issued an instruction to reduce to final approach speed and then turn right to a new heading. The secondary beacon target began the right turn and radar contact was lost with the airplane. The last recorded mode C report displayed 6,100 feet mean sea level. Witnesses near the impact site heard an airplane in the low overcast estimated to be 800 to 1,000 feet above ground level. The airplane sound was changing as though it was orbiting or turning. The witnesses then saw the airplane descending out of the clouds in a nose down attitude. The airplane appeared to start a pullout when a noise was heard and the airplane tail appeared to break apart. Fragmented components of the tail assembly were recovered from various locations and distances from the wreckage site. Reconstruction of the wreckage found no abnormal conditions in either the aircraft structure or flight instruments.
Probable cause
the pilot's in-flight loss of control which led to a subsequent structural airframe failure as the pilot exceeded the design stress limits of the airplane during an attempted recovery.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX98FA296
- Event ID
- 20001211X11086
- Case number
- LAX98FA296
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1998-09-21.
- API snapshot SHA-256: ab51a10b4f95c461835e1ea41cd2ad4da6678d49f51a535354fa05df2caf4ee4; retrieved 2026-09-20T22:24:20.939Z.