Civilian Airports / Events Log
Events Log
An attributed, chronological record of the airport day, with status changes posting themselves.
The problem
Reconstructing today from memory afterward is where details go missing
An inspection kicks off. A NAVAID trips from good to degraded and back. A discrepancy gets closed out. Each of those lives inside its own screen, and putting together an accurate account of the whole day means opening several of them and hoping nothing important happened somewhere nobody thought to check.
Even once something does get written down, a note by itself doesn't say much. Whether it came from the system or from a person, and exactly when it was entered, matters just as much as its content, especially the first time somebody outside day-to-day operations asks to see it.
How it works
A single feed, built from what already happens
- 01
The system writes its own entries
A NAVAID moving from operational to degraded, an inspection or check starting or wrapping up: these land in the feed on their own, at the moment they happen, with no extra step for anyone to remember.
- 02
Anything else gets typed once
A call from the tower, something spotted on a drive-around, a coordination note: type it straight into the log, using a template or free text, and it takes its place in the same feed as the automatic entries.
- 03
Zoom into exactly the window that matters
Today, the last week, the last month, or any custom range in between narrows the feed down instantly, so pulling together a specific stretch of activity doesn't mean scrolling past everything else first.
- 04
One click turns the feed into a document
Excel or PDF, built from whatever's currently on screen, so a filtered slice of the day becomes something shareable without anyone retyping a line of it.
The benefit
What it automates
Most entries write themselves
The system's own status changes and completions populate the feed without anyone stopping to log them by hand, so the record exists independent of whether someone remembered to.
A specific window, not the whole history
Today's activity, last week's, or a custom range pulls up on its own, so answering a question about a particular stretch of time doesn't require scanning everything ever logged.
Every row says who, and exactly when
Zulu timestamps and operator initials sit on every entry, automatic or manual, so nothing in the feed is a mystery about its source.
Related
Works alongside
FAQ
Straight answers
Does someone have to log every NAVAID change or completed check by hand?
No. Those post to the feed on their own the moment they happen. Typing something in manually is for whatever the app itself didn't see, like a phone call or a radio call.
Can the log be narrowed to a specific stretch of time?
Yes. Today, the last 7 or 30 days, or a custom range all filter the feed down to just that window.
Is it clear who made a manual entry?
Yes. Every entry, automatic or manual, carries the operator's initials alongside its timestamp.
How do I turn part of the log into something I can share?
Whatever's currently on screen, filtered or not, exports straight to Excel or PDF in one step.