> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt
> Use this file to discover all available pages before exploring further.
# How to Use the Release Checklist
> Complete the pre-departure release checklist to verify crew qualifications, aircraft airworthiness, weather review, NOTAMs, fuel plan, weight and balance, passenger manifest, and customs compliance before dispatching a trip.
By the end of this guide, you will have completed the pre-departure release checklist -- verifying crew qualifications, aircraft airworthiness, weather, NOTAMs, fuel plan, weight and balance, passenger manifest, and customs compliance -- and released the trip for dispatch.
The Operations module must be enabled for your workspace. You also need the appropriate operations
permissions. Contact your workspace administrator if you cannot access these features.
You need the `dispatch.release` permission to complete the checklist and release a trip.
## Prerequisites
* The trip must be in **Confirmed** status with aircraft and crew
assigned.
* All trip legs must have departure and destination airports set.
* A current weather briefing should be available (auto-fetched or
manually uploaded to the trip binder).
## Open the release checklist
### Step 1: Navigate to the trip detail page
Open the trip from the **All Trips** list, the **Dispatch Board**,
or the **Schedule** page. The trip must be in **Confirmed** status.
### Step 2: Click Release
In the trip detail header, click the **Release** button. The
Release Checklist dialog opens as a full-page overlay with all
checklist items displayed.
Alternatively, you can access the checklist from the **Dispatch
Board** by clicking the **Release** action on the trip's queue card.
The **Release** button is only visible on trips in **Confirmed** status. If the button is not
visible, verify that the trip status is Confirmed and that you have the `dispatch.release`
permission.
## Checklist items
The release checklist is organized into five groups: **Crew qualifications**, **Aircraft airworthiness**, **Flight planning**, **Passenger and customs**, and **Trip binder**. Each item has a checkbox, a status indicator (green for passed, red for failed), and supporting detail.
Some items are auto-checked by PlaneConnection based on crew profile data, aircraft records, and trip timing. Items marked "Manual" require you to verify the condition outside the system and check the box yourself.
Auto-checks rely on current data in crew profiles. If a pilot has recently renewed a medical
certificate or completed a proficiency check, ensure the record has been updated in their crew
profile before attempting the release. Stale data will cause false failures.
## Complete the checklist
### Step 1: Review auto-checked items
Scan the checklist for items that are already checked (green
indicator). These have been verified automatically. Review the
detail text for each to confirm the data is current.
If an auto-checked item shows a red indicator, click the item row
to expand the detail panel, which explains the failure reason (e.g.,
"PIC medical expires in 2 days -- valid for departure but will
expire before return leg").
### Step 2: Verify manual items
For items that require manual verification (marked with a "Manual"
badge), perform the check outside the system and then check the
box:
* **MEL items reviewed** -- Open the aircraft discrepancy list,
review any open MEL deferrals, and confirm the aircraft is
dispatchable under the MEL.
* **NOTAMs reviewed** -- Read through the NOTAMs in the trip binder
and confirm no NOTAMs affect the planned operation.
* **Fuel plan adequate** -- Verify the fuel load on the fuel plan
meets regulatory minimums for the route and conditions.
* **Alternate airport designated** -- Confirm an alternate is filed
if weather at the destination is below alternate minimums.
* **eAPIS filed** -- Verify the eAPIS filing confirmation document
is in the trip binder.
* **Customs/immigration arranged** -- Confirm CBP notification or
customs clearance for international arrivals.
* **Required equipment operative** -- Verify that all equipment
required for the specific operation (RVSM, ETOPS, overwater) is
functioning.
When you check a manual item, you are attesting that you have
personally verified the condition. Your name and timestamp are
recorded on the checklist record.
### Step 3: Add notes (optional)
Each checklist item has a **Notes** field where you can document
observations, exceptions, or context. For example:
* "MEL: Autopilot yaw damper deferred per MEL 22-01, flight
restriction noted -- VFR only."
* "Fuel plan includes 200 lb extra for forecast headwinds."
Notes become part of the permanent release record.
### Step 4: Address any failures
If any item has a red indicator (failed auto-check or unchecked
manual item), the **Release Trip** button at the bottom of the
checklist is disabled. You must resolve the failure before
proceeding.
Common resolution paths:
| Failure | Resolution |
| ---------------------------------- | ---------------------------------------------------------------------------------- |
| PIC medical expired | Update the crew profile with the renewed medical, or assign a different PIC. |
| Aircraft has grounding discrepancy | Resolve the discrepancy in the maintenance module, or assign a different aircraft. |
| Weather briefing stale | Click **Refresh Weather** to fetch a current briefing. |
| W\&B missing | Complete the weight and balance calculation on the trip Legs tab. |
| Trip binder incomplete | Upload missing documents to the binder. |
### Step 5: Release the trip
When all items show green indicators (checked), the **Release
Trip** button becomes active. Click it to release the trip.
The trip status changes to **Released**. A release record is
created containing:
* Every checklist item with its status and any notes.
* The name of the dispatcher or PIC who completed the release.
* The timestamp of the release.
* A unique release reference number.
Crew members assigned to the trip receive a notification that the
trip has been released with all documents available in the trip
binder.
## Override a blocked item
In exceptional circumstances, a blocked checklist item can be
overridden by an authorized user.
Overrides are intended for situations where the system data is incorrect or where a regulatory
exception applies. Overriding a legitimately failed item without proper justification violates
your organization's operational control procedures and may constitute a regulatory violation under
14 CFR 135.
Only users with the **chief\_pilot** or **director\_of\_operations**
role can override blocked items. To override:
1. Click the failed item row to expand it.
2. Click **Request Override**.
3. Enter a mandatory justification explaining why the override is
appropriate (e.g., "Medical renewal completed today, paperwork
in transit, verbal confirmation from AME Dr. Smith").
4. Click **Approve Override**.
The item changes to a yellow "Overridden" indicator. The override,
justification, and authorizing user are recorded in the release
record.
## View release history
Every release creates a permanent, immutable record. To review past
releases:
1. Open the trip detail page.
2. Click the **Timeline** tab.
3. Release events appear as timeline entries with a link to the
full release record, including every checklist item, notes,
overrides, and the releasing dispatcher's name.
Release records are retained for the duration configured in your
workspace settings (minimum 12 months per 14 CFR 135.63).
## Related
Assemble documents required by the release checklist.
Complete the FRAT that the release checklist verifies.
Keep crew qualifications current to pass release checks.
Resolve aircraft discrepancies that block release.