Input
One PDF
Monthly roster PDFs work best when the trip chain is clear.
Calendar utility
Upload one crew duty plan, rewrite the visible carrier code, review the parsed legs, then download a standard .ics file. Your calendar app chooses which existing calendar receives the imported events.
Input
One PDF
Monthly roster PDFs work best when the trip chain is clear.
Output
.ics file
Import the downloaded file into whichever calendar you choose.
Trust boundary
Review first
Confirm parsed airports, times, and carrier codes before relying on the calendar.
Choose the carrier rewrite
Enter the code shown on the roster, then the code you want the calendar event titles to show. Routes, times, and flight numbers are preserved from the parsed PDF.
Conversion guide
1. Set the carrier swap
Match the code shown on the roster first, then choose the carrier code you want Calendar and Flighty to follow.
2. Name the .ics calendar
This becomes the calendar name embedded in the file; your calendar app still controls the destination calendar.
3. Upload the PDF
Use one monthly duty-plan PDF at a time so the parser can keep the leg list clean and predictable.
4. Convert and download
After conversion, inspect warnings and previewed legs before importing the .ics file.
What this tool can and cannot promise
Safer workflow
Inspect the converted legs first, then download the .ics file and choose the destination calendar inside your calendar app.
Before you import
Parsed legs are planning aids. Confirm operational changes, gate swaps, and airline status through official sources before you travel.
Check airports, local times, carrier rewrite, and deadhead labels against the original PDF before importing.
The website now returns a standalone .ics file. Apple Calendar, Google Calendar, Outlook, and similar apps ask which calendar should receive the events when you import it.
Calendar events are generated from the uploaded roster; they do not track delays, swaps, cancellations, or official TSA status.
Related tools