Military Airfields / PPR
PPR
Prior Permission Required, from public request form to approval to the PDF log.
The problem
A request to use the airfield starts before anyone official sees it
Someone wants to fly in, park, or operate on the airfield with prior permission required, and that begins as a public request, with no guarantee it reaches the right person, gets routed to everyone who actually needs to weigh in, or gets an answer back before the date it's needed.
And once more than one office has to sign off (one agency's concurrence, then another's, then a third's), tracking who's actually answered and who's still pending becomes its own small project, on top of the requests themselves.
How it works
From a public form to a signed-off approval
- 01
A public form, no account required
Anyone can submit a PPR request with their contact information, the aircraft or callsign details, and the date they need: no login, no separate system to learn first.
- 02
Every request starts in review
A submitted request lands in a review queue first: routed into coordination if it needs more than one office's input, approved directly if it doesn't, or denied, with the requester notified either way.
- 03
Coordination tracks every office, not just one
Each agency assigned to a request gets its own notification and records its own concurrence or non-concurrence. The request only clears coordination once every assigned office has actually responded.
- 04
The log and the export are the same record
Every request, its status, and its full coordination history live in one log, exportable to a PDF for a single request or the whole filtered list.
The benefit
What it automates
Nobody has to already know who to call
A public form is the only thing a requester needs. Routing the request to the right offices happens inside Glidepath from there.
Coordination can't finish quietly incomplete
A request only advances to approval once every assigned agency has actually responded, not once someone assumes they would have said yes.
One log, one export, nothing reassembled
Status, contact details, and the full coordination history live on the same record, exportable to a PDF without pulling it together from a few different places.
Related
Works alongside
FAQ
Straight answers
Does a requester need an account to submit a PPR?
No. The public form takes their contact information, the details of the request, and the date, with no login required.
What happens after a request is submitted?
It lands in a review queue first. From there it's either routed to the offices that need to weigh in, approved directly if it doesn't need coordination, or denied. The requester is notified either way.
How does multi-office coordination actually work?
Each office assigned to a request gets its own notification and records its own concurrence or non-concurrence. The request doesn't move to final approval until every assigned office has actually responded.
Can I get a record of a request, or all of them?
Yes. Export a single request or the full filtered log to a PDF, including its coordination history and any remarks.