The U.S. aircraft register, updated daily
Accidents · NTSB ERA22LA168 · Final report

Robinson Helicopter R44 accident near Myrtle Beach, South Carolina, March 26, 2022

On March 26, 2022 at about 9:15 pm local time, a 2000 Robinson Helicopter R44, registered N288L, was substantially damaged in an accident during initial climb near Myrtle Beach, South Carolina (Myrtle Beach International Air airport). It was an other work-use flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

Vibration in the airframe and flight controls for reasons that could not be determined based on the available evidence.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 26, 2022 · about 9:15 pm local time · cases in 2022
Place
Myrtle Beach, South Carolina · Myrtle Beach International Air · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 4 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Robinson Helicopter R44, built 2000 · all R44s on the register
Registration
N288L · registry record · serial 0930
Damage
Substantial damage
Flight
Other work-use flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot and three passengers departed for a short sightseeing tour after the helicopter had flown about 40 preceding tours on the day of the accident. The pilot reported that after takeoff about 500-700 ft above ground level (agl), he experienced a “violent shutter and shaking” of the helicopter flight controls. The pilot described the vibration as “very violent, like a brick in a [clothes] dryer, but three times more violent.” He stated that he noticed the erratic movement of the rpm on the tachometer and that the helicopter was no longer climbing. The pilot entered an autorotation to make an emergency landing in a parking lot. The vibration continued throughout the autorotation all the way to the ground; however, the pilot reported no unusual resistance, binding, or other issues with the flight controls. During the approach, he flared the helicopter and pulled the collective to cushion the landing; the helicopter landed on its skids and slid on the pavement before impacting a mound of dirt and rolling on its left side. The pilot and passengers were not injured and the helicopter sustained substantial damage to the tail boom and fuselage. A postaccident examination of the flight controls and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The examination of the engine included four successful test runs of the engine. The engine manufacturer had issued a mandatory service bulletin to mitigate an issue with sticking valves. While a stuck valve could not be ruled out, all valves moved freely during the two post-accident examinations, subsequent compression tests were not consistent with an open/stuck valve, and the maintenance records indicated that the manufacturer’s related service bulletin instructions were performed regularly. A “slight” engine vibration was reported during engine warm-up, but it smoothed out during the third and fourth engine runs. The pilot stated that he noted that the helicopter stopped climbing, which would normally associated with a loss of power. However, it’s also possible that when the violent vibrations occurred initially, the pilot inadvertently lowered the collective slightly as he tried to ascertain the reason for the vibrations and the erratic movement of the rpm on the tachometer. He likely interpreted the leveling of the helicopter’s altitude as a loss of power as he entered the autorotation due to the violent vibrations. Based on available evidence, the reason for the vibrations described by the pilot could not be determined.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Off-field or emergency landing during initial climb
  2. Unknown or undetermined during initial climb defining event
  3. Hard landing during landing

The NTSB's findings

  • Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: commercial pilot
  • Ratings: rotorcraft: helicopter
  • Flight time: 474 hours in all; 400 in this make and model; 163 in the last 90 days; 93 in the last 30 days; 434 as pilot in command
  • Last flight review: January 14, 2022
  • Medical certificate: Class 1
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,234 hours
  • Last inspection: 100-hour inspection, February 18, 2022; 83 hours since
  • Maximum gross weight: 2,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-540-F1B5 (piston); 3,318 hours total
  • Operator: Executive Helicopters INC

The flight

  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 290° at 21 knots, gusting 30
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 68°F (20°C), dew point 25°F (-4°C)
  • Altimeter: 29.67 inHg
  • Observation at 4:56 pm from MYR, 1 miles away

Weather report (METAR): KMYR 262056Z 29021G30KT 10SM CLR 20/M04 A2967 RMK AO2 PK WND 29033/2045 SLP046 T02001044 56020

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

Photographs from the investigation 5 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

9 documents, released by the NTSB on May 9, 2024. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA22LA168.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.