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

Robinson Helicopter R44 accident near De Kalb, Texas, March 11, 2023

On March 11, 2023 at about 9:30 pm local time, a 2008 Robinson Helicopter R44, registered N4164T, was substantially damaged in an accident during maneuvering (low-alt flying) near De Kalb, Texas (N/A airport). It was an aerial observation flight under general aviation rules (Part 91). 1 person was seriously injured and 1 person had minor injuries; 2 others were unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s inability to maintain control of the helicopter due to his failure to maintain rotor speed. Contributing to the accident was the failure of the helicopter’s low rotor speed warning system.

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

What the record shows

Date
March 11, 2023 · about 9:30 pm local time · cases in 2023
Place
De Kalb, Texas · N/A · map
Type
Accident
Injuries
1 person was seriously injured and 1 person had minor injuries; 2 others were unhurt.
Weather
visual conditions (good weather)
Aircraft
Robinson Helicopter R44, built 2008 · all R44s on the register
Registration
N4164T · no longer on the register · serial 1882
Damage
Substantial damage
Flight
Aerial observation flight · general aviation rules (Part 91)

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

The flight was conducted to hunt feral hogs. The pilot reported that a group of hogs had entered a large field, and he lowered the collective to maneuver the helicopter closer. When he lowered the collective, he perceived a loss of engine and rotor speed. The helicopter immediately began to lose lift. Once the pilot realized that he could not recover the helicopter, he attempted a running (skid-on) landing. However, the landing skids got stuck in the muddy field, the helicopter rocked forward, and the main rotor blades struck the ground causing the aircraft to roll over. The pilot reported the low rotor speed warning did not activate when the rotor speed started to decay. He also stated that all required preflight checklists were complied with before the flight began and no anomalies were noted. A postrecovery examination was unremarkable with exception of the low rotor warning system, which was not operational at the time of the examination. Specifically, the warning system did not activate when the collective control was brought off the low pitch stop and increased to full travel. The reason for the failure of the low rotor warning system was not 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. Collision with terrain or object (not controlled flight into terrain) during emergency descent
  2. Loss of control in flight during maneuvering (low-alt flying) defining event
  3. Sys/Comp malf/fail (non-power) during maneuvering (low-alt flying)

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft systems › Indicating/recording systems › Central warning › Inoperative other cases naming the instruments and avionics

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane; rotorcraft: helicopter
  • Flight time: 1,972 hours in all; 355 in this make and model; 135 in the last 90 days; 70 in the last 30 days; 1,750 as pilot in command
  • Last flight review: November 2, 2022
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: rear
  • Injury: no injuries

The aircraft

  • Airframe total time: 2,065.3 hours
  • Last inspection: annual inspection, December 10, 2022; 16.9 hours since
  • Maximum gross weight: 2,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-540-F1B5 (piston); 2,065 hours total
  • Operator: Hotel Sierra Aviation LLC

The flight

  • Departed from: PVT Haworth OK at 9:00 pm
  • Destination: PVT Haworth OK
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 190° at 8 knots
  • Visibility: 9 statute miles
  • Sky: broken clouds at 2,700 ft; scat at 2,000 ft
  • Temperature: 72°F (22°C), dew point 63°F (17°C)
  • Altimeter: 29.62 inHg
  • Observation at 3:53 pm from KTXK, 31 miles away

Weather report (METAR): METAR KTXK 112153Z 19008KT 9SM SCT020 BKN027 OVC036 22/17 A2962

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers111

Photographs from the investigation 8 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

10 documents, released by the NTSB on January 2, 2025. 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/CEN23LA130.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.