BF1 Flag
This article is a stub as it is considered incomplete. Why not help out?
Bristol F.2 IRL

The Bristol F.2 was a biplane fighter designed in Britain and used during World War I. Despite having two seats, the robust construction and powerful engine allowed it to carry out aerial maneuvers on par with single-seat fighters, with its agility earning it a favorable reputation that kept it in service into the 1930s.

The F.2B first saw combat during the Battle of Arras in April 1917 - a month known as "Bloody April" where aircraft losses were extremely high. After this time pilots began to recognize the strengths of the F.2 and fly accordingly. 5,329 aircraft of this type were produced between 1916 and 1927.

Battlefield 1Edit

Bristol F2.B
Bristol F2B Icon
Vehicle passengers • 1 pilot
• 1 gunner
(2 total)
Vehicle armor None
Passenger weapon Lewis Gun
Upgrades Ground Support Package (Default)
Tank Hunter Aircraft Package
Airship Buster Package
Vehicle speed Moderate
Vehicle maneuverability Moderate
Operators BF1 United Kingdom Icon British Empire (Royal Flying Corps)

BF1 Kingdom of Italy Icon Kingdom of Italy

This item has a Codex entry: The Brisfit

The Bristol F2.B is featured in Battlefield 1. It was first seen during the EA Play livestream. A more detailed view from the cockpit and of the F2.B in combat is shown in the Battlefield 1 Gamescom Trailer. The F2.B appeared in the Customization screen during the Open Beta, but was not used in the field.


The Bristol F2.A is controlled by the player in Friends In High Places. It is armed with machine gun and rocket pods.

Several F2.B fighters can be seen providing support in Storm of Steel. One Bristol is seen in The Runner, flying over Fort Nöbet.


The Bristol F2.B is the main attack plane of the Royal Flying Corps and Royal Italian Army.


Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.