Shared Cloud Login · Copa Airlines MCO. Use the account created for you by the station administrator.
MCO OTP Mission Control — September 2026 · v9
Copa Airlines · MCO Cloud · September 2026 · 184 approved departures · Goal ≥ 85%
OPERATOR MODESelect who is entering the delay.
CONNECTING
Simplified workflow: enter delays only
Cloud mode: every supervisor signs in with an individual account. Delays and Early Birds are stored in the shared MCO database and sync across PCs. Normal on-time flights remain automatic. Monthly schedule changes and month closing are Admin-only.
Current OTP D0
—
No operated flights yet
Completed
0 / 184
184 flights remaining
On-time D0
0
Minimum month target: 157
Delayed flights
0
Maximum month allowance: 27
Delay budget left
27
To finish the month at ≥85%
Delay minutes
0
0 min average delayed flight
🎯 Path to 85% — Goal Runway
The central objective: keep enough D0 departures to finish the active month at or above 85%.
WAITING FOR DATA
—
CURRENT OTP
157 D0 flights required
With 184 approved departures, at least 157 must depart on time to achieve the 85% monthly target.
You can absorb up to 27 delayed departures during the month and still finish at ≥85%.
0%50%85% target100%
✈
⚡ Register Delay Only
Only enter delayed flights. The selected operator is stored with each entry. Existing records can only be changed or deleted in Admin Mode.
NOT REGISTERED
🚨 Delay Cause * Control Tower
21 delay categories measured against the same objective: protect the 85% OTP target.
Low impactWatchHigh impact
⚠ Recurring Category Watch
A category enters the watch at 4 delays. First management notice at 4; action plan required at 7. From 7 onward, every new recurrence triggers another action-plan alert.
No category has reached the 4-delay attention threshold yet.
📈 Daily OTP Trend
Daily performance with the 85% reference line.
🧭 Delay Impact by Category
Delayed flights by cause. Categories directly consume the monthly delay budget.
✈ OTP by Flight Number
Identifies which scheduled departure needs the most protection.
📚 MCO Monthly OTP History
Closed months keep only the final OTP result in the shared record.
CLOUD HISTORY
Close Month is Admin-only. When a month is closed, its final OTP is saved here and the detailed cloud schedule/events for that closed month are removed.
🏁 AAA Station OTP Challenge — MCO vs IAD · LAX · JFK · MIA
MCO updates automatically from this dashboard. Enter the other AAA stations' OTP manually to create a live competition against the 85% goal.
COMPETITION
AAA Station OTP — Manual Input (Admin)
AAA station values are manual benchmarks stored in this browser. MCO is automatic. Enter Admin Mode to edit IAD, LAX, JFK or MIA.
Enter station OTP values to start the challenge.
The leaderboard ranks stations with available OTP data.
🗓 September 2026 Operational Heatmap
Click any date to review performance. Operated flights without a delay entry are automatically D0.
≥85%70–84.9%<70%
Flight Log — September 2026
184 approved departures loaded. Only delayed flights require entry; already-operated flights without a delay record count automatically as D0.
Date
Day
Flight
STD
ATD
Status D0
Delay Min
Early Min
Cause
OTP Impact
Entered By
Remarks
Action
Recurring Delay Category
0Occurrences
0Delay minutes
0OTP points used
0Delay budget used
Suggested plan of action
Upload Monthly Flight Schedule
Upload an approved monthly schedule in Excel (.xlsx/.xls) or a text-based PDF. The dashboard will detect outbound flights, month/year, STD and approved departure count before anything is applied.
WAITING FOR FILE
0Approved departures
0Flight numbers
0D0 needed @ 85%
0Max delayed @ 85%
Choose a monthly flight file from the Upload Monthly Flights button.
Excel import supports the MCO monthly matrix format (OUTBOUND + day columns) and standard Date / Flight / STD tables. PDF import works with PDFs that contain selectable text; scanned/image-only PDFs require an Excel version or a text-based PDF.
Date
Day
Flight
STD
No schedule parsed yet.
Admin Login
Enter the Admin PIN. On first use, you will be asked to create one.
Manage Operators
One operator per line. These names will appear in the Operator selector and will be stored with new delay entries.