Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

March 30, 2019 · Bell 222 A · N222ML

Montgomery, NY

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
March 30, 2019
Injury Outcomes
1 injury (1 minor injury), 5 uninjured
Location
Montgomery, NY
Aircraft
Bell 222 A (1982)
Tail Number
N222ML
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA19LA145

The twin-engine helicopter was about 500 ft into the initial climb after takeoff from the pilot’s private property when he noticed a “split” in the #1 and #2 engine rpm needles, with the #1 engine rpm indicating below normal operating rpm, and the #2 engine rpm indicating above normal operating rpm. The pilot believed that this was believed that this was indicative of a loss of power on the #1 engine and returned to the property for a run-on landing. The helicopter touched down, encountered uneven ground, and rolled onto its left side, which resulted in substantial damage to the airframe. Postaccident examination of the airframe found both of the throttles near the idle position, and no evidence of any preimpact mechanical malfunctions or failures of any airframe components. Both engines and their respective power turbine governors were examined and successfully test run after the accident. During the examinations, the #2 engine’s P3 Ng speed sensor connector was found disconnected. According to the engine manufacturer, if the disconnection had occurred inflight, the cockpit indication of the engine speed for the #2 engine would have been zero. Given this information, and the pilot’s description that the #2 engine rpm was abnormally high, it is likely that the disconnection of the connector occurred as a result of the accident sequence and not during the flight. Based on these findings, the reason for the difference between the indications of the two engines that the pilot observed during the takeoff could not be determined.

NTSB Probable Cause

A partial loss of engine power, as reported by the pilot, during takeoff for reasons that could not be determined based on available information.

Full Narrative

On March 30, 2019, about 1215 eastern daylight time, a Bell 222 helicopter, N222ML, was substantially damaged when it was involved in an accident near Montgomery, New York. The private pilot and four passengers were not injured, and one passenger sustained minor injuries. The helicopter was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot stated he completed the preflight inspection by the checklist, boarded passengers, and started the engines. Prior to takeoff, all gauges were in the “normal range.” The pilot conducted the takeoff from a concrete pad on his property, and about 500 ft above ground level he noticed a “split” in the #1 (left) and #2 (right) engine rpm needle indications. The #1 engine rpm needle had decreased below normal operating rpm, and the #2 needle had “spiked” above the normal operating rpm. The pilot believed there was a loss of engine power on the #1 engine, and he initiated a sharp left turn to return to his property to perform a run-on landing to a short asphalt surface in front of a utility building. According to the pilot, a strong wind pushed the helicopter left, and the left landing gear touched down in the grass that bordered a short strip of gravel, which pulled the helicopter onto uneven ground. The helicopter came to a stop, then tipped over onto its left side and the main rotor impacted the ground. After it came to rest there was a small fire underneath the helicopter. All the occupants exited the helicopter, and the fire was extinguished. The helicopter was righted to prevent a fuel leak. A Federal Aviation Administration (FAA) inspector traveled to the site and examined the helicopter. The rotor and transmission were separated and resting next to the helicopter. There was substantial damage to the nose and transmission pylon area, and fire damage to the upper portion of the fuselage aft of the number one engine. Postaccident examination found both of the throttles near the idle position. Continuity of the throttle was confirmed from the #2 engine twist grip to the respective fuel control. Continuity of the #1 throttle control could not be verified due to breaks in the linkages, though the twist grip and fuel control lever were both free to move. The airframe examination revealed no pre-impact anomalies. Both engines were removed, examined, and placed in test cells, where each ran satisfactorily. No anomalies were noted on either engine that would have precluded normal operation. During the examination, the #2 engine P3 Ng speed sensor connector was found disconnected. According to the engine manufacturer, a disconnected P3 connector could have caused the cockpit indication of the speed for the #2 engine to indicate 0 rpm. Additionally, the power turbine governors were functionally tested and exhibited no anomalies that would have precluded normal operation. The helicopter manufacturer performed one engine inoperative performance calculations based on the environmental and loading conditions of the helicopter at the time of the accident. Based on the calculations, the helicopter did not have the capability to hover in or out of ground effect, and that the flight manual advised pilots to perform a run-on landing under those conditions. The helicopter manufacturer also provided an explanation of how the helicopter’s configuration could result in the instrument indications similar to those that the pilot reported. The explanation stated that, “When the throttle for one engine on the twin engine Bell 222 is not in the fully governed range, then the affected engine will tend to droop at a lower Ng (N1) setting and not provide full engine power to the helicopter drive system. The helicopter will then in affect be flying in or near an OEI condition (One Engine Inoperative). Therefore, the pilot will see a split on the triple tachometer with the affected engine Np (N2) speed drooping and the unaffected engine Np (N2) speed stable at 100% Np. Depending on the conditions of flight (hover, landing, approach, maneuvering, cruise), outside temperature, and gross weight of the helicopter, the Nr (rotor rpm) might also droop. The remedy of having a drooping Nr would be to put the affected throttle back to the full on fully governed throttle position to regain N2 speed on the affected engine. If the pilot did not recognize the throttle was out of the governed region, a running landing to a suitable area should be performed. The engine run up checklist states the throttles should be rotated to FULL OPEN and verify Np at 97 to 100% during the engine runup and remain in that position until takeoff.”

Flight

Event TypeAccident
Event Time12:15 EDT
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireGrd
Aircraft ExplosionNo

Aircraft

AircraftBell 222 A
Tail NumberN222ML
Aircraft CategoryHeli
DamageSubstantial
Operating RulePart 91
Engines2
Engine TypeTurboshaft
Engine DetailsHoneywell · LTS-101 SER · Turboshaft · 650 | Honeywell · LTS-101 SER · Turboshaft · 650
Seats8

People & Injuries

Injury Summary1 injury (1 minor injury), 5 uninjured
Fatal0
Serious0
Minor1
Uninjured5
Total6
Crew 1Age 72 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind170° @ 13 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point64 F / 43 C
Altimeter29.95 inHg
Observation Time16:30
Weather SourceWFAC

Appendix: Source Data