Your first BlueBird 757 flight with Icelandair Virtual

BlueBird Simulations released its passenger 757-200 on 24 October 2026. Its 757-300 and freighter are separate future developments, not substitutes you need to select for this first flight. Use the current developer documentation for your simulator edition, installer and update process.

An Icelandair Virtual B752 assignment is a Boeing 757-200. Icelandair’s published aircraft specification lists Rolls-Royce RB211 engines; select the matching configuration where available. Check that any Icelandair livery is built for the BlueBird aircraft and the version you have installed, rather than another developer’s 757.

Complete an offline familiarisation flight using the aircraft’s own normal procedures before adding company dispatch or online ATC. This guide explains the VA workflow, not the aircraft’s systems operation, performance calculations or a real-world type rating.

Open the Boeing 757 hub and filter the route finder for Europe or North America. For a first session, compare shorter European sectors rather than committing to a crossing before you have tested the setup. The list comes from active company services whose permitted fleet includes the 757-200, not a generic assumption that every Icelandair flight uses that type.

Open a service in Pilot Hub, choose your date and inspect the aircraft at departure. Select an available B752 registration that matches the flight you intend to simulate. If your preferred tail is somewhere else or held for maintenance, choose another available registration or a different departure. Do not treat a livery change as moving the company aircraft.

Our virtual schedule may permit more than one aircraft type on a flight. That is not a claim about the real airline’s equipment on a particular date. Your final bid and release define the virtual assignment you are about to fly.

Departure fields in the flight workflow use UTC. Check the date as well as the time, especially if you are planning in the evening in North America. Do not convert an already-UTC value a second time. Where the feed does not publish a departure time, choose the intended UTC departure in Pilot Hub instead of assuming that a blank value means midnight.

Read back the flight number, departure, arrival and selected registration before confirming. In the simulator, load at the same departure airport and use the booked 757-200. The airframe you fly and the registration on the release should describe the same assignment.

Open the dispatch package attached to your bid. Check the callsign, route, planned fuel, payload, alternate and departure date. The airline flight number and the ATC callsign are not necessarily the same string, so use the callsign shown on the release when preparing an online flight plan.

If you import the plan through the add-on’s SimBrief facilities, cross-check what arrived in the aircraft against that release. A successful import is not a substitute for checking the airports, route and current navigation data. Use the aircraft documentation for fuel loading, weights and performance rather than copying generic 757 figures from a webpage.

Keep the current departure, arrival and approach charts available. For an online flight, prepare the aircraft and briefing before connecting to the network. VATSIM connection, radio and oceanic procedures have their own Northline guides; an unfamiliar aircraft and your first oceanic crossing do not need to be the same lesson.

Open the current Icelandair Virtual Pilot Client for your operating system and simulator. Sign in with the same linked pilot account, load the correct bid and confirm that the client is receiving live simulator data. Check the airport, position and aircraft details while still at the stand.

The add-on and the Pilot Client are separate products. Custom aircraft systems or failure telemetry can behave differently from standard simulator fields. If the connection or recording state is wrong, solve that on the ground and include the aircraft version, simulator version and client version in a support report. Do not assume that a release being visible means the flight is already being recorded.

Confirm dispatch and recording status before pushback, then keep the simulator connection and client running throughout the sector. Follow the aircraft’s own checklists. Company dispatch messages are part of the operational flight record, not replacements for the aircraft manual or instructions from online ATC.

After landing, continue to the stand and complete the aircraft’s parking and shutdown procedure. Finish the tracked flight in Pilot Client, then check that the report has synchronized. If the client shows a pending upload, keep it open and follow the displayed recovery instructions instead of submitting another copy.

Review the debrief and flag missing or implausible telemetry rather than treating it as a reliable score. An accepted flight report updates the pilot’s history and the company aircraft record. A pending or returned report is not the same as an accepted one, so the aircraft’s public location may not change immediately.

For the next flight, check current aircraft position, turnaround and maintenance restrictions again. You can join a company event, plan another European sector or prepare a North Atlantic trip with the same account. If something is wrong, contact support with the bid or report reference; creating a duplicate pilot account will not repair the flight.