TOGA · javeri.ca
Key Finding — DBM Effect
Loading…
QS by Month
Loading…
Months on Record
Newest first · tap a month to open it
Loading…
Intel Notes
Loading…
Loading…
Awarded Pairings Database — every pilot, every month
Every pairing awarded across the whole YUL B787 FO category, month by month, taken from the Category Block Reports. This is what was held, not what was offered. It is the raw data behind the Holdability section above. Your rows are highlighted.
| Month | BH | Pilot | Pairing(s) | Dest | Tier | Local Nights | TAFB | Layover | Hotel | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||||
Destinations — tier legend
Every destination the tracker knows, grouped by tier. The tier sets the colour of a destination everywhere on the site. Tap a code anywhere for its note.
Loading…
Blocks — Category Block Report, All Pilots
Sort by
Loading months…
| Position | Name | Sen. | Pairings | Destinations | Notes |
|---|---|---|---|---|---|
| Loading… | |||||
Category — YUL-787-FO · Position Assignment List
Loading…
| # | Sen. | Name | From | Activation |
|---|---|---|---|---|
| Loading… | ||||
The official category from the latest CMSC review: who holds a seat, in order. An amber activation date is still ahead — the pilot holds the position on paper but is not flying it yet. Activation is the contractual pay date, not a training date; a pilot can reach it untrained. The monthly roster on each month page is who actually bid.
Company Seniority — Pilot System Seniority List
Loading…
| Sen. | Emp ID | Name | Status |
|---|---|---|---|
| Loading… | |||
Seniority Events
| Effective | Emp ID | Pilot | Event | Reason | Pos | Source |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Backup — a copy of all your data, in a file you keep
Press it just before Claude loads a month's data, and again after. The first file is a copy of everything as it was before any new row went in. The page reads every table without changing anything and gives you a file; put it in your Google Drive folder and keep the last three (on a phone or iPad, use Share and choose Save to Drive). The JSON file is the complete copy — the bid tracker, the logbook (including its import receipts), the quiz, the surveys and the recommendations. Put that file back with Restore below. The ZIP holds one spreadsheet per table to read in Excel or Sheets.
Restore — put a backup file back
Choose the JSON backup. Check this file only counts: for each table, how many rows are already stored and how many would be added. Nothing is written yet. Add the missing rows then inserts only the new ones. A row that is already stored is left as it is — not changed, not deleted. Checking the same file again afterwards should add nothing. This does not restore the sign-in.
Import New Month Data
Paste the table-keyed JSON block Claude gives you after parsing a block report, score report, seniority list or pairing package, then press Push. The page shows the rows, writes only the ones that are not already stored, then reads the counts back. Pushing the same month again inserts nothing and says why. A new month, or a new line on a month already there, is still added. A skip does not change the row that is already there. Accepted tables are the keys shown in the box below; the monthly pairing package (what was offered) goes in as package_pairings.
Monthly Cycle — Two Moments
The tracker is fed twice per bid month. Moment 1 when the pairing package publishes and the bid is built; Moment 2 on award day. Each moment: hand the documents below to Claude in a Claude Code session. Claude parses them, shows you the exact rows, waits for your "go", writes them to the database directly and reads the counts back. Nothing is written without that go. The month then appears, or fills in, on the Months tab. The Import tab is the manual fallback, not the normal path.
Pre-Bid Verification Protocol — Mandatory Before Every Bid Save
Adopted Aug 16, 2026 after the September miss: the manual's RESERVE AWARDS and SDO sections were in hand all along and never cross-checked against the strategy. The bid was verified to fire — nobody verified what firing delivered. No monthly bid is validated or saved until all three steps below are done. Claude initiates this proactively at every bid session, before bid close. First run: October 2026, Sep 4.
Step 1 — Manual cross-check
Re-read the relevant PBS manual sections against the drafted bid: every bid-option mechanism used, RESERVE AWARDS whenever reserve is a possible outcome, and the SDO section whenever a critical date exists. Goal: surface any mechanism the manual describes that touches the strategy and wasn't considered.
Step 2 — Failure-mode walkthrough
For every protection layer in the bid, state in writing: if this layer activates, what does the award look like, and what does the next layer actually guarantee? — each answer sourced to the manual, not assumed. September's walkthrough would have read: isolate fires → reserve → reserve pyramid is preference-only, coverage beats it → wedding day callable → SDO required before bidding.
Step 3 — Critical-date gate
A hard immovable date in the month? An approved SDO via myaccess is the only accepted protection. Bid-line protection alone — isolates, avoids, reserve pyramids — means the plan is incomplete, and the bid does not get saved until that is said out loud. Vacation needs nothing: PBS builds around it on its own.
How the SDO works (Seb, Sep 9): requested two months ahead — for a date in month M, ask in month M−2, before M's package is even out. Once approved it overrides any schedule or reserve: nothing can be assigned on an approved SDO. So the SDO decision comes a month before the bid, not with it.
How the SDO works (Seb, Sep 9): requested two months ahead — for a date in month M, ask in month M−2, before M's package is even out. Once approved it overrides any schedule or reserve: nothing can be assigned on an approved SDO. So the SDO decision comes a month before the bid, not with it.
Moment 1 — Package & Bid
When
Pairing package published → before bid close.
Documents to bring
· The Pairing Report PDF (e.g. OCTUL787_Pairing_Report) — the native PDF parses fine
· Planning numbers: DBM and blocking window, the official ones
· Your critical dates and vacation for the month
· After saving: a screenshot of the saved bid and of the Analyzer, sorted by Time Factor
· Planning numbers: DBM and blocking window, the official ones
· Your critical dates and vacation for the month
· After saving: a screenshot of the saved bid and of the Analyzer, sorted by Time Factor
Written by Claude, after your go
months (1 row) · package_pairings (one row per pairing in the package) · bid_lines (the saved bid)
What appears on the Months tab
Planning Environment · Pairing Package (available destinations, FO) · Estimated Holdability from the last 12 awarded months · Bid Submitted
Before close — every month
· Check consecutive days reads 7 on Other Options
· Thinking of a domestic isolate or avoid? Read the via domestic column first — it catches international trips that connect through YYZ/YVR
· Analyzer diagnostic: click into wanted pairings not near the top, unwanted ones near it
· Remember the special bids (Work Periods, Days Worked, NN Day Breaks) never show in the Analyzer
· Optional: submit bid + Analyzer output to the ALPA PBS Committee via DART
· Thinking of a domestic isolate or avoid? Read the via domestic column first — it catches international trips that connect through YYZ/YVR
· Analyzer diagnostic: click into wanted pairings not near the top, unwanted ones near it
· Remember the special bids (Work Periods, Days Worked, NN Day Breaks) never show in the Analyzer
· Optional: submit bid + Analyzer output to the ALPA PBS Committee via DART
Moment 2 — Award Day
When
Block awards published (usually early in the prior month's last week).
Documents to bring
· Single Block Report — your awarded block
· Block Score Analysis — the score report
· Fleet Category Block Report, all pilots
· Reserve and no-block lists for the full seniority picture
· Block Score Analysis — the score report
· Fleet Category Block Report, all pilots
· Reserve and no-block lists for the full seniority picture
Written by Claude, after your go
pairings_awarded · score_report_lines · roster · pairing_db · lessons · the months row updated (QS, classification, diagnosis, award status)
What appears on the Months tab
Observed Holdability (who actually held what) · Your Awarded Pairings · Score Report · Diagnosis · Lessons Learned
Read together
· The award against the bid: did the targets land, what filled the rest, was anything a surprise
· Offered vs held per destination — was a miss "senior-locked" or "thin that month"
· Anything worth keeping goes into Lessons and into the handout the same session
· Offered vs held per destination — was a miss "senior-locked" or "thin that month"
· Anything worth keeping goes into Lessons and into the handout the same session
Seniority Cycle — Company List Upkeep
Per equipment bid: bring the CMSC Line Status Report (and any monthly retirement list) to a session. Claude parses it, shows the event batch for approval, then inserts into seniority_events directly. Rules: paired active/inactive rows with matching dates are transfers (no seniority effect); effective dates are scheduled, not applied early; Medical and ALPA leave are reversible, retirements and ITF are not.
Each January: bring the new Pilot System Seniority List PDF. Claude parses and validates it, loads it under the new list year (about 5,900 rows, in batches, each shown for approval), and reconciles the year's logged departures against positions gained. Your list number changes with each new list — the tool compares month by month for that reason.
Each January: bring the new Pilot System Seniority List PDF. Claude parses and validates it, loads it under the new list year (about 5,900 rows, in batches, each shown for approval), and reconciles the year's logged departures against positions gained. Your list number changes with each new list — the tool compares month by month for that reason.
Import Tab — Manual Fallback, Read Before Every Push
0. The normal path is Claude writing rows after your go, with counts read back. Use the Import tab only when you have a JSON block in hand and no session open.
1. Push shows the rows, then writes only what is not already stored. Pushing a month that is already loaded inserts nothing and says why. It does not change a row that is already there.
2. After every push, read the counts the page reads back before trusting the result.
3. If a push fails partway, push the same block again. Rows already stored are skipped, and only what is missing is written.
1. Push shows the rows, then writes only what is not already stored. Pushing a month that is already loaded inserts nothing and says why. It does not change a row that is already there.
2. After every push, read the counts the page reads back before trusting the result.
3. If a push fails partway, push the same block again. Rows already stored are skipped, and only what is missing is written.
LOADING FLIGHT DATA…
| Date | Flt | Route | G/C Dist | Type | Reg | CREW | Block | PIC | SIC | Dual | FI | XC | IFR | Night | TO | Ldg | RMKS |
|---|
Career totals
Recency & currency
Block hours per month
Months year-over-year
Yearly block totals
Cumulative career hours
Hours by aircraft type12-mo average · stacked
Top city pairs
Records
New airports per year
Average sector lengthnm · per year
On this day
Night flying share% of block · per year
Function splithours · per year
Red-eye departures22:00–04:00 · % of flights
Type timeline
Top tails
Most flown with
Engine power
Aircraft model
Function
Top 10 flight durations
drag to rotate · pinch or scroll to zoom
| Code | Airport | Visits | Routes | Coordinates |
|---|
| Pilot | Company | Flights | Block | Last flight | Notes | Rating |
|---|
Presets
Saved queries
None yet — build a query below and save it.
Edit entry
Edit aircraft
Edit airport
Edit pilot
Confirm?
AC Monthly Import
| Date (Z) | Flt | Route | OUT–IN (Z) | Block | Night | TO | Ldg | E | PIC | Status |
|---|