RotorAlert
Incidents🇷🇺 Russia2016-02-24
Incident report

Enstrom F-28 crash near Globitsy, Russia

fatal2016-02-241 fatality
Summary

On February 24, 2016, about 1754 hours local, an Enstrom F-28A, RA-2348G, registered to the City of Saint-Petersburg, Russia, operated by a private individual, impacted terrain near Globitsy Township, Lomonosov District, Leningrad Region, Russia. Visual meteorological conditions prevailed at the time and flight plan information is unknown for the non-US, non-commercial other work use flight. The helicopter was substantially damaged, and the private pilot was fatally injured while the passenger sustained minor injuries. The flight originated about 1637, from a location about 13 nautical miles east-southeast of the accident site location. The helicopter departed with an adequate supply of fuel but with a non-certificated helicopter pilot at the controls. After takeoff during an aerial search for a stolen vehicle while flying at or below 60 meters, the passenger later reported that the engine lost power. The helicopter subsequently crashed in a field with evidence of high vertical descent rate. Postaccident examination of the fuel system revealed the left fuel drain was inoperative, and ice was found in the left fuel tank. The investigation is under the jurisdiction of the Interstate Aviation Committee. Further information can be obtained from: Interstate Aviation Committee 22/2/1 Bolshaya Ordynka Str. Moscow, 119017, Russia Tel: (495) 953-12-44 Fax: (495) 953-35-08 E-mail: mak@mak.ru http://www.mak.ru This report is for informational purposes and only contains information released by the Interstate Aviation Committee.

Incident details
Date
2016-02-24
Location
Globitsy, Russia
Aircraft
Registration
RA-2348G
Operator type
civil
Fatalities
1
Injuries
0
Probable cause
Weather
VMC
Source
NTSB
59.7378, 29.2275
Quick stats
Severityfatal
Fatalities1
Injuries0
SourceNTSB
Other incidents in Russia
Other Enstrom incidents
← Back to all incidents
See something wrong or have more info?
Help us improve this incident record with corrections, additional details, or sources.
Submit info
ShareX / TwitterFacebookWhatsAppLinkedIn