The U.S. aircraft register, updated daily
Accidents · NTSB WPR12LA109 · Final report

Robinson Helicopter R22 BETA and Beech 35-A33 mid-air collision near Antioch, California, February 20, 2012

On February 20, 2012 at about 2:45 am local time, 2 aircraft, Robinson Helicopter R22 BETA (N7508Y) and Beech 35-A33 (N433JC), were involved in a mid-air collision near Antioch, California (Byron airport). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The failure of both pilots to see and avoid the other aircraft during cruise flight. Contributing to the accident was the failure of air traffic control personnel to issue the helicopter pilot with a prompt and appropriate alternate course of action upon receiving a conflict alert.
The failure of both pilots to see and avoid each other during cruise flight, which resulted in a midair collision. Contributing to the accident was the failure of air traffic control personnel to issue the helicopter pilot a prompt and appropriate alternate course of action upon receiving a conflict alert.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 20, 2012 · about 2:45 am local time
Place
Antioch, California · Byron · map
Type
Accident · mid-air collision
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft 1
Robinson Helicopter R22 BETA, built 2005 · all R22 BETAs on the register
Registration
N7508Y · no longer on the register · serial 3757
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)
Aircraft 2
Beech 35-A33, built 1961 · all 35-A33s on the register
Registration
N433JC · no longer on the register · serial CD-351
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative for the Robinson Helicopter R22 BETA final · quoted from the NTSB record

The helicopter and airplane collided midair. Both aircraft sustained minimal damage during the impact but substantial damage during the subsequent forced landings. The airplane pilot was performing a local flight and was not in contact with air traffic control (ATC) before the collision. The helicopter pilot was receiving visual flight rules flight following services from ATC throughout the flight. The helicopter pilot transitioned between two ATC sectors before the accident. On multiple occasions, the controllers for each sector misidentified the last three digits of the helicopter's call sign. Additionally, the controller in the accident sector issued a traffic advisory using the wrong call sign. Further, an aircraft with the same last three digits as the helicopter's incorrect call sign made radio contact with the controller shortly before the collision, which increased the confusion. Audio data revealed that the air traffic controller provided multiple traffic advisories to the helicopter but did not issue an alternate or immediate course of action in accordance with ATC procedures despite the fact that the aircraft's converging flightpaths had triggered the radar conflict alert system. Radar playback also revealed that, at that time, the controller was receiving a visual alert on the radar console. This alert was also observed by a controller in an adjacent approach sector who called the radar assist controller warning of the threat. The assist controller responded, "yeah, we're givin' him traffic." A few seconds later, the radar targets merged. The helicopter pilot stated that she received and complied with the traffic advisories by performing a visual scan but that, based on her communications with the air traffic controller, she did not perceive the situation to be urgent. Radar data revealed that the helicopter descended 600 feet before the collision but that the pilot did not inform the air traffic controllers about the descent. Further, as the airplane got closer and the traffic advisories were issued, the helicopter pilot began turning north, which brought the helicopter directly into the path of the approaching airplane while simultaneously placing the airplane behind her immediate field of vision. Shortly after, she sighted a silhouette of the airplane and propeller at her 4-o'clock position. She performed an evasive maneuver to the left but then felt the helicopter being struck. Neither the airplane pilot nor the occupant observed another aircraft near the airplane before the collision. Although the airplane pilot was not receiving traffic advisories from ATC, it was still the pilot's responsibility to maintain a proper visual lookout to avoid other aircraft in the area. The helicopter's left navigation light was inoperative when tested after the accident; however, this most likely did not affect the outcome because the left side of the helicopter would not have been visible to the airplane pilot at any point during the flight.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The NTSB's narrative for the Beech 35-A33 final · quoted from the NTSB record

The helicopter and airplane collided midair. Both aircraft sustained minimal damage during the impact but substantial damage during the subsequent forced landings. The airplane pilot was performing a local flight and was not in contact with air traffic control (ATC) before the collision. The helicopter pilot was receiving visual flight rules flight following services from ATC throughout the flight. The helicopter pilot transitioned between two ATC sectors before the accident. On multiple occasions, the controllers for each sector misidentified the last three digits of the helicopter's call sign. Additionally, the controller in the accident sector issued a traffic advisory using the wrong call sign. Further, an aircraft with the same last three digits as the helicopter's incorrect call sign made radio contact with the controller shortly before the collision, which increased the confusion. Audio data revealed that the air traffic controller provided multiple traffic advisories to the helicopter but did not issue an alternate or immediate course of action in accordance with ATC procedures despite the fact that the aircraft's converging flightpaths had triggered the radar conflict alert system. Radar playback also revealed that, at that time, the controller was receiving a visual alert on the radar console. This alert was also observed by a controller in an adjacent approach sector who called the radar assist controller warning of the threat. The assist controller responded, "yeah, we're givin' him traffic." A few seconds later, the radar targets merged. The helicopter pilot stated that she received and complied with the traffic advisories by performing a visual scan but that, based on her communications with the air traffic controller, she did not perceive the situation to be urgent. Radar data revealed that the helicopter descended 600 feet before the collision but that the pilot did not inform the air traffic controllers about the descent. Further, as the airplane got closer and the traffic advisories were issued, the helicopter pilot began turning north, which brought the helicopter directly into the path of the approaching airplane while simultaneously placing the airplane behind her immediate field of vision. Shortly after, she sighted a silhouette of the airplane and propeller at her 4-o'clock position. She performed an evasive maneuver to the left but then felt the helicopter being struck. Neither the airplane pilot nor the occupant observed another aircraft near the airplane before the collision. Although the airplane pilot was not receiving traffic advisories from ATC, it was still the pilot's responsibility to maintain a proper visual lookout to avoid other aircraft in the area. The helicopter's left navigation light was inoperative when tested after the accident; however, this most likely did not affect the outcome because the left side of the helicopter would not have been visible to the airplane pilot at any point during the flight.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record for the Robinson Helicopter R22 BETA from the NTSB's investigation tables, in plain English

What happened, in order

  1. Midair collision during enroute (cruise) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during emergency descent

The NTSB's findings

  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
  • factor Personnel issues › Action/decision › Action › Lack of action › ATC personnel

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instructor: airplane single-engine; instrument: airplane
  • Flight time: 1,700 hours in all; 71 in this make and model; 39 in the last 90 days; 19 in the last 30 days; 1,548 as pilot in command; 173 on instruments
  • Medical certificate: Class 1
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,787 hours
  • Last inspection: annual inspection, February 16, 2012; 10 hours since
  • Maximum gross weight: 1,370 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-360 SERIES (piston); 1,587 hours total

The flight

  • Departed from: HWD Hayward CA at 2:15 am
  • Destination: SAC Sacramento CA
  • Flight plan: none

Weather at the time

  • Light: night
  • Wind: from 290° at 7 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 46°F (8°C), dew point 37°F (3°C)
  • Altimeter: 30.07 inHg
  • Observation at 2:53 am from KLVK, 22 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

The factual record for the Beech 35-A33 from the NTSB's investigation tables, in plain English

What happened, in order

  1. Midair collision during enroute (cruise) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during emergency descent

The NTSB's findings

  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
  • factor Personnel issues › Action/decision › Action › Lack of action › ATC personnel

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 668 hours in all; 266 in this make and model; 11 in the last 90 days; 6 in the last 30 days; 612 as pilot in command
  • Last flight review: March 22, 2011
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,830 hours
  • Last inspection: annual inspection, December 12, 2011; 9 hours since
  • Maximum gross weight: 3,000 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Cont Motor IO-470 SERIES (piston); 0 hours total

The flight

  • Departed from: C83 Byron CA at 2:35 am
  • Destination: C83 Byron CA
  • Flight plan: none

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Other NTSB records under N7508Y the same tail number, which may have belonged to a different aircraft at the time

2007-07-31DEN07CA131 · accident near Erie, CO · substantial damage · no injuries

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.