FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL04LA155 · Robinson Helicopter Co. R44 II

28 Jul 2004 · Goldsboro, NC, United States

Robinson Helicopter Co. R44 II · Accident: roll over during landing

From Emerald Isle, NC (private airstrip) to Goldsboro, NC (private airstrip)

Report a problem

Event

NTSB case
ATL04LA155
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
0 · 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
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

Robinson Helicopter Co. R44 II

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
N442RD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Emerald Isle, NC (private airstrip)To Goldsboro, NC (private airstrip)
Aircraft age
Not recorded
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
Landing
First occurrenceThe 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
Roll over
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

  • Pilot in command › Proper touchdown point, not obtained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

According to the pilot, he executed a landing on a concrete helipad that was elevated approximately six inches above the ground. He stated the helicopter touched down slightly off center, and he attempted to reposition the helicopter on the pad. The pilot stated that, during repositioning, the rear of the skids went off the rear of the pad, the helicopter tilted backward, and the tail rotor struck the ground. Examination of the accident site revealed the concrete helipad was approximately 13 feet long and 13 feet wide, and the width between the helicopter's skids was seven feet. Examination of the helicopter revealed the ninety-degree gearbox was separated, the tail rotor was separated and fragmented, and the lower portion of the vertical fin was crushed. The pilot reported no mechanical malfunction with the helicopter.

Probable cause

The pilot's failure to obtain the proper touchdown point during landing on a helipad with an exposed edge, which resulted in an in-flight collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL04LA155
Event ID
20040824X01271
Case number
ATL04LA155
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 7029fe850f598b9b8fe17ece11932effb965f503e478ba483fe14d4c431df21f; retrieved 2026-09-22T06:57:44.148Z.