FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX98FA118 · Cessna 310H

19 Mar 1998 · Corona, CA, United States

Cessna 310H and Cessna 152 · Accident: midair collision en route

Report a problem

Event

NTSB case
LAX98FA118
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
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

Aircraft 1 · Cessna 310H

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
N310RR
Operator
Unknown
Onboard fatalities
Unknown
Route
From L67 · Rialto, CATo Chino Airport (CNO), Chino, 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
Midair collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Aircraft 2 · Cessna 152

Aircraft type
Cessna 152
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
N6575L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Riverside Municipal Airport (RAL), Riverside, CATo AJO
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
Midair collision
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 › Visual lookout, inadequate
  • Pilot of other aircraft › Visual lookout, inadequate

Approximate · Estimated position: the centre of Corona, CA, the place the record names. Not the accident site.

NTSB narrative

A Cessna 310 and a Cessna 152 collided in-flight about 2 miles south of the Corona airport at 2,600 feet mean sea level (about 2,000 above ground level). The Cessna 310, with two pilots aboard, was descending toward another nearby area airport, and the Cessna 152, flown by a certified flight instructor (the sole occupant) from the right seat, was orbiting south of the airport awaiting the reopening of the runway following construction. Radar data showed that in the 1 minute 18 seconds prior to the collision, the Cessna 310 descended from 4,000 feet to the collision point on a southeast bound ground track at a rate of about 1,200 feet per minute. Nine seconds prior to the collision, the Cessna 152, which had been on a westbound track, began a right turn toward a northwest bound ground track. Over the 1 minute 18 second period, the horizontal separation decreased from 6.01 nautical miles to zero as the vertical separation decreased 1,400 feet. Reconstruction of the two airplanes revealed that at the point of collision, the Cessna 310's lateral axis was about 80 degrees to the Cessna 152's vertical axis as the 310's outer right wing and tip tank contacted the 152's left main gear strut, lift strut, and inboard left wing. In the one minute prior to the collision, the relative horizontal bearing from the Cessna 310 ground track to the Cessna 152 was between 8 and 10 degrees left of the track. During this same period, the relative horizontal bearing from the Cessna 152 ground track to the Cessna 310 varied between 25 degrees and 40 degrees right of the Cessna 152 ground track as it maneuvered prior to the right turn. Trigonometric calculation of altitude difference between the targets yielded a 2 degree 10 minute relative vertical angle between the target positions.

Probable cause

The failure of both pilots to maintain an adequate visual lookout and to see and avoid the other airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX98FA118
Event ID
20001211X09700
Case number
LAX98FA118
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-03-20.
  • API snapshot SHA-256: 6e5f31502f6b8bdfd762e95e40dab841a0baec89d1ba7bb343aff0036a605fda; retrieved 2026-09-20T22:39:07.277Z.