NYC02LA067 · Brantly Helicopter B-2
Brantly Helicopter B-2 · Accident: in flight collision with object while maneuvering
From Grove City, OH (no airport) to No airport
Event
- NTSB case
- NYC02LA067
- 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
Brantly Helicopter B-2
- Aircraft type
- Brantly B-2
- 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
- N2128U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Grove City, OH (no airport)To No airport
- 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 · hover
- 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
- In flight collision with object
- 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
- Pilot in command › Compensation for wind conditions, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
As the helicopter lifted off of the portable landing pad, a gust of wind began to push the helicopter backwards towards a hangar. The pilot raised the collective and the helicopter rose above the hangar; however, it continued in a rearward direction until the main rotor blades struck a tree. The pilot "rolled off" the power, and the helicopter began to descend to the ground. During the decent, the landing skid caught a vine, which rolled the helicopter inverted before it impacted the ground. The wind reported at a nearby airport, about the time of the accident, were from 220 degrees at 10 knots.
Probable cause
The pilot's inadequate compensation for wind conditions which resulted in an in-flight collision with trees. A factor related to the accident was the gusting wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA067
- Event ID
- 20020315X00349
- Case number
- NYC02LA067
- 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: ed51a03d74236c6451b5a3b0fb9c31cd05979b8d1e5e3e2d7559031a7047b438; retrieved 2026-09-21T19:46:10.352Z.