LAX04FA037 · Robinson R22 Beta II
Pacific Coast Helicopters Robinson R22 Beta II and Robinson R44 · Accident: midair collision during landing
Event
- NTSB case
- LAX04FA037
- 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
- 2 · 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 · Robinson R22 Beta II
- Aircraft type
- Robinson R22
- Category
- Helicopter
- 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
- N206TV
- Operator
- Pacific Coast Helicopters
- Onboard fatalities
- Unknown
- Route
- From Zamperini Field (TOA), Torrance, CATo not recorded
- 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
- Landing
- First occurrenceThe 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
- Destroyed
Aircraft 2 · Robinson R44
- Aircraft type
- Robinson R44
- Category
- Helicopter
- 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
- N442RH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Zamperini Field (TOA), Torrance, CATo not recorded
- 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
- Takeoff
- First occurrenceThe 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
- Destroyed
Cause areas
- Pilot in command › Atc clearance, not complied with
- Pilot of other aircraft › Atc clearance, not complied with
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB 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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04FA037
- Event ID
- 20031119X01921
- Case number
- LAX04FA037
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 924d5c03f6b1144fcc0cfa62f1f452b00e11713a9958d06b4ed9ec61e0f03f02; retrieved 2026-09-20T18:48:41.892Z.