vAMSYS 5.4.7

What's new

• 300 ft AFE stabilisation gate

  VA owners can now configure a 300 ft above-field-elevation stabilisation gate in the scoring rules — useful for matching real-world carrier policies (e.g. Alaska Airlines). Pegasus now emits 300 ft landing reports to support it.

What's improved

• Event-slot dispatch is now locked to the event

  When dispatching an event slot, the departure time auto-fills from the slot and locks, and the route picker is constrained to the event's own route(s) — regardless of the pilot's current location. Direct URLs can no longer dispatch an off-event route onto a slot.

What's fixed

• PIREPs getting stuck on "Processing" with no points awarded after a stabilised approach, caused by airline gate altitudes being stored as text

• 500 error when dispatching event-slot flights, caused by the forced network being dropped from the form

• Event detail pages returning a 404 for plain Event activities even though they appeared in the events list

• Pegasus PIREP filing returning a 500 when the filing pilot had been deleted — it now returns a clear "pilot not found" error

• A pilot with no rank causing a 500 wherever their name-with-rank was displayed

• Route creation accepting airports outside the caller's own airline network (cross-airline leak); foreign airports are now rejected

• Stabilised-approach scoring failing a go-around because of an unstable reading from an abandoned earlier approach — only the final approach is now evaluated

• Intermittent error on the Phoenix flight-center dispatch form caused by the event-slot reservation not surviving a live update; the callsign field could also wrongly become editable

• Crash when processing Discord staff updates for a staff member whose airline had been removed, and one bad record aborting a bulk duplicate-pilot merge

• 500 during server-to-server pilot name changes when no user was authenticated