FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA09CA138 · MD Helicopter Inc 369E

20 Jan 2009 · Atlanta, GA, United States

City of Atlanta Police Department MD Helicopter Inc 369E · Accident while standing

From Hartsfield Jackson Atlanta International Airport (ATL) to Hartsfield Jackson Atlanta International Airport (ATL)

Report a problem

Event

NTSB case
ERA09CA138
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

MD Helicopter Inc 369E

Aircraft type
MD Helicopters 369
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
N369PD
Onboard fatalities
Unknown
Route
From Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GATo Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GA
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
Standing · engine(s) operating
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
Miscellaneous/other
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

  • Environmental issues › Conditions/weather/phenomena

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The helicopter pilot was informed before landing about the wind direction and velocity (330 degrees at 18 knots with gusts to 28 knots). After an uneventful landing he began shutdown of the helicopter. He applied down collective and friction, and following a 2-minute cooldown period for the engine he closed the throttle and guarded the cyclic control. When the main rotor was at 200 rpm, he felt a wind gust from the right side of the helicopter and then heard a loud sound. He applied the rotor brake and exited the helicopter after the main rotor blades stopped. At that time he noted damage to the main rotor blades and also to the tailboom.

Probable cause

Wind gusts during engine shutdown, which resulted in the main rotor blades contacting the tailboom.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09CA138
Event ID
20090122X82054
Case number
ERA09CA138
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. 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: 83a7d9f27ad16825a42ad914c9f60badbdecf2bf8226872ab775f17a8d95b48c; retrieved 2026-09-15T10:42:34.162Z.