472nd Fighter Aviation Regiment
1950-1998 fighter unit of the Soviet and Russian Air Forces
The 472nd Fighter Aviation Regiment (Military Unit Number 61364) was a regiment of the Soviet Air Defence Forces, which later came under Russian command. The regiment was formed at the beginning of 1950.
It was formed on 15 May 1950 at Orel at the Oryol Yuzhny Airport, though its formation had begun early 1950. It was relocated to Kursk to Kursk Vostochny Airport ("Eastern") October 4, 1979 (leading the team, the material part), October 7, 1979, and the ground echelon of the regimental banner.
It was based at Orel from 1950 until 4 October 1979, upon which it moved to Kursk, where it was stationed until disbandment on 1 May 1998.
Armament
Since the formation of the regiment fighters Yak-17;
December 1950 with the fighters MiG-15;
In 1957, the fighters MiG-17 and MiG-19;
In 1979, the fighters MiG-23P.
Crashes
On December 27, 1989, Lieutenant Borsch's aircraft suffered engine failure. Airplane pilot led to the village Sapogova and ejected, and the fighter crashed in a field.
On March 3, 1994, during a training flight, Major Vladimir Zhivolup's MiG-23 suffered engine failure. After trying thrice unsuccessfully tried to restart the engine, the plane crashed on the outskirts of Kursk and cut through a clearing of a birch forest, destroying the number 59 house on the street and Bratsk. The wooden house caught fire, killing an old woman.
“472nd Fighter Aviation Regiment” enters the record as 1950-1998 fighter unit of the Soviet and Russian Air Forces. Crown Archives preserves that source wording while asking what 472nd, Fighter and Aviation can confirm, complicate or overturn.
Why this record matters
“472nd Fighter Aviation Regiment” is worth following because a concise public description often conceals a longer documentary argument. Here, 472nd, Fighter and Aviation provides the most credible route into that argument.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jan 17, 2026. The linked authority identifier is Q290246. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1950, 1979, 1998 and 1957.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. 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 “472nd Fighter Aviation Regiment”, its source revision and the description used here.
- Expand the search: follow 472nd Fighter Aviation Regiment primary sources, 472nd Fighter Aviation Regiment archive and 472nd 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 “472nd Fighter Aviation Regiment”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “472nd Fighter Aviation Regiment” 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.