Aeroflot Flight 721
plane crash

Aeroflot Flight 721 was a scheduled domestic passenger flight between Moscow and Yuzhno-Sakhalinsk in the Russian SFSR. On Wednesday, 2 September 1964, the aircraft flying this route, an Ilyushin Il-18V, crashed into the side of a hill on approach to Yuzhno-Sakhalinsk, killing 87 of the 93 people on board. At the time of the accident, it was the deadliest Il-18 crash and the deadliest aviation accident on Russian soil.
Aircraft
The aircraft involved in the accident was an Ilyushin Il-18V turboprop airliner registered CCCP-75531 to the Krasnoyarsk Civil Aviation Directorate of Aeroflot. At the time of the accident, it had only been in service for about a year and had logged merely 1,269 total flight hours and 358 pressurization cycles.
Crew
Nine crew members were aboard the flight. The cockpit crew consisted of:
Captain Anatoly Andrevich Smirnov
Co-pilot Boris G. Stepanov
Navigator Anatoly Davydovich Gilinsky
Navigator-in-training Ivan Vasilievich Ivanov
Flight engineer Arkady Kalayda
Radio operator Yevgeny Petrovich Ipatov
Flight attendants Anastasia Tsebak, Lyubov Orekhova, and Nikolay Filatov worked in the cabin. All nine crew members perished in the crash.
Synopsis
Flight 721's route led it eastward across Russia from Moscow to Yuzhno-Sakhalinsk, with stopovers in Khabarovsk and Krasnoyarsk. The flight changed crews at Krasnoyarsk airport and proceeded with the flight to Khabarovsk without incident.
At 20:00 the flight departed Khabarovsk en route to the final destination, Yuzhno-Sakhalinsk, carrying 84 passengers, including 17 children.
Begin with the source’s own compact description: “Aeroflot Flight 721” is plane crash. The dossier treats that line as a proposition to test through Aeroflot, Flight and plane, not as a finished interpretation.
Why this record matters
The phrase “plane crash” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Feb 19, 2026. The linked authority identifier is Q15944664. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1964.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Aeroflot Flight 721”, its source revision and the description used here.
- Expand the search: follow Aeroflot Flight 721 primary sources, Aeroflot Flight 721 archive and Aeroflot research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Aeroflot Flight 721”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Aeroflot Flight 721” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.