LH Virtual

vAMSYS · Pegasus · Crew Pad

The house rules, the tools and a few things nobody tells you until your first report bounces.

  • 23 facts
  • Checked 5 Nov 2026

vAMSYS and booking

A booking is made for one specific aircraft, so pick the registration you will really load. The rule behind it is strict: the type booked must be the type flown. Fly another type and the report is invalid, even if everything else about the flight was perfect.

Changed your mind? Rebook. Swapping the aircraft after booking and filing against the old one does not work.

Source: OM-B A32X, 7.1 and 7.5

You get it when you join, DLH1049 and the like, and it follows you everywhere: vAMSYS, the leaderboards and even the passcode of your Crew Pad.

Source: FAQ

On VATSIM, file the callsign shown on your vAMSYS booking, DLH… or OCN… for example. The commercial number (LH…, 4Y…, EN…) belongs on the schedule and in your paperwork.

Source: FAQ

vAMSYS cancels the booking you pick and every booking after it. If you only want to drop one leg, rebook the later ones afterwards. It also does not work while your flight is still sending position reports.

Source: vAMSYS Pilot API documentation

Pegasus, our ACARS, records position, altitude, fuel and the landing rate. At shutdown it files your PIREP and the grading happens on the spot. All you do is start it before pushback.

Source: FAQ

Any aircraft of the booked type works, freeware included, as long as it roughly matches the real performance.

Source: FAQ

Hours, legs and ranks from another virtual airline do not carry over. Every hour on your record was flown with us.

Source: FAQ

Reports and rules

Time acceleration, mid-air refuelling and a landing load above 2.6 g invalidate a report outright. There is no appeal, because the sector was not flown the way the report claims.

Time acceleration
Invalid
Mid-air refuelling
Invalid
Landing above 2.6 g
Invalid

Source: OM-B A32X, 7.3

A diversion, a new livery or a bounced landing send your report to staff review. A person looks at the sector before it counts, because the automatic checks cannot tell a good reason from a bad one.

Diversion
Staff review
New livery
Staff review
Bounced landing
Staff review

Source: OM-B A32X, 7.4

Crew Pad

DLH1049 unlocks with 1049. It is not a secret and it is not meant to be: your data is protected by your vAMSYS session on the server. The passcode just makes the device behave like a device.

Source: Crew Pad Guide

Roughly one open in four, the first look is refused, because real hardware does that too. It only ever happens on the first try, so just look again.

Source: Crew Pad Guide

From then on the Pad produces your briefings: preflight, weather and NOTAM post arrive in eDesk, staggered, from about three hours before departure until an hour after arrival. Without a check-in there is nothing to produce them for.

Source: Crew Pad Guide

Fuel checks and actual times add up on the same PIREP, and a completed Scenery Vote streak counts on your next accepted one. The points appear on the PIREP, not on the Pad.

Two fuel checks in flight
20 points
Actual times and fuel
5 points
Scenery Vote streak
100 points

A fuel check is any fuel figure entered on the Flightplan page of flySmart! after take-off. TOC and TOD do not count.

Source: Crew Pad Guide

vAMSYS removes the booking when Pegasus files the report. The Pad keeps the leg on your roster for up to 72 hours, marked TIMES MISSING, so you can still report your actual times and fuel.

Source: Crew Pad Guide

If the Pad does not know a value, it says so. An assumed value is labelled as assumed and a missing one is named as missing, because a confident wrong number in a cockpit is worse than an honest blank.

Source: Crew Pad Guide

Checked against: LH-V Operating Manual B, the Crew Pad Guide and our FAQ, 5 Nov 2026. For flight simulation only, never for real-world navigation. Procedures change, so your current charts and ATC always win.

More topics