ASN Wikibase Occurrence # 143865
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Sunday 19 February 2012 |
| Time: | 18:45 |
| Type: |  Beechcraft 35-A33 Debonair |
| Owner/operator: | Private |
| Registration: | N433JC |
| MSN: | CD-351 |
| Fatalities: | Fatalities: 0 / Occupants: 1 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Near Antioch, south of Rio Vista Municipal Airport - O88, Rio Vista, C -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Byron, CA (C83) |
| Byron, CA (C83) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Probable Cause: 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.
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 19-Feb-2012 22:13 | Geno | Added |
| 20-Feb-2012 04:17 | RobertMB | Updated [Aircraft type, Registration, Cn, Operator, Total occupants, Phase, Nature, Source, Damage, Narrative] |
| 02-Mar-2012 11:40 | Geno | Updated [Time, Location, Phase, Source, Narrative] |
| 21-Dec-2016 19:26 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 27-Nov-2017 20:19 | ASN Update Bot | Updated [Total occupants, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation