Start here
A few places to begin, from the aircraft’s story to the people who fly it.
Aircraft and simulator background
The Fokker Dr.I was a single-seat triplane fighter of the First World War. The RAF Museum's timeline records the first two F.I/Dr.I aircraft reaching Richthofen's unit on 21 August 1917 and Werner Voss recording the type's first combat victory on 30 August.
Fokker Dr.I
RAF Museum · Read more ↗The community simulator rendition
Got Friends lists the Dr.I as community content distributed through Flightsim.to, with manual installation. The product banner identifies a build for MSFS 2020 and forward compatibility with MSFS 2024.
Fokker Dr.I
Got Friends · Read more ↗Meet Fokker Dr.I
The Fokker Dr.I was a single-seat triplane fighter of the First World War. The RAF Museum's timeline records the first two F.I/Dr.I aircraft reaching Richthofen's unit on 21 August 1917 and Werner Voss recording the type's first combat victory on 30 August.
Got Friends represents the triplane in a simulator package. Its aircraft page is linked separately from the historical account.
Fokker Dr.I
Fokker → · Explore the family →
Fokker Dr.I
RAF Museum · World aviation timeline: 1917 ↗Aircraft type designators
No type designator selected for this reference.
History & design
Arrival and wing-construction problems
The first two F.I/Dr.I fighters reached Richthofen's unit on 21 August 1917. On 30 August Werner Voss recorded the first combat victory for the type. A Dr.I broke up in flight on 28 October, and the subsequent grounding and investigation revealed deficiencies in wing construction.
RAF Museum · World aviation timeline: 1917 ↗21 and 30 August; 28 October — F.I/Dr.I delivery, combat and grounding
Systems & details
The community simulator rendition
Got Friends lists the Dr.I as community content distributed through Flightsim.to, with manual installation. The product banner identifies a build for MSFS 2020 and forward compatibility with MSFS 2024.
The Oberursel rotary
The USAF Museum identifies the Dr.I’s Oberursel UR-2 as a 110 hp rotary derived directly from the French Le Rhône design of the same rating. Its account also distinguishes the surviving UR-2 in its collection from the engine of Richthofen’s aircraft held by the Imperial War Museum. This is the historical engine reference, rather than a description of a modern replica installation.
In your simulator
Systems, equipment and documentation for each developer’s aircraft.
MSFS 2020 · MSFS 2024Got Friends Fokker Dr.1
Got Friends · Released
Got Friends Fokker Dr.1
Got Friends · Released
Manuals & resources
Find your next read
Choose a topic for a short introduction and a link to the original source. Simulator references identify the developer and edition they cover.
Museum history
World aviation timeline: 1917Fokker Dr.I
21 and 30 August; 28 October — F.I/Dr.I delivery, combat and grounding
RAF Museum · Read the source ↗Developer documentation
Fokker DR.1Fokker Dr.I
Product description and feature list
Got Friends · Read the source ↗Read the original documentation from the people who created it. Manuals open on their publisher’s website.
Museum history
World aviation timeline: 1917RAF Museum · 21 and 30 August; 28 October — F.I/Dr.I delivery, combat and groundingDeveloper documentation
Fokker DR.1Got Friends · Product description and feature listAircraft documentation
Oberursel UR-2 rotary engineNational Museum of the United States Air ForceBuilt-in force-feedback profiles
Read the documentary basis, editable starting settings and remaining questions for the aircraft you fly. Each explanation refers to the exact profile revision shown.
Catalogue programme-20261011-v3 · 1 profile choice
Got Friends Fokker Dr.1
Got Friends · Free and Pro · Revision 2 · Inherited starting point
MSFS 2020 · MSFS 2024
A single-seat First World War triplane fighter.
Discuss this aircraft (0)
Questions, observations and useful sources from the community.
No published discussions yet. Bring a question or share a useful source.
Open aircraft discussions →Content expanded · What’s new
Something missing or a source that needs attention?
Suggest a correction ↗
