LAX01FA101 · Cessna 152
Candace A. Larned Enterprises Cessna 152 and Candace A. Larned Enterprises Cessna 172N · Accident: midair collision while maneuvering
Event
- NTSB case
- LAX01FA101
- 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
- 4 · 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
Aircraft 1 · 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
- N68763
- Operator
- Candace A. Larned Enterprises
- Onboard fatalities
- Unknown
- Route
- From Long Beach International Airport (LGB), Long Beach, CATo Long Beach International Airport (LGB), Long Beach, 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
- 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 172N
- Aircraft type
- Cessna 172
- 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
- N4686G
- Operator
- Candace A. Larned Enterprises
- Onboard fatalities
- Unknown
- Route
- From Long Beach International Airport (LGB), Long Beach, CATo Long Beach International Airport (LGB), Long Beach, 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
- 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
- Pilots of both aircraft › Visual lookout, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A midair collision occurred between the Cessna 152 and a Cessna 172, which were flying between 800 and 1,000 feet above the ocean in an established student training practice area. The flight instructors and their respective students lost control of their airplanes, which descended into the ocean and sank. An eyewitness in a ship observed the airplanes seconds prior to the collision. The witness stated that "one plane appeared to bank and turn directly into the other plane." Another witness, who was airborne in a helicopter, reported that before the impact he had observed one of the airplanes performing counterclockwise orbits, like a turn about a point ground reference maneuver. This airplane had completed several circles when it collided with another airplane that was flying in a westerly direction. Neither the Cessna 152's empennage nor the Cessna 172's engine was recovered. Radar tracks for the airplanes could not be determined. The collision occurred in a near head-on trajectory, based upon the severity of the impact damage to the leading edge of the Cessna 152's right wing, the lack of impact damage in the Cessna 172's aft fuselage and empennage, the witness statements, and the locations where the airplanes were found (the Cessna 152 was west of the Cessna 172).
Probable cause
The failure of the flight crews of both airplanes to maintain adequate visual lookout for traffic.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01FA101
- Event ID
- 20010228X00524
- Case number
- LAX01FA101
- 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: 9a545ce484a0c816c984cb3b8f0ef5d12dd9defdf0fe2263cc1da08919fa076c; retrieved 2026-09-20T20:39:44.020Z.