Mikoyan-Gurevich MiG-9
fighter aircraft family; first jet-powered MiG
The Mikoyan-Gurevich MiG-9 (Russian: Микоян и Гуревич МиГ-9, USAF/DoD designation: Type 1, NATO reporting name: Fargo) was the first turbojet fighter developed by Mikoyan-Gurevich in the years immediately after World War II. It used reverse-engineered German BMW 003 engines. Categorized as a first-generation jet fighter, it suffered from persistent problems with engine flameouts when firing its guns at high altitudes due to gun gas ingestion. Multiple different armament configurations were tested, but none solved the problem. Several different engines were evaluated, but none were flown, as the prototype of the MiG-15 promised superior performance.
In total, 610 aircraft were built, including prototypes, and they entered service in 1948 with the Soviet Air Forces. At least 372 were transferred to the People's Liberation Army Air Force in 1950 to defend Chinese cities against air raids by the Nationalist Chinese and train the Chinese pilots in jet operations. The MiG-9 was quickly replaced by the MiG-15. Three are known to survive as of 2026.
Development
Origins
In February 1945, the Council of People's Commissars ordered the Mikoyan-Gurevich (MiG) OKB to develop a single-seat jet fighter to be equipped with two German BMW 003 engines. Intended to destroy bombers, the aircraft was to be equipped with a single 57-millimeter (2.2 in) or 37-millimeter (1.5 in) gun, plus two 23-millimeter (0.9 in) guns.
The public source identifies “Mikoyan-Gurevich MiG-9” as fighter aircraft family; first jet-powered MiG. This brief keeps that definition visible, then builds a research path around Mikoyan-Gurevich, MiG-9 and fighter.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Mikoyan-Gurevich MiG-9”, the useful work is to connect “fighter aircraft family; first jet-powered MiG” to the records capable of establishing context and consequence.
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 Mar 18, 2026. The linked authority identifier is Q270839. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1948, 1950, 2026 and 1945.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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 “Mikoyan-Gurevich MiG-9”, its source revision and the description used here.
- Expand the search: follow Mikoyan-Gurevich MiG-9 primary sources, Mikoyan-Gurevich MiG-9 archive and Mikoyan-Gurevich 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 “Mikoyan-Gurevich MiG-9”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Mikoyan-Gurevich MiG-9” 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.