GYP Trip Data Intake

v7.2 — Cloudflare edition with the complete GYP operational rundown generated on this page.

The key is sent only to your own Netlify Functions in the X-GYP-Key header.
Drop the full schedule here or click to choose a file — XLS, XLSX, CSV, TXT and text-based PDF supported
GYP extracts all route airports and keeps the schedule text so the copied package can analyze every trip and build a fleet-priority board.
Drop all flight-plan PDFs here or click to choose multiple PDFs at once — text PDFs and scanned/image-only ICAO plans are supported; each flight-plan page is matched by tail / departure / destination
Optional. ARINC/FAA ICAO forms are read page-by-page. Image-only pages are OCR’d automatically. If a matched plan contains a usable filed route, enroute hazards are screened against that route; unresolved geometry falls back safely to the airport-to-airport corridor.
ICAO is best. 3-letter U.S. codes usually work too because GYP resolves ICAO from the FAA response when possible.
Required. Include the trip date plus scheduled departure/arrival times so GYP can compare hazards to the actual flight window.
FAA NMS NOTAMs Filed flight-plan routes Runway baselines Current METAR Current TAF SIGMETs G-AIRMET 0–12 hr forecasts PIREPs CWA / TCF when available Zoom Earth Radar Links
Advanced: FAA NOTAM effective-time filter (UTC)
This only filters FAA NOTAMs. Leave blank for normal GYP use.
Default 175 NM each side. With a matched flight plan, GYP follows resolved filed-route points; otherwise it uses the airport-to-airport route.
No trip data fetched yet.