WPR10TA016 · MD Helicopter 600 N
Department of Homeland Security MD Helicopter 600 N · Accident: hard landing
From Brown Field Municipal Airport (SDM) to Gillespie Field (SEE)
Event
- NTSB case
- WPR10TA016
- 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
- Government
- 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 600 N
- Aircraft type
- MD Helicopters 600
- 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
- N613BP
- Operator
- Department of Homeland Security
- Onboard fatalities
- Unknown
- Route
- From Brown Field Municipal Airport (SDM), San Diego, CATo Gillespie Field (SEE), San Diego, CA
- 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
- Public Aircraft
- 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 · flare/touchdown
- 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
- Hard landing
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot-in-command (PIC), he was performing autorotations at the lower part of the main rotor rpm green arc in part due to weight considerations. Upon entering the accident autorotation, he maintained an airspeed between 85-90 knots in the hope that extra speed would allow a more aggressive deceleration flare prior to touchdown, which should in turn further slow the rate of descent and forward speed. The helicopter's rate of descent was high, and as the PIC turned the helicopter onto the runway heading it was apparent to him that the rate of descent was excessive and that he was too low to execute either a proper deceleration flare or perform a power recovery. He attempted to level the helicopter as much as possible prior to impact to minimize the damage to the helicopter and prevent injury. The helicopter landed hard with the left skid contacting the runway first. The left skid collapsed, damaging the outboard landing gear damper attachment structure. The helicopter slid about 100 yards before coming to a stop. According to the manufacturer, the main rotor rpm range is 90 percent to 106.4 percent. At the helicopter's weight and the density altitude on the day of the accident, the main rotor rpm during the autorotation should have been above the 106.4 percent limit (red line), requiring the pilot to increase collective pitch to maintain the rotor rpm within limits. Performing autorotations at the lower part of the green arc provides less availability of rotor energy to perform an autorotation landing. The pilot should have recognized that he was not achieving the required main rotor rpm for the autorotations and terminated the maneuvers. The helicopter was within weight and balance limits.
Probable cause
The pilot's failure to maintain adequate main rotor rpm during an autorotation, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10TA016
- Event ID
- 20091013X04846
- Case number
- WPR10TA016
- 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: d32324c1305a35e4ebc24ed2cc257c45a7160fa4552ccca06e6e7f25def5d7d0; retrieved 2026-09-15T13:24:09.128Z.