DEN07FA079 · Robinson R44 II
Robinson R44 II · Accident: airframe, component or system failure en route
From Jacksonville Executive at Craig Airport (CRG) to an unrecorded destination
Event
- NTSB case
- DEN07FA079
- 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
- 2 · 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 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
- N744SH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jacksonville Executive at Craig Airport (CRG), Jacksonville, FLTo not recorded
- 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
- En route · cruise
- 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Company maintenance personnel › Maintenance, installation, improper
- Pilot in command(cfi) › Aircraft control, not possible
- Rotorcraft flight control › Disconnected
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The local instructional flight was scheduled for a east departure from the airport and a flight south along the coastline. Several witnesses observed the helicopter approximately 200-500 feet above ground level (agl) in cruise flight along the coastline on a south heading. One witness, a former pilot and mechanic, reported he observed the helicopter in straight and level flight, then heard a change in "rotor noise, followed by a bang/pop/twang sound." The helicopter then "snap-rolled" to the left and descended into the terrain in a nose low attitude. Examination of the helicopter's flight control system revealed that the right forward servo to swashplate push-pull tube joint was disconnected and the attach hardware (bolt, lock nut, two washers, pal nut) was missing. The left forward servo to swashplate push-pull joint was connected; however, the nut was found partially engaged on the bolt threads, and the torque was "finger tight"; no pal nut was noted. Material analysis of the components revealed that only one of the two nuts for the left and right connections were installed, and then only finger tight. The nut on right servo connection rotated off during flight which allowed the bolt to extract itself and disconnect the servo from the push-pull tube. Prior to the accident flight, an inspection, which required the push-pull tubes to servo connections to be disassembled, was performed on the helicopter, and a 0.5-hour maintenance test flight. The mechanic who preformed the inspection, stated he forgot to properly secure the hardware for the left and right servo connections. The mechanic stated the reasons for the error were the following: 1. He was pulled," in all directions" by company personnel since his arrival at that facility; 2. The "reassembly was not opposite of the disassembly," which was a personal maintenance practice he used to eliminate errors; 3. Two nights prior to the completion of the inspection and the maintenance test flight, the apprentice providing assistance, wanted to stay late to finish with the mechanic a certain section of the inspection. As a result, the mechanic forgot to go back and secure the hardware connecting the two push-pull tube to servo joints; 4. The company was understaffed with maintenance personnel. According to the company's maintenance quality control program, any maintenance completed on a helicopter was to be inspected by another mechanic. A review of the program revealed that the mechanics were not following the program, and the company was not providing oversight and enforcing the program.
Probable cause
the mechanic's improper installation of the attachment hardware for the servo to swashplate push-pull tube joint which resulted in a disconnection, subsequent loss of control, and impact with terrain. Contributing factors were the company management's inadequate surveillance and enforcement of maintenance procedures, the excessive maintenance workload due to inadequate staffing of maintenance personnel, and the insufficient management of maintenance tasks.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN07FA079
- Event ID
- 20070405X00374
- Case number
- DEN07FA079
- 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: cef49848eba6cb296a48d2bde760a2f80a39146b672c2e314ba9d623d4afa12a; retrieved 2026-09-20T16:46:47.705Z.