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

Robinson R22 Beta II and Robinson R44 mid-air collision near Torrance, California, November 6, 2003

On November 6, 2003 at about 11:28 pm local time, 2 aircraft, Robinson R22 Beta II (N206TV) and Robinson R44 (N442RH), were involved in a mid-air collision near Torrance, California (Zamperini Field). 2 people were killed and 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

the student pilot in the R22's failure to comply with an ATC clearance.
the failure of the pilot of the R22 to comply with an ATC clearance.

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

What the record shows

Date
November 6, 2003 · about 11:28 pm local time
Place
Torrance, California · Zamperini Field · map
Type
Accident · mid-air collision
Injuries
2 people were killed and 1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft 1
Robinson R22 Beta II · all R22 Beta IIs on the register
Registration
N206TV · registry record · serial 2753
Damage
Destroyed
Flight
Instructional flight · general aviation rules (Part 91)
Aircraft 2
Robinson R44 · all R44s on the register
Registration
N442RH · no longer on the register · serial 0002
Damage
Destroyed
Flight
Instructional flight · general aviation rules (Part 91)

The NTSB's narrative for the Robinson R22 Beta II final · quoted from the NTSB record

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.

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 Robinson R44 final · quoted from the NTSB record

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.

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 R22 Beta II from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: student
  • Flight time: 32 hours in all; 32 in this make and model; 32 in the last 90 days; 16 in the last 30 days; 1 as pilot in command
  • Medical certificate: Class 1
  • Seat: rgt
  • Injury: serious injuries

The aircraft

  • Airframe total time: 2,974 hours
  • Last inspection: 100-hour inspection, October 1, 2003; 23 hours since
  • Maximum gross weight: 1,370 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming 0-360-J2A (piston); 0 hours total

The flight

  • Departed from: TOA Torrance CA at 10:42 pm
  • Flight plan: none
  • Runway 29L, 3,000 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 290° at 8 knots
  • Visibility: 15 statute miles
  • Sky: a few clouds at 25,000 ft
  • Temperature: 70°F (21°C), dew point 45°F (7°C)
  • Altimeter: 30.01 inHg
  • Observation at 10:50 pm from KTOA

Injuries

FatalSeriousMinorNone
Crew1

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

Flight instructor

  • Certificate: flight instructor, commercial pilot
  • Ratings: instructor: helicopter; instructor: instrument helicopter; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 8,900 hours in all
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

Dual student

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane; rotorcraft: helicopter
  • Flight time: 370 hours in all; 52 in this make and model
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: rgt
  • Injury: fatal

The aircraft

  • Airframe total time: 1,046 hours
  • Last inspection: 100-hour inspection, July 1, 2003; 74 hours since
  • Maximum gross weight: 2,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming 0-540-F1B5 (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: TOA Torrance CA at 10:49 pm
  • Flight plan: none
  • Runway 29L, 3,000 ft by 75 ft
  • A second pilot was aboard

Injuries

FatalSeriousMinorNone
Crew2

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.

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.