Military Airfields / FLIP Management
FLIP Management
Flight Information Publication accountability and currency, tracked.
The problem
Publication accountability is easy to promise and easy to lose track of
Knowing which flight information publications the airfield holds, whether each one's been reviewed against the current edition, and who coordinated the last non-procedural change is supposed to live in one continuity record, not in whichever custodian happens to remember it.
And a change that skips a review step, or gets published without anyone confirming who approved it, is exactly the gap a continuity binder exists to close.
How it works
The continuity binder, kept current instead of filed away
- 01
The publication list you actually hold
The Local FLIP List is the single source for what your airfield holds. Every review pulls its publication choices from that list, not from someone retyping a title.
- 02
A change moves through the same three stages every time
Coordination, then submitted and awaiting publication, then completed. Every non-procedural change follows the same board, with dates, a NOTAM reference, and a PDF attached at each stage.
- 03
A review is signed in order, not all at once
Documenting a FLIP review (publication, effective date, any discrepancy found, the corrective action) locks only after three sequential sign-offs, each one unavailable until the one before it is done.
- 04
Every step keeps who and when
A published change captures who posted it and the date; a signed review captures the signer's name and a timestamp, permanently, once signed.
The benefit
What it automates
The publication list is the only list
Reviews pick a publication from the Local FLIP List instead of a free-text field, so a review can't reference something that isn't actually one the airfield holds.
Sign-off order is enforced, not just expected
The second and third signatures on a review simply aren't available until the one before them is in, so there's no way to sign out of order.
A change's record doesn't end at "published"
Who posted a change and when is captured at the moment it happens, not reconstructed afterward from memory.
Related
Works alongside
FAQ
Straight answers
Where does the list of publications for a review come from?
The Local FLIP List, the single record of what the airfield holds. Reviews choose from that list rather than free text, so a review can't reference something that isn't tracked.
Can a review be signed out of order?
No. Each review has a sequence of required sign-offs, and a later one simply isn't available to sign until the one before it is complete.
How does a non-procedural change move from idea to published?
Through three stages on the same board (coordination, submitted and awaiting publication, then completed), with the relevant dates, a NOTAM reference, and a PDF attached along the way.
Is there a record of who published a change and when?
Yes. Publishing a change captures the posting date at that moment, part of the permanent record rather than something reconstructed later.