Novictor Aviation Robinson R44 accident
Robinson R44 · Accident: inflight upset while maneuvering
From Daniel K. Inouye International Airport (HNL) to Daniel K. Inouye International Airport (HNL)
Event
- NTSB case
- WPR19FA123
- 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
- 3 · 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
- Charter & commuter
- 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
Robinson R44
- Aircraft type
- Robinson R44
- 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
- N808NV
- Operator
- Novictor Aviation
- Onboard fatalities
- Unknown
- Route
- From Daniel K. Inouye International Airport (HNL), Honolulu, HITo Daniel K. Inouye International Airport (HNL), Honolulu, HI
- Aircraft age
- About 19 years (built 2000)
- 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 135: Air Taxi & Commuter
- 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
- 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
- Inflight upset
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft propeller/rotor
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and two passengers departed on a helicopter tour flight around the island. Air traffic control radar and communications information indicated that the flight encountered deteriorating visibility conditions enroute. About this time, the helicopter slowed from about 108 knots (kts) to about 92 kts and initiated a turn. Shortly thereafter, radar data then indicated a rapid descent from an altitude about 1,700 ft above ground level. Witnesses near the accident site reported hearing the helicopter in the clouds and reported that it sounded as if it was very low. They then described the sound of metal hitting metal and saw pieces of the helicopter falling from the sky. Postaccident examination of the airframe revealed that the forward left roof and floor/chin exhibited damage consistent with contact from a main rotor blade. One main rotor blade exhibited a spanwise dent which displayed equally spaced score marks consistent with the row of screws in the windshield bow. The outboard portion of one of the main rotor blades, along with left fuselage and left side cabin components, were found early in the debris path. The main rotor drive shaft was bent about 20° above the swashplate. Arc-shaped scoring was observed on both sides of the main rotor hub adjacent to the pitch horns. Both teeter stops were crushed, and the driveshaft was dented. The droop stop bolt at the nut was sheard but remained in place. Examination of the engine revealed no anomalies and the evidence indicated that the engine was operating at the time of the accident. The accident helicopter was equipped with a two-bladed, semirigid rotor system. This design is susceptible to excessive rotor blade flapping, during periods of low-G’s or the pilot’s improper application of control inputs. Excessive rotor blade flapping can result in main rotor contact with the fuselage. A manufacturer safety notice stated, in part, that, when flying in turbulence, the helicopter should be slowed below a normal cruise speed to around 60 to 70 kts. Review of weather information for the area of the accident site around the time of the accident revealed a warm, moist environment that supported heavy rain showers that could produce unexpected strong downdrafts, reduced visibilities, wet microburst, and outflow wind conditions. At the time of the accident, weather surveillance radar reflectivity values indicated a descending core of 20 to 30 dBZ values descending towards the surface from above the accident site. The accident flight likely encountered this downdraft or outflow boundary, reduced visibilities, and rapidly changing and unexpected wind conditions. Which likely caused a low-G condition, excessive main rotor flapping, and an in-flight breakup when the main rotor contacted the cabin area.
Probable cause
The helicopter’s encounter with a strong downdraft or outflow boundary while operating at a higher than recommended airspeed in turbulence which resulted in a low-G condition, excessive main rotor flapping, and an in-flight breakup when the main rotor contacted the cabin area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19FA123
- Event ID
- 20190429X61624
- Case number
- WPR19FA123
- 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: 0f300bb87351e657f152d763883fe0d26376f56063f79a71ada8097cba97c585; retrieved 2026-09-15T06:57:14.578Z.