No assigned flights
Your schedule is empty
Assigned trips will appear here after Avianis synchronization is enabled.
MyAxcess
One secure, offline-ready workspace for flight operations, scheduling, documents, expenses, PTO, and company workflows.
Use your company Microsoft 365 account to continue.
Your assignments and operational records will appear after synchronization.
Assigned trips will appear here after Avianis synchronization is enabled.
Aircraft assignments and status will appear after Avianis synchronization.
Microsoft 365Identity and documents
Not connectedAvianisFlight operations
Not connectedBaldwin SMSSafety and FRAT
PlannedComplete, validate, and synchronize your assigned flight records.
Current primary and after-hours coverage will appear here.
The calendar is ready for live Avianis assignments. Select a synchronized trip to open its details, feasibility review, chat, and flight log.
This flight remains visible in the offline schedule, but its detailed trip package is outside this device’s cache window.
Friday, October 30 · Beechcraft King Air 350 · N812AX
AX-2461 · KTEB → KDAL
Released Oct 30 at 6:12 AM by Flight Scheduling
Current handling details for this leg.
100 Moonachie Ave · Teterboro, NJ
7367 Cedar Springs Rd · Dallas, TX
4 passengers · 692 lb total
| Passenger | Date of birth | Weight | Baggage | Travel documents | TSA profile | Notes |
|---|
Documents attached to this Avianis trip.
Catering, transportation, lodging, handling, and confirmations.
Only values applicable to the selected aircraft type are shown. Blank fields are not stored.
Oil additions are recorded separately. The dedicated oil-entry workflow remains the authoritative source for oil added and prevents duplicate reporting.
Select an assigned flight to begin.
This append-only note is saved with the selected flight, author, and UTC time.
This supports crew review; it does not replace company policy, dispatch, or PIC authority.
Assigned crew and Scheduling
BALDWIN SMSFlight risk assessment not startedComplete prior to flight release
AX-2461 · KTEB → KDAL
API availability pendingAvianis documents these feasibility areas; API access to the evaluated results remains unconfirmed.
iLeg 1 · N812AX VOR check valid. Last passed Oct 26.
✓Fire extinguisher inspection current through Nov 11.
✓Navigation database cycle 2611 is current.
✓Rob Williams has a passport on file.
i3h 23m projected duty is within the 14h limit.
i2h 55m projected flight time is within limits.
i13h 42m pre-duty rest meets the 10h minimum.
!Passenger TSA profile confirmation is pending for one traveler.
!KDAL runway closure overlaps the planned arrival window. Dispatcher review required.
✓Catering and ground handling confirmations received.
✓No international planning requirement for this leg.
✓Required trip tasks and TSA checks are complete.
Leg AX-2461 · KTEB → KDAL
Crew onlyFlight-specific notes pulled from Scheduling
API pendingN812AX · Avianis read-only feed
Enter local airport times. Zulu dates are calculated automatically.
The production app will resolve the diversion airport timezone before recalculating ON and IN times.
Calculated from the scheduled departure and the flight log’s actual block-in time.
Avianis feasibility governs compliance. MyAxcess calculates the time period, but it does not duplicate Avianis’s configured duty-limit rules.
Times are chronological and actual flight time matches the estimate.
Fuel burn is calculated from OUT and IN quantities. Post-flight fuel service is added only to the aircraft’s reported onboard quantity.
1 qt oil added · Left engineOct 14 · Total time 3,221.4 · Rob Williams
SyncedRequest days off and bid on available trips. All remaining dates become duty days automatically when bidding closes.
No active bid window is available.
Scheduling has not opened a monthly bid window.
Used as guidance during conflict review
Exact opening time
Submissions lock automatically
Pending or awarded requests
Click a date to choose priority, add an optional note, and submit a day-off request.
Trip bids remain available at any time. A trip appears here only after Scheduling explicitly marks it biddable.
Save a weekly pattern once. When each monthly bid window opens, MyAxcess creates separate pending bids for every matching date.
Automation submits requests—it does not award days. Each generated date remains subject to the normal seniority and scheduler-review process. Disabling or deleting a rule does not remove bids already created for an open period.
Pending bids may be withdrawn until the monthly window closes.
Existing Avianis totals, time-in-type, and training records—no duplicate configuration required.
Duty begins one hour before scheduled departure. Forecast duty ends 30 minutes after scheduled block-in; final duty ends 30 minutes after actual block-in. Avianis feasibility remains authoritative for the applicable company and regulatory limits.
Selected Avianis period
Selected Avianis period
Selected Avianis period
Selected Avianis period
Your Avianis time-in-type totals will appear here after the integration is connected.
| Aircraft type | Position | Total | Status |
|---|---|---|---|
No Avianis totals loadedExisting time-in-type records will populate without reconfiguration. | |||
Your Avianis training and currency records will appear here after the integration is connected.
| Training item | Aircraft / position | Last completed | Next due | Status |
|---|---|---|---|---|
No training items loadedAvianis status, due dates, and grace periods will be used directly. | ||||
The API returns flight-hour totals and evaluated feasibility results, but it does not expose the underlying company or regulatory limit configuration. MyAxcess will display Avianis’s results rather than maintain a second set of limits.
Verify offline data, refresh assigned trip packages, and review training status.
Open Sync Center to review failed or conflicting items.
Checked when online
Open online to refresh
UnknownCached controlled copies
UnknownCached notices
UnknownWhile MyAxcess is visible, online, and signed in, a lightweight revision check runs every minute. Cached operational data is downloaded again only when its server revision changes.
Using this device’s local calendar, MyAxcess keeps assigned trips for yesterday, today, and the next seven days. Unchanged trips are reused; changed packages replace the previous copy atomically.
Calculating device storage…
Permanent data and protected flight logs, expenses, inspections, and other submitted records are never removed by the operational trip-cache window.
Only trips assigned to the signed-in user are eligible.
Displays authoritative integration status and cached training items when safely matched to your identity.
Loading the Administrator-configured company fleet.
Active and maintenance aircraft configured by an Administrator appear here. Crew-specific assignments will be layered in when Avianis access is enabled.
Aircraft will be listed here when assignments are received from Avianis.
Beechcraft King Air 350
VOR Operational CheckPassed · October 26
Fire extinguisherPassed · October 12
Navigation databaseCycle 2611 · Updated Oct 29
Chart databaseCycle 2610 · Update available
N812AX · Avianis read-only feed
| Date | Event | Details | Personnel | System status |
|---|
Submit flight-linked or general expenses with receipt photos and PDF files.
Reports on this device
Awaiting integration
Marked for reimbursement
Photos and PDFs retained locally
Flight-linked and unattached expenses use the same append-only record workflow.
Create a report from this page or attach one directly to a flight log.
MyAxcess stores the report and receipt locally first. It will only claim an Avianis upload after the expense and attachment endpoints return identifiers that can be read back and verified.
Use MyAxcess-hosted files or open connected external libraries without mixing their contents.
These folders and files are maintained independently from SharePoint and other connected providers. Administrators control uploads and folder organization; authorized users can view the library.
An Administrator can create folders and upload company documents here.
These entries open the provider's own library. Linked access is available now; API synchronization remains disabled until that provider's OAuth credentials and permissions are configured and verified.
An Administrator can add a SharePoint, OneDrive, Google Drive, Dropbox, Box, or other secure document-library link.
One place for flight changes, company notices, acknowledgements, and operational alerts across MyAxcess.
New company, role-based, and aircraft-specific notices will appear here.
Review aircraft health records and the operational entries submitted by flight crews.
Compare left and right engines, maintain aircraft-specific averages, and review unusually high readings reported with flight logs.
Review protected oil-addition records by aircraft and engine. Pilots may continue submitting oil entries from Pilot View.
Fire-extinguisher checks, VOR checks, database updates, and discrepancies remain visible with their original author and audit history.
Maintenance access controls this reporting workspace. It does not prevent authorized pilots from recording operational aircraft data.
Compile optional flight-log readings, maintain like-for-like averages, and surface unusual values for human review.
Flags compare the same aircraft, engine side, propulsion type, and metric. They do not replace aircraft manuals, approved limitations, inspections, or maintenance judgment.
Last 90 days
same metric only
statistical flags
selected aircraft
Choose an aircraft and metric to review its history.
Protected flight-log values with aircraft, side, metric, author, and statistical status.
| Date | Flight | Aircraft | Engine | Metric | Value | Status |
|---|---|---|---|---|---|---|
No engine statisticsOptional flight-log readings will appear here. | ||||||
Monitor protected oil-addition records by aircraft and engine.
Last 90 days
oil additions
oil additions
current filters
Saved oil additions matching the selected filters will appear here.
| Date | Flight | Engine | Oil added | Aircraft time | Personnel |
|---|---|---|---|---|---|
No oil entriesCompleted oil entries will appear here. | |||||
A dedicated home for internal employee resources and future HR-connected workflows.
Centralize company-owned profile settings and employee support resources without changing Microsoft, Avianis, or payroll records.
Review pending vacation, PTO, and sick-time requests with a required human decision and an append-only audit trail.
HR access is assigned independently from Pilot, Scheduler, and Maintenance access. Administrators and the Owner retain access for support and oversight.
Review employee balances, dates, coverage notes, and request history before making an explicit human decision.
Requests awaiting a human
Provider-confirmed decisions
Reason required
Awaiting approved credentials
Only authorized HR personnel and administrators can review this queue.
Provider-confirmed decisions and local preview validations appear here with reviewer attribution.
Review submitted expenses, monitor documentation, and prepare controlled operational reports.
Review company-wide submitted expense reports, reimbursable amounts, receipt coverage, and workflow status.
Prepare department-owned financial reports for Excel or print-ready PDF without exposing other workspaces.
Finance access is assigned separately. The Finance Assistant can summarize and prepare review material, but cannot approve, pay, reimburse, or alter an expense.
View protected expense submissions across the company while preserving the original report and audit history.
Protected submissions
Current result set
Marked for review
Attachment metadata pending
Finance may review and export reports. Original pilot submissions remain append-only.
Financial metrics and audit-ready exports owned by Finance.
Submitted amount, reimbursable amount, category, aircraft, trip, payee, and documentation status.
Contribution margin per available aircraft-day, with owned versus leaseback aircraft segmentation.
Awaiting authoritative revenue and variable-cost feeds.Price lost and reason: aircraft, PIC, SIC, maintenance, duty/rest, price, or unsuitable aircraft.
Awaiting Avianis opportunity and trip feeds.Aircraft-health and maintenance-readiness reports for qualified human review.
Like-for-like engine readings, statistical flags, and source history.
Oil additions by aircraft, engine, date, flight, and reporting personnel.
Maintenance-caused unavailable days and open-work aging.
Awaiting maintenance-system integration.People-support reporting with privacy boundaries and human review.
Requests, balances, decisions, coverage notes, and provider confirmation status.
Preview-only until PrismHR access is validated.Onboarding, offboarding, role changes, and active-account counts.
Scheduling, bid, trip-demand, and coverage reporting for operational planning.
Day-off requests, awards, denials, replacements, aircraft type, PIC/SIC, and seniority guidance.
Aircraft-days requested, staffed, uncovered, outsourced, or declined.
Awaiting authoritative Avianis schedule data.Opportunity age, bid volume, assignment outcome, and premium-trip response.
Every entry is saved locally first, versioned, and queued without holding up the pilot.
Not submitted
Saved on this device
Nothing requires action
Verified shared copies
Each submission retains its schema version, original values, UTC timestamp, author, local integrity digest, and complete audit history. Corrections will be stored as linked amendments rather than destructive edits.
PIC and SIC submissions receive equal treatment. If two offline submissions disagree, neither replaces the other; both are preserved and the differing fields enter an audited conflict review.
Server-authorized administrators can review concurrent flight-log submissions without changing either original.
Items remain available even when a vendor connection is unavailable.
Drafts and submitted records will appear here automatically.
Record creation, draft saves, and synchronization attempts are logged separately from the original entry.
Configure each enabled aXcess Air module independently. Changes are versioned inside MyAxcess and never write to Avianis or another provider.
Provider boundary preserved. Avianis remains the external operational system of record. These settings control only MyAxcess behavior.
Review authenticated users and manage MyAxcess roles, seniority, bidding access, and app preferences.
Authenticated accounts
Permanent highest access
All-workspace access
Scheduling workspace
Daily flight control workspace
Final flight release personnel
Aircraft health workspace
Employee support workspace
Expense and reporting workspace
Manual charter brokerage
Add and configure company aircraft, then expose the approved operational profile throughout MyAxcess.
Registered records
Visible in Aircraft tabs
Operationally visible
Manual and CAMP items
Administrators may create manual inspection items. CAMP-sourced inspections will populate the same list as read-only records when that optional integration is enabled; no CAMP or Avianis write occurs here.
Choose an aircraft to review its protected configuration.
Review production tenant, module, identity, and authority status. Standalone product work is isolated in the Owner-only Development workspace.
The original MyAxcess roadmap remains intact. Avianis is prepared as the external operational system of record; provider writes remain disabled until credentials, approvals, and reconciliation are ready.
Active customer-facing environments
Membership-bound tenant access
Configured per operator
Production authority profiles
Tenant modules, identity domains, and authority boundaries will appear here.
Standalone architecture, sandbox tenants, import contracts, performance assumptions, scheduling rules, and integration classifications are consolidated in the separate Owner-only Development workspace.
Prepare the modular operator product independently while preserving the aXcess Air compatibility profile and Avianis authority boundary.
The navigation, screen, and API require the protected Owner role. Every record below belongs to the isolated standalone sandbox.
Original roadmap retained. Avianis remains the external operational system of record and production writes remain disabled.
Native scheduling, airport data, performance, quoting, modular entitlements, and customer configuration.
Loading setup workflow
Immutable assumptions and pricing
No aXcess Air operational records
Rule-driven demonstration cases
Existing standalone readiness gates now live with the development workbench.
Provider classifications remain visible only in the Owner development surface.
Future product work is documented here without expanding the current pre-1.0 release scope.
Configure the isolated demonstration operator. Saving creates an immutable company configuration version.
Enable the workspaces purchased by an operator. Required dependencies are included automatically.
Each module has an independent, versioned configuration tab. Disabled modules can be prepared before an operator enables them.
Define least-privilege job roles for each operator. Permissions remain subordinate to module entitlements, and the protected Owner role cannot be edited.
Configure modeled duty, turnaround, assignment, qualification, and data-quality rules for each operator.
Set required crew count and flight-deck positions by aircraft type without hard-coding a customer fleet.
Review every setup phase, retain the supporting evidence, and test readiness without provisioning production.
Download normalized schemas before official or licensed source files are received.
Inspect the shared aviation foundation and approved modular-sandbox overlays exactly as a future operator would see them.
Read-only sandbox view. Directory inspection does not promote an import, modify shared records, contact a provider, or alter aXcess Air.
Stage a small airport, runway, or FBO CSV against its published contract, inspect record-level findings, record an Owner decision, then promote it into the tenant-scoped standalone directory.
Configure customer-specific ground allowances, passenger service, contingency, tax placeholders, target margin, and international planning time.
Calculate distance, airborne time, block time, configurable planning price, and international review requirements against the synthetic airport directory.
Arrange up to six airports, apply one versioned aircraft profile, calculate every leg, and review combined time, distance, pricing, wind, and international requirements.
Test an aircraft, crew, route, authority, and time window against the active native scheduling rules and existing synthetic schedule.
Promote a planning request into the native operated-trip ledger, assign one trip-level Regulatory Set, and automatically publish any uncovered crew positions.
Standalone sandbox only. No Avianis record, dispatch release, flight plan, customer message, or aXcess Air record is created or changed.
Edit the synthetic profiles. Saving creates and activates a new immutable sandbox version.
Hard blocks, approvals, and warnings are evaluated from configurable rules.
Fictional fleet, crew, trips, and scenarios for testing and sales demonstrations.
aXcess Air remains isolated. Development actions are limited to the modular-sandbox tenant. Avianis remains the protected external system of record for the aXcess Air profile, and provider writes remain disabled.
Maintain one authoritative, gap-free seniority order for every active user with Pilot access.
Users with Pilot access
Current saved ranks
Placed at the end until saved
Drag pilots into position or type a rank. Saving renumbers the complete active Pilot roster from 1 without gaps.
Deactivating a pilot automatically removes their seniority rank and moves every lower-ranked active pilot up one position. The change remains in the permission audit history.
Track incoming revisions, controlled release, distribution, and pilot acknowledgements.
No revisions loaded
No documents under review
No active assignments
No overdue acknowledgements
Incoming revisions will populate this queue after the SharePoint integration is approved and synchronized.
| Pilot | Manual Revision | Assignment | Viewed | Acknowledgement | Status |
|---|---|---|---|---|---|
No acknowledgement assignmentsPilot status will appear after a controlled revision is distributed. | |||||
Track connection status and every vendor question required before implementation.
The complete Connect API specification has been audited: 181 operations and 280 data models.
Date-bounded resources are limited to 62 days. Personnel lookup requires an exact email.
Configure encrypted Avianis credentials before the first read. No live request is attempted until then.
Confirmed API capability is shown separately from what MyAxcess has enabled. Negative findings are retained so missing operations are not mistaken for pending research.
Identity, SharePoint, and controlled documents
Trips, personnel, aircraft, flight logs, feasibility, events, notes, and expenses
Inspection visibility through Avianis feasibility
FRAT and safety workflows
Hotels, rental cars, airline travel, catering, ground transportation, and FBO services
Marketplace RFQs, quoting workflows, and Trip Manager connectivity
Open implementation questionsAnswers can be marked complete here as vendor discussions progress.
Prepare employee identity linking, request workflows, manager review, and API readiness before credentials are enabled.
Credentials not configured
Microsoft-to-PrismHR mappings
Preview validation only
Remain in PrismHR initially
Administrator-only mockup of the future employee workflow. Values remain in this browser and are never transmitted.
Awaiting PrismHR balance data
Awaiting PrismHR balance data
Awaiting PrismHR balance data
The production version will require an explicit employee confirmation immediately before calling EmployeeService.requestPTO.
Complete the form to verify required fields and view the future confirmation step.
Server-side role checks, employee ownership verification, fresh PTO plan lookup, idempotency, audit history, and provider read-back must pass before submission is enabled.
Only these explicitly approved methods will be granted to the future Web Service User.
EmployeeService.requestPTOEmployeeService.getLeaveRequestsEmployeeService.cancelPTORequestEmployeeService.getManagerApproverNameEmployeeService.approveOrDenyPTORequestBenefitService.getPaidTimeOffBenefitService.getPaidTimeOffPlansBenefitService.getPtoAbsenceCodesBenefitService.getPtoRequestsListItems required before any pilot-facing PTO interface can be released.
Review today’s flights, resolve operational attention items, and record final flight releases with named Tier 1 accountability.
Authoritative scheduled legs
Ready for Tier 1 review
Named and time-stamped
Delay, crew, or aircraft concern
Primary and after-hours duty coverage
Flights requiring operational follow-up for the selected day.
Attention items for the selected day will appear here.
Current coverage and upcoming vacancies that require administrator attention.
Primary and after-hours assignments will appear here.
Named Tier 1 release records and release numbers.
Every release records the individual, time, and release number.
Review the authoritative upcoming flight list and record final releases. Every completed release retains the exact individual, time, and release number.
Operations access provides review capability but does not grant release authority.
24-hour release rule. Tier 1 Personnel can review upcoming legs in the 48- and 72-hour windows, but final release remains locked until 24 hours before departure.
Waiting for the authoritative Avianis flight-leg snapshot.
Apply the trip’s operating rules once, then use a leg exception only when a specific flight leg must differ.
Choose the trip-level set during trip setup. Expand a trip only when a leg requires a different set.
See who is handling primary and after-hours scheduling coverage. Administrators can publish upcoming coverage here.
The next scheduled primary shift will appear below.
After-hours coverage will appear when scheduled.
Recurring assignments, manual deviations, PTO vacancies, and after-hours coverage appear together.
Choose one or more weekdays and an effective date range.
Replace the normal scheduler, publish a known vacancy, or cancel coverage for one date.
Approved PTO and vacation records automatically create a vacancy against the employee’s normal recurring shift. Manual replacements clear that vacancy for the affected coverage period.
Record open trips, decisions, and follow-up items for the next scheduler without leaving the coverage page.
A focused view for schedule awareness and direct trip communication with assigned crews.
Avianis schedule connection pending
Shared conversations opened on this device
Available after Avianis flight-leg access
Trips, releases, assigned aircraft, and crew will populate here once the Avianis read connection is enabled.
Use the same trip or flight identifier the crew sees in Pilot View. Messages are shared through MyAxcess and remain tied to that trip.
Prepare hotels, rental cars, commercial airline, catering, ground transportation, and FBO services without leaving MyAxcess.
Avianis remains authoritative. MyAxcess will use FlightBridge for service reservations and then verify the confirmation returned to the Avianis trip. Duplicate booking protection will use the Avianis trip/leg ID and FlightBridge reservation ID.
Every action is mapped to the official Connect API but remains non-operational.
Test request validation, duplicate protection, provider failures, read-back verification, and scheduler review before API credentials are enabled.
Trip creation is simulated; no schedule record is created.
Confirmations and failures use simulated provider responses.
Every run receives an idempotency key and an append-only event trail.
MyAxcess uses one internal trip model while each provider retains a clearly defined source-of-truth boundary.
External writes remain locked. Future requests must pass role authorization, human approval, duplicate protection, provider read-back, and conflict reconciliation before they can become operational.
Use operationally realistic test information only. Do not enter passenger names, payment information, or membership numbers here.
The simulator stores the request and result for testing, but it cannot contact Avianis or FlightBridge.
These gates remain required even after API credentials are received.
Successful, failed, and incomplete provider scenarios remain available for scheduler review.
Prepare trip, itinerary, crew, passenger, service and feasibility requests.
MyAxcess watches consecutive trips by aircraft, proposes tentative reposition legs, and leaves every schedule change under scheduler control.
Proposals account for comfortable operating hours and require review of applicable flight-time, duty, and rest rules under 14 CFR 135.265 and 135.267. Avianis schedule data and company procedures remain authoritative.
Trip type, stage, coordinator, regulatory set, primary contact, and optional MyAxcess bidding.
POST /connect/v2/TripPUT /connect/v2/Trip/{tripId}All schedule times will be normalized to UTC with airport-local display.
POST /connect/v2/Trip/{tripId}/ItineraryPUT/DELETE /connect/v2/Trip/{tripId}/Itinerary/{id}PUT .../{id}/statusAircraft/fleet/category, flexible windows, revenue, reservation type, passengers and technical-stop status.
PUT /connect/v2/Trip/{tripId}/Itinerary/{itineraryId}/demandrequestSupports trip-itinerary crew and standalone aircraft crew assignments.
PUT .../Itinerary/{itineraryId}/AddCrewDELETE .../RemoveCrew/{crewId}POST/PUT /connect/v2/CrewAssignmentUpdate manifests and passenger-purpose information for each itinerary leg.
GET /connect/v2/Trip/{tripId}/PassengersPUT /connect/v2/Trip/{tripId}/PassengersTrip services remain linked to the correct leg, airport, vendor and scheduled time.
GET/POST /connect/v1/serviceRequestGET/PUT/DELETE /connect/v1/serviceRequest/{id}Use Avianis’s configured aircraft, crew, airport, service and regulatory checks.
POST /connect/v2/Trip/Feasibility/HypotheticalPrepare opportunities, quotes, deals, accounts, contacts and customer intelligence lookups.
Checking the saved Administrator setting for the Scheduling module.
Calculate airport distance, estimated flight time, route assumptions, airport/FBO details, and configurable quote components.
Sequence up to six airports and calculate every leg with the selected MyAxcess aircraft profile and configured commercial assumptions.
Search the operator directory by ICAO, IATA, local code, airport name, or city. Runway and service-provider records remain planning references until verified.
MyAxcess estimates only; no customer quote, trip, release, or Avianis record is created.
POST /connect/v2/OpportunityPUT /connect/v2/Opportunity/{id}POST /connect/v2/Opportunity/{id}/quotePOST /connect/v2/quotesPUT /connect/v2/quotes/{id}GET /connect/v1/quote/{id}POST /connect/v2/Deal/DealsByIdGET/PUT /connect/v2/Deal/{id}POST/PUT /connect/v2/AccountGET /connect/v2/Account/{id}POST/PUT/PATCH /connect/v2/ContactPOST/PUT/DELETE .../Contact/{contactId}/AccountPOST/PUT/DELETE .../AdditionalAddressRetrieve account or contact preferences, including vendors, account numbers, URLs and descriptions.
GET /connect/v2/Account/{accountId}/PreferenceGET /connect/v2/Contact/{contactId}/PreferenceRetrieve all flight legs associated with a contact.
GET /connect/v2/Contact/{contactId}/FlightLegsRetrieve contracts and associated aircraft, category, type and currency data.
GET /connect/v2/contractLoad organization-configured stages and trip types for scheduler forms.
GET /connect/v2/TripStageGET /connect/v2/TriptypeDocumented methods are prepared below; live writes remain disabled.
Manage account identity, contacts, trip defaults, preferences, tasks, notes, and customer history shared with Brokerage.
Choose a customer profile to review shared Scheduler and Brokerage information.
A large-format operational calendar prepared for Avianis trip synchronization.
Open monthly windows, manage trip opportunities, apply seniority guidance, review conflicts, and publish final decisions.
No active bid window is available.
Awarding a lower-seniority competing request requires a recorded explanation. Every window change and bid decision is retained in the audit history.
Awaiting award or denial
Same day or trip
Seniority setup required
Available this period
Create the next month automatically, open it on a consistent company-local schedule, and close it for review when the window expires.
Enable and save the rule to see the exact next opening and closing times.
Automatic periods use the normal review workflow. MyAxcess never publishes awards automatically, and a manually created period for the same month is never replaced.
New periods begin in Draft and must be opened manually.
Trips are never listed automatically. Scheduling must explicitly make each trip biddable; trip bidding remains available outside the monthly day-off window.
Each day shows the number of active crew bids. Run staffing analysis to evaluate coverage by aircraft type and crew position.
Sorted by administrator-assigned seniority, then pilot priority. Click a calendar date to filter this list.
Open a conversation by trip or flight identifier. Pilots use the same thread from the Flight tab.
Messages are shared with the crew through MyAxcess.
Enter a trip or flight ID to open the shared conversation.
Classify operational records and engine anomalies without changing the pilot’s original entry.
Unresolved items
Immediate attention
Human decisions
Closing an item creates a linked audit event; source records remain unchanged.
Create company-wide, role-based, or user-specific notifications. Critical alerts bypass Day Off Auto-Silence and remain visibly urgent until acknowledged.
Publishing records the administrator identity and UTC time. Critical alerts are intended only for urgent operational or safety-related information.
Cross-department governance, capacity, security, and audit reporting. Department-private details remain minimized.
Fleet coverage, qualified pilot-days, uncovered days, and low/base/high usage scenarios.
Role changes, device access, integration readiness, and protected-record activity.
Declined or outsourced trips by aircraft, PIC, SIC, maintenance, duty/rest, price, or suitability.
Awaiting authoritative trip and opportunity feeds.Measure qualified staffing coverage by aircraft without turning an informational analysis into an assignment or legality decision.
Coverage requires current duty schedules, aircraft assignments, qualifications, currency, leave, maintenance availability, and Part 91/135 eligibility. A green result does not assign crew or prove legality, fitness, or availability.
Measures published primary and after-hours coverage, vacancies, PTO conflicts, and manual schedule deviations across the next 60 days.
Connected and current
Current analysis period
Qualified and available
By aircraft and seat
Results remain unavailable until the required authoritative feeds are present.
| Aircraft Type | Required Crew | Qualified Pilot-Days | Demand | Reserve / Gap | Status |
|---|---|---|---|---|---|
| PA31 | 1 | — | — | — | Awaiting data |
| BE58 | 1 | — | — | — | Awaiting data |
| BE200 | 1 | — | — | — | Awaiting data |
| BE400XT | 2 | — | — | — | Awaiting data |
These rules come from the Staffing Management Setup work and remain separate from current operational facts.
One qualified pilot available for one calendar day.
PA31, BE58, and BE200 use 1 pilot-day per aircraft-day. BE400XT uses 2.
Contract pilots may cover Part 91 only and are excluded from Part 135 coverage.
Shared pilot availability is counted once and never duplicated across aircraft types.
Primary and backup assignments will populate here when current schedules and qualifications are connected.
Manage offline retention, review access changes, and triage application reports.
Operational cache uses local device time. Permanent data and protected submitted records are excluded.
Flights and trip packages outside this rolling local-calendar window are removed from this device.
Shows who changed a role, employee profile, trusted device, or offline-data policy. Personal UI scale adjustments are excluded.
Diagnostic metadata excludes passenger names and protected trip content.
Evaluate whether a charter request is suitable for aXcess-operated service. Avianis remains authoritative for any operated opportunity or trip.
This queue contains itinerary and passenger-count information. Brokerage carrier costs, margins, commissions, and customer documents are not exposed here.
Move charter requests from intake through sourcing, protected pricing, disclosure, acceptance, and trip support without crossing into aXcess operational control.
Administrators may review this workspace, but brokerage actions require a separately assigned job role.
OPERATED opportunities remain under Scheduling and authoritative Avianis control. BROKERED trips never receive aXcess crew assignment, flight release, flight-log, discrepancy, maintenance-control, or operational-feasibility actions.
Loading the administrator-controlled release gate.
Multi-leg requests awaiting sourcing or a customer decision.
Operator reviews, contribution exceptions, and brokered-trip holds.
Track prospects, follow-ups, estimated value, conversions, and lost opportunities without an external CRM.
Record calls, emails, meetings, portal activity, and internal notes as an append-only history. No message is sent from this screen.
This history records what already happened and schedules internal follow-up. Email, SMS, phone, Graph, and Dataverse writes remain disabled.
Capture the customer, complete multi-leg itinerary, passenger count, preferences, and fleet-fit routing.
Record operator responses manually and compare aircraft, availability, cost, terms, and verification status side by side.
Phone, email, and marketplace quotes can be entered here now. Each sourcing option becomes an immutable snapshot so later quote versions retain their original basis.
Build two to four options, protect company contribution, approve exceptions, and preserve every sent version.
Create expiring quote links, monitor customer views and acceptance, and prepare manual-first signature and payment requests.
Links use an opaque token whose plaintext is shown only when created. Internal carrier cost, contribution, margin, notes, and operational-control tools are never exposed. E-signature and Paynode writes remain disabled.
Create a new link from an issued quote, copy it once, and revoke it when needed.
Prepared records remain manual until approved provider adapters are released.
Maintain carrier authority, insurance, verification evidence, restrictions, and preferred status separately from sourcing responses.
Track contract, payment, carrier commitment, disclosure currency, customer acceptance, and carrier changes without taking operational control.
The direct air carrier retains operational control. Brokered trips never expose aXcess dispatch, crew-release, aircraft-release, or flight-release actions.
Track customer follow-up, sourcing, verification, document, payment, and trip-support work with named ownership and append-only status history.
See what each request still needs before a customer quote can be issued and accepted. This checklist reads MyAxcess records only and never performs a vendor write.
Intake, fleet review, sourcing, operator evidence, pricing, documents, issuance, and customer acceptance remain separate named steps.
Manage account identity, contacts, preferences, commercial references, tasks, and activity without exposing protected provider or margin data.
Choose a customer profile to review shared Scheduler and Brokerage information.
Review selling price, customer funds, operator payables, and immutable manual ledger events. Customer-facing documents never include internal economics.
Monitor operator approval, disclosure versions, delivery evidence, renewed acceptance, and carrier-change holds.
A brokered trip cannot return to Confirmed after a material carrier change until the replacement carrier is verified, a new disclosure version is issued, and renewed customer acceptance is recorded.
Export operationally separate brokerage metrics and review append-only commercial and compliance history.
Financial, legal, verification, and carrier-change events cannot be rewritten or deleted.
Review separate sandbox and production readiness, provider links, webhook intake, idempotent commands, reconciliation, and release gates.
Credentials remain server-side. No production command can be enabled until explicit approval and the provider-specific release gate are both recorded.
Publish immutable commercial-policy versions used for pricing floors, payment timing, and customer-facing disclosure language.
Saving creates a new effective version. Existing quotes, disclosures, generated documents, and acceptance evidence retain their original snapshots.
Every activation is named and time stamped.
Configure the identity, delivery language, operator-evidence requirements, and named staffing needed before a customer quote may be issued.
Internal intake, sourcing, and draft pricing may continue while incomplete. Issuing a customer quote remains blocked until every checklist item is complete and each quoted carrier has the required current evidence.
Customer quote issuance
Every change creates a new immutable version.
Your company identity, linked records, and offline devices.
Company profile
Pilot accessMicrosoft 365Not connected · read-only SharePoint access
Not connectedAvianis personnelNot connected
Not connectedBaldwin SMSThrough Avianis native integration
PlannedMicrosoft sign-in requiredRegistered devices appear after authentication.
OfflineChoose Push, SMS, Email, any combination, or no delivery for each alert type. New preferences start with Push only. Protected trip and passenger details remain inside MyAxcess.
On iPhone or iPad, add MyAxcess to the Home Screen before enabling push notifications.
Push is available now. SMS and Email choices are saved for the user and will begin delivering when their company connectors are enabled.
Use awarded days off and approved PTO to quietly queue routine notifications.
Store airline, hotel, and rental-car numbers for future FlightBridge bookings.
Membership numbers are encrypted at rest, displayed only in masked form, and reserved for server-side FlightBridge booking requests.
Optionally require this device’s built-in biometric verification before opening a remembered offline session. This does not replace Microsoft authentication.