Liveries

Livery Management is a quality control system that ensures pilots fly the correct aircraft type. When Pegasus ACARS detects an aircraft paint scheme during a flight, it creates a livery record. Staff review these liveries and approve, reject, or ignore them. A badge on the navigation item shows the count of pending liveries.

Accessing Liveries

In Orwell, go to Flight Centre → Liveries. You need the Can Manage Liveries permission.

How Liveries Are Created

Livery records are created automatically during PIREP processing — staff do not create them manually. When a pilot files a PIREP through Pegasus ACARS, the system detects the aircraft livery name and checks it against existing records. If no match is found, a new livery record is created with a pending status.

Livery Statuses

Status	Colour	Meaning
New	Grey	Not yet reviewed. Future uses flag PIREPs for review.
Accepted	Green	Approved by staff. Future uses will not trigger review.
Rejected	Red	Rejected by staff. Future uses trigger the Rejected Livery Rejector AutoReject.
Ignored	Blue	Marked as ambiguous. Future uses still flag PIREPs for review.

Tabs and Filtering

The livery table has five tabs:

• Pending — liveries awaiting review (default when pending exist, badge shows count)

• Accepted — approved liveries

• Rejected — rejected liveries

• Ignored — ignored liveries

• All — all liveries regardless of status

Additional filters are available for fleet, status toggles, and the user who last changed the livery status.

Table Columns

The table shows key livery information:

Column	Description
Name	The livery name as detected by Pegasus
Fleet Code	The fleet type this livery belongs to
Type	Detected aircraft type code (e.g. B738)
Aircraft	Detected aircraft name from the simulator
Addon	Detected addon package or developer (e.g. PMDG)
Simulator	Which simulator was used (MSFS 2020/2024, X-Plane 12, etc.)
PIREPs	Number of PIREPs that have used this livery
Status	Current review status (New, Accepted, Rejected, Ignored)

Review Actions

Livery review can be done directly from the table row actions or from the livery detail page:

Action	Effect	Effect on Pending PIREPs
Accept Livery	Marks as approved. Future uses pass without review.	PIREPs pending only for this livery are auto-accepted.
Reject Livery	Marks as rejected. Future uses trigger the Rejected Livery Rejector AutoReject.	No change to pending PIREPs.
Reject (Reject PIREPs)	Same as Reject Livery.	PIREPs pending only for this livery are rejected.
Reject (Invalidate PIREPs)	Same as Reject Livery.	PIREPs pending only for this livery are invalidated.
Ignore Livery	Marks as ambiguous. Future uses still flag PIREPs for review. Supports an internal note.	No change to pending PIREPs.

PIREP Auto-Processing Rules

When a livery action affects pending PIREPs, the system applies these rules:

• Only PIREPs in the Awaiting Review state are affected

• PIREPs where the pilot has already commented are skipped — they need manual review

• PIREPs with multiple other AutoReject failures are skipped when accepting — the PIREP needs review for other reasons

• Each affected PIREP gets a staff action log entry noting the change was made via Livery Review

Livery Detail View

Click any livery to see its full details:

• Livery information — name, fleet code, fleet name, detected aircraft name, type, addon, status, timestamps

• Internal note — markdown-formatted staff note (editable from the detail view)

• Review actions — same approve/reject/ignore actions as the table

• PIREP history — table of all PIREPs that have used this livery, with links to their review pages

• Next Pending Livery — header button to quickly navigate to the next unreviewed livery

Bulk Actions

Select multiple liveries using checkboxes to perform bulk actions. All require confirmation:

• Accept Livery — bulk approve selected liveries

• Reject Livery — bulk reject without affecting PIREPs

• Reject (Reject/Invalidate PIREPs) — bulk reject with PIREP processing

• Ignore Livery — bulk ignore with optional internal note

Typical Workflow

1. A pilot flies a flight with Pegasus ACARS

2. The system detects the livery name and creates a record if it's new

3. The Livery Name AutoReject flags the PIREP for review

4. Staff check the fleet code, aircraft type, and addon to confirm the correct aircraft was used

5. Staff accept the livery — the PIREP is automatically accepted if no other issues exist

6. Future flights with the same livery and fleet pass without review

Webhooks

Livery events trigger webhooks if configured:

• livery.created — new livery record detected during PIREP processing

• livery.updated — livery status changed (accepted, rejected, or ignored)

• livery.deleted — livery record removed

Related

• PIREPs — review PIREPs that may be affected by livery decisions