Aeroflot Flight 3352
| Company type | State-owned airline (Soviet Union) |
|---|---|
| Industry | Aviation |
| Founded | 1923 |
| Headquarters | Moscow , Soviet Union |
Area served | Domestic routes within the Soviet Union and international destinations |
| Products | Passenger and cargo air transport |
Template:Infobox aircraft occurrence
Aeroflot Flight 3352 was a scheduled domestic route operated by Aeroflot within the Soviet Union, traveling from Krasnodar to Novosibirsk with an intermediate stop at Omsk. On Thursday, 11 October 1984, during its approach to Tsentralny Airport, the aircraft collided with maintenance vehicles positioned on the runway, resulting in the deaths of 174 individuals aboard and four persons on the ground. The accident occurred due to a series of operational errors at the airport, primarily stemming from an air traffic controller who had fallen asleep while on duty.
As of 2025[update], this incident remains the deadliest aviation disaster to have occurred on Russian soil.[1] At the time, it was also the most fatal crash involving a Tupolev Tu-154 until the tragedy of Aeroflot Flight 5143 nine months later; As of 2025[update], it continues to be the second deadliest crash associated with this aircraft model.[2][3][4][5] According to a Komsomolskaya Pravda report in 2017, this newspaper was the first to cover the accident after two decades of media silence.[6]
Background
The Tupolev Tu-154 B-1 was initially operated by Aeroflot before transitioning to East Siberia. This aircraft was powered by three Kuznetsov NK-8-2U engines and made its maiden flight in 1977.Template:Fix/category[citation needed]
Onboard were 170 passengers, including eight teenagers and 16 young children, along with 2,700 kilograms (6,000 lb) of baggage, 306 kilograms (675 lb) of mail, and 1,600 kilograms (3,500 lb) of freight. The flight crew comprised four members in the cockpit and five flight attendants. The captain, Boris Petrovich Stepanov, aged 49, possessed extensive experience with 16,365 total flying hours, which included 4,303 night hours and 1,846 hours specifically on the Tu-154.[7] The first officer was Anatoly Yachmenev, 47 years old, who had accumulated 2,748 hours on the Tu-154. The remaining cockpit personnel consisted of flight engineer Vitaly Pronozin and navigator Yuri Blazhin.Template:Fix/category[citation needed]
As the flight neared Omsk, weather conditions were unfavorable: light rain prevailed with visibility around 3 kilometres (1.9 mi; 1.6 nmi) and a cloud ceiling at approximately 100-metre (330 ft).Template:Fix/category[citation needed]
At that period, this accident represented the most fatal incident in Soviet aviation history until it was overtaken on 10 July 1985 by Aeroflot Flight 5143, another Tu-154 crash in the Uzbek SSR (present-day Uzbekistan), which resulted in 200 fatalities.[2]
Accident details
At 5 a.m. local time (UTC+07:00), Flight 3352 was preparing for landing at Omsk Central Airport, situated in southwestern Siberia. Omsk is home to over one million residents and serves as the administrative centre of Omsk Oblast. At that moment, Flight 3352 was the sole aircraft approaching Omsk and had been cleared for landing upon establishing contact with the airport.[3][5]
By 5:20 a.m., concerned that persistent rain would render the runway dangerously slick, the ground maintenance team requested authorization to dry it. The ground controller on duty, Andrey Borodaenko, aged 23, granted this permission but then fell asleep shortly afterward. Crucially, he neglected to activate the "runway occupied" warning system. According to airport protocols, such runway closure and maintenance operations required approval from the chief controller, who was not present at that time.[3][5]
Following standard procedures, the maintenance team deployed three vehicles onto the runway: a UAZ-469 all-terrain vehicle towing a trailer operated by a driver and crew chief at the front; followed by KrAZ and Ural trucks. These trucks were equipped with dry air compressors and carried fuel loads between 16 and 20 tons. However, during their work, the crew breached safety regulations by not keeping their top-mounted flashing lights continuously illuminated as required. The lights were deemed excessively bright by the workers and were only switched on during vehicle startup and shutdown phases.[3][5]
This deliberate noncompliance hindered pilots' ability to detect vehicles on the runway from their vantage point.[3][5] Although the runway crew observed that runway lights had been activated, they were not informed about any incoming aircraft. Attempts to reach ground control three times regarding the lights went unanswered; consequently, they disregarded these signals assuming it was merely a test.[3][5]
At approximately 5:36 a.m., Flight 3352 contacted approach controller Vasily Ogorodnikov twice to request landing clearance. The pilots expressed concern over indistinct shapes visible on the runway and sought confirmation that it was clear of obstacles. Ogorodnikov checked runway status indicating it was free but failed to receive any response from ground controller Borodaenko when he attempted contact. Subsequently, he reached out via internal radio to flight controller Boris Ishalov and obtained an unclear reply resembling "[...]bodna," interpreted as "svobodna" (meaning "free"). These communications were recorded and analyzed later. Despite lacking visual confirmation of a clear runway—a requirement before authorizing landing—Ogorodnikov cleared Flight 3352 to land. Both ground controllers should have monitored runway status actively; however, one was asleep,[2] while the other was absent due to staffing shortages.Template:Fix/category[citation needed]
At 5:38 a.m., having reached decision height, the aircraft touched down at a standard speed of approximately 240 km/h (130 kn; 150 mph). Upon touchdown, pilots spotted maintenance vehicles on the runway and attempted evasive maneuvers but could not prevent impact. The plane collided first with an Ural truck before continuing roughly 200 metres (660 ft) along the runway into a KrAZ truck loaded with seven tons of fuel each; this collision ignited fuel both from the trucks and aircraft tanks. The aircraft cartwheeled violently, breaking apart with debris hitting the UAZ-469 vehicle as well. A catastrophic rupture of fuel tanks caused burning fuel to flood into the fuselage, resulting in fatal fires that claimed all but one passenger’s life. The cockpit section separated from the wreckage and flew beyond burning vehicles without sustaining major damage; all four crew members survived this portion of the crash—with only minor injuries reported for the first officer.[2][3][4][5] They evacuated from their cabin area promptly and rushed toward wreckage to assist survivors. Only one passenger survived: Anatoly Bordonosov, who lost his right leg during the accident and as of 2015 resided in Yurga, Kemerovo Oblast.[8] Four members of the ground maintenance team perished instantly inside their vehicles; one occupant in the passenger seat of the UAZ survived after a fire erupted but was extinguished.[5]
Afterwards, Captain Stepanov resumed flying duties following recovery from this crash and continued active service for eight more years before retiring. He later appeared several times as an aviation expert in Russian media outlets until his passing on 14 November 2016.[6] Reflecting decades later on surviving this tragedy, Stepanov remarked: "The realization that I had survived came much later that day. More difficult than surviving was bearing that I stayed alive while over 170 people behind me did not... After this tragedy every October 11th I called flight engineer Vitaly Pronozin and we always wished each other 'Happy birthday.'"[6]
Investigation
A governmental inquiry determined that the disaster resulted from a series of errors primarily linked to the negligence of air traffic control personnel and breaches of fundamental airport safety and maintenance protocols. The ground controller, Borodaenko, was held directly accountable as he had fallen asleep during his shift, failing to respond to urgent communications. Additionally, he permitted service vehicles to enter the runway and neglected to indicate that the runway was in use. During the hearing, he was unable to recall his actions at the critical time but did not contest the accusations. He received a 15-year prison sentence and later died by suicide while incarcerated. Furthermore, flight operations manager Boris Ishalov was also sentenced to 15 years, approach controller Vasily Ogorodnikov received 13 years, and airport maintenance chief Mikhail Tokarev was given a 12-year term. All three individuals appealed their convictions but were unsuccessful. Subsequent audits at various Soviet airports uncovered comparable safety violations, leading to the dismissal of multiple senior officials.
No faults were attributed to the pilots or mechanical issues with the aircraft. The plane’s weight and balance conformed to established limits. Due to limited visibility conditions, the crew was unable to see obstacles on the runway. Although there were some reasonable uncertainties about whether the runway was clear, these concerns were dismissed following assurances from the approach controller. The flight crew had only moments to react and attempted evasive maneuvers but were ultimately unable to prevent the collision. Consequently, they were cleared of any responsibility.
The flight and approach controllers involved were seasoned professionals with over a decade of experience each. In contrast, the 23-year-old ground controller on duty lacked sufficient experience and reportedly suffered from sleep deprivation in the days preceding the event, as he was caring for two young children.
The formal trial took place merely three months after the incident due to the straightforward nature of the case; much of that period was dedicated to victim identification and contacting next of kin. All defendants and their legal representatives faced threats and required heavy security during court proceedings.
See also
- Western Airlines Flight 2605
- Singapore Airlines Flight 006
- LATAM Airlines Perú Flight 2213
- Ozark Air Lines Flight 650
- Pacific Western Airlines Flight 314
References
- ↑ Korean Air Lines Flight 007 was shot down by the Soviet Air Defense Forces after entering Soviet airspace but crashed in international waters near Sakhalin.
- ↑ 2.0 2.1 2.2 2.3 Cite error: Invalid
<ref>tag; no text was provided for refs namedASN - ↑ 3.0 3.1 3.2 3.3 3.4 3.5 3.6 Cite error: Invalid
<ref>tag; no text was provided for refs namedru1 - ↑ 4.0 4.1 Cite error: Invalid
<ref>tag; no text was provided for refs namedru2 - ↑ 5.0 5.1 5.2 5.3 5.4 5.5 5.6 5.7 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
- ↑ 6.0 6.1 6.2 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
- ↑ Cite error: Invalid
<ref>tag; no text was provided for refs namedru4 - ↑ Cite error: Invalid
<ref>tag; no text was provided for refs namedaviator
Template:Aeroflot Template:Aviation accidents and incidents in 1984 Template:Aviation accidents and incidents in the Soviet Union during the 1980s and 1990s
- Pages with reference errors
- Pages with script errors
- Articles with short description
- Use dmy dates from June 2025
- Articles with invalid date parameter in template
- Articles containing potentially dated statements from 2025
- All articles containing potentially dated statements
- Pages with broken file links
- 1984 events in the Soviet Union
- 1984 events in Russia
- 20th-century aviation mishaps in Russia
- Aviation incidents from 1984
- Aeroflot incidents and accidents
- Runway incursions
- Aviation incidents caused by air traffic control mistakes
- Accidents involving the Tupolev Tu-154
- Aviation accidents within the Soviet Union
- Omsk history
- Airliner ground collision incidents
- October 1984 events in Europe
- October 1984 events in the Soviet Union
- Accidents and incidents involving the Tupolev Tu-154