The following areas of the Avianis Web Application have been updated:

**These items will be rolled out per customer in segments in the weeks following the production release. If you would like these features enabled sooner, please reach out to our Customer Success Team at CS@wheelsup.com**

For full details reference Feasibility List and Feasibility & Tools.

A new tab has been added within the Operations menu titled Feasibility. This page contains feasibility flags that are considered a warning or critical item and can be displayed for a specific time frame of 3 days, 5 days or 7 days. Users have the ability to filter by feasibility area and severity to always have a holistic view pertinent to your area and act accordingly.

The feasibility engine encompasses several changes in how the trip feasibility functions. The same checks are being accomplished and now when a trip is accessed, the feasibility and tools section will be expanded so the results are visible. When users update various data points such as trip/flight leg changes, passenger information, aircraft data, crew information, the feasibility check runs for all future trips and the results auto update the feasibility for all future trips that are affected.

An icon has been added to the ops dashboard to indicate if there are warning or critical flags in the leg feasibility. The indicator icon in the flight cards update in real-time as mitigations occur and critical and warning messages are handled. Quickly click on and see what the warning and/or critical items are.

The trip feasibility checks will now check if the Requires Flight Attendant box is checked. If this is selected for an aircraft and a flight attendant is not assigned to a leg on this aircraft, a critical flag will display in the aircraft section of the feasibility.

Certain maintenance discrepancies have operational impacts on what the aircraft can/cannot do during a flight. In order to capture these limitations, two new limitation options have been added, seating capacity reductions and day only operations.

If the Passenger Seating is set to Yes, a passenger count of 0 or higher is required to be entered. The trip feasibility checks to ensure the passenger count is not greater than the limit set for all flights scheduled while the discrepancy is active with the restriction. If the passenger count exceeds the restriction, a critical flag will appear.

If Day Only is set to Yes, a feasibility check is performed to ensure the flight is not operating at an airport outside daytime hours.

A new setting has been added to each leg status with the option to require an aircraft that was previously out of service to be returned to service prior to changing the leg status. If set to Yes and the offline event does not have a return to service date entered, a critical flag displays in the trip feasibility.

For full details reference Airport Directory - Setup and Configuration and Using the Airport Directory

Additional options have been added to the airport and customs hours configuration allowing operations the ability to notate if an airport is Day Only or Closed on specific days. If configured for Day Only, a feasibility flag displays if the flight leg is going into the airport at night (after sunset and before sunrise). If notated as Closed, a feasibility flag displays if the flight is scheduled to arrive at that airport on a day which it is closed.

A new section called Vendor hours has been added to the hours tab within an airport record. This allows operations the option to configure open hours for the Vendor/FBO at that airport. When a flight is scheduled into that FBO/Handler at that airport and it is outside of hours, a flag displays.

Operators now have the ability to setup temporary airport closures within the airport record > hours tab. Date range and applicable times for each day can be configured for each airport. Closure type can be captured as well after configuring Closure Reasons in Airports > Airport Closure Reasons. If a flight is scheduled during a closure, a flag displays in the trip feasibility.

Operations can now configure airport restrictions, conditional or denied ops, by aircraft model within the airport record > aircraft restrictions tab. One or multiple aircraft models can be added and the severity of the flag is configurable by the operation.

For each event category, the operation has the option to require a start and end airport to be selected within the event for all events created from within the Schedule Board.

If Require Airport is set to yes, a start and end airport is required before saving the event.

A new checkbox has been added to the Note Category setup form giving operators the option to sync trip trip or flight log related note categories to FlightBridge. When synced these notes are visible on FlightBridge's feature known as, Custom Schedules.

Operators now have a streamlined way to track instrument currency requirements for 135, SICs and 91, PICs. Approach, Hold, and Tracking have been added as a "type" within the regulatory set configuration. A Crew positions field has also been added for all limitation types allowing operators to configure which crew position (PIC, SIC, etc.) is required to meet these requirements/limitations when assigned to the applicable position(s) on the flight leg. For more details please reference Regulatory Sets: Limitations, Experience and Time Off.

For Operators using the V2 Logbook, a flight leg can now be crewed with an Augmented crew which includes 1 PIC, 1 PIC-Alt and 1 SIC. Away from Flight Deck Duty time can be configured in a regulatory set that is then applied to trips with an augmented crew. When logging the flight leg these 3 positions, an additional field displays within the Pilot Flying section called "Away from Flight Deck Duty" which aligns with the Flight Deck Time limitation in the reg set. The PIC-Alt position can log flight events such as take off, landing and approach. For additional details please reference Log a Flight (Scheduler Perspective: Logbook Version 2)