WPR12CA387 · Croman Corporation SH-3H
Croman Corporation SH-3H · Accident while maneuvering
From Round Valley Airport (O09) to Round Valley Airport (O09)
Event
- NTSB case
- WPR12CA387
- 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
- 0 · 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
Croman Corporation SH-3H
- Aircraft type
- Croman SH-3
- 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
- N611CK
- Operator
- Croman
- Onboard fatalities
- Unknown
- Route
- From Round Valley Airport (O09), Covelo, CATo Round Valley Airport (O09), Covelo, CA
- 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
- Maneuvering · low-altitude flying
- Defining eventThe 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
- Miscellaneous/other
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter was involved in firefighting operations. The pilot flying was in the left seat, and the senior pilot was in the right seat. The pilot completed numerous water drops on the fire during a 2-hour period. The helicopter was making its second drop in an area of steep terrain, which was about 1,000 feet lower in elevation than the lake the pilots were using for a water source. Due to the smoke, the visibility was about 1/2 mile. All five main rotor blades made contact with a snag (typically the remnants of a tree such as the trunk and/or main branches without most of its foliage), and were substantially damaged; the operator pointed out that the snag was similar in color to the smoke. The senior pilot took control of the helicopter, climbed, and made an uneventful landing near the fill point.
Probable cause
The pilot’s failure to maintain clearance from a tree during an aerial firefighting flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12CA387
- Event ID
- 20120903X92502
- Case number
- WPR12CA387
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: 82d459eefaedda59a82138f780e22471e76b13613ffceaebed34b8d2bf2030c3; retrieved 2026-09-15T19:39:16.886Z.