ERA24FA003 · Bell Helicopter Textron Canada 407
Bell Helicopter Textron Canada 407 · Accident: loss of control in flight during initial climb
From Croydon, NH (no airport) to Quonset State Airport (OQU)
Event
- NTSB case
- ERA24FA003
- 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
- 1 · all aircraft and ground
- Ground fatalities
- 0
- 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
Bell Helicopter Textron Canada 407
- Aircraft type
- Bell 407
- 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
- N802JR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Croydon, NH (no airport)To Quonset State Airport (OQU), North Kingstown, RI
- Aircraft age
- About 14 years (built 2009)
- 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
- Initial climb
- 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
- Loss of control in flight
- 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
- Aircraft › Aircraft systems
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Experience/knowledge
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The accident flight, a night visual flight rules positioning flight, originated at an off-airport landing site the pilot had landed the helicopter at two days before the accident. An onboard image recorder captured the accident flight, which was the first flight of the day for the pilot. The video revealed that after a normal preflight inspection and run-up, the pilot initiated a near-vertical (straight-up) takeoff. Shortly after takeoff, the pilot stated aloud that it was too dark, and the helicopter began flying in an uncoordinated manor. The pilot continued the climb and accelerated forward, and the helicopter entered multiple unusual attitudes, with the primary flight display (PFD) indicating that the helicopter was in an extreme nose-down, right-bank attitude. The PFD displayed multiple visual warnings prompting the pilot to correct the unusual attitude. The pilot made large cyclic applications during the maneuvers, continued to verbally express confusion, and the engine torque/power was increased to its maximum. The helicopter then entered a descending right turn for 15-20 seconds. Shortly before impact, an aural alert for terrain was sounded, red chevrons on the PFD continued to display, and the helicopter’s spotlight began illuminating the dark forest below. The video stopped recording about one second after trees were observed in the pilot’s windscreen. Postaccident examination of the helicopter revealed no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. Based upon the flight track data, onboard image recorder data, and astronomical data, the pilot initiated a visual flight rules flight into dark nighttime conditions over featureless terrain, which likely prevented the pilot from using visual references to the horizon. The pilot’s expressed confusion and large cyclic applications were likely the result of the pilot experiencing spatial disorientation. The onboard image recorder captured the pilot increasing the instrumentation and display lighting during the preflight inspection and he did not dim the instrumentation lighting before or during flight. Guidance from the FAA Helicopter Flying Handbook advises pilots to dim cockpit lighting for night operations to better identify outside terrain and hazard details. The guidance further outlined that taking off with cockpit lights that are too bright could cause reflections or glare off the windscreen, further reducing a pilot’s ability to fly by reference to the horizon outside. The pilot’s cockpit lighting settings likely contributed to the spatial disorientation. The pilot had available for his use an autopilot and stability augmentation system (HeliSAS) to help prevent the helicopter from entering unusual attitudes, in addition to helping the pilot exit an unusual attitude; however, the SAS mode was not engaged and remained in a standby mode for the entire flight. The SAS could have been engaged at the airspeed and altitudes through which the pilot was flying during accident flight. Review of the pilot’s experience found that an overwhelming majority of the pilot’s flight experience in the last 12 months was during daylight. Although, the operator did not record, nor where they required to record night currency, the pilot’s actions regarding lighting settings, his statement that it was “too dark,” and the ultimate loss of control due to spatial disorientation, likely indicate the pilot was not sufficiently current/proficient to fly the helicopter at night. The pilot had atherosclerotic and hypertensive cardiovascular disease that placed him at increased risk of a sudden impairing or incapacitating cardiovascular event. However, video evidence was not consistent with such an event occurring. Thus, it is unlikely that the pilot’s medical conditions contributed to the accident.
Probable cause
The pilot’s loss of control during the initial climb in dark night conditions due to spatial disorientation, which resulted in a steep banking descent into trees and terrain. Contributing to the accident was the pilot’s lack of recent night flight experience, improper cockpit lighting settings, and his failure to use the helicopter’s stability augmentation system before and during the unusual attitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24FA003
- Event ID
- 20231009193206
- Case number
- ERA24FA003
- 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, cause areas. 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: 8195b1b0330e514bea956b6c00531f4c3a76fd8e46af69ed235ceb32a2a33971; retrieved 2026-09-15T08:06:38.366Z.