Mcdonnell Douglas Helicopter 369E accident near Glastonbury, Gb, June 19, 2011
On June 19, 2011 at about 2:20 pm local time, a Mcdonnell Douglas Helicopter 369E, registered GKSWI, was substantially damaged in an accident during enroute (cruise) near Glastonbury. It was a personal flight under non-U.S. private rules. 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 19, 2011 · about 2:20 pm local time
- Place
- Glastonbury, United Kingdom · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Mcdonnell Douglas Helicopter 369E · all 369Es on the register
- Registration
- GKSWI · no longer on the register · serial 0204E
- Damage
- Substantial damage
- Flight
- Personal flight · non-U.S. private rules
The NTSB's narrative preliminary · quoted from the NTSB record
On June 19, 2011, at 1420 universal coordinated time (UTC), a McDonnell Douglas Helicopter Company model 369E, United Kingdom registration G-KSWI, s/n 0204E, was substantially damaged during an emergency landing after experiencing a mechanical failure of the tail-rotor control system near Glastonbury, United Kingdom. The helicopter was substantially damaged and the pilot was seriously injured during the accident. The investigation is under the jurisdiction of the United Kingdom Government. Further information may be obtained from: Department for Transport Air Accident Investigation Branch (AAIB) Farnborough House Berkshire Copse Road Aldershot, Hampshire GU11 2HH, United Kingdom Phone: +44 (0) 1252 510300 Fax: +44 (0) 1252 376999 E-mail: investigations@aaib.gov.uk Webpage: http://www.aaib.gov.uk This report is for informational purposes only and contains only information released by or obtained from the Air Accident Investigation Branch (AAIB).
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Sys/Comp malf/fail (non-power) during enroute (cruise) defining event
- Loss of tail rotor effectiveness during enroute (cruise)
- Off-field or emergency landing during emergency descent
The NTSB's findings
- cause Aircraft › Aircraft propeller/rotor › Rotorcraft flight control › Tail rotor control system › Failure
Pilot
- Seat: left
- Injury: serious injuries
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 3,000 lb
- Landing gear: fixed
- Engine: Rolls-Royce 250-C20B (turboshaft); 0 hours total
The flight
- Departed from: Yeovilton
- Destination: Cornwall
- Flight plan: not recorded
Weather at the time
- Light: daylight
- Sky: not recorded; not recorded
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.