Mid-air collision Accident Robinson R22 Beta II N206TV,
ASN logo
ASN Wikibase Occurrence # 45026
 
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:Thursday 6 November 2003
Time:15:28
Type:Silhouette image of generic R22 model; specific model in this crash may look slightly different    
Robinson R22 Beta II
Owner/operator:Pacific Coast Helicopters
Registration: N206TV
MSN: 2753
Year of manufacture:1997
Total airframe hrs:2974 hours
Fatalities:Fatalities: 2 / Occupants: 1
Aircraft damage: Destroyed
Category:Accident
Location:Zamperini Field, Torrance, California -   United States of America
Phase: Landing
Nature:Training
Departure airport:Torrance, CA (TOA)
Destination airport:
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
A Robinson R22 Beta II and a Robinson R44 collided in midair while in the traffic pattern. The R22 pilot did not broadcast that he was a student pilot, and the controller did not think that the R22 pilot was a student pilot based on the quality of his radio transmissions. The R22 pilot had been practicing at a helipad north of runway 29R, and was returning to his parking area on the ramp south of runway 29L. The R44 pilot was departing from runway 29L on a touch-and-go. The R22 was above the R44, and descending to the southwest while the R44 was climbing straight ahead on runway 29L at the time of the collision. A tower controller instructed the R22 pilot to hold when he requested to go from the helipad to parking. After traffic passed, the controller advised him that he could proceed in right traffic flying a downwind traffic pattern for runway 29R to the helipad. The R22 pilot requested takeoff to land at his parking area. The controller instructed him to fly westbound. A few seconds later, the controller cleared the R44 pilot for the touch-and-go option on runway 29L, and in the same transmission cleared the R22 pilot to make a right turn to the downwind on runway 29R. About 45 seconds later, the controller informed the R22 pilot that he could expect a clearance to cross midfield when the controller got a chance. About 20 seconds later, the controller instructed the R22 pilot to turn right. About 30 seconds after that, he cleared the R22 pilot to land on runway 29R; the R22 pilot acknowledged about 5 seconds later with his call sign. The controller immediately transmitted for him to turn right, and cleared him to land on runway 29R. There was no further communication from the R22 pilot. The R22 was still in a position to turn and land on runway 29R. It began a right turn, but then instead of landing on the runway, it crossed 29R and continued descending toward 29L at a continuously reducing angle. The controller had looked away to work other traffic. As he turned to inform the R44 of the R22 landing on the parallel runway, he observed the collision. Reconstruction of the collision geometry placed the R22 above and slightly forward of the R44, and on a similar track. Based on a visibility study, once the R22 pilot turned toward his pad while he was north of runway 29R, he was not in a position to see the R44. During the takeoff, the R44 pilot was not in a position to see the R22 prior to impact.
Probable Cause: the student pilot in the R22's failure to comply with an ATC clearance.

Sources:

NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20031119X01921&key=1
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=206TV

Location

Revision history:

Date/timeContributorUpdates
28-Oct-2008 00:45 ASN archive Added
27-Sep-2016 22:03 Dr.John Smith Updated [Time, Total occupants, Other fatalities, Location, Departure airport, Destination airport, Source, Narrative]
21-Dec-2016 19:24 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
08-Dec-2017 20:22 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:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org