ERA09FA419 · MD Helicopter Inc 530 (369FF)
Presidential Airways MD Helicopter Inc 530 (369FF) · Accident: low altitude operation/event while maneuvering
From Camp Butler (no airport) to Camp Butler (no airport)
Event
- NTSB case
- ERA09FA419
- 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
- 3 · 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
MD Helicopter Inc 530 (369FF)
- Aircraft type
- MD Helicopters 530
- 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
- N974BW
- Operator
- Presidential Airways
- Onboard fatalities
- Unknown
- Route
- From Camp Butler (no airport)To Camp Butler (no airport)
- 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
- Maneuvering · low-altitude flying
- Defining eventThe 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
- Low altitude operation/event
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The helicopter arrived at a military gunnery range with two pilots and two door gunners onboard. The gunnery range included an east-west track, approximately 1 mile long, with four targets just to the north of the track and three targets just to the south of it. Each target was to be engaged as it came into range, with gunfire coming from both sides of the helicopter. After engaging all of the targets along the track, the helicopter was to reverse course and commence another firing run. A total of eight tracks were flown prior to the accident: four in each direction. All of the eastbound tracks were flown by the copilot, seated in the left seat, and all the westbound tracks were flown by the pilot in command (PIC), seated in the right seat. After the completion of each track, the pilots transferred control of the helicopter and the new pilot at the controls executed the course reversal.
After the copilot had completed the final eastbound track, he transferred the controls to the PIC. The PIC then began a left-turn course reversal approximately 100 feet above the ground. The next thing the PIC remembered was that, while in the turn and “like a hazy dream,” he saw the copilot’s finger moving toward the instrument panel and, after that, “being dragged, shaken, and bumped along the ground.” The PIC stated that despite his hazy recollection, he remembered that the helicopter was operating properly, with no warnings, cautions, or changes in sound. He further noted that even though the copilot appeared to be pointing at something, the copilot did not speak or otherwise indicate that anything was wrong. There was no indication of hostile fire.
Observations at the accident site revealed that the helicopter was traveling westward at terrain impact. The initial impact point, at the eastern edge of a dried-up pond, was 17 meters in width, indicated by imprints of both skids. About 1 meter east feathered dirt indicated a spinning tail rotor. The second point of impact was on the western edge of the same dried-up pond. The distance between the first point of impact and the main wreckage was about 44 meters. The tail boom came to rest about 20 meters to the south, and about 24 meters east of that was the tail rotor.
After the wreckage was secured, it was shipped to the United States where examination revealed that the helicopter had impacted the ground in a descending left turn. Main rotor blade damage indicated flailing at impact, at operational rpm. Tail rotor blade damage also indicated that the rotor was under power at impact. Flight control continuity could not be confirmed from the cockpit to the flight control surfaces; however, continuity was confirmed at the tail rotor pitch change mechanism. The engine did not exhibit any preimpact mechanical anomalies, and interior compressor blade scoring on the engine shroud indicated that it was operating at impact.
The ENGINE OUT warning light was illuminated at some point during impact sequence; however, an expected RE-IGN P RST caution light was not concurrently illuminated for unknown reasons. It is possible that the ENGINE OUT warning light illuminated as the helicopter was decelerating while in ground contact. With no indication of mechanical failure or hostile fire, and with the PIC observing the copilot pointing to something on the instrument panel, it was possible that the PIC's attention was sufficiently diverted to allow the helicopter's inadvertent descent into terrain.
Probable cause
The pilot’s failure to maintain terrain clearance during a low-level course reversal.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09FA419
- Event ID
- 20090724X13440
- Case number
- ERA09FA419
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 1f15cab58e452a88ee8ed2330d80613de2ed74761090fa64fbc289a7b00e079e; retrieved 2026-09-13T20:23:13.298Z.