Military Airfields / Parking Plans
Parking Plans
Aircraft parking plans with wingtip and taxilane clearance envelopes computed for you.
The problem
A parking plan is geometry, and getting it wrong is expensive
Placing aircraft on a ramp isn't just "does it fit." Every aircraft parked, taxiing, or fueling near another needs a real, measured clearance: wingtip to wingtip, wingtip to the nearest taxilane, taxilane centerline to the boundary behind it. Working that out by hand for a whole ramp, every time the aircraft mix changes, is slow, and a subtly wrong answer is exactly the kind of mistake that doesn't show up until something's already too close.
And a plan built once and never saved is worth nothing the next time the same aircraft show up. The whole layout gets reasoned through again from a blank map.
How it works
Place it, check it, save it as a real plan
- 01
Build the layout on your ramp's satellite map
Click to place an aircraft where it parks, drag to move it, or select several at once and move them together. The plan gets built the way the ramp actually gets worked, not typed into a form.
- 02
Clearance math starts from the right aircraft
Each aircraft's wingspan and length come from Glidepath's own library of 200-plus aircraft, so a plan's clearance numbers are right from the moment it's placed. Nobody looks up a wingspan separately.
- 03
Every clearance is checked, not assumed
Wingtip to wingtip, wingtip to the nearest taxilane, taxilane centerline to the boundary: each is checked against UFC 3-260-01 the moment an aircraft is placed or moved, and flagged in color if it's tight or actually violating.
- 04
A plan persists, edits, and exports
Reopen a saved plan and adjust it instead of rebuilding it, and export it to a PDF carrying the map, the aircraft list, and every clearance flag together.
Built on the regulation
The citation, implemented
- UFC 3-260-01
The wingtip and taxilane clearance distances Glidepath checks against every placed aircraft come directly from this standard, the same math a parking plan otherwise verifies by hand, aircraft by aircraft.
The benefit
What it automates
Clearance math runs on every aircraft, not just the ones you double-check
Every aircraft placed gets checked against UFC 3-260-01's wingtip and taxilane clearances immediately, instead of being caught later once something's already too close.
A plan is a record, not a redraw
Move an aircraft, adjust a taxilane, save it again: the same plan updates and persists, instead of starting over whenever the ramp's aircraft mix changes.
One export carries the whole picture
The PDF includes the map, the aircraft summary, per-spot coordinates, and every clearance warning or violation. Nothing gets re-measured to build a submission.
Related
Works alongside
FAQ
Straight answers
Where do aircraft dimensions come from?
Glidepath's own aircraft reference library (over 200 military and commercial types), so a plan's wingspan and length are pulled in automatically instead of looked up separately.
Does the app just draw the plan, or does it check clearance too?
Both. Placing or moving an aircraft checks it against UFC 3-260-01's wingtip and taxilane clearance distances immediately, and flags anything tight or violating in color.
Can I reshape a taxilane, or only draw it once?
Every point on a taxilane's centerline is editable (drag one to move it, click a midpoint to add a new one, or remove one), and clearance rechecks as you go.
What does the exported PDF include?
The plan's map, an aircraft summary table, per-spot coordinates, and a table of every clearance warning or violation, referenced to the UFC item it comes from.