FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09FA248 · Cessna 172N

18 May 2009 · Long Beach, CA, United States

Aero Aviation Cessna 172N and Cessna 310P · Accident: midair collision while maneuvering

Report a problem

Event

NTSB case
WPR09FA248
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
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 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
N738NN
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
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
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
Substantial

Aircraft 2 · Cessna 310P

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
N777AL
Operator
Gary D Gierczak · private individual
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
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
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
Substantial

Cause areas

  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

A Cessna 172N and a Cessna 310P collided in flight in a common practice area for airwork. A witness was flying on a southerly heading within the immediate area of the collision and noticed a silhouette of an airplane, which appeared to be a Cessna 172 at his 10 to 11 o'clock position. The airplane appeared to be performing maneuvers and making turns in a counter-clockwise direction, followed by a turn in a clockwise direction. The witness stated that he noticed another airplane entering the area from the west, traveling at a high rate of speed on an easterly heading. He added that he was unable to see what kind of airplane it was and only saw a "black object" due to the sun being almost on the horizon. The witness continued to watch both airplanes and noted the fast moving airplane was continuing on an easterly heading while the Cessna 172N was still performing maneuvers on a southerly heading around the same altitude. The witness observed both airplanes collide, disintegrate into small pieces, and fall to the ocean below. Review of recorded radar data revealed that the Cessna 310P was maneuvering within a common practice area about 5 miles south of the shoreline at various altitudes. The data depicted the Cessna 172N on a southerly course at an altitude of 3,000 feet msl while conducting a series of shallow left and right turns prior to performing a left 360-degree turn to a southerly heading. The Cessna 310P was on an easterly heading at an altitude of 3,000 feet msl for about 2 minutes prior to the collision. The radar data depicted the two airplanes converging nearly perpendicular to one another about five miles south of the shoreline. During examination of the recovered wreckage, transfer marks were identified consistent with the radar-derived collision angle. Both airplanes were operating under visual conditions when they collided.

Probable cause

The failure of both pilots to see and avoid each other's aircraft.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09FA248
Event ID
20090519X12854
Case number
WPR09FA248
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2009-05-19.
  • API snapshot SHA-256: 3ebaf47cccfe0448b5816d488fff8db680a341323232aa66694b6202b4e0f4aa; retrieved 2026-09-13T18:04:14.438Z.