# Accident 20020724018599A: Bell 206B3, Seaside, OR, July 24, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 24, 2002, 14:15 local time
- Place: Seaside, OR
- Damage: Substantial damage
- Operating rules: General operating rules (Part 91)
- Location: 45.8850° N, 123.6033° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=45.8850&lon=-123.6033&mi=10
- Aircraft: N60PH, registered now (https://openairdocs.org/aircraft/N60PH) (OpenAirDocs)
- Registry model: Bell 206B (registry code 1181511, https://openairdocs.org/model/bell-206b) (OpenAirDocs)
- Registry engine: Allison 250-C20 series (registry code 03020, https://openairdocs.org/engine/allison-250-c20-series) (OpenAirDocs)
- Reported make and model: BELL 206B3
- NTSB investigation: [NTSB SEA02LA137](https://openairdocs.org/ntsb/SEA02LA137) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020724018599A

## Narrative

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

(-23) ON JULY 24, 2002, APPROXIMATELY 1415 LOCAL TIME, N60PH WAS TRAVELING ENROUTE SEASIDE, OREGON FROM CHELHAM, OREGON. THE PILOT STATED THAT HE WAS AT 2500 FEET ASL AT 110 MPH WHEN HIS PILOT WINDSHIELD EXPLODED. PARTIAL FRAGMENTS BLEW INTO THE PILOT AND THE REMAINING FRAMENTS BLEW OUTWARDS. HE THEN LOST CONTROL OF THE HELICOPTER, GOING INTO A RIGHT HAND SPIN. HE REGAINED CONTROL ABOUT 500 AGL, LANDING AT THE CLOSEST FIELD. POINT OF LANDING IS NEAR ELSIE, OREGON. PRELIMINARY INVESTIGATION REVEALED THAT THE WIRE CUTTER INSTALLED ON TOP OF THE CABIN HAD BEEN STRUCK BY THE MAIN ROTOR BLADES. ALSO, THE WIRE CUTTER BASE MOUNT HAD BEEN SHIFTED BY EVIDENCE OF THE POTTING AND PAINT CRACKING ON THE EDGE OF THE MOUNT. THE WIRE CUTTER WAS BENT IN THE LEFT DIRECTION FOLLOWING THE DIRECTION OF THE MAIN ROTOR BLADES. THE CO-PILOTS WINDSHIELD WAS ALSO BROKEN AT THE TOP OF THE WINDSHIELD NEXT TO THE WIRE CUTTER. THE WINDSHIELD PIECE FORCED INWARD AS IF THE WIRE CUTTER BASE HAD SHIFTED AND FORCED THE WINDSCREEN TO BREAK INWARD. BOTH VOR ANTENNAS MOUNTED ON TOP OF THE CABIN NEXT TO AND RIGHT BEHIND THE WIRE CUTTER ARE BROKEN OFF AT THE BASE MOUNT. INSPECTION OF THE PILOTS WINDSHIELD SHOWED NO DEBRIS TO INDICATE A BIRD OR FOD STRIKE. RETRIEVAL OF THE REMAINING PIECES VISUALLY SHOWS NO IMPACT DAMAGE. THE TOP WINDOW FRAME IS SLIGHTLY DEFORMED UPWARDS AS IF THE WIRE CUTTER, WHEN STRUCK BY THE BLADES, HAD PULLED THE FRAME IN THE UPWARD DIRECTION, GIVING THE IMPRESSION OF THE PILOTS WINDOW BEING BROKEN BY THE MOVEMENT OF THE WIRE CUTTER WHEN STRUCK BY THE MAIN ROTOR BLADES. INSPECTION OF THE MAIN ROTOR BLADES SHOW A GOUGE AT THE SAME DISTANCE FROM THE MAIN GEAR BOX MAIN ROTOR SHAFT TO THE WIRE CUTTER POSITION GIVING THE INDICATION OF BEING GOUGED BY THE WIRE CUTTER. SECONDARY INDICATIONS AREA ON THE MAIN ROTOR SHAFT SHOWING SIGNS OF BEING STRUCK BY THE MAIN ROTOR DROOP STOP STRIKE PLATE BY THE BARE METAL ON THE STRICK PLATE AND THE TRANSFERENCE OF PAINT TO THE ROTOR SHAFT. ALSO, THE MAIN GEARBOX SPIKE SHOWS SIGNS OF STRIKING AGAINST THE SPIKE BOX BY THE BARE METAL ON THE SIDES OF THE SPIKE AND THE SPIKE BOX. INSPECTION OF THE MAIN GEAR SKIDS SHOWS NO SIGN OF HARD LANDING.

## 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 SEA02LA137](https://openairdocs.org/ntsb/SEA02LA137), Jul 24, 2002: Bell 206B (N60PH), Elsie, OR, substantial damage. Probable cause: The shattering and separation of the forward right (pilot's) windscreen for undetermined reason(s).

## Other reports on N60PH (1)

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

- [Incident 19980716029619I](https://openairdocs.org/incident/19980716029619I), Jul 16, 1998: Bell 206B (N60PH), Ketchikan, AK, Minor damage. Pilot error, blade strike during landing into confined area. Local tracking number: IAL05980004

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.