# Accident 20000122008879A: Robsin R22BETA, Piru, CA, January 22, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 22, 2000, 13:15 local time
- Place: Piru, CA
- Damage: Substantial damage
- Phase of flight: To Vertical (Helicopter Only)
- Operating rules: General operating rules (Part 91)
- Location: 34.4295° N, 118.7501° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=34.4295&lon=-118.7501&mi=10
- Aircraft: N4072T, a cancelled registration (https://openairdocs.org/deregistered/N4072T-2003-09-19) (OpenAirDocs)
- Registry model: Robinson Helicopter R22 BETA (registry code 7640110, https://openairdocs.org/model/robinson-helicopter-r22-beta) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: ROBSIN R22BETA
- Reported engine: LYC O320B2C
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 800 total, 200 in the last 90 days
- NTSB investigation: [NTSB LAX00LA079](https://openairdocs.org/ntsb/LAX00LA079) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000122008879A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) FOLLOWING A LANDING IN THE SANDY RIVER BOTTOM IN THE PIRU PRACTICE AREA (SANTA CLARA RIVER NEAR PIRU, CA) AND DURING THE ENSUING LIFT-OFF, THE PILOT, CONCERNED ABOUT A LOW FLYING FIXED WING IN THE AEA, WAS PLANNING A 90 DEGREE RIGHT PEDAL TURN TO CHECK FOR FOR THE TRAFFIC WHEN HE EXPERIENCED A DYNAMIC ROLLOVER TO THE RIGHT. THE PILOT FOUND NOTHING BUT SAND NEAR THE SKIDS FOLLOWING THE ACCIDENT. THIS WAS NOT AN INSTRUCTIONAL FLIGHT. (.4)ON JANUARY 22, 2000, ABOUT 1315 HOURS PACIFIC STANDARD TIME, A ROBINSON R22B HELICOPTER, N4072T, SUSTAINED SUBSTANTIAL DAMAGE WHEN IT ROLLED OVER ON DEPARTURE FROM A DRY RIVERBED NEAR PIRU, CALIFORNIA. GROUP 3 AVIATION OPERATED THE RENTED HELICOPTER UNDER THE PROVISIONS OF 14 CFR PART 91. THE CERTIFIED FLIGHT INSTRUCTOR AND STUDENT WERE NOT INJURED. THE LOCAL INSTRUCTIONAL FLIGHT DEPARTED VAN NUYS, CALIFORNIA, ABOUT 1145. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AND NO FLIGHT PLAN WAS FILED. THE INSTRUCTOR STATED HE TOOK HIS FIANCE UP TO INTRODUCE HER TO HELICOPTER OPERATIONS. AFTER COMPLETING TRAINING THEY CLIMBED TO ALTITUDE TO OVERVIEW THE RIVER VALLEY BEING USED AS A PRACTICE AREA, THEN DESCENDED BACK DOWN. THEY OBSERVED AN AIRPLA        NE FLYING LOW THROUGH THE VALLEY, SO THE HELICOPTER LANDED IN THE RIVERBED TO WAIT FOR THE TRAFFIC TO CLEAR. AFTER A FEW MINUTES THE INSTRUCTOR PREPARED TO LIFTOFF. AS HE LIFTED OFF, THE RIGHT SKID STAYED IN CONTACT WITH THE GROUND AND THE HELICOPTER CONTINUED TO ROLL OVER TO THE RIGHT.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX00LA079](https://openairdocs.org/ntsb/LAX00LA079), Jan 22, 2000: Robinson R22B (N4072T), Piru, CA, substantial damage. Probable cause: Failure of the pilot to maintain control after encountering a dynamic rollover.

## Other reports on N4072T (2)

Matched to the same aircraft by N-number and date.

- [Accident 20020702013979A](https://openairdocs.org/incident/20020702013979A), Jul 2, 2002: Robsin R22BETA (N4072T), Chatsworth, CA, Substantial damage. (.19) On July 02, 2002, at 1445 pacific daylight time, a Robinson R22 beta helicopter, N4072T, was substantially damaged following a loss of control during a…
- [Accident 19930311004959A](https://openairdocs.org/incident/19930311004959A), Mar 11, 1993: Robsin R22BETA (N4072T), Folsom, CA, Substantial damage. High steep approach flared. Rotor RPM decayed. Landed hard bounced into air. Rolled over on second touchdown.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.