# Accident 20021102030459A: Bell 47G2, Pollickpines, CA, November 2, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 2, 2002, 09:10 local time
- Place: Pollickpines, CA
- Damage: Substantial damage
- Operating rules: General operating rules (Part 91)
- Location: 38.7228° N, 120.6017° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=38.7228&lon=-120.6017&mi=10
- Aircraft: N2616B, a cancelled registration (https://openairdocs.org/deregistered/N2616B-2013-08-21) (OpenAirDocs)
- Registry model: Bell-Yehnert 47G-2 (registry code 1181310, https://openairdocs.org/model/bell-yehnert-47g-2) (OpenAirDocs)
- Reported make and model: BELL 47G2
- Fatal injuries: 0
- NTSB investigation: [NTSB LAX03LA019](https://openairdocs.org/ntsb/LAX03LA019) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20021102030459A

## Narrative

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

(-23) DURING TAKE OFF HELICOPTER STRUCK BUSH AND CRASHED.

## 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 LAX03LA019](https://openairdocs.org/ntsb/LAX03LA019), Nov 2, 2002: Bell 47G-2 (N2616B), Pollock Pines, CA, substantial damage. Probable cause: The pilot's failure to maintain adequate obstruction clearance during initial climb, which resulted in a collision with vegetation.

## Other reports on N2616B (1)

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

- [Incident 20020610015879I](https://openairdocs.org/incident/20020610015879I), Jun 10, 2002: Bell 47G2 (N2616B), Sacramento, CA. (-23) Pilot stated that during a solo flight from and returning to rancho murieta airport, he observed the oil temperature rising. He contacted Sacramento…

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.