Civilian Airports / Parking
Parking
Aircraft parking with clearance envelopes computed against design standards.
The problem
Ramp geometry doesn't forgive a rough estimate
Two aircraft sharing a ramp, or one taxiing past a row of others, only work if the space between them is actually enough: not eyeballed, but measured against a real minimum. Redoing that math by hand across a whole ramp, every time a different aircraft type shows up, takes real time, and the kind of mistake that creeps in doesn't announce itself. It tends to show up later, as something parked closer than it should be.
None of that work carries forward if the layout isn't kept anywhere. The same aircraft come back, and without a saved plan, the ramp gets puzzled out again from scratch instead of being pulled up and reused.
How it works
Build the layout, and the clearance math runs itself
- 01
Drag aircraft onto the ramp the way they actually park
Click to drop an aircraft into position, drag it somewhere else, or grab a group and shift them all at once. The layout comes together the way the ramp is actually used, not filled out as a form.
- 02
Every aircraft already knows its own dimensions
Glidepath draws wingspan and length from its own reference set of more than 200 aircraft the instant one is dropped onto the map, so there's never a separate lookup before the numbers can be trusted.
- 03
The distances get verified, not eyeballed
Between two wingtips, from a wingtip to the closest taxilane, and from a taxilane's center to the edge behind it, Glidepath runs each of those checks the second an aircraft lands on the map or gets dragged somewhere new, coloring anything tight or over the line.
- 04
A saved plan is a plan you can reopen
Pull a saved layout back up and adjust it rather than starting fresh, or send the whole thing to a PDF that keeps the map, an aircraft rundown, and every flagged distance in one file.
Built on the regulation
The citation, implemented
- AC 150/5300-13B
AC 150/5300-13B sets the design-standard clearances a parking layout has to respect between aircraft, taxilanes, and the boundaries around them, the same clearances Glidepath checks automatically as each aircraft is placed, rather than leaving that math for someone to work out by hand.
The benefit
What it automates
Every placement gets its own check, on the spot
Nothing waits for a person to double-check it. Glidepath verifies wingtip and taxilane distances the instant an aircraft lands, well before anything could end up too close.
The layout remembers itself between visits
Nudge an aircraft, redraw a taxilane, hit save, and the plan holds the update and stays ready for the next time this exact ramp configuration comes up again.
The whole submission comes out of a single button
The PDF that comes out of it carries the ramp map, an aircraft-by-aircraft summary, coordinates for every spot, and anything still flagged, all pulled straight from the plan itself, with nothing left to reconstruct by hand.
Related
Works alongside
FAQ
Straight answers
Where does the app get an aircraft's wingspan and length?
From its own built-in reference set (over 200 aircraft), so those numbers populate automatically instead of getting looked up somewhere else and typed in.
Is this just a drawing tool, or does it check anything?
It checks continuously. The instant an aircraft is placed or dragged, its wingtip and taxilane distances get measured and colored if they're tight or crossed.
Can a taxilane be reshaped after it's drawn?
Yes. Grab any point on its centerline and move it, add a new point along the way, or delete one, and the distance checks update as you go.
What ends up in the exported PDF?
The map itself, a table summarizing every aircraft, coordinates for each spot, and a list of anything flagged tight or over a line.